SCES PWS - Draft RFP.docx

uni PERFORMANCE WORK STATEMENT (PWS)

1. Contracting Officer’s Representative (COR).

a. Primary COR. See DITCO Additional Text G1 - Points of Contact

b. Alternate COR. See DITCO Additional Text G1 - Points of Contact

c. Property Administrator

2. Contract or Task Order Title. Satellite Communications (SATCOM) Engineering Support (SCES)

3. Background. The Defense Information Systems Agency (DISA) Program Executive Office for Transport (PEO-Transport) acquires, develops, fields, and sustains SATCOM and terrestrial transport and end-user capabilities world-wide in support of the Department of Defense (DoD), Combatant Commands, Military Services, and Government Agencies. These capabilities extend the Defense Information Systems Network (DISN), using Military SATCOM (MILSATCOM), Commercial SATCOM (COMSATCOM), and other transport capabilities, enabling a vision for any information flow from any source to any gateway, uplink, satellite, deployed terminal, or user for any purpose, regardless of location or time.

This requirement provides engineering and test support services to PEO-Transport for SATCOM teleport capabilities, systems engineering, architecture and standardization efforts, data transport and spectral monitoring tools, and Airborne Intelligence Surveillance and Reconnaissance (AISR) data transport and video dissemination. Combined, these capabilities provide critical support to the warfighter by enhancing joint forces interoperability through secured access to voice, video, data, and transport services. PEO-Transport responds to the warfighter's direct SATCOM needs and provides flexible integration points throughout all phases of conflict.

Capabilities and efforts covered in this effort include, but are not limited to:

The DoD Teleport System:

I. The Teleport System is a system of systems at DoD SATCOM Gateways worldwide. Teleport Generation One fielded military and commercial SATCOM terminals including Ku-Band terminals, C-Band terminals, Ultra-High Frequency (UHF) terminals, Extremely High Frequency (EHF) terminals, and Ka-Band terminals.

II. Teleport Generation Two fielded Time Division Multiple Access (TDMA) SATCOM modems, Global Broadcast System (GBS) modem subsystem, and a converged, net-centric baseband system, providing serial and Internet Protocol (IP) based transport and services including NIPRNet, SIPRNet, Defense Switch Network (DSN) Voice, Defense Red Switch Network (DRSN), Voice over IP (VoIP), Voice over SIPRNet (VoSIP).

III. Teleport Generation Three fielded Advanced EHF (AEHF) SATCOM terminals, Modernization of Enterprise Terminals (METs), which replaced legacy X-Band terminals; and currently being fielded is the Mobile User Objective System (MUOS) to Legacy UHF Gateway Component (MLGC). Capabilities included under MLGC are MUOS Voice Gateway (MVG), and MUOS to DISN (M2D).

Global Broadcast Service (GBS):

The GBS was designated a Joint Program in March 1996 with the primary purpose of disseminating information worldwide over a high-speed one-way satellite broadcast to users throughout all DoD Areas of Responsibility (AORs). It primarily provided unmanned aerial vehicle (UAV) video dissemination but has since evolved several times to support a wide range of communication transport needs. It has adopted an open commercial off-the-shelf based architecture, migrated to an IP transport, and added two-way communications for users to request and uplink content.

Gateway Video Reception and Distribution System (GVRDS):

The GVRDS effort establishes seven (7) unclassified video news feeds down linked into the Northwest (VA) SATCOM Gateway for transport via the DISN Core to the DISA Hosting and Compute Centers (HaCCs) for processing and re-transmission in support of the GBS broadcast to disadvantaged Warfighters and Ships under Way.

Satellite Star (SATSTAR) and Survivable Super High Frequency (SSHF) Capabilities:

DISA is responsible for system engineering to provide worldwide communications connectivity for the E-4B in support of the Secretary of Defense (SecDef) and other senior leadership travel communications requirements, utilizing Wideband Global SATCOM (WGS) constellations of satellites. The SATSTAR network is currently undergoing a significant modification/tech refresh to remove the current legacy equipment and replace them with a logistically supportable variant of circuit-to-packet devices. The SSHF system will be a modern, resilient capability transformation for the E-4B platform, operating over multiple frequency bands with a variety of waveforms. The SSHF system will provide the aircraft a worldwide IP architecture over an advanced Modem for an alternate to the Enhanced Pentagon Capability (EPC).

