SPECIAL NOTICE
99 -- REQUEST FOR INFORMATION (RFI) Transformational Model � Battle Management (TM-BM) Transformational Model � Plan (TM-P)
- Notice Date
- 3/11/2024 11:47:45 AM
- Notice Type
- Special Notice
- Contracting Office
- FA8612 AFLCMC PZP ABMS DAYTON OH 45434-7104 USA
- ZIP Code
- 45434-7104
- Solicitation Number
- RFI-AFLCMC-ABMS-2023-0002
- Response Due
- 6/30/2024 2:00:00 PM
- Archive Date
- 07/15/2024
- Point of Contact
- Chris Core, Phone: 9379044575, Kathleen Rasmussen, Phone: 9372558421
- E-Mail Address
-
christopher.core@us.af.mil, kathleen.rasmussen.2@us.af.mil
(christopher.core@us.af.mil, kathleen.rasmussen.2@us.af.mil)
- Description
- REQUEST FOR INFORMATION (RFI) Transformational Model � Battle Management (TM-BM) Transformational Model � Plan (TM-P) Department of the Air Force (DAF) Advanced Battle Management System Cross Functional Team (ABMS CFT) ***AMENDMENT 1 (11 March 2024)*** Attachment 6 (TM-BM MEF Experiment Report, dated 13 February 2024) has been added. This is a Controlled document (see Attachment 7 (Contractor and Vendor Guide on Controlled Documents) for Vendor instructions on how to access controlled documents.) The Transformational Model Match Effectors report analyzes the result of applying automation to a specific battle management decision domain. This RFI amendment is providing a document for informational purposes ONLY � the government is not requesting any new or additional information at this time. The intent of sharing this information with C2 capability providers is to inform developmental efforts aimed at achieving specific ABMS decision advantage attributes. I. DISCLAIMER THIS NOTICE IS A REQUEST FOR INFORMATION ONLY. This RFI is issued solely for information and planning purposes � it does not constitute as a Request for Proposal (RFP) or a promise to issue an RFP in the future. This RFI does not commit the Government to contract for any supply or service whatsoever. Responses will be treated as information only and will not be evaluated as a proposal. Further, the Government is not at this time seeking proposals and will not accept unsolicited proposals. A return response from the government with regard to RFI submissions is not guaranteed. The RFI respondees are advised that the 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 interested party�s expense. Not responding to this RFI does not preclude participation from future announcements or contracts. Respondents should indicate which portions of their response are propriety and should mark accordingly. NOTE: This RFI is not associated with any previous or ongoing RFPs or Fair Opportunity Proposal Requests issued by the DAF. II. BACKGROUND DoD leadership continues to emphasize the importance of applying modern Systems Engineering principles to capability development, including the use of digital engineering environments and collaborative applications, as well as mission engineering approaches to requirements development. As an element of the Rules-based Approach to Performance Delivery, the ABMS CFT is applying Model-Based Systems Engineering (MBSE) best-practices to develop functional models of C2 concepts using Systems Modeling Language (SysML). The C2 models include the Transformational Model � Battle Management (TM-BM), Transformational Model � Plan (TM-P), and Transformational Model - Command (TM-C).� These models provide functional requirements for achieving Decision Advantage with the PEO C3BM led DAF Battle Network, which is the DAF�s contribution to Combined Joint All-Domain Command and Control (CJADC2). III. SPECIFIC INFORMATION OF INTEREST A. Problem Statement: Effective synchronization of CJADC2 capability development across nations, departments, and services, requires a common mental model of complex concepts. Battle Management is one such concept that is often subject to conflations and divergent perceptions. In Department of Defense Architecture Framework (DoDAF) artifacts, activity models, and swim-lane diagrams, Battle Management functions are often opaque activities with little if any internally defined structure, or they represent bespoke processes that are unscalable. The TMs aim to illuminate the enduring and all-domain nature of Battle Management, Plan, & Command (the C2 Decision Function domains) by establishing precise boundaries, i.e., distinguishing C2 from other related and adjacent decision-making concepts, and by defining them through decomposition into functions and subfunctions. To do the work necessary for achieving the goals of CJADC2, this model must be able to: 1. Provide an unambiguous, quantitative, and robust definition and conceptual description of Battle Management, Plan, and Command for all stake holders to share and work from. That conceptual description must provide insight on the ability to distribute and/or federate Battle Management functions to achieve effectiveness, resilience, capacity, and efficiency. 2. Provide a means to categorize and evaluate systems (materiel and non-materiel) and system elements in terms of their performance of specific C2 functions. 3. Convey robust, traceable, quantitative requirements for Battle Management, Plan, and Command functions and supporting architectures (i.e., materiel and non-materiel systems-of-systems solutions) and provide quantitative measures of performance of these functions within a common contextual (or �pacing�) scenario.� The pacing scenario is a set of vignettes based on Joint Mission Threads (JMTs) identified by warfighting commands, and is being developed in collaboration with Joint and Mission Partners.� The TM-BM/P/C must provide a quantitative means to compare different architectures and their performance of Decision Functions within that contextual scenario. In partnership with the Department of the Navy and our Allied Partners, the DAF ABMS CFT seeks to understand and improve the ability of the model to accomplish the above with inputs from Industry Partners.� This RFI represents an opportunity to incorporate the voices of developers in the MBSE foundation that will generate the requirements for CJADC2 solutions.� As such, the DAF ABMS CFT requests responses to the questions below based on the artifacts attached to this RFI, which are: Attachment 1: Read-Me file with instructions for the other attachments Attachment 2: Transformational Model Methodology Core Concepts Paper Attachment 3:� TM-BM & TM-P MagicDraw/Cameo (zip) Attachment 4:� TM-BM & TM-P HTML (zip) Attachment 5:� TM-BM & TM-P Images (pdf) Please note, the model is still in development, and therefore the artifacts represent draft products. �As more elements of the TM are completed, they will also be released.� Your feedback will inform the subsequent version releases. B. Request for Information: The DAF ABMS CFT seeks feedback on the MBSE functional model titled, �Transformational Model � Battle Management� and �Transformational Model � Plan.� (See the attachments to this RFI.) Please consider the following questions, and provide succinct responses along with any other questions, suggestions, and/or feedback (positive or negative) you have for the TM-BM/TM-P format, design, and/or the draft content. 1.� Does the TM-BM/TM-P provide a unifying mental model of Battle Management & Planning for Joint and Combined military operations?� With the artifacts provided, what insight do the TM-BM & TM-P provide about the potential for distribution and/or federation of some or all of the functions / subfunctions?� 2.� Can you assess how the TM-BM & TM-P can be used for micro-service and application development in the near term? 3.� If the TM-BM & TM-P were included with specific system and technical requirements, could you use the TM-BM & TM-P to understand the high-level functional requirements for the system and technical requirements, i.e., the �purpose� of system elements and components? � � � � a. Do you assess any positive or negative consequences for using the model as part of requirements documentation? � � � � b. Do the TM-BM/TM-P effectively covey Information Exchange Requirements (IERs) that can be aggregated for connectivity, computation, and data storage requirements? 4. Please provide any other questions, suggestions, and/or feedback you have, including: � � � � c. How did you view the TM-BM/TM-P artifacts (.mdzip file, html file, or pdf)? � � � � d. Did you find it easy or difficult to find and view information in the model? � � � � e. Have you attended or listened to any of the briefings or narratives about the TM-BM/TM-P prior to reviewing the model artifacts?� If so, did the briefing / narrative have an impact on your understanding of the model artifacts? � � � � f. Please list any additional questions you have about the TM-BM/TM-P. � � � � g. Please provide any additional suggestions and feedback you have for the TM-BM/TM-P. IV. SUBMISSION INSTRUCTIONS and FORMATTING REQUIREMENTS A.�Due Date: Responses are requested by 31 Oct 2023. B. Response Content and Format: In order for our small team to effectively process responses, answer content limited to approximately 5 pages will be greatly appreciated.� Response formats may be pdf, Excel, and/or Word and structured as follows: � � � � 1. COVER SHEET to include the following company information not to exceed 1 page. Company Name, CAGE Number (if applicable), Address, Point of Contact E-Mail Address, Phone, Company Web Page URL. State whether your company is a small business such as 8(a), small disadvantaged business, woman-owned business, HUBZone small business, Veteran-owned business, or service disabled veteran owned business. Also include a statement as to whether your company is domestically or foreign owned (if foreign, please indicate the country of ownership). � � � � 2. RESPONSES TO QUESTIONS as given in section III B (up to ~ 5 pages of response content). �Please organize your responses with the designation of individual questions (for example, �2.c. We can use the TM-BM to identify modules within Application X that appear to match the descriptions of certain subfunctions, however, the degree to which they match is��).� Respondents are not required to answer all questions, although a succinct, plain language response to each question will be greatly appreciated. V. POINT OF CONTACT Non-Government advisors may be used in the evaluation of responses and have signed non- disclosure agreements (NDAs) with the Government. Additional NDAs will not be required; instead, a response to this RFI will be considered an implicit acknowledgement and acceptance of the fact that non-Government advisors will be assisting the Government in this process. The Government understands that information provided in response to this RFI is presented in confidence and may contain trade secret, commercial or financial information, and it agrees to protect such information from unauthorized disclosure to the maximum extent permitted or required by- 18 USC 1905 (Trade Secrets Act); 18 USC 1831 et seq. (Economic Espionage Act); 5 USC 552(b)(4) (Freedom of Information Act); Executive Order 12600 (Pre-disclosure Notification Procedures for Confidential Commercial Information); and Any other statute, regulation, or requirement applicable to Government employees. RFI responses should be submitted electronically, via the appropriate communication channels (email preferred or a DoD SAFE link can be provided): Primary:��������������������������������������������������������������������� Alternate: Maj Jacob Thomas����������������������������������������������������� Maj Timothy Wintch jacob.thomas.11@us.af.mil� � � � � � � � � � � � � � � � � �timothy.wintch@us.af.mil Electronic submissions are highly preferred. In the event electronic submission is not possible, please contact the primary point of contact above for address information. Companies are encouraged to keep all elements of the response unclassified. In the case where a respondent has a need to submit a classified appendix, such material shall not be transmitted across open-source media like public phone, fax, internet, or e-mail. If a respondent has any reason to believe their concept / capabilities may reference ideas or operations that require special protection, please contact the primary point of contact.
- Web Link
-
SAM.gov Permalink
(https://sam.gov/opp/5e549f334fca4548bfde8f6317944943/view)
- Record
- SN06992156-F 20240313/240311230038 (samdaily.us)
- Source
-
SAM.gov Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's SAM Daily Index Page |