ITWAA-SEI PWS.pdf

Integrated Tactical Warning & Attack Assessment (ITW/AA) Systems Engineering and Integration (SE&I) Performance Work Statement (PWS)

1. PURPOSE

ITW/AA Enterprise Stakeholders require SE&I expertise for end-to-end systems analysis, assessment, engineering and integration activities at the enterprise level. The Chief Scientist Office (CSO) requires expertise in coding, aerodynamics and aeronautical engineering.

2. SCOPE

This Performance Work Statement (PWS) defines the requirements for ITW/AA Enterprise Stakeholder Support. The contractor will be providing SE&I expertise across ITW/AA related to interface verification, system deployment, operations and sustainment. The contractor supports Chief Scientist actions and tasks supporting Global Threat Characterization and Assessment (GTCA). Additionally, the contractor will interface with key ITW/AA stakeholders from North American Aerospace Defense Command (NORAD), United States Space Command (USSPACECOM) and United States Space Force (USSF), as well as stakeholders Nuclear Command and Control (NC3), Space System Command (SSC) Air Warning (also known as Aerospace Control), Sensor Information sources, Data processing nodes (i.e. Operations centers), and Forward / End Users that network or interface to the ITW/AA network.

Ensure the ITW/AA operational requirements receive the necessary level of ITW/AA change control management related to interface analyses, integration issues, and collaboration with key stakeholders for continued mission data integrity and accuracy.

Acts as the liaison for interfacing mission systems and the focal point for facilitating standardized review, assessment, coordination, control, planning, and baseline management of interface requirements.

3. REQUIREMENTS

3.1 Systems Engineering

3.1.1 Life-Cycle Systems Engineering

The contractor shall use disciplined systems engineering to include system architecture, integrated risk management, and configuration management in accordance with AFI 63- 101/20101, Integrated Life Cycle Management. The contractor shall identify dependencies and enforce standards of interaction between programs throughout the lifecycle.

3.1.2 Subject Matter Expertise

The contractor shall possess the advanced knowledge, experience and recognized ability to be considered a Subject Matter Expert (SME) in North Cheyenne Mountain Center (NCMC) ITW/AA, Ground Based Radars. Additionally, having an understanding of agile processing would be beneficial due to future contract constructs. Lastly, the contractor will demonstrate advanced theater mission expertise/knowledge of their technical/professional discipline as well as possess a comprehensive understanding and ability to apply associated standards. Proficient knowledge with CCI2S and SEWS Programs included in experience and past performance. Expertise/knowledge of strategic mission and policies is required. The capability to integrate future technologies such as datalinks and relational tools.

Functionally aligned minimum education and experience will include: Bachelor’s Degree and 12 years of experience in the respective technical/professional discipline being performed, of which 3 years include ITW/AA domain experience. This requirement is applicable to all subject matter experts/engineers who will complete the tasks associated with this PWS.

3.1.3 Training

Contractor personnel are required to possess the skills necessary to support their company’s minimum requirements of the labor category under which they are performing. Training necessary to meet minimum requirements will not be paid for by the Government or charged to the task order by Contractors.

3.1.4 Mission-Unique Training

In situations where the Government organization being supported requires some unique level of support because of program and/or mission-unique needs, then the contractor may directly charge the task order on a cost reimbursable basis for the unique training necessary to support those needs. Unique training required for successful support must be specifically authorized by the Contracting Officer (CO). Labor expenses and travel related expenses may be allowed to be billed on a cost reimbursement basis. Tuition/Registration/ Book fees (costs) may also be recoverable on a cost reimbursable basis if specifically authorized by the CO.

The agency requiring the unique support must document the contract file with a signed memorandum that such contemplated labor, travel, and costs to be reimbursed by the Government are mission essential and in direct support of unique or special requirements to support the billing of such costs against the task order.

3.2 ITW/AA Enterprise Systems Engineering and Integration (SE&I) Controls The SE&I contractor shall use SE&I controls to develop processes and deliver products within the

PWS.

The contractor SE&I controls shall address the following requirements:

• Manage, control, and analyze ITW/AA interface requirements. The ITW/AA Integrator will work closely on a regular basis with the unified combatant commands (NORTHCOM, USSTRATCOM), NORAD, AFSPC, ITW/AA and non-ITW/AA program offices, as well as the relevant ITW/AA change control forums regarding ITW/AA network and interface requirements. The ITW/AA Integrator will maintain a record (have access to) of the applicable and current ITW/AA network and interface requirements to be used for analyzing ITW/AA interface requirements.

• Assess integration issues within the ITW/AA enterprise

• Maintain currency of Master Message Catalog data content which resides within the

Integrated Database System Support (IDSS ) database and briefs the status to USSPACECOM Functional Managers Office (FMO) (NOTE: this is not maintaining the IDSS database maintenance and configuration). Interface with missile warning stakeholders on a periodic basis to collect relevant inputs on program status, coordinate with system points of contacts regarding pertinent information across affected programs and strengthen the working relationship. Attend system level program reviews as appropriate to enhance interactions and information sharing related to data updates/impacts to associated systems.

• Pro-actively identify potential cross programs activities and inter-program dependencies which results in a version controlled Watch Item List

• Analyze, assess, and rank order a Watch Item List of potential ITW/AA issues

• Manage ITW/AA systems listed in IDSS database. Identify and compare program baselines for recommended changes within IDSS. Implement data changes

