Technical Team Presentation Customer Requirements

1. Technical Team PresentationCustomer Requirements Stockholm, June 9, 2005 Claude Roche

2. Technical Council Structure TECHNICAL COUNCIL Vice Chair: Mike Curtis (IBM) Vice Chair Elect:Sheryl Sizelove (Boeing) Chair Emeritus: Alan Murdoch (NGC) STANDING TEAMS Education and Outreach Architectures and Standards Analysis Customer Requirements Chair: John Poladian (HP)Vice: Al Nauda (Raytheon) Exec Sponsor: TBDWorking Groups: - OSD/OFT Krishna Sankar (Cisco) - W2COG John Poladian (HP) - Distance Learning TBD ( ) Chair: Steve Russell (L-3)Vice: Rob Biddlecomb (NGC) Exec Sponsor: TBDWorking Groups: - Stakeholders ID Serialization TBD ( ) - Initiative ID & Analysis TBD ( ) - Mission Thread/Use Case Analysis TBD ( ) - Automation & Analysis Tools TBD ( ) Chair: Bob Lawrence (BAE Systems) Vice: Frank Miller (Rockwell)Exec Sponsor: TBDWorking Groups:- Position Paper / Lexicon Paul Mangione (Boeing/GBA) -Open Standards / Patterns Mark Bowler (Boeing) - NCOIC Interop Framework (NIF) Frank Miller (Rockwell) - NCO Analysis Tool (NCAT) Fred Mervine (IBM) Vish Dixit (Boeing) - Mobile Networks Jim Bound (HP) Steve Kobierowski (Boeing) - Tri-Service Initiatives TBD ( ) Engineering Processes Chair: Tim Wellman (Raytheon)Vice: Ken Cureton (Boeing) Exec Sponsor: TBDWorking Groups:- System Engineering Processes - Collaboration Processes - Modeling, Simulation, & Demos Building Blocks Chair: Steve Haken (Sun)Vice: James Burke (Lockheed Martin) Exec Sponsor: TBDWorking Groups: (To be launched)- Web Services; Category Definition Partner Management

3. Customer Requirements Team Description • Charter • Rigorous analysis of pertinent government agency architectures, capability needs, and mandated open standards to identify commonalities, synergies, conflicts, gaps and potential areas for improvement. Collection and tracking of key stakeholders and initiatives to identify areas of NCOIC focus. • Key Activities • Evaluate initiatives such as the GIG, NCOW Ref. Model, NCES, FORCEnet, C2 Constellation, LANDWARnet, JBMC2, DCGS, NATO NEC, and JC2 • Identify customer and other stakeholder communities of interest (COI) • Build Knowledgebase of stakeholders, initiatives, architectures, standards, and requirements using DoD Data Sharing concepts • Create test-bed for describing, discovering, sharing distributed data using member contributed products and expertise • Analyze mission threads for gaps and improvement opportunities • Align NCOIC technical efforts with Customer and member initiatives • Increase member understanding of the Customer missions and needs

4. Customer Requirements TeamResource Plan

5. Customer Requirements TeamDeliverables

6. Customer RequirementsTeamStakeholder ID & Serialization Working Group • Charter • Identify and document all potential customer and other stakeholder communities of interest within the government and industry, seek balanced representation of members, affiliated organizations, and advisors, and serialize for NCOIC focus. • Key Activities • Develop list of stakeholders by category (Community of Interest) • Research and analyze stakeholder information • Develop process for identifying a potential stakeholders appropriate role (i.e. Member, Affiliate, Advisor, Customer, or government partner) • Serialize stakeholders using a rigorous process of evaluation • Identify stakeholder initiatives, desired capabilities, and priorities • Capture data in a database for query, mining, and automated analysis

7. Customer RequirementsTeamStakeholder ID & Serialization Working • Objective: • A rigorous, defensible process for serializing (prioritizing) NCOIC focus • Identification of candidates for Membership, Affiliate, Advisor roles • Classification of stakeholders by Community of Interest (COI) • Evaluation of stakeholders Ability to Execute, Legitimacy, and Urgency • Deliverables: • List of Candidate Stakeholders by COI (category) • Database of stakeholder data with relationship to initiatives data • Analysis techniques and tools for serializing stakeholders • Outcome: • Process and tools for identifying, classifying, and evaluating stakeholders • Data and tools to support the Membership, Affiliate, and Customer Teams

