Académique Documents
Professionnel Documents
Culture Documents
PURPOSE
<<policy>>The purpose of this instruction is to state the department policy that all engineering programs,
contractural and strategic, without distinction, be designed in accordance with the Engineering
Department Product Design Plan.
REFERENCE
None.
BACKGROUND
<<process and procedure/guideline and templates>>The Product Design Plan (PDP) is a systematic
process for program identification, planning, execution, and monitoring, to assure that the requirements
and goals of the program are met through effective utilization of the department's skill and resources.
This process features the use of checkpoints, all or some of which are included in all engineering
programs. It is intended that the engineer's understanding and implementation of the process will result in
a systematic design approach. It is further intended that users will continually review and improve the
PDP.
<<need mechanism for review/feedback/improvement to be stated or referred to>>
<<combo of policy and guideline>>PROCEDURE
1.
<<policy>>The PDP shall be incorporated into all new engineering programs and design related
activities. The extent of incorporation into existing programs shall be determined by the
appropriate functional Engineering Manager, Lead Engineer and Program Manager (for customer
contracts).
2.
<<policy>>The PDP will provide for the implementation of the design process through the use of
a system of checkpoints to assure that the process is on target through all phases of the product life
cycle, including contract closure.
3.
<<process--tailoring guidelines>>The checkpoints included in the PDP are divided into two
groups: required and conditionally required. Required checkpoints must be included in the
program plan for every new program. Conditionally required checkpoints may not be necessary
Process Primer
Example/Exercise
Page 1 of 29
for certain programs. However, if a conditionally required checkpoint is not included in a program
plan, a justification of that checkpoint's exclusion must be given in the checklist that is part of the
PDP.
4.
<<fact>>Copies of the PDP are maintained in the Technical Resource Library and are held by all
Lead Engineers and functional Engineering Managers.
ATTACHMENT
ATTACHMENT A: Process Flow Chart(see hard copy in Library).
Process Primer
Example/Exercise
Page 2 of 29
ENGINEERING DEPARTMENT
PRODUCT DESIGN PLAN
Process Primer
Example/Exercise
Page 3 of 29
Process Primer
Example/Exercise
Page 4 of 29
POLICY
<<policy>>It is the Engineering Department policy that all engineering programs, contractual and
strategic, without distinction, be done in accordance with this plan. It is the responsibility of the
appropriate functional Engineering Manager and the Lead Engineer to assure that this plan is followed,
and that the applicable checkpoints are included in their program plans. It is also their responsibility to
assure that crossfunctional participation is facilitated for all aspects of the product design and that
concurrence with the program plan is obtained from the Program Manager through the Lead Engineer.
<process-tailoring guidelines>The checkpoints included in the plan are divided into two groups: required
and conditionally required. Required checkpoints must be included in the program plan for every new
program. Conditionally required checkpoints may not be necessary for certain programs. However, if a
conditionally required checkpoint is not included in a program plan, a justification of that checkpoints's
exclusion must be given in the checklist that is part of the PDP.
Process Primer
Example/Exercise
Page 5 of 29
TABLE OF CONTENTS
section
1.
INTRODUCTION
2.
MISSION STATEMENT
3.
4.
5.
THE PROCESS
CHECKPOINTS
GUIDELINES
6.
5.1
5.2
5.3
7.
8.
6
6.1
6.2
6.3
6.4
6.5
6.6
6.7
6.8
6.9
7
7.1
7.2
7.3
7.4
7.5
7.6
8
8.1
Process Primer
Example/Exercise
Page 6 of 29
11.
8.2
8.3
8.4
8.5
8.6
8.7
8.8
8.9
8.10
8.11
CHECKPOINTS: PROTOTYPE/
MANUFACTURE PHASE (REQUIRED)
9.1
9.2
9.3
9.4
9.5
9.6
9.7
9.8
9.9
9.10
10
10.1
10.2
10.3
10.4
10.5
10.6
11
Page 7 of 29
11.1
11.2
SYSTEM TEST
PRODUCT CAPABILITIES
PROTOTYPE FIELD TESTS
12.
11.3
11.4
11.5
13.
12.1
12.2
14.
12
13
13.1
13.2
13.3
Process Primer
Example/Exercise
Page 8 of 29
LIST OF CHECKLISTS
Process Primer
Example/Exercise
Page 9 of 29
1. INTRODUCTION
It is the goal of The Company to achieve industry leadership and become the preferred supplier for
solutions and services worldwide. In order to attain that position, the objectives become:
Customer Satisfaction
The Product Design Plan will aid in achieving this goal by providing a framework that:
The Product Design Plan (PDP) is a systematic process for program identification, planning, execution,
and monitoring, to assure that the requirements and goals of the program are met through effective
utilization of The Company's and other supporting skills and resources. This process features the use of
checkpoints, all or some of which should be included in all engineering programs. It is intended that the
engineer's understanding and implementation of the process will result in a systematic design approach.
It is further intended that users will continually review and improve the PDP. This will assure that
priorities are set which will be consistent with Company policy, and will aid in achieving industry
leadership.
The Product Design Plan checkpoints are integrated into four distinct phases of the design process: the
Proposal Phase, the Design Phase, the Prototype/Manufacture Phase, and the Commission Phase. In
addition, a final checkpoint for program closure is used within the Commission Phase to emphasize the
need for Engineering support throughout the life of the program. To facilitate implementation of the plan,
guidelines for each checkpoint have been developed. It is expected that systematic application of this
plan, along with sensible evolution of the guidelines, will result in highly productive design functions
which will converge on leadership in the transit industry.
Process Primer
Example/Exercise
Page 10 of 29
2.
MISSION STATEMENT
The Product Design Plan supports the Engineering Department mission statement, which is:
Global Solutions Development Engineering provides the transformation of information and creative
knowledge by motivated associates into products, processes and sevices that result in customer
satisfaction, competitive advantage and company value.
Process Primer
Example/Exercise
Page 11 of 29
3.
<<policy>>This Product Design Plan (PDP) shall be incorporated into all new engineering
programs and design related activities. The extent of incorporation into existing programs shall be
determined by the appropriate functional Engineering Manager, Lead Engineer, and Program
Manager.
B.
<<policy>>The PDP process flow described in Section 5 shall be the basis for planning each
program.
C.
<<policy>>The PDP will provide for the implementation of a concurrent design process through the
use of a system of checkpoints to assure that the process is on target through all phases of the
product life cycle, including contract closure.
D.
<<policy>>The list of applicable checkpoints for each program phase shall be defined jointly by the
appropriate functional Engineering Manager, Lead Engineer and Program Manager.
E.
<<policy>>Each Resultant Program Phase checklist will contain a basic set of checkpoints which
are required by policy, and, in addition, each checklist will contain other design practice"
checkpoints for consideration. Exclusion of any of these latter checkpoints must be justified.
Applying other checkpoints is at the discretion of the Lead Engineer and the appropriate functional
Engineering Manager.
F.
<<policy>>The guidelines and referenced procedures given in Section 6 through 12 are to be used
to implement the checkpoint review.
G.
<<policy>>Assigned Engineering department staff managers must approve the original PDP and
any revisions requiring the deletion or alteration of check points.
Process Primer
Example/Exercise
Page 12 of 29
4.
Customer requirements
B.
C.
Complexity of design
D.
E.
F.
The Product Design Plan is to be applied to both customer order programs and internal strategic programs
without distinction.
The Lead Engineer and the appropriate functional Engineering Manager must jointly decide on depth of
applicability for each major system element/component consistent with the committed budgetary
estimates.
Process Primer
Example/Exercise
Page 13 of 29
5.
B.
C.
D.
The operation phase of the system life cycle is not treated separately in the Product Design Plan. Field
operations reliability and performance data are used concurrently throughout the four phases of the
process.
Utilizing concepts of concurrent engineering, each phase embodies its own process flow. The sequence
of engineering functions at the top level are shown in bold print. A set of related activities is shown
within each functional block. These activities, when combined with the guidelines given in the following
related section constitute the baseline product design plan for each phase.
5.2 : CHECKPOINTS
<<policytailoring guidance>>In the flow chart, not all activities are necessarily required. This would
be the case with repeat business, for example. Conversely, some activities not shown might be required
by customer specification. For this reason, each plan is made unique by the selection of checkpoints for
each phase by the Lead Engineer and the functional managers. The checklists of check points to be
completed for each phase are given in tables 5-1 to 5-4 of this plan. Each checklist identifies mandatory
check points, recommended check points, and space for newly identified check points.
The purpose of mandatory checkpoints is to assure that a core design process is implemented for the
system (or element) being considered. Mandatory check points require that the tasks be done either on
the current program or use the results from another program, provided the results are applicable and
included in the current program via design review.
Where the core design process for a system (or element) differs from that shown in the checklist, such as
in software design, appropriate modifications should be made.
Recommended checkpoints are optional, but exclusion must be justified as above or traceability to similar
programs/applications showing acceptable risk must be provided.
All checkpoints selected including new checkpoints must be jointly approved by the lead engineer, the
functional manager and the program manager.
The check points generally follow the process flow, and each check point is identified and traceable to a
guideline.
Process Primer
Example/Exercise
Page 14 of 29
5.3 :GUIDELINES
Guidelines are provided for each check point. They are not procedures, but do contain good practice
recommendations, pointers to procedures and other supporting materials. As the plan is used, refinement
of guidelines is a certainty.
Process Primer
Example/Exercise
Page 15 of 29
Receive RFQ
Proposal Leader
Specification Review
Program Manager
Definition of Deviations/Risks
Operations Representatives
Marketing Manager(s)
Customer Needs
Analysis/Coordination
Company Requirements
Definition
Specification Review Meeting
Alternate Concept
Evaluation
Manufacturability
Other Selected CE
Disciplines
Comment/Exception Review
Resolution
System Performance
Analysis (Initial)
Life Cycle Cost Analysis
(Initial)
Maintenance Concept
Establish Material and Labor
Cost Targets
Trade Studies/Risk Analysis
Requirements Summary
Element Task Descriptions
Manpower Estimates
Program Schedules
Outside Pricing Support
Cognizant Engineer Review
Completed QEP Sign-Off
Evaluate Cost Versus CAC
for Similar Contracts
Proposal Write-Ups/Figures
Proposal Format Development
Support
Interface Requirements
Functional Requirements
Environmental Requirements
Manufacturability
RMSH Requirements
Design-to-Cost
Identify Milestones
Evaluate Element Tasks and
Manpower Loading Effects
Evaluate Design/Test Related
WBS Impact
Process Primer
Example/Exercise
Page 16 of 29
Review of Architecture
Review of Required
Checkpoints
Resolution of Comments/
Exception/Risks
Costs/Schedule Review
Enter order
Program Manager
Lead Engineer
Functional Manager
Cognizant Engineer(s)
Functional Engineer(s)
System Engineer(s)
Manufacturing Engineer
Field Engineer
Marketing
Purchasing
Drafter
Transition to Program
Information Package
Transition Reviews
Customer Interface
Meeting
Task Assignment
Update Task Description
Information for O&M Manuals
Initiate Task Folders
Finalize System
Requirements
Customer Needs Analysis
CE Gated Checkpoints
Project Schedule Requirements
Standardization Objectives
Analytical Models
Bread Boards
Tolerance/Margin Studies
System Performance
Analysis
Testability Analysis
RMSH Studies
Safety Studies
Logistic Support
Analyses (LSA)
Renewal Parts Analyses
Software Structure
System Details
Software Coding
Interface Design
Testability Design
Long Lead Disposition
Design-to-Cost
Development Prototype Tests
Process Primer
Example/Exercise
Page 17 of 29
Manufacturability
Analysis (DFMA)
Design-to-Cost
Standard Design
Applicability
Simulation
Models/Testing
Materials Testing
Vendor Tests
Preliminary
Development Tests
Informal Design Reviews
Trade Studies
Customer Participation
Final Analysis/Test Data
Closure of PDR Items
Review Completed Drawings/Test Specifications
Reconcile PDR Versus FDR Configuration
Manufacturing Process Review
Complete
Manufacturing
Documentation
Package
Fabricate Production
Prototype
Test/Inspect
(FA)
Signed Off
Drawings,
Test Specifications
Software
Documentation
O&M Manual
Information
Manufacturing
Process
Conduct Production
Prototype Review
Manufacturability
Verification
Environment Tests
Maintainability Verification
Tests
Factory Tests
System Tests
Field Tests
Product Capability
Documentation
Design Book Update
Conduct FAI
Process Primer
Example/Exercise
Page 18 of 29
Produce Deliverables
Produce Deliverables
Ship/Instal
l
Perform Commission
Tests
Perform
Demonstration Tests
Company Tests
Reliability Tests
Maintainability
Verification Tests
Availability
Verification Tests
Close-Out Review
Process Primer
Example/Exercise
Page 19 of 29
Program Plan
Status (In/Out)
In
In
System Architecture
In
Design Objectives/Specification
Requirements
In
In
In
In
Risk Analysis/Management
In
Manufacturability
In
Process Primer
Example/Exercise
Page 20 of 29
Justification
Program Plan
Status (In/Out)
In
Design Objectives/Requirements
In
Preliminary Design/Analysis/Test
In
In
Detail Design/Analysis/Test
In
In
Developmental Testing
In
In
In
Design To Cost
In
Manufacturability Analysis
In
Reliability/Maintainability/Human
Factors Studies
Testability Analysis
Tolerance/Margin Studies
Renewal Parts Analysis
Logistic Support Analysis
Long Lead Items
Trade Studies
Customer Design Review
O&M Information
Process Primer
Example/Exercise
Page 21 of 29
Justification
Program Plan
Status (In/Out)
Production Prototype
Documentation Package
In
In
Design/Verification Tests
In
In
Production Release
In
Factory Tests
In
Process Primer
Example/Exercise
Page 22 of 29
Justification
Program Plan
Status (In/Out)
Commission Tests
In
In
Demonstration Tests
Field Feedback/Reliability Data
Design Information File
Process Primer
Example/Exercise
Page 23 of 29
Justification
6.
Purpose
Guidelines
Documentation
References
Process Primer
Example/Exercise
Page 24 of 29
Purpose
Guidelines
Work with the proposal team to resolve any issues arising from the
specification review and evaluate risks prior to final selection.
Complete a preliminary performance and reliability history review.
Utilize Cognizant Engineers and Logistics Engineers to retrieve, evaluate
and maintain a performance history data base.
In cooperation with marketing and the cognizant design engineers,
Applications Engineering should define other concepts which potentially
meet requirements, particularly where standard components might not be
applicable.
Perform initial Life Cycle Cost Analyses to assess the design to cost"
potential for each alternate (perform acquisition cost analyses at a
minimum).
Perform initial manufacturability analysis.
Complete initial trade studies based on at least the costs, performance,
schedule, reliability, safety and operational availability.
Achieve general agreement with Marketing and Program Management
prior to further development of the overall Quotation Estimate Process
(QEP) for the selected concept, via conceptual review meetings.
Documentation
References
Process Primer
Example/Exercise
Page 25 of 29
Purpose
Guidelines
Documentation
Publish the work breakdown structure. Record and retain all input,
output and other interface data for use in developing design
requirements.
References
Process Primer
Example/Exercise
Page 26 of 29
The functional and design criteria established for each component in the
proposal phase during the creation of the system architecture.
Purpose
Guidelines
Process Primer
Example/Exercise
Page 27 of 29
Product Capabilities
Commission Test
The Use of Standard Components/Subsystems/Systems
Complete Table 6-1 and integrate with estimates during proposal phase.
Update with any changes developed during negotiations and use as the
baseline for task folders at the start of the design phase.
The Lead Engineer is responsible for ensuring that this information is
documented.
References
Process Primer
Example/Exercise
Page 28 of 29
Parameter
Special
Requirements/Comments
NOTES:
A.
For all major components, list all requirements, references and parameters.
B.
C.
For lower tier elements, cite major component WBS and record only any other
additional requirements.
D.
This list merely identifies the requirements and the sources. The design must
ultimately satisfy the customer contract specifications.
Process Primer
Example/Exercise
Page 29 of 29