Sharing Data Across the - Pennant International Group PLC · Sharing Data Across the ......
15
OmegaPS and Analyzer Users Group Meeting 2010 Sharing Data Across the “Great Divide” Pat Read Manager- Consulting Services Ottawa, Canada
Transcript of Sharing Data Across the - Pennant International Group PLC · Sharing Data Across the ......
OmegaPS and Analyzer Users Group Meeting 2010
Sharing Data Across the
“Great Divide”
Pat Read
Manager- Consulting Services
Ottawa, Canada
The Challenge
• As Defense Departments (like DND) and their primary
Industries move into
– Lifelong “Acquire & Support” Relationships
– Step into business models built on enterprise-wide (and beyond)
information toolsets
– That rely on shared information on enterprise subsets of
industry “products” forming military “fleets” of equipment
being integrated and used within defense forces
– Information that is multi-sourced from defense departments,
prime and sub- contractors
• How do we share the RIGHT NEEDED INFO as
accurately, seamlessly and effortlessly as possible
for DECADES
Some Thoughts • Based on our experience (decades) with
– DND’s enterprise solution for engineering & maintenance
(SAP® centred MASIS, now DRMIS)
– Evolving International Standards for sharing logistics
analysis data
• MIL-STD 1388/DEF-STAN 00-60
• ISO 10303STEP AP-239 PLCS; GEIA STD 927/0007 Log Product
Data; & ASD S-1000D/2000M/3000L series.
– Canadian DND process models for Supportability and
Equipment Management
– New DND Electronic Information Environment (EIE)
concepts to support In-Service Support Contracting (ISSC)
and Performance-Based Accountability (PBA) concepts
Some Shifts in Shared
Engineering & Support Datasets
• Source Product Design Data
– Paper drawings CAD/CAM & PDM databases
– Linkages to Config Mgt and ERP structure sets
• LSAR Datasets
– Web-based building of source LSAR datasets by DND, prime &
subs
– Linkages to DND/NATO catalogues, IETMs, OB Diagnostics,
CBT, and ERP support master datasets
• Feedback and Usage Info
– Into ERPs and OBD Health Usage Monitoring Systems (HUMS)
vice paper reports from techs
So How do We
JOIN Subsets of Two “Enterprise” Information
Sets?? • WE HAVE:
– Two Enterprises (Industry & Defense Depts), BOTH with a need
to link to
• EACH OTHER in a specific Equipment System subset
• And MANY OTHERS for the same/different Equipment Systems
– DND100,000s of suppliers
– Boeing many DNDs and commercial customers
• WE NEED TO
– Keep the two enterprise worlds working in their toolsets
– Open up Collaboration by allowing access of each into the
other’s “world”
– Establish Data Exchanges to pass information to each other.
• Mappings and Transformations
Contractor-Controlled INTRANET
(Proprietary)Contractor
Enterprise & Legacy IT/Files
DND-Controlled INTRANET
(DIN)DND
Enterprise & Legacy IT/Files
CollaborationEnvironment(unique to
each ES)
Electronic Data Exchange (EDE) via INTERNET(Common DEX Standards ,but content unique to each ES )
CAD/CAM
PDM
LSAR
PM FIN
Inv Mgt Maint Mgt
Publishing
DRMIS (MASIS FMAS & CFSS?)
ESDs
CGCS
RDIMS
PM
TDMS?
APDS
NDID/EIDDB/EMAP
CM
The DND Approach –
Enterprise Information Environment (EIE)
EIE includes FOUR Areas
• Two pre-existing separate INTRANETS – the Contractor’s and
DND’s that include a number of information systems and data
repositories required for the day-to-day business of each.
– These are largely pre-existing well before the PMO/EMT-specific need to
create linkage for their ES arises, even more so as DND buys
COTS/MOTS solutions.
• Two new EIE elements to meet the new requirements to share
information – that must be established for each PMO/EMT need:
– A collaboration environment (CE) to access and view each others data
– An electronic data exchange (EDE) to exchange data for use in each
others systems
The Collaboration Environment
• To view and access (perhaps even enter) data within each
others Intranet
• Two approaches
– VPN type access into an Intranet with other side users provided
controlled access. Examples:
• DND Contractor: PMO SE/ILS staff with read/comment roles into
contractor CAD/PDM/LSAR applications from contractor or internet
workstations
• Contractor DND: Contractor EMT members with DND laptop/ sep
network with DWAN access to DRMIS SAP, Outlook, EMT file
repositories
– FTP or trusted INTRANET website for “parking” reports and info
of mutual interest. Examples:
• PMO Internet Websites with access by approved contractors.
The Electronic Data Exchange (EDE)
• Provides for secure, efficient, two-way flow of information
between the Contractor and DND, by using the Internet
and internationally-accepted or DND common data
exchange (DEX) standards.
• Three primary transfer sets of DEXs
– REUSABLE MASTER DATA to enable engineering and support
activities in either enterprise.
Example: Maintenance Procedure Information DRMIS SAP
GMTLs
– TRANSACTION DATA on engineering and support activities in
either enterprise.
Example: DRMIS SAP Maintenance notification/order data
Contractor
– HEALTH AND USAGE MONITORING SYSTEM (HUMS)
DATA. Example: ONSTAR & OBD data to OEM for analysis
HUMS Data Flows – a MoDUK View
The basic model
Data Analysis
Platform
System
Status
Condition
Status
Configuration
Status
Data Acquisition
Platform
System
Data
Transfer
Platform
Systems
Data Sensing
CollectStore
On-board
processing
Configuration
Management
Asset
Management
Condition
Based
Maintenance
Availability
Index
OperationalRequirement (J3, J4..)
Maintenance, Supply,OEM ……
Information Exploitation
Operator(s)
Crew
Automotive
Communications
ECM
RWSPower
SA
Stakeholders
Extracted
from DEF-
STAN 25-24
Issue 2
Systems
Information
Exploitation
(with HUMS)
for LAND
Systems
Where is DND Now on EIE?
• Seen as backbone of ISSC & PBA Concepts
• PMO in ADM(IM) (linked to Defence Info
Service Broker – DISB) with mainly user pay by
ADM(Mat) Projects
– Requirements from ADM(Mat)
– Synch with DRMIS (was MASIS)
– Airforce leading ACP (C-130J) & MHLH
– Army considering (TAPV & CCV, maybe MSVS)
How is It Being Created??
• Scalable Infrastructure; Common but Tailored Design
– System Requirements Spec for DND end being written
– tailored mapping by transaction after contract award to specific
Contractor Intranet and DND project/EMT need.
• Some Pre-existing CE (VPN laptops, etc) so focus on EDE
• 24 primary transaction sets defined, tailored set being built
with L-M on C130J; Boeing to follow on MHLH.
MOST REUSEABLE for other projects
• CCV & TAPV intend to include in their RFP packages and
support concepts and may fund next step development
Challenges??
• Intellectual Property Issues
• DND Security Concerns
• How Common can Common be?
Mitigations?? • Industry already working electronic with subs
• New LSAR data standards with XML/UML tagged data
• OmegaPS-DND with pre-defined logic to
– accept commercial LSAR exports in old/new standards
– load many DND IS including CGCM & EIDDB,
DRMIS SAP
– export integrated DND/Contractor datasets
• MASIS Data Protocol Templates
