Upload
others
View
0
Download
0
Embed Size (px)
Citation preview
Trident Systems Inc 10201 Lee Hwy
Fairfax, Virginia 22030-2222www.tridsys.com
September 24, 2003
U.S. Army Logistics Integration Agency5870 21st Street, Bldg 212Ft. Belvoir, VA 22060-5941
www.lia.army.mil
EIAEIA--927: Common Data 927: Common Data Schema for Complex SystemsSchema for Complex Systems
September 24, 2003John Reber
September 24, 2003 2
Exploding System Scope &
Complexity
Exploding System Scope &
Complexity
+
Accelerating Technology Base Rate-of-Change
Accelerating Technology Base Rate-of-Change
Constrained Budgets & Schedules
Constrained Budgets & Schedules
Business
Military
Industrial
The Complex Systems ProblemThe Complex Systems Problem
Big Trouble
0 5 10 15 20 25 30 35 40 45
Percent of Total Ownership Cost Determined Percent of Total Ownership
Cost Spent (Cumulative)
MS 0 MS I MS II MS III
O & S Costs(48%)
Development Costs (20%)
Procurement Costs (32%)
Time (in years)
100%
80%
60%
40%
20%
0%
New Programs Must Lock-in Costly Decisions Early, Before Detailed Impact Analysis
CDDBLIFCMIS
FEDLOG
IETM
SBSX
ATAV
FVPDS
WOLFOSMISWLMP
LIDB
CCSS
AMDF
CBS-XPFSA
RIDB
SB700-20FVPDS
SDS AMCOS
JEDMICS
ReqVal
PADDSMEARS
WebCATS
ATIRS
Mature Programs Must Operate in a Chaotic, Stovepiped Environment of Legacy Data
September 24, 2003 3Largely manual: inconsistent design baselines, assessment lags designLargely manual: inconsistent design baselines, assessment lags design
Tactical Decision Support
Req Elicitationand Analysis
Functional Design
and Analysis
HME / HW / SW Design & Analysis
HME / HW / SW Development
Training and Ops Support
Modification and Upgrade
Maintenance and Logistics
Requirements Mgmt System Integration
and Test
Manufacturing & Development
Process
Cost / Risk / ScheduleManagement
The Complex Systems Tower of BabelThe Complex Systems Tower of Babel
System Data Today
� Stovepiped Tools With Limited Scope and No Substantial Interoperability� Multiple Independent Files and Databases With Ad Hoc Manual Configuration
Management, Traceability, and Consistency Checking across Domains� PDM and Enterprise Management Solutions are File Based and Fail to
Provide any Useful Integration of the Information Stored in the Files
Concept/Tech.Development System Development &
Demonstration Production & DeploymentOperations & Support
A BC IOC
FOC
AB
C
September 24, 2003 4
Today: Suboptimal, Reactive Program Management EnvironmentFuture: Proactive Management Enabled by Integrated InformationToday: Suboptimal, Reactive Program Management EnvironmentFuture: Proactive Management Enabled by Integrated Information
DemonstrationValidation
EngineeringDevelopment
Ops &Support
ConceptExploration
System Data Today
Eliminating the Tower of BabelEliminating the Tower of Babel
Data Shortfalls, Management Challenges– Stovepiped Tools & Data Stores With
Limited Scope and Scalability – Limited Interoperability Among Tools &
Data Stores– Error-Prone Traceability & Consistency
Optimized Management Environment– Enables Collaborative, Concurrent Effort
Across Distributed Sites– Timely Snapshots of Program Status
Across Multiple Information Domains– Complete, Integrated Picture of the
Program
System Data in the Future IDE
Top-Level Requirements
FunctionalDesign
HW/SWDevelopment
HW/SWDesign
Budget, Schedule,
Risk
Logistics &Support
OperationalNeed
EnvironmentRepresentations
September 24, 2003 5
• Formal Structure for Representing Spectrum of System Data• Dynamic Schema Provides Means for Accommodating Emerging
Data Representation Needs
Top Level Req IS Logical EnvironmentConceptual
Control
DataData
Logical Info Processing EnvironmentTop Level Req Structural / HMEConceptual
REQSPEC
Syn Env
Logical Implementation Structural / HMECONCEPTUAL
Support Sys & Dev Eng Env
CapabilitiesPerformanceDependabilityMaintainabilityConstraints
PlatformsSensorsWeaponsCommunicationTactics
HardwareSoftwareOperatorsDocumentation
HullMechanicalElectricalHydraulicPneumatic
Atmospheric
TerrestrialThreatAllied
ScheduleCostRiskStaffingProgrammatics
1000
100
10
Jan Apr Jul Oct
MANUFACTURING
Manufacturing
Material AcqFabricationAssemblyInteg / TestHandling / DelivFactory FloorRobots / Mach
FunctionData FlowControl FlowEnergy FlowMaterial Flow
EnvironmentManagement
Sys Eng Meth & ToolsHW/SW/HF Eng M&THME/Hyd/Pneum M&TPower/Propulsion M&T
Logistics / SupplyOperationsTrainingMaintenanceRepair
Oceanographic
Common Systems Information Common Systems Information Schema ConceptSchema Concept
A Broad, Extensible Representation Approach is KeyA Broad, Extensible Representation Approach is Key
September 24, 2003 6
Top Level ReqIS Logical IS Implementation Environment
Structural / HM EConcept ual
Control
DataData
Logical Info Processing EnvironmentTop Level Req Structural / HM EConcept ual
REQ
SPEC
Syn Env
Logical Implemen tation Structural / HM ECONCEPTU AL
Support Sys & Dev Eng Env
1000
100
10Jan Apr Jul Oct
M ANUF ACTUR ING
Manufact uring
EnvironmentManagement
Develop Data Schema
• Leverage Existing and Emerging Data Standards
• Accommodate Tools in Use by Candidate Pilots
• Work in the Gaps Where Required
Validate in Distributed COTS Testbed1
2
3
4
Conduct DoD Pilots
• Data Interoperability • Consistency Management• Interaction with Legacy Tools• Integration of Legacy/Emerging
Data Sources
Manage Transition
• Implement Testbed Capabilities• Demonstrate Utility (Collect Metrics)
• Evolve Industry Consortium• Focus on DoD Program Mgr Needs
EIAEIA--927 (MultiView) Program Approach927 (MultiView) Program Approach
Testbed Server
Interfaces to Legacy Databases
JDBC FutureXML
CustomODBC
Testbed Mapper
AbramsClient
Abrams D
ata N
avigation
Abrams D
ata Analysis
Abrams D
ata N
avigation
Abrams D
ata Analysis
SPAR
PFSAExcel …
Data
Query
QueryAnalyzer
COTS-based communications
QueryTranslator
Results Aggregator
ResultsTranslator
MultiView SchemaMV_Ele ment
Ac tor
Even t
Pe rso n Org an iza tio n
Fac il i ty En vi ro nme nt Flow
Fu nc tio nPr oce ssToo l
SystemMate rial_or _c omp on en t
De sig n
Doc ume nt
Plan Ob je cti ve
Req ui re men t Con stra in t
MultiView SchemaMV_Ele ment
Ac tor
Even t
Pe rso n Org an iza tio n
Fac il i ty En vi ro nme nt Flow
Fu nc tio nPr oce ssToo l
SystemMate rial_or _c omp on en t
De sig n
Doc ume nt
Plan Ob je cti ve
Req ui re men t Con stra in t
Model204
ODBC
Oracle Jasmine Sybase Future
COTSCOTS ModifiedCOTS
ModifiedCOTS
ModifiedCOTS
ModifiedCOTS
MultiView-specific
MultiView-specific
MultiView-specific
MultiView-specificKey
Import
Import
NativeOracle
September 24, 2003 7
Data Schema DevelopmentData Schema Development
� Standards Based– ISO 18876 (IIDEAS) Is Basis for Methodology– ISO 15926 (Formerly EPISTLE) – Initial
Integration Model– Ancillary Standards Incorporated by Reference
� Current State– Detailed Integration Procedure Defined– Standards Integrated
» ISO 10303 (STEP) AP233 – Systems Engineering» DoD Corporate Logistics Data Model (Partial)» AP212 – Electrotechnical Design and Installation
– Data Concepts Mapped to Model– Usage and Tailoring Guides Developed
September 24, 2003 8
Schema Integration Dynamic ViewSchema Integration Dynamic View
ExtendedIM (1)
InitialIM AM
AM
ExtendedIM (2) AM
ExtendedIM (3) AM
ExtendedIM (4)
September 24, 2003 9
Schema Integration Static ViewSchema Integration Static View
Integration Model
Intermediate Model
IntermediateModelAM AM AM
AM AM
AM AM AM
September 24, 2003 10
Data Schema Development (cont.)Data Schema Development (cont.)
� Next Integration Steps– Evaluate Product Life Cycle Support and EIA-836 (CM)
for Integration– Consider Remaining Candidates
� Standard Prioritization Rationale– Level of Adoption– Coverage of the DoD Scope of Interest– Maturity of the Standard– Currency of the Standard– Coverage of the Domain(s) Specified by the Standard
September 24, 2003 11
Testbed Architecture StatusTestbed Architecture StatusAbrams ImplementationAbrams Implementation
�An Integrated Digital Environment Based on a Common Data Format (“Schema”)– Program-Specific Tools…
»Access Data in Native Formats»Leverage Program Tool & Process Investment
– …Using Common Data Schema & Mechanisms…
»Extensible Data Format»Integrating Infrastructure»COTS-Intensive Implementation
– …To Interact with Legacy & Future Data Sources
»Preserve Legacy Data Source Integrity»Supports Data Source Migration to Future Technology
Excel
Concept Exploration &
Definitio n
Demonst ration / Validatio n
Engineering Manufact uring & Development
Production & Deplo yment
Upgrade and Replace
nt
PH ASE
1000100
10
MGMT
Jan Apr Jul Oct
SPAR(Simulation)
Post-Fielding Support Analysis
JDBC FutureXML
Data Comms
EIA-927 SchemaMV_Element
Actor
Event
Person Organization
Facility Environment Flow
FunctionProcessTool
SystemMaterial_or_component
Design
Document
Plan Objective
Requirement Constraint
ODBC
Future
NativeOracle
Database Interface Mechanisms
Data Mapping &Translation
CDDBLIFCMIS
FEDLOG
IETM
SBSX
ATAV
FVPDS
WOLFOSMISWLMP
LIDB
CCSS
AMDF
CBS XPFSA
RIDB
SB700-20FVPDS
SDS AMCOS
JEDMICS
ReqVal
PADDS
MEARS
WebCATS
ATIRS
COTSLegacy Modified COTS
MultiView-specificKey
Controller
September 24, 2003 12
COTSServer
�Establish Traceability – Determine impact of changes across
domains– Perform complex analysis on
integrated information�Configuration manage data
– Baseline across all information domains
– Manage multiple options & tradeoffs– Be alerted when data of interest
changes or schedule periodic analysis of data
�Graphically view or edit any information
– Common interface to all information– Aids verifying data completeness
EarlyEarly--Lifecycle Testbed ArchitectureLifecycle Testbed ArchitectureSystem RepositorySystem Repository--Based ImplementationBased Implementation
Agents
AdministrationQueries
Schema Editing
= Repository Plug-in
Manufacturing
StructuralSystem Design
ConceptDevelopment
System HW, SW Design
ProgramMgmt.
Operations, Logistics& Training
SystemRequirements
Test & Eval
Viewer
EIA-927 SchemaMV_Element
Actor
Event
Person Organization
Facility Environment Flow
FunctionProcessTool
SystemMaterial_
or_component
Design
Document
Plan Objecti ve
Requirement Constraint
September 24, 2003 13
ORD
EIAEIA--927 Application to Early927 Application to Early--inin--Life Programs:Life Programs:The Systems Engineering ChallengeThe Systems Engineering Challenge
The Magnitude and Complexity of the Modern Systems Environment Represents a Daunting Traceability and Consistency Management Challenge
The Magnitude and Complexity of the Modern Systems Environment Represents a Daunting Traceability and Consistency Management Challenge
Top Level Requirements
Functional Design
Software
Physical HME
CADM Architecture
Manning
Cost
Systems/Interfaces
Systems Design
Functions
Electronic Diagnostics/Electronic
PrognosticsEDEPs
Conceptual Requirements Validation Simulation
REQSPEC
System Requirements
Software
Hardware
ArchitectureTactics / Techniques /
Procedures (TTPs)TTPs
Trouble Reports (TRs)TRs
Operational ConfigurationsAMPS
TLR
CRD
Hardware
Test
System Development
System
Data Flow Modeling
Simulation & Modeling
Interface Exchange Requirements (IERs)
IERs
Architecture Modeling
Maintenance & Support
Engineering Change Proposals (ECPs)
ECPs
September 24, 2003 14
Capstone Requirements Document
Top Level Requirements Documents
Operational Requirements Documents
Mission Needs Statements
System Requirements Documents
ORD
TLR
CRD
REQSPEC
MNS
TLRTLR
TLR
MNSMNS
MNS
ORDORD
ORD
REQSPECREQ
SPECREQSPEC
REQSPECREQ
SPECREQSPEC
REQSPECREQ
SPECREQSPEC
Usually a Collection of English Language Documents, at Best Captured in Tool such as DOORS
No Clear Traceability from Capstone to TLR to ORD to System Requirements Docs
No Clear Partitioning From Higher to Lower Levels, Unknown Overlap and Redundant Specifications
Laborious Manual Process to Assess Impact of Requirements Change
High Level Requirements High Level Requirements Management & PartitioningManagement & Partitioning
September 24, 2003 15
Capstone Requirements Document
Top Level Requirements Documents
Operational Requirements Documents
Mission Needs Statements
System Requirements Documents
ORD
TLR
CRD
REQSPEC
MNS
TLRTLR
TLRMNSMNS
MNS
ORDORD
ORD
REQSPECREQ
SPECREQSPEC
REQSPECREQ
SPECREQSPEC
REQSPECREQ
SPECREQSPEC
High Level Requirements High Level Requirements Management & PartitioningManagement & Partitioning
September 24, 2003 16
System Functions
System RequirementsSystem Requirements
System Software
System Hardware
Design Domains Exist in Stovepipes with Inconsistent Contradictory Baselines
No Clear Traceability from Requirements to Functional Design to Implementation
Laborious Manual Process to Assess Consistency, Impact of Requirements Change, etc
System Requirements System Requirements Allocation and TraceabilityAllocation and Traceability
September 24, 2003 17
System RequirementsSystem Requirements
HW constraintsHW constraints
SW constraints
Functional Functional Requirements Requirements MappingMapping
System Functions
Functions Mapped to Software
Functions Mapped to Hardware
System Software
System Hardware
Integrate system design domains, enforce consistency across design baselines and eliminate engineering stovepipes
System Requirements System Requirements Allocation and TraceabilityAllocation and Traceability
September 24, 2003 18
Conceptual
Requirements Validation Simulation
Data Flow Modeling
Architecture Modeling
System System RequirementsRequirements
System Functions
System SoftwareSystem
HardwareSimulation
Results,Metrics
Scenario Simulation and Modeling Activities Lag Design and Require Manual Input of Design Parameters
Managing Consistency and Correctness from Design to Simulation is Expensive and Time Consuming
Simulation ConclusionsSimulation
ConclusionsSimulation Conclusions
Managing Consistency Managing Consistency Between Design & SimulationBetween Design & Simulation
September 24, 2003 19
Conceptual
Requirements Validation Simulation
Data Flow Modeling
Architecture Modeling
System System RequirementsRequirements
System Functions
System Software
System Hardware
Simulation Results,Metrics
Scenario
Simulation ConclusionsSimulation
ConclusionsSimulation Conclusions
Required CapabilitiesRequired CapabilitiesPerformance RequirementsPerformance Requirements
Functions, Data Flow
SoftwareBehavior
HardwareBehaviorCandidate
Design Modifications
Simulation Results
Scenario Inputs
Simulation Conclusions
Export design data directly to simulations and link results to design rationale
Managing Consistency Managing Consistency Between Design & SimulationBetween Design & Simulation
September 24, 2003 20
System System RequirementsRequirements
System Functions
System Software
System Hardware
Trouble reports (TRs) are not easily related to design and test information
Tactics / Techniques / Procedures (TTPs)TTPs
Trouble Reports (TRs)
TRsTRs
TRsTRs
TRsTRs
TRs
Engineering Change Proposals (ECPs)
ECPs
TTPsTTPs
TTPs
ECPsECPs
ECPsECPs
Engineering change proposals (ECPs) and TTPs responding to TRs require significant staff resources to track and manage
Tracking and Managing Trouble ReportsTracking and Managing Trouble Reports
September 24, 2003 21
System System RequirementsRequirements
System Functions
System Software
System HardwareTactics / Techniques /
Procedures (TTPs)TTPs
Trouble Reports (TRs)
TRsTRs
TRsTRs
TRsTRs
TRs
Engineering Change Proposals (ECPs)
ECPs
TTPsTTPs
TTPs
ECPsECPs
ECPsECPs
Link ECPs and TTPs to related system design data and directly track resolution of TRs
Tracking and Managing Trouble ReportsTracking and Managing Trouble Reports
September 24, 2003 22
TransitionTransition
� Required for– Continued Schema Development– Maintenance When Integrated Models Change– Tailoring Assistance for Specific Program Usage
More Complex than Single Point of Control
Multiple Funding Sources; Continued Buy-in
Something In-between
Lose Industry Buy-in; Not in Keeping with Current Business Practice
Central ControlFully-funded Government Program
Loses Relevance for DoD
Entirely Commercial Funding
Volunteer Effort under GEIA
DisadvantagesAdvantagesOptions
September 24, 2003 23
PhysicalSize, Weight, Power, Heat...
Info ProcessingData I/O, Memory, Proc. speed ...
DependabilityMTBF, MTTR, A0 …
CostUnit Cost, Repair Cost …
Simplified JTRS Object ExampleSimplified JTRS Object Example
Joint Tactical Radio Object
Hardware Architecture Design
Thermal Analysis
Network Design
Concept Exploration &
Definitio n
Demonst ration /
Validatio n
Engineering Manufact uring
& Development
Production &
Deplo yment
Upgrade
and Replace
nt
PH ASE
1000100
Speed
Jan Apr Jul Oct
Performance Analysis
Cost AnalysisPhoto
IdentityName, Version, Created by…
September 24, 2003 24
Sharing Data Across ProgramsSharing Data Across ProgramsJoint Tactical Radio System
Info Repository
DD(X) Info Repository
PhysicalSize, Weight, Power, Heat...
Info ProcessingData I/O, Memory, Proc. speed ...
DependabilityMTBF, MTTR, A0 …
CostUnit Cost, Repair Cost …
Photo
IdentityName, Version, Created by…
PhysicalSize, Weight, Power, Heat...
Info ProcessingData I/O, Memory, Proc. speed ...
DependabilityMTBF, MTTR, A0 …
CostUnit Cost, Repair Cost …
Photo
IdentityName, Version, Created by…
PhysicalSize, Weight, Power, Heat...
Info ProcessingData I/O, Memory, Proc. speed ...
DependabilityMTBF, MTTR, A0 …
CostUnit Cost, Repair Cost …
Photo
IdentityName, Version, Created by…
Future Combat SystemInfo Repository
Consistent Formats Enable Cross-Program, Context-Appropriate SharingConsistent Formats Enable Cross-Program, Context-Appropriate Sharing
September 24, 2003 25
Growing Industry CommitmentGrowing Industry Commitment
� EIA-927 “Common Data Schema for Complex Systems” Development Approved January 2002
� GEIA Taking Active Role in Evangelization Effort– Established Oversight, Technical Committees
» Industry Primes, High-level OSD, Service Membership» 12 Organizations Provide Membership (e.g., LMCO, NG,
Raytheon, JHU/APL, …)» Technical Group for Work Review
– High-Level OSD Briefings Conducted� EIA-927 Standard Publication Projected 4Q04
September 24, 2003 26
Next StepsNext Steps� GEIA sponsored a meeting with ADUSD(LP&P)
proponent on 1 May 03 to discuss transition� Multi-faceted approach was proposed:
– Establish and promote EIA-927 as the DoD endorsed standard for product data
– Establish policy that directs all new programs to have product data compliant with the EIA-927 standard
– Fund initial implementations of EIA-927 in Service acquisition programs
– Jointly host a conference to focus Service and Industry efforts on EIA-927 as the DoD solution to product data interoperability
� ADUSD(LP&P) endorsed approach; GEIA is coordinating follow-on letter
� Also exploring use of schema within new/emerging capabilities, such as Army ePDM infrastructure