About this file

SSA PWS

View the file

Other files for this federal contract opportunity

Other files attached to Advisory & Assistance Services & Systems Engineering & Technical Assistance Services for Headquarters, Air Force Space Command, newest first.
File Type Posted
Amendment 8 CSMC RFP.doc DOC document
CSMC RFP Amendment 6.doc DOC document
Block 13 Continuation Sheet 2 Oct 09.docx DOCX document
Amendment 5 Attachment L-3 MWMD PWS FINAL 29 Sep 09.doc DOC document
SF30 Summary of Changes - Amendment 4.doc DOC document
Amendment 4 Attachment L-3 MWMD PWS FINAL 25 Sep 09.doc DOC document
CSMC RFP 23 Sep 09 Amendment 3.doc DOC document
Amendment 3 Attachment L-3 MWMD PWS FINAL 23 Sep 09.doc DOC document
Attachment 1 CSMC PWS FINAL 21 Sep 09.docx DOCX document
Attachment 5 Section L Attachments 21 Sep 09.doc DOC document
SF30 Summary of Changes - Amendment 2.doc DOC document
Q A 22 Sep 09.doc DOC document
MILSATCOM CDRLs 29 9 Sep 09.rtf RTF text file
CDRLS Master List ILSS 11.rtf RTF text file
MILSATCOM CDRLs 30 9 Sep 09.rtf RTF text file
CDRLS Master List SESS 35 36.rtf RTF text file
Attachment 3 CSMC 254 24 Aug 09.pdf PDF
CDRLS Master List MGMT 29.rtf RTF text file
Attachment 2 Acronyms 22 Jul 09.doc DOC document
MWMD CDRLs 29 9 Sep 09.rtf RTF text file
CDRLS Master List SESS 37.rtf RTF text file
Rerevised Contract Mgmt Section.docx DOCX document
One-On-One Session Directions.pptx PPTX presentation
MILSATCOM 2 4 31 May 09.pdf PDF
Section L Past Performance Questionnaire.doc DOC document
9003-0043.doc DOC document
9003-0036.doc DOC document
9003-0035.doc DOC document
Market Research Questions.doc DOC document
A6-0176 CSMC PWS.docx DOCX document
A4 PWS 4 Sep 08.doc DOC document
9003-0019.doc DOC document
9003-0029.doc DOC document
9002-0014.doc DOC document
9002-0017.DOC DOC document
9002-0006.doc DOC document
9002-0009.doc DOC document
9002-0004.doc DOC document
9001-0004.doc DOC document
9001-0028.doc DOC document
9000-0018.doc DOC document
9000-0015.doc DOC document
9000-0027.doc DOC document
9000-0002.doc DOC document
9003-0034.doc DOC document
9000-0030.doc DOC document
9002-0026.doc DOC document
9001-0038.doc DOC document
CAASETAIPrimeandSubcontractorList.doc DOC document
2_MarketResearchQuestions.doc DOC document
Show all 50

Advisory & Assistance Services & Systems Engineering & Technical Assistance Services for Headquarters, Air Force Space Command has more files on GovTribe.

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

STATEMENT OF WORK

FOR

SUPPORT OF

HEADQUARTERS AIR FORCE SPACE COMMAND

DIRECTORATE OF REQUIRMENTS

Space Situational Awareness (SSA) and Command and Control (C2), Sensors & Space Superiority Systems Current As Of: 4 Nov 08

1.0 DESCRIPTION OF SERVICES: Headquarters Air Force Space Command (HQ AFSPC), Directorate of Requirements (A5), Space Situational Awareness/Command & Control Division (A5C) requires non-personal technical, system analysis, programmatic, and analytical support.

1.1 ORGANIZATION BEING SUPPORTED: HQ AFSPC/A5C (A5CI/CN/CS)

150 VANDENBERG ST., SUITE 1105

PETERSON AFB, CO 80914-4590

1.1.1 MISSION: Command and Control (C2) and Space systems and capabilities have become key to our nation’s military effectiveness. Without them, our military forces would not enjoy many of the advantages we currently have over our adversaries. Air Force Doctrine Document (AFDD) 2-8 “Command and Control,” and AFDD 2-2 “Space Operations,” emphasize the importance of C2 and space in achieving critical national objectives. It is Air Force Space Command’s (AFSPC’s) responsibility to organize, train, and equip forces for USSTRATCOM/JFCC SPACE by defining, developing, acquiring, fielding, testing, and sustaining C2 and Space systems and capabilities to exploit and control the “high ground.” AFSPC has organized space capabilities based on the functions they perform into the following four mission areas – inextricably linked via an effective C2 capability:

Space Force Enhancement Space Control Space Force Application Space Support

It is also AFSPC’s responsibility to field and sustain C2 capabilities for the North American Aerospace Defense Command (NORAD) in supp ort of the following missions:

Aerospace Warning Aerospace Control

The Air Force Space and the Command, Control, Communications, Computers, Intelligence, Surveillance, and Reconnaissance (C4ISR) Concept of Operations (CONOPS) identifies the capabilities needed by the Air Force to support Joint and Air Force missions. The Air Force Space Command Strategic Master Plan (SMP) then presents AFSPC’s vision for sustaining, modernizing, and transforming space and C2 capabilities to meet the growing warfighter demands for space-enabled capabilities to accomplish its assigned missions.

An essential element of the AFSPC vision is to provide net-centric, integrated, cost and operationally effective, responsive, and flexible Space Situational Awareness (SSA) and C2 capabilities that enable warfighters, at all levels, to quickly, accurately, and unambiguously:

Develop actionable information about the aerospace situation Monitor the world situation and identify operationally significant events Assess real or potential impacts of time-critical and evolving events and warn of attack against North America and US and allied space systems Plan operations to respond to changing situations and targets of opportunity Execute plans and direct and control forces to achieve strategic and tactical objectives Sustain the networks; support the training of space and C2 personnel; conduct, exercises, simulations and tests To provide and sustain these critical warfighter SSA, C2 and Sensor capabilities to the warfighters (NORAD, USSTRATCOM, JFCC SPACE, AFSPC), several SSA, C2 and Sensor modernization programs, projects, and initiatives are underway, such as the ones listed below (The acronym “ISSA/SC2/RB-20/STACS/CCIC2S” represent the required capability set currently requisite within those programs. The program names are subject to future change or restructure):

