Accessibility Information

Users of assistive technologies such as screen readers should use the following link to activate Accessibility Mode before continuing: Learn more and Activate accessibility mode.

Request for Information (RFI) For Data Link Network Planning, Monitoring & Analysis, and Training - Desired Capabilities for Operators

Solicitation Number: RFI-RIK-14-02
Agency: Department of the Air Force
Office: Air Force Materiel Command
Location: AFRL/RIK - Rome
  • Print


There have been modifications to this notice. You are currently viewing the original synopsis. To view the most recent modification/amendment, click here
Special Notice
Added: Jun 25, 2014 1:46 pm
Notice Type: Special Notice

Classification Code: A

NAICS Code: 541/541712

RFI Number: RFI-RIK-14-02

1.0 TITLE:

Request for Information (RFI) For Data Link Network Planning, Monitoring & Analysis, and Training - Desired Capabilities for Operators

Please reference this title and the RFI Number on all documentation submitted.


Department of the Air Force, Air Force Materiel Command, AFRL - Rome Research Site, AFRL/Information Directorate, 26 Electronic Parkway, Rome, NY, 13441-4514


This publication constitutes a Request for Information (RFI) as defined in Federal Acquisition Regulation (FAR) 15.201(e), Exchanges with Industry before receipt of Proposals, Requests for Information". Respondents should note that no funding has been specifically reserved for this announcement. We are soliciting Requests for Information abstracts only. Do not submit a white paper or proposal at this time.


This announcement is not a request for proposals; therefore, responses to the RFI are not considered offers and cannot be accepted by the Government to form a binding contract.


Refer to section five (5) of this announcement for instructions on submitting an RFI abstract.


Submission of an abstract is voluntary. Respondents are advised that AFRL is under no obligation to provide feedback with respect to any information submitted under this RFI.


The Air Force has a requirement for a data link network planning, monitoring, and analysis capability. This RFI addresses the operational requirements to support the Joint Interface Control Officer (JICO), Regional Interface Control Officer and unit-level Data Link Manager's tactical data link planning, execution and management of the Joint Multi-Tactical Data Link Network.

Details within this RFI consolidates recommendations from Air Force (AF) data link managers on the required capabilities for today's fight, based on the current operational environment and advances in system software applications.

Basic Assumptions:
- It is not a requirement for the network monitoring & analysis capability to function as a gateway (translation and forwarding are not required)
- It is not a requirement for the network monitoring & analysis capability to incorporate a voice communication component
- The list of desired capabilities that follows does not imply that all capabilities need to be resident in a single system, application or computer. Moreover, the desired capabilities should be separated into three major mission components or applications that are wholly separate, but are interoperable (ref: MIL-STD 6016D Tactical Data Link (TDL) 16 Message Standard Section 3 paragraph 3.3):
- Allows for the separate development and fielding of the three major mission components, minimizing the probability that delays in the development one component will prevent fielding of other mission-ready components. The three major mission components are as stated below, by priority:

        Priority 1: Multi-TDL Network (MTN) Monitoring and Analysis
        Priority 2: MTN Planning & OPTASK LINK creation
        Priority 3: Training Component

- To the greatest extent possible, software solutions are desired over hardware solutions. The intent is to minimize the number of separate hardware systems, computers, etc. operators are required to use and that units are required to house/sustain.
- To the greatest extent possible, format and schema of input/output products should allow for exchanges of files and information between these three separate mission applications as well as with other planned core management systems for the Air Operations Center (AOC) and AF Enterprise.

