The Department of Defense (DoD), Defense Information Systems Agency (DISA), Services Development Executive Office (SD) Command and Control (C2) Portfolio Management Office (SD4) has a requirement for Joint Capabilities Requirements Manager (JCRM) Software Sustainment and Maintenance.

N/A

The contractor shall provide services to meet the following:

• Information Assurance (IA) and Cybersecurity are important to JCRM as an operational system while the modernized effort is being developed. Describe and provide an example of your company’s experience providing Cybersecurity and IA that utilizes the Risk Management Framework, such as: reporting and disclosing the status of security related matters, reviewing the Information Assurance Vulnerability Alert (IAVA) weekly and assessing impacts, updating Plans of Action and Milestones (POA&Ms) in the Page 3 of 5 Pages enterprise Mission Assurance Support Service (eMASS), providing Commercial Off The Shelf (COTS) patch releases, and maintaining a fully Security Technical Implementation Guide (STIG)-compliant environment.
• JCRM is an operational program that is utilized worldwide 24 hours per day, seven days per week, and 365 days per year. It is essential that the system remain available for users without issue. Describe and provide an example of your company’s experience providing Tier 3 Help Desk Support. This should include specialized skills and support over and above the skills and experience of Tier 2 support. Tier 3 deals with complex system and software issues that require in-depth technical, architectural, and developmental knowledge to solve a problem which may require a workaround or modification to the system and/or software.
• JCRM has several external users connected to the system. Maintaining the system is important to the overall user experience. Describe and provide an example of your company’s experience in providing preventive, adaptive, and corrective maintenance for a system in sustainment and the methodology used (i.e., Agile). “Preventive maintenance” is defined here as: performing activities to prevent the occurrence of errors, reducing software complexity, and thereby improving program understandability and increasing software maintainability. “Adaptive maintenance” is defined here as: the implementation of changes in a part of the system, which has been affected by a change that occurred in some other part of the system or by an external system. Adaptive maintenance consists of adapting software to changes in the environment. “Corrective maintenance” is defined here as: corrective actions that deal with the repair of faults or defects found in day-to-day system functions. A defect can result due to errors in software design, logic, patches, and coding.
• Similar to the above required capability is providing perfective maintenance. Describe and provide an example of your company’s experience in providing perfective maintenance on a system to include implementing new or changed user requirements and the methodology used. This also involves making functional enhancements to the system in addition to the activities to increase the system’s performance even when the changes have not been suggested by faults. This includes enhancing both the function and efficiency of the code and changing the functionalities of the system as per the users’ changing needs.
• Testing is an integral part of fielding software. Describe and provide an example of your company’s experience conducting test and evaluation for preventive, perfective, adaptive, and corrective maintenance. Software testing is a process of executing a program or application with the intent of finding the software bugs and verifying that a software program or application meets requirements and operates as intended. Testing may be comprised of testing conducted at the contractor’s facility, Contractor Integration Testing (CIT) at the Government’s facility in a Secret Internet Protocol Router (SIPR) environment, and support for Government Acceptance Testing (GAT), which may consist of one or more of the following test events based on complexity of the change: (System)