Attachment_001_-_Base_CRS_&_Attachments.pdf

PRODUCT LEAD

WIDEBAND ENTERPRISE SATELLITE

SYSTEMS

(PL WESS)

PROJECT OFFICER

WIDEBAND CONTROLS (POWC)

WIDEBAND SATELLITE COMMUNICATIONS (SATCOM) TREND ANALYSIS AND

ANOMALY RESOLUTION SUBSYSTEM/WIDEBAND SATCOM OPERATIONS

MANAGEMENT SYSTEM (WSOMS) MEDIATED INTEROPERABILITY INFRASTRUCTURE

(WSTARS/WMII) BASE CONTRACT

Revision 7 13 December 2016

Attachment 001 - Base CRS & Attachments, 13 December 2016 i

Table of Contents

1 OBJECTIVE

1.1 Scope

1.2 General Information

1.2.1 Type of Contract

1.2.2 NOTICE: Federal Holidays

1.2.3 Hours of Operation

1.2.4 Place of Performance

1.2.5 Post Award Conference/Periodic Progress Meetings

1.2.6 Technical Execution Plan:

1.2.7 Special Qualifications

1.2.8 Key Personnel

1.2.9 Contractor Manpower Reporting

1.2.10 Use of Subcontractors

1.2.11 Contractor Travel

1.2.12 Other Direct Costs

1.2.13 Data Rights

1.2.14 International Traffic in Arms Regulations

2 SECURITY

2.1 Access to Government Systems:

2.2 Security Requirements

2.3 Other Security Requirements

2.4 Physical Security

2.5 Contractors Requiring Common Access Card

2.6 Facility Security Clearance

2.7 Information Technology

2.8 Information Security and Other Miscellaneous Requirements

3 GOVERNMENT FURNISHED ITEMS AND EQUIPMENT

3.1 Property:

3.2 Services:

3.3 Information:

4 CONTRACTOR FURNISHED ITEMS AND RESPONSIBILITIES

ii

5 SPECIFIC TASKS

5.1 Performance Requirements

5.2 Program Management

5.2.1 Integrated Master Schedule

5.2.2 Performance Risk

5.2.3 Contractor Manpower Reporting

5.2.4 Progress, Status and Management Report

5.2.4.1 ......................................................................................... Performance and Cost Reporting:

5.2.5 Program Meetings

5.2.5.1 Integrated Product Team Meetings:

5.2.5.2 Technical Reviews:

5.2.5.3 Program Management Review:

5.2.5.4 Integrated Baseline Reviews:

5.2.5.5 Briefing Materials:

5.2.5.6 Meeting Minutes:

5.2.7.1 Configuration Management Plan:

5.2.7.2 Configuration Status Accounting:

5.2.7.3 Engineering Change Proposals:

5.2.7.4 Engineering Change Proposal Class I:

5.2.7.5 Engineering Change Proposal Class II:

5.2.7.6 Specification Change Notice:

5.2.7.7 Request For Deviation:

5.2.7.8 Configuration Control Board:

5.2.8 Quality Control:

5.2.9 Quality Assurance:

5.2.10 Continuous Process Improvement:

5.3 System Engineering:

5.3.1 WSTARS/WMII Implementation:

5.3.2.1 Design Testing:

5.3.2.2 Cybersecurity Testing:

5.3.2.3 Logistics Demonstrations:

5.3.2.4 Environmental Testing:

iii

5.3.2.5 Preliminary Qualification Testing:

5.3.2.6 Formal Qualification Testing:

5.3.2.7 System Readiness Testing Support:

5.3.2.8 On-Site Acceptance Tests:

5.3.2.9 Over-the-Satellite Tests:

5.3.2.10 Government Confidence Tests:

5.3.2.11 Failure Analysis:

5.3.2.12 Test Readiness Reviews:

5.3.2.13 Test Documentation:

5.3.2.14 Other Testing Considerations:

5.3.3 Drawing Tree:

5.3.4 Technical Data Package:

5.3.5 As Built Configuration List:

5.3.6 Interface Control Document:

5.3.7 Software Version Description:

5.4 Cybersecurity:

5.4.1 Cybersecurity Engineering:

5.4.2 Software Code Reviews:

5.4.3 Assessment Testing:

5.4.4 Cybersecurity Working Group:

5.5 Integrated Logistics Support:

5.5.1 Level of Repair Analysis:

5.5.2 Recommended Spares:

5.5.3 Item Unique Identification:

5.5.3.1 Item Unique Identification Marking:

5.5.3.2 Commercial Markings:

5.5.3.3 IUID Coding:

5.5.3.4 IUID Registration:

5.5.4 Maintenance Allocation Chart:

5.5.5 Repair Parts and Tools List:

5.5.6 Maintainability Engineering Evaluation:

5.5.7 Basis of Issue Plan Feeder Data:

5.5.8 System Support Package:

iv

5.5.9 Electronic Technical Manual (ETM):

5.5.9.1 ETM Supplements:

5.5.9.2 ETM Technical Manual Quality Assurance Reviews:

5.5.9.3 ETM Validation:

5.5.9.4 ETM Verification:

5.5.10 Training:

5.5.10.1 New Equipment Training:

5.5.10.2 Instructor and Key Personnel Training:

5.5.10.3 Training Support Conduct Documents and Training Program Structure:

Documents:

5.5.10.4 IKP Training Material Execution:

5.5.10.5 Computer-Based Training Execution:

5.5.10.6 Training Conferences:

5.5.10.7 Instructor Qualifications:

5.5.11 Post Production Support Analysis:

5.5.12 Disposal and Demilitarization:

5.5.13 Design Interface:

5.5.14 Logistics Demonstration:

5.5.15 Request for Nomenclature:

5.5.16 Reliability Prediction Report:

5.5.17 Supplemental Data for Provisioning:

5.6 Installation Effort:

5.7 Safety:

5.7.1 Safety Engineering:

5.7.2 Inspection and Verification:

5.7.3 Safety Assessment Report:

5.7.4 Safety Assessment Report Updates:

5.7.5 Health Hazards:

5.7.5.1 Pollution Prevention and Toxic Substances:

5.7.5.2 Radioactive Materials:

5.7.6 Hazard Tracking and Risk Resolution:

5.7.7 Electronic Hazard Tracking System:

5.7.8 Risk Assessment Code:

v

5.7.8.1 Hazard Severity Categories:

5.7.8.2 Probability of Occurrence:

5.7.8.3 Risk Assessment Matrix:

5.8 Post Design/Production Software Support:

5.8.1 Contractor Participation and Responsibilities:

5.8.2 Software Technical Data and Artifacts:

5.8.3 WSTARS/WMII Laboratory Configuration:

5.8.3.1 Software Sustainment Environment:

5.8.3.2 Software Sustainment Environment Test Bed:

5.8.3.3 Software Sustainment Environment Transition:

5.8.4 Computer Software Product:

5.8.4.1 Software Updates:

5.8.4.2 Software Enhancements:

5.8.4.3 Software Reviews:

5.8.5 Field Software Changes:

5.8.5.1 Software Testing:

5.8.6 Electronic Technical Manual:

5.8.7 Software Configuration Management:

5.8.7.1 Software Configuration Audit Documentation:

5.8.7.2 Software Configuration Audits:

6 APPLICABLE PUBLICATIONS (Current Editions)

7 DELIVERY SUMMARY

Standards

8 DEFINITIONS AND ACRONYMS

8.1 Definitions

8.2 Acronyms

vi

List of Tables

Table 1-1 WSTARS/WMII Requirements Locations Table 1-2 Personnel Qualifications

Table 5-1 Electronic Technical Manual Table 5-2 Training Conferences Table 5-3 Probability of Occurrence Table 5-4 Risk Assessment Matrix Table 5-5 Priority Codes

Table 6-1 Department of Defense Specifications and Standards Table 6-2 Commercial Standards Table 6-3 Other Documents Table 7-1 CDRL List Table 7-2 Performance Requirements Summary (PRS) Table 7-3 Performance Requirements Summary (Continued) Table 8-1 Definitions Table 8-2 Acronyms

PRODUCT MANAGER, DEFENSE COMMUNICATIONS AND ARMY TRANSMISISON

SYSTEMS (PM DCATS)

PRODUCT LEAD, WIDEBAND ENTERPRISE SATELLITE SYSTEM - WIDEBAND CONTROL

(PL WESS - WC)

CUSTOMER REQUIREMENTS STATEMENT (CRS)

FOR

WIDEBAND SATELLITE COMMUNICATIONS (SATCOM) TREND ANALYSIS AND

ANOMALY RESOLUTION SYSTEM/WIDEBAND SATCOM MEDIATED INTEROPERABILITY

INFRASTRUCTURE (WSTARS/WMII)

BASE CONTRACT

1 OBJECTIVE

This CRS is to support the Wideband Satellite Communications (SATCOM) Trend Analysis and Anomaly Resolution System / Wideband SATCOM Operational Management System (WSOMS) Mediated Interoperability Infrastructure (WSTARS/WMII), a part of the WSOMS for the United States Department of the Army Product Manager Defense Communications and Army Transmission Systems (PM DCATS).

The PL WESS-WC goal for WSTARS/WMII is to enhance and improve the productivity, accuracy, and situational awareness of the Satellite Controller, 53rd Signal Battalion (53rd SigBN) and the United States Army Space and Missile Defense Command / Army Forces Strategic Command (USASMDC/ARSTRAT) Wideband Watch Officer by implementing a fully functional, high availability, low-failure, low-maintenance, remotely or locally controllable and maintainable management system capability. Additionally, POWC aims to efficiently, effectively, and economically support the mission requirements of USASMDC/ARSTRAT, the 53rd SigBN, and Defense Information Systems Agency (DISA), who support Wideband Global Satellite (WGS) and Defense Satellite Communications System (DSCS) operations.

The WSTARS/WMII will be the component of the WSOMS that will provide enhanced data sharing and information management capability while focusing on expanding the trend analysis and anomaly resolution capability. The vision for the WSTARS end-state is a subsystem that replaces the existing DSCS Integrated Management System (DIMS), automates many of the routine satellite resource allocation and configuration functions for managers, and removes many of the routine “operator-in-the-loop” functions of controllers. WSTARS will, in the future, alleviate much of the status reporting from the operator as this function becomes increasingly automated. WSTARS will support management of Wideband Commercial SATCOM and Wideband Military Satellite Communications systems and be accessible to all levels of the wideband SATCOM Community of Interest (COI). WSTARS will be installed at the Wideband SATCOM Operations Centers (WSOC) and other WSOMS support sites noted in the WSOMS Capability Product Document (CPD) Increment 2 (Draft). The WSOMS Network (WSOMSNET) is the network that connects the WSOMSNET nodes such as WSOCs and WSOMS support sites. WMII will be the common computing infrastructure which hosts WSTARS software, databases, and all other applicable subsystem software in a VM environment and provide communication via Web Services/Service Oriented Architecture (SOA) Bus. WMII will serve as the interface to other WSOMS subsystems and other external users.

The Army intends to award a contract to satisfy this mission requirement. This CRS defines the required results of the Contractor to execute this mission.