• At the ITW/AA program level, the contractor shall maintain and evolve Government approved engineering management control processes

• Maintain a list of system points of contact (POCs) to facilitate collaboration of change impacts

• Tracks proposed changes to the ITW/AA system interfaces, provides analysis to and suggesting resolution of integration issues between systems supporting the ITW/AA mission prior to an actual change

• Monitors the implementation of changes to ensure mission integrity

• This effort includes establishment of an Integrator Configuration Control Board and a requirements management process for the IWSD and SCF portions of the IISIS tool.

This process will include a method for managing changes to the appropriate portions of the IISIS tool while maintaining requirements consistency/traceability.

• Record the official copies of relevant Interface Control Documents (ICDs) within the IWSD. The ITW/AA Integrator will coordinate with ICD owners to provision the “official” ICDs to be maintained in the IWSD. However, the approval authority for any ICD changes remains with the owner or SPO and the Integrator does not have responsibility for ICD maintenance. Coordinate with owners of systems and system interfaces for ICD updates to be included in IWSD. Ensure consistency with the Program of Record (POR) and their system documentation.

• Validate external interface data. External interface data must be validated for non- ITW/AA systems communicating with the ITW/AA system to ensure ITW/AA mission integrity. This activity focuses on validating external interface data for non-ITW/AA systems to ensure all interface documents and message formats are accurately represented and incorporated. Significant coordination and interaction is required with SMEs, sites and programs, other commands and common users to support this activity, validate documentation, and ensure data currency and accuracy.

• Monitor Key Performance Parameters (KPPs) supports monitoring Key Performance Parameters (KPPs) and evaluating ITW/AA performance data to assure end-to-end system timelines meet performance timelines established per CJCSI 6210. This effort includes coordination and collaboration with other program offices for collection and analysis of TPE event data.

• Identify ITW/AA performance and capability gaps and to provide relevant performance/capability improvement recommendations. The ITW/AA Integrator monitors or requests information from various testing activities related to key platform performance and mission capability and KPP thresholds, as well as performing the necessary performance analyses. This activity includes identifying and briefing the ITW/AA Operations Approval Board (OAB) on ITW/AA C2 System-of-systems risks.

This effort also looks at future changes with potential ITW/AA performance and capability impacts.

3.2.1 ITW/AA Enterprise External and Internal Stakeholder CM

The contractor shall participate, document, execute and evolve the ITW/AA Enterprise CM process to provide configuration identification, control, status accounting and audits of the

ITW/AA Enterprise. (Contract Data Requirements List (CDRL) A001 Technical Report Study/Services)

Maintain Configuration Management of IWSD and SCFDB3 includes establishment of an Integrator Configuration Control Board and a requirements management process for the IWSD and SCF portions of the IISIS tool. This process will include a method for managing changes to the appropriate portions of the IISIS tool while maintaining requirements consistency/traceability.

Record the official copies of relevant Interface Control Documents (ICDs) within the IWSD.

The ITW/AA Integrator will coordinate with ICD owners to provision the “official” ICDs to be maintained in the IWSD. However, the approval authority for any ICD changes remains with the owner or SPO and the Integrator does not have responsibility for ICD maintenance.

Coordinate with owners of systems and system interfaces for ICD updates to be included in IWSD. Ensure consistency with the Program of Record (POR) and their system documentation.

The ITW/AA Integrator will track ITW/AA schedules to create and maintain an integrated master schedule. This master schedule will show milestones and integration dependencies of new systems or system upgrades. After an analysis of the schedule the Integrator can highlight possible impacts to ITW/AA system interfaces. This effort includes coordinating with system program offices and owners on program schedules; creating a master integrated schedule (leveraging the existing ESC/HSI integrated schedule and the test master schedule);

analyzing the milestones and dependencies for ITW/AA impacts; and tracking and reporting on watch items or issues.

3.3 SE&I Execution

3.3.1 ITW/AA Enterprise Master Planning (EMP)

The contractor shall maintain an ITW/AA Enterprise Master Plan (EMP) describing key activities necessary to accomplish enterprise requirements. (CDRL A001 Technical Report Study/Services)

3.3.2 ITW/AA Enterprise “To-Be” Architecture

The contractor shall control and maintain an ITW/AA Enterprise “To Be” architecture to reflect the “As Is” as modified by the funded program(s) of record capabilities. (CDRL A001 Technical Report Study/Services)

The contractor shall validate the architecture against the approved enterprise requirements baseline.

The contractor shall identify missing, incomplete or inaccurate architectural elements (e.g.

data not available, unfunded approved or unmet requirements, etc.). (CDRL A001 Technical Report Study/Services) The contractor shall recommend corrective actions to fill in missing information and implement as directed. (CDRL A001 Technical Report Study/Services)

3.3.3 Chief Scientist Support

Support HBQ Chief Scientist actions and tasks supporting Global Threat Characterization and Assessment (GTCA), Missile Warning Algorithm Working Groups and Missile Warning Database updates

Identify means to improve missile warning and characterization of events including emerging threats.

Conduct modeling analysis, reviews and updates to algorithms. Evaluate algorithms against changing operational threats. Evaluate message data sets for algorithmic improvement opportunities. Validate accuracy of message data sets based on algorithmic comparisons. Research and modify algorithms based on emerging technological advances. Review database files for errors and required changes and then update those files as required. Ensure database integrity through regression testing (verification and validation) and system modeling using database analysis tools. Perform / support testing of database updates.