JSpOC Weapon System. A family of interdependent programs to produce a suite of net-centric space services for JFCC SPACE. Key current programs include the following:

Space C2 Operations. The space C2 system provides integrated space information and C2 of space forces for JFCC SPACE. The space C2 system will provide a net-centric, service-oriented technical implementation architecture that meets JFCC SPACE top priority requirements.

Integrated Space Situation Awareness (ISSA). ISSA improves the integration of the disparate data components of SSA to provide timely, actionable knowledge necessary for maintaining space superiority and exercising C2 of space forces.

Rapid Attack Identification, Detection and Reporting System (RAIDRS) Block 20 / Space Threat Assessment Characterization Service (RB-20/STACS). RB-20/STACS provides access to non-traditional data sources, data fusion and threat processing to detect and characterize attacks in support of the Defensive Space Control mission. Data fusion and characterization assists in anomaly characterization and response to hostile/non-hostile event in support of C2 for other joint space missions.

Combatant Commanders Integrated Command and Control System (CCIC2S). CCIC2S provides the fixed C2 nodes, communications processing and capabilities to support Commander, North American Aerospace Defense Command (NORAD), to execute NORAD assigned missions and the Commander, JFCC SPACE, to execute the missile warning mission.

1.2 OVERVIEW OF SERVICES REQUIRED

Support AFSPC/A5C requirements, analyses, planning, architecture, programming, budgeting and execution activities in support of the acquisition and fielding of SSA, C2 and Sensor systems and programs which include space, air, missile, command and control, unclassified as well as classified elements.

The Contractor shall provide life-cycle management, planning, and engineering and technical assistance to AFSPC/A5C to:

Analyze stated near, mid-range, and long term visions and needs of the supported warfighters.

Define and assess SSA, C2 and Sensor (e.g. Systems, sensors, architectures etc) alternatives/solutions for meeting those needs.

Develop roadmaps and/or master plans for implementing the preferred alternative/solution.

Provide operational advocacy for new SSA, C2 and Sensor capabilities and systems.

Integrate and synergize new AFSPC SSA, C2 and Sensor capabilities and systems with capabilities and systems being planned, developed, and delivered by other organizations.

Define, consolidate, and validate SSA, C2 and Sensor operational concepts, architectures, and requirements.

Provide an owner/operator/user/sustainer interface to the development and testing communities charged with defining, developing, testing, fielding and sustaining the required new SSA, C2 and Sensor system capabilities to ensure:

Warfighter needs are adequately understood, prioritized, and achieved, and That new system(s) comply with evolving top-down DoD, Air Force, and AFSPC visions, objectives, and guidance/direction.

Lead, support and/or coordinate activities to deliver Government “dependencies” critical to the success of the SSA, C2 and Sensor programs, projects, and initiatives.

Evolve AFSPC SSA, C2 and Sensor policies, processes, procedures, and procurements from “platform-centric” to “net-centric” “capabilities-based” acquisitions in accordance with DoD new and evolving direction.

1.3 SPECIFIC REQUIREMENTS

1.3.1 REQUIREMENT 1: PROGRAM, PROJECT AND PORTFOLIO MANAGEMENT SUPPORT

Program, Project and Portfolio Management Support includes the program management tasks required to provide on-going support to the customer throughout the Task Order period of performance.

The Contractor shall:

1.3.1.1 Provide an architecture laboratory for the development and maintenance of architectures at the Unclassified through TS/SCI security clearance levels.

1.3.1.1.1 Develop and operate a technical information facility with databases containing architecture program documentation material i.e., Department of Defense Architecture Framework (DoDAF), as approved by the government representative, up to and including Secret information and include monthly reports of new documents.

1.3.1.1.2 Establish and maintain access to Government unclassified (NIPRNet) and classified (SIPRNet) networks from the contractor’s facility to streamline information sharing.

1.3.1.1.3 Develop, maintain, and/or utilize unclassified, on-line, controlled-access electronic portal(s) at contractor facility to facilitate information sharing i.e., Enterprise Architecture (EA) products among geographically dispersed AFSPC SSA, C2 and Sensor program stakeholders.

1.3.1.1.4 Host weekly project working groups and provide graphic support to include technical interchange meetings for up to 100 people conducted up to and including the Secret Level and for up to 50 people conducted at the Top Secret/SCI level. (CDRL 0009)

1.3.1.1.5 The meetings will not necessarily be held at the contractor's facility and may require travel, as noted in section 4.4.

1.3.1.1.6 Develop and maintain a portfolio management process and database for advising and assisting AFSPC/A5 in the Planning, Programming, Budgeting, and Execution (PPBE) and Program Objective Memorandum (POM) processes by developing draft documents for financial actions such as budgeting, tracking, reporting Division financial obligations, expenditures .

1.3.1.1.7 Provide daily recommendations and/or deliverables (i.e., briefs, point paper, command position) on higher headquarters’ tasking to AFSPC/A5 representative and ensure actions and submissions are worked expeditiously and comply with suspenses (approximately 700 formal taskers per year and 35-50 informal taskers per week).

1.3.1.1.8 Draft approximately 8 to 10 Memoranda of Agreements (MOAs) and Memoranda of Understanding (MOUs) per year among required agencies (e.g., DoD, NASA, NOAA, etc.) on SSA, C2 and Sensor systems and projects for approval by the government.

1.3.1.1.9 Draft approximately 3 to 5 organization and/or group Charters for assigned SSA, C2 and Sensor systems and projects per year for approval by the government.

1.3.1.2 DELIVERABLES (1): CDRL 0009 Report, Record of Meeting/Minutes

1.3.2 REQUIREMENT 2: STRATEGIC PLANNING, SSA AND C2 ADVOCACY, RESOURCE MANAGEMENT, AND HORIZONTAL AND VERTICAL CAPABILITY INTEGRATION SUPPORT

1.3.2.1 STRATEGIC PLANNING SUPPORT