AISR Data Transport (AISR DT) and Data Dissemination System:

DISA provides the foundation for DoD's Airborne Intelligence, Surveillance, and Reconnaissance (A-ISR) transport, directly supporting Joint ISR Full Motion Video (FMV) critical missions. The program objectives are to develop, field, and sustain an enterprise global data dissemination capability to support worldwide distribution of FMV to key warfighting and processing, exploitation, and dissemination cells. Additional program objectives are to develop, field, and sustain an enhanced, resilient AISR spread spectrum and two-way broadcast service satellite connectivity to DoD Gateways to provide worldwide tactical to strategic connectivity for FMV and other high bandwidth ISR data traffic.

Applicable to only Option Year (OY) 3 and OY4:

Data Controller Tools:

DISA sustains the DISA Integrated Waveform data controller capability known as PDA-184 to provide data connectivity for UHF SATCOM users while also pursuing follow-on data controller capabilities to meet newly identified warfighter requirements.

Applicable to only OY3 and OY4:

SATCOM Systems Engineering, Architecture, and Standardization:

DISA leads end-to-end systems engineering efforts to ensure integration and synchronization of DoD SATCOM capabilities through the development of reference architectures, transition plans, and technology analyses. DISA also leads DoD efforts to standardize all MILSATCOM systems to ensure interoperability and efficient performance.

4. Objectives: The objective of this requirement is to provide contractor support to the PEO-Transport with engineering and test support and expertise for SATCOM and SATCOM Transport related capabilities. The specific goals and expectations of this effort are designed to provide the maximum integration, reliability, and interoperability for the DISN, and associated PEO-Transport programs and systems.

5. Scope. This effort provides systems engineering and test support related to SATCOM, Teleport, and associated transport capabilities.

The Government may require surge support during the base or any option period of the requirement. Surge modifications will be within the scope of the effort and provide increased support for the defined task areas of this PWS. Surge support over the life of the contract will not exceed TBD percent of the contractor’s total proposed cost / price for the base and all option periods, excluding any six-month extension of services pursuant to Federal Acquisition Regulation (FAR) 52.217-8.

The following Systems Engineering, Technology, & Innovation (SETI) Indefinite Delivery / Indefinite Quantity (ID/IQ) contract performance areas from the list below apply to the work to be performed:

· Performance Area 1 – Systems Engineering

· Performance Area 2 – Design Analysis

· Performance Area 3 – Systems Architecture

· Performance Area 4 – Software Development

· Performance Area 5 – Systems Integration

· Performance Area 6 – Test & Evaluation

· Performance Area 7 – Deployment & Lifecycle Engineering

· Performance Area 8 – Special Systems Engineering Requirements

· Performance Area 8 – Subtask 1 – Network Engineering

· Performance Area 8 – Subtask 2 – Satellite Communications Engineering

· Performance Area 8 – Subtask 4 – Cybersecurity Engineering

· Performance Area 8 – Subtask 5 – Information & Knowledge Engineering

· Performance Area 8 – Subtask 9 – Emerging Technologies

6. Performance Requirements.

The requirements described below are subject to the following conditions:

· The contractor is required to use Government-designated network devices in the performance of this effort.

Government Rights: All hardware, firmware, and software acquired by the contractor and any deliverables developed by the Contractor for supporting Government requirements shall become the property of the U.S. Government. The Government’s technical and data rights regarding all hardware, firmware, and software items enhanced under this contract shall be governed in accordance with FAR clauses 252.227-7013 and 252.227-7015 of the contract.

· Contractor Purchases: The contractor may need to purchase miscellaneous items of hardware and software under this contract. All items purchased by the contractor on behalf of the Government shall be documented appropriately on Form DD250.

· Comply with DoD baseline Information Assurance (IA) Controls including those documented within the Security Technical Implementation Guides (STIGS), DoD policies and procedures and DISA Instruction 630-230-19, Information Assurance (IA), March 2007.

· All capabilities, services and products shall adhere to all applicable Federal, DoD, and DISA policies and guidance. The contractor shall comply with FAR clause 239.7103 (a), Protection against Compromising Emanations (June 2004).