Global System/Applications Requirements:
- Software-based to the greatest extent possible. Given minimum requirements for operating system, processor speed, etc., software application would be effective on any commercial-off-the-shelf computer.
- To the greatest extent possible, applications are operating system agnostic
- Utilizes (most current version of software systems) formats and schemas for input/output products allowing for exchanges of files and information between the MTN Monitoring and Analysis, MTN Planning & OPTASK LINK creation and Training components, as well as with other planned core management systems (i.e. TBMCS follow-on system) for the AOC/AF Enterprise
- Allows for exchange of data files via AF Enterprise email
- Modular, tailorable, scalable for use in an AOC, CRC or ground-based deployable unit. Units would utilize one or more of the major mission applications based on mission, need.
- Transportable system with minimal footprint (software only solutions preferable)
- Allows for remote management
- Interoperability (AFSIT/JITC) and IA (ATO/ATC) certified/tested for SIPR, coalition (ex: RELCAN) and NIPR networks
        o If software application only, application should be tested and certified via the USAF Approved Products List (APL) process to allow application to be loaded on any AF networked computer
        o If hardware solution is required, the hardware, operating system and relevant components must be in accordance with the National Information Assurance Partnership (NIAP) Validated Products List per DOD Directive 8500.1E.
- MIL-STD compliant with MIL-STD 3011B all appendices, MIL-STD 6004, MIL-STD 6011C, MIL-STD 6016D, MIL-STD 6040, MIL-STD 6017, and MIL-STD 6020B
        o Complies with Defense Information Systems Agency, Standards Management Branch (DISA/GE332)
        o Complies with Multi-TDL Data Extraction and Reduction Guide, current version
- Ability to import and incorporate ACOs and display selected overlays
        o Compatible with the most current, and all previous USMTF versions
- Ability to import and correlate data to an ATO
        o Compatible with the most current, and all pervious USMTF versions
- Applications password, profile protected by position titles with administrator privileges for ICO, and tailorable permissions for other assigned user positions with a read only default
- Intuitive, operator-friendly and user-defineable operational picture (UDOP) interface with toolbars, pull-down menus and left/right click options for operator switch actions.
        o Preference settings option for operators
        o Customizable Maps/Features/Boundaries with option to depict C2 AORs/SADL GWs AORs/Orbits, etc. in relation to terrain maps
        o 3D feature terrain aspect ratio/ digital terrain elevation data (DTED level 2)
        o Single click and drag bearing and range/LOS calculation from platform to platform
        o Option to set primary participant or point on which to calculate ranges/LOS calculations
        o Color selectable displays for track data (category ID, RR, IU, etc.)
        o Operator tailorable data block display

MTN Monitoring and Analysis Component

MTN Monitoring and Analysis:
- Recording and Playback for both visual display and forensics-level data
        o Continuously records track data display and Data Extraction and Reduction Guide (dated 14 Feb 2011) (DERG) data from multi-TDL ops for dynamic playback and analysis
           Provides DERG capability for MIL-STD 3011 mission management messages
           Continuously extracts and records the multi-TDL picture in real time, while maintaining correct time stamping (Zulu, with full date-time-group) on permanent external storage media/network storage without over-writing
           Able to record a minimum of 36 hours of multi-TDL ops without over-writing
              • Intuitive means to manually or automatically backup/store recordings to external media and/or network storage
           Store recorded information onto a permanent external storage media/network storage while not interrupting or otherwise impacting real-time recording
           Able to capture, save and transmit via email, segments of playback recording utilizing a program compatible with AOC/AF Enterprise viewer capabilities (Ex: windows media file or MPEG type video file)
           Playback in normal speed, slow and fast mode(s), or to a user identified time, displaying file details and allowing annotation of the file by user
           Search feature- allows for search and highlight of specific track number/IU, fast-forwarding recording to specific date/time identified track is found
           Records, saves and displays DERG data into easily readable, searchable, sortable and downloadable spreadsheet format
              • Allows Boolean logic for filtering and searches of recorded data by message type (i.e. J2.2, etc.), IU, modes/codes, RR, ID, etc.
              • Allows operator to select which fields to view, as well as to manipulate column order and sort on a column
              • Allows for custom filtering/color coding of selected messages
              • Compares messages to MIL-STD, identifying discrepancies
              • Ability to display, save and export multiple log files based on search criteria
              • Able to save screenshots of DERG data which can be cut and pasted into slides or sent via email for analysis, reference