3.4 Meetings and Communications

Organize meetings and milestones in the SE&I process in order to facilitate recommendations for configuration changes to the ITW/AA systems and interfaces. Facilitate interchange meetings to assist in resolving interface issues

Maintain distro list of customers for MWDB updates on a quarterly basis Coordinates materials from across the ITW/AA stakeholder and contributor communities supporting updates to USSPACECOM for GTCA

Shall act as lead, operationally knowledgeable, facilitator guiding discussions on incorporation and integration of data sources into PORs with the end goal of a harmonized display through all phase of conflict across theater and strategic missions

Solicits and Coordinates materials from across the ITW/AA stakeholder and contributor communities for presentation/discussion at MWAWGs

Coordinate and publicize integration milestones and meeting schedules to concerned organizations. This effort includes staffing final documents through the branch (and division if needed), posting information on the Integrator SharePoint site (includes calendar of meetings, announcements and documents), maintaining the ITW/AA Integrator mailbox, and sending out notifications to stakeholders and other appropriate organizations.

The ITW/AA Integrator will assist in resolving integration issues between systems assigned to other SPOs supporting the ITW/AA system by participating in Technical Information Meeting (TIM) discussions to identify risks and interoperability/integration resolution issues (including capacity assessments and evaluations) that cross program boundaries. This activity also includes data gathering from other program offices to minimize system information ambiguities and to augment IISIS content. The ITW/AA Integrator will also track ITW/AA Communications, Interoperability and Integration Risks/Issues. As part of this activity, the ITW/AA Integrator will operate and maintain an automated tool for recording and tracking ITW/AA communications, interoperability and integration risks and issues (such as RISKNAV or similar Risk Management Tool). The intent is to also publicize this information for collaboration and information sharing purposes with stakeholder community.

Interface with missile warning stakeholders on a periodic basis to collect relevant inputs on program status, coordinate with system points of contacts regarding pertinent information across affected programs and strengthen the working relationship. Attend system level program reviews as appropriate to enhance interactions and information sharing related to data updates/impacts to associated systems.

Interface with air warning information sources and stakeholders on a periodic basis to collect relevant inputs on program status, coordinate with system points of contacts regarding pertinent information across affected programs, and strengthen the working relationship.

Attend program and system level reviews as appropriate to ensure relevant information is validated, coordinated and ready for dissemination across affected programs and/or ITW/AA systems.

Interface with sensor information sites on a periodic basis to collect relevant inputs on program status, coordinate with system points of contacts regarding pertinent information across affected programs and strengthen the working relationship. Attend system level program reviews as appropriate to information is validated and coordinated and ready for dissemination across affected programs.

Interface between nodes operations centers on a periodic basis to collect relevant inputs on program status, coordinate with system points of contacts regarding pertinent information across affected programs and strengthen the working relationship. Attend system level program reviews as appropriate to information is validated and coordinated and ready for dissemination across affected programs.

Interface between communications information sources on a periodic basis to collect relevant inputs on program status, coordinate with system points of contacts regarding pertinent information across affected programs and strengthen the working relationship. Attend system level program reviews as appropriate to information is validated and coordinated and ready for dissemination across affected programs.

3.4.1 ITW/AA Enterprise Working Group (IEWG)

Serve as the Secretariat for the IEWG providing both administrative support and SE&I expertise to facilitate discussions between programs

3.4.2 Missile Algorithm Working Group

Serve as the Secretariat for the Missile Algorithm Working Group providing both administrative support and SE&I expertise to facilitate discussions between programs.

3.4.3 Interface Control Working Group (ICWG)

Chair the ICWG to provide a forum to ensure proposed modifications to the ITW/AA System and their interfaces support the successful implementation and deployment of changes. The ICWG coordinates with the external system interfaces, such as, Space Based Infrared System, Upgraded Early Warning Radars, Early Warning Radars, forward users, and others;

while complementing those systems processes and compliance with NI 10-3 and SI 534-22.

As needed, the ICWG will elevate issues above their authority through the appropriate CCM processes, OAPs, Communications and Architecture Panel (CAP) and if needed up to the OAB and Mission Oversight Board (MOB).

3.4.4 (Optional Task – Not currently being performed) Performance Working Group

(PWG)

Chair the PWG to provide a forum to address the technical performance characteristics of the ITW/AA System under “high load” scenarios. The ITW/AA C2 PWG leverages vertical release test events, USSTRATCOM/J65 TPE events, CMAFS Systems Center and the CCIC2S Performance Model to capture and assess technical performance characteristics. As needed, the PWG will elevate issues above their authority using the appropriate CCM processes, OAPs, CAP and if needed up to the OAB and MOB.

3.4.5 (Optional Task Pending SPI 34221.01 ) Integration and Engineering Sub-Group

(IESG)

Co-Chair the IESG

• Conducts overall ITW/AA System of systems integration and engineering, ensuring compliance and integrity for the full ITW/AA system (not limited to CCIC2S), working with the various ITW/AA sub-system operators, SPOs, and sustainers, as well as external organizations as required.

• Request/direct internal and external ITW/AA organizations work together to integrate and harmonize systems of systems changes to fully field an updated operational capability on all systems at once in an expeditious manner (including MW Database changes, version releases, other system changes, modifications, and/or updates, etc).

• As part of the IESG, develop AF Form 1067’s and/or corollary SCFs in response to SCFs, as necessary artifacts of impact determination, resourcing, and material development.

• The IESG will declare the priority of the SCF, based on need date, mission impact, and other factors. The IESG will direct the affected SPO(s) to provide an initial assessment of system modifications to IESG/Force Provider for baseline determination and potential impacts. The IESG may SPI 3422.01 DD Full Month XXXX B-6 Enclosure B utilize and/or request from various organizations or members of the ITW/AA/NC3 Enterprise community numerous types of data/analysis/tools to assist with and inform decisions, to include mission/operational performance results/shortfalls/risks, predicted or actual performance data, architecture diagrams, communications link needs and assessments, etc.

3.5 (Optional Task) ITW/AA Enterprise Threat Assessments.

The SE&I contractor shall identify means to improve missile warning (also known as Aerospace Warning) and characterization of events including emerging threats. The SE&I contractor supports Chief Scientist actions and tasks regarding Global Threat Characterization and Assessment (GTCA).

The SE&I contractor shall conduct modeling analysis, reviews and updates to algorithms. The contractor shall:

- Evaluate algorithms against changing operational threats

- Evaluate message data sets for algorithmic improvement opportunities

- Validate accuracy of message data sets based on algorithmic comparisons

- Research and modify algorithms based on emerging technological advances

- Review database files for errors and required changes and then update those files as required

- Ensure database integrity through regression testing (verification and validation) and system modeling using database analysis tools

- Perform / support testing of database updates

- Conduct operational effectivity analyses of Display changes resulting from potential lab-based algorithmic and data sourcing changes

4. CONTRACTUAL REQUIREMENTS

4.1 Place of Performance

The primary place of performance will be the Contractor’s Facilities. The Government will not provide any permanent work space to Contractor personnel. The Contractor shall perform work at the Contractor's facility, various temporary meeting locations at PAFB, Cheyenne Mountain Air Force Station (CMAFS), and other locations within the greater Colorado Springs CO region (work at a Government facility shall be coordinated in advance with the COR).

The contractor’s logistics must be able to support sending its key personnel to onsite meetings at PAFB within one hour of notice from the Air Force as required (the Air Force will not reimburse the contractor for travel costs related to meetings at PAFB, CMAFS, or within the greater Colorado Springs region). Travel outside of the greater Colorado Springs region (including PAFB and CMAFS) may be required and shall be coordinated with the COR and CO in advance.

4.2 Normal Hours of Operation/Business Hours

The average work week shall be 40 hours. The average work day is 8 hours and the window in which those 8 hours may be scheduled is between 6:00 AM and 6:00 PM, Monday through Friday, except for days listed as Federal Holidays.

Federal Holidays:

New Year's Day Martin Luther King, Jr. Day

George Washington’s Birthday Memorial Day Independence Day Labor Day Columbus Day Veterans Day Thanksgiving Day Christmas Day

Government surveillance of Contractor performance shall be utilized to ensure that the Contractor is meeting the requirements of this PWS.

4.3 Government Furnished Property

The Government will provide access to equipment, data, documentation, systems, sites, processes, tools, etc. to ensure appropriate Contractor support for the ITW/AA Enterprise mission. Contractors will be provided Government furnished laptops that will allow access to sites and data on NIPRNet. No other property will be turned over to the Contractor as

GFP/GFE.

4.4 Morale and Recreation

There may be occasions when support contractors are invited to participate in morale and recreational activities (i.e., holiday parties, golf outings, sports days and other various social events). Contractor employees shall not be directed to attend such events by the Government. Since a contract employee is not a Government employee, the contract employee cannot be granted the same duty time activities as Government employees.

Participation in such events is not billable to the task order and Contractor employee participation should be IAW the employees, company’s policies and compensation system.

4.5 Non-Personal Services

The Government will neither supervise Contractor employees nor control the method by which the Contractor performs the required work. Under no circumstances shall the Government assign work to, or prepare work schedules for, individual Contractor employees.

It shall be the responsibility of the Contractor to manage its employees and to guard against any actions that are of the nature of personal services, or give the perception of personal services. If the Contractor feels that any actions constitute, or are perceived to constitute personal services, it shall be the Contractor’s responsibility to notify the Contracting Officer (CO) immediately. These services shall not be used to perform work of a policy/decision making or management nature, i.e., inherently Governmental functions. All decisions relative to programs supported by the Contractor shall be the sole responsibility of the Government.

These operating procedures may be superseded by Theater Commander’s direction during deployments.

4.6 Contractor Identification

All Contractor/Subcontractor personnel shall be required to wear AF-approved or provided picture identification badges so as to distinguish themselves from Government employees while at a Government facility.

When conversing with Government personnel during business meetings, over the telephone or via electronic mail, Contractor and Subcontractor personnel shall identify themselves as such to avoid situations arising where sensitive topics might be better discussed solely between Government employees.

Contractors and Subcontractors shall identify themselves on any attendance sheet or any coordination documents they may review.

Electronic mail signature blocks shall identify their company affiliation.

4.7 Performance Reporting

The Contractor’s performance will be monitored by the Government and reported in Contractor Performance Assessment Reports (CPARs) or a Customer Survey depending on the dollar amount of the contract.

Performance standards shall include the Contractor’s ability to provide or satisfy the following:

Provide satisfactory solutions to requirements with the necessary customer support

• Provide solutions and services that meet or exceed specified performance parameters

• Deliver timely and quality deliverables to include accurate reports and responsive proposals

• Ensure solutions to requirements are in compliance with applicable policy and regulation

4.8 Program Management / Project Management

The Contractor shall identify a Program Manager or a Project Manager who shall be the primary representative responsible for all work under this task order, participating in Program/Project Management Reviews and ensuring all standards referenced herein are adhered to.

4.8.1 Contract Management

The Contractor shall establish and provide a qualified workforce capable of performing the required work. The workforce may include a project/contract manager who will oversee all aspects of the task order.

The Contractor subject matter experts who will be completing the technical tasks associated with this PWS are considered “key personnel” by the Government. If a key person, for whatever reason, is no longer providing support for this task order, the Contractor shall notify the Government immediately upon learning of the key person’s departure from this task order.

The Contractor shall then provide the Government with the resumes for any proposed replacement personnel, and shall give the Government 72 business hours to concur or reject the new proposed key person. Any resumes submitted to the Government for a key person shall outline that individual’s qualifications as they relate to the requirements in this PWS.

During the period of performance the Government reserves the right to request that any Contactor staff, including key personnel, be replaced by the Contractor with or without cause.

The Government shall not be responsible for the recruitment costs related to replacing and on -boarding any Contractor staff that leave are no longer providing support for this task order, including any instances where the Government requests the removal of a Contractor staff member.

During a period when a key person is in the process of being replaced, the Contractor shall ensure that the tasks associated with this PWS are still being completed in a manner satisfactory to the Government.

The Contractor shall institute and maintain a process that ensures problems and action items discussed with the Government are tracked through resolution and shall provide timely status reporting. Results of contractor actions taken to improve performance shall be tracked, and lessons learned incorporated into applicable processes. See Attachments IV thru VII for the CDRL’s applicable to this task order and their respective requirements (Specifically, CDRL A001 Technical Report Study Services; CDRL A002 Status Report).

4.8.2 Records, Files, and Documents

All physical records, files, documents, and work papers, provided and/or generated by the Government and/or generated for the Government in performance of this PWS, maintained by the contractor which are to be transferred or released to the Government or successor contractor, shall become and remain Government property and shall be maintained and disposed of IAW AFMAN 33-363, Management of Records; AFI 33-364, Records Disposition

– Procedures and Responsibilities; the Federal Acquisition Regulation, and/or the Defense

Federal Acquisition Regulation Supplement, as applicable. Nothing in this section alters the rights of the Government or the Contractor with respect to patents, data rights, copyrights, or any other intellectual property or proprietary information as set forth in any other part of this PWS or the Application Services contract of which this PWS is a part (including all clauses that are or shall be included or incorporated by reference into that contract).

4.8.3 Personnel Security

Individuals performing work under this task order shall comply with applicable program security requirements as stated in this PWS.

This task order requires all contractor personnel to have a minimum of an active Top Secret/Sensitive Compartmentalized Information (TS/SCI) Security Clearance and requires that all contractor employees be United States citizens.

The contractor shall ensure all personnel obtain adequate security clearances prior to performing services under this task order.

The Contract Security Classification Specification (Attachment VIII - DD Form 254) will be at the task order level and will encompass all security requirements.

All contractors located on military installations shall also comply with Operations Security (OPSEC) requirements as set forth in DoD Directive 5205.02, Operations Security Program and AFI 10-701, Operations Security. IAW DoD 5200.2-R, Personnel Security Program (Jan 87), DoD military, civilian, consultants, and Contractor personnel using unclassified automated information systems, including email, shall have, at a minimum, a completed favorable National Agency Check plus written inquiries (NACI). In cases where access to systems such as email is a requirement of the Government, application/cost for the Personnel Security Investigation (PSI) shall be the responsibility of the Government.

Acquisition planning must consider Anti-Terrorism (AT) measures when the effort to be contracted could affect the security of operating forces (particularly in-transit forces), information systems and communications systems IAW DoD Instruction 2000.16, AntiTerrorism Standards.

4.8.3.1 Transmission of Classified Material

The contractor shall transmit and deliver classified material/reports IAW the DoD 5220.22-M, National Industrial Security Program Operating Manual.

4.8.3.2 Protection of System Data

The contractor shall protect system design-related documents and operational data whether in written form or in electronic form via a network in accordance with all applicable policies and procedures for such data, including DoD Regulation 5400.7-R, Freedom of Information Act Program, and DoD Manual 5200.01(v1-v4), DoD Information Security Program, to include latest changes, and applicable service/agency/ combatant command policies and procedures.

The contractor shall protect system design related documents and operational data at least to the level provided by Secure Sockets Layer (SSL)/Transport Security Layer (TSL)-protected web site connections with certificate and or user ID/password-based access controls.

In either case, the certificates used by the contractor for these protections shall be DoD or IC approved Public Key Infrastructure (PKI) certificates issued by a DoD or IC approved External Certification Authority (ECA) and shall make use of at least 128-bit encryption.

4.8.3.3 System and Network Authorization Access Requests

For contractor personnel who require access to DoD, DISA, or Air Force computing equipment or networks, the contractor shall have the employee, prime or subcontractor, sign and submit a System Authorization Access Report (SAAR), DD Form 2875.

4.8.4 Travel

