slide template

1. LandWarNet 2008

3. PURPOSE: To present and discuss: An overview of the software development process from a life-cycle integration, certification / testing and fielding perspective focused on ensuring system interoperability. Introduction - COL Steven Drake Life Cycle Software Engineering Support � Ted Dzik AIC Testing - David McClung Developmental/ Certification Interoperability Initiatives - Mark Hosson Data Interoperability Strategy - Judith Pinsky OBJECTIVES: By the end of this presentation you will be able to: Understand the current life cycle processes and initiatives Understand the scope of the interoperability certification challenges Understand the details of the Army Interoperability Certification process

7. Need For Software Sustainment Sustainment Drivers: - Changing operational needs or environment -- Respond to new threats/requirements -- Maintain interoperability with other changing systems -- Accommodate new weapons, systems or munitions -- Increase efficiency/effectiveness -- Support new doctrine/tactics -- Implement IAVA fixes for information security - RESET - Port to new platform (e.g. unsupportable HW) - Satisfy policy mandates (e.g. IPV6) - Insert new technologies to deliver new capabilities - Fix problems/defects discovered during system use Business Drivers: - Maximizes total life-cycle ROI for given investment - Maintains operational effectiveness (avoiding expensive/unnecessary replacement) - Affords opportunity to get new capabilities to the field with less risk, faster & cheaper

8. Software in a Net-Centric Environment

10. Software Replication, Distribution, Installation & Training (RDIT)

12. Software Business Initiatives ? Software Asset Management/License Management (SAM) ? Software Assurance ? Enterprise Solutions Competency Center (ESCC) ? JUICE/JOIN ? Data Strategy Center of Excellence ? Single Interface to the Field ? Replication, Distribution, Installation & Training (RDIT) ? Software Product Line Re-Architecting ? CMMI/Lean 6-Sigma Process Improvement

13. SAM/CALM OBJECTIVE: The Enterprise pays for no more and no fewer COTS licenses than are needed, and software is acquired, and maintained at the most efficient cost per license. 

14. Enterprise Solutions Competency Center (ESCC)

16. Software Integration � ExampleSWB-1 (Fires)

17. Army Interoperability Testing

18.

19. Governance Structure

21. Army Interoperability: Exchange of information, data, and/or services from producer to consumer. System of systems oriented According to standards specified in SWB TV-1 Expressed in Mission Threads Automated and �swivel-chair� Applies to systems and platforms Context: production, transmission, retransmission, receiving, parsing, storing, displaying or regeneration Operational Context: �Operationally representative� architecture Sufficient depth (Corps to system/platform) Sufficient breadth (adjacent units) Information exchange requirements �check ride�

22. Types of Interoperability Testing

23. Quality in Traceability

25. Keys to Success Interoperability � early design consideration Follow BEMP TV-1 (obey standards) Software Blocking System Engineer/Architect MATDEV and COMBAT DEV tenaciously engaged in thread development and approval PM and Vendor active presence at CTSF APM, TICM, Test Officer, CIO/G6 Team �Sand-table� rehearsal of operational touch points between systems and platforms SoS Risk Reduction ? Test-Fix-Test

26. Interoperability Initiatives

28. Scope of Army�s Integration Challenge

29. Reduce Army Interoperability Certification Cycle Time Better Utilization of Resources (Facilities, SMEs, System Assets) Leverage Existing Assets Quantity of Systems Requiring Certification is Growing Support System of System Integration Up-Front Detect/Resolve Software Anomalies Prior to Certification Capable of Integrating Joint and Coalition Systems Bottom Line: Get Capabilities to the Field as efficiently as possible Objectives

30. Federated Net-Centric Sites (FaNS)

31. Environment Fully Supportive of Army CIO/G6�s FaNS Concept A federation of existing Army and Joint (when applicable) facilities, networked together to execute horizontal integration, Army Interoperability Certification (AIC) testing, and CM in support of applicable Army IT/NSS across all Mission Areas/Domains Concept Originated as a Means to Efficiently Support the Growth of Central Technical Support Facility (CTSF) AIC Mission FaNS Objectives Achieve cost and schedule efficiencies Align with evolving AIC demands Maintain integrity of AIC testing Required Activities Identifying and scheduling facility for participation in AIC test Accrediting the facility for the FaNS environment Executing AIC test events FaNS Initiative

32. FaNS Conceptual Layout

33. Software Developmental Integration Network (SDIN)

