Similarly, the development processes supporting that product have to be on par with those in the larger companies. This means that the smaller company’s product-development infrastructure will be competing along with the product itself.

The product may require a global design team with offshore manufacturing; it may need integrated mechanical and electronics subassemblies; and it may need to be re-designed, or at least updated, every six months. These needs must be supported by the infrastructure. The larger company is almost certainly going to have a product data management (PDM) repository to manage file versioning and team collaboration; the smaller company may not. The more complex the product, the greater the difficulty SMBs will experience in conducting effective collaboration.



A typical PTC Windchill ProductPoint product home page. ProductPoint is based on Micrsoft’s SharePoint technology.

Collaboration, and in particular, file sharing – is key to competing through product-development, yet most SMBs are using less than adequate tools for sending and sharing files. Some work by email; others use shared network folders or FTP sites. Each presents significant problems:

• Search –Searching for a part from memory or by part number is a hit or miss proposition. A usable part file may or may not be identified based on the quality of the CAD database. The time spent searching and scanning for designs by part number and scanning paper documentation deprives a company of product excellence. Even if the most recently product part is located, it may not be the best variation to serve its purpose.

• Naming – Without an automated naming mechanism, smaller companies are forced to track all design changes manually, and to create an effective naming system for parts and assemblies. In practice, file names for parts and assemblies can become more random than consistent, as engineers resort to using their own names, file-save dates, original vendor part numbers, or other strategies to keep track of files.

• Versioning – Different users may be working on different components of the same assembly at the same time, so it is critical to keep track of the versions of files as they are checked in and checked out of the central repository. Also, it should be possible to roll versions back, because changes to one component may affect how other components function within the assembly.

• Conflicts – Without a multi-user conflict-resolution framework, shared files run the risk of introducing redundancy and errors into product designs, since it’s possible for multiple users to make conflicting changes simultaneously.

• Robustness –A part file may have relationships to five thousand other parts that make up a single assembly, and an assembly may have relationships with other parts and other assemblies. A CAD designer (or test or manufacturing engineer) should be able to see at a glance all dependencies of the part he or she is working on. For standard email, shared network folders, and FTP sites this is impossible.