8. Customer Requirements TeamInitiative ID & Analysis Working Group • Charter • Research and document the details of the serialized customers’ major initiatives to determine areas of common and conflicting requirements and gaps. Determine through Thread Analysis and other analytical techniques the direction and status of various NCO initiatives. Provide data to the Consortium Deliverables Working Groups to identify projects for further research. • Key Activities • Identify NCO initiatives from strategy level to awarded contracts • Summarize initiatives to a common information template • Assess technical readiness level (TRL) of initiatives key technologies • Assess viability (funding and support) • Analyze initiatives and identify successful and failing components • Perform thread analysis for converging and diverging requirements • Capture data in a database for query, mining, and automated analysis

9. Customer Requirements TeamInitiative ID & Analysis Working Group • Objective: • Develop a rigorous process for evaluating NCO initiatives • Develop the data and tools for tracking NCO initiatives • Perform Thread Analysis to map initiatives to identify likely NCO roadmap • Evaluate initiatives to focus NCOIC efforts to areas of most likely success • Deliverables: • Thread Analysis of key customer NCO initiatives • Database of initiatives data with relationships to stakeholders, architectures, standards, requirements, best practices, COTS building blocks, etc. • Outcome: • Process and tools for identifying, classifying, and evaluating initiatives • Data and tools to support the Consortium Deliverables, Engineering Process, COTS Building Blocks, and Education Teams

10. Customer Requirements TeamMission Thread Analysis Working Group • Charter • Research and understand Customer missions and identify gaps and opportunities for interoperability improvements and new capabilities or technology insertion. • Key Activities • Review and evaluate CONOPS, Capstone Requirements Documents, Mission Needs Statements, Mission Threads, Initial Capability Documents, capability assessments, roadmaps, etc. • Review and evaluate company strategic plans and technology roadmaps • Identify opportunities and gaps • Participate in NCOIC Roadmap and NCO Landscape Study & Analysis • Create Operational Descriptions (ODs) for input to the NCOIC Interoperability Framework (NIF) • Capture data in a database for query, mining, and automated analysis

11. Customer Requirements TeamMission Thread Analysis Working Group • Objective: • Research and understand architectural depictions of Customer missions and analyze the capabilities needed. Identify gaps and patterns that offer opportunities for common solutions, building blocks, and standards. • Deliverables: • Operational Descriptions (ODs) for inclusion in the NCOIC Interoperability Framework (NIF) • Periodic inputs to the NCO Business Study & Analysis Team • Outcome: • Alignment of NCOIC Technical efforts with Customer missions and capability needs. • Increased understanding about Customer missions, operations, and capability requirements.

12. Customer Requirements TeamAutomation & Analysis Tools Working Group • Charter • Investigate and implement automated methods for collecting, organizing, storing, accessing, and analyzing Stakeholder and Initiative data for use by other NCOIC teams and members • Key Activities • Assess sources of stakeholders and initiatives data • Work with Advisory Council and Customer Contact team to overcome access restrictions to FOUO, program, and proprietary information • Automate data collection via federated portals, RSS, XML, crawlers, etc. • Create taxonomy for stakeholder, initiative, and mission thread data • Assess advanced concepts, technologies, and tools for complex distributed information discovery, sharing, and analysis • Use the vast sea of information about NCO on the Internet and at Member companies as a test-bed for the DoD Data Sharing Strategy

13. Customer Requirements TeamAutomation & Analysis Tools Working Group • Objective: • Research and development into tools and techniques for describing, discovering, and using vast distributed information sources as will abound under DoD’s Data Sharing Strategy (TPPU – Task, Post, Process, Use) • Deliverables: • Database of Stakeholder and Initiatives data and library of NCO documents • Federated industry and government portals, databases, resources • Automated data collection via XML, RSS, Blogs, web crawlers, etc. • Simple to complex data analysis and visualization techniques and products • Taxonomy and metadata for NCO related information • Outcome: • Techniques and tools to align NCO Landscape and NCOIC Roadmap • Expertise in technology, practices, and standards that will be required for the DoD Data Sharing Strategy at the heart of Network Centric Warfare.

14. Customer Requirements Team Accomplishments • New Member Recruitment and Orientation: • Created orientation materials for new Customer Requirements Team members • International Teams: • First International effort with Ofer Haruvi, IAI. Isabelle Okashi to be project manager • Second international effort underway with Jan Wiberg and Sigvard Broden, SAAB, leading the formation of a European and NATO team. • Sent set of materials, templates, and formats. Additional support material is in work • Information Access: • Information sharing is the essence of the NCOIC and the critical change for NCO • Shared open understanding of customer requirements, and compete on execution • Requested support from Advisory Council and Customer Outreach Team • Visits with Customers to build trust relationships with organization and key personnel • NCOIC contract vehicle under consideration for FOUO access when needed • Working with Legal Team, Dave Shaw, Carl Schwab on revisions to IPR Policy and Position Paper clarifications dealing with NCOIC respect of distribution restriction

