United States Air Force: USAF Product Lifecycle Management (PLM) for Integrating Program Requirements through an Asset’s Lifecycle Larry Uchmanowicz Siemens Government Technologies
Problem Statement • USAF needs to own and manage the Technical Baseline for new and ongoing Weapon System Acquisitions • To accomplish this, the Air Force needs to establish Configuration Management (CM) of program data with links to requirements, legacy product data, and new design and build data to support cost tradeoffs, impact analysis and trade studies early in acquisition
Digital Thread for the Asset Life Cycle Engineering & Manufacturing Material Solution Analysis A Technology Development B C Production & Deployment Operations & Support Development • ID Key R&M Cost Drivers • Failure Definition/Scoring Criteria • Reliability Allocations • Feasibility Analysis Tail MDS RAM Requirements LCSP LCSP AOA RAM-C RAM-C RAM-C Rationale Rationale Rationale • Operational Mode Summary & Mission Profile CDD CPD • Failure Definition & Scoring Criteria RAM-C Rationale • Requirements • Logical Models • Analytics • Reporting • Documents • CDRLs • Parts/systems Teamcenter • Supporting Technical Data Acquire Technical Rather than here… Baseline here…
Technology Deployment • In October 2016, the US Air Force, NCMS, and Siemens Government Technologies (Siemens) entered into a collaborative agreement to perform work for the Ground Based Strategic Deterrent (GBSD) Program, located at Hill AFB, UT and managed by NCMS. • Value Proposition – Teamcenter provides a single view of program information from “ Requirements to Retirement” – Early acquisition information in a single location leveraged for later acquisition stages (e.g., AOA, LCSP, RAM-C data) – Drive Technology Dev, Manufacturing/Development, and sustainment phases through a single source of program engineering data (e.g., models, supporting documentation, requirements)
Overall Benefits Process Improvements Business Initiatives • • Integrate design data management Provide a single Integrated Intellectual Property (IP) within a PLM Solution. Backbone. • Incorporate authors, Engineer, and • Introduce consistency and Approvers in product development improve accuracy of information lifecycle where knowledge and to reduce time spent looking for processes are common. information. • Optimise process for authoring and • Reduce total Document, managing documents, requirements, and data. – reduce button clicks. Requirements and Data management costs by improving • Standardise authoring process for access to information at the right engineering and pure document time and in the right form. management authors.
Technical Approach Siemens uses their commercial expertise and practices, such as the AdvantEdge Delivery methodology, to: • Provide a Teamcenter template solution, “PLM -in-a-Box – Early Acquisition Edition” • Deliver a virtual machine application copy and supporting documentation to enable deployment to a host environment for PLM on-boarding and Program Management Office The Early Acquisition PLM Solution is being modeled on the Ground Based Strategic Deterrent Program (GBSD) program office and select Enterprise PLM-CI Defense Business System (DBS) artifacts.
Technical Approach MR Plan Business Goals & Hand-Over to Deployment Team Process Improvements Frozen Solution Verified Solution … Maturity Reviews… Definition Iterative Configuration & Verification Validate Solution Deploy Definition Sustain Affirm Value Key User Exposure Business Adoption & Readiness Business, Process & IT Characteristics Initial Business Impact & Refine Business Impact & & UOC / Learning Strategies Adoption Plan Iterative Configuration & Affirm Value Validate Solution Definition Key User Exposure Deploy Sustain Verification • • • • • • Establish project scope Validate (or define*) the solution Define configuration points with Key Users to execute scenario- Execute final user acceptance Maintain the solution through an integrated review of process experts based verification activities • • • Outline solution and define Ensure users and system Support users characteristics, process, business • • value Verify (test) subset of Gain further understanding of readiness for production • Monitor system health use cases, capabilities and scenarios requirements as solution solution and prepare for deployment • Configure & integrate • Verify the value delivered to the • Confirm and freeze scope & matures through scenario-based adoption • solutions into single view Complete learning delivery, and business business requirements maturity reviews (Big-Block) document process impacts AdvantEdge Delivery *requirements-based variant • Secure stakeholder support • Business Adoption & Readiness Define and communicate business value • Assess business impact and ensure user readiness
Entire spec including body Text Spec with Headings Only Spec Only Derived from SOW Table A Not imported Links to Paragraphs Para Titles and links derived from “Requirements Traceability with Dist D” Links to Specs Creation of Specs and mapping derived from SOW Table A
Links To the SOW • The SOW has both defining and complying links
Links Between CDD-WSS • Links between CDD-WSS were derived from “Requirements Traceability with Dist D”
Solution: Document & Change Management From This: To This: Go through CCB Document Request 5.1 Process Received Document assigned to Document Owner 5.2 for creation or Document Owner revision, determines 5.3 provides document classification to PIT for submittal 5.8 to PM for review/ signature Technical Reviewer(s) review document 5.4 Document Owner inputs changes, as Yes Changes required and works required? with PIT to ensure Document Owner Changes Yes 5.5 PM approval inputs changes, as required? 5.9 required (CRM) No No 5.10 CMO prepares Branch Lead document for reviews/ approves release document 5.6 Yes Document Owner Changes 5.5 inputs changes, as External Yes Document provided required? 5.9 required (CRM) Approval to PIT for external 5.11 Required? signatures No No No Document needs Document released CCB Approval? and uploaded into 5.7 Document Library Yes
Initiate a Workflow Change Management is controlled by a series of Workflows covering all Approvals and changes 12
Workflow Visualization The Workflow continues to run until all Tasks are completed. 1 13
Thank you Questions? Comments? POC: larry.uchmanowicz@siemensgovt.com
Recommend
More recommend
