Product Data Interoperability Overview Critical Context for Today’s Capability Demonstration. www.NSRP.org. Dan Billingsley NSRP Program Manager NAVSEA 05DM. Pete Halvordson Vice President, Engineering GD Electric Boat. Rick Self NSRP Executive Director ATI Corporation. Objectives. - PowerPoint PPT Presentation
22
Product Data Interoperability Product Data Interoperability Overview Overview Critical Context for Today’s Capability Demonstration Critical Context for Today’s Capability Demonstration www.NSRP.org www.NSRP.org Dan Billingsley Dan Billingsley NSRP Program Manager NSRP Program Manager NAVSEA 05DM NAVSEA 05DM Rick Self Rick Self NSRP Executive NSRP Executive Director Director ATI Corporation ATI Corporation Pete Halvordson Pete Halvordson Vice President, Vice President, Engineering Engineering GD Electric Boat GD Electric Boat
Transcript
Product Data Interoperability OverviewProduct Data Interoperability Overview
Critical Context for Today’s Capability DemonstrationCritical Context for Today’s Capability Demonstration
www.NSRP.orgwww.NSRP.org
Dan BillingsleyDan BillingsleyNSRP Program ManagerNSRP Program Manager
NAVSEA 05DMNAVSEA 05DM
Rick SelfRick SelfNSRP Executive NSRP Executive
DirectorDirectorATI CorporationATI Corporation
Pete HalvordsonPete HalvordsonVice President, EngineeringVice President, Engineering
GD Electric BoatGD Electric Boat
Objectives
Explain the context of NSRP and Product Model Explain the context of NSRP and Product Model InteroperabilityInteroperability– NSRP OverviewNSRP Overview– The shipbuilding interoperability challengeThe shipbuilding interoperability challenge– The scope of Product Data InteroperabilityThe scope of Product Data Interoperability
» and how current efforts fitand how current efforts fit Business Case: Annual Cost of Business Case: Annual Cost of NOTNOT having having
interoperabilityinteroperability Evidence from commercial shipbuildingEvidence from commercial shipbuilding Business Model Demands for InteroperabilityBusiness Model Demands for Interoperability Navy future-state vision challenge to industryNavy future-state vision challenge to industry
• Attacks common cost-drivers and inherently multi-yard, multi-program problems
National Shipbuilding [& Ship Repair] Research ProgramCollaboration of 11 U.S. Shipyards teaming with Navy and supplierson Technologies
and Processes to Reduce the Cost of Naval Ship Acquisition and Repair
Execution-focused formula that works ! A rapid, agile, enterprise-wide real-time collaboration to ACT (not study) … Rapidly develop and deploy cross-program solutions to prioritized common cost drivers … Where there is strong commitment to execute thru multi-shipyard teams and … Willingness to share cost, risk and knowledge in real-time with all yards
A cost-sharing, collaborative, shipbuilding technology research consortium focused on reducing the cost of Navy shipbuilding and repair
Formed at Navy request in 1997-1998
NSRP = Enterprise-wide CollaborationNSRP = Enterprise-wide CollaborationEffecting Large Scale Change with Industry-wide SolutionsEffecting Large Scale Change with Industry-wide Solutions
Accuracy control – metrology, processes and toolsBenefit: Reduces rework labor, materials, cost and cycle time; enables automation
Steel Processing – Laser cutting, precision forming, and tab & slot technologyBenefit: 30% reduction in steel cutting costs; 8% reduction in steel plate usage in first production use
IT Interoperability – Integrating shipyard IT systems (CAD, CAM, Parts …) across firms & functionsBenefit: Reduces costs & acquisition cycle time, improves 1st time quality, enables outsourcing
eBusiness for Enterprise Integration – across construction, repair, logistics activities and suppliersBenefit: cuts labor and cycle time of daily processes by 60%
Common Parts Catalog – Enterprise standard, shared parts databaseBenefit: facilitates standardization & IPDE initiatives; fewer parts to procure, inspect, certify, track, warehouse …
Joint Lean Learning Curve - Accelerate adoption of productivity ImprovementBenefit: Systematic, repeatable boosts in productivity from shop-level to design, engineering and supply chains
Todd
NASSCO
Bath Iron Works
Northrop Grumman Ship Systems
Newport News
Suppliers
Electric Boat
NationwideeBusiness Networkfor Shipbuilding &
Ship Repair
The Problem While credited with major reductions in design and manufacturing While credited with major reductions in design and manufacturing
cost, IPDEs pose a significant software development / integration cost, IPDEs pose a significant software development / integration challenge and expense. challenge and expense. – IPDE cost for a major ship or submarine construction program can total IPDE cost for a major ship or submarine construction program can total
$150M to $200M, of which 45-55% is for integration planning, information $150M to $200M, of which 45-55% is for integration planning, information engineering and interface software development.engineering and interface software development.
Typically each ship or submarine program develops an IPDE to take Typically each ship or submarine program develops an IPDE to take advantage of latest hardware and software and to suitadvantage of latest hardware and software and to suit– program requirements,program requirements,– team member work practices, and team member work practices, and – team member business relationships team member business relationships
Interoperability among components has been achieved by ad-hoc Interoperability among components has been achieved by ad-hoc and proprietary interfaces resulting in: and proprietary interfaces resulting in: – Duplication of development effort,Duplication of development effort,– 8-10 partially integrated systems that are not interoperable with others,8-10 partially integrated systems that are not interoperable with others,– Annual integration expenses of $10M-$30M for each major program,Annual integration expenses of $10M-$30M for each major program,– Multiple incompatible systems at each shipyard, and Multiple incompatible systems at each shipyard, and – Numerous inconsistent sources of product information for Navy engineering Numerous inconsistent sources of product information for Navy engineering
and service life support.and service life support.
The Problem (con’t)
Information technology ages quickly - access to vital product data becomes problematic early in the ships life cycle
Managing the Cost and Risk of Computer Managing the Cost and Risk of Computer Systems Development – IDE / IPDE / PLM Systems Development – IDE / IPDE / PLM – The development of these systems represents a significant The development of these systems represents a significant
investment in time and moneyinvestment in time and money
– It can represent a significant amount of Program riskIt can represent a significant amount of Program risk
– Interoperability of disparate systems remains a significant Interoperability of disparate systems remains a significant challenge challenge
Shipbuilders’ 3D CAD SystemsProgram Location 3D CAD
2005 Benchmarking Study2005 Benchmarking StudyComparison to leading int’l commercial yardsComparison to leading int’l commercial yards
““Inconsistent and ill defined design processes in the U.S. Inconsistent and ill defined design processes in the U.S. shipbuilding industry have led to excessive design lead-times shipbuilding industry have led to excessive design lead-times and design man-hours. and design man-hours.
International shipyards have International shipyards have a standard approach to ship design a standard approach to ship design with well-defined design stages and clearly specified prioritywith well-defined design stages and clearly specified priority when when compared to international counterparts.”compared to international counterparts.”
““To optimize production performance at the shipyard level, To optimize production performance at the shipyard level, each shipyard should have a formalized and consistent each shipyard should have a formalized and consistent shipbuilding strategy from which design rules and guidelines shipbuilding strategy from which design rules and guidelines are developed for each stage of the design process.are developed for each stage of the design process.
If the Navy continues acquisition strategies that are teamed, or If the Navy continues acquisition strategies that are teamed, or wants to provide for later cooperation of given designs, wants to provide for later cooperation of given designs, industry-wide design standards would have to be developed if industry-wide design standards would have to be developed if this level of flexibility is desired without impairing productivitythis level of flexibility is desired without impairing productivity””
Computer AidedEngineeringVisualizationSimulation
ANALYZE
ComputerAided
Design
DEFINE
Planning/ERP
PLAN
Parts Order/Parts Catalog
SOURCE
ComputerAided
Manufacturing
MANUFACTURE
Product Data ManagerProduct Data Manager
Requirement Management
System
REQUIREMENTS
Computer AidedEngineeringVisualizationSimulation
ANALYZE
ComputerAided
Design
DEFINE
Planning/ERP
PLAN
Parts Order/Parts Catalog
SOURCE
ComputerAided
Manufacturing
MANUFACTURE
Product Data ManagerProduct Data Manager
Requirement Management
System
REQUIREMENTS
IPDE Elements Found at Every ShipyardVarious levels of automation, integration
Computer AidedEngineeringVisualizationSimulation
ANALYZE
ComputerAided
Design
DEFINE
Planning/ERP
PLAN
Parts Order/Parts Catalog
SOURCE
ComputerAided
Manufacturing
MANUFACTURE
Product Data ManagerProduct Data Manager
Requirement Management
System
REQUIREMENTS
Computer AidedEngineeringVisualizationSimulation
ANALYZE
ComputerAided
Design
DEFINE
Planning/ERP
PLAN
Parts Order/Parts Catalog
SOURCE
ComputerAided
Manufacturing
MANUFACTURE
Product Data ManagerProduct Data Manager
Requirement Management
System
REQUIREMENTS
Current Events
Total Ship Total Ship Shock TrialShock Trial
LEAPSLEAPS
CPCCPCISEISE
Navy ERPNavy ERP
SPARSSPARS
Computer AidedEngineeringVisualizationSimulation
ANALYZE
ComputerAided
Design
DEFINE
Planning/ERP
PLAN
Parts Order/Parts Catalog
SOURCE
ComputerAided
Manufacturing
MANUFACTURE
Product Data ManagerProduct Data Manager
Requirement Management
System
REQUIREMENTS
Computer AidedEngineeringVisualizationSimulation
ANALYZE
ComputerAided
Design
DEFINE
Planning/ERP
PLAN
Parts Order/Parts Catalog
SOURCE
ComputerAided
Manufacturing
MANUFACTURE
Product Data ManagerProduct Data Manager
Requirement Management
System
REQUIREMENTS
Product Data Transfer TodayEstimated Annual Cost to Navy of Product Data Transfer
$504M$504M
$$396M396M
$1.5B per year$1.5B per year
TotalTotal
$144M$144M
$504M$504M
Across organizationsAcross organizations– Co-production / Co-design - more flexibility in teaming & 2Co-production / Co-design - more flexibility in teaming & 2ndnd sourcing. sourcing.– Acquisition programs can re-use engineering tools and data Acquisition programs can re-use engineering tools and data
management components developed by preceding programs.management components developed by preceding programs.– Expedited review of shipbuilder designs by government engineering Expedited review of shipbuilder designs by government engineering
agents.agents.– Enable common methods of handling product data for service life Enable common methods of handling product data for service life
supportsupport Within shipyardsWithin shipyards
– Components can be upgraded or replaced without major disruption Components can be upgraded or replaced without major disruption or redevelopment of the rest of the IPDE infrastructure – yielding or redevelopment of the rest of the IPDE infrastructure – yielding improved flexibility, improved leverage with vendors and reduction of improved flexibility, improved leverage with vendors and reduction of recurring cost.recurring cost.
– Third-party capability can be introduced in specific areas including Third-party capability can be introduced in specific areas including discipline-focused software developed by ABS, ONR, DARPA, discipline-focused software developed by ABS, ONR, DARPA, academia and industry.academia and industry.
– Reduce/eliminate need for multiple IPDE’s within a single yard.Reduce/eliminate need for multiple IPDE’s within a single yard.
Business Drivers for InteroperabilityBusiness Drivers for Interoperability
CustomersCustomersNavyNavyFleet ShipFleet Ship
Interfaces and Tools to exchange data Interfaces and Tools to exchange data among key IT systems and across the among key IT systems and across the enterprise’s organizationsenterprise’s organizations - Engineering Data (ISE)- Engineering Data (ISE) - Inter-organization Transaction Data - Inter-organization Transaction Data
(SPARS)(SPARS) - Parts Data (Common Parts Catalog, - Parts Data (Common Parts Catalog, Mat’l Mat’l Stds)Stds) - - Manufacturing data (ISPE)Manufacturing data (ISPE)
Industry Consensus Industry Consensus eBusiness ModeleBusiness Model
Integrated Shipbuilding Environment for the Integrated Shipbuilding Environment for the Networked Functional Capability across the Networked Functional Capability across the
EnterpriseEnterprise
CAMCAM
PDMPDM
MRP / ERPMRP / ERP
Part CatalogPart Catalog
CADCAD
WorkflowWorkflow
Elements of Interoperability
Shared Concept of Shared Concept of Information Content Information Content and Relationshipsand Relationships
Native ANative A Native BNative BTT TT
ExchangeExchangeFormatFormatSpecSpec
Contract Contract TermsTerms
Acquisition PolicyAcquisition Policy
NSRP ISE AccomplishmentsNSRP ISE Accomplishments National consensus architectureNational consensus architecture for product data interoperability for product data interoperability Published 100’s of industry Published 100’s of industry use casesuse cases defining requirements for defining requirements for
information sharinginformation sharing Developed consensus data element definitions and Developed consensus data element definitions and consensus consensus
taxonomytaxonomy for communicating product data across the enterprise for communicating product data across the enterprise Developed Developed toolstools and demonstrated feasibility for interoperability and demonstrated feasibility for interoperability
of :of :– Structure & Piping (March 2000 to December 2003)Structure & Piping (March 2000 to December 2003)– HVAC & CPC Interfaces (October 2003 to October 2004)HVAC & CPC Interfaces (October 2003 to October 2004)– Current Project (April 2005 – July 2006)Current Project (April 2005 – July 2006)
» Ship Compartmentation Ship Compartmentation » Engineering AnalysisEngineering Analysis» ElectricalElectrical» Steel Processing with Rules ProcessingSteel Processing with Rules Processing
Result of this approachResult of this approach: : Product Data Interoperability Standards are Substantially CompleteProduct Data Interoperability Standards are Substantially Complete
Standard Approved
Standard Development
Information Model
Testing Framework
Prototype Translators
Information interoperability lifecycle
RolesRoles
ISOISO
NSRPNSRP
NAVSEANAVSEA
NAVALNAVALPROGRAMPROGRAM
Information Information interoperabilityinteroperability
and work with the Navy to ….and work with the Navy to …. Navy: Create the business pullNavy: Create the business pull
– Define Navy Shipbuilding Enterprise plan for standards-based Define Navy Shipbuilding Enterprise plan for standards-based product data acquisition & useproduct data acquisition & use
» Throughout design, construction and service lifeThroughout design, construction and service life» Standard contract clauses Standard contract clauses » Through-life archival & access approachThrough-life archival & access approach
ShipyardsShipyards – Move toward modular IPDE architecture with standards-base interfacesMove toward modular IPDE architecture with standards-base interfaces– Clarify marginal costs to package and deliver digital dataClarify marginal costs to package and deliver digital data– Demand standards-based translators from software vendorsDemand standards-based translators from software vendors– Capitalize on business opportunities enabled by interoperabilityCapitalize on business opportunities enabled by interoperability
Business considerations and cultural barriers are Business considerations and cultural barriers are more significant than technical issuesmore significant than technical issues
Jan1999
Jan2000
Jan 2001
Jan 2002
Jan 2003
Jan 2004
Jan 2005
Jan 2006
Phase 2 – Deployment for Structure & Piping
Phase 1- Requirements definition & architecture for shipbuilding systems interoperability
