Redacted PWS_SOO TmNS ADD IDIQ 31 May 24 V1.0.docx

Statement of Objectives For Telemetry Network Standards (TmNS) ADD IDIQ 22 May 2024

INTRODUCTION

With emerging technologies and a changing mission, the 412th Test Wing (412th TW) has set a goal to augment its Telemetry Systems and build a network structure that will provide the ability to have access to, “Any Data, Any Time, Any Where”. As the mission progression pushes deeper into mission systems, and more specifically systems of systems testing, the need to make near real-time informed decisions and support faster turnaround times on test reports is a must.

The Central Test and Evaluation Investment Program (CTEIP) has developed the bi-directional integrated Network Enhanced Telemetry (iNET) project to an Early Operational Capability (EOC) state. The 412 Test Engineering Group (412 TENG) is requiring support to analyze system attributes and progress developments from the released EOC state through multiple Initial Operational Capability (IOC) releases and leading to a Final Operational Capability (FOC). The development goal is to support our test customers with superior tools for real-time mission support and post-test data analysis. The 412 Test Wing has available funding under the Spectrum Relocation Fund (SRF) project to further TmNS developments and integrating the technologies into the Range.

PURPOSE

The 412 TENG is dedicated to meet Telemetry Network Standards (TmNS) developed under the Range Commanders Council (RCC) Telemetry Group (TG). Meeting these standards will best position the 412 TENG in supporting interoperability needs with neighboring Test Ranges. The iNET capability is the only system that meets the RCC TmNS standards to date and developing efforts will be focused on maturing and integrating the technology into range infrastructure. The purpose of this delivery order is to establish an IDIQ contract that allows for delivery order to the following requirements:

· EQDR Software development and Systems Engineering:

The Enhanced Querry Data Recorder (EQDR) is a software application developed under a Test Resource Management Center (TRMC) Science and Technology (S&T). The program allows for real-time data extraction/playback while concurrently recording data Streams (read; while write capability). The application will be a critical component to support the 412 TENG future mission. EQDR support is identified as:

· EQDR Enhancements – The goal is to improve general usability of the system and enhance integration of EQDR with the Edwards range infrastructure. Examples include, MDL version enhancements, TmNS data capabilities development (e.g. ability to run complex data queries across Data Values (Min., Max, and Thresholds), Time intervals, and/or data packet types., and network status acquisition), and on-board data processing capabilities development.

· Airborne PCM-to-TmNS gateway - The Airborne PCM-to-TmNS Gateway development can provide a physical and logical bridge between traditional PCM (clock and data) inputs and TmNS network messages onboard a test article. The benefit is that the EQDR and other TmNS components will be able to be interoperable DAUs that are not TmNS-enabled.

· Ground EQDR/TmNS-to-MCS gateway - The TmNS/EQDR-to-MCS gateway development can provide an interface between a ground-based EQDR and the Edwards Mission Control System (MCS). This gateway will support complex scenarios of ground-based and airborne-based recorders working together in a coordinated fashion to minimized retransmission requests over the air.

· TmNS System Engineering – The purpose of this task is to assist in the planning development, integration, and testing of operationally supportable and sustainable TmNS capabilities using the EQDR. The TmNS architecture will require numerous, Commercial and Government owned systems, operating collectively in a systems-of-systems environment. This task will provision for the support to developments in support of TmNS are planned, integrated, and tested appropriately.

· EQDR Technical and Product Support:

· Support services shall be provided on an as-needed basis, supported through on-site or on-call, to ensure successful product integration and operational use.

· Secure Telemetry System Engineering and Technical Services:

· Secure TM development – The objective of this requirements is to support the design and upgrade of secure telemetry units to ensure effective execution and operative integration in support of serial and bi-directional communication. The KS-750 encryptor/decryptor modernization effort is a critical element in the pursuit of TmNS operations and will be crucial in meeting current and future test needs and Information Assurance (IA) directives. The development of replacement airborne Secure Telemetry units is a critical element to support future Secure Telemetry requirements and to support SST transmitter Command and Control (C2).

