Chip lifecycle / Industrial lifecycle / Concept & Application Scope

Concept & Application Scope

Defining the industrial or energy application the product serves, such as factory automation, process control, machinery, power grid and substation equipment, inverters, drives or energy storage, with its operating environment, the markets and certification schemes it must enter, the safety and security functions it may carry, and the supply life customers expect, so the overall scope of the safety lifecycle and the compliance plan are fixed before design starts.

Where this stage sits

This stage with its neighbours. Each row is a discipline active here, shaded by how mature its work is by the end of each stage.

Stage

^A01 Concept & Application ScopeYou are here

^A02 Hazard, Risk & Threat Analysis

^A03 Safety, Security & Compliance Requirements

Product, compliance and supply milestones

CAConcept approval SAScope and compliance plan agreed

Engineering and safety milestones

TFTR1TR1: Technology feasibility RAHazard and threat analysis approved RBRequirements baselined

Product and program management^A

0.0

0.3

0.5

Functional safety management^A

0.0

0.3

0.5

Product security^A

0.0

0.3^A

0.5

Product compliance and certification^A

0.0

0.3

0.5^D

System and safety architecture^A

Board and power hardware design^A

0.0

0.3

Firmware and software^D

0.0

Verification and validation^A

0.0

0.3

Long-life supply and obsolescence^A

0.0

0.3

Key0.0Planned0.3Early draft0.5Draft0.8Feature complete1.0CompleteFreezeFrozenFaded block: still at the step shown before it, Held below Complete or Maintained under change control once complete or frozenFreeze or sign-off pointMilestone for one item; the rest of the work carries onMilestone gateTRTechnical readiness review (TR): a gate that checks the technology is ready before the next commitment.You are here: Concept & Application ScopeAI impactDisruption (red)Augmentation (blue)Opportunity (green)How AI is changing the workWhat the steps mean What the codes mean

Show this chart as a list

Stages

Concept & Application Scope (this stage)^A
Hazard, Risk & Threat Analysis^A
Safety, Security & Compliance Requirements^A

Product, compliance and supply milestones

Engineering and safety milestones

TR1: Technology feasibility (TF) (technical readiness review TR1)
Hazard and threat analysis approved (RA)
Requirements baselined (RB)

Disciplines

Product and program management^A
- Concept & Application Scope: maturity 0.0, Planned. Business case approved, and the application profile, program plan and supply life agreed with assessment, certification and long supply costed in.
- Hazard, Risk & Threat Analysis: maturity 0.3, Early draft. Program running against the agreed integrity and security targets, with their effect on cost and schedule reviewed with lead customers.
- Safety, Security & Compliance Requirements: maturity 0.5, Draft. Product requirements and plan in force; customer and program reviews track the open safety, security and certification questions, and the datasheet is outlined.
Functional safety management^A
- Concept & Application Scope: maturity 0.0, Planned. Functional safety management plan approved, with the roles, competence and independence the integrity level requires.; Functional safety management plan baselined (milestone for one item)
- Hazard, Risk & Threat Analysis: maturity 0.3, Early draft. Hazard and risk analysis approved and the target integrity level of each safety function agreed with the customer or system owner.
- Safety, Security & Compliance Requirements: maturity 0.5, Draft. Safety requirements specification approved; confirmation reviews of the architecture and the design under way.
Product security^A
- Concept & Application Scope: maturity 0.0, Planned. Security management plan approved: the secure development process, its roles and the standard it follows.; Security management plan baselined (milestone for one item)
- Hazard, Risk & Threat Analysis: maturity 0.3, Early draft. Threat and risk assessment approved, with zones, conduits and target security levels agreed.^A
- Safety, Security & Compliance Requirements: maturity 0.5, Draft. Security requirements specification approved, and the security architecture drawn up and approved against it.
Product compliance and certification^A
- Concept & Application Scope: maturity 0.0, Planned. Compliance and certification plan approved: standards, schemes, markets and bodies, with the export classification recorded.
- Hazard, Risk & Threat Analysis: maturity 0.3, Early draft. Each target market's rules and the bodies to engage listed, with first contacts made.
- Safety, Security & Compliance Requirements: maturity 0.5, Draft. Product compliance requirements approved, each with the evidence it needs, and the design reviewed against them.^D
System and safety architecture^A
- Concept & Application Scope: maturity 0.0, Planned. Candidate architectures, and the component, process and isolation technology they need, assessed at the technology feasibility review.
- Hazard, Risk & Threat Analysis: maturity 0.3, Early draft. Product requirements outlined from the hazard and threat analysis, and architecture options for the safety functions sketched.
- Safety, Security & Compliance Requirements: maturity 0.5, Draft. Product requirements specification baselined and traced to the safety, security and compliance requirements; architecture and partitioning drafted.
Safety analysis^A
- Hazard, Risk & Threat Analysis: maturity 0.0, Planned. Analysis methods and failure rate sources chosen, and the hazard analysis supported with failure modes of the candidate architecture.
- Safety, Security & Compliance Requirements: maturity 0.3, Early draft. Safety concept outlined from the safety requirements: the diagnostics and fault tolerance each safety function needs.
Chip and IP design^A
- Hazard, Risk & Threat Analysis: maturity 0.0, Planned. Chip lead named, and the chips to reuse or develop checked against the hazards and target integrity levels, with the effort estimated; no safety mechanisms outlined yet.
- Safety, Security & Compliance Requirements: maturity 0.3, Early draft. Chip functions, diagnostics, monitors and safety mechanisms outlined from the safety requirements.
Board and power hardware design^A
- Hazard, Risk & Threat Analysis: maturity 0.0, Planned. Hardware lead named, and the reuse of boards, power stages and approved components estimated for the application profile; no power or isolation needs outlined yet.
- Safety, Security & Compliance Requirements: maturity 0.3, Early draft. Power, isolation and insulation needs outlined from the hazard analysis and the compliance requirements.
Firmware and software^D
- Safety, Security & Compliance Requirements: maturity 0.0, Planned. Software safety and security needs scoped from the requirements, with the software plan, coding standard and tools chosen.
Verification and validation^A
- Hazard, Risk & Threat Analysis: maturity 0.0, Planned. Verification lead named, and the verification, fault insertion and independence effort the target integrity levels need estimated; no strategy yet.
- Safety, Security & Compliance Requirements: maturity 0.3, Early draft. Verification strategy outlined with the requirements: a method for every requirement and the independence each needs.
Long-life supply and obsolescence^A
- Concept & Application Scope: maturity 0.0, Planned. Supply life plan agreed with the business: the support period and the long-life needs of the product.
- Hazard, Risk & Threat Analysis: maturity 0.0, Planned. Supply life plan agreed with the business: the support period and the long-life needs of the product.
- Safety, Security & Compliance Requirements: maturity 0.3, Early draft. Long-life component and supplier strategy outlined for the architecture.

Register or sign in to read on

The full lifecycle detail, with its charts, flows, tables and every section, is for registered members. Registration is free and takes a minute. You come back to this page afterwards.