· The contractor may have access to planning information, live data, proprietary data, and records that are sensitive and/or classified. The contractor shall not divulge information about Government files, procurement, and source selection activities, or any other sensitive or classified information to anyone who is not authorized to have such information.

6.1 Task 1 – Engineering Program Management. (Firm Fixed Price (FFP))

6.1.1 Integration Management Control Planning.

The Contractor shall designate a Contractor Program Manager (CPM). The CPM shall perform the duties of the Prime Contractor and shall use the Contracting Officer Representative (COR) and Alternate COR (ACOR) as the primary points of contact for all requirement activities. The Contractor shall report any programmatic and/or technical issues to the COR and ACOR immediately via email, as well as in the Task Order Management Plan (TOMP) and the Monthly Status Report. The Contractor shall track issues and provide resolution to issues within five (5) business days. The Contractor shall ensure all work is planned and executed in an integrated manner to achieve cost, schedule, and technical performance objectives and is handled in accordance with the DISN Security Classification Guide (SCG).

The contractor shall provide an updated Supply Chain Risk Management (SCRM) Plan to the COR and Program Manager within five (5) business days whenever there is a change that affects one or more security controls as described in the Committee on National Security Systems Instructions (CNSSI) 1253 Appendix D (companion publication to National Institute of Standards and Technology (NIST) Special Publication (SP)). At a minimum, the following events will require a SCRM Update: changes in company ownership, changes in senior company leadership, supplier changes, subcontractor changes, and Information and Communications Technology (ICT) supply chain compromises.

6.1.2- Task Order Management.

The Contractor shall provide task order level management support to ensure successful completion of each task. The Contractor shall oversee all task level activities and provide the leadership to meet deliverable targets, maintain staffing at levels required to satisfy customer requirements, interface directly with Government leads for all supported areas, and exercise control over all assigned task personnel. All TS/SCI tasks identified by the Government shall be managed by the Government with support from TS/SCI cleared contractors. The Contractor shall establish, implement, and maintain a task order management system that provides timely, reliable, and verifiable information to the Government. The Contractor’s task order management system shall track the status of each task order from planning to completion, estimate time to complete activities, provide associated milestones, reflect associated risk, record projected and actual resources (cost and personnel), and summarize technical activities expended, problems and deficiencies, impacts and recommended solutions on each task order. The Contractor shall ensure all applicable engineering milestones are included in the TOMP.

6.1.3 - Meetings and Reviews.

The Contractor shall hold a kickoff meeting at the task order level within 15 business days after the contract award or unless otherwise specified in the order. At a minimum, the Contractor shall present, for review and approval by the Government, the details of the intended approach, work plan, and project schedule for each effort. Dates, locations (can be virtual), and agenda shall be specified at least five (5) calendar days prior to the meeting. At minimum, invitations for attendance shall be provided to the Contracting Officer (KO), COR, and Government Program Managers. The Contractor shall record meeting minutes and submit to the COR and ACOR within five business days after the conclusion of the meeting. The Contractor shall attend quarterly Program Review meetings with the COR and ACOR to address overall program status and provide details regarding technical, programmatic, scheduling, service implementation, completion, operation, administration, and management issues. The Contracting Officer is the only individual authorized to make changes to the PWS and the requirements.

6.1.4 – Posting of Deliverables.

The Contractor shall use the Government-owned DISA electronic infrastructure to post, store, manage, and deliver to the Government technical data assembled as described as deliverables in this PWS.

6.1.5 – Data Rights.

The Government will retain data rights in all deliverables created by the Contractor shall perform the duties under this contract in accordance with Defense Federal Acquisition Regulation Supplement (DFARS) 252.227-7013, 252.227-7014 and 252.227-7015. Other DFARS clauses incorporated by reference or included in the contract shall also be applicable. The Government will acquire: (a) “unlimited rights” in all noncommercial technical data and noncommercial computer software and noncommercial computer software documentation created exclusively with government funding; and (b) “Government purpose rights” in all deliverables created with Government and private funding. The Contractor shall provide written notification to the Government Thirty (30) days prior to delivery if any deliverables will be delivered with “limited” or “restricted” rights under DFARS 252.227-2013 and 252.227-7014. The parties agree that the Government shall also acquire “unlimited” rights as defined in DFARS 252.227-7013, in all information; including but not limited to reports, meeting minutes, management plans, technical reports, white papers, test schedules, procedures and papers, not considered to be technical data created by the Contractor during contract performance. The Contractor shall provide written notification to the Government COR and ACOR of all third-party software, including any open-source software that the Contractor shall use in performing the tasks under this contract and if requested, copies of the applicable licensing agreement for the Government COR and ACOR review and approval.