- Monitors Time Slot Duty Factor (TSDF)
    o Ensures proper equation/calculation of TSDF
    o Analyzes TSDF for each JU, based on actual transmission pulses versus assigned
    o Able to calculate total area TSDF for a geographic area defined by an operator 
    o Monitors TSDF through examination of network elements by time slot group 
    o Alert capability to show potential and actual TSDF violations
    o Able to record, save, print TSDF log file and transmit via email

- Track Data Monitoring and Analysis
    o Able to display, process and analyze MTN messages to include no less than 16,000 link tracks (threshold) and 20,000 (objective)
    o Directly monitors local RF NTR (Network Time Reference) and ETR (External Time Reference) based networks
    o Allows for accurate remote monitoring and analysis of NTR and ETR based networks from reach back location via TCPIP/JREAP C connectivity from terminal and/or connectivity to established gateway (i.e., does not require additional equipment or terminal on either end to interface)
    o Utilizes unit's existing JTIDS/MIDS terminals to extract data - no additional terminal required
    o Compatible with all variants of JTIDS/MIDS terminals as well as all available protocols (e.g. 1553, x.25, and IP protocols)
     o Able to remotely monitor and analyze data via TCPIP/JREAP C connectivity from multiple terminals/sites
    o "JICO Whiteboard" capability to visualize active/inactive participants and connectivity
           Automatically identify units within the MTN (RF and BLOS) and identify to operator those units actively participating, not participating or those units who have issues that require attention
           Ability to click on units and/or links to display properties derived from the link monitoring or OPTASK LINK roles/duties (IU, track block, role, etc.)
o Monitors OPTASK LINK compliance, alerting operator for non-compliance such as:
           Unassigned/incorrect IU
           Transmission outside of track block
o Monitors tracks, identifies anomalies, providing operator selectable (filterable) alerts to include:
           Loss of NTR
           Multiple NTR
           Loss of NCS
           Loss of Sat-J/JREAP A Controller
           Loss of ETR node -GPS synch
           Dual tracks
           Duplicate tracks, track numbers
           ID conflicts
           PPLI location shifts, jumps
           R2 battles or shifts
           Track jumps
           Track drops
              IU conflicts
              Data looping
              Loss of network controller
          IFF/SIF and identification conflicts
          IU transmitting outside of assigned track block
          Unassigned/unknown JU
          Unassigned/unknown track number
    o Searches and provides alerts for operator-specified MTN parameter trends
    o Displays relevant operational status information for:
         Link 16 (threshold)
  Synchronization and network time
• Network participation status
• Connectivity
• Timeslot utilization by NPG
• Data and/or track update rates by unit and for network
• Proper unit initialization
• Proper unit participation in the network
• PPLI position reports for anomalies
• Navigation qualities, time qualities, status indicators, equipment status
• Relative navigation
• Net time reference, net entry terminal and other network participation roles
• Control and voice nets selected
• Track capacity vice assigned slot capacities
• Interfaced terminals loop back and received message status
• NTR/ETR NTR status - with alert if lost or changed
• Message and bit error rates
• Round Trip Timing status - with operator selectable alert threshold
• Identifies active relay platforms
• Identifies active Time Slot Reallocation platforms
          SATCOM Link 16 (threshold)
• Satellite network cycle time - with operator selectable alert threshold
• Participation status
• Error rates
• Data received and transmitted
• Transmit sequence list
          Link 11 UHF/HF (objective)
• Net cycle time - with operator selectable alert threshold
• Participation status
• RF quality
• Reception qualities
• Side band usage by unit
• Proper unit participation and update rates in network
• Unit position reports for anomalies
• Status indicator and equipment status
• Presence of NCS/Loss of NCS
• Presence of GRU/Loss of GRU
- Interoperable with the MTN training component - allowing for monitoring and analysis training of real-world track data and injected anomalies as created by the MTN training component

