Simple philosophy

Vision; take the time up front to analyze ALL (emphasized) requirements necessary to formulate a complete solution that meets a client<92>s requirements expectations. There are no shortcuts to achieve quality; careful planning always creates a clear path towards implementation and generally achieves a consistent high quality product.

JCM Functional Test Process

1. test Strategy Creation/Architecture Definition
   1. Project Planning and Resources Allocation
2. Test Plan Creation, Design Requirements (HW,SW,MECH)
3. Design/Parts Procurement
4. Integration
5. Verification
6. Implementation, Turn-Up
7. Support/Maintenance

The goal of any manufacturing test process is to ensure the highest quality product consistently ships; however, easier said than done. The test strategy is a key to understanding all the requirements a Test Architecture must support. The test strategy must consider quality targets, volumes, likely test setups, data, equipment costs and most importantly, support/maintenance costs/expectations. The Test Strategy can be further enhanced to include more requirements or to migrate legacy products/processes.

The Test Strategy Document clearly details the strategy for testing the product at both unit and system levels. The document should provide a brief overview of the test process for each unit, a block diagram of the test set-up of each test, and an estimate on the expected coverage and test time. The document should also detail the system test processes to be used in the testing of the product, a block diagram of the test set-ups, and may even include an estimate of the 'Cost of Goods' (COG) to support. This document is a living, changing document that can eventually encompass all products. Additional detail is added to sections where open questions remain, regarding the details of how various functions are to be performed or when process flows have yet a definition.

Defining the Test Architecture is the next sequential step, the JCM Test Strategy contains our recommendations for an Architecture that can either be adopted in whole, or in part, to suit a Clients particular needs.

With the top-level vision realized we focus on resource and project planning all of the activities required to meet the end goal/objective. Although Microsoft Project is an ideal tool to identify and track all of the tasks/resources required for test implementation, we can also use an alternative GANT/Project Planner as requested. It is only after completing this stage that a complete cost assessment for the entire project can be realized.

The difference between a good manufacturing solution and a great one often lies in the back-end of the implementation, or step #7 from the table above. The OH cost of step #1 generally pays for itself in the first year of product use, as careful consideration to the back-end process was primary in the Solutions creation.

Together with JCM, a customer will have the capability to provide a MFG solution that is cost effective to implement, support and sustain while providing the data/information required for continuous process/product improvement.