NC3 CMIS RFI.pdf

NC3 CMIS - Request for Information (RFI)

Nuclear Command, Control, and Communication (NC3) Classified Maintenance Information System (CMIS)

Request for Information (RFI)

1. Introduction

1.1. The Air Force Life Cycle Management Center (AFLCMC), Program Executive

Office Combat Readiness, Rapid Sustainment Office (RSO) intends to develop a CMIS for Air Force Global Strike Command (AFGSC) initially focusing on a subset of NC3 Weapon System use cases. This capability will specifically address field maintenance of NC3 assets, and will be hosted at Department of Defense (DoD) Information Impact Level 6 (IL-6).

This effort will entail agile development of cloud-hosted software, application programming interface (API) development, cybersecurity activities (such as gaining Authority to Operate at IL-6), training, and demonstrations. The project team is seeking information from innovative solution providers who are capable and interested in participating in this effort.

1.2. The scope of the solution includes the following;

1.2.1. The capabilities of an NC3 CMIS may be developed and fielded iteratively, beginning with a Minimum Viable Product (MVP). The overarching capability areas for an NC3 CMIS are described in Table 1.

The initial scope of capabilities that may constitute an MVP are identified in the “MVP” column in Table 2. All other rows in Table 2 would be required for a fully functional NC3 CMIS and could be developed in subsequent iterations.

Table 1: NC3 CMIS Capability Area Descriptions

Capability Area Description Manage Maintenance Asset

This capability area provides the processes required to manage the inventory, possession/assignment, status, configuration, and utilization of the maintenance assets within the field maintenance information technology system.

Manage Maintenance Requirement

The capability area provides the processes required to establish, maintain, and assign scheduled maintenance requirements (inspections and/or time changes) to maintenance assets. It also provides the processes required to load, change, manage and maintain the status of Time Compliance Technical Orders (TCTOs).

Mission Schedule & Execution

This capability area provides the processes used to build an operational event schedule, record deviations from the operational event schedule, and debrief the operational events executed/attempted.

Maintenance Documentation

This capability area provides the processes to manage maintenance discrepancies, create maintenance discrepancies, record/complete maintenance, manage significant historical documentation, manage maintenance asset digital forms, and manage supply requisitions for maintenance.

Capability Area Description Manage Personnel This capability area provides the processes used to manage organizational structures in the system, manage personnel information, update user certifications/qualifications, and manage user security roles/access.

Manage Security This capability area provides the processes required to establish default data access restrictions/permissions for a base/unit in the system and establishing and maintaining security roles for use within the system.

Trip and Team Tracking

This capability area provides the processes necessary to manage and capture data associated with sending maintenance teams on trips to conduct maintenance at locations away from the teams assigned station.

Table 2: NC3 CMIS “Ability To” Statements

Row # Capability Area Process Title Ability To MVP 1 Maintenance

Documentation Manage Maintenance Discrepancy

Read, Update, Delete discrepancies

2 Maintenance Documentation

Create Scheduled Discrepancy

Create all types of scheduled discrepancies

3 Maintenance Documentation

Create Unscheduled Discrepancy

Create all types of unscheduled discrepancies to match scheduled discrepancies

4 Maintenance Documentation

Record Complete Maintenance

Create, Read, Update, Delete all maintenance actions in accordance with TO 00-20-2

5 Maintenance

Significant Historical Documentation

Create, Read, Update, Delete, archive significant historical data on equipment in accordance with

TO 00-20-1.

6 Maintenance

Digital Forms - Utilities

Create, Read, Update, Delete digital forms

7 Maintenance Documentation

Digital Forms - Entries

Read, Update, Delete digital form entries

8 Maintenance Documentation

Digital Forms - Print Print completed, partial, blank or redacted digital forms

9 Maintenance

Data Integrity Review, Update, Delete system entries for data integrity

10 Maintenance

Supply Requisition Reference supply details corresponding to a discrepancy

11 Maintenance

Reporting Compile and produce reports for presentation and publication

12 Manage Maintenance Asset

Equipment Designator Create, Read, Update, Delete a Equipment Designator master record while allowing loading, inquiry, changing, and removal of the records

13 Manage

Asset

Assignment Read, Update possession purpose, process transfers, gains, losses and terminations of equipment, in accordance with DAF I21-103 & AFI 16-402

14 Manage

Asset

Asset Details Create, Read, Update, Delete equipment details

15 Manage Maintenance Asset

Approved Config Create, Read, Update, Delete configuration rule sets

16 Manage

Maintenance Asset

Configuration Read, Update, Delete equipment configuration management

17 Manage

Asset

Status Create, Read, Update, Delete equipment status at multiple levels of installation hierarchy

18 Manage

Asset

Manage Master Part Number

Create, Read, Update, Delete part numbers and associated product information

19 Manage

Asset

PNSN Details Create, Read, Update, Delete serialized components

20 Manage Maintenance Asset

Multi Equip Asset Location

Read, Update location of asset(s)

21 Manage Maintenance Asset

Multi Equip Utilization

Read, Update utilization of system(s) at all hierarchies

22 Manage

Asset

Actual vs Approved Configuration

Read, Compare, Identify errors for actual and approved configurations in accordance with TO 00-20-2 and DAFI 21-103

23 Manage

Requirement

Scheduled Maintenance Requirement

Create, Read, Update, Delete requirements

24 Manage Maintenance Requirement

Job Package Create, Read, Update, Delete tasks and job packages for established requirements

25 Manage

Requirement

Scheduled Maintenance Requirement On Asset

Create, Read, Update, Delete a maintenance requirement for equipment

26 Manage

Requirement

TCTO One Time Inspection Detail

Create, Read, Update, Delete a Time Critical Technical Order (TCTO) or One Time Inspection

(OTI).

27 Manage

Requirement

TCTO Maintenance Task

Create, Read, Update, Delete task(s) required to accomplish TCTO/OTI

28 Manage

Requirement

TCTO Resources Identify resource requirement and annotate resource status

29 Manage

Requirement

TCTO Assignment Create, Read, Update, Delete a TCTO/OTI to/from a piece of equipment.

30 Manage

Requirement

TCTO Association Create, Read, Update, Delete dependencies between TCTOs/OTIs.

31 Manage Personnel

Organization Create, Read, Update, Delete organizational structures

32 Manage

Personnel Details Create, Read, Update, Delete users for an organization

33 Manage

Certs Quals Create, Read, Update, Delete qualifications and certs to individual users

34 Manage

Personnel Security Create, Read, Update, Delete user security roles

35 Manage Security User Roles Create, Read, Update, Delete position-based roles 36 Manage Security Installation and work center access Create, Read, Update, Delete organizational-level security roles (hierarchical)

37 Manage Security Manage Security - Local Reference Data

Create, Read, Update, Delete reference data globally within the system

38 Mission Schedule & Execution

Manage Operational Event Schedule

Create, Read, Update, Delete an operational event schedule.

39 Mission Schedule & Execution

Debrief Operational Event

Create, Read, Update, Delete the operational event

40 Mission Schedule & Execution

Manage Operational Event Deviation

Create, Read, Update, Delete a deviation for a scheduled operational event

41 Trip and Team Tracking

Manage Maintenance Trip

Create, Read, Update, Delete a trip structure for applicable components by mission type

42 Trip and Team

Manage Trip Equipment

Create, Read, Update, Delete equipment packages by trip type with fulfillment status

43 Trip and Team

Manage Training / Certification Requirements

Create, Read, Update personnel requirements by trip type

44 Trip and Team

Manage Maintenance Trip Details

Read, Update, Delete details associated with trip package for execution

45 Trip and Team

Manage Equipment ID / PNSN Trip Equipment

Read, Update, Delete equipment and part IDs to load lists to a trip package

46 Trip and Team

Manage Trip Status Read, Update trip status details

47 Trip and Team Tracking

Manage Trip Personnel

Read, Update, Delete personnel required for trip package

1.2.2. Ground Rules, Assumptions and Constraints (GRAC)

- The NC3 CMIS software/program will not be classified. Only the data processed and stored by the software will be classified.

- The NC3 CMIS will be deployed to an approved IL-6 environment.

- The NC3 CMIS should not depend on “external” systems for full functionality, either within the deployed IL-6 boundary or beyond.

- The NC3 CMIS should be architected to make data available via modern APIs to the maximum extent possible, although no external interfaces are currently planned.

1.3. THIS IS A REQUEST FOR INFORMATION (RFI) ONLY to understand innovative solutions to accomplish the NC3 mission. This RFI is issued solely for information and planning purposes. It does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. This RFI does not commit the U.S.

Government to contract for any supply or service. Responders are advised the U.S.

Government will not pay for any information or administrative costs incurred in response to this RFI. All costs associated with responding to this RFI will be solely at the respondent party’s expense. Not responding to this RFI does not preclude participation in any future RFP, if issued. The U.S. Government has made no final solicitation decision regarding eventual procurement or by what means such a solicitation, if any, would be handled. The information provided in this RFI is subject to change and is not binding upon the U.S. Government. The U.S. Government has not made a commitment to procure any of the items discussed, and release of this RFI should not be construed as such a commitment or as authorization to incur costs for which reimbursement would be required or sought. All submissions become U.S.

Government property and will not be returned.

2. Requested Information

2.1. Respondents should describe recommended solutions to provide the capabilities detailed in paragraphs 1.1 and 1.2 of this RFI in accordance with the deliverable instructions provided in paragraph 3 “Responses”. Additionally, respondents may attach or reference presentation materials (slide shows, videos) if they are available. Finally, respondents are encouraged to leverage experience from prior contracted efforts and/or Independent Research and Development (IR&D) activities. The following items are required and must be addressed in the response according to the guidance in paragraph 3.2.

2.1.1. Include, at a minimum, a system architecture diagram, a description of the systems and subsystems involved, and/or an evaluation of the feasibility of recommended modifications to existing systems

2.1.2. Provide estimated timelines to develop and deploy to an IL-6 environment the subset of rows in Table 2 that are identified as MVP (last column), as well as an estimated timeline to further develop and deploy to an IL-6 environment the remaining rows in Table 2. Describe risks to the proposed solution or dependencies of the proposed solution.

2.1.3. Provide a Rough Order of Magnitude (ROM) cost estimate to develop and deploy to an IL-6 environment the subset of rows in Table 2 that are identified as MVP (last column), as well as a ROM cost estimate to develop and deploy to an IL-6 environment the remaining rows in Table 2.

2.2. Your responses should further address the topics posed below along with any additional pertinent information deemed appropriate to fully characterize submitted solutions:

2.2.1. Describe your experience in developing and deploying cloud applications (i.e., automated testing, Continuous Integration/Continuous

Deployment (CI/CD) pipelines, sustainment of a production application, etc.).

2.2.2. Describe your experience in obtaining and maintaining an Authority to Operate (ATO) for a cloud hosted application, both as a standalone application and/or with multiple application integrations, continuous monitoring, and Risk Management Framework (RMF) package creation.

2.2.3. Describe your experience utilizing SysML-based Model Based System Engineering (MBSE) tools and practices.

3. Responses

3.1. Interested parties are requested to respond to this RFI with a white paper not to exceed

10 pages using 12-point Times New Roman font. White papers are due no later than 13 JUN 2025, 1400 Eastern Time. Unclassified responses shall be submitted via secure e-mail or secure website to the technical point of contact (TPOC), Corey Shanahan (corey.shanahan@us.af.mil) and the contracting officer, Andrew Gross (andrew.gross.4@us.af.mil). Classified responses will not be accepted.

3.2. Interested parties shall follow the instructions below regarding how to deliver the white paper response package content. RFI responses shall be organized into two separate sections.

3.2.1. Section 1 of the white paper response shall provide administrative information to include the following as a minimum:

3.2.1.1. Company name, mailing address, CAGE code, phone

number, and both name and e-mail of designated point of contact.

3.2.2. Section 2 of the white paper response shall address the recommended approaches to address the problem identified in paragraph 1 of this RFI and provide data as requested in paragraph 2.

3.2.3. Responses should be marked, if applicable, with the appropriate Controlled Unclassified Information (CUI) caveats.

3.3. Proprietary information, if any, MUST BE CLEARLY MARKED. The U. S.

Government shall not be liable for or suffer any consequential damages for any proprietary information not properly identified. Please be advised that all submissions become U. S. Government property and will not be returned. All information received in response to this RFI that is properly marked as “proprietary” will be handled accordingly.

3.4. Respondents are advised that employees under contract with the U.S. Government mailto:corey.shanahan@us.af.mil mailto:andrew.gross.4@us.af.mil may be used to administratively process submissions and provide technical evaluations requiring access to other contractor's proprietary information. These contractors have executed nondisclosure agreements prohibiting their contractor employees from disclosing any information submitted by other respondents/contractors or using such information for any purpose other than that for which it was furnished.

4. Questions and Industry Discussion

4.1. Questions regarding this RFI shall be submitted in writing via e-mail to the TPOC, Corey Shanahan (corey.shanahan@us.af.mil) and contracting officer, Andrew Gross (andrew.gross.4@us.af.mil) Verbal questions will NOT be accepted. Accordingly, questions shall NOT contain proprietary or classified information. The U.S.

Government does not guarantee questions received after 30 MAY 2025, 1400 Eastern Time, will be answered in time for the 13 JUN 2025 white paper submittal deadline.

4.2. If warranted, U.S. Government representatives may consolidate and disseminate general feedback to all respondents after white papers are submitted. Follow-on discussions with individual interested parties may be coordinated. The intent of any such discussions would only be to obtain additional clarification of potential capabilities to meet U.S. Government requirements and further identify risks.

mailto:corey.shanahan@us.af.mil mailto:andrew.gross.4@us.af.mil