(Objective) MTN Monitoring and Analysis capabilities - should not delay the delivery of a network monitoring and analysis tool

          Combat Net Radio/VMF K series message analysis
          SADL XY and SADL Z/EPLRs analysis
          JREAP A, B and C header messages analysis
          Link 22 analysis

(Objective) MTN Monitoring and Analysis capability - should not delay delivery of network monitoring and analysis tool:

- Beyond-Line-of-Sight (BLOS EHF SATCOM, IP Connectivity) Analysis and Management
o Monitors/Analyzes BLOS connectivity (to be leveraged against Navy efforts with Link Monitoring and Management Tools (LMMT) prototype and JWIN JTCD, if possible) - more information from, coordination with Navy Air and Missile Command and applicable ACC/A5/8/9 Divisions required to pursue common or complimentary capabilities.
          BLOS connectivity
          error rates
          data latency
          speed of service
          data delays
          data loss
          improved data routes
          OPTASK LINK compliance

(Objective) MTN Management capability - should not delay delivery of network monitoring and analysis tool:

Dynamic Network Management

- Future AF operational requirements may necessitate the ability for the JICO/JICO organization to dynamically plan/re-plan the MTA. In the case of Link 16 network management, the following will be required as capabilities mature:
    o Dynamic Network Management
          Password, user profile protected for ICO position, designees
          Read only default permissions for other users
    o Able to dynamically manage (send Link 16 management messages) to local RF networks as well as to remotely manage RF networks from a reach back location via JREAP C/TCPIP connectivity
    o Able to identify unassigned/unused timeslots
    o Able to assign unallocated time slots to a platform's participation group over the link via J0.x series messages
    o Able to transmit partial and complete time/relay slot assignments to platforms via the J0.x series messages to support dynamic entry and egress of platforms
    o Able to delete partial and complete time/relay slot assignments for platforms via J0.x series messages
    o Able to change operational network
    o Able to reassign network roles
    o Able to activate and deactivate relays
    o Able to add unassigned timeslots to a Network Participation Group (NPG)
    o Able to add/delete timeslots within a NPG
    o Able to add/delete timeslots between NPGs
    o Able to change platform initialization loads
    o Able to change message packing format
    o Able to change crypto variable logic label (CVLL) assignments
    o Able to modify platform crypto loads (i.e., over-the air rekeying)
    o Immediate error/alert message when intended action fails or is prohibited

Priority #2
MTN Planning Component

MTN - Plan Creation and Plan Analysis:
- Planning tool that assists JICO in designing a new, or modifying an existing MTA and runs a connectivity analysis
    o Password, user profile protected for creation and editing - JICO/designees
          Selectable permissions for others, with a read only default
    o Conducts analysis based on long-haul and point-to-point communications and standard RF propagation characteristics, considering local environmental factors such as weather and terrain masking for friendly order of battle capabilities to include:
          Link 11 HF/UHF
          Link 16 UHF
          SADL
          VMF/CNR waveforms
          Satellite connectivity for data and voice (UHF, SHF, EHF)
          Surveillance radar propagation
    o Conducts analysis for both NTR and ETR networks
    o Identifies where relays are required to ensure connectivity
    o Provides a moving, 3D visual depiction of connectivity analysis incorporating level 2 DTED for terrain depiction (i.e., displays connectivity of aircraft as it flies the length of its orbit/tasking)
    o Able to import an existing Link 16 Network .jjl file to run message, connectivity analysis
          Able to select, filter and add participants for analysis
          Able to modify unit/platform locations, altitudes etc. for analysis
    o Able to import OPTASK COMMs; compatible with all USMTF versions
    o Able to import ATO/ACO to support analysis
          Compatible with the most current and all previous USMTF versions
          Able to filter/select overlays for unit and orbit locations
    o Runs line of sight (LOS) connectivity analysis scenarios against simulated denied (jamming) environments
    o Able to create connectivity graphic from program analysis that can be cut and pasted into slides for downloading and distribution (ex: Power point, Google earth, etc.) via AF Enterprise email
    o Able to record, store, retrieve and distribute multiple MTA/MTN plans/analysis to distant users
    o Produces reports based on network connectivity analysis with sortable, filterable fields
          Includes track count lists
          Includes track lists
    o Products, reports and recordings must be in format interoperable (Ref: MIL-STD 6016D Section 3 paragraph 3.3) with other AOC/AF Enterprise systems allowing for import, export and emailing
    o Maintains updateable data base of current M series/ J series/K series implementations by platform
         Password protected for JICO/Designees
         updateable via download with an option for manual updates by authorized operators (ICO) in REMARKS section (objective)
         Identification of data base update source, with date stamp of input
         Compatible with eSMART databases
         Hyperlinks to service Capabilities and Limitations databases


