Draft SOW TA components v02.docx

March 20, 2012

INTRODUCTION:

Scope This Statement of Work (SOW) describes the efforts required for the design, development, testing, integration, and demonstration of the Telemetry Network System (TmNS). In addition, it encompasses the option for limited initial rate production items. The TmNS components to be developed are advanced prototypes and reference applications. The advanced prototypes represent the commodity items when produced will be cost effective to satisfy the requirements for aeronautical telemetry as well as other possible telemetric network systems. The reference applications are used to support/control/manage the advanced prototypes as well as production items. This effort is focused on the aeronautical telemetry environment.

Background Project Background The integrated Network Enhanced Telemetry (iNET) is a tri-service project that is tasked via the Director of the Central Test and Evaluation Investment Program (CTEIP), which is a program element under the Office of the Secretary of Defense (OSD), to enable advances in networking and telemetry technology to meet emerging needs within the Major Range and Test Facility Base (MRTFB). The iNET project started as a study to determine the feasibility of network telemetry and worked with the community to produce architectures, interface standards, and design documentation. The TmNS is architected to be an open system that makes maximum utilization of off-the-shelf technology. The goal of the TmNS is to satisfy existing requirements but still have provisions for satisfying additional requirements that can cost effectively support the infusion of emerging technologies. The system design documentation represents, from a system level, an allocated baseline in which to produce components for the TmNS. This baseline is targeted to support the aeronautical test environment but in general is design independent of any particular airframe, weapon system, or range.

Technical Background The concept of network-enhanced telemetry is embodied in the Telemetry Network System (TmNS) which will be used to augment current telemetry systems with network technology. This means that the existing Pulse Code Modulation PCM telemetry systems are expected to operate as they do today in the presence of the TmNS. The TmNS is basically comprised of five subsystems: (1) The Test Article (TA) Subsystem which is onboard a test article that enables communications among devices such as data acquisition units and recorders; (2) the Mission Control Subsystem which communicates with the test article data system to provide data into the existing telemetry processing system; (3) the radio frequency (RF) Subsystem that connects the TA Subsystem with the Range Operations Subsystem; (4) the Range Operations Subsystem which utilizes the existing range network infrastructure to communicate with the RF Subsystem and manage the Serial Streaming Telemetry (SST) functional components on the black-side of the system; and (5) the network Ground Support Equipment (GSE) subsystem, which provides various support functions, necessary to support the operations, maintenance, and checkout of the TA and RF components.

Current communication links based on the Inter-Range Instrumentation Group (IRIG) 106 standard are one-way, dedicated links. Two-way network communication channels can be dynamically shared to provide operation that is more flexible and to optimize spectrum utilization. It is expected that, in the near-term, time critical data such as safety of life data will continue to be moved via the time proven traditional legacy telemetry links. Network connectivity will be used to provide multiple levels of service to other types of data/information, as well as allow the test team to interact flexibly with the test article and its data acquisition system. This increased flexibility will facilitate the RDT&E community meeting the testing demands of future weapons systems while operating within limited spectral resources. As non-critical data and redundant data migrate out of the legacy telemetry links, these links will require less spectrum usage, freeing up spectrum that can be used for shared network links. In order to efficiently utilize the RF (radio frequency) network link and establish a level of interoperability between mission control rooms and test articles, networks will be utilized to enable a reliable and robust data delivery system. The network system provides a Quality of Service that is appropriate for real-time and critical data as well as a reach back capability into the test article for data analysis and anomaly investigations.

Development Documents The development documentation being provided currently represents a mixed level of maturity. The documents describe the requirements and functions required to enable the capability of the interfaces between the system components. The development documentation is meant to help foster interoperability between system components. The documentation will be matured through the advance flight demonstration.

System Demonstrations Integration Integration is planned to occur at multiple levels. (1) The first level of integration will likely occur at each development site. (2) The next level of integration will occur in the various subsystem integration labs. (3) The next level is systems integration. (4) A partial range integration will be conducted as part of the flight test activities, with follow-on integration and support based on each range’s needs and timelines.

Flight Test The flight tests are divided into two phases. The first phase is the developmental flight test that is primarily focused on testing out Radio Access Network. The developmental flight test will occur at Edwards Air Force Base in California. The second phase is the advanced flight test, which is focused on demonstrating the end-to-end test capabilities. The advanced flight test will occur at Patuxent River Naval Air Station in Maryland.

TmNS Components Advance Prototypes The advanced prototypes are TmNS components built using known technologies where the technologies are directly supporting the functionality for the application of the developmental component. The advance prototypes represent the first articles that will be utilized for qualification testing. It is expected that these first articles will be production representative and serve as basis for low rate initial production (LRIP).