15. Customer Requirements Team Accomplishments • Information Access: • W2COG: Providing Use Cases, briefings from returning troops, and documents Provided NCOW Reference Model evaluation report by Dr. Rick Hayes-Roth Provided OGC industry review and comments of NCES LOI signed to cooperate on 9 points, including Mission Thread analysis • Navy: CAPT Tom Dlugolecki, FORCEnet POC, sponsoring VPO access Mike Stewart provided FORCEnet Standards Lists (DODAF TV-1 and TV-2) Admiral Bush (via Tim Pavlick) provided Navy OA documents Provided industry comments on FORCEnet Architecture and Standards Invited to joint NCOE and FORCEnet Engineering Conference June 27 - 30 • OSD/OFT: Agreed to provide their Case Studies to NCOIC LOI ready for Executive Council approval • Air Force: COL Clapp designated AF POC. Sent request for website access and documents • JFCOM: Has agreed to send next version of JBMC2 Roadmap when released in June • OSD/NII: NCOW RM, NR-KPP, KIPs, GIG Architecture, GEDEN access still not resolved

16. Customer Requirements Team Accomplishments • Quick Look Reports • Drafts Completed • Navy/Marines FORCEnet • GIG Architecture • Distributed Common Ground System (DCGS) • Air Force C2 Constellation • JBMC2 • Drafts In Work • Net-Centric Enterprise Services (NCES) • JC2 • Army LANDWARnet • Net-Centric Operations & Warfare Reference Model (NCOW RM) • NATO Network-Enabled Capability (NNEC) • Near Term Actions: • Request members review and provide comments and suggestions • Pink Team and Red Team review and release to members and affiliates • Establish teams around Quick Looks to do deep dive and maintain as requirements emerge

17. Customer Requirements TeamNext Steps • Work with NIF Work Group on Operational Description details to connect NIF PFC efforts to customer requirements • Work with S&II Work Group on NCO Landscape taxonomy & ontology • Work with Infrastructure group to build net-centric test bed using data about NCO stakeholders and initiatives. Government and Industry knowledgebase. • Customer visits to build trust relationships, foster information sharing, and gain access to FOUO documents and web accounts • Continue to monitor exercises, demos, BAAs for successes as a source of emerging customer requirements, solutions, standards, and best practices • Follow up with rigorous architecture analysis of 10 Quick Look Report initiatives

18. Technical Council Structure TECHNICAL COUNCIL Vice Chair: Mike Curtis (IBM) Vice Chair Elect:Sheryl Sizelove (Boeing) Chair Emeritus: Alan Murdoch (NGC) STANDING TEAMS Education and Outreach Architectures and Standards Analysis Customer Requirements Chair: John Poladian (HP)Vice: Al Nauda (Raytheon) Exec Sponsor: TBDWorking Groups: - OSD/OFT Krishna Sankar (Cisco) - W2COG John Poladian (HP) - Distance Learning TBD ( ) Chair: Steve Russell (L-3)Vice: Rob Biddlecomb (NGC) Exec Sponsor: TBDWorking Groups: - Stakeholders ID Serialization TBD ( ) - Initiative ID & Analysis TBD ( ) - Mission Thread/Use Case Analysis TBD ( ) - Automation & Analysis Tools TBD ( ) Chair: Bob Lawrence (BAE Systems) Vice: Frank Miller (Rockwell)Exec Sponsor: TBDWorking Groups:- Position Paper / Lexicon Paul Mangione (Boeing/GBA) -Open Standards / Patterns Mark Bowler (Boeing) - NCOIC Interop Framework (NIF) Frank Miller (Rockwell) - NCO Analysis Tool (NCAT) Fred Mervine (IBM) Vish Dixit (Boeing) - Mobile Networks Jim Bound (HP) Steve Kobierowski (Boeing) - Tri-Service Initiatives TBD ( ) Engineering Processes Chair: Tim Wellman (Raytheon)Vice: Ken Cureton (Boeing) Exec Sponsor: TBDWorking Groups:- System Engineering Processes - Collaboration Processes - Modeling, Simulation, & Demos Building Blocks Chair: Steve Haken (Sun)Vice: James Burke (Lockheed Martin) Exec Sponsor: TBDWorking Groups: (To be launched)- Web Services; Category Definition Partner Management

19. Customer Requirements TeamAllied comparison