SCOPE

The contractor shall provide all labor and travel necessary to satisfy the requirements of this contract. Unless otherwise specified, the contractor shall provide development and system engineering services as specified in a Delivery Order or Task Order authorized by the Contracting Officer.

The primary services are described herein:

· EQDR Software Development and Technical Services – CLIN 0001

· Secure Telemetry Engineering Technical Services – CLIN 0002

· Technical Support and Field Service – CLIN 0003

TECHNICAL REQUIREMENTS

EQDR Software Development Services The objectives of these requirements are to provide operational sustainment, enhancement, development, and general support services for EQDR software. Meeting these objectives will enable the EQDR to support T&E mission needs. The Contractor shall provide the following support services:

Software Enhancements The Contractor shall provide services for software enhancements identified and prioritized by AFTC personnel. A software enhancement is defined by modifications to software to improve performance, attributes, or adapt the product to a modified environment. The Contractor shall identify a release date and version in which the identified enhancements will be delivered.

New Capabilities The Contractor shall provide services for creating new software capabilities identified and prioritized by AFTC personnel. A Software capability is defined by modifications to software in order to produce new functionality not currently available within the software. The Contractor shall identify a release date and version in which the identified capability will be delivered.

Bug Fixes The Contractor shall provide services to fix software bugs identified and prioritized by 412TW personnel. A software bug is defined as an error, flaw, failure, or fault in the program that causes it to produce an incorrect or unexpected result, or to behave in unintended ways. Bug fixes shall be reported to the Contractor via the Contractor’s standard deficiency reporting process. The Contractor shall identify a release date and version in which the identified bug will be fixed.

Software Maintenance The Contractor shall provide unified version updates that incorporates both commercial and Government updates to support operating system advancement, information assurance, and interfaces. The Government shall provide or make available all necessary hardware and software components required to conduct development, testing, and verification.

Operating System (OS) and System Driver Updates The Contractor shall provide version updates to support operating system advancement. Version updates shall ensure compliance with current commercial operating system and system drivers. The Contractor shall identify a release date and version in which the identified OS updates will be available.

Information Assurance (IA) Requirements The Contractor shall provide version updates required to maintain compliance with Information Assurance (IA) requirements. (e.g. operating system, approved software, Security Technical Implementation Guidelines (STIGs), etc.). The Contractor shall identify a release date and version in which the identified IA updates will be available.

Interface Upgrades The Contractor shall provide version updates to support interface modifications as a result of change to any of the DoD and commercial systems (e.g. MCS or IADS interface). The Contractor shall identify a release date and version in which the identified interface updates will be available.

Systems Engineering The contactor shall provide engineering support for the planning development, integration, and testing of operationally supportable and sustainable TmNS capabilities using the EQDR. Efforts will include, but will not be limited to, the identification any technology gaps that exist requiring development, recommend design alternatives to close gaps, and assistance with requirements generation to complete development efforts. The goal for the task is to analyze and develop system elements and desired capabilities to ensure the successful integration of EQDR into lab and operational TmNS system to optimizes performance and utility for users requiring dynamic data access, processing, and display.

Documentation At the conclusion of each software release cycle, the Contractor shall provide the Government with documentation for the release, executable files, updated online help files associated with the release, updated user manuals associated with the release, and a Software Version Description Document for the release. The Contractor’s format for the User Documentation is acceptable.

Secure Telemetry Products and Engineering Technical Services Description of Development and Engineering Services The Contractor shall develop and/or review the technical requirements and build-to specifications for upgrading legacy encryption and decryption units meet the government’s requirements (e.g.to network compatible decryption devices, provide bi-directional IP encryption/decryption, maintain serial encryption/decryption capabilities, …).

