Electronic Warfare Planning and Management Tool (EWPMT)

*** Amendment 0001 - All requests for a draft PWS and Security Appendix must be made no later than 21 January 2022.  Vendors previously denied access to these documents are encouraged to resubmit their request. 

*** NOTE – Product Manager (PdM) Electronic Warfare Integration (EWI) elects to resolicit responses with updated contract requirements included.  This Request for Information (RFI) is an update to the previous market survey, which is more than 12 months old. *** 

Request for Information (RFI): 

Program Executive Officer (PEO) Intelligence, Electronic Warfare & Sensors (IEW&S), Project Manager (PM) Electronic Warfare & Cyber (EW&C), PdM EWI, is conducting this RFI to identify sources capable of providing a range of continued services necessary for the update, continued development, integration, testing, delivery, fielding, training, maintenance, configuration management, and sustainment of the EWPMT system.  A copy of the draft Performance Work Statement (PWS) and Security Appendix of this EWPMT requirement will be provided through Department of Defense (DoD) Secure Access File Exchange (SAFE) upon request.  All requests for a draft PWS and Security Appendix must be made no later than 21 January 2022.

BACKGROUND 

PdM EWI is the Product Manager for the Acquisition, Development, Deployment, and Sustainment of the EWPMT. Facing an electromagnetic environment that is congested and contested among adversaries and nonaligned parties as well as the proliferation of electronic warfare (EW) technologies worldwide, the Army intends to continue development of a framework and equipping of capabilities to integrate current and future EW capabilities into a networked, modular system capable of providing a unified EW capability across the force.  The EWPMT is a software application that gives Electronic Warfare Officers (EWO) and Electromagnetic Spectrum Managers (ESM) mission capabilities to plan, coordinate, manage, and de-conflict unit EW activities. It provides battle management for distributed, networked EW capability, aligned with fires and synchronize air/ground electromagnetic spectrum operations across the intelligence, operations, and spectrum management areas of responsibility. 

EWPMT is an open, modular, plug-in architecture based upon a layered Service Oriented Architecture (SOA) design that enables incremental integration of EW applications, services and interfaces. It is currently comprised of four Computer Software Configuration Items (CSCIs): Total Battlespace Awareness (TBSA), Electronic Warfare Battle Management (EWBM), Electromagnetic Operating Environment (EMOE), and Spectrum Management (SM). The EWPMT software application is installed on a Secure Host Baseline-Army (SHB-A) configured laptop with the latest security patches and is accessed via Google Chrome. EWPMT is permitted to operate in Unclassified and Classified environments.

EWPMT is currently being developed and supported under contract W15P7T-14-D-C006 with Raytheon Technologies.   This RFI is to gain information for a potential contract competition for the continued development of updates for relevancy, functionality, sustainment, and customer funded procurements to support the future of EWPMT. 

A copy of the draft PWS and draft Security Appendix of this EWPMT requirement will be provided through DoD SAFE upon request.  The EWPMT draft PWS and draft Security Appendix are marked Controlled Unclassified Information (CUI) and are controlled under DISTRIBUTION STATEMENT D. To obtain a copy of these documents for review purposes, your eligibility will have to be verified by the Government. At this time, PdM EWI is only soliciting comments back from verified Cleared Defense Contractors with an active Commercial and Government Entity (CAGE) Code and at least a Secret Facility Clearance Level (FCL). The adjudication and response process is as follows:

1. The interested and cleared company provides PdM EWI with the information requested below under “RESPONDING TO THIS RFI”.

2. PdM EWI Security verifies that a valid company clearance exists in the Department of Defense (DoD) National Industrial Security System (NISS).

3. PdM EWI releases a soft copy of EWPMT PWS and comment response matrix (CRM) to the verified company POC.

4. The company reviews EWPMT PWS and fills out the CRM with comments.

5. The company provides the completed CRM and accompanying files back to PdM EWI NO LATER THAN 26 January 2022.

6. Further correspondence, including questions and comments, will be provided by PdM EWI.

DESIRED INFORMATION

Provide potential solutions to the following capabilities and support requirements.  Interested parties should cite relevant and recent experience and how that experience relates to the EWPMT requirements and capabilities listed in this RFI.  Recent is defined as less than three years from the date of this RFI.  Please include a description of the work completed along with program names, software capability names, customer, contract numbers, and the date of completion.  Vendors should not submit capability statements. Please indicate what additional information is required (if any), beyond what is requested below, in order for the vendor to compete.

CURRENT AND REQUIRED EWPMT TECHNICAL CAPABILITIES

PdM EWI is requesting information on industry’s ability to maintain and provide additional EWPMT capabilities and solutions per the requirements listed below:

1. EW Mission Planning - Provide the data necessary to identify signal type or signal identification and its effects on EW operations based on live sensor data and previously characterized systems of interest.  Provide modelling and simulation capability to inform the user of optimal use of available EW assets, Tactics, Techniques, and Procedures (TTPs), and environment.

2. EW Effectiveness - Provide the capability to identify friendly vulnerabilities in the area of operations exploitable by enemy actions.  Provide damage assessments of electromagnetic attacks of identified targets to determine if the desired effects were achieved or the target requires re-attack.  Display current and post mission analysis to determine mission effectiveness and non-lethal Battle Damage Assessment (BDA). 

3. Reprogramming of Organic EW assets - Command and control of the Multi-Function Electronic Warfare (MFEW), Terrestrial Layer System (TLS), Government off-the-shelf (GOTS) and Commercial off-the-shelf (COTS) receivers and sensors.   Provide the capability to remotely control all organic, assigned, and/or OPCON EW assets over the network.  Provide the capability to execute "Buzzer On / Buzzer Off" (an unclassified term to initiate and terminate EA activities) remotely over the tactical network in support of EW missions.  The EWPMT shall have a graphical user interface (GUI) for the control of EW assets. 

4. EA Alert – Provide the capability to display EW Strike. Display detected RF emitters associated with enemy weapons and sensor systems providing display warning of impending threat or attack. 

5.  Targeting Process - Provide the capability to pass Find-Fix-Target (F-F-T) information to Fires and Maneuver elements based on live sensor data, including Multi-Function Electronic Warfare (MFEW) and Terrestrial Layer System (TLS) survey data, to support the deliberate targeting process for scheduled and on-call targets; and to support the unplanned and unanticipated dynamic targets of opportunity.  Provide Find-Fix-Target (F-F-T) information to Fires and Maneuver elements as necessary involving actions tasked by, or under direct control of an operational commander to search for, intercept, identify, and locate sources of intentional and unintentional radiated electromagnetic energy for the purpose of immediate threat recognition, targeting, planning, and conducting future operations. 

6. Electromagnetic Spectrum Management Information – Provide the ability to assess unit's emission from electromagnetic, acoustic, or other sources to optimize friendly operations and capabilities while minimizing detection by enemy sensors and mutual interference among friendly systems. 

7.  Common Operational Picture (COP) – Provide the capability to send data to and ingest data from a Commander’s COP to support creation of an integrated picture of the Area of Responsibility (AOR), and allow upper echelons to better understand the battlefield.  For example, EWPMT provides the necessary data to the Command Post Computing Environment (CPCE) framework in order to build out the COP.

8. Large Data Set Management – Ingest and display curated data sets to facilitate the Military Decision Making Process (MDMP) without overwhelming the user and network.  All pertinent data will be utilized but may not have to be displayed to the user.

9. Engineering and Development Practices – Provide the capability to implement a software development process that supports DevSecOps principles in the automation, monitoring, and application of security at all phases of the software lifecycle: plan, develop, build, test, release, deliver, deploy, operate, and monitor. Within DevSecOps principles, security and functional capabilities are tested and built simultaneously. The Contractor shall provide a clear DevSecOps strategy and explanation of the continuous delivery pipeline in the form of sprints and epics, to rapidly deliver incremental capabilities, test incremental updates, and address defects and evolving requirements on an ongoing basis.  Knowledge of systems engineering principles and practices to achieve delivery and maintenance of an operationally relevant capability is key.  Ability to design and implement an open SW architecture to allow for third party developers to provide additional capabilities with minimal support, as well as ingest information from a larger data fabric are also key.

SUPPORT REQUIREMENTS 

  1. Training Support: 

a. Provide knowledgeable trainers/instructors to conduct EWPMT New Equipment Fielding (NEF), New Equipment Training (NET), and network integration to military units as directed by the Government. It is preferred but not required that the trainers/instructors have Electronic Warfare (EW) and Electromagnetic Spectrum (ESM) knowledge and experience.  Training will be conducted at CONUS and OCONUS sites.

b. Provide qualified Field Service Representatives (FSR’s) as needed to support New Equipment Fielding (NEF), New Equipment Training (NET), network integration and any follow-on/additional support as directed by the Government. FSRs will be expected to travel within CONUS and OCONUS.

2. Test Support- Conduct and support testing as required.  This will include but not be limited to testing for functionality, cybersecurity, integration, regression, and system of system tests with other systems.    

3. Sustainment Engineering Support:

a. Provide software development engineering support for analyzing and fixing Category 1 and 2 software defects (catastrophic, or severe with no workaround), cybersecurity patching, artifacts to support Risk Management Framework (RMF), support ATO maintenance and updates to the documentation as well as ensuring the overall security of the system.

b. Update the software technical manual/training packages if necessary due to development/sustainment updates, and manage defects reported from the field and/or testing.

c. Provide a software development environment that is sufficient to build and maintain the software baseline; provide developer-focused training (e.g., how to rebuild, develop code, how Information Assurance Vulnerability Alert (IAVA) patches are developed and applied, and how to develop and maintain the Software Development Toolkit (SDK)).

4.  If a Request for Proposal (RFP) is released, the following existing documents may also be released:

• Software Test Plan/Procedure (STPP)
• System Development Environment (SDE) Design Document
• Software Development Kit (SDK)
• System Security Plan (SSP)
• System/Subsystem Specification (SSS)
• Software Architecture Design Document (SADD)
• Software Design Description (SDD)
• Interface Design Description (IDD)
• Software Version Description Document (SVDD)
• Database Design Description (DBDD)

• System Engineering Master Plan (SEMP)

OTHER INFORMATION REQUIRED

Interested parties should address the following information in addition to the capabilities and support requirements listed above.

1. State whether the vendor has the capability to fully meet some or all of the above EWPMT requirements. If the vendor can only partially meet the requirements, state the specific capabilities.   

1. Describe innovative approaches to meeting the above engineering support and developmental capabilities for EWPMT. Include in the approach: development and test process; configuration management tools and process, integration of external GOTS or COTS software, software deployment and patching, use of and adoption of messaging standards (e.g. Joint Interface Control Document (JICD) 4.0 and later, Integrated Sensor Architecture (ISA)), and improving existing capabilities.  The proposed effort would be to build upon the current EWPMT to support user requirements, continuing development and transitioning to sustainment activities.  Describe considerations and information required in a Technical Data Package (TDP) (Should the Government provide the TDP as GFI and GFP) to support technical proposal development and transition to the development/sustainment activities. 

1. Describe the ability to implement Development, Security, Operations (DevSecOps) in the continued development and iterative deployment of EWPMT.

1. Clearly identify any approaches to meeting the above capabilities in which the Government would receive less than Government Purpose Rights (GPR).  Identify any techniques, capabilities, algorithms, or other approaches that were developed solely by the vendor as proprietary data or internal research and development (IRAD). 

1. Confirm the vendor’s ability to provide staff cleared up to the TS/SCI level. The vendor shall also provide information on its facility clearance and if it can be achieved and maintained at a minimum Secret level with ready access to a SIPR terminal.  What is the vendor’s ability to access SECRET documents on a 24 hour time-frame?

1. Describe the vendor’s ability to fulfill some or all of the requirements using Commercial Off-The-Shelf (COTS) or Government off-the-shelf (GOTS) software, if applicable.

RESPONDING TO THIS RFI

Any interested party shall submit a white paper in response to the above capabilities.  Vendors should cite relevant and recent experience and how that experience relates to the EWPMT requirements and capabilities listed in this RFI.  Recent is defined as less than three years from the date of this RFI.  Please include a description of the work completed along with program names, software capability names, contract numbers, and the date of completion. 

The white paper shall be due no later than 30 days after the posting of this RFI.  The response date denoted on SAM.Gov shall hold precedence. Vendors may submit any questions related to this RFI, or the accompanied PWS, no later than one week after the posting date.  RFI responses are limited to fifteen (15) pages, including cover and administrative pages.  All RFI responses shall include the following: 

Company name, company address, overnight delivery address (if different from mailing address), DUNS Number, CAGE code, point of contact, e-mail address, telephone number, and fax number. Additionally, please state if your company is foreign owned, either directly or indirectly.

Certification of business size (large or small) under NAICS code 541511 "Custom Computer Programming Services". Also provide socioeconomic categories if a small business (i.e. large, small disadvantage, veteran-owned, woman-owned, etc.). 

Interested parties are requested to respond to this RFI in Microsoft Word Office compatible format.  Responses shall be written using a 12 point font size or larger.  This RFI is for planning purposes and does not constitute a commitment, implied or otherwise, that a procurement action will be issued. No entitlement to payment by the Government of direct or indirect cost or charges will arise as a result of the submission of a company's or corporation's information. 

The Government shall not be liable for or suffer any consequential damage for any improperly identified proprietary information. Proprietary information will be safeguarded in accordance with the applicable Government regulations and requirements.  The Government does not guarantee that this RFI will result in a Request for Proposal (RFP) or contract award. The Government will not provide reimbursement for any costs incurred by vendors who respond to this RFI.   

All questions and responses relating to this notice shall be sent via email to the below with the Subject, (EWPMT RFI - "Your Company Name") 

Mr. Charlesworth Williams (charlesworth.c.williams2.civ@mail.mil), Contract Specialist  

To request a copy of the draft PWS and draft Security Appendix, vendors should provide DUNS Number, CAGE code, address that coincides with the CAGE code, point of contact, e-mail address, and telephone number to the below POC NLT 21 January 2022:

Ms. Alison T. Powell, alison.t.powell.civ@army.mil

In accordance with Federal Acquisition Regulation PART 10.001, the results of this Market Survey will primarily be used to develop the Government's acquisition approach and will be used to determine if sources capable of satisfying the agency's requirements exist.  This is NOT a request for proposal and does not constitute any obligation by the Government to award a contract based on the findings from the survey. The Government will not reimburse interested sources or respondents to notice, or any follow-on notice, for any costs incurred in association with this announcement or for subsequent exchange of information.  All requests for further information must be in writing and via email; telephonic requests for additional information will not be honored. 

Contact Information: 

Contracting Office Address 

DIV C HQ CECOM CONTRACTING CTR  

6565 SURVEILLANCE LOOP 

ABERDEEN PROVING GROUND, MD 21005-1846 

Primary Points of Contact:

Charlesworth C. Williams II

charlesworth.c.williams2.civ@mail.mil