6.1.6 – Transition.

The contractor shall:

Transition-In. All key personnel/key positions shall be onboarded at start of the period of performance (PoP). 50 percent total staffing shall be complete within 14 calendar days of the start of the PoP and 100 percent within 30 calendar days.

Transition-Out. The contractor shall collaborate with the mission partner (MP) at least 120 calendar days or sooner, prior to the end of the contract, to develop a transition-out plan IAW FAR 52.237-3. Prior to contract expiration, or in the event of a contractual change or turnover, the contractor shall provide at a minimum all materials and support necessary to accomplish a seamless and expeditious transition of the tasks identified in this PWS to the incoming contractor. The contractor shall include electronic copies of the following: all in-progress working files; historical files for all tasks; Concept of Operation (CONOPS) procedures, and final phase out meeting with Government, incumbent and the new contractor. The contractor shall support a formal contract close-out process, including the documenting of lessons learned throughout the life of the contract. All deliverables shall be provided 30 calendar days before the end of the contract.

Deliverables:

PWS

Task #

SCG Read and Understood

quarterly

Plan

6.1.1, 6.1.2

6.2 Task 2 – Communications Engineering.

This task includes engineering activities to implement DISN connectivity with content sources, the DISA Core Data Centers (CDC), DoD Gateways, and other Department of Defense Information Network (DODIN) enterprise services and tactical systems in compliance with the DoDI 5000.02 framework. When combined, these objectives will provide effective integration, reliability, and interoperability for associated systems of systems (SoS) and stakeholder content.

6.2.1 Requirements Analysis & Technical Consultation.

The contractor shall conduct a System Requirements Review/System Functional Review (SRR/SFR) to analyze project cost, schedule, and performance requirements to determine sufficiency for developing technical solutions for the capabilities covered in this effort. The contractor shall document assumptions and risks. The contractor shall provide technical consultation to internal and external agencies customers and partners to refine requirements and to provide potential courses of action to provide transport connectivity between multiple communications gateways.

The contractor is responsible for providing the following deliverables to the program office as requested:

Deliverables:

· Briefing and materials, white paper, point papers / memorandums, meeting minutes, flowcharts, after action reports, Standard operating procedures (SOPs), Concept of Operations (CONOPS)

· Systems Requirements Review / System Functional Review (SRR/SFR)

· Program and project Requirements Analysis documentation

6.2.2 Preliminary Designs.

The contractor shall provide preliminary designs in support of the capabilities and project requirements. Preliminary designs include the initial design mapped to requirements, testing requirements, and Rough order of Magnitude (ROM) solutions with the initial Manufacturing Bill of Materials (MBOM), and a cost estimate. The contractor shall prepare artifacts for Preliminary Design Reviews (PDRs) and other decision forums.

The contractor is responsible for providing the following deliverables to the program office as requested:

Deliverables:

· Briefing and materials, white paper, point papers / memorandums, meeting minutes, flowcharts, after action reports, Standard operating procedures (SOPs), Concept of Operations (CONOPS)

· Preliminary Design

· PDR Artifacts

· Analysis of Alternatives

· Preliminary Engineering Implementation Plan

· Rough order of Magnitude (ROM) solutions

· Preliminary Manufacturing Bill of Materials (MBOM)

· Preliminary life cycle cost estimate

· Preliminary Test Plans

· Program and project Requirements Preliminary Design documentation

· DoD Architectural Framework Architectures

6.2.3 Final Designs.

The contractor shall provide final designs in support of the capabilities and project requirements. Final Designs include complete design solutions mapped to requirements, test results, final MBOM with costs. The contractor shall prepare artifacts for Critical Design Reviews (CDRs) and other decision forums.