The Contractor shall support the Joint Capabilities Integration and Development System (JCIDS) to identify, define, prioritize, and advocate SSA, C2 and Sensor solutions to meet current and future warfighter needs.

The Contractor shall:

1.3.2.1.1 Develop and maintain a portfolio management process and database for advising and assisting AFSPC/A5 in Air Force and AFSPC JCIDS analyses to ensure SSA, C2 and sensor capabilities, needs, and solutions are included in all related Air Force and AFSPC Mission Area Plans (MAPs) and Mission Support Plans (MSPs). Provide planning, engineering, and technical support for AFSPC Functional Area Analyses (FAA), Functional Needs Analysis (FNA), and Functional Solution Analysis (FSA), and Post Independent Analysis methodologies in support of requirements production.

1.3.2.1.2 Participate in the Air Force Technical Planning Integrated Product Teams (TPIPTs) on an ongoing basis as AFSPC/A5 representatives:

1.3.2.1.2.1 Identify materiel and non-materiel solutions to provide the needed mission capability specified from the FSA analysis;

1.3.2.1.2.2 Identify the proposed modernization strategy/approach to implement the AFSPC preferred solution(s) to include resource estimates and schedules;

1.3.2.1.2.3 Identify and recommend prioritization of new technologies to effectively develop, field, and sustain systems required to eliminate/mitigate mission deficiencies

1.3.2.1.2.4 Identify and characterize the nature of linkages/dependencies between the SSA, C2 and Sensor plans and Air Force MAPs.

1.3.2.1.3 Develop and provide written SSA, C2 and Sensor input to AFSPC Mission Area Plans and the Strategic Master Plan, Air Force MAPs and MSPs, and NORAD and USSTRATCOM C4 planning processes and documentation to the AFSPC/A5 representatives.

1.3.2.1.4 Review and assess policies, directives, and guidance that relate and integrate with SSA, C2 and Sensor systems to provide technical assessments, reports, and briefings identifying the impacts of on-going “Enterprise-wide” developments on AFSPC SSA, C2 and Sensormodernization programs, projects, and/or initiatives.

1.3.2.1.5 Provide AFSPC/A5 representative with technical assessments, reports and briefings to the “Enterprise” community i.e., Joint Forces Command (JFCOM), Air Combat Command (ACC), Missile Defense Agency (MDA) regarding the AFSPC SSA, C2 and Sensorvision, concepts, objectives, and modernization roadmap to ensure AFSPC SSA, C2 and Sensor capabilities are effectively synergized and integrated into the Enterprise architecture.

1.3.2.1.6 Provide AFSPC/A5 representative technical assessments, reports, and briefings with recommendations to leverage “Enterprise-wide” architecture developments to more effectively and efficiently define, develop, field, and sustain the SSA, C2 and Sensor programs and initiatives. (CDRL 0036)

1.3.2.2 SSA, C2 AND SENSOR ADVOCACY SUPPORT

The Contractor shall support AFSPC in advocating for materiel and non-materiel SSA, C2 and Sensor solutions to warfighter needs identified by the JCIDS. The Contractor shall:

1.3.2.2.1 Provide analysis of existing documentation (i.e., JCIDS products) to develop defensible business cases for SSA, C2 and Sensor modernization programs, projects, and initiatives.

1.3.2.2.2 Prepare and assist AFSPC/A5 representatives in advocating AFSPC position by participating in a variety of verbal or written forums to obtain community “buy-in” for AFSPC SSA, C2 and Sensor modernization programs, projects, and initiatives.

1.3.2.2.3 Prepare and provide written inputs for JCIDS documentation, Combatant Commanders’ Integrated Priority Lists (IPLs), and PPBE products to the AFSPC/A5 representatives. These documents are required to obtain senior leadership advocacy for AFSPC SSA, C2 and Sensor modernization programs, projects, and initiatives.

1.3.2.3 SSA, C2 AND SENSOR RESOURCE MANAGEMENT SUPPORT

Develop and maintain a portfolio management and work breakdown structure (WBS) process with database for assisting AFSPC/A5 in developing products to secure and defend resources for AFSPC SSA, C2 and Sensor modernization programs, projects, and initiatives; document, track, and report actual and planned resource utilization; assess impacts of funding changes, and; prepare and present AFSPC/A5-approved impacts to senior decision makers. The Contractor shall:

1.3.2.3.1 Review and assess annual Planning, Programming, Budgeting, and Execution (PPBE) strategic guidance (i.e., Strategic Planning Guidance (SPG), Joint Programming Guidance (JPG), Annual Planning and Programming Guidance (APPG), Capability Required Risk Assessment (CRRA)).

1.3.2.3.2 Recommend strategies to support financial management of AFSPC SSA, C2 and Sensor modernization program(s).

1.3.2.3.3 Recommend strategies and provide written inputs to AFSPC/A5 representative to support the “build” of the POM / Budget Estimate Submission (BES) and President’s Budget (PB) for AFSPC SSA, C2 and Sensor modernization programs, projects, and initiatives.

1.3.2.3.4 Draft operational impact statements and consequences of budget cuts to defend AFSPC SSA, C2 and Sensor modernization program(s) during Program Budget Decision (PBD) and Reclama, and “cut drills” processes.

1.3.2.3.5 Develop annual draft strategies and provide written inputs to support the development of Execution Plans (ExPLANs).

1.3.2.3.6 Provide analysis during the development of annual Requirements Documents (R-Docs) and Procurement Documents (P-Docs) to ensure research and development and procurement strategies are consistent with program objectives.

1.3.2.3.7 Draft inputs, assess changes, and produce reports within Automated Budget Interactive Data Environment System (ABIDES) to assist in defending SSA, C2 and Sensor program budgets.

1.3.2.4 HORIZONTAL AND VERTICAL CAPABILITY INTEGRATION SUPPORT

Utilize a portfolio management process and database for advising and assisting AFSPC in horizontally and vertically integrating AFSPC-provided SSA, C2 and Sensor capabilities. The Contractor shall:

1.3.2.4.1 Apply AFSPC/A5 approved Enterprise Architectures (EA) developed by the contractor to identify SSA, C2 and Sensor program required capabilities and identify their relationships and dependencies to other AFSPC, Air Force, and Joint programs.

