october 23, 2003 smmoa supply, maintenance, monitoring open architecture tosa team presented by...
TRANSCRIPT
October 23, 2003October 23, 2003
SMMOASMMOASupply, Maintenance,Supply, Maintenance,
MonitoringMonitoringOpen ArchitectureOpen Architecture
TOSA Team
Presented byDavid Perrussel
SMMOA Project Lead
2
Open Systems Architecture
The Open System Architecture (OSA) concept was developed by
the computing industry in the 1970’s and 1980s to help
compatability among vendors, thus reduce costs. Involves defining an architecture and “open standards” for
interfaces within that architecture Multiple companies are then free to build (innovative) products that
“plug into” open standard Widely used throughout Information Technology (IT) Industry
Examples of OSA Interfaces “Plug and Play” Storage Devices for common interface
3
Performance Spec: Performance Envelope Human Factors Power consumption ILS docs
Industry can choose any implementation (including proprietary) to meet OSA
interface
Open Systems Approach
IMPLEMENTATION B
IMPLEMENTATION A
OSA Interfaces Physical (Geometric & Tolerances) Electrical Air interfaces Cooling interfaces Control Sensors, Monitoring
interfaces Piping connections Human Factors Survivability/Vulnerability:
shock/vibration/EMI/EMC CG / VCG
PerformanceSpecification
OSA Interfaces
Acquisitionof System + =
4
DoD/Navy Unique Need
Platforms with increasingly long lifecycles (30+ years)
Increased used of commercial technologies
Short lifecycles of COTS (<7 years)
– Often obsolete by time fielded
6+ Years ofTechnology
Advancement
41+ Years of Technology Advancement
OSA facilitates exploitation of commercial market &
technology advances throughout ship
development & operation phases
Ship Life Cycle
Equipment Selection/
Design FreezeEquipment Installation
Design and Construction
Increased market “exposure” & small market strength Increased emphasis on Technology Refresh &
Insertion Response to COTS / Market changes
Response to Mission changes
Response to New Technologies (evolutionary and disruptive)OSA is a large component of the
answer
5
Flexibility Allows access to multiple vendors at system and component level
Competition during acquisition and over lifecycle Avoid sole source constraints
Upgradability Allows new technology to be inserted cost effectively Does not limit industry’s ability to innovate
Scaleability For future upgrades
Affordability Reduces procurement costs Reduces production costs Reduces construction costs Reduces O&S costs
Projected Cost Savings based on studies to date:
Acquisition : 20 - 25%O&S : 20 - 35%
Open System Benefits
6
21
Open Zones
Ordnance
Machinery Equipment
C4IOrganic Off board Vehicles (OOV)
Open Distributed Systems
Topside
Other
HVAC
+Monitoring
IPS
+Maintenance
Open Modules
+Supply
Various
TOSA Vision: The Adaptable Ship
TSCE Etc.
7
Need for Supply, Maintenance and Monitoring Open
Architecture
Increased operational readiness – particularly when optimal manning is specified (e.g.DDX).
Use Open Standards for better Interoperability and technology upgrade & refresh.
Optimal efficiency for shipboard maintenance and supply functions Condition assessment Condition-Based maintenance Automation of supply functions (such
as inventory and parts ordering)
Solutions must be acceptable to both system integrators and component manufacturers for new ships and compatible with on going ISEA programs.
8
SMMOA Vision
CM
SUPPLY
Personnel
Tech Data Library
Fleet Support
Vendors
ISEAs /FTSCs
Tech Infusion
Maintenance Assist
Tech Data UpdateTraining Assist
JIT Parts
Accurate CM Data
Maintenance
Supply
Config DataMgr
Personnel
CBMMonitored Data
OperationalReadiness
Engineering
DamageControl
HumanResources
ConfigurationManagement
Supply Maintain
Monitor
Benefits of open information exchange
9
SMMOA Elements
TOSA has established the following elements as part of the SMMOA Focus Area Team:
Open Sensor/Network Interface (OSNI) Development
Open Material Condition Information (OMCI) Development [For Condition Based Maintenance]
Open Logistics Support Interface (OLSI) Development
10
Open Sensor/NetworkOpen Sensor/NetworkInterface (OSNI) DevelopmentInterface (OSNI) Development
11
Automation andOpen Architecture
Reduced/optimized manning requirement for future ship classes drives for increased automation.
Increased automation will require a significantly increased number of transducers installed aboard ship Possibility of 25,000 (or more) transducers on DD(x) class
of ships Levies unique requirements for future Naval platforms
Open architecture approach will be key to achieving vision of highly automated ship in a cost effective manner Reduced installation costs Allow for Technology Insertion / Upgrade Allow for streamlined Maintenance & Supply
12
OSNI Goals & Objectives
Explore various sensor-bus standards & interfaces
Perform Risk Mitigation on candidate sensor-bus standards
Help establish a set of Navy Open Architecture sensor-bus standards & interfaces
Work with Standards Bodies to develop Open Sensor-Bus Standards for both Industry and Navy
Promulgate the use of sensor-bus standards for Navy systems to shipyards, systems integrators and vendors
13
Open Sensors/Networks and Total Ship Computing (TSCE)
Sensors
Total ShipComputing
Network
Combat System
LocalProcessing
C4I
OtherSystems
Distributed Computing
HM&E
Sensors
Sensors
Total ShipComputingTotal ShipComputingTotal ShipComputing
Combat System
LocalProcessing
C4I
OtherSystems
Distributed Computing
HM&E
OtherSystems
OtherSystems
Sensors
FutureSystems
Network
NetworkNetwork
Open Systems Architecture Approach for TSCSimilar approach for sensors/sensor networks
14
The IEEE 1451 sensor-bus network family attempts to address interoperability issues
1451 family allows for interoperability among different network AND transducer manufacturers
1451 family allows for plug & play of transducers and network
1451 family allows for easy upgrade Development of the 1451 family is evolving
OSNI Initial Focus onIEEE 1451 Family
We have chosen our initial focus on the IEEE 1451 family:
OSNI chose to focus on IEEE 1451 as a candidateopen interface sensor/network standard
15
IEEE 1451 Standards Family
Nex
t Gen
Net
wor
k
Net
wor
k
Fut
ure
Gen
Net
wor
k
Var
ious
Net
wor
ks/ P
roto
cols
Interface
Open Interface
Nex
t Gen
Net
wor
k
Net
wor
k
Fut
ure
Gen
Net
wor
k
Var
ious
Net
wor
ks/ P
roto
cols
Network Interface Sensor
Open Interface
Network Capable
Application Processor
(NCAP)
Smart Transducer Interface Module (STIM)
Transducer Bus
Interface Module (TBIM)
MixedMode
Interface (MMI)
1451.1
1451.2
1451.3
1451.4
SmartSensor
Vendor C
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor C
SmartSensor
Vendor B
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor B
DumbSensor
Vendor A
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor C
SmartSensor
Vendor B
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor B
DumbSensor
Vendor A
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor C
SmartSensor
Vendor B
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor B
DumbSensor
Vendor A
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor C
SmartSensor
Vendor B
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor B
DumbSensor
Vendor A
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor C
SmartSensor
Vendor B
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor B
DumbSensor
Vendor A
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor C
SmartSensor
Vendor B
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor B
DumbSensor
Vendor A
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor C
SmartSensor
Vendor B
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor B
DumbSensor
Vendor A
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor C
SmartSensor
Vendor B
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor B
DumbSensor
Vendor A
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor C
SmartSensor
Vendor B
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor B
DumbSensor
Vendor A
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor C
SmartSensor
Vendor B
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor B
DumbSensor
Vendor A
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor C
SmartSensor
Vendor B
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor B
DumbSensor
Vendor A
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor C
SmartSensor
Vendor B
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor B
DumbSensor
Vendor A
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor C
SmartSensor
Vendor B
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor B
DumbSensor
Vendor A
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor C
SmartSensor
Vendor B
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor B
DumbSensor
Vendor A
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor C
SmartSensor
Vendor B
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor B
DumbSensor
Vendor A
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor C
SmartSensor
Vendor B
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor B
DumbSensor
Vendor A
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor C
SmartSensor
Vendor B
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor B
DumbSensor
Vendor A
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor C
SmartSensor
Vendor B
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor B
DumbSensor
Vendor A
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor C
SmartSensor
Vendor B
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor B
DumbSensor
Vendor A
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor C
SmartSensor
Vendor B
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor B
DumbSensor
Vendor A
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor C
SmartSensor
Vendor B
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor B
DumbSensor
Vendor A
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor C
SmartSensor
Vendor B
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor B
DumbSensor
Vendor A
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor C
SmartSensor
Vendor B
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor B
DumbSensor
Vendor A
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor C
SmartSensor
Vendor B
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor B
DumbSensor
Vendor A
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor C
SmartSensor
Vendor B
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor B
DumbSensor
Vendor A
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor C
SmartSensor
Vendor B
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor B
DumbSensor
Vendor A
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor C
SmartSensor
Vendor B
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor B
DumbSensor
Vendor A
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor C
SmartSensor
Vendor B
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor B
DumbSensor
Vendor A
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor C
SmartSensor
Vendor B
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor B
DumbSensor
Vendor A
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor C
SmartSensor
Vendor B
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor B
DumbSensor
Vendor A
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor C
SmartSensor
Vendor B
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor B
DumbSensor
Vendor A
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor C
SmartSensor
Vendor B
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor B
DumbSensor
Vendor A
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
SmartSensor
Vendor A
Next Generation
SmartSensor
Vendor C
SmartSensor
Vendor C
SmartSensor
Vendor B
SmartSensor
Vendor B
DumbSensor
Vendor C
DumbSensor
Vendor C
DumbSensor
Vendor B
DumbSensor
Vendor B
DumbSensor
Vendor A
DumbSensor
Vendor A
Next
Generation
SmartSensor
Vendor A
SmartSensor
Vendor A
Next Generation
1451.5
1451.5 is Wireless
16
DistributedSensor-bus Network
Work Stations
Ship wide LAN(s)
Compartments & Application Zones
Distributed Processing
Module
TransducersDistributedProcessing Modules
17
ModularSensor-bus Interfaces
Remote Station
T
Bus Interface
T
Bus Interface
T
Bus Interface
T
Bus Interface
Work Station
ReplaceableTransducers
Command andControl Network
Interfaces installedwhen ship built
18
Initial Risk Mitigation
Development of an Open Sensor/Network Interface Demonstrator IEEE 1451.3 (multi-drop bus) chosen for testing
Used an early draft of the standard (2001)
Examine and explore Navy needs and requirements Tested a concept of additional backup features added
to help address Navy specific issues
Help demonstrate the use of plug-and-play for sensor-bus networks
Adapted existing COTS parts and systems to simulate IEEE 1451.3 network Pressure & Temperature sensors
Encoder & Stepper motor actuators
19
OSNI Demonstrator
Open Material Condition Information
(OMCI)
21
OMCI Requirements
Need to reduce/optimize manning for DDX Need to reduce maintenance man-hours Requires more Sophisticated and Extensive
Maintenance Applications There are multiple Navy and commercial
maintenance information interfaces Maintenance developments including future
Condition Based Maintenance (CBM) applications require: Access to expanding commercial developments. Interoperability between commercial CBM systems and
maintenance information systems. A Navy/commercial standard interface for maintenance
applications.An Open Material Condition Information
Standard is Required
22
SENSOR
NCAP
CBM Processor
Software
Database
Data Acquisition
Board
ContinuousFluctuating value(500 +/- x%)
Stable values
Updated at preset
intervals
Value (500)
Value (700)
Value (300)
Processed value
or
Discrete signal
ID ASW53001
Other
Signals
(500)
Permanent info
Sensor IDs, etc.
Software samples
value(s) at preset
intervals
Alarm
Add Time Stamp
TriggerRule?
AutomatedWork order and supply
requestY
LAN
Material Condition Information Data Flow
Software logs & time stamps values at preset intervals
SENSOR
ID ASW53002 Discrete value
(low or good)
(500)
(good) (good)
End
23
Open Material Condition Information
CommonDatabase
Common Database
On-Ship Off Ship
Comm
on Data
Schem
a
Comm
on Data
Schema
Common Data Schema
Common Data Schema
A common database information schema for all material condition information, NOT just CBM data.
Integration of CBM and Information SystemsInformation Interoperability
24
Military Market Surveillance/Technology Projection
Working Groups Gas Turbine Working Group Maintenance Engineering Technology
Team (SEA04M) Joint Wireless Working Group
(SPAWAR)
R&D Programs Reduce Ships crew through Virtual
Presence (RSVP) SMARTSHIP Initiatives Submarine Towed Arrays Submarine Maintenance Monitoring
Program Etc.
Other CBM Data Activities Army Diagnostic Improvement
Program AAAV JAHUMS OSA-CBM MIMOSA Etc.
Navy Development Efforts Total Ship Monitoring (TSM) Battle Group Automated
Maintenance Environment (BG-AME)
Enterprise Resource Planning (ERP)
DDX Etc.
25
MIMOSA
Maintenance Information Management Open Systems Alliance
Consortium of 50+ system integration providers, component vendors and end-users
MIMOSA addressing the interoperability deficiency in information integration and exchange.
Developing open specifications for all material condition information, not just CBM
MIMOSA goal to become an ISO Standard
SMMOA Selected MIMOSA as a Candidate Navy OMCI Standard
26
MIMOSA Database Structure
Fixed Reference Data
Engineering UnitsTransducer TypesData Source typesMeasurement Location Types
Navy Specific Reference DataSegments - ESWBSAssets – EC/LAPL/APL
Ship Specific Reference DataAssets on Segments – CMDM-OAMeasurement Locations – ICAS CDS, VTAGS, Thermographic Routes, Etc.
Data ValuesPressuresTemperaturesVibration Signatures
27
OMCI ServerDemonstrator
Predict/DLI Server
Initial Agreement
ICAS ServerPending Agreement
TOSA MIMOSA
Demo Server
PS/ARL Lab ServerInitial Agreement
OSA-CBM ServerInitial Agreement
CRIS
CRIS CRIS
CRIS
Goal: Demonstrate Information Interoperability
28
Open Logistics Support Interface
(OLSI)
3
Transportation ModesLand
•Rail
•Trucks/trailers
Sea
•Ships
•Barges
•Craft
Air
•Fixed Wing
•Helicopter
•Tilt Rotor
29
New Support Paradigm
Legacy MILSPEC Support System
COTS Acquisition (Mid 90’s)
“TOSA Enabled”
Acquisition (Year 2010)
Navy Design
Navy CM Control
Full Data
Disclosure
Stable Technology
Stable Supplier
Support Bit &Piece
Maintenance
Organic Support
Performance Based
Contracting
Multiple Suppliers
Rapid Tech Insertion
TOSA Interface Specs
Condition Based
Maintenance
Global Information Grid
Vendor Design/CM Control
Limited Data Disclosure
Limited Supplier Stability
Rapid Technology Change
Modular MaintenanceOrganic/Contractor mix
30
C2C2LOGISTICSLOGISTICSOPERATIONSOPERATIONS
INTELLIGENCEINTELLIGENCE
IntegratedReal-TimeSituationalAwareness
6
JTAV GTNJOPES
WPS SARSS
Network CentricLogistics
Environment
VADM Holder VADM Holder Director of Logistics Director of Logistics
The Joint StaffThe Joint Staff
OLSI Vision
31
Logistics Requirements
Reduced Manning Necessary to automate Logistics
Ability to see assets while in storage or transit Streamlined Acquisition & Tracking Management
Increase Operational Readiness Accountability for necessary items Ability to obtain items from multiple sources
Utilize Open Standards Increased Life Cycle Support Reduced Total Ownership Costs Interoperability between different systems
32
OLSI Goals
• Integrate supply support with material condition monitoring and maintenance data bases to enable exchange of data and interoperability
• Advance the use of open standards for critical interfaces
• Enhance asset visibility to reduce cost and enhance readiness
• Automate supply chain management through use of Material Handling Equipment and Automatic Identification technologies
Leverage industrial and government best practices, new technology, and emerging standards
33
Market Surveillance& Technology Projection
Universal Identification (UID) part marking Universal Identification Code Smart stores/smart shelves Radio Frequency Identification (RFID) Ultra Wide Band (UWB) Serial Number Tracking Data Matrix Symbology Contact Memory Buttons AIT networks Material handling equipment
January 3, 2003 87
Description
Sponsor/Mfg: Hyster
Technology Readiness:Characteristics:
TRL Today = 9Funded = N/ATRL 8 = N/A
Container lifting systems
Reach StackersSuppliers from http://www.hyster.com/dealers/
2002 2003 2004 2005 2006 2007 2008 2009 2010
TRL TodayTRL FundedYear Technology/System will reach TRL 8
TRL = 9
2002 2003 2004 2005 2006 2007 2008 2009 2010
TRL TodayTRL FundedYear Technology/System will reach TRL 8
TRL = 9
Container lifting system stacks containers onto vehicles and ground.
34
OLSI’s Use ofOpen Standards
Review and evaluate evolving standards for AIT, inventory management, MHE, storage & transportation
Become involved in standards development Better interoperability between systems Insure various Logistics systems communicate
with each other From hand-held bar-code readers & CMBs to databases to
communications systems
35
Integrated Supply, Maintenance, and Monitoring Workflow
Detect P
Monitoring
Data collection (OSNI)
Trend analysis (CBM, OSNI)
Identify material degradation or pm requirement (OMCI)
Maintenance planning
Estimate repair resources (OMCI)
Determine sources of supply (OMCI)
Set priority (OMCI)
Ship Shore facilities
Supply chain management
Acquire parts (OLSI)
Ship/transport parts (OLSI)
Track Parts (OLSI)
Maintenance execution
Part installation & checkout (OMCI)
Supply chain management
Initiate requisition (OLSI)
Process & approve requisition (OLSI)
36
ILS ScenarioMajor Unplanned
Maintenance
VENDOR A
VENDOR B
VENDOR C
ENCODED
CONDITIONED BASEDMAINTENANCE
SURVEILLANCE TEAM
Global Readiness Center
IN P
LACE
CONTRACTS
CBMONBOAR
D
RAPID RESPONSE
Rapid Response
Team
37
Conclusion
SMMOA is a Prime Concern for Navy’s future Future Manning requires better use of technology for
monitoring, maintenance and supply
Open Standards should be developed/used for interfaces
Need risk mitigation on candidate Open Standards
Need to reach common Agreements & Strategies
Consensus set of Standards for SMMOA
Open Sensors, Databases and Supply & Logistics
management
Promulgate these standards to Naval and Industry
Systems Integration Teams
38
Contact Information
SMMOA Contacts
David PerrusselSMMOA Lead/OSNI Lead(540) [email protected].
mil
Win RoyceOMCI Lead(301) [email protected].
mil
Sam JudgeOLSI Lead(301) [email protected].
mil
Jack AbbottTOSA IPT Lead/BlueSky
DDX(301) [email protected].
mil
39
Backup
40
TOSA Industry-Navy Integrated Product Team
Customers
(Defense)
Industry
Shipbuilders
CommercialSystem Vendors
System Integrators
Marine
Engineering
Acquisition Programs
Logistics
Community
SteeringCommitte
e
Design
Community
R&D
Community
41
A/V-8B Avionics
Open Systems
OSA Examples
Mil-Std 200 ton A/C Plant
Advanced Food ServiceShip/UAV Interface
Closed Systems
UYK-44
UYQ-70 Joint Strike Fighter
Direct Drive Propulsion
Ship Habitability Modules
Chilled Water Module
42
Background/Initial Research
• Began with a comprehensive market surveillance of CBM programs and projects– Identified key players and key programs in the CBM
arena– Identified standards bodies and standards
development work with potential TOSA implications
• Established contacts/working relationships with key CBM programs, projects, and companies– Commercial companies– Navy R&D projects– Other military service programs– Universities involved in CBM
43
OMCI Work Flow
CollectData
Organizedata perschema
Establishclient/server
interoperability
Transmit/receive
data
Perform CBM on
data
Analyze faults
Identify critical
systems/conditions
Project life/failure probability
Modify operations/
Initiate maintenance
action/Issue work
order
Sensor Data
(OSNI)
To OLSI
Obtain resources,
order parts, etc.
44
MIMOSA Database Structure
Segments
Propulsion PlantPropulsion Units
Propulsion Gas Turbines
Propulsion Gas Turbines, Main
Propulsion Gas Turbines, Support Systems
GTM1A
GTM1B
GT Start Air
GT LOF&S
Assets
GELM2500
Model112Serial 76132910
AssetOn Segment
Measurement Locations
Compressor Discharge PressureCooling Air Outlet Temperature
45
MIMOSA Implementation Issues
MIMOSA is the gatekeeper for the fixed reference tables
We need a gatekeeper for the Navy specific reference tables
MIMOSA DB’s ship and shore have to be maintained as ship configuration changes
Application software is needed to simplify setup of the MIMOSA database
Hooking up real-time data acquisition to demo server 1451 demonstrator PS ARL Predict DLI ICAS
46
MIMOSA Interfaces
MIMOSA defines interfaces for the following “technologies” Trend – static values (pressure or temperature and alarm
values) Dynamic – spectral values (vibration, ultrasonic, electric
current) Sample – fluid tests such as oil analysis or gas tests BLOB (binary large objects) – graphic files (thermographic
or digital camera images) Diagnostic – text values (diagnostics and
recommendations) Reliability – FMEA information Registry – asset management information Work – work management information
MIMOSA Compliance is determined on a technology by technology basis Not all applications use all “technologies “