9000-0016.doc

HQ AFSPC

CONTRACT INFORMATION

AFSPC Enterprise Architecture and the AFSPC Infostructure Architecture

1050 North Newport Rd

Colorado Springs, CO 80916-2742

(Base + 1 Opt Yr)

STATEMENT OF WORK

FOR

ARCHITECTURE AND INTEGRATION SUPPORT

FOR

HQ AFSPC/A6II

7 July 2006 9000-0016

1.0 DESCRIPTION OF SERVICES. This contract is for non-personal services to support HQ AFSPC/A6II requirements for architecture development, integration analysis and planning activities for the AFSPC Enterprise Architecture. This task supports the development of the AFSPC Enterprise Architecture and the AFSPC Infostructure Architecture through the activities (i.e. events) described in the AFSPC Architecture Campaign Plan (ACP), Version 2.1 (final). The ACP identifies specific goals for the AFSPC use of architecture(s) in order to meet the one overarching goal of the ACP, which is the development and implementation of the AFSPC Enterprise Architecture. Through the use of architecture, AFSPC will be better able to support planning and programming, as well as, the analysis of capabilities, effects, systems and technologies to bring space capabilities to the warfighter.

1.1 ORGANIZATION BEING SUPPORTED: HQ AFSPC/A6II

150 VANDENBERG ST., STE 1105

PETERSON AFB CO 80914-4510

1.1.1 MISSION: The enterprise architecture describes how an organization performs its work using people, processes, data and technology. That enterprise architecture helps build a blueprint for improving the efficiency and effectiveness of the organization.

“Consistently implementing the Air Force Enterprise Architecting processes and products will ensure the Air Force mission is accomplished more effectively and efficiently.”

General Jumper and Secretary Roche, AF Policy on Enterprise Architecting, 6 Aug 2002.

Space systems play an essential role in today’s Air Force. Without properly integrated space systems, the Air Force Enterprise Architecture will not support the Air Force vision for architectures in a net-centric operations environment.

“We recognize the importance of Enterprise Architecting as the enabling foundation for an integrated, capabilities-based, air and space force…we are committed to the long term benefits.” General Lord, AF Policy on Enterprise Architecting, 12 Jan 2003.

The four pillared components of the AFSPC Enterprise Architecture are (a) warfighter/ operations, (b) operations support, (c) business/corporate processes and (d) infostructure. The AFSPC Enterprise Architecture will facilitate effective integration analysis and planning activities, such as the AFSPC Integrated Planning Process and the AF Capabilities Review and Risk Assessment process. The AFSPC Enterprise Architecture will also facilitate the detailed trace of capabilities; conduct detailed horizontal and vertical integration to provide better insight to support future planning capabilities acquisition development, modernization, sustainment and funding decisions.

To ensure AFSPC has the opportunity to leverage architecture products to guide integration of current and future systems, it is clear that we must institutionalize the use of architectures. It is apparent AFSPC cannot elicit the maximum benefit from architectures without defining a process that reaches across the command. The AFSPC Architecture Campaign Plan is the AFSPC instrument for achieving the Air Force vision for architectures in our evolving net-centric operations environment. The ACP identifies specific goals for AFSPC use of architectures and associated activities necessary to achieve these goals. Through the use of architectures, AFSPC will be better able to support planning and programming, as well as, the analysis of capabilities, effects, systems and technologies to bring the needed space capabilities to the warfighter. The (4) ACP goals include (a) development of the AFSPC Enterprise Architecture (EA), (b) development and implementation of governance, (c) awareness and training and (d) compliance with Air Force and Higher Headquarters guidance. The AFSPC path to achieve the vision as described by CSAF and SECAF is through implementation of the activities identified in the AFSPC Architecture Campaign Plan.

A6II manages the oversight and implementation of the Architecture Campaign Plan. This entails active partnering with all HQ AFSPC directorates, the System Program Offices (SPO) at the Space and Missile Center at Los Angeles AFB CA, Electronic Systems Center at Hanscom AFB MA and at Hill AFB in Ogden, UT, as well as, AFCA, USSTRATCOM, AFC2ISRC, SAF/XC and various Higher Headquarter and other Government agencies in and around Washington D.C., Los Angeles, CA and Omaha, NE.

1.2 OVERVIEW OF SERVICES REQUIRED: The contractor shall conduct (a) document and architecture reviews and analysis, (b) accomplish the specified activities of the Architecture Campaign Plan in support of the development of the AFSPC Enterprise Architecture, (c) begin development of the AFSPC Infostructure Architecture, a critical component of the AFSPC Enterprise Architecture, (d) perform mission impact analysis, (e) support AF- and DoD-level architecture councils, (f) identify and maintain an architecture and an integration issues and opportunities repository and finally (g) perform Task Order management.

The contractor shall use current versions of the major architectural tools currently used by AFSPC, namely Popkin System Architect Enterprise Modeling Tool, Rational Rose Software Development Tool and the Metis Visual Modeling Tool.

1.3 SPECIFIC REQUIREMENTS:

1.3.1

REQUIREMENT 1:

The contractor shall conduct 100 technical analysis and reviews of architectures, architecture products, documents and briefings annually. Reviews will include (a) Operational Requirements Document (ORD), (b) Interoperability Requirements Document (IRD), (c) Joint Requirements Oversight Council (JROC) Results Review, (d) DoD, AF and AFSPC Instructions and Guidance, (e) DoD Architecture Framework (DoDAF) Documents, (f) C4 Intelligence Support Plans (C4ISP), (g) Net Centric Operations and Warfare (NCOW) Architecture, (h) Concept of Operations (CONOPs), (i) Functional Concepts, (j) Enabling Concepts, (k) Congressional Testimony and finally (l) ConstellationNet Architecture. Also, the contractor shall prepare inputs for the Weekly Activity Report (WAR). The contractor shall provide a conference room at their facility that is available to support 15 attendees. The contractor shall attend the weekly A6II staff meeting, as well as the A6I staff meeting (as requested) in Bldg 1.

1.3.1.1 Deliverables (1): The contractor can anticipate (1) CDRL deliverable (CDRL 036, Technical Report-Study Services) per document/architecture reviewed. Anticipate 100 reviews for the period of performance. Weekly Activity Reports are due by COB every Monday. A6II staff meetings occur weekly, unless canceled by the Government, however, meeting minutes are not required. CDRL 0036 (Technical Report – Study/Services).

1.3.2

REQUIREMENT 2:

The contractor shall produce up to (6) DOD Architecture Framework (DODAF) Enterprise Architecture OV-6c’s (Operational Event Trace Description).

1.3.2.1 Deliverables (2): Using the most current version of the DoD Architecture Framework, products shall include up to (6) OV-6c’s. Each OV-6C will be delivered 30 days after project is assigned.

1.3.3

REQUIREMENT 3:

The activities or events (approximately seven major inputs per year) are described in the Architecture Campaign Plan (ACP). While the activities are not deliverables in themselves, they are the higher level requirements that will generate the deliverables. These higher level requirement descriptions are identified in the 1.3.3 grouping of the Architecture Campaign Plan (ACP), Version 2.1 (final).

1.3.3.1. The contractor shall develop and maintain the single AFSPC Command-Wide AV-2 (Integrated Dictionary), the single TV-1 (Technical Architecture Profile) and the single TV-2 (Standards Technical Forecast). Reference ACP Activity EA1.3.

1.3.3.1.1 Deliverables (3): Using the most current version of the DoD Architecture Framework, products shall include a single AV-2, TV-1 and TV-2. These products will be built using the Popkin System Architect Enterprise Modeling Tool, Version 9.1.4.0 or higher. All products will be delivered 30 days prior to the end of contract period.

1.3.3.2. The contractor shall develop and maintain architecture products for the six AFSPC Functional Concepts and any Enabling Concepts designated by A6II. Products shall include the AV-1 (Overview and Summary), AV-2 (Integrated Dictionary), OV-2 (Operational Node Connectivity Description), OV-3 (Operational Information Exchange Matrix), OV-4 (Organizational Relationships Chart) and OV-5 (Operational Activity Model). Reference ACP Activity EA2.1.

1.3.3.2.1 Deliverables (3): Using the most current version of the DoD Architecture Framework, products shall include a single AV-1, AV-2, OV-2, OV-3, OV-4 and OV-5. These products will be built using the Popkin System Architect Enterprise Modeling Tool, Version 9.1.4.0 or higher. All products will be delivered 30 days prior to the end of contract period.

