Paul Nelson, Northrop Grumman, Partner to Achieve Your Mission · Abstract •Title:Paul Nelson,...
Transcript of Paul Nelson, Northrop Grumman, Partner to Achieve Your Mission · Abstract •Title:Paul Nelson,...
Abstract
• Title: Paul Nelson, Chief Technical Strategist, Northrop Grumman
• Bio: Paul leads technical strategy for Integrated Digital Product Development and Services (IDPDS) as chief technical strategist at Northrop Grumman. He is promoting the proper processes and tools to significantly reduce development time and costs while meeting all customer requirements. Paul has BS and MS degrees in mechanical engineering. He is INCOSE CSEP certified, holds a graduate certificate in Systems Engineering, and is CM2-Professional certified.
• Presentation Title: Partner to Achieve Your Mission
• Abstract: Complex missions require partnerships to reduce risk and help ensure success. Delivering robust Enterprise-level Integrated Process Excellence (IpX) is a complex mission. Organizations typically partner together to increase the likelihood of each achieving their mission and to amplify their reach. Partnering strategies as well as recent Northrop Grumman Innovation System successes enabled by partnering shall be shared.
1
Partner to Achieve Your Mission
IpX ConX18, Chicago
Paul NelsonChief Technical Strategist, iDPDS
Outline: Why are partners required?
What makes a good partner?
When do partnerships succeed?
Partnering Examples
Conclusions and Recommendations
3Partnership starts with a foundation of Trust and Culture
Why Are Partners Required?
Complexity Drives Partnerships
What Makes a Good Partner? Physics: Source and Sink
What Makes a Good Partner?Games: Fixed-Pie and Pie-Building
• Distributive negotiations – divide the pie– There is only so much to go around
– Competitive– Win / lose
– Adversarial– Claiming value
• Integrative negotiations – enlarge the pie– Everybody wins something (usually)
– Cooperative– Win / win
– Problem-solving– Creating value
• What type of pie do you deal in?
When Do Partnerships Succeed?
Treat Partnerships as Equals
Partners are required to Deliver the Digital Thread
PhysicalEngineering Manufacturing
MCAD
ECAD
Software
Structure
MBOM
BOP
As-tested
As-built
As-maintained
Requirements
Customer
Regulatory
Design
Build
Program Plan and Execution
SOW
Work Pkg.
Schedule
Cost
Systems Engineering
Functions
Logical
Architecture
Verification
Program Management, EVMSChange, Issue, and Configuration Management
Integrated Reliability, System Safety, Maintainability, and Risk ManagementTraceability and Accountability
Behavioral Simulation, Design Trade off, Test, and ValidationEnterprise Reuse and Knowledge Management
Material and Processing
Appreciate Partnerships with the Extended Enterprise
When Do Partnerships Succeed?
Diversity Drives Creativity
Internal PartnersVertical Integration Within Flight Systems Group
Internal PartnersVertical Integration Within Space Systems Group
• 12
When Do Partnerships Succeed?
Respect fosters collaboration, communication, and innovation
IpX Partnering Examples
• IpX Training has provided a common foundation/language for NGIS alignment
• IpX / CM2 holistically integrates process, tools, people, methods with priority on foundational elements to achieve integrated process excellence
• Aim high (e.g. 100% data integrity)
• Global Congress value (e.g. Industry 4.0 and PLM Certification subcommittees)
• IpX listens and responds; a strong partner
14
Situation 1 Situation 2 Situation 3 Situation 4
Datasets & Requirements
Clear, Conciseand Valid
Clear, Conciseand Valid
Subject To Interpretation
Subject to Interpretation
Verification Measurements
Easily Applied and Concise
Subject to Interpretation
Easily Applied and Concise
Subject to Interpretation
Results Consistent Conformance Intermittent Errors Intermittent Errors
Work Harder to Maintain Status
Quo (Chaos)
Reason for Changes
Continual Improvement Corrective Action
Conclusions and Recommendations
For the Harvest to Come
A Seed Must be Planted
Conclusions and Recommendations
17