S2 Stage 2 Flashcards
Project Planning & Concept Development
Stage 2 Project Planning and Development
the cross functional team collaborates to substantiate the market (customer) need and product value based on the functional requirements in order to complete a concept design and demonstrate a proof-of-concept.
The team is to assess and justify the required resource and capital investment and develop a project plan to meet the project objectives with reasonable certainty and within required timelines.
Initiate the Project & Review Program Goals and Objectives
S2.PM.01
During the Planning Stage, the project team defines the specific goals and objectives of the project.
Two aspects to this determination are defining the product and project scope.
Create Project Plan and Schedule
S2.PM.02
defines; activities, duration, dependencies, and milestones of the project
During the early efforts of the Planning Stage, the project team develops a project Work Breakdown Structure (WBS).
A Gantt chart should be prepared with team members using MS Project or an equivalent tool.
benefit of CPA is that it helps to identify the minimum length of time needed to complete a project.
Work Breakdown Structure
WBS
A WBS is a deliverable grouping of project activities that organize and define the scope of the project (work not in the WBS is outside the scope of the project)
Critical Path Analysis
CPA
formally identifies those tasks which must be completed on time for the whole project to be completed on time.
Create Project Budget & Expense Forecast
S2.PM.03
project team fully defines estimated expenses
These expenses could include, but are not limited to; staff hours, laboratory, computer support, travel, prototypes, and miscellaneous expenses. These estimated expenses become the budget for the Project team.
Perform Risk Analysis
S2.PM.04
Risk management includes the processes concerned with identifying, analyzing, and responding to project risk.
Risk Identification
determining which risks are likely to affect the project and documenting the characteristics of each
Risk Quantification
evaluating the risks and risk interactions to assess the range of possible project outcomes
Risk Response Development
defining enhancement steps for opportunities and responses to threats
Risk Response Control
responding to changes in risk over the course of the project.
These risks can be product or project related
Organize Project Team
S2.PM.05
Division Management appoints a project team
A cross-functional team generally consists of representatives from Engineering, Marketing, and Manufacturing. Depending on the size and complexity of the project, other team members may be included from organizations such as Application Engineering, the Customer, Purchasing, Quality Assurance, Plant Engineering, Plant Production, Accounting, or Vendors.
Hold Project Kick off & Review Meetings
S2.PM.06
the project manager or team leader calls a Project Kick-off Meeting to define organizational and technical interfaces between different groups that input into the design process.
The purpose of this meeting is to agree on the technical, cost, and schedule goals of the project and begin forming the specific plans for project execution.
Conduct a Lean/Complexity Review
S2.PM.07
Conduct a Lean review meeting to evaluate the complexity impact of the product or process to the business.
Use the Complexity Indicator Worksheet to help rank the complexity of the project.
Objective: understand, evaluate and approve the complexity impact to other division products, operations organizations and supply chain.
Func Areas Needed: Product Management (Platform Leader), Engineering, Procurement and Operations
Review History / Lessons Learned / Team Experience
S2.PM.08
The project team should review historical customer concerns and wants in order to assess the potential for recurrence during the design, manufacture, installation and use of the product
Develop Preliminary List of Special Product & Process Characteristics
S2.PM.09
Special product and process characteristics are identified by the customer in addition to those selected by the organization through knowledge of the product and process
tracked in the APQP process
Special Product Characteristics
- Product assumptions based on the analysis of customer needs and expectations
- Identification of reliability goals and requirements
- Identification of special process characteristics from the anticipated manufacturing processes
- Similar part FMEAs
Special Product Characteristics FLOW
hese Critical to Quality (CTQ) requirements need to flow down and be documented in the engineering drawings, DFMEA, Prototype Control Plan, Process Flow Chart, Process Failure Mode Effects Analysis (PFMEA), Production Control Plan and Plant Work Instructions.
Key Characteristics Classification LINKED
Voice of Customer -> Identification of Critical Characteristics -> Drawings -> Design FMEA -> Prototype Control Plan -> Process Flow Chart -> Process FMEA -> Production Control Plan -> Operator Instructions
Create Business Plan & Assess Strategic Fit
S2.MAR.01
The business plan and marketing strategy will set the framework for the project plan.
may place constraints (e.g., timing, cost, investment, product positioning, and research and development resources
becomes the financial success criteria that will later be used in Post Launch Reviews.
Update Product Specification
S2.MAR.02
Update the product specification
Conduct Competitive Product/Process Benchmarking
S2.MAR.03
Analyze real and potential competitive products that exist and benchmarked against our own current product offering if applicable
Perform Branding Recommendation
S2.MAR.04
Discussion of how our product will be branded and taken to market
Identify a Product Introduction & Obsolescence Plan
S2.MAR.05
Begin to plan how this product will be introduced and if it replaces an existing product, plan how that product may be phased out.
Identify Customer Contract Requirements
S2.MAR.06 VOC
At this point, identify what customer(s) are going to want in contracts. Supply provisions, quality requirements as well as terms and conditions are examples of what is to be analyzed.
Review Product Specifications & Develop Design Goals
S2.ENG.01 VOC
Requirements from the Product Specification and Market Studies are analyzed and an outline design specification developed.
Develop Detailed Design Specification
S2.ENG.01.1
- Hardware/Software specifications
- Any major innovations that must occur to enable this product
- Prioritized system/process requirements traced from features description – scalable options identified
- Manufacturing & Operations requirements
- Supply chain requirements
- Performance and Quality requirements. This includes Critical to Quality (CTQ) flow down characteristics and tolerances
- Environmental regulations product may be required to meet. (RoHS, REACH, etc.)
- Interface requirements (e.g. other products, systems/processes)
- Standards
- Aftermarket Strategy
Develop an Initial Performance Test Plan
S2.ENG.02
Project Schedule development project teams develop a test plan to include all product and customer testing required prior to project completion
Product Test Plan
- High risk elements
- Customer performance requirements
- Customer engineering standards
- Customer reliability standards
- Customer quality requirements
- Application testing at NMC Motor Technology Center
- Customer facility application/laboratory testing
- Industry product requirements
- Testing Agency approval specifications
- U.L. standards compliance verification
- Material evaluations
- Unproven component design evaluations
- Prototype validation
- Supplier and Vendor part evaluations
- Environmental requirements
- Unproven or new process testing
- Validation of NMC Test Procedures
- Validation of NMC Standard Engineering Instructions for Manufacturing (SEIMs)
- Validation of NMC Material Specifications
- CAE requirements (i.e., FEA, CFD, Mold Flow, Tolerance Analysis, etc.)
- Specification of third party testing.