1.3.3.3. The contractor shall develop a single profile that includes: AV-1 (Overview and Summary), SV-1 (Systems Interface Description), SV-2 (Systems Communications Description) Reference ACP Activity EA4.4.

1.3.3.3.1 Deliverables (3): Using the most current version of the DoD Architecture Framework, products shall include a single AV-1, SV-1, SV-2 . These products shall be built using the Popkin System Architect Enterprise Modeling Tool, Version 9.1.4.0 or higher. All products will be delivered 30 days prior to the end of contract period.

1.3.3.4. The contractor shall identify and address architecture, integration and net-centric issues and opportunities. Reference ACP Activity EA6.3.

1.3.3.4.1 Deliverables (3): CDRL 0036 (Technical Report – Studies/Services).

1.3.3.5. The contractor shall provide an Implementation Plan to create and populate an AFSPC architecture repository. Supporting Air Force and DoD-level architecture repository efforts. Reference ACP Activity G3.1, G3.2, G3.3 and G3.4.

1.3.3.5.1. Deliverables (3): CDRL 0038 (Implementation Plan).

1.3.3.6. The contractor shall develop guidance for use, implementation and integration of architecture tools as part of the AFSPC corporate process. Reference ACP Activity G4.

1.3.3.6.1. Deliverables (3): CDRL 0036 (Technical Report – Studies/Services).

1.3.3.7. The contractor shall develop an AFSPC Net-Centric Integration Roadmap. This roadmap will apply net-centric tenets and standards, through the use of architecture principles, across all AFSPC missions, programs and systems.

1.3.3.7.1 Deliverables (3): CDRL 0036 (Technical Report – Studies/Services). This deliverable will include the strategy, schedule, milestones, checklists and way ahead.

1.3.3.8. The contractor shall assess progress of the AFSPC Campaign Plan activity accomplishments against the milestones identified in the ACP. Reference ACP Activity C.1.

1.3.3.8.1. Deliverables (3): CDRL 0036 (Technical Report-Study/Services).

1.3.3.9 The contactor shall develop a capability alignment matrix between the AFSPC Enterprise Architecture and up to twenty (20) AFSPC systems/programs with current architectures. An updated Architecture Metadata Sheet shall be developed for each system/program assessed to develop a capability alignment matrix.

1.3.3.9.1 Deliverables (3): CDRL 0036 Technical Report. This deliverable includes an Enterprise Architecture capability alignment matrix for up to twenty (20) systems/programs. CDRL 0035 Technical Report. This deliverable will include an Architecture Metadata Sheet for each system/program assessed to develop a capability alignment matrix.

1.3.4

REQUIREMENT 4:

In April 2002, USAF Program Action Directive (PAD) 01-04 named HQ AFSPC/SC (now A4A6) as the Single Communications Integrator for space systems. This PAD implemented the U.S. Space Commission recommendations for the Air Force (AF). It charged HQ AFSPC/SC to integrate fragmented network and information systems and processes into a single “infostructure”. This integration is crucial to the successful operations and sustainment of AFSPC Enterprise and the space and missile warning systems included therein.

1.3.4.1 The contractor shall develop and maintain the AFSPC “To Be” Architecture. “To Be” architecture products shall include the AV-1 (Overview and Summary), AV-2 (Integrated Dictionary), OV-1 (High Level Operational Concept Graphic), OV-2 (Operational Node Connectivity Description), OV-3 (Operational Information Exchange Matrix), OV-4 (Organizational Relationship Chart), and OV-5 (Operational Activity Model). Reference ACP Activity 4.1.

1.3.4.1.1 Deliverables (4): Using the most current version of the DoD Architecture Framework, “To Be” products shall include a single AV-1, AV-2, OV-1, OV-2, OV-3, OV-4 and OV-5. These products shall be built using the Popkin System Architect Enterprise Modeling Tool, Version 9.1.4.0 or higher.

1.3.4.2 The contractor shall develop a design approach (including bins and initial linkages) and spiral development schedule for the AFSPC Infostructure Architecture Dashboard. The design approach shall include identification of the applicable data, based on the design approach (bins and linkages). Based on the design approach, the contractor shall define the concept of operations (including posting location, purpose, users and user interface) for internal (HQ AFSPC) and external (AFSPC Wings) use of the AFSPC Infostructure Architecture Dashboard. In addition, the contractor shall revalidate Troux Metis as the best tool for the application, or identify other options.