34. Persistent, Agile, and Efficient Horizontally-Focused Distributed Software Developmental Integration Network Targeted to Support Full Life-Cycle Product Development & Integration Community Asset SoS Integration Peer-Peer Software/System Integration Distributed Troubleshooting Experimentation and Analysis Can be Leveraged for Certification Testing Leverage Core Competencies to Implement Joint On-Demand Interoperability Network (JOIN) infrastructure and distributed testing expertise Connectivity, data collection, monitoring CM, IA, Replication/Distribution Federate Army & Joint capabilities (e.g. ATIN, JMETC) Government and Contractor Facilities (Meeting IA/Other Requirements) SDIN Initiative

37. Joint Mission Environment Test Capability(JMETC)

38. SDIN Conceptual Layout

39. Provide Environment to Support Interoperability Certification as the CTSF Mission Expands Across All Mission Areas/Domains Support Environment to Enable Integration Testing During Development Process Key Enabler � Data Interoperability Summary

40. Army Net Centric Data Strategy

41. Why Army Data Strategy Is Needed Ensuring �System of System� Data Interoperability Enable Data Visibility, Accessibility, Understandability, and Interoperability Find, get and be able to use the real-time mission-critical data needed during a mission Mission Areas, Domains, Joint, DoD Single Source of Truth Authoritative Data Sources Improved Data Quality Minimization of Data re-entry Derivations of Data Convergence Of Common Data Sets Alignment of Business Processes within and across Mission Areas / Domains / DoD

42. DoD Data Strategy Vision

43. Situational Awareness Example Commanders and staff need to maintain situational awareness during a mission Real-time information exchanges primarily through soldiers (radios, email, briefings) as events occur Data interoperability among systems manual (e.g., swivel-chair integration) Army Net-Centric Data Strategy enables situational awareness during a mission Find, get and be able to use the mission-critical real-time data needed during a mission Right Information, Right Time, Right Format for system data interoperability to avoid swivel-chair data integration From Logistics to Personnel to Battlefield Situational Awareness Across Mission Areas, Domains, Joint, DoD

44. Value Added Characteristics of Data Must meet the needs of the commanders and staffs to maintain situational awareness and obtain the highest level of quality for their information by ensuring: Relevance � ensure data applies to the mission, situation, or task at hand Accuracy � conveys the true situation Timeliness � available in time to make decisions; current data Usability � portrayed in common, easily understood formats and displays Completeness � provides all necessary data Precision � required level of detail Security � affords required protection

45. Key to Success � Teaming Chief Data Officer, Data Stewards, and Army Senior Leaders Implements Army, Joint and Federal Data Strategy Standards and Policy Serves as advocates for Data Strategy implementation Army Data Harmonization and Integration Working Group Serves as mechanism to ensure Joint Interoperability Synchronizes activities across COIs, Mission Areas, Joint Facilitates cross-COI data sharing, reuse, harmonization of data products Promotes consensus on data policy, governance, & architecture issues Army Net Centric Data Strategy Center of Excellence Promotes a common approach and focus to data strategy implementation Leverages Best Practices and Commercial Standards Provides Subject Matter Expertice to Missions Areas / Programs of Record / COIs in executing Net Centric Data requirements Collaborating through the Enterprise Solutions Competency Center (ESCC) to enable Business Transformation Continual feedback to ensure satisfaction through HTTP://DATA.ARMY.MIL Communities Of Interests (COIs) Collaborative groups of users working toward common shared information through implementation of Net-Centric Data Strategy End Users Data Consumers and Producers that understand User Needs

46. Summary Understand the current life cycle processes and initiatives Includes development integration support to the warfighter and requires strong configuration management , criteria and metrics The SDIN/FaNS initiatives will further CECOMs ability to support Army/Joint developmental and certification activities on a much larger distributed environment Data integrity is paramount to achieve net centric data interoperability Understand the scope of the interoperability certification challenges CTSF Mission Expands from 60+ to upwards of 500+ future systems for certification testing Future FaNS construct will include SILs positioned around the world CTSF serves as the hub of the FaNS architecture Understand the details of the Army Interoperability Certification process Interoperability Certification process begins with Interoperability integration under PM/PEO Title 10 responsibilities Interoperability certification is a Title 40 requirement of the CIO/G6 CTSF supports interoperability integration engineering for PM�s and executes certification testing for the CIO/G6 The AIC is a 3-9 Month process, which includes G6,G3,G8, ASA(ALT) and TRADOC stakeholders