The contractor is responsible for providing the following deliverables to the program office as requested:

Deliverables:

· Briefing and materials, white paper, point papers / memorandums, meeting minutes, flowcharts, after action reports, Standard operating procedures (SOPs), Concept of Operations (CONOPS)

· CDR Artifacts

· Updated Engineering Implementation Plan

· Final Engineering Implementation Plan

· Final Manufacturing Bill of Materials (MBOM)

· Final Test report

· Final life cycle cost estimate

· Program and project Requirements Final Design documentation

6.2.4 Implementation Plans.

The contractor shall provide engineering plans to incorporate project solutions into the multiple DoD Communications Gateways. The contractor shall develop the Request for Work (RFW) to develop any needed system management capability.

The contractor is responsible for providing the following deliverables to the program office as requested:

· Briefing and materials, white paper, point papers / memorandums, meeting minutes, flowcharts, after action reports, Standard operating procedures (SOPs), Concept of Operations (CONOPS)

· Implementation Plan

· Configuration Guide

· Implementation Guide

· Request for Work (RFW) Documentation

· Configuration Management updates to the major equipment list (hardware, software, firmware, licenses, and warranties)

6.2.5 Tier III Engineering Support.

The contractor shall provide Tier III Engineering support in response to internal and external requests and escalations. Troubleshoots and resolves system issues and problems, develops configurations for systems and capabilities, maintains equipment baseline configuration, provides training, and provides analyses/recommendations/lessons learned reports.

Tier III expertise is required in the following areas: Terminal, Modem, and baseband equipment configurations (Router, Switch, etc.). End-to-end connectivity for voice, video, and data capabilities. Multicast Routing, IP V4/V6 Networking, MPLS Networks, SONET Networks, VPN services, SD-WAN, Dynamic Multipoint VPNs and other network service configurations and architectures. Encryption Device Configurations, and also experience with Cryptography Equipment.

The contractor is responsible for providing the following deliverables to the program office as requested:

Deliverables:

· Briefing and materials, white paper, point papers / memorandums, meeting minutes, flowcharts, after action reports, Standard operating procedures (SOPs), Concept of Operations (CONOPS)

· Operations documentation (SOPs, TTPs)

· Analyses, recommendations, and lessons learned reports.

6.2.6 Circuit Engineering.

Provide program and project updates to register circuit in various registration and cyber databases (SNAP, SGS/GIAP, DISA Storefront, DISA Market Place, Oracle MetaSolv Solution (MSS),) in support of capabilities and projects.

The contractor shall produce:

- intra-and inter-theater network/system drawings at the IP and Optical layers

- end-to-end circuit designs in support project requirements.

- Circuit ordering requests

The contractor is responsible for providing the following deliverables to the program office as requested:

Deliverables:

· Briefing and materials, white paper, point papers / memorandums, meeting minutes, flowcharts, after action reports, Standard operating procedures (SOPs), Concept of Operations (CONOPS)

· Registration and cyber databases updates

· Network and system drawings

· End-to-end circuit designs

6.2.7 Configuration Management.

The contractor shall support change management activities to maintain system baselines for the capabilities and project requirements. The contractor shall represent capabilities and projects at internal and external Configuration Control Boards.

The contractor shall:

- Update entries in the DISN configuration management database (MSS/NCCM-R).

- Update configuration management (CM) database to capture events (adding and removal of equipment, configuration, and reservation of ports, etc.)

- Create discrepancy reports between database records and live equipment

- Update the database to correct identified discrepancies

- Develop and update a CM plan

- Develop and maintain a system baseline control document

- Develop and maintain site-specific system baseline control documents

- Develop and maintain the Major Equipment List

- Conduct Physical Configuration Audits (PCA)

The contractor is responsible for providing the following deliverables to the program office as requested:

-Briefing and materials, white paper, point papers / memorandums, meeting minutes, flowcharts, after action reports, Standard Operating Procedures (SOPs), Concept of Operations (CONOPS) -Configuration Management Plan -Baseline Control Documents -Major Equipment List -PCA reports -Management databases and documentation -Discrepancy reports

6.2.8 Operations Support and Safety.