1.1 Scope:

The scope of this contract shall include system definition, design and execution, equipment purchase and inventory, integration, site surveys, installation, and verification of the functionality of the WSTARS/WMII. The Contractor shall perform all necessary program management and facility support services as stated in this CRS in the form of system engineering. The Contractor shall perform all system software updates for security and Information Assurance Vulnerabilities Alerts (IAVAs), by installing Government approved updates and integrating them into the system.

The Contractor shall also provide program management, quality assurance, and configuration management services for the execution and acceptance of the Integrated Logistics Support (ILS), Electronic Training Manuals (ETMs), and training packages, as requested by the Government, for supporting the WSTARS/WMII.

The Contractor shall test the integration of new equipment and conduct training at all sites after each installation. The Contractor shall perform cutover activities to deliver a fully operational system and shall be responsible for maintaining the current WSTARS/WMII Technical Data Package. The Contractor shall also coordinate efforts with existing subsystem Contractors to ensure complete integration of the subsystems in the new WMII environment. Additionally, spare equipment shall be required to support the initial fielding and depot sparing of the WSTARS/WMII system, and to meet operational availability standards identified in Section 3.7 of Attachment 001 - RLM-WSTARS-C005SSV2 (System Specification).

The Contractor tasking described by this CRS includes, but is not limited to the following:

a. The Contractor shall work in conjunction with the Government to create and maintain a Product Roadmap of the iteratively derived functional capability of WSTARS/WMII, across the overall Base and Option Task Orders of this contract. This Product Roadmap shall define a finished product that fully conforms with the WSTARS/WMII System Specification in effect as of the date of contract award, the approved WSTARS Concept of Operations, and WSOMS CPD Increment 2 (Draft). This Product Roadmap shall cite all dependencies on the corresponding evolution of other WSOMS subsystems identified in Section 5.1. The Product Roadmap shall be delivered IAW CDRL F002 (DI-MISC- 80711A).

b. The Contractor shall coordinate with other Contractor and Government personnel working on inter-related WSOMS subsystems, to ensure the success of WSTARS/WMII, but will not perform work on the other WSOMS subsystems. The Contractor will be restricted to defining the architecture but will not be integrating or implementing.

c. The Contractor shall provide all system and software engineering services and products defined in Sections 5.3 and 5.8 of this CRS to achieve the following high-level capability requirements of the WSTARS/WMII:

1) Integration of WSTARS/WMII into the web-service and SOA based WSOMSNet infrastructure;

2) Centralization of all WGS related subsystem databases into a single logical design, which static and dynamic data analytics shall utilize;

3) Standardized Information Management software across all appropriate subsystems;

4) Produce Data Analytics algorithms and Situational Awareness tools to enable forward-looking assessment, and provide visualization of Communication Link and Network Management Trends and Anomalies;

5) Deployment of Zero Client or Virtual Desktop to all WSOC’s identified in Table 1- 1;

6) Provide Public Key Infrastructure (PKI) / Access Management for all users of

WSOMS;

7) Manage external system communications;

8) Automate typical controller functions such as Resource Allocations, Anomaly

Resolution, and the issuance Status Reporting and Trouble Tickets; and

9) Facilitate timely upgrade of software and hardware as required by PM DCATS.

d. The Contractor shall produce and maintain three (3) configuration current, Integration

Hardware Environment systems to facilitate WSTARS/WMII system software design, execution, testing and verification, and post-production support as defined in Sections

5.3 and 5.8 of this CRS.

e. The Contractor shall produce, test, and install WSTARS/WMII end items as defined in Sections 5.3 and 5.6 of this CRS, at the locations identified in Table 1-1.

f. The Contractor shall ensure that Cybersecurity and associated security requirements defined in Section 5.4 of this CRS, are achieved to obtain and maintain an Authority to Operate (ATO) for deployed WSTARS/WMII systems.

g. The Contractor shall provide ILS as defined in Section 5.5 of this CRS for the initial WSTARS/WMII system design and execution, and for any enhancements made to the system.

h. The Contractor shall conduct an ongoing Safety Program as defined in Section 5.7 of this CRS.

i. The Contractor shall produce and maintain all hardware and software Technical Documentation as defined in Sections 5.3 and 5.8 of this CRS to enable a manufacturer of similar equipment to produce physically and functionally equivalent WSTARS/WMII equipment.

j. The Contractor shall provide all system and software engineering services and products (including a Software Sustaining Environment) required to conduct the WSTARS/WMII Post Design/Production Software Support activities defined in Section 5.8 of this CRS.

1.2 General Information:

1.2.1 Type of Contract:

The Government will award a five (5) year single award Indefinite Delivery / Indefinite Quantity (ID/IQ) contract. Task Orders will be issued by the Government, consistent with the overall scope of this CRS, defining specific tasking, funding and schedule requirements for each authorized task. These Task Orders may be either FFP or CPFF, based on the Government’s understanding of scope and risks associated with each task.

Period of performance will be indicated in each Task/Delivery Order.

1.2.2 NOTICE: Federal Holidays:

Government employees will not be working the following holidays, however this does not dictate when contractors are expected to work and is for informational purposes only:

New Year’s Day Labor Day Martin Luther King Jr.’s Birthday Columbus Day President’s Day Veteran’s Day Memorial Day Thanksgiving Day Independence Day Christmas Day

1.2.3 Hours of Operation:

The Contractor is responsible for establishing their own hours of operations. However, the Contractor shall conduct all meetings, reviews, surveys, site preparations, installations, testing and verifications, and trainings that require either Government personnel or access to a Government facility within the hours of 08:00 to 17:00 East Coast, United States time, Monday through Friday, or within hours designated by that specific Government facility.

