: Added: Jun 25, 2014 1:46 pm
Notice Type: Special NoticeClassification Code: A
4.0 TECHNICAL BACKGROUND:
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
- 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
- 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
- Complies with Defense Information Systems Agency, Standards Management Branch (DISA/GE332)
- Complies with Multi-TDL Data Extraction and Reduction Guide, current version
- Ability to import and incorporate ACOs and display selected overlays
- Compatible with the most current, and all previous USMTF versions
- Ability to import and correlate data to an ATO
- 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.
- Preference settings option for operators
- Customizable Maps/Features/Boundaries with option to depict C2
AORs/SADL GWs AORs/Orbits, etc. in relation to terrain maps - 3D feature terrain aspect ratio/ digital terrain elevation data (DTED level 2)
- Single click and drag bearing and range/LOS calculation from platform to platform
- Option to set primary participant or point on which to calculate ranges/LOS calculations
- Color selectable displays for track data (category ID, RR, IU, etc.)
- Operator tailorable data block display
5.2 SPECIAL CONSIDERATIONS
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.
5.3 SUBMISSION
RFI abstract due date is July 9, 2014.
6.0 AGENCY CONTACTS
Primary TPOC - Gregory Hadynski Telephone: 315-330-4094 Email: gregory.hadynski@us.af.mil
Secondary TPOC- Rob Riley Telephone: 315-330-4326 Email: robert.riley.12@us.af.mil
References
- U.S. Air Force Selects Northrop Grumman Team to Provide Tactical Datalink Network Management System (NYSE:NOC)
- CJCSI 6240_RESPONSIBILITIES FOR THE JOINT TACTICAL OPERATIONS INTERFACE TRAINING PROGRAM.pdf
- USAF Approves Northrop JICO Support System Production - Airforce Technology
- TACTICAL DATA LINK P LANNING AND OPERATIONS afi11-261.pdf
- Ultra Electronics Advanced Tactical Systems : Products : TacViewCloud
- JSS overview brief to JICRB #21
•US
Forces Command initiative to provide a link monitoring and situational
awareness tool for JICOs
•No
development, integration only
•Systems
(evolutionary build):
–Air Defense Systems Integrator (APC)
–iMTDS (MITRE)
–Joint Range Extension Gateway (Titan)
–LMS-16 [later upgraded to LMS-MT]
(Northrop Grumman)
–Communications equipment (JTIDS Class 2,
USQ-125, voice)
No comments:
Post a Comment