materiel readiness enabled through “sense and respond” optimized logistics increasing momentum...
TRANSCRIPT
Materiel Readiness Enabled Through“Sense and Respond”
Optimized Logistics Increasing Momentum Within DoD Maintenance
John PetersonOADUSD (Materiel Readiness & Maintenance Policy)
Sense-Interpret-Respond
SENSE
RESPOND
INTERPRET-SIMConnections/Standards/ Web Services/Applications
ICATSSARRSGCSSERPPDM
Intelligent NetworksMaster Data CleanupIntranet/InternetGIGSPOE
Asset VisibilityMateriel VisibilityLife Cycle MgntCycle Time MgntCustomer Service Reports
IUID/RFIDS1000DISOGEIAMILS/DLMS
OperatorInput
EquipmentGauges
Other equipmentsensors healthmonitoring systems
CBM(+) Supply
Engineering
Acquisition
RADARMalfunction Pump
MalfunctionOilChangeRequired
Distribution
RADARFixed Pump
Replaced
OilChangeCompleted
Description
• Sense – An abnormal or timed event occurs
– Sensing mechanisms are triggered:• Operator Input• CBM(+)• Equipment Gauges• Other equipment health monitoring systems
– Sensed event/condition may effect system capability, dependability, and/or availability
• Interpret – Understanding event condition by enabling relevant information/data systems to communicate
– Mechanisms to facilitate data interpretation:• Connections – The connection of sensed data’s relationship to databases
of information about the situation. (e.g. IUID/SIM, MIS, WAWF, DSS, technical data, etc.)
• Standards – Compare data standards between the database elements and convert as necessary to the desired format. (e.g. Validate/convert S1000D, GEIA, PLCS, legacy, etc. data to a common standard)
• Web Services – The transformation of the resulting data into actionable information surrounded by security access rights (e.g. Asset visibility, materiel visibility, cycle time management, etc.)
• Applications – The systems delivering timely and accurate information so people can make best case decisions (e.g. ERP, PDM, supply/logistics systems, etc.)
Description
• Respond – Restore system integrity using interpreted data for sensed event via:– Integrated application of functional disciplines
• Engineering – Test/Analyze/Predict/Prevent/(re)design
• Acquisition – Procure materiel fix(es)
• Maintenance – Incorporate materiel fixes
• Supply – Provide piece part support – Materiel visibility
• Distribution – Deliver required materiel to the right location at the right time
– System materiel readiness restored effectively and efficiently
Description
Business Processes and IT Technology Stack Required to Deliver
a Common Maintenance Process to a Weapon System Platform
Sense& Respond
CoreS&R
Functions
Weapon System Programs
DD
X/F
CS
InterpretConnections(Intelligent Network,
Master Data Cleanup)
InterpretStandards
(PLCS, S1000D, GEIA,IUID/RFID, etc.)
InterpretWeb Services
(ICATS)
InterpretApplications
(ERP, PDM/PLM,Supply/Logistics Systems)
HM
MW
V T
AR
DE
CP
LCS
, IU
ID,
dat
a
H6
0 E
LIT
EP
LCS
Jo
int
Str
ike
Fig
hte
r –
PM
S&
R,
SP
OE
, IC
AT
S,
data
Ma
rine
LA
VS
enso
r, I
UID
, da
ta
SENSE
RESPOND
INTERPRET - SIMConnections/Standards/Web Services/Applications
ICATSSARRSGCSSERPPDM
Intelligent NetworksMaster Data CleanupIntranet/InternetGIGSPOE
Asset VisibilityMateriel VisibilityLife Cycle MgntCycle Time MgntCustomer Service Reports
IUID/RFIDS1000DISOGEIAMILS/DLMS
OperatorInput
CBM(+)
EquipmentGauges
Other equipmenthealth monitoringsystems
Supply
Engineering
Acquisition
RADARMalfunction Pump
MalfunctionOilChangeRequired
Distribution
RADARFixed Pump
Replaced
OilChangeCompleted
Status and Next Steps
Sense& Respond
CoreS&R
Functions
Weapon System Programs
DD
X/F
CS
InterpretConnections
(Intelligent Network Master Data Cleanup)
InterpretStandards
(PLCS, S1000D, GEIA, IUID/RFID, etc.)
InterpretWeb Services
(ICATS)
InterpretApplications
(ERP, PDM/PLMSupply/Logistics Systems)
HM
MW
V T
AR
DE
CP
LCS
, da
ta
H6
0 E
LIT
E (
PL
CS
)
Jo
int
Str
ike
Fig
hte
r –
PM
S&
R,
SP
OE
, IC
AT
S,
data
Ma
rine
LA
VS
enso
r, I
UID
, da
ta
•Marine LAV – 11 sensored vehicles the response mechanisms are in place.
•JSF – 10 sensored vehicles the response mechanisms are in place.
•Marine LAV – This needs to be developed as system data strategy. SPOE could be re-used if available on time
•JSF – SPOE program sponsored by BTA
•ELITE (PLCS) – H60 AMC/NavAir/Sikorsky (Standards Rationalization)
•CLOE vs. JALog vs. SPAWARS vs. BWS vs. Etc.
•Marine LAV – ICATS possible with work to be defined and completed
•JSF – ICATS possible due to this being an Air Force system
•Marine LAV – BTA working Master Data and MILS/DLMS
•JSF – BTA working Master Data and MILS/DLMS
Status
Next Steps•Continue to participate with Marine LAV and UMD (F-18) teamsto enable S&R, IUID, master data cleanup and data interoperability•Continue to rationalize the various data interoperability programs•Work with BTA on SPOE and next generation GIG rationalization•Work with TLCSM and LPP to select software vendors/standardsto enable required capabilities in design and sustainment (H60)•Work with BTA on materiel visibility programs to take currentfunctionality and expand it to other Service systems•Monitor BTA progress on Master Data and MIL/DLMS programs
TARDEC HMMWV PLCS-IUIDID Task Name Duration Start
1 TACOM-HMMWV PLCS Pilot 291 days? Mon 5/1/06
2 Develop & refine project plan with deliverables & milestones with BTA 14 days Mon 5/8/06
3 Implementation architecture and methodology (Deliverable) 1 day? Fri 5/26/06
4 Contract prep with Federation and Eurostep 30 days Mon 5/29/06
5 Program review meeting 1 day? Mon 5/29/06
6 UID schema based on PLCS DEX (Deliverable) 1 day? Tue 5/30/06
7 Formalization of UID schema through OASIS 90 days Wed 5/31/06
8 Development of SAP PLCS Federation adpaters 90 days Mon 7/10/06
9 Implementation of PLCS based UID exchange to DOD Registry 30 days Wed 5/31/06
10 Integration with Lattice3D 3D visualization viewer 14 days Mon 5/1/06
11 PLCS tech data Integration between AMG"s SAP PLM and TACOM Windchill30 days Mon 11/13/06
12 Installation and integration of Share-a-space with Windchill 14 days Mon 7/10/06
13 Integration of LSAR data from AMG's Powerlog into Share-a-space 30 days Mon 7/10/06
14 Program review meeting 1 day? Mon 8/21/06
15 Program review meeting 1 day? Fri 10/27/06
16 Integration of tech data and log data in PLCS format into Share-a-space 30 days Mon 12/25/06
17 Develop PLCS functional views based on Share-a-space 14 days Mon 2/5/07
18 Load "as-designed" armor kits data into system from SAP 14 days Mon 2/5/07
19 Develop PLCS based UID exchange between AM General's SAP and Windchill30 days Wed 5/31/06
20 Program review meeting 1 day? Mon 1/22/07
21 Load "as-built" armor kit configurations as they become available 30 days Fri 2/23/07
22 Develop "what-is" scenarios based on integrated system 30 days Fri 4/6/07
23 Pilot demonstrations of integrated system / Meeting at TACOM 1 day? Fri 5/18/07
24 Develop business case including ROI analysis for system 15 days Mon 5/21/07
25 Final project report completed (Deliverable) 1 day? Mon 6/11/07
TARDEC,BTA,AM General
TARDEC
TARDEC
TARDEC,BTA,PM UID
Eurostep
Eurostep
Federation
Eurostep
Lattice3D
Federation
Eurostep
Eurostep,LOGSA
TARDEC,BTA,PM UID
TARDEC,BTA,PM UID
Eurostep
Eurostep
TARDEC,AM General
Eurostep
TARDEC,BTA,PM UID
TARDEC
TARDEC
TARDEC,BTA,PM UID,AM General
TARDEC
TARDEC
4/30 6/4 7/9 8/13 9/17 10/22 11/26 12/31 2/4 3/11 4/15March 1 May 11 July 21 October 1 December 11 February 21
Marine LAV Phase 1
PHASE I EVENT RESPONSIBILITY
Develop demonstration project plan PMLAV
Select components to mark in demonstration phase PMLAV
Establish IUID marking guidelines PMLAV
Procure IUID marking equipment PMLAV
Identify IUID training requirements PMLAV
Modify VAMMP program to integrate IUID JDSR
Identify requirements for integration of VAMMP IUID data to infrastructure (AMIS)
JDSR
Complete Proof of Concept demonstration PMLAV
Marine LAV Phase 2
PHASE II EVENT RESPONSIBILITY
Review lesson learned in Phase I PMLAV
Identify benefits/risks discovered during Phase I PMLAV
Identify necessary action to reduce risk PMLAV
Develop detailed overall Project Plan PMLAV
Rewrite VAMMP in a web based application JDSR
Ensure compliance with MIL-STD-130L PMLAV
Procure UID Marking equipment PMLAV
Complete training PMLAV
Modify existing policies and procedures for UID PMLAV
Complete integration with IUID database PMLAV/JDSR
Identify and address remaining implementation issues PMLAV
Initiate marking of parts PMLAV
Define business rules to gain maximum benefit from IUID implementation PMLAV
Write Final Project Report PMLAV
DLMS Bridge Prototype
DLMSO/DAASC
September 2006
The legacy AIS processes MILS transactions and related data.Problem: How can the legacy AIS use passive RFID data to perform
supply-type receiving functions?
DAAS
Passive RFID
Tagged Material
DoD Enterprise Capabilities
DoD Facility with Legacy AIS that does not now process or receive EDI transactions
Transactions with RFID and
UID data
Distribution Center/Depot
Store DLMS Transaction DLMS 856S
MILS
Current CapabilityRFID
ServerLegacy
AIS
Related Issues and Objectives• Related Issues (Problems):
– Inability of legacy systems to operate in DLMS environment now (not until 2010, 2011, 2012 or beyond for permanent solution, ERP, etc.)
– Lack of middleware solution for integration of RFID and legacy systems– Lack of data exchange and visibility due to legacy systems inability to accept
RFID, IUID, etc.
• Objectives (Desired Outcome):– Enable use of RFID data by legacy systems (sooner rather than later), provide temporary solution until permanent is available
– Enable DLMS transactions and RFID receiving process (system integration) through DLMS middleware
– Provide data exchange and visibility through DLMS middleware functionality
WAWFGEX
DoD Enterprise Logistics Systems
DAAS UID Registry
DoD Facility that cannot receive EDI transactions
Legacy AIS
Manufacturers/Vendor Suppliers
Tagged Material
DLMS – 856
Middleware Solution: RFID data flows from the shipping activities to the DoD legacy systems. GEX is the entry point for Manufacturers (or Vendors) EDI
and DAASC is the entry point for DSS EDI.
Distribution Centers/ Depots Suppliers
DLMS – 856S
DLMS -856A
Shipper Material
RFID interrogator
software
DLMSBridge
Other Trading Partners
MILS AE_,AS_, DR_
527
856856S856A
RF Tag ID
Updates for NICP, Requisitioner,USTRANSCOM,LOGSA, IDE-AV, etc.
856527
MILSDLMS or MILS determinedby customer system profile
DLMS Bridge Prototype - What Has Actually Been Done?
• A DLMS Bridge prototype has been developed (as briefed Jan 06).– Middleware for use between Passive RFID (PRFID) and legacy logistics system
(AIS). – External interfaces unspecified so emulations used (PRFID test kit).– Completed without benefit of a site survey (some educated guesses).
• The “Bridge” has several discrete capabilities including:– A “Normalizer” to account for variations in X12 transactions– Data processor to “parse” the incoming data into reusable form– Database to manage the tag and transaction data– DLMS to MILS mapping capability for legacy transactions (works with 856S for
now)– DDN wrapper for MILS transactions– Basic error handling for mismatches between DLMS 856S and RFID data– Limited query capability for tag reads– Notification transaction capability for DAASC update.
What Does the Prototype Do?• Processes Passive RFID tag read data and DLMS 856S
data (with placeholder for IUID).
• Converts DLMS transactions to corresponding MILS transactions.
• Prepares new transactions for reporting purposes (DAASC, LOTS and legacy logistics system).
• Can be modified to accommodate user defined output requirements other than DLMS or MILS (“flat file”, “data set”, XML, etc.).
DAASC
Passiv
e R
FID L
eg
acy
“Normalizer”
Parser
X12 (856S)
WORK DATA
OUTPUT
DB
Mapping
Plugins
Plugins
RFID tag read data
DLMS Bridge Processing Flow
Business Rules(Library of Business Rules Applicable to Site, Business
Processes, Legacy Systems, any Service Specific Rules)
Translation Maps (Expandable Library of Maps: DLMS to MILS, DLMS to UDF,
MILS to DLMS, UDF to DLMS etc.) 856S, or 856, 856A, 527D, 527R, 842, 861 and others
Transaction Database(tailored to work with other databases such as
SQL, Oracle, DB2, etc.)
RFI
D S
yste
m In
terf
ace
(Exp
anda
ble
Libr
ary
of R
FID
Sys
tem
Spe
cs &
Inte
rfac
es)
Com
mun
icat
ions
Inte
rfac
e(E
xpan
dabl
e Li
brar
y of
App
licat
ion
Prog
ram
inte
rfac
e Pl
ug-In
O
r Con
nect
ors
to L
egac
y Sy
stem
s an
d D
AA
S)
Install & Setup(User selects the RFID and Legacy System interfaces - via
Drop Down Menus - for site installation)
Lega
cy S
yste
ms
and
DA
AS
Flexible Technical Architecture: Modular Construction, Hardware Independent, JAVA-based Code, Multiple O/S (Win XP & Linux for now), Centralized Configuration Management
RFID TagRead
DLMS BRIDGE Architecture
Summary• The DLMS Bridge prototype has technical capabilities
that provide DLMS to MILS translation; it can be modified to process other transactions as needed (UDF, data set, etc.).
• The DLMS Bridge prototype is a “middleware” solution that also addresses other challenges coming soon (IUID data, finance (SFIS) data, transportation data, etc.).
• It is ready now for tailoring to a specific system (next step - schedule a site survey).
Enterprise Integration Hub Features
Value Chain
…5 6 7 8 N1 2 3 4
System Silos
DoDDoD PEOPEO PrimePrime … SubsSubs
Reliable Messaging between Disparate Systems
Translation & Transformation
Business Process Management
Business Intelligence
OSDOSD
PEOPEO
Sub ContractorsSub Contractors
DoDDoD
Lead SI’sLead SI’s
PrimePrime
CommandCommandForcesForces
CPMiHub
Oracle’s Collaborative ProgramManagement Hub (iHub)
Data InteroperabilityArchitecture
Oracle 10g
Appliance
Operating System
JavaPlatform
NCES Collaboration
ContivoBuilder
EuroSTEPShare-A-Space
Cisco AON Framework
Web Service Interfaces ( Custom WSDL)[for: Policy Engine, Directory, Mediator, and Repository]
Open Source(Policy & Directory Services)
ApplicationDesign
ApplicationRuntime
CustomGUI(s)
NCESDiscovery
NCESCollaboration
Cisco Appliance
Operating System
ContivoBuilder
EuroSTEPShare-A-Space
Web Service Interfaces ( Custom WSDL)
Query and Post-Query Processing
Oracle 10g Java Cisco AON Framework
MediatorWSDL API
DirectoryWSDL API
RepositoryWSDL API
Policy EngineWSDL API
Pellet Cluster SweetRules Cluster
Data Pipeline Asset Finder APP Mgr.
Full Stack
Apache Tomcat Cluster
Data InteroperabilityArchitecture
Oracle NCO Reference Architecture
GlobalGlobalInformationInformation
GridGrid
…
…
…
ConnectedLegacy
Systems
Standards-Based
Integration
Applications
UserInterface
Oracle Portal, Collaboration Suite
DataHub
Planning Execution AssessmentSituationalAwareness
Reach-back(Intel, DHS,
Coalition)
Common Operational Picture
Multi-Level Label SecurityMulti-Level Label Security
Role-based Single Sign-onRole-based Single Sign-on
TRANS-COM
LogisticsMobility
Distri-buted
Operators,Sensors
and Shooters
DIMHRSPersonnel
Mgmt,Financials
CombatantCommand,SECDEF,POTUS
Multi-Level Label SecurityMulti-Level Label Security
Joint ForceCommanders
CoalitionPartners
Air/Sea/GroundCombatants
ISRLogistics &
Support
VirtualCentralized
Data Repository
CommonData
Model
DataMgmt
GlobalInformation
Grid
…
…
…
CPM iHub Solution Architecture
ConnectedLegacySystems
Standards-BasedIntegration
Applications
Users
Enterprise Portal, Collaboration, Business Intelligence, Wireless
CPMiHub
Resource Management
QASP Compliance
Program Management
Finance
Common Operational Picture
Multi-Level Label SecurityMulti-Level Label Security
Role-based Single Sign-onRole-based Single Sign-on
SCMPDM HR
Multi-Level Label SecurityMulti-Level Label Security
Presentation
Knowledge Management
CAD
Centralized Centralized Data Data
RepositoryRepository
Central Repository
Data Warehouse
ETL
OLAP
Data Mining
Program Program Info Sharing Info Sharing
PartnersPartners
A look inside the CPM iHub
Service Branch
App
Lead Integrator
App
Marketplace
App
PEO
App
Subcontractor
App
DoD
App
CPMCPM
iHubiHub
CPMCPM
iHubiHub
A look inside the CPM iHub
InterConnectInterConnect WorkflowWorkflow
SemanticSemanticTransformationTransformation
BusinessBusinessProcessProcess
ManagementManagement
Reliable MessagingReliable Messaging
AdapterAdapter AdapterAdapter
AdapterAdapter AdapterAdapter
AdapterAdapterAdapterAdapterBusiness Partner ConnectBusiness Partner Connect
Service Branch
App
Lead Integrator
App
Marketplace
App
PEO
App
Subcontractor
App
DoD
App
Collaborative Program Management Network
• An iHub may be networked with other iHubs across a GRiD fabric, based upon:
– Transaction volume– System Management decisions
CPMiHub
CPMiHub
CPMiHub
CPMiHub
CPMiHub
CPMiHub
Central iHubCentral iHub
Oracle Collaborative Program Management
Project Portfolio Planning
Project IntelligenceProject Intelligence
Secure Program
Repository Project CostingProject Billing
Project ContractsTrack Efforts/Costs
Manage Contract LifecycleCapitalize Assets
Cross-Charge
Project CostingProject Billing
Project ContractsTrack Efforts/Costs
Manage Contract LifecycleCapitalize Assets
Cross-Charge
ProjectCollaborationUpdate ProgressResolve Issues
Review Documents
ProjectCollaborationUpdate ProgressResolve Issues
Review Documents
Resource ManagementUpdate Skills
Match ResourcesTrack Utilization
Resource ManagementUpdate Skills
Match ResourcesTrack Utilization
Project Management
Plan ProjectManage Change
Manage Performance
Project Management
Plan ProjectManage Change
Manage Performance
ProgramDelivery
Research
ProductDevelopment
InformationTechnology
SystemIntegration
Financials
HR
Asset Mgmt
Sales
Supply Chain
DocumentsMarketing
ProgramInitiatives
EnterpriseIntegration
Personalized Role-Based Views
The Bigger PictureThe Bigger Picture
Building the pieces for Network-CentricCollaborative Program Management
Vertical & HorizontalIntegration
PROGRAM OFFICE
PRIME
SUBCONTRACTORSConsolidate – Simplify – Integrate - SecureConsolidate – Simplify – Integrate - Secure
Program Program OfficeOffice
InformationInformation
DesignDrawings
Program Schedules
MissionData
BudgetData
IntelligenceData
DeliverableData
SchedulingData
EngineeringData
BudgetData
DesignConcepts
MissionData
DeploymentData
SupportData
Engineeringdata
Sourcing Data
ContractAgreements
ProgramSchedules
Scheduling Data
Program Office
Forces
Lead Integrators
SubcontractorsDoD
Supply Base
PEOs
DeliveryAcceptance
ServiceLifecycleSupport
PrimesSupplyChain Federal
ForcesSubsSupply Chain
ProgramMgmt
Support
The Future—Powered by Grid Computing
At each level:
• DoD
• PEO
• Forces
• Integrators
• Manufacturers
• Subcontractors
• Raw Material Providers
At each level:
• DoD
• PEO
• Forces
• Integrators
• Manufacturers
• Subcontractors
• Raw Material Providers
Procurement
Support
Engineering
Program Mgmt
Procurement
Design
RequirementsDevelopment
Supply
ConstructionOversight
Engineering
Program Mgmt
Delivery
DoD
“Global Information Grid”
iHubiHub
iHub
iHub
iHub
iHub
Enterprise Portal
Enterprise Role-based Access
Enterprise Portal
Enterprise Role-based Access
ICATS In-Transit Critical Asset Tracking System
• ICATS is a management tool that provides end to end visibility information in a context and volume previously unavailable
• Genesis – After 9/11, the need to “hand massage” and “birddog” critical parts being shipped into a new Theater of Operations and provide instant status to warfighter
• ICATS is a tool for:– Unit-level supply personnel– Regional Supply Squadrons (RSS)– Air Logistics Centers / Supply Chain Managers– Major Command Headquarters– CONUS Distribution Mgt Cell (CDMC) and Logistics Readiness Center (LRC)
• Answers Most Important Questions
• WHERE IS MY PART?• WHEN WILL I GET IT?
Warfighter registers for location of interest
Have the ability to search by TCNWould like to add place holders for searchs by Doc #, NSN, UID and RFID TagPlace holders would not be active for the POC
After logging in only shipments are displayed that user registered for, in this case Diego Garcia shipments are displayed,
Click on Add Feedback
After reviewing the EDDs warfighter could generate feedback,Asking for more explanation or expedite service
Warfighter adds comments,Automatically updates CDMC view
CDMC view
Workload management prioritizes workload
New feedback is displayed,CDMC needs to respond
Able to sort based on EDDs
Able to get general info about shipment
Click on TCN to get detailed shipment information
Detailed shipment informationACC MICAP information automatically displayed,For POC would add field that displays IUID in this area
Detailed shipment informationEnd to End visibility displayed through events P1-P11.Would add RFID events into this view.
Parameters of the shipment display other shipping informationRFID tags and passive tag numbers would be added under this section
Detailed shipment informationICATS generated data due to logistics data and destination specific performance
Detailed shipment informationCDMC update area, add information based human intervention
Shipments without pipeline information are backordered items, not in transportation pipeline. After POC would expand visibility of ICATS to start at time of requisition.
CDMC will manage open feedbacks
Warfighter wants shipment moved via Diego Airlink
CDMC adds their actions taken, which is Automatically seen by the warfighter
Next Steps• Continue to participate with Marine LAV and UMD (F-18) teams
to enable S&R, IUID, master data cleanup and data interoperability– IUID agreed; vehicle sensor implementation underway, next PM meeting in October– F-18 demonstration in October
• Work with BTA on SPOE and next generation GIG rationalization– Work with BTA and the weapons systems program offices (JSF, DDX and FCS) from October
• Continue to rationalize the data interoperability programs– CLOE (July 25), JALog, BWS, SPAWARS (August 2). Way ahead meeting on September 15
• Work with TLCSM and LPP to select software vendors/standardsto enable required capabilities in design and sustainment (H60)
– Work with LPP/BTA on the rationalization of standards with the software and standards primes next AIA meeting July 27
– Continue to work with the expansion of the ELITE program (NavAir) from August• Work with BTA on materiel visibility programs to take current
functionality and expand it to other Service logistics systems– ICATS inclusion of IUID/RFID and the potential expansion of this process to other like
systems starting in September• Monitor BTA progress on Master Data and MIL/DLMS programs
– Continue to monitor the progress of the Master Data cleanup (on-going) and the MILS/DLSM (December) programs
Project DetailsObjectives Initiative Status Plan Forecast Actual Priority/Next Steps Owner(s)/Sponsors Comment
ENTERPRISE
Sense and Respond Programs
Marine LAV
Existing and funded program by the Marines to sensor a set of vehicles, understand how the sensor data is to be gathered and analyzed, optimize the number, type and location of the sensors, and determine the optimum sensors to keep and monitor. OPEN Dec-06 Dec-06
High; Waiting for attendance at the next PM meeting in September Rick Lanier
Carl Zink/Bob Lusardi/Bob Appleton/Robert Charleton
MR&MP has received commitment that the IUID and RFID fields and information will be added to the database and information capturing portion of this program.
UMD (F-18)
Existing and funded program by the LPP team in support of NavAir to create a 2nd data point in the validation of the SPOE common data exchange concept. OPEN Oct-06 Oct-06
Medium; LPP will monitor progress. Demo due in October. Fred Tillack LPP
This will produce another SPOE variant if successful.
JSF
Existing and funded system by the Air Force, Navy, Marines and an international community to ultimately deliver a sensored and autonomic logistics system to support this weapons system. This phase 1 program will demonstrate the SPOE prototype. OPEN Oct-06 Oct-06
High; Waiting for SPOE technical review and/or budget decision by the BTA/JSF team Chuck Silva JSF PM
SPOE functionality is desired but no weapon system funding is in place to enable it.
Way Forward
These programs, and others to be evaluated, will be assessed for their viability to demonstrate the optimized logistics programs to make the maintenance and support of these, and other weapon systems these process can be expanded to, more efficient and effective. OPEN Jan-07 Jan-07
2007 Objectives
Align the Service transformation programs (FRC’s, AFL21, etc.) with the combination of the PBL/CPI/IUID/RFID/Data Interoperability programs. OPEN Jan-07 Jan-07
The biggest transformational priority for M&MR in 2007 Dave Pauling M&MR
This will take effort from many OSD offices along with Service alignment
2007 Objectives
Review the next weapon system to use the “Sense and Respond” combination of optimized systems/processes to enable optimized maintenance and logistics. OPEN Mar-07 Mar-07
Operationalizing "Sense and Respond" maintenance and logistics. John Peterson
The Services, Acquisition PM's and Industry
Representatives of the key new weapon systems
This will take a lot of coordination with the Services and the Acquisition PM's.
Data Interoperability
Programs
ICATSUS Air Force system based on SBSS/DSS and in an alternate instance it includes IUID and RFID OPEN May-06 May-06 May-06
High; Enablement of an existing system to be upgraded with the IUID and the RFID information BTA Mark Reboulet/Vickey Lake
Can be operationalized - Air centric at this point - Air Force driven
CLOE
US Army system that defines the data interoperability standards to integrate the legacy and new Army systems. This is both an overview architecture and has several elements that are installed and currently in use. OPEN Jul-06 Jul-06 Jul-06
High; This is the first Service wide architecture and plan for data interoperability. JALog will likely help in the realization of this environment. MR&MP Miranda Keeney/Greg Reid
Program review completed by Greg Reid. Ground vehicle centric. The path forward is being investigated. - Holistic logistics view with a total architecture defined
JALog
Lockheed data interoperability program that could be an operation element of the CLOE program. Under ACTD and JCTD review. OPEN Aug-06 Aug-06
High; Lockheed understand the DoD systems architecture the JALog solution they are suggesting will likely be able to help in the realization of the CLOE environment. MR&MP
Lori Lindholm/Michael Erickson
Could be an operational element to support CLOE but it needs to be funded to begin. The path forward is being investigated. Air centric. - Holistic logistics view
Blue Water Solutions
A collection of teams with much experience and good ideas around a air centric data interoperability program. Roll Royce was there with an EDS to update air craft engines (T56) to achieve an 8% fuel saving as part of the project. OPEN Aug-06 Aug-06
Medium; Good people with good ideas but they are a solution looking for a problem. If we need extra people, they will be a good source. MR&MP Mac Armstong
Need to be funded to begin. Holistic logistics view
SPAWARSNavy high level decision support methodology/mechanism in place and being used currently. OPEN 02-Aug-06 02-Aug-06 Aug-06
Medium; Once the data interoperability issues are solved this will be very helpful but for the majority of MR&MP work this will be later. Possibly a good fit for Rebecca's DDRS program. Navy/MR&MP
Larry Gwozdz/Roy Roebuck/John Keathley
Operational in the Navy. To expand to the other Services or an OSD operation funding will be required. - Decision management tool.
Way Forward
These programs, and others will be evaluated, will be assessed for their viability to demonstrate the data interoperability programs to make the maintenance and support of these, and other IT systems these process can be expanded to, more efficient and effective. OPEN Oct-06 Oct-06
2007 Objectives
Finalize the selection of the internal and external data interoperability methodologies for the various Services (CLOE, JALog, SPAWARS, etc.) to understand the optimal way forward. OPEN May-07 May-07
Optimize the use of the internally and externally developed data interoperability solution to enable this requirement across the Services John Peterson
The Services, various OSD departments and defense
agencies
Data Standards
S1000DData standard written into a policy memo but never followed up with a DoDD or DoDI OPEN Aug-06 Aug-06
Medium to high; These are dependant on how we attack these issues through tools DoD purchases or through a data interoperability standard but they need to be handled for interoperability internal and external to the DoD. Fred Tillack ADSL - Tim Tate
Al Mize project - Mostly documentation centric
ISO 10303, Application
Protocol 239 (PLCS)
Standard that is being advocated for use as a product life cycle nomenclature standard by the IUID director and MR&MP. OPEN Jul-06 Jul-06 Jul-06
Medium to high; These are dependant on how we attack these issues through tools DoD purchases or through a data interoperability standard but they need to be handled for interoperability internal and external to the DoD. Charlie Lord
LeAntha Sumpter/Dave Pauling/Raj Iyere/BTA
ELITE H60 helicopter program between Sikorsky, AMC and the Navy is complete and being expanded in NavAir. Dr. Iyere is implementing PLCS on the HMMWV at TARDEC. - Item and life cycle centric.
ISO 10303, Application
Protocol 239 (PLCS)
Continuation
Standard that is being advocated for use as a product life cycle nomenclature standard by the IUID director and MR&MP. OPEN Dec-06 Dec-06
Medium to high; These are dependant on how we attack these issues through tools DoD purchases or through a data interoperability standard but they need to be handled for interoperability internal and external to the DoD. Charlie Lord
LeAntha Sumpter/Dave Pauling/Raj Iyere/BTA
Continuation of the ELITE H60 helicopter program to operationalize this effort across the whole of the Navy Air community.
GEIA-927
Standards that is attempting to wrapper the ISO, S1000D, other GEIA and other life cycle standards to allow them all to work together. OPEN Oct-06 Oct-06
Medium to high; These are dependant on how we attack these issues through tools DoD purchases or through a data interoperability standard but they need to be handled for interoperability internal and external to the DoD. Fred Tillack Jim Colson
Still in the development phase. - Holistic logistics view
ISO 13374 MIMOSA
ISO standards centered on the maintenance aspect of a piece of equipment's life cycle. OPEN Oct-06 Oct-06
Medium to high; These are dependant on how we attack these issues through tools DoD purchases or through a data interoperability standard but they need to be handled for interoperability internal and external to the DoD. Greg Kilchenstein
Penn State University driven program. - Maintenance view "As sensed". This program needs commitment.
Other ISO AP'sISO standards centered on specific equipment or design or MFG processes. OPEN Oct-06 Oct-06
Low; Many more main stream standards will have a larger impact. These may become more important when the more visible standards are accommodated. Fred Tillack ISO teams
Other AP's are being modularized to work, from data perspective, like the AP 239 PLCS standard. - view specific to the topic being defined (ships, CAD drawings, electronics, etc.)
Way Forward
These programs, and others to be evaluated, will be assessed for their viability to deliver the data interoperability required to enable the software tool vendors to deliver the capabilities required by the defense contractor OEM's on behalf of the DoD's stated requirements. OPEN Oct-06 Oct-06
2007 ObjectivesData standards must be rationalized and then established as requirements within DoD policy. OPEN Jul-07 Jul-07
Data Connections
SPOECommon data transportation portal to help in the creation of a interoperability data environment OPEN Jul-06 Jul-06 Jul-06
Medium to low dependant on the interest level by JSF; July 20, 2006 meeting completed. Waiting on a technical review and funding commitment. May be we should begin to build the intelligent network instead of a SPOE application. John Nyere Don Hall
Where does this program stand today? A meeting was held on July 20 at 9:30am. - Holistic logistics view was given and funding a functionality questions need to be answered.
Intelligent Network
Create an intelligent network environment where data can flow freely between systems and at the request of an end user the data is gathered, aggregated, analyzed and reported. OPEN TBD TBD
High; A mechanism to intelligently route data to the right location visible to the right people is required. Rick Lanier NII?
This needs to be funded and the environment created to show the value in a small environment before it can be operationalized in a large project. - Holistic logistics view
Core Data Projects
Master Data Clean Up
BTA working with Battle Creek to clean up the item and other master data elements. OPEN Jul-06 Jul-06 Jul-06
High; Under the BTA's guidance and monitoring
Kris Haag/Darren Farber Charlene Woodman
Underway with the assistance of the BTA. Continued funding required.
MILS to DLMS system
transformation
Transforming the DLA and Army ERP systems to be able to pass variable character length data to eliminate the 80 column card limitations that exist today. OPEN Dec-06 Dec-06 Dec-06
High; Under the BTA's guidance and monitoring
Kris Haag/Rick Lanier Army LMP program
Underway with the assistance of the BTA. Continued funding required.
Topics of Interest and impact
EVENTS2006 Maintenance Symposium in Reno, NV to demonstrate S&R capability OPEN Oct 23-26 Oct 23-26
High; S&R will be a big topic at the Maintenance Symposium
Marine LAV S&R Team/data interoperability
DoD PolicyAll existing serialized assets entered in UID Registry and under serialized item management. OPEN Sep-07 Sep-07 Many, many parts to mark LeAntha Sumpter
The Services, various OSD departments and DoD
agencies
Huge program very likely to be missed. Focus on the most critical and costly items.
JSF Platform Requirement
“Sense and Respond” maintenance logistics needs to be enabled for the JSF platform. OPEN Dec-08 Dec-08
Not in the center of the JSF PM's radar screen for logistics. Chuck Silva JSF PM
Huge program lots of complex and move project elements
DoD Policy All items meeting the IUID criteria need to be marked. OPEN Dec-10 Dec-10 Many, many parts to mark LeAntha Sumpter
The Services, various OSD departments and DoD
agencies
Huge program very likely to be missed. Focus on the most critical and costly items.
Overall objective, "Sense and Respond" maintenance and logistics via data interoperability driven by SIM
Timeline OSD Owner(s) Assigned
Next StepsServices Coverage
USA USMC USAF USN DLA Transcom
Sense
Interpret
Connections
Interpret
Standards
Interpret
Web Services
Interpret
Applications
Respond
JALog/JSF CLOE (LAV/HMMVW) BSM Navy Apps (MFOM)
DecisionAnalysis Tool
SPAWARSSPOE
Back Up Slides
Business Processes and IT Technology Stack Required to Deliver
a Common Maintenance Process to a Weapon System Platform
Weapon Systems Platforms
Co
mm
erci
al S
up
plie
rs
Inte
llig
ent
Net
wo
rk
Product LifeCycle System (DEX)
-Product Common Data Environment
-ELITE(PLCS), GEIA, S1000D, etc.
-CLOE, JALog, BWS, SPAWARS.-SPOE, Intelligent
Network
Sense and Respond
Measurement detectedPossible solutions
1,2,3,etc.Optimal solution
Optimized Logistics
Optimal solutionFind optimal parts, resources,
materials, instructions, etc.Proper itemsdelivered to
the optimal locations.
- Sense and Respond-Marine’s
LAV Vehicle,UMD(F-18)
JSF
UIDCust
MasterItem
MasterSupplierMaster
End-to-End Material Visibility (IUID) -Web Services-ICATS, Master Data
clean up, MILS to DLMS transactions
(SIM)
COCOM Demand Pull
End-to-End Supply/Maintenance Operations
Visibility Availability TDD Bom’s Specs Configs
Web Service enabled “Reach Back”
Intelligent Network
Vendor DoDMaintenance
Vendor3PLDesign/MFG
VendorPBL DoD
DoDRepair
Product DataCommon Environment
“Sense and Respond” Optimized Logistics
Warfighter “Demand Pull-Through”
DoDRCA/CA/PA
VendorVMI
DoDSE