The contractor shall provide technical support over life cycle for issue resolution on the operational systems and ensure that the systems are safe to operate. The contractor shall perform safety inspections, as required. Operations Support and Safety ensures that operational system issues are resolved, and safety findings are addressed before and during operations. This is a continual process for all current and future program increments.

The contractor is responsible for providing the following deliverables to the program office as requested:

Deliverables:

· Briefing and materials, white paper, point papers / memorandums, meeting minutes, flowcharts, after action reports, Standard operating procedures (SOPs), Concept of Operations (CONOPS)

· Safety inspection reports

· Safety Letters and Reports

· ECR Process Inputs

6.2.9 Business, Technical and Network Operations (NetOps) Readiness Support.

Assist programs and projects to ensure business, technical, and overarching level of operational risk and NetOps readiness of services will meet the operations and quality of execution to meet customers and end-users’ requirements.

The contractor shall:

Support program and project critical technical and operational reviews now operational acceptance. (e.g., ORB/OAB, CEP, COOP, PPSM, ICSP, CCB, SRUM, ATO reviews, etc.)

(Operational Review Process, now Operational Acceptance - A collection of representatives from organizations across DISA that forms a single body which oversees the Operational Review Board (ORB) or Operational Acceptance Board (OAB). The Board determines the level of operational risk and NetOps readiness of services based on an evaluation of its operations and quality of execution for delivery of agreed services to customers and end-users. Additionally, the NRRB is responsible for the overarching execution, delegation, and escalation of tasks and activities to support and ensure compliance with NetOps milestones and standards. The NRRB promotes use and development of the DISA NetOps Resource Center as the primary source for guidance material authored and maintained by the Operations Center (OP) for the NRRB and NRRP.)

(DISA Chief Engineering Panel - The primary objective of the DISA CEP is to ensure the business, technical, and risk review processes are a systematic evaluation of a product or solution. The CEP examines the acceptance of a product or solution for its intended business use and identifies discrepancies and risks from specifications and standards. These reviews may also provide recommendations and examinations of various alternatives. The reviews ensure the designs will satisfy all aspects of the requirements and that they are in accordance with applicable DISA goals, objectives, and standards. The CEP is supported by DoD Architectural Framework (DoDAF) descriptions. DoDAF viewpoint and model-descriptions will be presented (as required). Examples of standardized DoDAF architectural views and designs.)

Deliverables:

· Briefing and materials, white paper, point papers / memorandums, meeting minutes, flowcharts, after action reports, Standard operating procedures (SOPs), Concept of Operations (CONOPS)

· Program and project commissioning artifacts.

6.2.10 Systems Sustainment Engineering.

The contractor shall provide engineering support to assist in the sustainment, technical insertion and technical refreshing of the sub-systems covered by this effort. This includes the identification, development, proposing of solutions and testing to address end of life / end of support equipment as well as new requirements.

The contractor is responsible for providing the following deliverables to the program office as requested:

Deliverables:

· Briefing and materials, white paper, point papers / memorandums, meeting minutes, flowcharts, after action reports, Standard operating procedures (SOPs), Concept of Operations (CONOPS)

· Technical reviews (Analysis of Alternatives)

· Engineering plans

· Design documentation

· Test plans

· Implementation/Integration Plan

· Configuration Guide

· Implementation Guide

· Configuration Management updates

· Joint Interoperability Certification updates

Deliverables:

Title

Format approved by Government

approved by Government

approved by Government 30 calendar days after requested.

approved by Government

approved by Government

approved by Government

approved by Government

approved by Government

approved by Government

approved by Government 30 calendar days after requested.

approved by Government

approved by Government

approved by Government

approved by Government

approved by Government

approved by Government

approved by Government

As requested, estimated 1X/monthly.

approved by Government

approved by Government

As requested, estimated 1X/monthly.

approved by Government

As requested, estimated 6X/year.

approved by Government

As requested, estimated 6X/year.

approved by Government

As requested, estimated 1X/monthly.

approved by Government

As requested, estimated 1X/monthly.

approved by Government

As requested, estimated 1X/monthly.

approved by Government

As requested, estimated 1X/monthly.

approved by Government

As requested, estimated 1X/monthly.

approved by Government

As requested, estimated 1X/monthly.

approved by Government 21 calendar days after requested.