1.3.2.4.2 Coordinate with the development community (i.e., primarily Electronic Systems Command (ESC), Space and Missile Systems Center (SMSC)) to integrate the DoDAF-compliant SSA, C2 and Sensor EA Operational and Technical Standards Views with the development community’s Systems Views.

1.3.2.4.3 Utilize a portfolio management process to assist the development community in using the EA and approved operational requirements documents i.e., Capability Development Documents (CDDs) in defining SSA, C2 and Sensor Technical Requirements ensuring operational requirements are fully addressed.

1.3.2.4.4 Identify and track disconnects (cost, schedule, and performance) among SSA, C2 and Sensor programs and draft action plans to resolve disconnects.

1.3.2.4.5 Participate in JSpOC Weapon System and other integration IPTs and working groups (i.e., JSpOC Weapon System Engineering and Integration IPT and SSA/Space C2 IPT) using portfolio management and WBS to facilitate cost, schedule, and performance integration recommendations to AFSPC/A5.

1.3.2.4.6 Provide recommendations, in the form of technical reports, technical assessments, and briefings to effectively integrate AFSPC capabilities among programs. (CDRL 0036)

1.3.2.5 DELIVERABLES (1): CDRL 0036 Technical Report – Study/Services

1.3.3 REQUIREMENT 3: DEVELOP CONCEPTS OF OPERATIONS AND ARCHITECTURE, TO ENSURE INTEGRATED OPERATIONAL REQUIREMENTS.

The Contractor shall provide advice and assistance, planning, and system engineering and technical guidance to develop DoDAF-compliant architectures, Concepts of Operations (CONOPS), and operational requirements in accordance with the JCIDS analysis process. Under the JCIDS context, the Contractor shall develop architecture products, CONOPS, and other documents such as Initial Capability Documents (ICD), Capability Development Documents (CDDs) and Capability Production Documents (CPDs) in the framework of joint concepts and integrated architectures that reflect future capability shortfalls and technological opportunities.

1.3.3.1 ARCHITECTURE DEVELOPMENT

The Contractor shall, for assigned SSA, C2 and Sensor functional areas, capabilities, and/or systems:

1.3.3.1.1 Purchase and maintain Rational Software Model, Rational Software Architect and Rational Rose/Team Unified Platform, equipment and licenses necessary to use/maintain existing architectural products, as well as to develop and deliver DoDAF-compliant architecture models employing state-of-the-art object-oriented (OO) Unified Modeling Language (UML) methodologies to: (CDRL 0025).

1.3.3.1.1.1 Allow the warfighter and developer to visualize key actors, roles and responsibilities, functional processes, operational event sequences, and information exchanges required to provide the capability stipulated in the JCIDS analysis process.

1.3.3.1.1.2 Serve as a tool for integrating new capabilities with relevant DoD, Air Force, other Services and AFSPC “Enterprises”.

1.3.3.1.1.3 Serve as the framework for developing CONOPS and operational requirements.

1.3.3.1.1.4 Provide a detailed visual model of the linkages between required operational capabilities and the solution developed to enable those capabilities.

1.3.3.1.2 Vet the architectures in a collaborative architecture lab environment with warfighters, owner/operators, developers, testers, sustainers, and other agencies, to ensure the expected system behavior depicted in the architecture is accurate and clearly understood.

1.3.3.1.3 Update and maintain currency of the architectures, to respond to changes in threats, missions, requirements, organizational changes and associated changes in roles and responsibilities, interfaces, and new capabilities that may present themselves as a result of emerging technology.

1.3.3.1.4 Coordinate and provide technical assessments, reports and briefings to obtain and document formal Government approval of the baseline architectures and proposed changes.

1.3.3.1.5 Develop, coordinate and provide the government representative technical reports and briefings to provide explanations of the application of the architecture methodology used in SSA, C2 and Sensor programs, projects, and initiatives.

1.3.3.1.6 Utilize automated visualization tool to provide insight to SSA, C2 and Sensor personnel into the actual execution of capabilities as articulated in the EAs.

1.3.3.1.7 Utilize automated tools to the greatest extent possible to produce products not currently supported by IBM Rational Rose or Rational Software Modeler (RSM). Capabilities of such tools can include, but not be limited to, the auto-production of OV-2’s and “use case” specifications.

1.3.3.1.8 Promote and exploit re-use of common architecture products and/or artifacts within AFSPC, and other DoD architectures.

1.3.3.1.9 Structure and deliver the architecture models as formal version releases (CDRL 0036) (CDRL 0025) and such in a manner that they can be easily presented at classification levels up-to and including Top Secret/SCI. Contractor shall deliver formal releases with Version Description Documents and supporting white papers to explain the content and methodology of the releases to AFSPC.

1.3.3.1.10 Ensure consistency among the architectures, CONOPS, operational requirements, and provide AFSPC/A5 representative technical reports and briefings that identify disconnects and recommended corrective actions.

1.3.3.1.11 Provide AFSPC with the methodology used for bridging Operational Views to System Views maintaining traceability from the requirement inception.

1.3.3.1.12 Assess and provide AFSPC/A5 representatives reports and briefings on the impacts of policy changes, CONOPS evolutions and technology advancements on current and planned AFSPC SSA, C2 and Sensor architecture development efforts and associated programs, projects, and initiatives, such as, Net Enabled Command and Control (NECC), Net Centric Enterprise Services (NCES), Global Information Grid (GIG), RAIDRS, Sensors and other associated SSA.

1.3.3.1.13 Identify and comply with governing architecture policies (i.e., DoDAF) and architecture technology (i.e., OO/UML) which bear on the evolution of the AFSPC architecting method.

1.3.3.2 CONCEPT OF OPERATIONS DEVELOPMENT

The Contractor shall, for assigned SSA, C2 and Sensor functional areas, capabilities, and/or systems. (CONOPS encompasses Enabling Concepts, Employment Concepts, Operating Concepts, etc.):

1.3.3.2.1 Develop and deliver AFSPC-compliant CONOPS, capitalizing on the content of all associated architectures, to communicate how new capabilities/systems and individual capability/system “increments” will be employed in the context of the systems origin, mission, operations, security, safety, logistics, planned future (evolution).