- Provides ability for user to import, create, edit, validate and export an OPTASK LINK message in machine-parseable USMTF B.1.01.11 format (threshold)
    o Able to import and export existing OPTASK LINKs for editing, saving and redistribution on SIPRNET and/or coalition IP networks
    o Compatible with all versions of OPTASK LINK from 2006 baseline to current version
    o Compatible with Automated Message handling System (AMHS) to allow for distribution of OPTASK LINK
    o Ability to read OPTASK COMMS document and be able to use/adapt frequency and crypto authorizations for use in the OPTASK LINK
    o Ability to develop OPTASK LINK using an "expert" or "wizard" functionality in an Information Exchange Requirement (IER) style format
    o Ability to create a database of unit capabilities (which links they are capable of, terminal/radio types, Terminal Base Addresses (TBAs), IPs/ports, etc. and points of contact information) to be used to populate required OPTASK LINK fields
    o Provides examples of properly formatted fields and field parameters, for OPTASK LINK version used
    o Validates OPTASK LINK for properly completed/formatted fields, providing user alerts for errors
    o Alerts operator to conflicting or duplicate data: e.g. IUs, track blocks, IP assignments
    o Breaks out unit/platform data from an OPTASK LINK into a downloadable, editable, selectable view (ability to sort and filter as well as select which columns to view and in what order) spreadsheet by :
          Platform strength (numbers)
          Unit
          Platform type
          PU/RU/JU (both individual or in IU pools of multiple assignments)
          Call sign
          Variable Message Format (VMF)/Combat Net Radio (CNR) Unit Reference Number (URN)
          VMF/CNR IP Addresses
          VMF/CNR Data Link Addresses
          JU Block for network enabled weapons (NEW)
          Primary & Alternate controller for NEW
          Track Blocks, with calculations for octal track capacity
          Forwarding Track Blocks, with calculations for octal track capacity
          Load file, option and sequence
          Location/Orbit
          Links Duty
          Terminal Base Addresses
          Remarks section - updateable by operator
          Unpopulated fields are displayed, but left blank on spreadsheet
    o Spreadsheet must be in format interoperable (Ref: MIL-STD 6016D Section 3 paragraph 3.3) with other AOC/AF Enterprise systems allowing for import, export and emailing.

Interoperable with MTN Monitoring & Analysis component - OPTASK LINK created by Planning component can be imported by MTN Monitoring & Analysis component to allow for OPTASK LINK compliance monitoring and alerts

Priority #3
Training Component

- Overt, highly visible "SIM MODE" banner or background display to clearly distinguish between simulated and live operations
- Ability to simulate interface link capabilities and create anomalies found in real-world operation to aid in interface control troubleshooting
- Be engineered such that training data shall be protected against inadvertently transmitting any simulation generated track data onto any live MTN (threshold)
- Be compliant with Defense Modeling and Simulation Office (DMSO) high-level architecture requirements to enable applications to function in a distributed manner
    o Password/profile protected for ICO position
          Tailorable user permissions, preferences for other users
