What is the process to take my idea into production?

The flowchart below diagrams the steps of a typical OEM Solution

How do I assure I'll get what I want?

It is necessary to have clear and candid discussions with our design team to convey everything you're trying to accomplish. This includes not only the performance requirements for the product, but must also cover business issues such as regulatory compliance, product life cycle management, service and support strategies and IP ownership. These discussions occur in the "document expectations" portion of the process shown above.

The outcome from these discussions (typically a RFQ or Requirements Document) is written documentation that casts all features, performance requirements and expectations into three categories.

Specifications

The list of measurable criterion that describe the operation, performance and quality of the product.

Compliance

The method used to demonstrate that the product meets each specification of the design goals.

Assurance

The sub-list of compliance methods applied to each unit to assure production quality goals.

What do I need to get started?

Laser testing a customized linear motor stage. This is an example of a method used for both compliance & assurance.

The success of an OEM solution is highly dependent on the ability to accurately and completely describe your project. We recommend organizing your information into four topics:

Detailed Description

This is a description of the general operation or use of the machine or product. It may include concept sketches or drawings. It should discuss not only the operation of the product, but how it works with other components and systems. For example: most applications require some 'item of interest' to be put onto the positioning stage as part of the payload. Describe how the stage interacts with and interfaces to other equipment. If you expect new generations of the product to improve on some performance or feature, be sure to describe it now. Here it is most effective to describe what you want to accomplish rather than how it will be accomplished.

Technical Specifications

Over-specifying a project can increase its cost. Increased costs can be avoided by recognizing that many applications are actually a series of smaller tasks. Describe and specify each of the tasks individually. For example: many short high speed moves may be required in one part of an application, and long moves at slower speed may be adequate in another part. If only one higher speed specification is offered it may result in a more expensive drive train to accommodate greater thermal effects than is actually necessary.

Compliance and Assurance

Have an idea as to how to test compliance for every specification. Recognize that some specifications are 'tested' through analysis rather than measurement. Assurance testing occurs on production units and is a sub-set of the compliance tests. Be aggressive in paring down the assurance tests as more tests have higher costs.

Business Requirements

An OEM solution that is too expensive is not a solution. Determine your target development, prototype and production costs up front to give us a guideline with which to make trade-offs. These must be determined in the context of quantities: monthly, yearly and/or lifetime. Also describe your service strategy, product life-time, packaging, documentation, warranty and deliverable requirements.

What does it cost?

Custom measuring tool used to verify the flatness of a multi-axis stage against a granite surface. This is an example of a method used for both compliance & assurance.

There are three costs associated with OEM Solutions: engineering, prototype and production.

Engineering Cost

A one-time charge to cover our design, documentation and other engineering time based on complexity and project schedule.

Prototype Cost

The unit cost to build one or more prototypes based on the complexity, quantity and schedule.

Production Cost

The cost of a production unit. This may require a minimum order quantity with scheduled delivery.

Most projects exist to meet a targeted production cost, therefore the design, components and processes used to manufacture the product are directed toward this goal. Engineering and prototype costs are determined by the complexity of the project, schedule and other business requirements.

What if I want to make changes?

Even if the prototypes meet or exceed all requirements, changes may be necessary for many reasons: re-evaluation of performance based on prototype, new or revised features or business changes that affect the project. The schedule and cost for any changes are determined by the nature of the changes.

What's next?

Give us a call to review your requirements and determine if an OEM solution is right for your application.