1.3.3.2.2 Vet CONOPS in a collaborative environment with warfighters, owner/operators, developers, testers, sustainers, and other agencies to ensure the concept of operations is accurate, clearly understood and the resulting system meets the warfighters’ and sustainers’ needs.

1.3.3.2.3 Update and maintain currency of CONOPS to respond to changes in threats, missions, requirements, organizational changes and associated changes in roles and responsibilities, interfaces, new capabilities that may present themselves as a result of emerging technology, changes in spiral development/evolutionary acquisition strategies (i.e., Increment content), and fiscal constraints.

1.3.3.2.4 Coordinate and provide AFSPC/A5 representative technical reports and briefings to obtain and document formal Government approval of the baseline CONOPS and proposed changes.

1.3.3.2.5 Provide AFSPC/A5 representative CONOPS traceability analyses to ensure consistency among the architectures, CONOPS, operational requirements, system architectures, technical architectures and provide technical reports that identify disconnects and recommended corrective actions.

1.3.3.3 OPERATIONAL REQUIREMENTS DEVELOPMENT

The Contractor shall, for assigned SSA, C2 and Sensor functional areas, capabilities, and/or systems draw upon experiences with existing CCIC2S requirement documents (i.e., Mission Need Statement, Operations Requirements Document (ORD), Air Force Form 1067s) in order to further develop products IAW the JCIDS processes:

1.3.3.3.1 The contractor will continually initiate/update new requirements documents IAW the JCIDS process in support of SSA , C2 and Sensor modernization programs, projects, and initiatives.

1.3.3.3.1.1 Update and maintain currency of operational requirements documents to respond to changes in threats, missions, operational concepts, requirements, policies, organizational changes and associated changes in roles and responsibilities, interfaces, new capabilities that may present themselves as a result of emerging technology, changes in spiral development/evolutionary acquisition strategies, and fiscal constraints (e.g., as the program progresses through its acquisition phases).

1.3.3.3.2 Coordinate and provide to AFSPC/A5 representatives technical assessments, reports, and briefings to obtain and document formal Government approval of the baseline requirements documents and proposed changes.

1.3.3.3.3 Provide AFSPC/A5 representatives requirements traceability analyses to ensure consistency among the architectures, CONOPS, operational requirements, system architectures, technical architectures, and test plans and provide technical assessments, reports and briefings that identify disconnects and recommended corrective actions.

1.3.3.3.4 Support organizations developing joint and Air Force CONOPS and requirements, and provide technical assessments, reports and briefings communicating AFSPC recommendations to synergize joint and Air Force operational requirements with SSA, C2 and Sensor operational requirements being developed by AFSPC.

1.3.3.3.5 Assess and provide AFSPC/A5 representatives technical assessments, reports and briefings regarding the impact of joint and Air Force CONOPS on current and planned AFSPC SSA, C2 and Sensor operational requirements and associated programs, projects, and initiatives.

1.3.3.3.6 Draft, update, maintain, and deliver a government approved Requirements Maturity Matrix (RMM) to AFSPC/A5 representative consisting of the quantifiable requirements from the approved SSA, C2 and Sensor Systems JCIDS documents to complement the SSA, C2 and Sensor architectures as a “Build-to” document for the designated development contractors and a “Test-to” document for the designated SSA, C2 and Sensor modernization Operational Test Agency.

1.3.3.3.7 Provide AFSPC/A5 representatives advice and assistance in planning, system engineering, analytical support to integrated product and capability teams charged with developing the spiral development/evolutionary acquisition strategy to prioritize the incremental fielding of SSA, C2 and Sensor capabilities to achieve operational requirements.

1.3.3.4 DELIVERABLES (3): CDRL 0036 Technical Report – Study/Services CDRL 0025 Software Version Description

1.3.4 REQUIREMENT 4: LIFE-CYCLE SYSTEMS ENGINEERING AND TECHNICAL ASSISTANCE

The Contractor shall provide life-cycle system engineering and technical services for AFSPC SSA, C2 and Sensor modernizations programs, projects and initiatives and their major components and provide technical support to the logistics community in developing cost and operationally effective sustainment strategies, concepts, plans, and procedures. The major SSA, C2 and Sensor modernization initiatives currently in work are JSpOC Weapon System and NORAD C2 modernization.

1.3.4.1 System engineering as it applies to this task consists of the activities that must be accomplished to transform an operational need into an operationally and cost effective warfighter capability. This will entail:

1.3.4.1.1 transforming an operational need into a description of the system configuration that best satisfies the operational need according to measures of effectiveness

1.3.4.1.2 integrating related technical parameters and ensure compatibility of all physical, functional, and technical program interfaces. (Reference: System Engineering Capability Maturity Model-95-01)

1.3.4.2 RISK MITIGATION SUPPORT

1.3.4.2.1 The Contractor shall provide system engineering and technical assistance support to reduce the risk to successfully developing, field, testing, and sustaining on-going AFSPC SSA, C2 and Sensor programs, projects, and initiatives on a continuing basis.

1.3.4.2.2 For new and on-going programs, projects, and/or initiatives, the Contractor shall provide recommendations, inputs or courses of actions to AFSPC/A5 representatives:

1.3.4.2.2.1 Provide advice and assistance in planning, and engineering support for the development of AoAs.

1.3.4.2.2.2 Assist in the development of draft cost/resource estimates and budget inputs in support of AFSPC A5 representatives.

1.3.4.2.2.3 Utilize modeling activities to ensure system architecture proposals meet minimal essential processing, throughput, and growth requirements and provide technical assessments, reports, and briefings of findings.

1.3.4.2.2.4 Attend JCIDS-required program reviews to enhance understanding of system design, evaluate requirements flow down, designs, and specialty engineering areas and provide technical assessments and recommendations in the form of meeting minutes.(CDRL 0009)

1.3.4.2.2.5 Evaluate designs and concepts including military utility tradeoff analyses, engineering analyses, economic analyses, risk assessments, mathematical analyses, analytical models, performance predictions, simulations, and prototypes.

1.3.4.2.2.6 Evaluate technical and programmatic impacts of evolving system requirements on system engineering and development phases and assist in developing detailed programming, implementation, and transition plans to allocate responsibilities and schedule milestones for the affected missions and programs.