- Ability to conduct individual training for other data links such as SADL
- Records real-world track data to generate scenarios for test simulations, analysis and training, using playback when required
- Able to inject dynamic "on the fly" tracks/anomalies and other network issues even in playback mode with the ability to save newly created scenario(s).
- Able to import previously recorded live network operations for simulation mode/training with the ability to inject and manipulate data and use management tools to replicate real world management/actions/analysis
- Able to export recordings to distant users for use in analysis and data link management training
- Scenario generation mode provides all tools and objects for generating, displaying and storing scenarios for future use, to include adding dynamically generated tracks to previously recorded track data
- Ability to generate all of the anomalies the MTN Monitoring and Analysis component is programmed to detect, as well as simulate anomalies operators could expect to detect manually
- Directly interoperable with the MTN Monitoring and Analysis component - allowing for monitoring and analysis training of real-world track data and injected anomalies as created by the MTN training component.


ACC Air Combat Command
ACO Air Control Order
AF Air Force
AFRL Air Force Research Laboratory
AFSIT Air Force System Interoperability Test
AMHS Automated Message Handling System
AOC Air Operations Center
AOR Area of Responsibility
APL Approved Products List
ATC Authorization to Connect
ATO Air Tasking Order
ATO Authorization to Operate
BLOS Beyond Line of Sight
C2 Command and Control
CNR Combat Net Radio
COMM Communications
CRC Control and Reporting Center
CVLL Crypto Variable Logic Label
DERG Data Extraction and Reduction Guide
DMSO Defense Modeling and Simulation Office
DTED Digital Terrain Elevation Data
EHF Extremely High Frequency
EPLR Enhanced Position Location Reporting System
eSMART Enhanced Systems Management and Requirements
ETR External Time Reference
GPS Global Positioning System
GRU Gridlock Reference Unit
GW Gateways
HF High Frequency
ICO Interface Control Officer
ID Identification
IER Information Exchange Requirement
IFF Identification Friend or Foe
IU Interface Unit
JCTD Joint Capability Technology Demonstration
JICO Joint Interface Control Officer
JITC Joint Interoperability Test Command
JREAP Joint Range Extension Applications Protocol
JTIDS Joint Tactical Information Distribution System
JWIN Joint Warfighting Integrated NETOPS
LMMT Link Monitoring and Management Tool
LOS Line of Sight
MIDS Multi-functional Information Distribution System
MIL-STD Military Standard
MTA Message Transfer Agent
MTN Multi-TDL Network
NCS Network Control Station
NEW Network Enabled Weapon
NIAP National Information Assurance Partnership
NIPR Non-classified Internet Protocol Router Network
NPG Network Participation Group
NTR Network Time Reference
OPTASK LINK operational tasking data links
PPLI Precise participant location and Identification
PU Participating Units
RELCAN Releasable to Canada
RF Radio Frequency
RR Reporting Responsibility
RU Reporting Unit
SADL Situation Awareness Data Link
SATCOM Satellite Communications
Sat-J Satellite TDL J
SHF Super High Frequency
SIF Selective Identification Feature
SIPR Secret Internet Protocol Router Network
TBA Terminal Base Address
TBMCS Theater Battle Management Core Systems
TCP/IP Transmission Control Protocol/Internet Protocol
TDL Tactical Data Link
TSDF Time Slot Duty Factor
UDOP User Defined Operational Picture
UHF Ultra High Frequency
URN Unit Reference Number
USMTF United States Message Text Formatting
VMF Variable Message Format



All abstracts shall state that they are submitted in response to this announcement and identify the Priority Number to which the response is applicable.