APPLICABLE DOCUMENTS:

The documents listed in this section represent the documentation for accomplishing the work described in this SOW.

Requirements Documents System Documents Telemetry Network System Specification Telemetry Network System Design Document Advanced Prototypes Camera Manager Camera Manager Component Development Specification Multi-Function Display Multi-Function Display Component Development Specification Data Acquisitions Units Data Acquisition Unit Component Development Specification Network Data Recorder Network Data Recorder Component Development Specification Network Encryptor Network Encryptor Component Development Specification Network Gateway Network Gateway Component Development Specification Network Router Network Router Component Development Specification Network Switch Network Switch Component Development Specification PCM Gateway PCM Gateway Component Development Specification TA Manager Test Article Manager Component Development Specification TmNS Radio Ground Radio Component Development Specification Ground Radio Software Requirements Specification Queue Manager Software Requirements Specification Test Article Radio Component Development Specification Test Article Radio Software Requirements Specification Voice Gateway Voice Gateway Component Development Specification Standards Documents RF Network Element Standard, Maturity Level 1 – Experimental Version 0.7, January 31, 2010 System Management Standard, Proposed Version 0.08, January 29, 2010 Metadata Standard, Proposed Version 0.08, January 29, 2010 Test Article Standard, Proposed Version 0.08, January 29, 2010 General REQUIREMENTS:

The overall objective of this statement of work is to provide mature TmNS components for the TmNS Demonstration System.

Program Management Work Breakdown Structure The Contractor shall establish a Work Breakdown Structure (WBS) for all work proposed under this SOW. The WBS shall be established in detail to the third level identifying the project tasks, schedule for each task, performance metrics, project milestones, deliverables and other efforts required to achieve the objectives of the project. The WBS shall be delivered with the Contractor’s proposal.

Technical Performance Measures The Contractor shall plan, project out, track, and report Technical Performance Measures (TPMs). The TPMs are identified in the System Specification, Component Development Specifications, and Software Requirements Specifications. The TPMs shall be reported at technical interchange meetings and design reviews. The Subcontractor shall describe in their proposal the process they will use for monitoring and reporting TPMs.

Key Personnel and Subcontractors The Contractor shall identify and provide resumes for all Key Personnel supporting this effort. The list of Key Personnel and Subcontractors shall be delivered with the Contractor’s proposal. The Contractor needs to be aware that many facilities (Government and Contractor) that perform work for the Government restrict access of foreign nationals and this must be taken into consideration in order to fulfill the requirements of this SOW.

Status Reporting The Contractor shall provide a Periodic Status Report (PSR) by the 6th business day of the reporting period for the closing reporting period. The PSR (CDRL A001) shall be in electronic form in an agreed to format and delivered to the Government. The PSR shall be a stand-alone deliverable that addresses the WBS concerning performance, schedule, and cost against the established baseline to the third level, including deliverable status. The Contractor shall also provide a cumulative project summary of accomplishments, tasks accomplishments for the month, tasks planned for the upcoming month, corrective actions for maintaining baseline, and provide forecast relative to the completion of the work identified in this SOW.

Meetings The Contractor shall organize and conduct meetings, and provide meeting minutes (CDRL A002) within five business days of the conclusion of the meeting.

Technical Interchanges The Contractor shall conduct reviews to support the developmental and testing efforts. In addition, the Contractor shall conduct Technical Interchange Meetings (TIM) as required. TIM’s will be conducted on an as-needed basis to discuss issues concerning requirements, specifications, standards, or other topics of importance to the iNET project. These meetings will be conducted at the Contractor’s site and at times via Telephone Conferences or Web Conferencing. For estimating purposes, assume an average of one meeting a month.

Technical Working Groups The Contractor shall participate in Technical Working Group (TWG) meetings that affect the TmNS Radios as the standards are matured through the development process. These meetings will be conducted via Telephone Conferences or Web Conferencing. For estimating purposes, assume an average of one meeting a month.

Reviews Requirements Review The Contractor shall hold a Requirements Review at their facility. The Requirements Review shall be held within 30 days after award of the contract to ensure a common understanding of the contract, specifications, statement of work, and proposal by the Government and the Contractor’s development team. Minutes for the review shall be delivered in accordance with CDRL A002.