1.3.4.2.2.7 Ensure approved policies, procedures, processes, and standards impacting SSA, C2 and Sensor are being consistently and uniformly applied throughout assigned programs and projects and provide technical assessments, reports and briefings identifying disconnects, impacts, and risk mitigation recommendations.

1.3.4.2.2.8 Review program Master Schedules and provide technical assessments, reports, and briefings to provide schedule assessments and recommendations to ensure:

1.3.4.2.2.8.1 All key tasks are identified and effectively integrated

1.3.4.2.2.8.2 Adequate time is allocated for task accomplishment

1.3.4.2.2.8.3 Resource contention challenges are identified and mitigated

1.3.4.2.2.8.4 Implementation of systems fielding strategies minimize impacts to on-going mission operations

1.3.4.2.2.9 Assess “trends” to identify performance, cost, and schedule risks.

1.3.4.2.2.10 Provide planning and system engineering support to deliver, or coordinate the delivery of Government-provided facilities, hardware, software, communications, manpower, interfaces, etc. to successfully field the war fighting capability.

1.3.4.3 TRAINING SUPPORT

The Contractor shall provide system engineering and technical assistance to define, develop, implement, and sustain the full spectrum of training required for AFSPC SSA, C2 and Sensor modernization programs, projects, and initiatives. The Contractor shall provide recommendations, inputs or courses of actions to AFSPC/A5 representatives to:

1.3.4.3.1 Incorporate use cases into training system(s) mirroring operational requirements and CONOPS.

1.3.4.3.2 Support AFSPC Representatives by developing draft cost, operational training strategies and approaches for the government’s SSA/C2 efforts with the development community (i.e., primarily ESC and SMSC).

1.3.4.3.3 Support the development of System Training Plans (STPs) and a Master Training Plan.

1.3.4.3.4 Support development of training system scenarios.

1.3.4.3.5 Review development, fielding, testing, and sustainment plans to ensure they are consistent with approved use cases, operational requirements, and training concepts, and then provide technical assessments, reports and briefings, to identify training status, disconnects, and recommendations for corrective actions.

1.3.4.3.6 Assess the design and development of training systems (i.e., Cheyenne Mountain Training System (CMTS)) to ensure they provide operationally effective life-cycle training capabilities for the warfighter and sustainer, and develop and deliver technical assessments, reports, and briefings regarding adequacy, issues, and recommendations.

1.3.4.4 INFORMATION ASSURANCE (IA) ANALYSIS AND IMPLEMENTATION SUPPORT

The Contractor shall provide system engineering and technical assistance support to define, develop, implement, and sustain capabilities to safeguard sensitive unclassified and classified information required by AFSPC SSA, C2 and Sensor modernization programs, projects, and initiatives.

The Contractor shall provide recommendations, inputs or courses of actions to AFSPC/A5 representatives while:

1.3.4.4.1 Supporting the development and/or aggregation of Security Classification Guides.

1.3.4.4.2 Developing and delivery of security “use cases” for incorporation in architectures, security operational requirements documents and security concepts of operations; support the development of security test plans to meet the SSA, C2 and Sensor modernization programs.

1.3.4.4.3 Reviewing development, fielding, testing, and sustainment plans to ensure they are consistent with approved security use cases, operational requirements, and system security concepts, and provide technical assessments, reports and briefings, to identify security status, disconnects, and recommendations.

1.3.4.4.4 Supporting the conduct of security tests and evaluations, evaluate test results, and provide technical assessments, reports and briefings on the ability of the system to meet system security operational requirements and concepts.

1.3.4.4.5 Supporting IA controls assignment and validation process.

1.3.4.4.6 Supporting the development of Plans of Action and Milestones (POA&Ms) for AFSPC SSA, C2 and Sensor modernization systems.

1.3.4.4.7 Ensuring that data management and sharing policies and required security classification guidelines are developed for SSA, C2 and Sensor Systems.

1.3.4.4.8 Assisting SSA, C2 and Sensor Information Assurance and Security Vulnerability Management working groups by advocating AFSPC/A5 positions and concerns.

1.3.4.5 TESTING & EVALUATION, EXERCISE, AND WARGAMING SUPPORT

The Contractor shall provide planning, system engineering and technical assistance support to define, develop, implement and sustain methodologies and capabilities to: a) test AFSPC SSA, C2 and Sensor modernization programs, projects, and initiatives, to ensure they meet warfighter requirements and b) ensure delivered systems can conduct and support integrated and stand-alone exercises and wargames.

The Contractor shall provide recommendations, inputs or courses of actions to AFSPC/A5 representatives to:

1.3.4.5.1 Implement based on lessons learned from organizations and services, i.e. Joint Staff, Air Force, NORAD, USSTRATCOM tests and exercise operations in order to develop “use cases” for incorporation into operational requirements documents, CONOPS, and existing architectures.

1.3.4.5.2 Develop Critical Operational Issues (COIs), Measures of Effectiveness (MOEs), and Measures of Performance (MOPs) for SSA, C2 and Sensor modernization programs, projects, and initiatives, tied to Key Performance Parameters (KPPs).

1.3.4.5.3 Review operational requirements documents and provide technical assessments, reports and briefings containing recommendations to ensure requirements are testable.

1.3.4.5.4 Support the test community (i.e., Air Force Operational Testing and Evaluation Center (AFOTEC), SPO, developer, warfighter, 17th Test Squadron) in developing cost and operationally effective test strategies, concepts, plans, and procedures and ensure they:

1.3.4.5.4.1 Are consistent with National, DoD, Joint Staff, NORAD, USSTRATCOM, Air Force, and AFSPC direction regarding development, fielding, and sustainment of net-centric, service oriented architectures.

1.3.4.5.4.2 Address operational mission and support requirements.

1.3.4.5.4.3 Provide an assessment of system operational capability against stated requirements.

1.3.4.5.4.4 Do not unnecessarily impact mission operations.

1.3.4.5.5 Support development of system test scenarios by the test community.

1.3.4.5.6 Support the test community in the development of test documents by advocating AFSPC/A5 positions and concerns.

