Compiler Monitor System (CMS-2Y) Software Language Operation in X86 Linux Computing Environments
Navy SBIR 2018.1 - Topic N181-030
NAVSEA - Mr. Dean Putnam -
Opens: January 8, 2018 - Closes: February 7, 2018 (8:00 PM ET)


TITLE: Compiler Monitor System (CMS-2Y) Software Language Operation in X86 Linux Computing Environments


TECHNOLOGY AREA(S): Battlespace, Electronics, Sensors

ACQUISITION PROGRAM: Program Executive Office Integrated Warfare System (PEO IWS) 1.0 – AEGIS Combat System

The technology within this topic is restricted under the International Traffic in Arms Regulation (ITAR), 22 CFR Parts 120-130, which controls the export and import of defense-related material and services, including export of sensitive technical data, or the Export Administration Regulation (EAR), 15 CFR Parts 730-774, which controls dual use items. Offerors must disclose any proposed use of foreign nationals (FNs), their country(ies) of origin, the type of visa or work permit possessed, and the statement of work (SOW) tasks intended for accomplishment by the FN(s) in accordance with section 5.4.c.(8) of the Announcement. Offerors are advised foreign nationals proposed to perform on this topic may be restricted due to the technical data under US Export Control Laws.

OBJECTIVE: Develop a method for executing legacy Compiler Monitor System (CMS-2Y) tactical code on an X86 computer running the Linux operating system to validate critical software updates in the AEGIS Test Bed (ATB).

DESCRIPTION: CMS-2Y computer software language for tactical operations was developed for Fleet Computer Programming Center - Pacific (FCPCPAC) to support Naval Tactical Data Systems (NTDS) operations.  The language continued to be developed, eventually supporting a number of combat system computers including the AN/UYK-43 which became the standard 32-bit computer of the United States Navy for surface ship and submarine platforms.  AEGIS platforms have AN/UYK-43 units that are currently in service.  The UYK-43 is being replaced by the AN/UYQ-70 and commercial off-the-shelf (COTS) systems on the majority of AEGIS Combat System platforms, with the exception of AEGIS Baselines (BL) 3.6, 5.3, and 5.4.

CMS-2Y is currently run on AEGIS BL3.6, BL5.3, and BL5.4.  The current ATB resides on an X86 computer system that utilizes Linux operating systems.  The ATB is a simulation environment that contains representative functions for the AEGIS Combat System (ACS) such as sensors, radars, digital data links, and weapons systems which comprise the ACS.  CMS-2Y software language code is not compatible with the X86 COTS hardware and the Linux operating system which hosts the ATB.  This incompatibility prevents these legacy baselines from being thoroughly tested in the current ATB environment.  CMS-2Y tactical software code needs to run in the ATB hosted environment on an X86 computer system running the Linux operating system to ensure that the ships running CMS-2Y software are accurately and thoroughly tested. A method is required to translate CMS-2Y tactical code to support its evaluation on the ATB.

The solution will develop emulation, virtualization, and/or compilation using open-source code to facilitate testing critical updates of AEGIS ships operating with CMS-2Y tactical code.  The translator must execute the 32-bit CMS-2Y tactical code on COTS X86 computer system running the Linux operating system in the ATB environment.  The translated CMS-2Y code must process data at variable speeds (real-time, faster than real-time, and slower than real-time) to support various test requirements and scenarios in the ATB.  Translation results will be compared to Navy land-based test facility operational data to verify and validate emulator functionality.

The Phase II effort will likely require secure access, and NAVSEA will process the DD254 to support the contractor for personnel and facility certification for secure access.  The Phase I effort will not require access to classified information.  If need be, data of the same level of complexity as secured data will be provided to support Phase I work.

Work produced in Phase II may become classified. Note: The prospective contractor(s) must be U.S. Owned and Operated with no Foreign Influence as defined by DOD 5220.22-M, National Industrial Security Program Operating Manual, unless acceptable mitigating procedures can and have been implemented and approved by the Defense Security Service (DSS). The selected contractor and/or subcontractor must be able to acquire and maintain a secret level facility and Personnel Security Clearances, in order to perform on advanced phases of this contract as set forth by DSS and NAVSEA in order to gain access to classified information pertaining to the national defense of the United States and its allies; this will be an inherent requirement. The selected company will be required to safeguard classified material IAW DoD 5220.22-M during the advance phases of this contract.

PHASE I: Develop a concept for a translator to execute CMS-2Y legacy tactical code to run on an X86 using the Linux operating system environment as identified in the Description section of this document.  Also develop a preliminary Plan of Action and Milestones (POA&M) to design, develop, test and integrate the proposed emulator into the AEGIS Test Bed.  Prove the concept is feasible through comparison to Navy land-based test facility operational data to verify functionality.  The Government will provide the facility for the comparison. The Phase I Option, if awarded, will include the initial design specifications and capabilities description to build a prototype in Phase II. Develop a Phase II plan.

PHASE II: Based upon the results of Phase I and the Phase II Statement of Work (SOW), develop and deliver a prototype software application. Implement the software into the ATB, which represents the combat system test environment.  The prototype must be capable of demonstrating the ability to thoroughly exercise CMS-2Y-based AEGIS BL in the ATB environment.  The demonstration will take place in a Government-provided facility. The company will provide software design documentation, test plans, and procedures to document and demonstrate the product meets the attributes described in the Description section of this document. Prepare a Phase III development plan to transition the technology for Navy use and Program of Record.

It is probable that the work under this effort will be classified under Phase II (see Description section for details).

PHASE III DUAL USE APPLICATIONS: Support PEO IWS 1.0 in system integration of the developed software application from Phase II.  This will be accomplished by incorporation of the software into the ATB. This will consist of integrating into a BL definition, incorporation of the BL existing and new threat capabilities, validation testing, and combat system certification.

This development can be used in many of the operating systems for computers. A development that can translate code from one computer to another will be invaluable in the industry for companies that have varying and different computer systems. It would make using the different systems unique in that they can port code from one system to another and not have to worry about which computer or operating system it was developed on.


1. “Reference Manual for AN UKY-7 and AN UYK-43 Computers.” October 1986.  29 March 2017.

2. Iwamiya, R., Mumm, H., Ollerton, B., Riegle, B., and Colket, C. “CMS-2 to Ada Translator Evaluation Final Report.” Technical Document 2984 September 1997, NRAD and SPAWAR.  30 March 2017.

KEYWORDS: CMS-2Y Computer Software Language for Tactical Operations; X86 COTS Hardware; Linux Operating System in the ATB; CMS-2Y Tactical Code; Emulation, Virtualization, and Compilation Using Open Source Code; Critical Updates of AEGIS


These Navy Topics are part of the overall DoD 2018.1 SBIR BAA. The DoD issued its 2018.1 BAA SBIR pre-release on November 29, 2017, which opens to receive proposals on January 8, 2018, and closes February 7, 2018 at 8:00 PM ET.

Between November 29, 2017 and January 7, 2018 you may talk directly with the Topic Authors (TPOC) to ask technical questions about the topics. During these dates, their contact information is listed above. For reasons of competitive fairness, direct communication between proposers and topic authors is not allowed starting January 8, 2018
when DoD begins accepting proposals for this BAA.
However, until January 24, 2018, proposers may still submit written questions about solicitation topics through the DoD's SBIR/STTR Interactive Topic Information System (SITIS), in which the questioner and respondent remain anonymous and all questions and answers are posted electronically for general viewing until the solicitation closes. All proposers are advised to monitor SITIS during the Open BAA period for questions and answers and other significant information relevant to their SBIR/STTR topics of interest.

Topics Search Engine: Visit the DoD Topic Search Tool at to find topics by keyword across all DoD Components participating in this BAA.

Proposal Submission: All SBIR/STTR Proposals must be submitted electronically through the DoD SBIR/STTR Electronic Submission Website, as described in the Proposal Preparation and Submission of Proposal sections of the program Announcement.

Help: If you have general questions about DoD SBIR program, please contact the DoD SBIR Help Desk at 800-348-0787 or via email at