Distribution Statement A : Approved For Public Release; Distribution is unlimited 1 A testcase framework for the PLCS-IF Ben Kassel Naval Surface Warfare Center Carderock Division Distribution Statement A : Approved For Public Release; Distribution is unlimited
A testcase framework for the PLCS-IF. Ben Kassel Naval Surface Warfare Center Carderock Division. Distribution Statement A : Approved For Public Release; Distribution is unlimited. Part & System Definition (Caterpillar 3512, Starboard Main Engine, Propulsion System) - PowerPoint PPT Presentation
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Distribution Statement A : Approved For Public Release; Distribution is unlimited
1
A testcase framework for the PLCS-IF
Ben KasselNaval Surface Warfare Center
Carderock Division
Distribution Statement A : Approved For Public Release; Distribution is unlimited
Distribution Statement A : Approved For Public Release; Distribution is unlimited
2
Product Model data is the combination of 3D geometry and non-graphic attributes to define ship objects such as a piece of equipment, deck, bulkhead, etc. Product Model data can be organized to define interim products and ultimately the entire ship.
Advocates anticipate substantial economies from Product-Model-based design, construction, and service-life support activities due to better integration and reduction of engineering effort to locate, verify, and transform information.
Part & System Definition (Caterpillar 3512, Starboard Main Engine, Propulsion System)
Process Definition (Starting instructions, shaft alignment)
Logistics Support (FGC, SCLSIS, etc.)
Digital Product Model DataA brief review
Distribution Statement A : Approved For Public Release; Distribution is unlimited
3
Digital Product Model Data… its more than just design and construction
Functional Analyses
Concept or Feasibility
Studies (Analysis of
Material Approaches)
Identify Critical
Systems & Technologies
Analysis of Alternatives
Feasibility Studies
Capabilities Development
Pre-Preliminary / Indicative;
Preliminary; andContract Design
Sub-Systems Development
IOCDetail Design
Ship Production
Trials
Life CycleOperations
&Support
A B FOC
Ship Production
DT&E/LFT&E/IOT&E
Follow (FRP) Ship ConstructionFRP DR
ICD CDD
C
Follow (LRIP) Ship Construction
Program Initiation at MS A or MS B
Acquisition Strategy Defined
Full Program Funding through
Out Years
Lead Ship Ready for Deployment
Full Rate Production
Decision Review
Lead Ship Construction
Major Sub -Systems Development
System Integration
RDT&E BA 4 & BA 5(for Concepts, Requirements Dev, Design, Systems Eng, Acq Doc, Major Systems Dev.)
Design Readiness
Review
SCN
Critical Technology Development
O&MNRDT&E BA 3 & BA 4 (for Critical Technology Development)
FOT&E (as required)
DRR
Operations &Support
New DoD New DoD 50005000
Technology Opportunities & User Needs
Operations &Support
System Development
& Demonstration
Technology Development
BProduction & Deployment
Pre-Systems Acquisition Systems Acquisition(Engineering Development, Demonstration, LRIP & Production)
C
Sustainment
ICD CDD
FOC
LRP/IOT&E FRPDecision Review
IOC
Concept Refinement
A
DisposalSustainment
ConceptDecision
CPD
Joint Capabilities Integration & Development
CD
CPD
Design Decision Review
Exploratory Design Force
Architecture Studies
ROM or Concept Studies
Functional Analyses
Concept or Feasibility
Studies (Analysis of
Material Approaches)
Identify Critical
Systems & Technologies
Analysis of Alternatives
Feasibility Studies
Capabilities Development
Pre-Preliminary / Indicative;
Preliminary; andContract Design
Sub-Systems Development
IOCDetail Design
Ship Production
Trials
Life CycleOperations
&Support
AA BB FOC
Ship Production
DT&E/LFT&E/IOT&E
Follow (FRP) Ship ConstructionFRP DR
ICD CDD
CC
Follow (LRIP) Ship Construction
Program Initiation at MS A or MS B
Acquisition Strategy Defined
Full Program Funding through
Out Years
Lead Ship Ready for Deployment
Full Rate Production
Decision Review
Lead Ship Construction
Major Sub -Systems Development
System Integration
RDT&E BA 4 & BA 5(for Concepts, Requirements Dev, Design, Systems Eng, Acq Doc, Major Systems Dev.)
Design Readiness
Review
SCN
Critical Technology Development
O&MNRDT&E BA 3 & BA 4 (for Critical Technology Development)
FOT&E (as required)
DRR
Operations &Support
New DoD New DoD 50005000
Technology Opportunities & User Needs
Operations &Support
System Development
& Demonstration
Technology Development
BBProduction & Deployment
Pre-Systems Acquisition Systems Acquisition(Engineering Development, Demonstration, LRIP & Production)
CC
Sustainment
ICD CDD
FOC
LRP/IOT&E FRPDecision Review
IOC
Concept Refinement
AA
DisposalSustainment
ConceptDecision
CPD
Joint Capabilities Integration & Development
CD
CPD
Design Decision Review
Exploratory Design Force
Architecture Studies
ROM or Concept Studies
The Digital Product Model can support the entire ship’s lifecycle.
• The DPM should be the primary source of data for all pre milestone B activities.• The DPM should be used by NAVSEA to validate the design during the Detail
Design and Ship Production phases.• The DPM should be the authoritative source of data in support of the Situation
Incident Room upon delivery of the ship.• The DPM should be the authoritative source of data for technical manuals,
training.
Distribution Statement A : Approved For Public Release; Distribution is unlimited
4
Uses of the Digital Product ModelRear Admiral Eccles affirmation
Distribution Statement A : Approved For Public Release; Distribution is unlimited
5
• Provide guidance for the acquisition of product model and related technical data.• This instruction applies to product models and technical data derived directly from
the product model such as engineering analysis, bills of material, and drawings.• This instruction implements the DON POLICY ON DIGITAL PRODUCT/TECHNICAL
DATA issued in 2004 and the NAVSEA SHIP DESIGN AND TOOLS GOALS issued in 2008.
• This instruction does not specify a format explicitly, but instead requires Navy stakeholders to reach consensus on the definition and delivery of product model data.
• Balances cost, data utility, and data exchange technology.
NAVSEA Instruction 9040.3AAcquisition and Management of Product Model and other Technical Data
Ship and ship system design, acquisition, and fleet support activities shall procure and accept product model data in accordance with ISO 10303, Standard for the Exchange of Product model data (STEP) format, native Computer Aided Design (CAD) files, and/or Leading Edge Architecture for Prototyping Systems (LEAPS) format. This should be based on solutions that provide the best technical and cost performance as determined by a NAVSEA business case analysis.
Distribution Statement A : Approved For Public Release; Distribution is unlimited
6
Product Model Data Definition and ExchangeA NAVSEA perspective
A two level approach for the exchange of product model data
First level :
Second level :
Support configuration management, logistics support, provisioning, spares, and repairs through the use of STEP for geometry, product structure, non graphical attributes, and to manage configuration items of the as-built / as-maintained ship.
Deliver the as-designed class model of 1) molded forms suitable for defining a general arrangement2) scantling level of detail of structure to support structural (and
other types of) analysis3) functional distributed systems model (i.e. path, components, and
connections)4) compartmentation, including accesses, opening, and tightness5) plates, stiffeners, brackets, collars, and other structural
components as parts6) distributed system components, fittings, and equipment as parts.
Distribution Statement A : Approved For Public Release; Distribution is unlimited
7
The Digital Product Model shall be delivered in both a native and neutral format. The neutral format shall comply with the Department of the Navy Policy on Digital Product/Technical Data dated 23 October 2004. ISO 10303 Part 214 shall be used to define the Digital Product Model geometry. ISO 10303 Part 239 shall be used to define product structure, the relationship between objects, and configuration management data. The Builder shall provide a list in the PPM1 of each data exchange specification (DEX) that will be used to support the ISO Part 239 exchange. In the event the contractor can demonstrate the need for an additional DEX, then the contractor shall develop a NAVSEA approved DEX.
1 Process and Procedures Manual
Implementing the PolicyShips Specification 098 – 3D Product Model
Distribution Statement A : Approved For Public Release; Distribution is unlimited
8
NATIVE ShipConstructor® DATA
EXTRACTED NON-GRAPHICAL ATTRIBUTES
EXTRACTED GEOMETRY
Archiving Ship Product Model DataMining ShipConstructor Product Model Definition
Distribution Statement A : Approved For Public Release; Distribution is unlimited
9
A testcase framework for PLCS-IFTest case ultimate depth and breadth
Distribution Statement A : Approved For Public Release; Distribution is unlimited
A testcase framework for PLCS-IFA small distributed system
Distribution Statement A : Approved For Public Release; Distribution is unlimited
Monitor Gate Valve condition
1. Locate all of the valves in fuel oil service2. Determine the date the valve was placed in service3. If the valve is more than 20 years old flag it to be replaced4. If the valve is between 10 and 20 years old, issue a service
bulletin to inspect for signs of seepage and report back5. For all reports that indicate seepage, schedule valve
replacement during the next scheduled maintenance period6. Determine the next time the ship has maintenance scheduled7. For all reports that indicate no problem make a notation in the
ships maintenance logs
Attributes to support USE case
ShipHull NumberDate put in serviceLocationAvailability
System AttributesType (SWBS?)Fluid Type
Part AttributesSeal typeModel numberSerial numberSeal materialInstall dateOverhaul dateSize
The useful life of gate valves used in fuel oil service is 20 years. Gate valves between 10 and 20 years old should be inspected periodically, and their condition reported. This is not a critical issue so the repair does not need to be made immediately. However, planning is required to purchase new seals or replacement valves depending on their condition. From the product model repository
A testcase framework for PLCS-IFA sample USE case
(Product Operational Information)
Distribution Statement A : Approved For Public Release; Distribution is unlimited
12
The test case was developed to exercise • Parts• Assemblies• Systems• Configuration Management• Multiple product structures• Workflow• Revision control • Parts placed in a system• Parts placed in an assembly• Assemblies placed in a system• Systems divided into subsystems
A testcase framework for PLCS-IFScope like stuff
The test case includes information required to • Design the system• Develop the work package to assemble a system• Purchase components• Maintain the system• Repair the system• Operate the system
Provide sufficient data to develop a product model and collect all the “other technical data” necessary to perform the aforementioned task. The test shall be of sufficient breadth and depth that the output products required to support the aforementioned tasks can be generated automatically from the product data. Additionally, there will be sufficient information to associate the other technical data to the product data and to allow simultaneous configuration management of the product data and other technical data.
Distribution Statement A : Approved For Public Release; Distribution is unlimited
13
A testcase framework for PLCS-IFBill of Material (well almost)
Instance Component Item Name T0 T1 T2 R00 R01 R02 R10 R11 R12 R20 R21 R22 pipe end x pipe end y pipe end z lengthE01 Tank, 700 gallon 48 0 0 0 -1 0 1 0 0 0 0 1E02 10 GPM Pump and Motor Unit 120.898 47.38 -4.07 0 1 0 -1 0 0 0 0 1E03 Tank, 200 gallon 209.12 54 12 0 1 0 -1 0 0 0 0 1E04 Breaker Box, 300 amp 183 72 36 1 0 0 0 1 0 0 0 1
From To Node 1 UID Node 2 UID Unique ID Connection Description
J03 Port 1 J04 Port 2 distPort_20 distPort_23 distJoint_5 J03 Port 1 - J04 Port 2J04 Port 1 V01 Port 1 distPort_22 distPort_62 distJoint_6 J04 Port 1 - V01 Port 1V01 Port 2 J05 Port 1 distPort_63 distPort_24 distJoint_7 V01 Port 2 - J05 Port 1J05 Port 2 J06 Port 1 distPort_25 distPort_26 distJoint_8 J05 Port 2 - J06 Port 1
distPort_26
A testcase framework for PLCS-IFConnections and Connectors
Distribution Statement A : Approved For Public Release; Distribution is unlimited
23
A testcase framework for PLCS-IFConnections and Connectors
P06 Port 2J15 Port 2
J15P06
Distribution Statement A : Approved For Public Release; Distribution is unlimited