Atch 1 TDL Software Performance Work Statement (TDL Interoperability Software) v4.pdf

PERFORMANCE WORK STATEMENT (PWS)

For Tactical Datalink (TDL) Interoperability Software

1.0 BACKGROUND

Air Combat Command's (ACC) mission requires robust Tactical Datalink (TDL) interoperability to improve mission effectiveness for United States Air Force (USAF), Joint, and coalition forces.

To support this mission, the Government requires a modern software solution that serves as a relational database and analysis toolset. This toolset is essential for the iSMART (interoperable Systems Management and Requirements Transformation) process and is used to populate, edit, analyze, and manage TDL message data, platform implementations, and interoperability evaluations.

2.0 SCOPE

The Contractor shall provide a commercial off-the-shelf (COTS) software solution, including all necessary licenses, updates, training, and technical support. The software shall provide a comprehensive toolset for managing TDL platform specifications, conducting interoperability analysis, and supporting mission planning across the TDL enterprise.

3.0 REQUIREMENTS

The Contractor shall provide the following:

3.1 Software Capabilities

The provided software solution shall meet the following key performance parameters:

3.1.1 User Interface and Training:

The software shall feature an intuitive, modern graphical user interface (GUI) that minimizes the need for extensive training. The GUI shall be designed to allow an operator with basic TDL knowledge to achieve proficiency on core tasks in no more than three (3) standard working days.

The system's design must be intuitive enough to mitigate significant skill fade for infrequent users.

3.1.2 Automated Data Ingestion:

• 3.1.2.1 Standards: The software shall automatically ingest, parse, and structure data directly from published TDL standards, including but not limited to MIL-STD 6016, without requiring manual data re-entry or reformatting by the operator.

• 3.1.2.2 Platform Data: The software shall provide multiple pathways for ingesting platform implementation data, including manual entry via a unified display, automated import from pre-defined Microsoft Excel formats, and import from internal system templates. The system must include features like automatic "fill-down" to increase the speed and accuracy of manual data entry.

3.1.3 Data and Issue Management:

• 3.1.3.1 Management of TDL Differences: The software shall allow users to capture, document, and grade deviations from a standard TDL baseline directly within a platform's implementation record. This capability must allow operators to identify and prioritize interoperability issues and potential workarounds within a single system.

• 3.1.3.2 Platform Issue Tracking: The software shall provide a mechanism to record and maintain a history of platform-specific issues (e.g., design, testing, operational) through their entire lifecycle. This information must be linked to the platform specification to enable automatic updates to existing analyses.

• 3.1.3.3 Capabilities & Limitations Summary: The software shall be capable of generating a consolidated, high-level summary of a platform's TDL capabilities, including implemented TDLs, message baselines, equipment fits, and network capabilities (e.g., Link 22, JREAP).

3.1.4 Interoperability (IO) Evaluation:

The software shall provide a robust module to conduct detailed, multi-platform IO evaluations.

This capability must:

• Leverage existing platform specifications and issue records to rapidly generate IO analyses;

• Assess interoperability in a multi-link environment;

• Generate user-focused outputs in multiple formats (e.g., interactive HTML, "Kneepad" summaries);

• Provide a "System of Systems" scenario view.

3.1.5 Mission Thread Analysis:

The software shall enable the user to analyze and visualize IO evaluation results within the context of specific operational mission threads. This must include the ability to create mission roles, allocate platforms to those roles, and assess how different platforms fulfill mission-specific Information Exchange Requirements (IERs).

3.1.6 Data Export and Reporting:

The software shall be capable of exporting data in open, non-proprietary, and machine-readable formats, including at a minimum XML, HTML, and Microsoft Excel (CSV and XLSX). Export functions must be intuitive and allow for the easy dissemination of platform specifications, templates, and analysis results.

3.2 Data Migration Support

To ensure continuity of operations, the software must support the streamlined migration of existing TDL implementation data. The system shall be capable of migrating an entire database of platform specifications in a single action and provide a pre-migration report detailing differences and potential impacts. The solution must support data import from pre-defined Microsoft Excel formats to facilitate the transition from legacy systems.

3.1.6 Data Export and Reporting:

The software shall be capable of exporting data in open, non-proprietary, and machine-readable formats, including at a minimum XML, HTML, and Microsoft Excel (CSV and XLSX). Export functions must be intuitive and allow for the easy dissemination of platform specifications, templates, and analysis results.

3.2 Data Migration Support

To ensure continuity of operations, the software must support the streamlined migration of existing TDL implementation data. The system shall be capable of migrating an entire database of platform specifications in a single action and provide a pre-migration report detailing differences and potential impacts. The solution must support data import from pre-defined Microsoft Excel formats to facilitate the transition from legacy systems.

3.3 Training Requirements

The Contractor shall provide the following software training sessions and materials annually:

3.3.1 Advanced Practitioner Training

The Contractor shall provide one (1) advanced practitioner training course per year for up to ten

(10) students. This course shall be delivered in-person within the continental United States over four (4) consecutive business days. The training must cover advanced software functionalities, including but not limited to: development and exploitation of platform data, conducting detailed Interoperability Evaluations, scenario development, and Mission Thread analysis.

3.3.2 Platform User Training

The Contractor shall provide one (1) foundational platform user training course per year for up to ten (10) interactive students (with unlimited "listen-only" participants). This course shall be delivered online in a virtual environment and shall not exceed five (5) total hours of instruction, delivered over a minimum of two (2) sessions, with a follow-up one (1) hour Q&A session. The training must cover core software functionalities, including but not limited to: developing platform Implementation Plans, documenting Platform Issues, and using basic comparison tools.

3.3.3 Training and Support Materials

The Contractor shall provide the Government with enduring, post-training reference materials to support operator proficiency and continuous learning. These materials shall be delivered digitally and must include, at a minimum:

• PDF copies of all training presentation slides and workshop materials.

• A comprehensive software User Manual.

• Training databases and associated configuration files.

• Quick-start guides and accompanying video tutorials stepping through the end-to-end interoperability analysis process.

4.0 DELIVERABLES

4.1 The Contractor shall provide 120 individual user licenses for the software toolset.

4.2 The Contractor shall provide all software updates, including patches for critical errors and bi-annual releases of the latest version of the toolset.

4.3 The Contractor shall provide all training sessions and enduring training support materials in accordance with the specifications, schedules, and student capacities detailed in Paragraph 3.3 (including Sub-paragraphs 3.3.1, 3.3.2, and 3.3.3) of this Performance Work Statement.

5.0 PERIOD OF PERFORMANCE

Base Year + Four (4) Option Years