1.2.4 Place of Performance:

The primary work under this contract is to be performed at the Contractor facility. Additional work is to be performed at the Government CONUS and OCONUS operating installations identified in Table 1-1. The Contractor shall coordinate site visits with the POWC to ensure that the on-site contract team will have a Department of Defense (DoD) Clearance level necessary and facility access requirements, such as Common Access Card (CAC), to work on-site. The Contractor shall provide access lists of personnel/vehicles entering site with sufficient lead time to allow for the issuance of entry passes.

Table 1-1 WSTARS/WMII Requirements Locations

Location Date of Installation 1 Company A, 53rd Signal Battalion, Fort Detrick, MD (WSOC) TBD 2 Company B, 53rd Signal Battalion, Fort Meade, MD (WSOC) TBD 3 Company C, 53d Signal Battalion, Landstuhl, GE (WSOC) TBD 4 Company D, 53rd Signal Battalion, Wahiawa, HI (WSOC) TBD

5 Company E, 53rd Signal Battalion, Fort Buckner, Okinawa, Japan (WSOC) TBD

6 Joint Engineering Center (JSEC) Control Systems Laboratory (CSL), Aberdeen Proving Ground, MD TBD

7 56th Signal Company, 54th Signal Battalion, Camp Arifjan, Kuwait TBD

8 NAVSATCOMMFAC Northwest, NCTAMS LANT, Chesapeake, VA TBD

9 514th Signal Company, 302nd Signal Battalion, Camp Roberts, California TBD

10 NAVSATCOMMFAC Lago NCTAMS, Lago Patria, Italy TBD

11 Geraldton, Australia TBD 12 Harmon, Australia TBD 13 Fort Gordon, GA TBD 14 RSSC-West, CO TBD 15 RSSC-East, FL TBD 16 RSSC-Pacific, HI TBD 17 RSSC-Europe, GE TBD

18 CONUS TBD SITE TBD

19 CONUS TBD SITE TBD

1.2.5 Post Award Conference/Periodic Progress Meetings:

The Contractor shall attend a Post Award Conference in the National Capital Region within one week of contract award, and any other Periodic Progress Meetings convened by the contracting activity or contract administration office IAW Federal Acquisition Regulation Subpart

42.5. The Contracting Officer (KO), Contracting Officers Representative (COR), and other Government personnel, as appropriate, may meet periodically with the Contractor to review the Contractor's performance. At these meetings the KO will apprise the Contractor of how the Government views the Contractor's performance and the Contractor shall apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the Government.

Periodic progress meetings will be conducted at the Governments discretion.

1.2.6 Technical Execution Plan:

The Contractor shall deliver a Technical Execution Plan (TEP) IAW CDRL A001 (DI-MGMT- 80004A) to the Government within ten business days of contract award, and shall provide a summary briefing of that plan at the Post Award Conference (identified in Section 1.2.5). The Contractor shall deliver appropriate updates to the TEP within five business days following the receipt of any formal comments from the Government.

1.2.7 Special Qualifications:

The Contractor shall have experience and certifications in the following areas:

a. SATCOM: The Contractor shall have an existing knowledge base of DSCS and Wideband Global SATCOM Wideband SATCOM Operational Management System (WGS WSOMS) control subsystem applications and databases, including inter-dependencies among the systems.

b. Cybersecurity: The Contractor shall possess on-going knowledge of DoD’s evolving Risk Management Framework (RMF) for information systems, National Institute of Standards & Technology (NIST) documentation requirements with thorough knowledge of SATCOM architecture, all current and future WSOMS control subsystem applications (payload control and network planning/management/control) and databases, including inter-dependencies among the readiness of products and baselines being integrated, applicable Joint, DoD and Army regulatory cybersecurity guidance.

1.2.8 Key Personnel:

The following personnel are considered key personnel by the Government:

• Project Manager

• Senior Systems Engineer

• Lead Test Engineer

• Senior Information Assurance Analyst

• Lead Logistics Analyst

The key personnel specified in this CRS are considered to be essential to work performance.

For this Contract, Key Personnel shall be assigned for the life of the contract barring circumstances outside the control of the Contractor, (e.g., death, disability, the result of leaving the employ of the Contractor, etc.).

The Contractor shall notify the Contracting Officer and shall submit comprehensive justification for a replacement request (including the proposed substitute) for key personnel at least 30 days prior, to permit evaluation by the Government of the impact on performance under this Task Order. The Contractor shall not divert or otherwise replace any key personnel without the written consent of the Contracting Officer. The Government may modify the contract to add or delete key personnel at the request of the Contractor or Government.

The Contractor shall provide a Project Manager that is responsible for the performance of the work. The name of this person and an Alternate who will act for the Contractor when the Project Manager is absent, shall be designated in writing to the KO. The Project Manager or the designated Alternate shall have full authority to act for the Contractor on all contract matters relating to daily operation of this contract. The Project Manager or the designated Alternate shall be available at the Place of Performance to ensure the performance of the work of this CRS between 0800-1700, Monday through Friday except Federal holidays or when the Government facility is closed for administrative reasons. Qualifications for all key personnel are listed in Table 1-2:

Table 1-2 Personnel Qualifications

TITLE PERSONEL QUALIFICATION

Project Manager (PM)

A minimum of fifteen (15) years of experience on similar projects and systems as the requirements and scope of this CRS. A minimum of five (5) years’ experience in Project Management with previous accomplishments of similar size and scope of this CRS. Bachelor’s Degree in Information Management, Engineering, or Business.

PMP, Lean Six Sigma, and Agile Scrum Master and / or Product Owner Certifications desirable.

Senior Systems Engineer

A minimum of ten (10) years of experience in System Development Life Cycle, experience on similar projects and systems as the requirements and scope of this CRS, plus Bachelor’s Degree in Engineering.

Lead Test Engineer

A minimum of ten (10) years of experience in complex system Testing (including Manual and Automated Testing, Test Procedure Development, and Reporting). Bachelor’s Degree in Engineering or Computer Science. Three (3) years of experience as the “Lead” in similar projects and systems as the requirements and scope of this

CRS.

Senior Information Assurance (IA) Analyst

A minimum of ten (10) years’ experience in Information Assurance with DoD IA mandates. Bachelor’s Degree in Information Management, Engineering, or Computer Science. Level III certified IAW DoD 8570.01-M. Certification required at Contract Award, and RMF experience is desirable.

Lead Logistics Analyst

A minimum of ten (10) years of experience in military acquisition logistics management (including development of technical manuals, training packages, equipment fielding planning and documentation).

Bachelor’s Degree in Functional area or related subject. Three (3) years of experience as the “Lead” in similar projects and systems as the requirements and scope of this CRS.

1.2.9 Contractor Manpower Reporting:

The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract via a secure data collection site. The contractor is required to completely fill in all required data fields using the following web address: http://www.ecmra.mil/, and then click on “Department of the Army CMRA” or the icon of the DoD organization that is receiving or benefitting from the contracted services.

Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year, beginning with 2013. Contractors may direct questions to the help desk by clicking on “Send an email” which is located under the Help Resources ribbon on the right side of the login page of the applicable Service/Component’s CMR website.

1.2.10 Use of Subcontractors:

The Contractor shall flow down all applicable contract program, product, and performance requirements to Subcontractors and suppliers contracts, and shall conduct periodic Subcontractor/supplier product/ process reviews with Government participation. Subcontractors shall be required to have Secret Facility clearance and shall need to have an approved DD254.

1.2.11 Contractor Travel:

Contractors shall be required to travel to CONUS and OCONUS WSOCs, and locations identified in Table 1-1, to attend meetings, conferences, installations, and training. Key personnel shall be required to travel within the National Capitol Region during the performance of this contract to attend meetings and conferences.

Some of the work to be performed under this contract shall be performed at the locations listed in Table 1-1. Contractor will be authorized travel expenses consistent with the substantive provisions of the Joint Travel Regulation (JTR) and the limitation of funds specified in this contract. All travel requires Government approval/authorization and notification to the COR.

Costs for transportation may be based upon mileage rates, actual costs incurred, or a combination thereof, provided the method used results in a reasonable charge. Travel costs will be considered reasonable and allowable only to the extent that they do not exceed on a daily basis, the maximum per diem rates in effect at the time of the travel. The JTR shall provide the basis for the determination as to whether travel costs are reasonable. Maximum use is to be made of the lowest available customary standard coach or equivalent airfare accommodations available during normal business hours. All necessary travel meeting the above criteria shall be reviewed in advance by the COR. Contractor shall accommodate travel and extended duty hours beyond the normal forecasted hours (Monday – Friday, 0900-1500 Local Time) in order to support mission critical travel.

1.2.12 Other Direct Costs:

For CPFF Task Orders, these costs must be approved by the COR. This category includes travel, as outlined in Section 1.2.11 Contractor Travel, reproduction, and shipping expenses associated with training activities, and visits to Contractor facilities. It could also entail the renting of suitable training venues. Other items that may be charged as ODCs are equipment shipping, reproduction, and shipping expenses associated with training activities.

1.2.13 Data Rights:

The Contractor shall provide Data Rights for software, materials, and information for system documentation IAW with the clauses in the contract.

All records, files, documents, and working papers provided by the Government, generated by the Government, or generated for the Government in performance of this CRS shall be and remain Government property and shall be maintained and disposed of IAW the Contracting Officer's instructions and/or applicable markings. Delivery and storage methods shall be in compliance with Army security policies governing “public release” and security standards.

All deliverables such as briefings, graphics, project schedules, spreadsheets, reports, and documents shall be provided using Microsoft and AutoDesk compatible software (e.g.

PowerPoint, Visio, Access, Project, Excel, and AutoCad). Other formats such as Adobe Portable Document Format (PDF) and Hyper Text Markup Language (HTML) may be used only as approved by the Government COR. Upon delivery, all documents become government property and shall bear no proprietary markings.

1.2.14 International Traffic in Arms Regulations:

The Contractor shall be responsible for establishing a Technical Assistance Agreement (TAA) allowing collaboration with Australian Defense Forces personnel supporting the WSTARS/WMII, USASMDC/ARSTRAT, DISA, and PM-DCATS. The Contractor shall be responsible for compliance with International Traffic in Arms Regulations (ITAR) restrictions and any export of data, software, or material. All Subcontractors shall review the ITAR agreements and be signatories to the TAA.

2 SECURITY

2.1 Access to Government Systems:

IAW DoD Directive 7045.14, The Planning, Programming, Budgeting and Execution Process, dated 25 January 2013, Contractors are not allowed access to any DoD system without explicit authorization of a relevant Government official, and that is based on a need-to-know basis only.

Individuals getting access shall have the appropriate Security Clearance for access to a particular system.

Contractors are required to use Defense Collaboration Services (DCS), and to have computers that can support the usage of DCS.

2.2 Security Requirements:

Contractor personnel performing work under this contract shall have a minimum of a SECRET security clearance at time of the proposal submission, and shall maintain the level of security required for the life of the contract. All Contractor personnel that will perform work at any of the Government locations identified in Table 1-1, shall have a TOP SECRET security clearance at the time of Contract Award. The security requirements are IAW the attached DD254, Contract Security Classification Specification incorporated in this contract. In addition, for this CRS:

a. The Contractor facility shall have a SECRET safeguarding capability at a minimum of two cubic feet.

b. The Contractor will require access to Non-Sensitive Compartmented Information intelligence information and For Official Use Only (FOUO) information. The Contractor will also require access to Communications Security information, NATO information, and Foreign Government information. In performing this contract, the Contractor will receive and generate classified information (only collateral SECRET will be performed at the Contractor’s facility), and have Operations Security (OPSEC) requirements, IAW the

DD254.

c. Administrative duties performed by the Contractor will not require a clearance, but may require an investigation for information technology sensitive duties.

d. Per AR 530-1, Operations Security, new Contractor employees shall complete Level I OPSEC training within thirty (30) calendar days of reporting for duty. All Contractor employees shall complete annual OPSEC awareness training.

2.3 Other Security Requirements:

Per the DD254 (Standard Contract Provision and Clause Text Applicability and/or Additional CRS Language), the Contractor shall adhere to the following security requirements:

a. Antiterrorism Training (AT) Level I Awareness Training. This provision/contract text is for

Contractor employees with an area of performance within an Army-controlled installation, facility, or area. All Contractor employees, including Subcontractor employees, requiring access to Army installations, facilities, or controlled access areas shall complete AT Level I awareness training within sixty (60) calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever applies. The Contractor shall submit certificates of completion for each affected Contractor employee and Subcontractor employee to the COR, or to the contracting officer, if a COR is not assigned, within fourteen (14) calendar days after completion of training by all employees and Subcontractor personnel. AT Level I awareness training is available at https://atlevel1.dtic.mil/at.

b. AT Awareness Training for Contractor Personnel Traveling Overseas. U.S.-based Contractor employees and associated Subcontractor employees shall have available and shall receive Government-provided AT awareness training specific to the Area of Responsibility (AOR) as directed by AR 525-13. Specific AOR training content is directed by the combatant commander, with the unit ATO being the local point of contact.

c. Access and General Protection/Security Policy and Procedures. This standard language is for Contractor employees with an area of performance within an Army-controlled installation, facility, or area. The Contractor and all associated Subcontractors’ employees shall comply with applicable installation, facility, and area commander installation and facility access and local security policies and procedures (provided by the Government representative). The Contractor shall also provide all information required for background checks to meet installation access requirements to be accomplished by the installation Provost Marshal Office, Director of Emergency Services, or Security Office. The Contractor workforce shall comply with all personal identity verification requirements as directed by DoD, HQDA, and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition at any individual facility or installation change, the Government may require changes in Contractor security matters or processes.

d. Contractor Employees Who Require Access to Government Information Systems. All Contractor employees with access to a Government information system shall be registered in the Army Training Certification Tracking System at commencement of services and shall successfully complete the DoD Information Assurance Awareness training prior to access to the information system and then annually thereafter.

e. For the Handling or Access to Classified Information, the Contractor shall comply with FAR 52.204-2, Security Requirements. This clause involves access to information classified “Confidential,” “Secret,” or “Top Secret” and requires Contractors to comply with one (1) the Security Agreement (DD Form 441), including the National Industrial Security Program Operating Manual (DoD 5220.22-M), and (2) any revisions to DoD 5220.22-M, notice of which has been furnished to the Contractor.

f. For Information Assurance (IA)/Information Technology (IT) Training. All Contractor employees and associated Subcontractor employees shall complete the DoD IA awareness training before issuance of network access and annually thereafter. All Contractor employees working IA/IT functions shall comply with DoD and Army training requirements in DoDD 8570.01, DoD 8570.01-M, and AR 25-2 within six (6) months of employment.

g. For Information Assurance (IA)/Information Technology (IT) Certification. Per DoD 8570.01-M, DFARS 252.239.7001, and AR 25-2, the Contractor Information Assurance Engineer supporting IA/IT functions shall be appropriately certified upon contract award.

The baseline certification as stipulated in DoD 8570.01-M shall be completed upon contract award. The Contractor’s Cybersecurity (Information Assurance) Engineer in Section 5.4 shall be responsible for administering any updates to fielded systems. All other supporting activities, including any work on our standalone-classified systems, will https://atlevel1.dtic.mil/at be considered design execution or test systems and are not required to comply with the subject regulations included in this section.

h. For Contracts Requiring Performance or Delivery in a Foreign Country. DFARS Clause 252.225-7043, Antiterrorism/Force Protection for Defense of Contractors outside the United States applies. The clause shall be used in solicitations and contracts that require performance or delivery in a foreign country. This clause applies to both contingencies and non-contingency support. The key AT requirement is for nonlocal national Contractor personnel to comply with theater clearance requirements and allows the combatant commander to exercise oversight to ensure the Contractor’s compliance with combatant commander and subordinate task force commander policies and directives.

i. The Contractor shall produce an OPSEC Standing Operating Procedure/Plan IAW CDRL A009 (DI-MGMT-80934C) within ninety (90) calendar days of contract award, to be reviewed and approved by the responsible Government OPSEC officer. This plan shall include a process to identify critical information, where it is located, who is responsible for it, how to protect it and why it needs to be protected. The Contractor shall implement OPSEC measures as ordered by the commander. In addition, the Contractor shall have an identified certified Level II OPSEC coordinator per AR 530‐1.

2.4 Physical Security:

The Contractor shall be responsible for safeguarding all Government equipment, information and property provided for Contractor use, IAW National Industrial Security Program Operating Manual.