1.3.4.2.1 Deliverables (4): CDRL 0036 Technical Report. This deliverable, dashboard design approach, shall include detail list of proposed bins and sub-bins, top-level linkage between bins and sub-bins and a graphical depiction (Power Point or graphic) of dashboard layout. CDRL 0036 Technical Report. This deliverable shall include a matrix or other format showing data required for each bin or sub-bin and initial source(s) of the data identified in the design approach. CDRL 0036 Technical Report. This deliverable shall include a Concept of Operations addressing use and sustainment of the dashboard format and content based on the design approach. CDRL 0036 Technical Report. This deliverable shall include a Spiral Development Schedule. CDRL 0036 Technical Report. This deliverable shall include a tool assessment and recommendation.

1.3.5 REQUIREMENT 5:

The contractor shall provide up to three (3) mission impact assessments using the DoD Architecture Framework products to include the impacts or changes to any part of the AFSPC Enterprise Architecture (defined in SOW Paragraph 1.1.1) mission capabilities. The contractor shall, within the current net-centric environment, identify the underlying dependences between the enterprise parts that are often difficult to discover, but are crucial to training, equipping, organizing and operational decision making.

1.3.5.1 Deliverables (5): CDRL 0036 (Technical Report – Study/Services).

1.3.6

REQUIREMENT 6:

The contractor shall provide technical and administrative support (agendas, action items, briefings, recommendations, conference logistics) for AFSPC, Air Force and DoD level architecture and net-centric councils, working groups and integrated product team meetings. The contractor shall also be responsible for building the necessary staff coordination packages. Contractor shall support approximately 2 conferences per month.

1.3.6.1 Deliverables (6):

(a) CDRL 0036 (Technical Report – Study/Services).

(b) CDRL 0004 (Conference Agenda)

(c) CDRL 0005 (Conference Minutes)

(d) CDRL 0008 (Presentation Materials)

(e) CDRL 0009 (Report, Record of Meeting/ Minutes)

1.3.7 REQUIREMENT 7: The contractor shall maintain a repository of architecture integration and net-centric success stories.

1.3.7.1 DELIVERABLES: CDRL 0036 (Technical Report – Study/Services).

1.3.8 ADDITIONAL DELIVERABLES: The contractor shall provide a monthly status report.

CDRL 0030 (Contractor’s Progress, Status and Management Report).

2.0 Service Delivery Summary.

1.3.2

1.3.3

1.3.4

1.3.5

1.3.6

1.3.7 1.3.8

1.3.9 No more than (1) late document per month and no more than (5) working days late. No more than (1) set of corrections or edits and all corrections must be accomplished within (5) working days

3.0 GOVERNMENT FURNISHED PROPERTY AND RESOURCES.

3.1 GOVERNMENT FURNISHED PROPERTY (GFP): No Government furnished property will be provided.

3.2 GOVERNMENT FURNISHED RESOURCES: A6II will furnish up to two workspaces in the Hartinger Building on Peterson AFB. Included with the workspace will be desk space, chair, computers connected to Peak Net, Secret Internet Protocol Router Network (SIPRNet) access, use of telephones, copier and fax machine.

3.3 MATERIALS AND OTHER DIRECT COSTS (ODCs): Two specific items are required for the performance of this task order: (a) purchase of current Popkin System Architect Enterprise Modeling Tool license renewal and (b) purchase of large plotter paper. For any other items, the QAE is required to provide prior approve for all contractor purchases costing less than $500. Any item exceeding this dollar threshold will require prior approval of the Contracting Officer prior to purchase.

4.0 GENERAL INFORMATION.

4.1 SECURITY: Provisions outlined in the basic DD 254 apply to this task order.

4.2 ACCESS TO GOVERNMENT PROPERTY AND FACILITIES: The contractor shall be allowed unescorted access to Government buildings on Peterson AFB and other sites consistent with the requirements of this Task Order.

4.3 TRAVEL: All travel to fulfill the tasks in this SOW shall be performed with the prior approval of the QAE in accordance with Federal Acquisition Regulation (FAR) Part 31.

4.3.1 TRAVEL ESTIMATES: The following travel is estimated per year of this Task Order.