Travel may be required to Buckley, AFB, CO, Hanscom AFB, MA, Offutt AFB, NE and/or Los Angeles AFB, CA as well as other pop-up locations. If the contractor is required to travel outside of the greater Colorado Springs, CO area then the contractor shall follow the travel instructions in the next two paragraphs.

The contractor shall coordinate any travel requests with the COR, and any vendor travel requests shall be submitted by the COR to the CO for approval in writing in advance of the travel.

The contractor shall submit the request for travel in writing via email and include the dates, locations and estimated costs of the travel.

If any travel arrangements cause additional costs to the task order that exceed those previously negotiated, written approval by CO is required prior to undertaking such travel.

The contractor shall submit travel costs in accordance with FAR Part 31.205-46, Travel Costs and the Federal Travel Regulations (FTR).

The contractor shall travel using the lower cost mode commensurate with the mission requirements.

When necessary to use air travel the contractor shall use economy class or similar accommodations to the extent they are available and commensurate with the mission requirements. Travel will be reimbursed on a cost reimbursable basis; no profit, overhead, or fee will be paid.

4.8.5 Other Government-Provided Training

The contractor employees may participate in other Government provided training, on a non-discriminatory basis as among contractors, under the following circumstances: The contractor employees’ participation is on a space-available basis.

• The contractor employees’ participation does not negatively impact performance of this

PWS.

• The Government incurs no additional cost in providing the training due to the Contractor employees’ participation.

• The training participation is approved by the COR in advance of the training in writing.

4.9 Data Rights and Non-Commercial Computer Software

In order to implement the provisions at DFARS 252.227-7013(b) and (e) and DFARS 252.227- 7014(b) and (e) and DFARS 252.227-7017, the Contractor shall disclose to the ordering CO and ordering office in any proposal for a contract, or after award of a contract if not previously disclosed in the proposal, any technical data or non-commercial computer software and computer software/source code documentation developed exclusively at government expense in performance of the task order. This disclosure shall be made whether or not an express requirement for the disclosure is included or not included in the PWS or solicitation for the order. The disclosure shall indicate the rights asserted in the technical data and noncommercial computer software by the contractor and rights that would be acquired by the government if the data or non-commercial software was required to be delivered under the contract and its CDRL requirements and any cost/price associated with delivery. This disclosure requirement also applies to segregable routines of non-commercial software that may be developed exclusively at Government expense to integrate Commercial Software components or applications provided under a commercial software license or developed to enable Commercial Software to meet requirements of this PWS. Performance of this disclosure requirement shall be considered a material performance requirement of any contract under which such technical data or non-commercial computer software is developed exclusively at Government expense.

4.10 Data Rights

The data rights ownership/licensing guidance is specified in Section I, Clause 252.227-7013 and 252.227-7015.

4.11 Enterprise Software Initiative

In situations where the purchase of new COTS software is needed to satisfy the requirements of the task order, the Contractor shall use available existing enterprise licenses. If enterprise licenses are unavailable, then products will be obtained via the DoD Enterprise Software Initiative (ESI) Blanket Purchase Agreements (BPAs). The updated listing of COTS software available from DoD ESI sources can be viewed on the web at: http://www.esi.mil. Any software expenses must be approved by the COR and CO in writing before purchase.

4.12 Transition Period

Any vendor selected for award of this task order, other than the incumbent vendor, will be required to participate in a two month transition period from 01 September 2022 to 01 November 2022. The transition period tasks are limited to participating in meetings with Government stakeholders, obtaining the point of contact (POC) list from the incumbent contractor, and participating in the November 2017 IEWG meeting and other meetings requested by SCC at Peterson Space Force Base, CO.

The new vendor will not be providing direct performance of the tasks in the PWS during the two month transition period. Therefore, its level of effort during the transition period should be limited to the effort necessary to participate in the transition period meetings stated in this section with full performance of the tasks beginning on 02 November 2022(or two months after the date of award, whichever is later).

5. SERVICES DELIVERY SUMMARY

The Contractor shall meet the requirements described in Section 3 of this PWS.

5.1 Contractor Performance Requirements

Table 1 depicts the Contractor Performance Requirements.

Table 1. Contractor Performance Requirements

Performance Requirements Performance Threshold Monitoring Method http://www.esi.mil/ http://www.esi.mil/

Accuracy – Contractor performance met specifications of the task order.

Contractor met requirements in the TO 95% of the time and received no more than two (2) written (e.g., email) customer complaints per month concerning contractor deficiencies relating to the task order requirements.

Identified deficiencies were successfully corrected within five (5) workdays of notification.

COR monthly review of performance metrics and feedback from Government team

Timeliness – Contractor met required delivery schedule. This element applies to task order performance including timely submission of all deliverables identified in the task order.

Contractor met requirements in the TO 95% of the time and received no more than two (2) written (e.g., email) customer complaints per month concerning contractor deficiencies relating to the task order requirements.

Identified deficiencies were successfully corrected within five (5) workdays of notification.

COR monthly review of performance metrics and feedback from Government team

DATA DELIVERABLES

The Government requires all deliverables that include Scientific and Technical Information (STINFO), as determined by the Government, be properly marked IAW DoD Instruction 5230.24, Distribution Statements on Technical Documents, and AFI 61-201, Management of Scientific and Technical Information, prior to initial coordination or final delivery. Failure to mark deliverables as instructed by the Government will result in non-compliance and non-acceptance of the deliverable.

