The document discusses a service oriented approach to providing capabilities for joint warfighters through architecture federation. It aims to create a common infrastructure that enables the generation of reusable architecture models depicting operational, system and technical perspectives. This is intended to reduce duplication of effort, encourage collaboration, and improve the speed and efficiency of developing joint capabilities.

1. Joint Architecture Federation “SOA In Action - for Joint Warfighter Capabilities” One warfighter Multiple technical configurations Incose Dinner 2010 Howard Cohen Joint Architectures & Capability Engineering Division 757-836-9334 howard.cohen@jfcom.mil

2. Joint Forces J89 System Engineering and Architectures. Enterprise consisting of people, process, Methods and Tools including applications providing a standard framework and repeatable process enabling the generation of reusable architecture depicting operational, system and technical perspectives.

3. System Integration

4. System Virtualization The term virtualizationbroadly describes the separation of a resource or request for a service from the underlying physical delivery of that service.

5. System Quality and Assurance Production VM Production VM DEV VM QA VM Production VM Development Quality Assurance Production VM Deploy Test Develop System Testing

6. 1 Database Server App Server App Server Citrix Server App Server Many to One Server Consolidation App Server ESX Citrix Server App Server App Server Database Server

7. System Layers

8. System Tuning Apache Tomcat 6.0.18 Weblogic 9.2 Versant 7.0.1.4 Patch11 Sun Solaris 9 64 Bit Windows 2003 R2 32 Bit Windows 2003 R2

9. System Deployment Methodology

10. Service Oriented Warfighter

11. **Architecture Context Service Oriented Warfighter Reduce Rework and Eliminate/Reduce Duplication of Effort Share Data Between Various Organizations, Tools and Environments Encourage a More Effective Collaboration Environment Create More Efficient Architecture Development and Analysis Processes in Support of DoD Initiatives Improved Speed of Development

12. **Architecture Context Service Oriented Warfighter

13. 13 Joint Common System Functions List (JCSFL) USN USMC USA JCAs JCAs USAF NCES/NECC Other CPMs Capability Mapping Baseline “Periodic Table” for Operational DOTMLPF-P Analysis Policy Standards Policy Architectures Systems Functions Joint Capability Areas (JCAs) CPM Areas Standards Tier I Analysis Policy Technical Standards Accreditations C2 Portfolio* - Programs of Record - Systems - Sub-systems - New Capabilities Policy Platforms/Weapons Standards ADS & Data Models Policy Joint Staff J7 Mapping Standards Operational Activities Applications/Services Policy JTF OperationalActivities / Tasks / Sub-tasks Networks/Comms UJTL SN X.X ST X.XX OP X.X.X TA X.X.X.X Standards Policy Assessments Joint Tasks Operational Standards AUTLs, MCTL, NTTL, AFTL Documentation Policy Service Tasks Concepts/Plans Operational Nodes & Billets Standards Joint Warfighter Billets Programmatic JCAs- to- PECs Op Nodes PA&E Mapping Joint Integration & Interoperability Recommendations via Detailed DOTMLPF Analysis Authoritative Sources:

14. 14

15. 15 Service Oriented Warfighter

16. Any Questions? The warfigher is always on our mind

17. BACKUP

18. Policy & Guidance DoD Directive 8000.1, “Management of DoD Info Resources”, November 21, 2003 DoD Manual 8020.1-M, “Functional Improvement Process”, August 1992 DoD Directive 8100.1, “GIG Overarching Policy”, September 19, 2002 DoD Directive 8100.2, “Wireless Technologies and the GIG”, April 14, 2004 DoDI 8110.1 “Multinational Information Sharing Networks Implementation”. DoD Directive 8115.1, "I.T. Portfolio Management", October 10, 2005 DoD Manual 8320.1-M, “Data Administration Procedures”, March 1994. DoD Manual 8320.1-M-1, “Standard Data Element Development”, May 1992. DoD Directive 8320.2, “Data Sharing in DoD”, December 2, 2004. DoD Directive 8320.03, “Identification Standards”, March 23, 2007. DoD Directive 8500.1, “Information Assurance”, October 24, 2004. DoD Net-Centric Data Management Strategy: Metadata Registration, April 3, 2003 DoD Net Centric Strategy, May 9, 2003 Department of Defense Discovery Metadata Specifications DEPSECDEF Memorandum on “Information Technology Portfolio Management”, March 22, 2004 Director of Central Intelligence, “Intelligence Information Sharing”, June 9, 2004

19. DoD Directive 8320.02, Data Sharing in a Net-Centric Department of Defense, April 23, 2007 Department of Defense Chief Information Officer, Department of Defense Net-Centric Service Strategy, May 4, 2007 Global Information Grid (GIG) Architecture Federation Strategy, 01 August 2007 Policy Standards Guidance

20. Architecture Federation Guidance Business Transformation Agency (BTA), BMA – Federation Strategy and Roadmap, 26 September 2006 US Army Regulation (AR) – 71, Force Development Architecture (Draft) 10 September 2008. DoD Instruction 8210.aa (Draft), Architecting the DoD Enterprise, 22 September 2008 DoD Manual 8210.11 (Draft), DoD Architecture Federation, 22 September 2008 DoD Metadata Registry and Clearinghouse Version 7.0 Federation Specification DoD Architecture Framework (DoDAF) 2.0

21. Policy & Guidance DoD CIO Executive Board (CIO EB) Military Communications and Electronics Board (MCEB) GIG E2E Systems Engineering Advisory Board (SSEB) IT Standards Oversight Panel (ISOP) Information Assurance Senior Leadership Group (IASLG) Interoperability Senior Review Panel (ISRP) GIG Waiver Board and Panel DISN Flag Panel DISN Designated Approving Authority (DAA) DISN Security Accreditation Working Group (DSAWG) DIAP (Defense-Wide Information Assurance Program.) Joint Battle Management Board (JBMC2 BoD) Defense Business Systems Management Committee (DBSMC) CCB (Configuration Control Board)

22. Architecture Federation Project Background Architecture information, if properly developed, informs decision-making and assists in visualizing complex warfighter capability relationships and business processes Some standards and guidance for architecture development exist, however: Data is “stove-piped” in various proprietary tools and repositories Information sharing is difficult Use of proprietary architecture information has hampered the DoD’s capability to re-use and integrate previously developed architectures

24. Provide and maintain a stable architecture data environment through the use of tools and configuration management processes

25. Enable performance and efficiency of architectural baseline and future developments, change control during development, and facilitate the accuracy and validation of joint data/information

26. Provide traceability of CPM operational, technical and programmatic elements to provide a standard context for the development, assessment, test, and exercise training of current and future warfighting capabilities

27. Facilitate architecture reusability across the C2 enterprise by normalizing business rules for web-service development and federation