2.5 Contractors Requiring Common Access Card:

Before CAC issuance, the Contractor employee requires, at a minimum, a favorably adjudicated National Agency Check with Inquiries (NACI) or an equivalent or higher investigation IAW Army Directive 2014‐05. The Contractor employee will be issued a CAC only if duties involve one of the following: (1) Both physical access to a DoD facility and access, via logon, to DoD networks on‐ site or remotely; (2) Remote access, via logon, to a DoD network using DoD‐approved remote access procedures; or (3) Physical access to multiple DoD facilities or multiple non‐DoD federally controlled facilities on behalf of the DoD on a recurring basis for a period of six (6) months or more. At the discretion of the sponsoring activity, an initial CAC may be issued based on a favorable review of the FBI fingerprint check and a successfully scheduled NACI at the Office of Personnel Management.

2.6 Facility Security Clearance:

The work to be performed under this contract is up to the TOP SECRET level and will require Sensitive Compartmented Information (SCI) access eligibility for some personnel. Therefore the company shall have a final Facility (Security) Clearance (FCL) from the Defense Security Service (DSS) Facility Clearance Board (FCB) at time of award, IAW the DD254.

2.7 Information Technology:

The following Key Personnel require a minimum of an Interim IT- Level I eligibility at the time of Contract Award:

• Project Manager

• Senior Systems Engineer

• Lead Test Engineer

• Lead Logistics Analyst

The following Key Personnel require a minimum of an Interim IT- Level III eligibility at the time of Contract Award:

• Senior Information Assurance Analyst

2.8 Information Security and Other Miscellaneous Requirements:

a. Contractor personnel shall comply with local security requirements for entry and exit control for personnel and property at the Government facility.

b. Contractor employees shall be required to comply with all Government security regulations and requirements. Initial and periodic security training and briefings will be provided by Government security personnel. Failure to comply with security requirements can be cause for removal.

c. The Contractor shall not divulge any information about DoD files, data processing activities or functions, user identifications, passwords, or any other knowledge that may be gained, to anyone who is not authorized to have access to such information. The Contractor shall observe and comply with the security provisions in effect at the DoD facility. Identification shall be worn and displayed as required.

d. Contractor personnel will generate or handle documents that contain FOUO information at Government facilities. Contractor shall have access to, generate, and handle classified material only at Government facilities. All Contractor deliverables shall be marked at a minimum FOUO, unless otherwise directed by the Government. The Contractor shall comply with the provisions of the DOD Industrial Security Manual for handling classified material and producing deliverables.

e. The Contractor shall afford the Government access to the Contractor’s facilities, installations, operations, documentation, databases and personnel used in performance of the contract. Access shall be provided to the extent required to carry out a program of IT inspection (to include vulnerability testing), investigation and audit to safeguard against threats and hazards to the integrity, availability and confidentiality of data or to the function of information technology systems operated on behalf of DISA or DoD, and to preserve evidence of computer crime.

f. The Contractor and all associated Sub‐contractors shall brief all employees on the local iWATCH program (training standards provided by the requiring activity ATO). This local developed training shall be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR. This training shall be completed within thirty (30) calendar days of contract award and within thirty (30) calendar days of new employees commencing performance with the results reported to the COR NLT forty-five (45) calendar days after contract award.

g. For all Contractors with security clearances. Per AR 381‐12 Threat Awareness and Reporting Program (TARP), Contractor shall receive annual TARP training by a Counterintelligence (CI) agent or other trainer as specified in 2‐4b.

3 GOVERNMENT FURNISHED ITEMS AND EQUIPMENT

The Contractor shall not supplement or replace any Government-Furnished Equipment (GFE), Government-Furnished Software, or other Government-Furnished Material without written direction from the KO. The Contractor shall establish Contractor property management, inventory and accountability procedures and records, as well as maintenance procedures and records for the GFP and describe it in their proposal. In their proposal, the Contractor may request GFP and Government-furnished services that have not been identified herein. Rationale and cost data shall be provided for all such requests.

3.1 Property:

The following Government Furnished Property (GFP) will be provided to the Contractor as required to accommodate the tasking identified in the Integrated Master Schedule (Section 5.2.1):

a. The current functioning, WSTARS/WMII specific version of the software baseline, and support documentation (as described in the applicable Software Version Description, Software Product Specification, As Built Configuration List, and Software Build Procedures) for each of the following WSOMSNET subsystems identified in Section 5.1 :

i. Common Network Planning Software

ii. Global Satellite Configuration Control Element

iii. Replacement Satellite Configuration Control Element

iv. Global Terrestrial Critical Control Circuit System

v. Wideband Remote Monitoring Subsystem

vi. Joint Management Operations Subsystem

vii. Replacement Frequency Modulated OrderWire

viii. Replacement Radio Frequency Interconnecting Subsystem

ix. Remote Management and Control Equipment

b. The current functioning Database and Schema for each of the following WSOMSNET subsystems identified in Section 5.1, as applicable:

i. Common Network Planning Software

ii. Global Satellite Configuration Control Element

iii. Replacement Satellite Configuration Control Element

iv. Global Terrestrial Critical Control Circuit System

v. Wideband Remote Monitoring Subsystem

vi. Joint Management Operations Subsystem

vii. Replacement Frequency Modulated OrderWire

viii. Replacement Radio Frequency Interconnecting Subsystem

ix. Remote Management and Control Equipment

c. The current functioning version of the Satellite Simulation Tool.

d. The DoD Unified Master Gold Disk.

3.2 Services:

The following Government Furnished Services will be provided to the Contractor as required to accommodate the tasking identified in the Integrated Master Schedule (Section 5.2.1):