The Contractor shall include the proper markings on any deliverable deemed STINFO regardless of media type, stage of completeness, or method of distribution. Therefore, even draft documents containing STINFO and STINFO sent via email require correct markings.

Additionally, the Contractor shall formally deliver as a CDRL all intellectual property, software, licensing, physical records, files, documents, working papers, meeting minutes, and other data for which the Government shall treat as deliverable.

The Government will identify instructions for each CDRL using a DD Form 1423-1. Table 2 depicts the CDRLs using a DD Form 1423-1.

Table 2. CDRL 1423-1

Sequence Number

Data Item Description

Title or Subtitle PWS Reference(s)

A001 DI-MISC-80508B Technical Report-Study/Services 3.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.5, 3.3.1, 3.3.1.1, 3.3.2, 3.3.3, 3.3.4, 3.3.5

A002 DI-MGMT-80368A Status Report 4.8.1

A003 Alternate Cost Report 4.8.1

APPLICABLE STANDARDS AND REFERENCES

Table 3 depicts the Standards and References for the Contractor to follow.

Table 3. Standards and References Forms/Publication Description Location sCJCSI 6210.02C Information and Operational

Architecture of the Integrated Tactical Warning and Attack Assessment System, 15 Nov 2013 - Classified

Restricted access – available after task order award

Strategic Command Instruction 534-22

Mission Integrity, Change Control Management, and test Control For The Integrated Tactical Warning and Attack Assessment (ITW/AA) System, 25 Mar 2011 (supersedes SI 508- 10, 12 Jul 06)

Restricted access – available after task order award

North American Aerospace Defense (NORAD) Instruction 10-3

Mission Integrity, Change Control Management, and Test Control For The Integrated Tactical Warning and Attack Assessment (lTW/AA) System, 9 Sep 2011

Restricted access – available after task order award

AFI 63-131 Modification Management, 12 May 2015, and AFSPC Supplement, 16 Jul 2015 http://static.e-publishing.af.mil/production/1/s af_aq/publication/afi63131/afi63-131.pdf

Forms/Publication Description Location sStandard Change

Form (SCF)

ITW/AA Standard Change Form (Pre- existing forms in use, no longer generated for requirements)

Restricted access – available after task order award

Air Force Form 1067 Modification Proposal http://static.e-publishing.af.mil/production/1/s af_aq/form/af1067/af1067.xfdl http://static.e-publishing.af.mil/production/1/saf_aq/publication/afi63-131/afi63-131.pdf http://static.e-publishing.af.mil/production/1/saf_aq/publication/afi63-131/afi63-131.pdf http://static.e-publishing.af.mil/production/1/saf_aq/publication/afi63-131/afi63-131.pdf http://static.e-publishing.af.mil/production/1/saf_aq/publication/afi63-131/afi63-131.pdf http://static.e-publishing.af.mil/production/1/saf_aq/publication/afi63-131/afi63-131.pdf http://static.e-publishing.af.mil/production/1/saf_aq/publication/afi63-131/afi63-131.pdf http://static.e-publishing.af.mil/production/1/saf_aq/publication/afi63-131/afi63-131.pdf http://static.e-publishing.af.mil/production/1/saf_aq/publication/afi63-131/afi63-131.pdf http://static.e-publishing.af.mil/production/1/saf_aq/publication/afi63-131/afi63-131.pdf http://static.e-publishing.af.mil/production/1/saf_aq/publication/afi63-131/afi63-131.pdf http://static.e-publishing.af.mil/production/1/saf_aq/form/af1067/af1067.xfdl http://static.e-publishing.af.mil/production/1/saf_aq/form/af1067/af1067.xfdl http://static.e-publishing.af.mil/production/1/saf_aq/form/af1067/af1067.xfdl http://static.e-publishing.af.mil/production/1/saf_aq/form/af1067/af1067.xfdl http://static.e-publishing.af.mil/production/1/saf_aq/form/af1067/af1067.xfdl

Air Force Directive 33-

Information Assurance (IA) Program http://static-epublishing.af.mil/production/1/s af_cio_a6/publication/afpd33- 2/afpd33-2.pdf

DoD 5200.2-R Personnel Security Program http://www.dtic.mil/whs/directiv es/corres/pdy/520002r.pdf

Air Force Instruction 17-

Air Force Information Technology Service Management http://static.e-publishing.af.mil/production/1/s af_cio_a6/publication/afi33115/afi17-100.pdf

Air Force Instruction 63- 101/20-101

Integrated Life Cycle Management http://static.e-publishing.af.mil/production/1/s af_aq/publication/afi63101_20-101.pdf

Air Force Instruction 10-

Operations Security

(OPSEC)

http://static.e-publishing.af.mil/production/1/a f_a3_5/publication/afi10701/afi10-701.pdf

DD Form 2875 System Authorization Access Request (SAAR) http://www.disa.mil/Services/N etwork- Services/Video/DVSG/~/media/Files/DISA/Services /DVS/DD2875.pdf

FAR (All references) Federal Acquisition Regulations http://www.acquisition.gov/far/

DFAR (All references) Defense Federal Acquisition Regulation Supplement

(DFARS)

http://www.acq.osd.mil/dpap/d ars/dfarspgi/current

APPENDIX A. ITW/AA Stakeholders

The list of ITW/AA stakeholders identified here contains the most detailed set of stakeholders currently available but may change over time with the decommissioning of legacy systems and deployment of new systems.

A1. Operators, Force Providers, and System Program Offices The following groups, governance bodies, and organizations represent the interests of the ITW/AA Operators:

• Program Executive Officers (PEOs)

• Electronic Systems Center (ESC)

• Air Force Life Cycle Management Center (AFLCMC)

• United States Space Command (USSPACECOM)

• United States Strategic Command (USSTRATCOM)

• Nuclear Command Control and Communications (NC3) Enterprise Center (NEC)

• Air Combat Command (ACC)

• Air Force Global Strike Command (AFGSC)

• United States Space Force (USSF) & the Space System Command (SSC)

• NORAD and United States Northern Command (NORTHCOM) http://static-e-publishing.af.mil/production/1/saf_cio_a6/publication/afpd33-%202/afpd33-2.pdf http://static-e-publishing.af.mil/production/1/saf_cio_a6/publication/afpd33-%202/afpd33-2.pdf http://static-e-publishing.af.mil/production/1/saf_cio_a6/publication/afpd33-%202/afpd33-2.pdf http://static-e-publishing.af.mil/production/1/saf_cio_a6/publication/afpd33-%202/afpd33-2.pdf http://static-e-publishing.af.mil/production/1/saf_cio_a6/publication/afpd33-%202/afpd33-2.pdf http://static-e-publishing.af.mil/production/1/saf_cio_a6/publication/afpd33-%202/afpd33-2.pdf http://static-e-publishing.af.mil/production/1/saf_cio_a6/publication/afpd33-%202/afpd33-2.pdf http://static-e-publishing.af.mil/production/1/saf_cio_a6/publication/afpd33-%202/afpd33-2.pdf http://static-e-publishing.af.mil/production/1/saf_cio_a6/publication/afpd33-%202/afpd33-2.pdf http://static-e-publishing.af.mil/production/1/saf_cio_a6/publication/afpd33-%202/afpd33-2.pdf http://static-e-publishing.af.mil/production/1/saf_cio_a6/publication/afpd33-%202/afpd33-2.pdf http://static-e-publishing.af.mil/production/1/saf_cio_a6/publication/afpd33-%202/afpd33-2.pdf http://www.dtic.mil/whs/directiv http://www.dtic.mil/whs/directiv http://static.e-publishing.af.mil/production/1/saf_cio_a6/publication/afi33-115/afi17-100.pdf http://static.e-publishing.af.mil/production/1/saf_cio_a6/publication/afi33-115/afi17-100.pdf http://static.e-publishing.af.mil/production/1/saf_cio_a6/publication/afi33-115/afi17-100.pdf http://static.e-publishing.af.mil/production/1/saf_cio_a6/publication/afi33-115/afi17-100.pdf http://static.e-publishing.af.mil/production/1/saf_cio_a6/publication/afi33-115/afi17-100.pdf http://static.e-publishing.af.mil/production/1/saf_cio_a6/publication/afi33-115/afi17-100.pdf http://static.e-publishing.af.mil/production/1/saf_cio_a6/publication/afi33-115/afi17-100.pdf http://static.e-publishing.af.mil/production/1/saf_cio_a6/publication/afi33-115/afi17-100.pdf http://static.e-publishing.af.mil/production/1/saf_cio_a6/publication/afi33-115/afi17-100.pdf http://static.e-publishing.af.mil/production/1/saf_cio_a6/publication/afi33-115/afi17-100.pdf http://static.e-/ http://static.e-/ http://static.e-/ http://static.e-/ http://www.disa.mil/Services/N http://www.acquisition.gov/far/ http://www.acquisition.gov/far/ http://www.acq.osd.mil/dpap/d

• Defense Information System Agency (DISA)

• Communications Squadrons for relevant ITW/AA and non ITW/AA communications

• Operations Approval Board (OAB)

• Operations Approval Panels (OAPs) and their designated Change Control Managers

(CCMs) for:

o Mission Systems OAP o Forward Users OAP o NORAD Air OAP o USSF OAP

• Space Operations Command (SpOC)

• Space and Missile System Center (SMC)

A2. Key Systems Supporting ITW/AA The following systems play a key role in supporting the ITW/AA mission. The ITW/AA Enterprise consists of components that produce, transmit, receive, correlate, and disseminate vital mission data. The list below highlights some of systems, operational centers, and units that support the ITW/AA mission. Where applicable, the responsible contractor vendor has been identified in parentheses.

• Perimeter Acquisition Radar Attack Characterization System or PARCS (Summit Technical Solutions LLC (STS))

• Ground Based Sensors Ballistic Missile Early Warning System or BMEWS (Northrop

Grumman) PAVE Phased Array Warning System or PAVE PAWS (Northrop

Grumman) Upgraded EWRs or UEWRs (Raytheon)

• Space Based Infrared System or SBIRS (Lockheed Martin) o Ground Communications Network Modification or GCNM o Mission Control Station or MCS (System High Corporation)

• MCS Backup or MCSB (System High Corporation)

• Mobile Ground System or MGS (Lockheed Martin) o SBIRS Survivable and Endurable Evolution or S2E2 (Raytheon)

• Space Defense Operations Center or SPADOC (Raytheon)

• Integrated Correlation and Display System or ICADS A – at DET 45 (Ball Aerospace)

• Battle Control System-Fixed or BCS-F (Raytheon)

• Defense Support Program or DSP (Northrop…