Platform Mission Equipment Software Branch System Descriptions_18 May 2020.docx
DOCX document 55 KB Posted
- Attached to
- Sources Sought Platform Mission Equipment Software Branch Federal contract opportunity
- Solicitation number
- W56JWSR18D0004
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| DRAFT_Base_IDIQ_PWS_Platform_Mission_Equipment_Software_Branch.docx | DOCX document | |
| DRAFT_Task_Order_PWS_Platform_Mission_Equipment_Software_Branch.docx | DOCX document |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Platform Mission Equipment Software Branch CURRENT SYSTEMS DESCRITION
A2C2S RCM
1. System Name: Army Airborne Command and Control System (A2C2S) Radio Control Manager (RCM).
2. System Manager: CECOM LCMC LRC
3. System Proponent: CECOM LCMC LRC, Airborne Battle Command Program Support Office (ABC PSO)
4. System Deployed: 1st, 2nd, 4th, and 25th Infantry Division (ID); 1st Cavalry (CAV) Division (DIV), 36th Combat Aviation Brigade (CAB), 10th Mountain (MTN) DIV; C Company, 3rd Battalion, 1st Aviation Regiment (C/3-1 AVN).
5. System Overview: A2C2S Radio Control Manager (RCM) provides the services that allow an A2C2S operator to configure the different radios used by the A2C2S. RCM provides the operator the ability to create, edit existing, store, retrieve, and delete multiple radio configurations in non-volatile memory. These configurations can also be archived and retrieved from removable media. Once a configuration has been selected for implementation, that data will be sent to the applicable radio. RCM controls the ARC-231 radios via the Enhanced Micro Central Switching Unit (eMCSU) or MIL-STD-1553.
6. System Interoperates With: SINCGARS, AN/ARC-231 Radio.
7. Other Systems Dependent On: UH-60L/M Blackhawk.
8. Software Application Description:
a. Language: C++.
b. Source Line of Code: Approximately 200K.
c. Operating System: MS Windows 7.
d. Software Version(s): 7.1
e. COTS:HelpMaker v7
f. GOTS: None
9. Software Development Tools/ Applications:
| Support Tools/Applications |
| Description |
| Visual Studio 2010 Professional. |
| Compiler, linker for C++ Source code |
| Visual Source Safe 2005 |
| Configuration Management |
| HelpMaker v7 |
| Used to develop Help files |
10. Hardware: The following is a subset of hardware equipment list required to maintain, test and operate A2C2S RCM software. This is not an all-inclusive list.
| Test Hardware Resources |
| Description |
| Miltope V3 |
| PC used for MIL-STD-1553 testing |
| Panasonic CF-19 |
| PC used for TCP/IP RS-232 testing |
| ARC-231 Radios |
| RADIO used by software for test |
| Crew Access Unit (CAU) |
| Used for test |
| eMSCU |
| Required for TCP/IP RS-232 testing |
| CISCO router |
| Required for TCP/IP RS-232 testing |
| DELL Precision T7400 |
| PC used for A2C2S RCM development |
AHUD
1. System Name: AVIATION NIGHT VISION (ANVIS) HEADS-UP DISPLAY (AHUD)
2. System Manager: Program Manager Air Warrior (PM AW), under the direction of the Program Executive Office Soldier, CECOM LCMC LRC
3. System Proponent: USAACE
4. System Deployed: AHUD is operational on approximately 5,000 Regular Army Reserve, Army National Guard, Coast Guard, and Navy logistics workstations platforms in CONUS and OCONUS units.
5. System Overview: The AHUD AN/AVS-7 system is an advanced electro- optical system that combines the images seen thru the night vision goggles with computer generated graphics and digital symbols depicting essential flight data such as horizontal and vertical attitude, air data and weapon aiming. It deceases pilot workload by providing enhanced night vision capability; thus, greatly eliminating the need to refer to the cockpit instrumentation for required flight information. The AN/AVS-7 system permits the Army to perform night operations.
6. System Interoperates With: UH-60 A&L, CH-47D, MH-47D, MH-60A&L, CH-46E, UH-1N, UH-1H, CH-53E, MH-60K, MH-47E, AND HH-60H HELICOPTER PLATFORMS
7. Other Systems Dependent On: AN/AVS-6 NIGHT VISION GOGGLE SYSTEM
8. Software Application Description:
a. Language: C, Visual C++ .net, VB.net, Crystal Report, Pyroto script engine
b. Source Line of Code: Approximately 282,950 TLOC
c. Operating System: Windows XP SP3
d. Software Version(s): 3.1
e. COTS: VB.net, Visual C++ .net, Crystal Report 2005, pSOS, Pyroto/POMPT script engine
f. GOTS: None
9. Software Development Tools/ Applications:
| Support Tools/Applications |
| Description |
| Notepad++ 6.2 |
| Source/hex text editor |
| WinMerge 2.12.4.0 |
| Source code compare tool |
| Pico Scope v6 |
| Soft scope for measuring timings |
| Cam Studio 2.0 |
| Video capture for HUD testing |
| ToupView 3.7 |
| HUD pilot/co-pilot displays |
10. Hardware: The following is a subset of hardware equipment list required to maintain, test and operate AHUD software. This is not an all-inclusive list.
| Test Hardware Resources |
| Description |
| Dell Optiplex 755 |
| Development machine |
| Dell Latitude D630 |
| Test machine |
| HP NX9030 Laptop |
| Test machine |
| Micron PC |
| Test machine |
| Dell Latitude D620 |
| Test machine |
| Single board PC with 3rd party vendor PCI cards |
| ATADS unit with dual camera support |
Air Traffic Navigation Integration Coordination System/Fixed Base Precision Approach Radar (ATNAVICS/FBPAR) DESCRIPTION
1. System Name: Air Traffic Navigation Integration Coordination System/Fixed Base Precision Approach Radar (ATNAVICS/FBPAR)
2. System Manager: Program Manager, Air Traffic Control (PM ATC), under the direction of the Program Executive Office Aviation (PEO Aviation).
3. System Proponent: Program Manager, Air Traffic Control (PM ATC)
4. System Deployed: There are more than fifty-two (52) ATNAVICS systems and about 22 FBPAR systems within the U.S. Army. The U.S. Marine Corps (USMC) has procured six (6) ATNAVICS in the past five years. ATNAVICS has been fielded for the U.S. Army to replace the AN/TSQ-71B Landing Control Central to the deployed units on Army critical missions such as: 1-58th ATS Battalion (BN), Fort Bragg, NC; 1- 11th ATS BN, Fort Rucker, AL; F-Company 58th AVN and 3-58th AVN, Germany; 164th ATS Group, Korea; 1-245th ATS BN, Oklahoma; 204th ATS Group, Louisiana; and G-Company 58th AVN, Oahu, HI.
5. System Overview: The Air Traffic Navigation Integration Coordination System (ATNAVICS) is an Airport Surveillance Radar (ASR) and Precision Approach Radar (PAR) system that will provide Air Traffic Services at Army terminal airfields, landing sites or zones at Division, Corps and Echelons Above Corps (EAC). The operational system and communications equipment are installed in an S-788 shelter, which is mounted on a High Mobility Multipurpose Wheeled Vehicle (HMMWV). The ATNAVICS includes the operation shelter, the sensor equipment (ASR, PAR, Secondary Surveillance Radar/Identify Friend or Foe (SSR/IFF)), two multimode display units, generator, trailer, personnel gear for technicians, placement and setup equipment, cables and other ancillary equipment. The ATNAVICS configuration is transportable with roll-on/roll-off capability on a C-130 or larger aircraft and has also been designed to be transportable by CH-47 helicopter.
The Fixed Base Precision Approach Radar (FBPAR) is a dismounted variation based on ATNAVICS system designed for deployment of non-mobile locations such as domestic army air bases. It defers from ATNAVICS primarily in that the radar sensors are all in fixed locations.
6. System Interoperates With: ATNAVICS is compatible with the Forward Area Air Defense (FAAD), via a ground-to-ground radio providing information up to 100 nautical miles from the system.
7. Other Systems Dependent On: : All DOD aircraft
8. Software Application Description: (*Source Code is not maintained by SEC)
a. Language: C
b. Source Line of Code: Approximately 1.8 Million.
c. Operating System: Operating System: Sun Solaris, VX Works Real Time Operating System.
d. Software Version(s): ATNAVICS v4.x(Various versions fielded), FBPAR 1.x, 2.x and 3.x (Various versions fielded).
e. COTS: Auto Trac, ATNAVICS, INGRES.
f. GOTS: None.
9. Software Development Tools/ Applications:
| Support Tools/Applications |
| Description |
| Sun C Compiler |
| Compile all CSCIs |
| Wind River VX Works |
| Development and test environment for single board computers CSCIs |
| ICS builderXcessary |
| GUI builder |
| bitVise |
| PC-Sun connectivity |
10. Hardware: The following is a subset of hardware equipment list required to maintain, test and operate ATNAVICS/FBPAR software. This is not an all-inclusive list.
| Test Hardware Resources |
| Description |
| Rack Mounted Server |
| Sun Solaris to run ATNAVICS. |
| Tower Server |
| To run embedded radar simulations |
Lab cabling, switches, routers and power distribution To connect all LRUs
Lab SEE DESCRIPTION
1. System Name: Mission Equipment Support (MES) Lab Software Engineering Environment (SEE)
2. System Manager: CECOM SEC/IEW&S/A&TS-MES/Mission Equipment Support
3. System Proponent: CECOM SEC/IEW&S
4. System Deployed: N/A
5. System Overview: The MES SEE is the laboratory space provided for support activities to accomplish the mission of all systems under MES management. In order to maintain the SEE, support is needed to maintain the MEB Server and network infrastructure (switches, routers, firewalls, VLAN, cabling, etc. as required for connectivity).
6. System Interoperates With: All Systems under MES management.
7. Other Systems Dependent On: N/A
8. Software Application Description: N/A
9. Software Development Tools/ Applications:
| Support Tools/Applications |
| Description |
| Windows Server 2012 |
| Operating system for MEB Server |
| RHEL 6 |
| Operating system for MEB Server |
| Active Directory |
| Tools utilized to manage MEB systems |
| McAfee Antivirus |
| Tools utilized to manage MEB systems |
| Group Policy |
| Tools utilized to manage MEB systems |
| ACAS |
| Tools utilized to manage MEB systems |
10. Hardware: The following is a subset of hardware equipment list required to maintain, test and operate the MEB Lab. This is not an all-inclusive list.
| Test Hardware Resources |
| Description |
| Rack Mounted Servers |
| Dell Servers |
| Lab cabling, switches, routers and power distribution |
| Lab environment consisting of 100+ computer workstations |
MUXTOOLKIT DESCRIPTION
1. System Name: MULTIPLEX TOOL KIT (MUXTOOLKIT).
2. System Manager: CECOM LCMC SEC
3. System Proponent: ARNG, 160th Special Operations Aviation Regiment (SOAR), Project Manager Apache Attack Helicopter (PM AAH), PM Aviation Mission Equipment (PM AME, CECOM LCMC LRC, Army Fleet Support (AFS), Naval Air Systems Command, Patuxent River (NAVAIR PAX River)
4. System Deployed: Aviation Units; Aviation Classification Repair Activity Depots (AVCRADs) 1106th, 1107th, 1108th and 1109th; TF AVCRAD (CENTCOM); 160th SOAR; CECOM LCMC LRC Avionics Logistics Assistance Representatives (LARs); and New Equipment Training Teams (NETTs).
5. System Overview: The MUXTOOLKIT includes a family of MIL-STD-1553 test and integration software tools, related training and technical services to provide support for engineering and repair activities associated with avionics platforms, systems, subsystems, and data bus networks. Applications are designed to assist Army avionics maintainers in determining the operational status of MIL-STD-1553 avionics including navigation, communication, weapons, flight control, and Aircraft Survivability Equipment (ASE). MUXTOOLKIT software tools are compatible with the Army issued Maintenance Support Device (MSD), commercial PC or laptop computer systems and run under the Microsoft Windows operating systems currently used in the field. The MUXTOOLKIT maintenance software product lines provide diagnostic assistance across Army aviation platforms to support maintenance activities for multiple implementations of MIL-STD-1553 avionics data bus networks.
Tools and services include:
a) The Army Multiplex Avionics Tester (AMAT): AMAT is a software and hardware tool that provides an intermediate and depot level test capability for MIL-STD-1553 avionics subsystems and/or remote terminals. AMAT is mainly used at the Aviation Intermediate Maintenance (AVIM) level to assist in testing Line Replaceable Units (LRUs). AMAT is developed with product line engineering practices under the product line architecture which allows quick time to market for the LRU tests which are developed. It is used for software lifecycle testing, and engineering development validation and verification testing. AMAT uses SEC developed electrical interface component called Automated Break-Out-Box (ABOB) that provides input voltage stimulus to the LRUs under test.
b) The Advanced Multiplex Test System (AMTS): AMTS software product line provides comprehensive test tools at the Aviation Unit Maintenance (AVUM) and depot levels for MIL-STD-1553 avionics platforms, systems, subsystems and/or remote terminals. AMTS assists maintainers to determine the operational status of avionics network components and line replaceable units (LRUs) including navigation, communications, weapons, flight control, and Aircraft Survivability Equipment (ASE). AMTS is designed to provide support for current and future Army aviation and ground platforms that utilize a
MIL-STD-1553 avionics data bus (e. g. A-Model Apache, Longbow Apache, Black Hawk, Kiowa Warrior, Abrams, Bradley, etc.).
c) The Common Interface Driver (CID): CID is a standard Application Programming Interface (API) that provides access to multiple vendor MIL-STD-1553 Personal Computer Memory Card International Association (PCMCIA) / Peripheral Component Interconnect (PCI) devices. CID enhances device support and mitigates hardware costs by minimizing the effort required to integrate new devices while allowing integration of currently fielded devices. CID is currently utilized by AMTS and SLV, and will be integrated with AMAT.
d) The Validation and Test Facility (VALFAC): VALFAC is an onsite test laboratory that is used to provide Validation and Verification test services for MIL-STD-1553 systems and subsystems. VALFAC supports validation testing for avionics software, hardware development and engineering changes. VALFAC utilizes Government off-the-shelf (GOTS) and commercial off-the-shelf (COTS) software and hardware test systems to provide services and is routinely upgraded.
e) The Platform Network Simulation Environment (PNSE): PNSE is a set of integrated equipment, software, and hardware that provides the capability to simulate MIL-STD-1553 Avionics data bus network systems and subsystems in a controlled environment. The PNSE allows engineers to simulate multiple avionics network system configurations in the lab, including systems used on fielded DoD weapon platforms (i.e., AH-64D, CH-47F, UH-60M, M1-A2, etc.), so as to increase availability of relevant environments and enhance software testing, engineering, and field technical support activities.
6. System Interoperates With: EGI, SINCGARS ,HAVE QUICK II, AN/ARC-186 , AN/AYD-1(V) PERSONNEL LOCATOR SYSTEM, AN/ARC-210, AN/APX-100, AN/ARC-164, AN/ARC-231, AN/ARN-147, AN/ARN-149.
7. Other Systems Dependent On: AH-64A MODEL APACHE, AH-64D LONGBOW APACHE, OH-58D KIOWA WARRIOR, HH-60L/MH-60K/MH- 60L BLACK HAWK , MH-47D/MH-47E CHINOOK, M1A2 ABRAMS, M2A3 BRADLEY.
8. Software Application Description:
a. Language: MS Visual C++ 6.0, MS Visual Basic 6.0, VB .NET, C# , Lab View
b. Source Line of Code: Approximately 300,000.
c. Operating System: Microsoft Windows 95/XP/Vista/7
d. Software Version(s): AMAT 8.2, AMTS 3.3, AMTS 3.4, AMTS 4.0, CID 3.0
e. COTS: Crescent Software 4.53, DDC MIL-STD-1553 card driver, Andor MIL-STD-1553 PCMCIA card driver, Excalibur MIL-STD- 1553 PCMCIA card driver
f. GOTS: None.
9. Software Development Tools/ Applications:
| Support Tools/Applications |
| Description |
| Visual Studio Source Safe 2005 |
| Used for configuration management purposes. |
| Visual Studio 6 |
| Application design environment |
| Visual Studio .Net 2008 |
| Application design environment for AMTS 4.0 |
| Setup Factory 8 |
| Create installation programs for users |
| Crescent Software 4.53 |
| Used to add custom controls and functions to the application. |
| Project Analyzer |
| Analyze source code. |
| Roxio version 9 &10 |
| Write to CD/DVD. |
| Irfanview 4.2 |
| Create/Modify pictures and icons. |
| Beyond Compare 3 |
| Compare files/folders. |
| DDC data-Sims v.4.4.3 |
| 1553 Bus Controller Software |
| Lab View v2012 |
| Diagnostic Software |
| SBS Pass3200 |
| Software to monitor and record bus traffic. Also able to |
act as bus controller.
ILC DDC MIL-STD-1553 Section 100 RT Validation Test Plan 65518 VTP Automated test software to run tests from MIL-HDBK- 1553 Section 100
| DDC BusTrACEr |
| Software to monitor and record bus traffic. Also able to act as bus controller. |
| DDC 1553 Interface driver software |
| Used to communicate with the DDC 1553 devices |
| SBS 1553 software |
| Used to simulate 1553 communication for testing |
10. Hardware: The following is a subset of hardware equipment list required to maintain, test and operate MUXTOOLKIT software. This is not an all- inclusive list.
| Test Hardware Resources |
| Description |
| Dell Optiplex 745, 755 |
| Dell desktops configured for development and test. |
| Dell Latitude D610, D620 & D630 |
| Dell laptop configured for test purposes. |
| Panasonic Toughbook CF-19, CF- 30, CF-31 |
| Panasonic laptop configured for test purposes. |
Miltope MSD-B, MSD-V2-B, MSD- V3-B Miltope laptop configured for test purposes.
| Andor PC-401 PCMCIA card Andor PC-301 PCI card |
| Provides the MIL-STD-1553 interface between the computer and UUT. |
| DDC PCMCIA 1553 card |
| Provide the MIL-STD-1553 interface between the |
AMTS computer and simulation computer
| DDC 1553 USB device |
| Provide the MIL-STD-1553 interface between the AMTS computer and simulation computer |
| DDC 1553 express card |
| Provide the MIL-STD-1553 interface between the AMTS computer and simulation computer |
| SBS PCMCIA 1553 card |
| Provide the MIL-STD-1553 interface between the |
AMTS computer and simulation computer
| Loral Instruments SBA-100F |
| Used to monitor the MIL-STD-1553 signals to and from the computer and Unit Under Test (UUT) |
Tenma Corp Dual Power Supply model 72-6854 Used to power the UBOB/ABOB/UUT
| Hewlett-Packard DC Power Supply model 6269B |
| Used to power the UBOB/ABOB/UUT |
Applied Dynamics Incorporated Automated Break-Out-Box (ABOB) Used to establish an automated connection, addressing, and power for the UUT.
| Hewlett-Packard Universal Frequency Counter model 5328A |
| Used to obtain the transmitted frequency from the UUT. |
| SEC Avionics Branch Model Type 1 or 2 Universal Break Out Box (UBOB), model AAT328103 |
| Used to establish a manual connection, addressing, and power for the unit under test. |
Tektronix Mixed Signal Oscilloscope model MSO-4045 Used to view and trace the signal from the UUT.
| DURO PCs, PN:RAC341 |
| PC holds DDC dataSims, Lab View software |
| Curtiss-Wright 1553 Multiplex Bus Switches, PN:DHAS-MBS1616 |
| 1553 Multiplex Bus Switches |
| Black Jack Test PN: BTI-150 |
| Power Supply |
| Loral Serial Bus Analyzer 100V 50471 |
| Bus Analyzer |
| ILC DDC 1553 Noise Tester BUS- 68015 |
| Produces noise according to specific requirements necessary to run Noise Rejection Test, Section 5.3 of SAE AS4111 RT Validation Test Plan |
Tektronix Digital Mixed Signal Oscilloscope MSO 4054 Oscilloscope
| Fluke True RMS Voltmeter 8921A |
| True RMS Voltmeter |
| HP Triple Output 450 Watt DC Power Supply 3630A |
| Power Supply |
| HP Impedance Analyzer 4192A LF |
| Impedance Analyzer |
| HP Arbitrary Waveform Generator 33120A |
| Waveform Generator |
SLV
1. System Name: Software Loader Verifier (SLV).
2. System Manager: CECOM LCMC SEC
3. System Proponent: PM Aviation Mission Equipment (AME), CECOM LCMC LRC
4. System Deployed: CECOM LCMC LARs, AVCRADs (1106th, 1107th, 1108th and 1109th), 160th SOAR, Aviation units from 101st Air Assault, 1st Cavalry Division, 82nd ABN DIV, 10th MTN DIV, and the 3rd, 4th, and 25th Infantry Divisions (ID)
5. System Overview: The SLV is a user-friendly software tool utilizing a Graphical User Interface (GUI) and menu-driven selections. It is a software tool which allows the rapid and effective uploading of Operational Flight Programs (OFP) onto Line Replaceable Units (LRU) in the field and other facilities. The SLV program architecture is designed in a product line approach allowing simple addition of other LRUs as needed. By adopting a product line approach it allows for more rapid and timely modification of software to meet changing threats, doctrine and technology. SLV operates on portable personal computers and is deployed to aviation and tank maintenance units, depots, and software support facilities. The SLV program and the Operational Flight Program (OFP) to be uploaded are stored and distributed on CD-ROMs.
6. System Interoperates With: IDM, EGI, EGI+, AN/ARC-220, AN/ASN- 128B/D SCD/CDU/DB, AN/APX-118 CXP RT, AN/APX-123 CXP RT, AN/ARC-231
7. Other Systems Dependent On: AH-64A/D, OH-58D, SOA Aircraft, UH- 60, CH-47, M1A2 ABRAMS, and M2A3 Bradley
8. Software Application Description:
a. Language: C#
b. Source Line of Code: Approximately 250,000.
c. Operating System: MS Windows XP/Vista/7
d. Software Version(s): SLV Framework v7.0.1, SLV Framework v6.2, SLV Library v1.8, v2.5, APX-123 MKIT v1.2, APX-123 v1.3, ARC- 220 v1.0, ARC-231 v1.2, ASN-128 BOB v2.1, ASN-128 v2.1, EGI ICA v1.2, EGI v2.2, EGI+ ICA v1.1, EGI+ v1.2
e. COTS: None
f. GOTS: MUXTOOLKIT CID
9. Software Development Tools/ Applications:
| Support Tools/Applications |
| Description |
| MS Project/Excel |
| Track Project Management Activities |
| MS Word |
| Software Documentation Tool |
| MS SourceSafe |
| Configuration Management and source-code repository |
| Setup Factory |
| For building install executables |
| MS Visual Studio |
| Software Development Tool |
10. Hardware: The following is a subset of hardware equipment list required to maintain, test and operate SLV software. This is not an all-inclusive list.
| Test Hardware Resources |
| Description |
| Panasonic Tough Book Laptop Miltope V1 Laptop |
| Laptops configured to reflect an entire SLV architecture. |
Dell Optiplex GX620 (1) Dell Optiplex 745 (2) Dell Optiplex 755 (4) Development & Test PCs that stores development resources such as software, VMware, Perforce, and JIRA.
EGI LRU EGI+ LRU ARC-231 LRU
APX-118/123 LRU
LRU devices that interface with the SLV application.
Blue Force Tracker - Aviation (BFT-A)
1. System Name: Air Traffic Navigation Integration Coordination System/Fixed Base Precision Approach Radar (ATNAVICS/FBPAR).
2. System Manager: Program Manager Aviation Mission Equipment (PM AME)-APM BFT-Aviation (BFT-AVN), under the direction of the Program Executive Office Aviation (PEO Aviation) for the MT2001 Transceiver and support equipment. PM Air Warrior (PM AW) for the EDM, CECOM LCMC LRC/PM Mission Command (PM MC) for the Field Service Station Software (FSS tool used by FSRs), Foreign Military Sale (FMS).
3. System Proponent: Program Manager, PM AME and PM AW.
4. System Deployed: All Combat Aviation Brigades (CAB), All Theater Aviation Support Mantaince Groups (TASMG), Corpus Christi Army Depot, TX NTC – Fort Irwin, CA , JRTC – Fort Polk, LA, 21st CAV BDE/166 AVN BDE, Ft Hood TX, Task Force (TF) 160 AVN, Theatre Aviation Operations Groups (TAOG).
5. System Overview: The BFT-AVN System is an automated, digitized computer network, with a seamless battle command capability. The BFT- AVN AN/UYK-128(V) Computer, along with associated communication and Global Positioning System (GPS) equipment, display blue and red icons that represent friendly forces, enemy combatants, and landscape hazards so units can synchronize operations and avoid fratricide. Additionally, it inter-operates with Army and Joint Command and Control (C2) and other sensor systems resulting in the vertical and horizontal information integration of the battlefield.
6. System Interoperates With: DAGR AN/PSN-13, PLGR AN/PSN-11, MT- 2011 TRANSCEIVER.
7. Other Systems Dependent On: : BFT-Ground/BFT-Ground Tactical Operation Center (TOC). IDM, AH-64A/D, OH-58D, UH-60 A/L, CH-47 D/F, UH-60M, UH-72, AASC, USMC CH-46E, USMC CH-53D/E, C-27J, USMC MV-22, USN HH-60H, USAF JSTARS, USAF C130-E, USN HH-60H, USMC C130-J, USAF MQ-1/9, USN LHD-6
8. Software Application Description: (*Source Code is not maintained by SEC)
a. Language: C
b. Source Line of Code: COTS Not Available.
c. Operating System: FSS tool Windows 7, EDM Windows XP, MT2011 embedded firmware.
d. Software Version(s): EDM Spiral version 2.5, FSS tool.
e. COTS: Raytheon’s Interactive Situational Awareness Software (ISAS), US Air Force’s Falconview, COMTECs MT2011 firmware & PM MC FSS tool.
f. GOTS: PM AW/Government does have data rights to ISAS/Falconview.
9. Software Development Tools/ Applications:
| Support Tools/Applications |
| Description |
| Windows XP/7 & LinuxC Compilers |
| Compile all CSCIs |
| Win XP/Win7/Linux |
| Development and test environment for single board computers CSCIs |
10. Hardware: The following is a subset of hardware equipment list required to maintain, test and operate BFT-A software. This is not an all-inclusive list.
| Test Hardware Resources |
| Description |
| Development computers |
| To update EDM software with IAVAs and create image. |
| Test computers |
| To run testing program |
| Lab cabling, switches, routers and power distribution |
| To connect all LRUs |
ENFIRE
1. System Name: INSTRUMENT SET, RECONNAISSANCE AND SURVEYING (ENFIRE).
2. System Manager: CECOM LCMC SEC
3. System Proponent: Program Manager (PM) Terrestrial Sensors, Product Director (PD) Combat Terrain Information Systems, Assured Mobility, Construction Task Manager (TM) (Maneuver Support Center of Excellence) , Program Executive Office Intelligence Electronic Warfare and Sensors (PEO IEW&S).
4. System Deployed: Brigade Combat Teams (BCT), Separate Brigades, Engineering Units At Various Echelons, US Army Training Sites, Marine Corps.
5. System Overview: The Instrument Set, Reconnaissance and Surveying (common name: ENFIRE) is a digital tool kit that replaces the Surveying and Sketching Set that has been used by Army Engineers for the past five decades. ENFIRE is used by units at the battalion, company, platoon, and squad levels as a means to facilitate rapid collection, absorption, and dissemination of reconnaissance information. ENFIRE incorporates the ability to automatically populate field data on forms used for route, road, bridge, ford, river, tunnel, and obstacle reconnaissance with relevant information from devices included in the ENFIRE set. Information collected using ENFIRE is transferable to other ENFIRE sets and other systems used at Battalion military levels and above.
6. System Interoperates With: N/A
7. Other Systems Dependent On: N/A
8. Software Application Description:
a. Language: Java, C#
b. Source Line of Code: Information Not Available
c. Operating System: Microsoft Windows 7
d. Software Version(s): ENFIRE v6.0
e. COTS: N/A
f. GOTS: ArcGIS Military Overlay Editor (MOLE).
9. Software Development Tools/ Applications:
| Support Tools/Applications |
| Description |
| Visual Studio Source Safe 2005 |
| Used for configuration management purposes. |
| Visual Studio 6 |
| Application design environment |
| Visual Studio .Net 2008 |
| Application design environment for AMTS 4.0 |
| Setup Factory 8 |
| Create installation programs for users |
| Project Analyzer |
| Analyze source code. |
| Roxio version 9 &10 |
| Write to CD/DVD. |
10. Hardware: The following is a subset of hardware equipment list required to maintain, test and operate ENFIRE software. This is not an all-inclusive list.
| Test Hardware Resources |
| Description |
| Dell Optiplex 745, 755 |
| Dell desktops configured for development and test. |
| Dell Latitude D610, D620 & D630 |
| Dell laptop configured for test purposes. |
Global Positioning Systems User Environment
1. System Name: Defense Advanced GPS Receiver (DAGR) and Ground- Based GPS Receiver Application Module (GB-GRAM).
2. System Manager: Program Manager, Position, Navigation and Timing (PM PNT), under the direction of the System of Systems Engineering & Integration (SoSE&I) Directorate.
3. System Proponent: Program Manager, Position, Navigation and Timing (PM PNT).
4. System Deployed: There are approximately 300,000 DAGRs systems worldwide. GB-GRAM is being installed in the (Defense Advanced GPS Receiver (DAGR)) Distributed Device (D3).
5. System Overview: The GPS/UE is a suite of equipment that receives and processes GPS satellite data to provide highly accurate position, velocity and timing information to the Warfighter. The GPS/UE consists of stand-alone devices (Defense Advanced GPS Receiver (DAGR)) and modules (Ground- Based GPS Receiver Application Module (GB-GRAM)) that can be fully integrated into DoD systems.
6. System Interoperates With: GPS-UE is Hand-Held device for the soldier but is compatible with the All DOD Systems that utilize the Defense Advanced GPS Receiver (DAGR) for the precision data and timing.
7. Other Systems Dependent On: All DOD Systems that utilize the Defense Advanced GPS Receiver (DAGR).
8. Software Application Description: (*Source Code is not maintained by SEC)
a. Language: (TBD)
b. Source Line of Code: (TBD).
c. Operating System: (TBD)
d. Software Version(s):
| AN/PSN-13 | 984-2461-016 (MWO Fielded version) |
| 987-2461-017 (Version loaded on Warranty Repair) AN/PSN-13A | 984-3006-008 |
| AN/PSN-13B | 811-4960-002 |
e. COTS:
f. GOTS: None.
9. Software Development Tools/ Applications:
| Support Tools/Applications |
| Description |
| GNSS Simulator (CP&I) |
| Simulate GPS data |
| PERL Script |
| Automating Test Procedures |
| Excel |
| Data Reduction |
| Maploader |
| For load Maps |
10. Hardware: The following is a subset of hardware equipment list required to maintain, test and operate GPS/UE software. This is not an all-inclusive list.
| Test Hardware Resources |
| Description |
Defense Advanced GPS Receiver
(DAGR)
2 DAGRs for IV&V testing.
| Laptop Server |
| XP to run CTS-153 tool |
| 2 Desktop PCs |
| One to run new version of CTS-153 |
One to run on the NIPR to download new baselines
| Lab cabling, switches, routers and power distribution |
| To connect all LRUs |
AN/ARC-220 High Frequency Radio (HF Radio)
1. System Name: AN/ARC-220 High Frequency Radio (HF Radio)
2. System Manager: Program Manager, Aviation Mission Equipment (PM AME), under the direction of the Program Executive Office Aviation (PEO Aviation)
3. System Proponent: Program Manager, Aviation Mission Equipment (PM AME)
4. System Deployed: There are 3,100 AN/ARC-220 radios in the field. Deployed systems include the AH-64s, MH-60s, CH-47s, Special Operations Aircraft (SOA), and Tactical Vehicles.
5. System Overview: The AN/ARC-220 is a HF Nap-of-the-Earth (NOE) COMM radio. The radio has preset channels, selective squelch, variable power outputs, and a MIL-STD-1553 data bus interface. It provides secure and non- secure voice and digital data communications with Automatic Link Establishment (ALE) and Electronic Counter Counter-Measures (ECCM) capabilities.
In addition to AN/ARC-220 Primary Application Software Support, the MES Branch also supports two software applications, the HF Planner to manage AN/ARC-220 mission data and HF-Tracker to provide position reports to be plotted on the digital map.
The HF-Planner program is a stand-alone application to input frequencies, unique ALE addresses for each radio, modem setup and also the creation and management of internal AN/ARC-220 messages for the creation of the AN/ARC-220 mission data also loading the data to AN/ARC-220 via serial port.
The HF-Tracker is a software application tool used to interface with the AN/VRC-100 HF Radio. It facilitates the capability to receive position reports, plot aircraft position, exchange free text messages with the aircraft and forward position information to another HF-Tracker on the network.
6. System Interoperates With: The AN/ARC-220 interoperates with the AH- 64A/D, MH-60K, MH-47E, UH-60A/L, CH-47D, Army Airborne Command and Control System (A2C2S), Air Traffic Services, and Tactical Vehicles.
7. Other Systems Dependent On: The AH-64A/D, MH-60K, MH-47E, UH- 60A/L, CH-47D, A2C2S, Air Traffic Services, Tactical Vehicles.
8. Software Application Description:
a. Language: Java, C#, Ada
b. Source Line of Code: Approximately 140,000.
c. Operating System: Windows 7 64-bit and 32-bit.
d. Software Version(s): HF Tracker 7.1, HF CPS 2.3, OFP ECP3
e. COTS: None.
f. GOTS: FalconView.
9. Software Development Tools/ Applications:
| Support Tools/Applications |
| Description |
| Git |
| Configuration Management |
| Visual Studio .net 2010 |
| Integrated Development Environment for HF CPS |
| Eclipse |
| Integrated Development Environment for HF Tracker |
| Rational Apex 2.4.6 |
| Development tool for OFP |
| Tartan Ada Compile 4.3.1 |
| Compiler for OFP |
| Visual Studio 6 |
| Development tool for OFP software verification |
| Setup Factory 8 |
| Create installation for HF Tracker |
| Code Reviewer |
| Interactive code review tool |
| Mantis |
| Defect tracker |
| WISE |
| Create installation for OFP |
| Integrated Test System (ITS) 4.4.0 |
| Test automation for OFP |
10. Hardware: The following is a subset of hardware equipment list required to maintain, test and operate HF Radio software. This is not an all-inclusive list.
| Test Hardware Resources |
| Description |
| Rack Mounted Server |
| Redhat Linux to host development tools (Git, Mantis, |
Code Reviewer)
| Development Laptops |
| Laptops configured for development of HF Tracker and HF CPS |
| Test Desktops |
| Desktop computers configured for testing HF Tracker |
and HF CPS
| Lab cabling, switches, routers and power distribution |
| To connect development environment |
| Sun Ultra 60 |
| Apex Development for OFP |
| Test Desktop |
| PC with Windows NT 4.0 SP5 for OFP testing |
| Development Desktop |
| Windows XP SP3 development for OFP |
| AN/VRC-100 Radio with Handset H- 250U |
| Ground radio station for test |
| AN/ARC-220 radio, PA Coupler, Receiver/Transmitter |
| Airborn radio station for test |
Improved Data Modem (IDM)
1. System Name: Improved Data Modem (IDM)
2. System Manager: Communications-Electronics Command, Life Cycle Management Center (CECOM LCMC), Program Executive Office (PEO)/ Aviation, Product Manager Aviation Systems (PM AS)/Product Directorate (PD) Aviation Networks Mission Planning (ANMP).
3. System Proponent: U. S. Army Training and Doctrine Command (TRADOC).
4. System Deployed: The IDM system has 300 deployed systems currently on Rotary wing Army Platforms that includes the UH-60 Blackhawk, the AH- 64A/D Apache, the OH-58 Kiowa, and the Ch-47 Chinook.
5. System Overview: IDM Hardware Series 302 provides an intelligent interface between tactical radios and the on-aircraft MIL-STD-1553B data bus subsystem. It is part of a digital data link between a ground-based observer, scout helicopter, attack helicopter, and attack teams, as well as artillery fire direction centers. Utilizing standard tactical communications radios, the IDM provides both analog and digital communications capability among a variety of U.S. Army, Air Force, and Marine Corps aircraft and ground-based units engaged in Suppression of Enemy Air Defense (SEAD), Close Air Support (CAS), Airborne Forward Air Control (AFAC), special operations, and command and control missions. Its main purpose is to rapidly transfer mission and targeting data to and from ground-based fire support teams, airborne observers, and airborne weapons systems. Its fixed formatted- TACFIRE messages are backward compatible with the present Airborne Target Handover System (ATHS-ECP5), CP-1516A/ASQ.
The interface to the avionics systems is via the MIL-STD-1553B multiplex data bus. The user interface is via a Multi-Function Display (MFD) and Data Entry Keyboard (DEK). The IDM provides four (4) half-duplex radio channels, capable of data transmission rates of 75 to 16K bits per second. Simulta- neous reception or transmission is allowed on any of the four (4) radios.
Each of the channels is capable of being configured into one (1) of three (3) different communications ports: Analog, Digital and Secure. The IDM supports the following digital data link protocols: Army Tactical Fire (TACFIRE), and Air Force Application Program Development (AFAPD).
6. System Interoperates With: The IDM is capable of receiving and transmitting using existing tactical Army radios. The capability of the IDM to communicate utilizing the TACFIRE, AFAPD, and MTS digital data link protocols provides the IDM with interoperability capability with the following systems: ATHS, IDM 304, Battlefield Computer System (BCS), Digital Message Device (DMD), Forward Observer System (FOS), and Advanced Field Artillery Tactical Data System (AFATDS).
The capability of the IDM to communicate on the MIL-STD-1553B data bus provides access to the typical aviation equipment: aircraft data bus controller, navigation, fire control, communications, Operator data entry and display devices, and other remote terminals on the MIL-STD-1553B data bus.
7. Other Systems Dependent On: Systems dependent on the operation of the IDM are: Army Longbow Apache (AH-64C and AH-64D) attack helicopter, Army Kiowa Warrior (OH-58D) attack helicopter, Army Aviation Command and Control System (A2C2S), Army Black Hawk (UH-60Q) helicopter, Army Aviation Tactical Operational Center (AVTOC), Joint Surveillance Target Acquisition Radar System (JSTARS) and the Special Operation Aircraft (SOA). The IDM has also been installed on the Air Force's F-16 C/D aircraft and the Marines’ AV-8B aircraft.
8. Software Application Description:
a. Language: MS Visual C++ 6.0, MS Visual Basic 6.0, VB .NET, C# , Lab View
b. Source Line of Code: Approximately 300,000.
c. Operating System: Microsoft Windows 2000/XP/Vista/Win7/AGM
d. Software Version(s): SLV-E v2.40; SLV-E v3.0;IDM OFP v2.91I
e. COTS: Crescent Software 4.53, DDC MIL-STD-1553 card driver, And/or MIL-STD-1553 PCMCIA card driver, Excalibur MIL-STD-1553 PCMCIA card driver
f. GOTS: None.
9. Software Development Tools/ Applications:
| Support Tools/Applications |
| Description |
| Visual Studio Source Safe 2005 |
| Used for configuration management purposes. |
| Visual Studio 6 |
| Application design environment |
| Visual Studio .Net 2008 |
| Application design environment for AMTS 4.0 |
| Setup Factory 8 |
| Create installation programs for users |
| Crescent Software 4.53 |
| Used to add custom controls and functions to the application. |
| Project Analyzer |
| Analyze source code. |
| Roxio version 9 &10 |
| Write to CD/DVD. |
| Irfanview 4.2 |
| Create/Modify pictures and icons. |
| Beyond Compare 3 |
| Compare files/folders. |
| Blue Force Tracker Network Simulator v8.1 (BTNS) |
| Simulation of BFT data sent to the IDM |
| Lab View v2012 |
| Diagnostic Software |
| SBS 1553 software |
| Used to simulate 1553 communication for testing |
| WireShark |
| Ethernet traffic monitoring tool |
| Linux |
| Some linux tool to validate IDM OS |
10. Hardware: The following is a subset of hardware equipment list required to maintain, test and operate the IDM. This is not an all-inclusive list.
| Test Hardware Resources |
| Description |
| Dell Optiplex 745, 755 |
| Dell desktops configured for development and test. |
| Panasonic Toughbook CF-19, CF- 30, CF-31 |
| Panasonic laptop configured for test purposes. |
| Miltope MSD-B, MSD-V2-B, MSD- V3-B |
| Miltope laptop configured for test purposes. |
| Excaliber PCMCIA 1553 card |
| Provide the MIL-STD-1553 interface between the |
computer and BTNS simulation computer
| Loral Instruments SBA-100F |
| Used to monitor the MIL-STD-1553 signals to and from the computer and Unit Under Test (UUT) |
Tenma Corp Dual Power Supply model 72-6854 Used to power the UBOB/ABOB/UUT
| Hewlett-Packard DC Power Supply model 6269B |
| Used to power the UBOB/ABOB/UUT |
Hewlett-Packard Universal Frequency Counter model 5328A Used to obtain the transmitted frequency from the
UUT.
| Interface Cable Assemply |
| Used to establish a manual connection, addressing, and power for the unit under test. |
| DURO PCs, PN:RAC341 |
| PC holds DDC dataSims, Lab View software |
Curtiss-Wright 1553 Multiplex Bus Switches, PN:DHAS-MBS1616 1553 Multiplex Bus Switches
| Black Jack Test PN: BTI-150 |
| Power Supply |
Lightweight Doppler Navigation System (LDNS) System Name: Lightweight Doppler Navigation System (LDNS) AN/ASN-128 DGNS
1. System Manager: Program Manager, Aviation Mission Equipment (PM AME).
2. System Proponent: Program Manager, Aviation Mission Equipment (PM AME).
3. System Deployed: There are more than three thousand units deployed on various platforms (Chinook & Blackhawk). Some with older version AN/ASN- 128B, but most have already been upgraded to the AN/ASN-128D version.
4. System Overview: LDNS/DGNS is a self-contained jam resistant, airborne navigational set with a fully militarized/NAVWAR-compliant Global Positioning System (GPS) receiver in a Doppler Navigation System providing present position and bearing, time and distance to selected destinations in friendly and hostile environments. It is operational in nearly 3,000 U.S. Army helicopters deployed worldwide.
5. System Interoperates With: LDNS communicates with pilot.
6. Other Systems Dependent On: None
7. Software Application Description: (*Source Code is not maintained by SEC)
a. Language: Ada
b. Source Line of Code: Approximately 1.0 Million.
c. Operating System: Operating System: Vax, MS Operating System.
d. Software Version(s): WMM 2015 (Global Map), CDU - V1.27, SDC(D/B) - V1.08, SDC – V1.15 (OFP).
e. COTS: None.
f. GOTS: Software Loader Verifier (SLV).
8. Software Development Tools/ Applications:
| Support Tools/Applications |
| Description |
| VAX Compiler |
| Compile source Code |
| SLV Loader - GOTs |
| Soft Loader |
9. Hardware: The following is a subset of hardware equipment list required to maintain, test and operate LDNS software. This is not an all-inclusive list.
| Test Hardware Resources |
| Description |
| VAX |
| Sun Solaris to run ATNAVICS. |
| MS Vista Desktop |
| To utilize SLV Software |
| Cabling |
| To communicate with ASN-128 CDU/SDC |
MOBILE TOWER SYSTEM
1. System Name: MOBILE TOWER SYSTEM (MOTS).
2. System Manager: CECOM LCMC SEC
3. System Proponent: PEO Aviation
4. System Deployed: 1-58th ATS BN (Fort Bragg, NC), 1-11th ATS BN (Fort Rucker, AL), F CO 58th AVN, 3-58th AVN (Germany), 164th ATS Group (Korea), 1-245th ATS BN (Oklahoma), 204th ATS Group (Louisiana) and G CO 58th AVN Oahu (Hawaii); U.S. Marine Corps and various Army National Guard units.
5. System Overview: The MOTS mission is to provide Air Traffic Services (ATS) in airspace designated for air traffic movement at terminal areas of the Joint Operations Area (JOA) and Theater, during war and for supporting crisis response and limited contingency operations. The MOTS, along with the Tactical Terminal Control System (TTCS) and Air Traffic Navigation Integration and Coordination System (ATNAVICS), also integrates with the Army’s area airspace management system, the Tactical Airspace Integration System (TAIS), to form a network that provides management of airspace over an area of operation.
6. System Interoperates With: Tactical Terminal Control System (TTCS), Air Traffic Navigation Integration and Coordination System (ATNAVICS), Tactical Airspace Integration System (TAIS).
7. Other Systems Dependent On: N/A.
8. Software Application Description:
a. Language: C# , Java
b. Source Line of Code: Not Available (TBD)
c. Operating System: Microsoft Windows 7
d. Software Version(s): Not Available (TBD)
e. COTS: ClearQuest/Clearcase, DOORS, TOCNET SoftCAU, TOCNET Mission Recorder,WhatsUp Gold, McAfee Application Control/Change Control, McAfee Data Loss Prevention Device Control Manager, WorldClock, ALSCU
f. GOTS: MOTS Audio Player
9. Software Development Tools/ Applications:
| Support Tools/Applications |
| Description |
| Windows Server 2008 R2 |
| Server Operating system |
| AGM Windows 7 |
| Workstation Operating system |
McAfee VirusScan Enterprise 8.8 Detects and removes viruses, Trojan horses, spyware, keystroke loggers, and other unwanted monitoring software.
| Symantec Ghost |
| Develop an image of the software for distribution of MOTS. |
| Java 7 update 51 |
| Run time environment |
TOCNET Configuration Manager A component for the Tactical operations Center Intercommunications System allowing for bridging, crossbanding and conferencing of various radio communication.
TOCNET Mission Recorder A component for the Tactical operations Center Intercommunications System that records and stores voice communications from all MOTS audio channels.
TOCNET SoftCAU This component makes the radios, telephones and intercom accessible to the operator while displaying the time, necessary meteorological information and status of the NDB and UPS.
WhatsUp Gold Standard Edition Provides extensive monitoring and alerting on the status of network services, SNMP data, Windows and syslog events.
| MOTS LRU Controller |
| An application to set the LRU parameters. |
| MOTS Audio Player |
| Playback tool for TOCNET audio. Plays back multiple audio files simultaneously. |
| C# Audio Library |
| Freeware compiled into Audio Player |
| Windows Server 2008 R2 |
| Server Operating system |
| AGM Windows 7 |
| Workstation Operating system |
McAfee VirusScan Enterprise 8.8 Detects and removes viruses, Trojan horses, spyware, keystroke loggers, and other unwanted monitoring software.
| Symantec Ghost |
| Develop an image of the software for distribution of MOTS. |
| C# Logging Library |
| Freeware compiled into Audio Player and LRU Controller |
| Fabulatech Serial Port Redirector |
| Provides communication and access to remote serial devices through virtual ports. |
| ALS Control SW |
| Airfield lighting control software. |
| WorldClock v5.49 |
| The application allows user configurable clocks, each with its own time zone. |
| Digi X-CTU |
| The application allows MOTS to test radio modems. |
| Logic Instrument Night Vision Software |
| The server display supports the night vision software |
10. Hardware: The following is a subset of hardware equipment list required to maintain, test and operate MOTS software. This is not an all-inclusive list.
| Hardware Resources |
| Description |
Operator Workstation:
Logic Instrument Getac (Model No. V205) This platform will be used as the Operator Workstations in the test environment.
MOTS Server:
General Dynamics Itronix GD8200 Hosts applications which provide data to the Operator Workstations.
| Operator/Trainer Jackbox with Headset/Handset |
| Communication devices for the Operator Workstations. |
| TOCNET eMCSU |
| Digital switch for voice communications. Also connects the MOTS Server to the ALS & MMS modems. |
| Adtran |
| Switch connecting phone lines to the TOCNET eMCSU. |
Operator Workstation:
Logic Instrument Getac (Model No. V205) This platform will be used as the Operator Workstations in the test environment.
MOTS Server:
General Dynamics Itronix GD8200 Hosts applications which provide data to the Operator Workstations.
| Operator/Trainer Jackbox with Headset/Handset |
| Communication devices for the Operator Workstations. |
| TOCNET eMCSU |
| Digital switch for voice communications. Also connects the MOTS Server to the ALS & MMS modems. |
| Adtran |
| Switch connecting phone lines to the TOCNET eMCSU. |
| Digi RF Modem |
| Modem that provides communications to the ALS and MMS. |
| TACMET II MMS |
| Receives data from the weather sensors |
| Airfield Lighting System |
| Software-controlled airfield lights |
| PRC-117G radio |
| Provides radio communications path via TOCNET |
| ARC-220 |
| Provides radio communications path via TOCNET |
| GPS Antenna & Splitter |
| Provide time data to the radios, TOCNET and the rest of the system. |
| Digi RF Modem |
| Modem that provides communications to the ALS and MMS. |
| TACMET II MMS |
| Receives data from the weather sensors |
Army Installation Entry (AIE) DESCRIPTION
1. System Name: Army Installation Entry (AIE)
2. System Manager: Program Manager (PM) Terrestrial Sensors, Product Manager Force Protection Systems (PdM FPS), under the direction of the Program Executive Office Intelligence Electronic Warfare and Sensors (PEO IEW&S).
3. System Proponent: Product Manager Force Protection Systems (PdM FPS)
4. System Deployed: There are 26 AIE-2+ Operational Installations.
5. System Overview: The Army AIE system is an electronic entry control system employed to provide automated authentication and verification of personnel and vehicles entering Army Installations. The operational system consists of an integrated database containing registered personnel and registered vehicles with linkage to the vehicle owner and authorized operators of each registered vehicles. The AIE System standardizes and integrates identification, authorization, authentication, credentialing, registration and access into Army Installations.
6. System Interoperates With: The AIE system interoperates with Defense Enrollment Eligibility Reporting System (DEERS), Interoperability Layer Service (IoLS) and Continuous Information Management Engine (CIME). AIE 3 uses IoLS as a conduit to National Law Enforcement Telecommunications System (NLETS) and National Crime Information Center (NCIC).
7. Other Systems Dependent On: DEERS, IoLS, CIME, NLETS and NCIC.
8. Software Application Description:
a. Language: HTML, SQL, XML
b. Source Line of Code: N/A
c. Operating System: Windows 7 Professional and Windows Server 2008 R2.
d. Software Version(s): AIE 3.0
e. COTS: EntryPoint, Symmetry Security Management Software, Identity Management Middleware (IMM), IMM AutoReg, Express Cluster X, SQL Server, Hawkeye Mobile, Automated License Plate Recognition (ALPR) Server.
f. GOTS: None.
9. Software Development Tools/ Applications:
| Support Tools/Applications |
| Description |
| Git |
| Configuration Management |
| Visual Studio 2015 |
| Integrated Development Environment |
| Code Reviewer |
| Interactive code review tool |
| Mantis |
| Defect tracker |
10. Hardware: The following is a subset of hardware equipment list required to maintain, test and operate AIE software. This is not an all-inclusive list.
| Test Hardware Resources |
| Description |
| Cisco ASA 5510-AIP10SP-K9 and ASA 5505V11 |
| Firewalls |
| Cisco CON-SU1-ASAINC10 |
| Intrusion Detection Systems / Intrusion Prevention Systems |
| Belkin F1DN104U |
| KVMs |
| Cisco WS-C2960-24TS-L, WS-C2960G-24TC-L, WS-C2960-24-S, WS-C3750G-24S-S |
| Swtiches |
| Cisco 2921 |
| Routers |
| NEC NEC-5800 |
| Primary Site Server |
| Dell Power Edge 410, Dell T-710 |
| Secondary Site Server, Access Control Point Server |
| Panasonic Toughbook, Dell Optiplex 780, HP HPZ400, AMBX 226SB7-6LP |
| Workstations |
| Cisco AIR-SAP2602E-A-K9 |
| Access Point |
| Dell Equal Logic PS410 |
| Storage Area Network Arrays |
Persistent Surveillance and Dissemination System of Systems (PSDS2) DESCRIPTION
1. System Name: Persistent Surveillance and Dissemination System of Systems (PSDS2)
2. System Manager: Program Manager (PM) Terrestrial Sensors, Product Manager Force Protection Systems (PdM FPS), under the direction of the Program Executive Office Intelligence Electronic Warfare and Sensors (PEO IEW&S).
3. System Proponent: Product Manager Force Protection Systems (PdM FPS)
4. System Deployed: There are 88 operational systems in OCONUS.
5. System Overview: The PSDS2 video management system integrates multiple sensors for enhanced situational awareness and rapid decision-making. It provides real-time viewing, dissemination, archiving and exploitation for operations, intelligence and protection. It manages video bandwidth for edge to enterprise networks and delivers quality without disruption. PSDS2 provides monitoring and management of multiple sensor feeds through a web browser interface and dynamically adapts to user layout and sensor selections to improve overall client environment performance. Sensor status, location, field of regard and tracks are integrated on a map display, which enables users to see both the video data and map tracks in context.
The Blue Eye Sensor (BES) software provides Data Management System ingests and disseminates video, audio and metadata from multiple sensors data. The Blue Eye system provides multiple web based tools to view and analyze sensor data, generate video clips and images, and disseminate the analyzed data to other systems. Sensor status, location, field of regard and tracks are displayed on a map, allowing users to see available sources of intelligence data. The Blue Eye system retains the sensor data and provides a centralized motion imagery archive for forensic analysis.
6. System Interoperates With: The PSDS2 system…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .