Learning from the Aerospace Industry Interoperability & Systems ...
AAMI-FDA Interoperability Summit
Learning from the Aerospace Industry Interoperability & Systems Integration
Interoperable Solutions through Integration New Mission (Business) Objectives Campaign
Known
Platforms
People Processes Support Cost Maintenance
Unknown
Systems Integration
(Systems Engineering Process)
Known
Equipment
Ownership Implications
Concepts of Operation
Integration Ready Products
Available Technology (Options) Copyright (c) 2012 Lockheed Martin Corporation Author: Jamie Bishop ([email protected])
AAMI-FDA Interoperability Summit
Learning from the Aerospace Industry Interoperability & Systems Integration
Integration Ready Products for Interoperability Integratable Devices
Common Interfaces
Functional Qualifications
• Standalone (No Servers) • Bus Communications • Robust Built In Test (Ethernet, 1553) • Role Specific Design • Std Behavioral Compliance • Externally Controllable • Point toasPoint Digital Data Aerospace Products are Designed Standalone, Interoperable “Building Blocks” • Reliability Predictions (ARINC 429, RS-232) • Common Form Factors • Environmental Testing • Discrete Electrical Signals • Human Factor Designs (Digital I/O, Analog Signals) • Sub Assemblies are Modules • Interface Control Documents • Partitioned Operating Sys (Not Interface Data Specifications)
L3 UHF SATCOM Modem • Controlled using: • Remote Control Unit • RS-232, RS-422/423 • 1553 serial bus • UHF MIL-STDs: -181,-182,-183
Rockwell Cockpit Display Unit • Dual Ethernet, MIL-STD-1553B • ARINC 429: 12 in, 6 out • RS-232: 2 input, 2 output • Discrete I/O: 19 input, 8 output • ARINC 739 Compliant
Copyright (c) 2012 Lockheed Martin Corporation Author: Jamie Bishop ([email protected])
Northrop Grumman Mode-S Trans • STANAG 4193 specifications • ARINC-429 or 1553B • > 4,000 hours MTBF • 99% internal fault detection
AAMI-FDA Interoperability Summit
Learning from the Aerospace Industry Interoperability & Systems Integration
Recommendations for HC Interoperability … Healthcare Organization focus on Operational Requirements • • • •
Define common interfaces and protocols (e.g. RS-232, Ethernet, HTTP, SSL) Consider device interoperability use cases: (1) data push; (2) data query; (3) remote control Define a set of security measures for bus technologies Avoid specifying implementation details
Device Industry focus on Standalone, Interoperable Products • • •
Role specific, standalone, modular, and service oriented (without the need for server software) Rugged, human factors designs for usability Network enabled interface with identical features and controls as human interface
Leave System Decisions to the System Integration • • • •
Wired vs. wireless Redundancy in communications network Enterprise security and impacts of network outages Architectural growth and system roadmaps
Use Modular Integration Techniques • •
Follow Systems Engineering & Systems Integration design processes Recognize that “need is the mother of invention” and modular integration techniques help define “need” Copyright (c) 2012 Lockheed Martin Corporation Author: Jamie Bishop ([email protected])
AAMI-FDA Interoperability Summit
Learning from the Aerospace Industry Interoperability & Systems Integration
Integrate with “Building Blocks”
Incremental Technology Advancement
Basic Interoperability Specs Invention
Technology Innovation
Custom Solutions Copyright (c) 2012 Lockheed Martin Corporation Author: Jamie Bishop ([email protected])
AAMI-FDA Interoperability Summit
Learning from the Aerospace Industry Interoperability & Systems Integration
Thank You
Copyright (c) 2012 Lockheed Martin Corporation Author: Jamie Bishop ([email protected])
Learning from the Aerospace Industry Interoperability & Systems Integration
Interoperable Solutions through Integration New Mission (Business) Objectives Campaign
Known
Platforms
People Processes Support Cost Maintenance
Unknown
Systems Integration
(Systems Engineering Process)
Known
Equipment
Ownership Implications
Concepts of Operation
Integration Ready Products
Available Technology (Options) Copyright (c) 2012 Lockheed Martin Corporation Author: Jamie Bishop ([email protected])
AAMI-FDA Interoperability Summit
Learning from the Aerospace Industry Interoperability & Systems Integration
Integration Ready Products for Interoperability Integratable Devices
Common Interfaces
Functional Qualifications
• Standalone (No Servers) • Bus Communications • Robust Built In Test (Ethernet, 1553) • Role Specific Design • Std Behavioral Compliance • Externally Controllable • Point toasPoint Digital Data Aerospace Products are Designed Standalone, Interoperable “Building Blocks” • Reliability Predictions (ARINC 429, RS-232) • Common Form Factors • Environmental Testing • Discrete Electrical Signals • Human Factor Designs (Digital I/O, Analog Signals) • Sub Assemblies are Modules • Interface Control Documents • Partitioned Operating Sys (Not Interface Data Specifications)
L3 UHF SATCOM Modem • Controlled using: • Remote Control Unit • RS-232, RS-422/423 • 1553 serial bus • UHF MIL-STDs: -181,-182,-183
Rockwell Cockpit Display Unit • Dual Ethernet, MIL-STD-1553B • ARINC 429: 12 in, 6 out • RS-232: 2 input, 2 output • Discrete I/O: 19 input, 8 output • ARINC 739 Compliant
Copyright (c) 2012 Lockheed Martin Corporation Author: Jamie Bishop ([email protected])
Northrop Grumman Mode-S Trans • STANAG 4193 specifications • ARINC-429 or 1553B • > 4,000 hours MTBF • 99% internal fault detection
AAMI-FDA Interoperability Summit
Learning from the Aerospace Industry Interoperability & Systems Integration
Recommendations for HC Interoperability … Healthcare Organization focus on Operational Requirements • • • •
Define common interfaces and protocols (e.g. RS-232, Ethernet, HTTP, SSL) Consider device interoperability use cases: (1) data push; (2) data query; (3) remote control Define a set of security measures for bus technologies Avoid specifying implementation details
Device Industry focus on Standalone, Interoperable Products • • •
Role specific, standalone, modular, and service oriented (without the need for server software) Rugged, human factors designs for usability Network enabled interface with identical features and controls as human interface
Leave System Decisions to the System Integration • • • •
Wired vs. wireless Redundancy in communications network Enterprise security and impacts of network outages Architectural growth and system roadmaps
Use Modular Integration Techniques • •
Follow Systems Engineering & Systems Integration design processes Recognize that “need is the mother of invention” and modular integration techniques help define “need” Copyright (c) 2012 Lockheed Martin Corporation Author: Jamie Bishop ([email protected])
AAMI-FDA Interoperability Summit
Learning from the Aerospace Industry Interoperability & Systems Integration
Integrate with “Building Blocks”
Incremental Technology Advancement
Basic Interoperability Specs Invention
Technology Innovation
Custom Solutions Copyright (c) 2012 Lockheed Martin Corporation Author: Jamie Bishop ([email protected])
AAMI-FDA Interoperability Summit
Learning from the Aerospace Industry Interoperability & Systems Integration
Thank You
Copyright (c) 2012 Lockheed Martin Corporation Author: Jamie Bishop ([email protected])