a. The Government or its designate will assist the Contractor in the installation of, and provide training for the operation of all GFP software baselines listed in Section 3.1.a.

b. The Government or its designate will assist the Contractor in the installation of, and provide the training for the operation of the Satellite Simulation Tool identified in Section 5.8.4.3.2

3.3 Information:

The Government will supply information upon contract award in support of the tasks contained in this CRS – in an easily accessible library on WC’s Internal Knowledge Portal (IKP), for all documents that are in electronic form. Information to be supplied includes information about the capabilities of the facilities in which the WSTARS/WMII is to be installed, existing installation engineering information to be used as input to new or upgraded installation data items, and subsystem interface data. Requests for additional information shall be made directly to the WSTARS/WMII COR. Government Furnished Information (GFI) is noted in Attachments 001- 004 of the solicitation as RLM-WSTARS-C005SSV2 (System Specification) (001), WSTARS CONOPS Final 1 July 15 (002), and WSOMS CPD Inc 2 15 Jun 16 (Draft) (003). Additional GFI to the Contractor will be the Program Executive Office (PEO) Policy Memorandum #12-65 (004)

– PEO EIS Software Code Reviews, the PEO Policy Memorandum #12-65 Attachment – Standard Operating Procedures, and the following documents that describe e the existing DIMS functionality, and associated subsystems interface data:

a. Defense Satellite Communications System (DSCS) Integrated Management System (DIMS) and DSCS Operational Support System (DOSS) - Interface Control Document, Revision 5, July 2002

b. Defense Communications Satellite System Integrated Management System (DIMS - Software Design Document, Version 6.0, January 2010

c. Defense Satellite Communications System Integrated Management System - Administration Guide, Revision 2, 25 August 2015

d. User Guide for DIMS Rev 6 – Appendix A: Troubleshooting Using DIMS, Revision 2, 27 August 2015

e. Wideband Remote Monitoring Sensor (WRMS) Services - Interface Control Document, Version 2.0 – Draft, 3 October 2016

f. Wideband Remote Monitoring Sensor (WRMS) Services - Interface Definition Document, Version 2.0 – Draft, 3 October 2016

g. Technical Report on the GSCCE Use of Objective Defense Satellite Communications System Operational Control System Software Services - Interface Control Document, Revision E, 2016

h. Common Network Planning Software (CNPS) Version 6.0 - CNPS-WSOMS Interface Control Document, Final Revision 1, 18 January 2016

i. Common Network Planning Software (CNPS) Version 6.0 - CNPS-WSOMS Interface Control Document - Annex A: Consumer View Access Guidance, Final Revision 1, 18 January 2016

j. Common Network Planning Software (CNPS) Version 6.0 - CNPS-WSOMS Interface Control Document, Annex B: Producer View Development Guidance, Final Revision 1, 18 January 2015

4 CONTRACTOR FURNISHED ITEMS AND RESPONSIBILITIES

4.1 General:

The Contractor shall furnish all supplies, equipment, facilities and services required to perform work under this contract that are not listed under Section 3 of this CRS.

4.2 Materials:

The Contractor shall be responsible for providing cables, connectors, and other ancillary equipment as required, to configure the WSTARS/WMII systems to full operational states.

Warranties for all equipment/software purchased by the Contractor on behalf of the U.S.

Government shall name the Government as the warrantee.

The contractor shall obtain three quotes for all purchases over the current micro-purchase threshold identified in the FAR and purchase the lowest quote. The contractor shall provide all supporting documentation including waivers, quotes and receipts to the Government, upon request.

Commercial Software Licenses:

a. All software shall, as a minimum, be licensed and priced for use on a single computer or for use on any computer at a particular site.

b. The license shall be in the name of the U. S. Government.

c. The license shall be perpetual (also referred to as a nonexclusive, paid-up, world-wide license).

d. Software documentation shall be identical to that provided to a customer in the general public in the course of a private sale. The Government’s right to software documentation shall be no less than the rights provided with the associated software.

e. The license shall apply to any software changes or new releases.

5 SPECIFIC TASKS

5.1 Performance Requirements:

The WSTARS will be a global information, situation detection, and situational awareness subsystem designed to enhance wideband operations and situational awareness in support of the Wideband SATCOM COI. In addition, knowledge collected and processed by the WSTARS will be available both internally to the WSOMS COI through Zero Client or Virtual Desktop interface, and to authorized users external to the WSOMS Network. The WSTARS/WMII is intended by the Government to enhance trend analysis and anomaly resolution capability over that of which is currently fielded in WSOMS. WMII will enable exchange of wideband SATCOM planning and performance information between primary control subsystems that comprise WSOMS. In addition, WSTARS will act as a central data repository for WSOMS. WMII will also provide mechanisms to allow external users to access WSOMS data.

To enhance trend analysis and anomaly resolution, WSTARS shall be a subsystem that centralizes and consolidates all of the databases of the WSOMS subsystems to including:

Common Network Planning Software (CNPS), Global Satellite Configuration Control Element (GSCCE), Replacement Satellite Configuration Control Element (RSCCE), Global Terrestrial Critical Control Circuit System (GTC3S), Wideband Remote Monitoring Subsystem (WRMS), Joint Management Operations Subsystem (JMOS), Replacement Frequency Modulated OrderWire (RFMOW), Replacement Radio Frequency Interconnecting Subsystem (RRFIS), Remote Management and Control Equipment (RMCE) and any emerging subsystem deemed critical to the operational management of WSOMSNET. The WSTARS shall utilize data analytics engine to perform trend analysis and anomaly resolution in the management of the terrestrial WSOMSNET and also management of the WGS satellite networks.