RFI responses shall include the company name, address and the title, telephone number, mail and e-mail addresses of the point of contact having the authority and knowledge to discuss the RFI submission.

The Government is assessing the current state-of-the-art and existing tactical data link management product solutions. The RFI responses should describe the product solution proposed, address coverage of the requirements stated in this RFI by the proposed solution, explain the potential advantage to the Air Force, and provide a rough order of magnitude for the cost of the proposed solution. NO CLASSIFIED INFORMATION SHOULD BE INCLUDED IN THE RFI RESPONSE.


Multiple abstracts within the purview of this RFI announcement may be submitted by each responder.

Network complexity, large AORs, challenging terrain and capacity issues within the Link 16 networks require a tool that helps operators plan for the effective use of the Link 16 capabilities. Emerging capabilities such as network enabled weapons and the growing emphasis on integrated air and missile defense require tools to effectively manage and more effectively employ data link capabilities as greater burden is placed on the Link 16 networks. The ever-increasing challenge of TDL management requires a training tool to effectively train operators in garrison to manage TDLs and the data that flows across them.

Network Planning, Network Monitoring and Analysis, and Training, be pursued as separate but interoperable and complimentary components. While the components are designed or (in the case of an already existing system) modified, to compliment the other and be interoperable, delays in the development and fielding of one mission-ready component should not delay the delivery of another component ready for fielding.

All components should be interoperable with relevant current and future AF Enterprise systems such as the proposed AOC management system, email, spreadsheet, and media viewer software.

JICOs and Data Link operators require the planning component to effectively implement emerging capabilities such as network enabled weapons. Satisfying these operational requirements will result in more effective employment of data link resources and a reduction in manpower hours dedicated to data link troubleshooting.

Current data link management/interface control operational expertise and manpower will be employed to operate and maintain these mission applications.


RFI abstract due date is July 9, 2014.


The abstracts will be formatted as follows:

Section A: Title, Period of Performance, Estimated Cost, Name/Address of Company, Technical and Contracting Points of Contact (phone, fax, and email) In addition, respondents are requested to provide their Commercial and Government Entity (CAGE) number, their Dun & Bradstreet (D&B) Data Universal Numbering System (DUNS) number, a fax number, an e-mail address, and reference this RFI with their submission. (This section is Not included in the page count.)

Section B: Technical Summary: The technical abstracts shall be limited to 8 pages.

All abstracts shall be double spaced with a font no smaller than 12 point. All responses to this announcement must be addressed to the TPOCs, as discussed in Section 6.0 of this announcement. Respondents are required to submit at least one electronic copy to the Government technical point of contact (TPOC) in Microsoft Office Word. It is strongly suggested that you confirm receipt of your electronic submission with the Primary TPOC.


Verification of government receipt or questions of a technical nature can also be directed to the cognizant TPOC.

Primary TPOC                                                   Secondary TPOC
Gregory Hadynski                                            Rob Riley
Telephone: 315-330-4094                              Telephone: 315-330-4326
Email:                  Email:

Chief, Tactical Data Link Ops & Mgt TPOC      AOC WS Sustainment TPOC
Gregory A. Tschupp (ACC/A3CJ)                     Matthew Hester (ACC/A5CS)
Telephone: (757) 764-8328/9                       Telephone: (757) 225-2130
Email:               Email:

COP/JDN Requirements TPOC                      TDL Programs Branch TPOC
John Swartz (ACC/A5CR)                              Larry Watlington (ACC/A5JT)
Telephone: (757) 225- 4145                        Telephone: (757) 225-6173
Email:                    Email:

Questions of a contractual/business nature shall be directed to the cognizant Contracting Officer, as specified below:

Gail Marsh
Telephone: (315) 330-7518



26 Electronic Parkway
Rome, New York 13441-4514
United States
Gregory Hadynski,
Primary TPOC
Phone: 315-330-4094
Rob Riley,
Secondary TPOC
Phone: 315-330-4326