1.3.4.5.7 Assist the Combined Test Force to identify testing resources (hardware, software, facilities, manpower, funds) needed for an operational combined test.

1.3.4.5.8 Review development, fielding, testing, and sustainment plans to ensure consistency with approved test and exercise/wargaming “use cases”, operational requirements, and test and exercise/wargaming concepts to provide technical assessments, reports and briefings, to identify test and exercise/wargaming status, disconnects, and recommendations.

1.3.4.5.9 In support of the development community, assess the design and development of the testing subsystems (e.g., scenario data generators/injectors) to ensure they provide cost life-cycle testing and exercise/wargaming capabilities for the warfighter and sustainer, and develop and deliver technical assessments, reports and briefings regarding adequacy, issues, and recommendations.

1.3.4.5.10 Support test community to coordinate / schedule testing resources, conduct test planning, and post test analyses, as requested, for Developmental Testing and Evaluation (DT&E), Operational Test and Evaluation (OT&E) to include Force Development Evaluation (FDE) testing, Operational Assessments (OA), Operational Utility Evaluations (OUE), Interoperability OT&E (IOT&E), Follow-on OTE&E (FOT&E) and provide technical assessments, reviews, reports and briefings delineating strategies, results, and/or recommendations relating to these tests.

1.3.4.6 SITE ACTIVATION SUPPORT

The Contractor shall assist AFSPC A5 in planning, system engineering and technical assistance support to define, develop, and implement methodologies and capabilities to stand-up new operational facilities and/or transition existing command, operations and support centers from legacy to new AFSPC SSA, C2 and Sensor modernization programs, projects, and initiatives.

The Contractor shall provide recommendations, inputs or courses of actions to AFSPC/A5 representatives to:

1.3.4.6.1 Perform facility studies in the context of relevant programs, projects, initiative architectures, operational requirements, and operational and support concepts.

1.3.4.6.2 Employ human factors engineering, electrical engineering, survivability, endurability, environmental engineering, communications and network engineering, and associated engineering disciplines to best support specific system installation and operation.

1.3.4.6.3 Draft operational requirements for command, operations, and support centers affected by site modifications / activations.

1.3.4.6.4 Assist AFSPC A5 representatives with site activation working groups to guide the activation of new centers or modifications of existing centers.

1.3.4.6.5 The Contractor shall develop and maintain high fidelity 3-dimensional (3-D) virtual models (CDRL 0036) of designated command, operations, and/or support centers (to include mission equipment and connectivity), linked to a resource database and conduct design reviews.

1.3.4.6.6 The Contractor shall provide facility and/or associated resource information in 3-D graphics, 2-D graphics, engineering drawings, and/or text format (CDRL 0036) in electronic and hardcopy media.

1.3.4.7 DELIVERABLE (3):

CDRL 0009 Report, Record of Meeting/Minutes CDRL 0036 Technical Report – Study/Services

1.4 ADDITIONAL DELIVERABLES (1):

CDRL 0030 Contractor’s Progress, Status & Management Report

1. SERVICE SUMMARY

Performance Objective
SOW Para.
Performance Threshold

Contractor develops the following architecture products required to articulate operational and/or system behaviors:

a. UML 2.0 use cases for expressing requirements

b. UML EA version releases using IBM Rational Rose and Rational Software Modeler

c. SoDA reports

d. Animated UML scenarios/models

e. UML Activity Model

f. UML Use Case Overview Diagram

g. UML Sequence Diagram

h. UML Context Diagram

i. UML Class Diagram

j. UML Class Relationship Diagram

k. UML Communication Diagram

l. UML Collaborations

1.3, 1.4
Contractor develops the following products IAW current DoD Information Information Technology Standards (DISR) for UML modeling as prescribed by the IBM Rational RUP-SE process and the Object Management Group (OMG) and within timelines as required by JCIDS.
Deliverables are completed in an accurate and timely manner
ALL

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

All requirements of the Task Order are met
ALL

Contractor receives no more than 2 formal, validated customer complaints/contract discrepancy reports per year. The contractor successfully resolves customer complaints within 10 calendar days of receipt, 100% of the time.

3.0 GOVERNMENT FURNISHED PROPERTY AND RESOURCES:

3.1 GOVERNMENT FURNISHED PROPERTY (GFP): None

3.2 GOVERNMENT FURNISHED RESOURCES.

3.2.1 FACILITIES, SUPPLIES, AND SERVICES: AFSPC/A5C will furnish up to fifteen workstations in the Hartinger building on Peterson AFB, desk space, chairs, computers connected to NIPRNet; and Secret Internet Protocol Router network (SIPRNET) access, use of telephones, copier and fax machines. AFSPC/A5C will provide pro-rated NIPRNet and SIPRNet leased circuits costs to one contractor facility. In addition the Government will provide DSN access to one contractor facility.

3.2.2 INFORMATION SOURCES: The Government team will interact with the contractor to corroborate, provide technical input, answer questions, review/accept completed work, and provide feedback regarding contractor efforts. The QAE is the primary source of technical guidance for this SOW.

3.2.3 GOVERNMENT FURNISHED INFORMATION:

3.2.3.1 The current CCIC2S / JSpOC Weapon System Enterprise Architecture Release Version.

3.2.4 DOCUMENTATION: The contractor will be provided access to Government-owned applicable documents, reports, and briefing materials, including classified materials up to TS/SCI for use in transitioning contract work from existing to newly awarded contracts.

3.3 MATERIALS AND OTHER DIRECT COSTS (ODCs): Four software licenses (Rational Software Modeler, Rational Software Architect, Rational Rose and Team Unified Platform) are required for the performance of this task order. The Contractor shall be authorized to purchase these items costing less than $500 with QAE approval. An item exceeding this dollar threshold shall require approval from the Contracting Officer prior to purchase.

1. GENERAL INFORMATION

4.1 SECURITY. Access for up to 15 SCI and Special Access Program (SAP) level systems and information is required for this task order.

4.2 ACCESS TO GOVERNMENT PROPERTY AND FACILITIES: The contractor will be allowed unescorted access to Government buildings on Peterson AFB/Cheyenne Mountain and other sites consistent with Task Order requirements. Access to Government facilities, documents, and systems shall be in accordance with the basic award DD254.

