United States Transportation Command United States Transportation Command Aligning, not Integrating Aligning, not Integrating Architectures: Architectures: Leveraging a Common Language Leveraging a Common Language to Federate Disparate Architectures to Federate Disparate Architectures May 1 2006 May 1 2006 Mr. Bill Grass Mr. Bill Grass Mr. David Bailey Mr. David Bailey
Agenda Agenda • Guiding Principles • Challenges • Federated Methodology & Solution • Alignment Approach • Systemic Analysis • Maintenance • Benefits & Conclusion
Guiding Principles Guiding Principles � Connect a series of disparate process architectures to uncover the end-to-end visibility of the broader distribution process � Establish automated means to access, trace and display the information • Utilize the information to expose potential systemic gaps, seams, overlaps and inefficiencies • Maintain touch-points and configuration
Challenges Challenges • DPO architecture and processes in CRIS (Corporate Resource Information Source) • Logistics end-to-end (E2E) processes flow across independent service/agency architectures that are managed in a variety of applications • Compliance requirements from Business Enterprise Architecture (BEA) and other policy architectures • No disruption to ongoing service architectures • Limited resources
Federated Methodology Federated Methodology Iterative process that aligns existing architectures within a Federated Methodology. Establishing Governance Defining Governing Standards and Authority Feedback Guidelines Common/ Adapting Alignment/ Reference Standards and Integration Architecture Commonalities Identification of Commonalities Autonomous Architectures Scope Definition
Solution Solution • Utilize ARIS as independent application that federates (aligns rather than integrates or duplicates) existing architectures • Establish a tailored model representing DoD’s Joint Deployment and Distribution environment founded on SCOR • Web based, Tool Agnostic Plan Deliver Make Source Return Return
Structure by Levels Structure by Levels SCOR Overview Level 2 SCOR Level 3 Enable JDDA Deliver ED Manage Assess Manage Manage Manage Manage Manage Manage Manage Deliver Business Delivery Deliver Finished Goods Deliver Capital Product Life Import/Export Force Plan Source Make Deliver Return Transportation Rules Performance Information Inventories Assets Cycle Requirements Protection ED.1 ED.2 ED.3 ED0.4 ED.5 ED.6 ED.7 ED.8 ED.9 Enable Enable Enable Enable Enable Plan Source Make Deliver Return EP ES EM ED ER Source Plan Source Deliver Make-to- Return Supply Stocked Stocked Stock Defective Chain Product Products Product P1 S1 M1 D1 SR1 Deliver Source Deliver Plan Make-to- Return Make-to-Order Make-to-Order Source Order Defective Product Product Product P2 S2 M2 D2 DR1 JDDA Level 4 Source Deliver Source Plan Engineer- Engineer- Engineer- to-Order Return MRO Make to-Order to-Order Products Product Product P3 S3 M3 D3 SR2 Manage Deliver Deliver Deliver Plan Retail Return MRO Information Deliver Product Product P4 D4 DR2 ED.3 Source Plan Return Return Excess CAPTURE ANALYZE Product PROVIDE ADJUST PERFORMANC DISTRIBUTION P5 SR3 STATUS TO DISTRIBUTION E DATA BY PIPELINE CUSTOMER PLAN Deliver NODE PERFORMA... Return Excess Product ED.3.1 ED.3.2 ED.3.3 ED.3.4 DR3
JDDA Alignment Tree JDDA Alignment Tree JDDA Alignment Architecture Overview JDDA - BEA 3.0 BEA 3.0 Mapping JDDA JDDA Alignment Analysis JDDA - JDDA - JDDA - JDDA - DLA JDDA - USTRANSCOM Airfor... USMC ... OA Mapping NAV... JDDA - Mapping ARM... ARMY to JDDA AF LogEA to JDDA DTS to JDDA USMC to JDDA DLA to JDDA NAVY to JDDA Alignment Alignment Alignment Alignment Alignment Alignment (Order Fulfillment) (Order Fulfillment)
JDDA Alignment Approach JDDA Alignment Approach Defining Standards and References Developing Reference Architecture Analyzing (JDDA is SCOR Based) Architectures Aligning Architectures Linking (Activity to Activity) Architectures Alignment Platform Managing Architectures and Processes
Resulting Resulting Business Enterprise Architecture (BEA) Environment Environment Materiel Supply & Services ALIGNMENT INTEGRATION SCOR Navy DPO Master DLA Capabilities List JDDA Army Air Force Reference/Capability Model Service/ USMC Agency Architectures JDEA DTS JDA Joint Theater TCCs Tactical Core Financial Distribution Architectures Architectures Dep Arch Architectures (JTCDA)
Systemic Analysis / Utilization & Value Systemic Analysis / Utilization & Value • Changing the Paradigm – From: Independent business unit driven, reactive, and system-centric – To: Proactive and focused on the complete supply chain process – Examples: • Policy Compliance • Capability Fulfillment • Process Comparison/Improvement
Policy Compliance Example Policy Compliance Example • Example Issue: – BEA 3.0 Mandated RFID Standards support by Service/Agency/CoCOM systems • Analysis Steps: – BEA 3.0 aligned to JDDA – RFID standards compliance traced from the BEA through the JDDA, and into Service/Agency/CoCOM system views – Focus systems GATES, WPS • Results: – Focus systems currently not actively supporting RFID standards in TV-1 profile – Program Managers of identified systems of requirement for standards support – Standards traceability established, potential feed in to program IPT reviews
Recommend
More recommend