As requested, estimated 1X/monthly.

approved by Government

As requested, estimated 6X/year.

approved by Government 21 calendar days after requested.

Standard Distribution*

As requested, estimated 6X/year.

approved by Government

As requested, estimated 1X/monthly.

approved by Government

As requested, estimated 1X/monthly.

Format approved by Government

As requested, estimated 1X/monthly.

Format approved by Government

As requested, estimated 1X/monthly.

approved by Government

As requested, estimated 1X/monthly.

approved by Government

As requested, estimated 1X/monthly.

approved by Government

As requested, estimated 1X/monthly.

approved by Government

As requested, estimated 1X/monthly.

approved by Government

As requested, estimated 1X/monthly.

approved by Government 21 calendar days after requested.

Standard Distribution*

As requested, estimated 1X/monthly.

approved by Government 21 calendar days after requested.

Standard Distribution*

As requested, estimated 1X/monthly.

approved by Government

As requested, estimated 1X/monthly.

approved by Government

As requested, estimated 1X/monthly.

approved by Government

As requested, estimated 1X/monthly.

approved by Government

As requested, estimated 1X/monthly.

approved by Government

As requested, estimated 1X/monthly.

approved by Government

As requested, estimated 1X/monthly.

approved by Government

As requested, estimated 1X/monthly.

Format approved by Government

As requested, estimated 1X/monthly.

Format approved by Government

As requested, estimated 1X/monthly.

Format approved by Government

As requested, estimated 1X/monthly.

approved by Government

As requested, estimated 1X/monthly.

6.2.10

Joint Interoperability Certification

Format approved by Government 42 calendar days after requested.

Standard Distribution*

As requested, estimated 1X/Quarterly.

*Standard Distribution: 1 copy of the transmittal letter without the deliverable to the Contracting Officer; 1 copy of the transmittal letter with the deliverable to the Primary COR and Alt COR.

6.3 Task 3 - Communications Test and Evaluation (T&E).

T&E is a series of verification and validation processes to ensure that the system meets the design specifications and user requirements. The T&E results will be used to assess design progress and risk throughout the system development life cycle. T&E is a continual process for all current and future program increments including Technology Refresh/Insertion of the existing system.

6.3.1 Test and Evaluation.

The contractor shall:

· Update and maintain program testing-related statutory/regulatory documentation as required by DoDI 5000.02, including, but not limited to, Test and Evaluation Strategy (TES) and TEMP.

· Develop requirement traceability documents and System Test Verification Plan (STVP) to verify requirement.

· Develop test planning and execution activities pertaining to, as appropriate: system demonstrations, integration testing, component testing, Operational Assessments, Confidence Test, Developmental Test and Evaluation, and Operational Test and Evaluation.

· Analyze deficiencies discovered from Operational Test and Evaluation (OT&E), acceptance tests, production reports, and maintenance reports and provide correction actions.

· Reviews and updates briefings, test plans, and test reports to include analysis of the results, observations and issues, lessons learned and recommendations.

· Define, coordinate, and execute a Teleport test strategy per DoDI 5000.02, covering the test life cycle from test planning to execution to reporting phases.

· Evaluate and Lab Test Technology refresh components to validate functional and performance baselines are met prior to fielding new capabilities to the warfighter.

· Analyze and document Joint Information Technology and National Security System Interoperability Certification activities, as well as Operational Test Agency Report of OT&E Results.

· Analyze and document cyber security and survivability related testing.

· Involve in the development of the following documents:

Joint Information Technology and National Security System Interoperability Certification Requirement Traceability Matrix System Test Verification Plan (STVP) Test and Evaluation Strategy (TES) Test Evaluation Master Plan (TEMP)

The contractor is responsible for providing the following deliverables to the program office:

Deliverables:

· Briefing and materials, white paper, point papers / memorandums, meeting minutes, flowcharts, after action reports, Standard operating procedures (SOPs), Concept of Operations (CONOPS)

· Requirement Traceability Matrix

· Test Plan/Test Reports

· Updated Acquisition program documentation

· Test result evaluation reports

6.3.2 Formal Testing and Certification.