Design The Contractor shall provide engineering support Air Force efforts to develop new ground and airborne Secure Telemetry units that may provide the following (but not limited to) generic characteristics:

· Encrypt/Decrypt (two channels one encrypt/one decrypt) RCC-218-20 TMoIP data, including TMoIP data that encapsulated IAW IRIG-106-20 DQE.

· Encrypt/Decrypt (two channels one encrypt/one decrypt SST. The Encrypt capability will be the same functionality for SSTG, and additionally will provide capability to output (black side) TMoIP (cipher text payload) from either (red side) input TMoIP (plain text payload) or serial PCM plain text data.

· Decrypt two channels of SST.

· The Software/firmware/hardware designs will comply with NSA requirements to garner High Assurance Device (HAD), formerly Type 1 COMSEC unit Cybersecurity Certification.

· Output TMoIP formatted decrypted data where cipher text telemetry payload (or DQE telemetry cipher text payload is replaced with plain text payload (or DQE plain text payload) or output serial streaming telemetry (and clock).

· Process plain text TmNS input messages and bypass same to red side output.

· Encrypt/decrypt IP data.

Integration

· The Contractor shall support prototype testing and provide a sub-system design/requirements document alternatives and design tradeoffs for the integration of units into the into the 412TW mission systems to support secure telemetry flight test operations.

Documentation

· Technical Requirements Documents (TRD) and technical reviews of same.

· Subsystem Design for 412TW Integration

· Management Plan to meet Air Force/NSA Cybersecurity effort.

Reviews and meetings

· The task will also include attending SRR, PDR, CDR and other technical coordination meetings, reviewing and providing reports on the vendor product reviews, and preparing briefings to cover the Air Force response to the vendor submittals.

· The contractor shall also participate in developing concept of operations documentation and the functional, performance, acceptance and operational test methods and procedures.

· The contractor shall participate in the Air Force/NSA cybersecurity certification process, reviewing vendor proposals to meet cybersecurity requirements, NSA re-design direction/feedback to the Air Force, and aid in formulating efficient response that will maintain product performance and meet NSA requirements.

Technical Expertise

· The contractor shall have demonstrated networked and serial streaming telemetry processing expertise in designing/developing telemetry processors, writing telemetry processing requirements and standards for Secure Telemetry applications, and knowledge and experience with Range Commanders Council (RCC) Telemetry Group (TG) Standards; specifically, IRIG 106 (SST, TMATS, Chapter 10/11 recording), telemetry processing for Telemetry Network Standards (TmNS), and RCC-218.

· The Contractor shall have demonstrated experience and knowledge with integration of telemetry products into the 412 TW range and airborne instrumentation infrastructure, including its Mission Control System (MCS) or in similar substantiated integrations.

· The contractor shall have demonstrated experience and knowledge with Rish Management Framework (RMF) principals. RMF principals shall include documented approach for risk identification, assessment against Security Technical Implementation Guides (STIGs), mitigation, and governance.

Technical Support and Field Services Telecommunications or Field Response The contractor shall define the type and quantity of technical support, via telecommunications, or via field support. The contractor shall propose the basis for technical support charges (e.g. per incident, by labor hour, or other). Any travel required in support of field services will be provided in the price proposal. The pricing of telecommunications and field support shall be based upon the negotiated pricing.

Response time for support shall be 48 hours or less from time of notification. In special cases where the technical issues cannot be resolved by telephone, the contractor shall provide on-site support within 48 hours of notification.

Training The contractor shall define the type and quantity of training support, at the factory, via telecommunications, or at a government facility. The contractor shall provide technical training, as required, upon receipt of delivery/task order. The pricing of each effort shall be based on the negotiated pricing.

DELIVERABLES

Types of Deliverables

Data Deliverables

Data Deliverable, CDRL / DID reference index and summary A001 Price Proposal – DI-FNCL-81116 A002 Presentation Materials - DI-ADMN-81373 Deliver electronically 3 workdays prior to scheduled video conference meetings. Deliver one (1) week before TIM and design reviews. Deliver four (4) weeks before conferences to ensure time for review for public release.

A003 Review Presentations and Meeting Minutes – DI-ADMN-81505, with tailoring for deliveries 7 days before and after meetings.

A004 Technical Report – DI-MISC-80652, with tailoring to N/A DID para.7.2 and 7.3, 10.2 e-format is acceptable.

A005 Training Materials – DI-SESS-81697, with tailoring for delivery 10 days before class.

A006 Test Procedure - DI-NDTI-80603 A007 Acceptance Test Plan - DI-QCIC-80553A A008 Acceptance Test Report – as above, with tailoring to include test data, results, and conclusions.

A009 Qualification Test Plan – DI-IPSC-81438 A010 Qualification Test Report – DI-QCIC-81890 A011 Software Version Description – DI-IPSC-81442A A012 Interface Control Document – DI-SESS-81248B, with tailoring to include specified content.

A013 O&M manuals and instructions – DI-MISC-81414 A014 Status Report – DI-MGMT-80368, with tailoring for content A015 Software Design Description - DI-IPSC-81435 A016 Supplier's Configuration Management Plan - DI-SESS-80858

ADDRESSES FOR DATA:

Steven Davies Technical Project Manager

812 TSS/ENTI

Ronald Pozmantier Chief Engineer

812 AITS/ENI

PZ: TBD

Delivery Requirements The Contractor shall deliver reports as identified in section 4.1.

Document Marking All documents containing technical information shall be marked as follows unless approved for public release:

Distribution Statement D:

Distribution authorized to the Department of Defense and U.S. DoD contractors only due to the need to protect technical or operational data and/or export limitations as determined on 2 October 2017. All requests for this document shall be referred to the Program Manager, 812 TSS/ENTI, Edwards AFB, CA 93524.

Release of Information The contractor shall not release any information to any person, Government agency, or contractor concerning the program under this delivery order without the approval of the Government Program Manager.

Delivery Instructions The contractor shall deliver, and successfully complete requirements as called out in section 1.3 and deliver to 304 E. Popson Blvd. Edwards AFB, CA 93524.

GENERAL INFORMATION

Period of Performance The period of performance for this delivery order is not to exceed 60 months after receipt of order (ARO).

Project Manager The contractor shall designate a Project Manager who shall be responsible for the control and coordination of all work performed on this delivery order. The contractor shall provide the project manager’s name, in writing, to the PCO within 7 days after issuance of delivery order.

Program Status The contractor shall monitor performance and cost of all delivery orders IAW the applicable clauses of the contract.

Travel The Contractor shall be required to travel as needed for support. The Government shall incur travel costs. The Contractor must budget for travel and gain approval from the Government before incurring travel costs.

Site Visits Site visits for field services shall be scheduled through the Government Technical Project Manager or designated representative.

Place of Performance/Delivery Work is primarily performed at the contractor’s facility. Technical Interchange Meetings may require secured communication and will be performed at Government Facility: Bldg. 1600, Edwards AFB, CA 93524.

Security Clearance A supplemental DD254 is required for this task. Contractor will require Common Access Card (CAC) for E-mail and Teleconferencing services. Access to classified data, and handling of COMSEC materials is required for this effort. Contractor personnel working on this task shall be capable of holding a Secret Security Clearance.

Government Furnished Assets

Government Furnished Facilities None.

Government Furnished Equipment or Property As required, the Government shall provide necessary GFP to the contractor within 60 days after receipt of delivery/task order. GFP includes property furnished for repair, maintenance, overhaul, or modification.

Government Furnished Information (GFI) As required, the Government shall provide necessary GFI to the contractor within 60 days after receipt of delivery/task order. GFI includes property furnished for repair, maintenance, overhaul, or modification.