Design Reviews The Contractor shall define the occurrences of the Design Reviews for the TmNS components and hold these reviews at the Contractor’s facility. The purpose of the design reviews is to review the progress of work completed and work to be done. The first Design Review shall be conducted within 45 days after the Requirements Review. These design reviews shall be identified in the Program Schedule and agreed upon by the Contractor and the Government. The Design Reviews shall be conducted in accordance with CDRL A003. Minutes for the reviews shall be developed and delivered in accordance with CDRL A002.

Development Phases The effort identified in this SOW will be executed in phases due to resource constraints. In general, the phases will be based on the agreed upon WBS. Near the completion of each phase, at a technical interchange meeting, the phase accomplishments will be reviewed and the next phase activities will be laid out and mutually agreed upon.

Training The Contractor shall develop and deliver a set of comprehensive materials in accordance with CDRL A006.

Course Material and Training Aids The Contractor shall develop the necessary training materials to support the training objectives defined in the Training Course requirement identified in Section 3.9 of the System Specification.

Familiarization Class The Contractor shall conduct an introductory familiarization class using the material provided (Course Material and Training Aids Requirement) at Contractor’s facility for the purpose of describing and demonstrating the deliverable components, test procedures, and any special test equipment used in testing or maintenance of the components. The class shall be conducted at a mutually agreed upon timeframe, but prior to final System Integration and Test.

Government Furnished Items The Government shall not provide any equipment in the performance of this SOW. Software tools are available for use as the Contractor sees fit from https://www.tena-sda.org/display/INET/Home. These tools are offered in good faith as is to support interoperability; however, the Government does not make any claims or guarantees relative to the use of the tools.

Data Rights for Reference Applications The Contractor shall relinquish all copyright and Intellectual Propriety rights to any material (documentation and software) developed under this SOW. It is expected that the deliverables, in whole or in part, delivered under this SOW will be released to the iNET development community.

Advance prototype DEVELOPMENT RequiremEnts The Contractor’s proposal shall describe in detail how they intend to meet these overall tasks using the applicable documents identified in Section 2 of this SOW.

Advance Prototype Development For each component proposed, the Contractor shall design, develop, and manufacture the component in accordance with its Component Development Specification (CDS).

Design and Engineering The Contractor shall design and develop prototype(s) to meet the TmNS specifications utilizing engineering trade-offs between performance, reliability, maintainability, and supportability. The TmNS component designs shall include the performance characteristics, physical characteristics, materials, the software/firmware design elements, basic module description, and interface design.

Manufacture The Contractor shall manufacture advanced prototypes in accordance with specifications. These prototypes shall be used for component qualification testing. See System Specification 3.10.

Deliverable Prototypes The Contractor may propose one or more of the following TmNS of components.

· Airborne TA Manager

· Camera Manager

· Data Acquisition Unit

· Multi-Function Display

· Network Gateway

· PCM Gateway

· TA Recorder

· TA Router

· TA Network Switch

· TmNS Radio

Engineering Tests The Contractor shall perform engineering test(s) to the level necessary to ensure compliance with the TmNS specifications. Where the Contractor fails to meet the requirements identified in the specifications, the Contractor may be required to perform additional testing to determine the level of non-compliance. These non-compliance(s), along with the level of non-compliance, shall be submitted to the Government for approval.

Interface Control Documents The Contractor shall develop and deliver Interface Control Documents (ICDs) in accordance with CDRL A004. These documents shall include: (1) functional interface parameters (i.e. specifications for electronic, electrical, optical, etc.), (2) physical interface parameters (i.e. specifications for dimensions, weight, mounting, connectors, cabling, etc.), and (3) environmental parameters (specifications for vibration, shock, temperature, electromagnetic, etc.).

Component Development Manuals The Contractor shall develop and deliver Component Development Manuals in accordance with CDRL A005. These documents shall include: (1) the form, fit, and function specifications, (2) functional description of the Line-Replaceable Unit, (3) detailed functional description of each Shop Replaceable Unit, and (4) software interface signals/control documents and the software protocols that will be used.

Trade-offs The Contractor should make maximum utilization of off-the-shelf equipment and technology when designing the TmNS components. The components should be flexible enough to satisfy the requirements of different users. The Contractor shall evaluate the equipment size, giving special attention to the tradeoffs in time, cost, reliability, maintainability, and flexibility.

Input/Output Electrical Connectors The Contractor shall select the electrical connectors, and a summary of the selection criteria used in making the selection shall be submitted to the Government for review and approval at the first Design Review. The Contractor shall select connectors that are commercially available from multiple sources. The Contractor shall use, whenever practical, the same pin numbers on different components for similar functions.

TEST AND EVALUATION

TmNS Component Testing Technical Requirements The Contractor shall test and support integration of the tasked prototypes and reference applications in accordance with the specifications and this statement of work. The Contractor shall provide all labor hours, materials, and any other required resources, unless specified otherwise in other sections of this SOW.

Test Program The Test Program shall involve two general test categories: 1) tests that are performed one-time to demonstrate that all functional and performance requirements have been incorporated into the TmNS component design, and 2) acceptance tests that are performed on each end item delivered to the Government to demonstrate that the TmNS component satisfies performance requirements.

Testability The Contractor shall design testability into the tasked TmNS components. This testability shall be an integral part of the development, beginning with the first phases of design. Design Reviews shall include testability aspects of the component. Consideration should be given to the different aspects of the component life cycle such as testing, fault isolation, maintenance, data collection, and analysis, as well as testability versus costs.

Non-Compliance Testing In conducting testing on the TmNS components, where the Contractor fails to meet the requirements identified in the specifications, the Contractor may be required to perform additional testing to determine the level of non-compliance. These non-compliance(s), along with the level of non-compliance, shall be submitted to Government for approval.

Test Plans/Procedures All formal test plans/procedures require approval of the Government prior to performing tests.

System Integration Testing The Contractor shall support system integration testing, which will be conducted by the Government at the Air Force Flight Test Center, Edwards Air Force Base, California and the Naval Air Warfare Center Aircraft Division, Patuxent River, Maryland. The Government will provide integration test plans for reference prior to system integration and testing. The Contractor shall provide support in the installation and integration of the TmNS components at the Government facilities and provide technical assistance and material to the Government through final System Integration and Test.

Flight Qualification Test The Contractor shall support Flight Qualification Tests, which will be conducted by the Government at the Air Force Flight Test Center, Edwards Air Force Base, California and the Naval Air Warfare Center Aircraft Division, Patuxent River, Maryland. The TmNS components will be installed by the Government and the TA components will be operating in up to four test-bed aircraft. The Contractor shall provide support in the installation and integration of the TmNS components at the Government facilities and provide technical assistance and material to the Government through final flight test.

Advance Prototype Testing The Contractor shall prepare test procedures for the following tests: Environmental Qualification Test(s), Electromagnetic Compatibility Test(s), and Component Acceptance Test(s). Component Acceptance Test(s), Electromagnetic Compatibility Test(s), and Environmental Qualification Test(s) will be held at the Contractor’s proposed and Government approved facility.

Qualification Testing Environmental Qualification Testing The Environmental Qualification tests for advance prototypes are one-time tests to demonstrate that the prototypes will operate in accordance with performance requirements when exposed to the various environments specified in the TmNS System Specification. The Contractor shall develop and deliver Environmental Qualification Test Procedure(s) in accordance with CDRL A007 and the Environmental Qualification Test Report(s) in accordance with CDRL A008.

Electromagnetic Compatibility Testing The Electromagnetic Compatibility tests for advanced prototype are one-time tests to demonstrate that the prototypes will operate in accordance with performance requirements when exposed to the various electromagnetic environments specified in the TmNS System Specification. The Contractor shall develop and deliver Electromagnetic Compatibility Test Procedure(s) in accordance with CDRL A009 and the Electromagnetic Compatibility Test Report(s) in accordance with CDRL A010.

Component Acceptance Test The Component Acceptance Test shall be conducted at the Contractor’s facility on all deliverable components and may be observed by Government Representatives. The Contractor shall develop and deliver Component Acceptance Test Procedures in accordance with CDRL A011 and Component Acceptance Test Reports in accordance with CDRL A012.

Acceptance/Demonstration Testing The Contractor shall conduct integration and acceptance/demonstration testing at various locations.

Contract Option Low Rate Initial Production The Contractor shall provide the means for the Government to procure Low Rate Initial Production TmNS components. It is anticipated that the Contractor shall utilize component test plans and manufacture test tools developed under this SOW.

Documentation Updates Based on the results of the testing and evaluation activities, the Contractor shall update the technical documents developed under this SOW. Therefore, the Contractor shall submit revisions to CDRL’s A004, A005, and A011.

Additional Support It is anticipated that, after initial integrations and flight tests, additional efforts will be required to support range integration for Initial Operational Capabilities at multiple ranges. This additional support would likely include telephonic technical support, travel, training, additional development, and supporting materials.

DATA

Contract Data Requirements List The Contractor shall provide all personnel and resources necessary to produce and deliver the Data Items identified in the Contract Data Requirements List (CDRL). Contractor’s format and content for these deliverables must be submitted to the Government prior to development of the data items for approval.

1.1.1 Data Items