VDA_6.3_EN_Yellow_Volume_22-05-16.pdf - 第57页

55 P3.2* Has the feasibility been comprehensively evaluated accordi ng to the product and process requirements? • Variant management, flash con- cepts P3.3 Are the activities for produ ct and process development planned …

P3.2* Has the feasibility been comprehensively evaluated according to the

product and process requirements?

Minimum requirements relevant for assess-

ment

Examples for implementation

An interdisciplinary procedure for evaluating

feasibility (including potential production loca-

tions) must be used.

All determined product/process-specific require-

ments (technology, function, quality, logistics,

software, etc.) must be checked for feasibility.

Material and personnel resources must be con-

sidered in the feasibility study.

The results of the feasibility study must be

available before tendering.

The feasibility of critical purchased parts must

be ensured.

If customer requirements cannot be fulfilled, the

customer must be notified or non-conformities

approved by the customer prior to the contract

being awarded.

A flash concept is available for programming at

the plant and updates in the field (if required).

Product/process development

• Customer requirements and

standards

• Schedules, time frame

• Regulations, standards, legisla-

tion, environmental impact

• Requirements from product liabil-

ity

• Traceability concept

• Buildings, premises

• CAM, CAQ

• Product/process innovation

• Interdisciplinary feasibility analy-

sis (for example, sales, develop-

ment, purchasing, production

planning, production, QM plan-

ning, logistics)

Product development

• Laboratory/test equipment

• Parallel software development /

prototyping

Process development

• Capacity monitoring

• Availability of primary materials

• Manufacturing options, manufac-

turing locations

• Equipment, tools, production/in-

spection equipment, auxiliary

materials, laboratory facilities,

means of transport, containers,

storage

P3.2* Has the feasibility been comprehensively evaluated according to the

product and process requirements?

• Variant management, flash con-

cepts

P3.3 Are the activities for product and process development planned in

detail?

Minimum requirements relevant for assessment

Examples for implementation

When planning the product and process develop-

ment, the level of detail depends on the component,

software and complexity of the process.

In the development phase, suitable risk mitigation

measures must be used for product and process

development assurance, so that the product meets

the required operational conditions when goes into

series production (function, reliability, safety).

In case of product and process innovations, there is

a fallback concept.

Risk analyses are part of the planning.

The inspection planning concept includes the re-

quirements regarding series production, product au-

dits and requalification.

The schedules contain all information regarding

product and process development (including dead-

lines and duration, milestones according to the

overall project plan, performance testing, PPA date,

software standards…).

The methods and evidence for development re-

lease meet the customer requirements and clarifi-

cation must be sought with the customer if non-con-

formities occur.

The software engineering process has been speci-

fied and meets the customer’s requirements.

The software development progress must also be

taken into consideration in the planning, such that

the required software functions are tested and

available at the required point in time.

Product/process development

• Overall project plan including

all deadlines

• Customer requirements

• Customer schedule

• Lead times

• Risk mitigation measures (in-

cluding backup strategy and

cybersecurity)

• (QFD, FMEA, HARA etc.)

• Prototype/pre-launch plan-

ning

• Regular status checks on the

progress of the development

(reviews)

• Project plans for investment

items (facilities and equip-

ment)

• Logistics planning for all

phases of product and pro-

cess development, including

packaging

• Spare parts concept

Product development

• Reliability testing, functional

testing, trial plan

P3.3 Are the activities for product and process development planned in

detail?

• Deadlines for development

phase samples

• Requirement analysis

• Architecture design

• Implementation

• Test

• Artifacts of agile project man-

agement (product backlog,

sprint backlog, increment,

definition of ready, definition

of done, sprint planning,

DevOps)

• Release planning

Process development

• Tool deadlines (parts from

production tools),

• Inspection planning, inspec-

tion equipment planning,

maintenance planning in-

cluding spare parts manage-

ment