For each requested formal test event, the contractor shall create the test scenario and test plan, configure the test environment, execute the test, capture the test results, and create a formal test report. For each successful test event, the contractor shall prepare the needed artifacts for certification and for submission to Configuration Control Boards and other decision forums. Examples include Engineering Change Requests, Implementation Plans, memoranda, and briefings. For major engineering changes, the contractor shall support Interoperability testing events to achieve a Joint Interoperability Certification (JIC).

Deliverables:

· Briefing and materials, white paper, point papers / memorandums, meeting minutes, flowcharts, after action reports, Standard operating procedures (SOPs), Concept of Operations (CONOPS)

· Test Plan

· Test Reports

6.3.3 Informal, Proof of Concept and Operational Testing.

For each informal test whose purpose is to determine a concept’s feasibility, rough configurations or use cases or for operational testing, the contractor shall conduct the minimum testing required to reach a conclusion. The contractor shall provide a test summary that includes the test scenario, findings, resolution/recommendations, and implementation methodology.

Deliverables:

· Briefing and materials, white paper, point papers / memorandums, meeting minutes, flowcharts, after action reports, Standard operating procedures (SOPs), Concept of Operations (CONOPS)

· Test Plan

· Test Reports

6.3.4 Test Automation.

The contractor shall develop and maintain modular and documented baseline test plans that are updated as platforms, services, and capabilities are added to or removed from the various SoS that support the Communications Gateway programs and projects. The contractor shall develop automation scripts to automate the manual test procedures and data capture in order to provide a streamlined and repeatable testing environment. Automation scripts shall be documented and modularized for use in future applications. The contractor shall prove that the automated results match the manual results and document the resource savings with the automation of each module. The results shall be provided in a test automation progress report.

Deliverables:

· Briefing and materials, white paper, point papers / memorandums, meeting minutes, flowcharts, after action reports, Standard operating procedures (SOPs), Concept of Operations (CONOPS)

· Test Plan

· Test Reports

· Automation scripts

· Implementation procedures for Automation scripts

6.3.5 Lab Management.

The contractor shall provide management of DISA Headquarters laboratory spaces for the capabilities covered in this effort. The contractor shall:

· Lead all laboratory activities for the capabilities covered in this TO

· Ensure lab spaces follow all DISA policies and procedures for safety, security, accountability, and operations.

· Develop and maintain lab rack elevation and connectivity drawings.

· Lead projects for lab improvement or expansion

· Work with the government property custodians and hand receipt holders with the management and accountability of lab equipment. Track and facilitate the movement of purchased and loaned equipment into and out of the lab. Prepare shipping/receiving packages and documentation.

· Develop and maintain budgets and spend plans for the lifecycle support of lab equipment.

· Prepare funding packages for lab equipment purchases.

· Develop and maintain lab testing and resource schedules.

The Contractor shall serve as ISSO for all Lab environments and accreditations, and ISSE functions for operational systems administration (Patching and Reporting). The contractor shall have expertise in the DISN, Risk Management Framework (RMF) in accordance with CNSSI 1253 and NIST SP 800-53, DITPR, EMASS database, vulnerability scan analysis risk assessment including mitigations and counter measures, development of accreditation documentation, excellent communication skills in writing to maintain accreditation status for all labs.

The Contractor shall produce:

· complete accreditation package documents including diagrams 90 days prior to accreditation expiration.

· cybersecurity artifacts for each security control identified in the cybersecurity database (e.g. eMASS).

· cybersecurity validation artifacts including hardware, software, and firmware lists; user access lists; equipment configurations and change justifications.

The contractor shall:

· conduct vulnerability scans.

· respond to cybersecurity and operations orders and directives, perform assessments, implement security controls and hardening, and produce Plan of Actions and Milestones (POA&M) documentation.

approved by Government

As requested, estimated 1X/monthly.

approved by Government

As requested, estimated 6X/year.

approved by Government

As requested, estimated 1X/monthly.

approved by Government

As requested, estimated 6X/year.

approved by Government

As requested, estimated 1X/monthly.

approved by Government

As requested, estimated 1X/monthly.

Format approved by Government

As requested, estimated 1X/monthly.

Format approved by Government

As requested, estimated 1X/monthly.

approved by Government

As requested, estimated 1X/monthly.

Format approved by Government

As requested, estimated…