The IEC 61499 gives developers considerable freedom and offers several features that support reuse. Although this can help the adoption of the standard into an organization's development process, the range of design decisions can also harm the reusability of software, if components are developed with incompatible design principles. Guidelines are needed, but the unique backgrounds and market positions of industrial players must be respected. The paper analyzes some alternative solutions that were developed by automation designers using IEC 61499; although the solutions differ considerably, it is very difficult to rate their reuse potential absolutely. The factors that must be addressed in a reuse strategy are discussed, concluding with the suggestion that it is not possible to present detailed guidelines that would apply to the entire industry