systems engineering in nuclear energy sector

®

IBM Software Group

© 2009 IBM CorporationInnovation for a smarter planet

Rebuilding Babel: The language of systems engineering in Nuclear licensing

Paul FechtelkotterGlobal Executive – Energy Sector and Complex [email protected]

mailto:[email protected]

http://www.ibm.com/software/rational

http://www.ibm.com/software/rational

IBM Software Group | Rational software

2Innovation for a smarter planet

SMR Projects must balance market viability with safety and security

Safety

Design and Plant

Market

Safety & security

Regulations

Design Certification

Licensing

Custom

er exp

ecta

tions

Afford

ability

Predicta

bility



Meanwhile, global headlines continue to influence and disrupt the market

CHANGE IS THE ONLY CONSTANT



The Nuclear Energy Sector can learn from other highly complex industries

Effectively leveraging systems engineering concepts is critical

Source: Final Report: NASA Study on Flight Software Complexity, Commissioned by the NASA Office of Chief Engineer, Technical Excellence Program, Adam West, Program Manager (2009)



Success takes a village … collaboration is critical

Owner

Operator

Major

Equipment &

Systems

Suppliers

EPCM

–

ISV’s and

Systems

Integrators

Regulators

SME’sAssociations

And

Academics

Clear expectations and requirements

Complete set of expectations and requirements

Synchronized expectations and requirements

Validate and Verify expectations and requirements



SUCCESS is not always what you see



There is risk in what you do not knowToday’s predominant approach is not up to the challenge

1. If a system requirement changes, how do you know which subsystem requirements are also impacted?

2. How do you assess development progress?

3. How do you identify and mitigate conflicts between requirements?

4. If a test fails, how do you know which requirements it relates to?

5. Do you know how often you update requirements? What is the cost of change?

6. How do you ensure you satisfied all regulations or company policies?

Insert graphic here

Ask yourself:

Stakeholder

Comments

Update

documentReview and Approvals

Change

Tracking

Change

Tracking

Update document

new version

Gap

Assessments

Audits /

Reports

External

Documents

Informal

reviews

Formal

reviews

HIDDEN RISK



The traditional approach creates risk

Best practices

enabled by technology

Standard practice

today Missing things Defects. Poor quality.

Source: The Economics of Software Quality [Hardcover] Capers Jones, OlivierBonsignour, Addison-Wesley Professional; 1 edition (August 3, 2011)



Systems Engineering helps solve these challenges What is Systems Engineering?

An interdisciplinary field of engineering that focuses on how to design and manage complex engineering projects over their life cycles.

It considers all aspects of a project or systems and ensures they are integrated into a whole.

Both an approach and a discipline in engineering

Very mature in industries such as aerospace and defense

- The Apollo program is a classic example



Source: Technical Board INCOSEVersion 2a, June 2004

Systems engineering techniques yield significant improvements in cost and schedule

More Systems Engineering concepts applied More Systems Engineering concepts applied

Cost Schedule

Re

du

ced

c ost o

verru

n

Re

du

ced

s che

du

le o

v erru

n



The Essential Building Blocks of A Collaborative Engineering Platform

QUALITY MANAGEMENTAchieve “quality by design” with integrated

automated testing and verification processes.

COLLABORATION, PLANNING & CHANGE MANAGEMENTCollaborate across geographically diverse engineering disciplines and

development teams, both onshore and offshore.

REQUIREMENTS MANAGEMENTManage all business & system requirements (Safety,

Environmental, Regulation, Permits, Compliance) with full traceability across the lifecycle

PERFORMANCE REPORTING and ANALYSISAutomated, transparent collection of role-based dashboards to drive Supplier

performance reporting and analysis across the Supply Chain

PORTFOLIO STRATEGY and MANAGEMENTScenarios/Options prioritization, Investment Analysis, Financial Modeling,

Complex Analysis

PROCESS METHODS AND BEST PRACTICESCreate and maintain libraries of structured process assets to easily reuse process

methods and tools.



Similarities between NASA's Curiosity rover and Nuclear projects

Program Dynamics Big, complex projects

Harsh environments

Safety a “must have”

Production and productivity

Team Collaboration Several engineering disciplines

World wide scope

Workforce Life long industry careers

Retiring workforce



Level 1 – 4 drove a total of

16,000 Requirements

11,000 links to requirements and artifacts

Need for strong Verification & Validation approach to tie requirements to support extreme testing

NASA's Curiosity rover….. The Requirements Challenge

Level 1 - Program or science requirements developed with NASA

Level 1 - Program or science requirements developed with NASA

Level 2 - Project system requirements

Level 2 - Project system requirements

Level 3 - System-level requirements. (e.g. flight system, ground system, launch vehicle)

Level 3 - System-level requirements. (e.g. flight system, ground system, launch vehicle)

Level 4 - Subsystem of the Flight System. (e.g. Instrument payload)Level 4 - Subsystem of the Flight System. (e.g. Instrument payload)

Level 5 - Requirements for subassemblies, hardware

components and software modules

Level 5 - Requirements for subassemblies, hardware

components and software modules

Q: How does the team effectively manage the sheer number of requirements and their inter-dependencies?

A: By implementing requirements management practices enabled by technology

Large number of additional requirements and linkages



What did NASA’s Curiosity rover gain with Requirements Management?

Productivity and Speed• Fewer duplication of efforts – assessments,

research studies, etc. Money saved

• Time saved – greater transparency, sharing of resources, rework, audits, reporting

Visibility and knowledge capture• Better tracking of requirements completion

• Metrics – requirements volatility

• Improved Safety

• History and audit controls - know who changed what and when and even why.

14

Increased likelihood of mission’s success• More complete and understandable requirements• Higher quality. Improved testing through linkage to test plans and case



Success is a Journey

Owner

Operator

Major

Equipment &

Systems

Suppliers

EPCM

–

ISV’s and

Systems

Integrators

Regulators

SME’sAssociations

AndAcademics

MISSION SUCCESS!


16Innovation for a smarter planet16

For More Information:

Ben Amaba: [email protected]

Paul Fechtelkotter: [email protected]

Tammy Kulesa: [email protected],.com