4.3 SERVICES DURING CRISIS: The performance of these services is non-mission essential during times of crisis. Should a crisis be declared, the Contracting Officer or their representative will verbally advise the contractor if temporary suspension of work is required, followed by a written notification. A representative of the contracting officer will further notify the contractor verbally when the crisis has ended with written notification to follow. Any price changes resulting from this crisis will be negotiated in accordance with FAR clauses for “Changes”.

4.4 TRAVEL: The following travel is estimated in support of this task order.

Travel. Any travel required to fulfill the tasks in this PWS shall be performed with the prior approval of the QAE in accordance with Federal Acquisition Regulation (FAR) Part 31. The Contractor shall be responsible for making travel arrangements for their personnel, including air travel, car rental, lodging and subsistence. Contractor employees may be required to travel to various locations within the continental United States (CONUS) and outside the continental United States (OCONUS) in performance of task orders. Estimated travel requirements are included below. All contractor travel shall be approved by the Government prior to departure. Any travel required shall be performed in accordance with FAR 31.205-46, Travel Costs.

Destination
Estimated Number of Trips
Estimated Duration

(Days)

Alexandria, VA
1
3
Arlington, VA
5
5
Camp Smith, HI
1
6
Fairfax, VA
2
3
Hampton, VA
1
4
Langley AFB, VA
2
3
Los Alamos, NM
1
2
Los Angeles, CA
4
8
Montgomery, AL
1
3
Omaha, NE
1
2
Ottawa, Canada
1
4
Vandenberg AFB
16
5
Washington D.C.
3
3
Wright-Paterson AFB, OH
1
3

1.3.1.3.2. Passports, Visas, Customs, and Travel. All contractor employees are subject to customs, processing procedures, laws, agreements, and duties of the country to which they are traveling and procedures, laws, and duties of the United States upon re-entry. The Government will supply the Contractor with letters of travel when necessary to travel by Military Airlift.

4.4.1 Any travel required to fulfill these required tasks in this SOW shall be approved by the QAE prior to actual travel and reimbursed IAW FAR 31.205-46. Local travel is defined as within 50 miles of Peterson AFB. The Contractor shall fund all local travel.

4.5 INTERNATIONAL TRAFFIC IN ARMS REGULATION (ITAR): The contractor shall be required to exchange detailed technical data (Controlled Unclassified Military Information (CUMI) and/or Classified Military Information (CMI)) with Canadian, Australian, and United Kingdom military personnel assigned to AFSPC under the terms of this task order. Based on this requirement, the contractor must apply for the appropriate export authorization, in accordance with the International Traffic in Arms Regulations (ITAR), 22 CFR Chapter 1, Subchapter M, Parts 120-130, immediately upon award of the task order. Export authorization guidance can be accessed at http://pmddtc.state.gov.

4.6 DATA RIGHTS: The Government will retain ownership of all drafts, supporting documentation, and products developed under this contract. The Government retains distribution authority for all products resulting from this effort. The Government also has unlimited right to all data and deliverables developed under this contract. Material developed under this contract will not be utilized outside of this contract unless authorized by the QAE.

4.4. Place of Performance

AFSPC/A3FS will furnish up to two workspaces in the Hartinger building on Peterson AFB, to include desk space, chairs, computers connected to 21 NET, Secret Internet Protocol Router network (SIPRNET) access, use of telephones, copier, fax machines and additional media storage. Any other contractor personnel shall work at contractor facilities.

4.5. Duty Hours

When working on government sites, the government’s normal duty hours are 0730-1630, Monday through Friday, unless otherwise specified in individual task orders. Circumstances may require the Contractor to provide services after normal duty hours.

***CDRLS***

***Attached*** DD Form 1423-2, CDRL 0009 Dated 21 April 2008 DD Form 1423-2 CDRL 0025 Dated 21 April 2008 DD Form 1423-2, CDRL 0030 Dated 21 April 2008 DD Form 1423-2, CDRL 0036 Dated 21 April 2008

ANNEX A: SPACE FENCE PROGRAM PLANS AND REQUIREMENTS SUPPORT

1.2 OVERVIEW OF SERVICES REQUIRED: The Contractor shall provide planning and technical services support for HQ AFSPC/A5C. This support includes: requirements document development, assistance with the preparation of Study Plans and AoAs for new programs, Concepts of Operations (CONOPS) development, Program Objective Memorandums (POM), and program planning development (e.g., Strategic Master Plan, Mission Area Plans) for Space Control/Space Superiority programs managed by HQ AFSPC/A5C. The Contractor shall support across HQ AFSPC organizations and interface other DoD, Joint and civilian agencies as appropriate. The Contractor shall also support appropriate, planning and development forums for developing technical analysis in support of HQ AFSPC. The Contractor shall also assist AFSPC/A5C with staff functions to include reviewing documents, writing point papers, and preparing briefings.

1.3 SPECIFIC REQUIREMENTS:

1.3.1 REQUIREMENT 1: The Contractor shall provide operational and system requirements support to AFSPC/A5C. The Contractor shall support requirements activities in direct support of the Space Fence program and related SSA programs for AFSPC/A5C. This requirement represents approximately 25% of this TO.

1.3.1.1 The Contractor shall participate in Air Force and AFSPC JCIDS analyses to ensure capabilities, needs and solutions are comprehensively included in Air Force and AFSPC Mission Area Plans (MAPs) and Mission Support Plans (MSPs). The process shall include providing planning, engineering and technical support for AFSPC Functional Area Analysis (FAA), Functional Needs Analysis (FNA), and Functional Solution Analysis (FSA) methodologies.

1.3.1.2 The Contractor shall assist AFSPC/A5C draft requirements documents (ICD, CDD, CPD); coordinate these documents through AFSPC, Air Force, and joint communities; and prepare briefings for requirements strategy reviews (RSRs) and Air Force Required Operational Capabilities Council (AFROCC) and Joint Requirements Oversight Council (JROC) staffing.

1.3.1.3 The Contractor shall assist AFSPC/A5C develop training requirements and training concepts for incorporation in requirements and CONOPS…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .