AI RFI Response Form 02172026.xlsx
XLSX spreadsheet 33 KB Posted
- Solicitation number
- FA8688-RFI-26-0001
About this file
This is a Request for Information (RFI) Response Form for the Air Force Materiel Command's market research on artificial intelligence tools to accelerate aircraft acquisition activities. The RFI, numbered FA8688-RFI-26-0001, is issued by the Air Force Life Cycle Management Center/Mobility Aircraft Directorate (AFLCMC/WL) and seeks vendor capability information on Commercial Off-the-Shelf (COTS) and Government Off-the-Shelf (GOTS) AI tools with Technology Readiness Levels (TRL) of 7-9 and Impact Level (IL) 5/6 certification or scheduled certification timelines. The submission deadline is 20 March 2026. The form captures vendor information including company details, points of contact, existing federal contract vehicle availability, and Platform One/Department of Defense (DoD) experience.
The response form is structured in four sections covering vendor information, scenario-based capability responses across three acquisition lifecycle phases, and pricing details. Section 1 requests tool specifications including cybersecurity certifications (CMMC and FedRAMP levels), secure development environment support, and general product descriptions. Sections 2 and 3 address Phase I (Requirements Definition through Contract Award) and Phase II (Procurement through Fielding) respectively, requiring vendors to describe supported activities, functional areas, AI tool types, input/output data formats, Government Purpose Rights (GPR) confirmation, workflow integration, performance metrics, trustworthiness alignment with NIST AI RMF standards, expected outcomes, and case studies. Phase III covers Product Support/Sustainment with similar requirements. Section 4 requests pricing information using formats such as enterprise licenses, per-user licenses, per-transaction models, or subscriptions, along with rough order of magnitude cost estimates. Vendors may provide supporting cost models in Excel, PDF, or proprietary formats and should attach relevant documentation demonstrating tool effectiveness across the acquisition lifecycle.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| AI Tools to Accelerate Acquisition RFI 02172026.docx | DOCX document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
RFI Ingest Form
| TITLE: Current and Emerging Artificial Intelligence (AI) Tools to Accelerate Air Force Mobility Aircraft Acquisition Activities RFI Response Form |
| RFI Submission Instructions: |
• Please keep each response concise (max 2000 characters per field).
• Use dropdowns and checkboxes where provided.
• Attach supporting documents as needed.
• Submit completed form by 20 March 2026.
| RFI Line Reference # | Section | Prompt | Response | |
| 1 | Section 1: Vendor Information | |||
| 2 | Company Name: | |||
| 3 | Company Website Address: | |||
| 4 | Point of Contact Name: | |||
| 5 | Point of Contact Email: | |||
| 6 | Is this tool currently available for purchase through an existing federal contract vehicle (e.g., GSA Schedule)? | YES/NO/Not Applicable | (Optional) If yes, please provide contract(s) information here. | |
| 7 | Company DoW PlatformOne Experience? If yes, describe (max 2000 characters): | |||
| 8 | Tool/Product Name: | |||
| 9 | Tool URL: | |||
| 10 | Tool Technology Readiness Level (TRL): | |||
| 11 | Tool Cybersecurity Maturity Model Certification (CMMC) Level (e.g., Level 2) | |||
| 12 | Tool FedRAMP designation (Authorized, Ready, In-Process, None): | |||
| 13 | FedRAMP Future Implementation. If none, do you have a plan to secure FedRAMP designation? (Y/N) | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 14 | Tool DoW Impact Level (IL) Certification Level (e.g., IL5/6): | |||
| 15 | IL 5/6 Future Implementation. If your tool is not currently IL5/6, do you have a plan to secure those certifications level(s)? (Y/N) | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 16 | If yes, anticipated release date: | |||
| 17 | Tool Secure / “Locker” Development Environment(s). Explain how tool supports secure, isolated development environments (“lockers”) for controlled feature development, testing, and promotion of artifacts (max 2000 characters): | |||
| 18 | Tool/Product Description (max 2000 characters): | |||
| 19 | Automation and User Involvement. Explain how the tool distributes work between automated functions and human users (i.e., tasks performed automatically versus tasks that require user input, and how users interact with the tool). (Max 2000 characters): | |||
| 20 | Trial License Available (if yes, indicate duration): | YES/NO/Not Applicable | (Optional) Insert duration here. | |
| 21 | Section 2: Scenario-Based AI Tool Capability Response | |||
| 22 | Instructions: Limit each response to 2000 characters or less. Attach supporting documents if needed. Concise responses are acceptable, and vendors do not need to provide exhaustive documentation. Responses do not require proprietary or sensitive information. |
Many tools only support one or two phases of the acquisition lifecycle, while others support all three in different ways. The question sets for Phases I–III are intentionally similar and may appear repetitive. This is by design. Please respond only for the phases where your tool is applicable, and answer the questions from the perspective of how the tool is used in that phase.
| 23 | Phase I: Requirements Definition through Contract Award | |||
| 24 | 1. Supported Activities (dropdown menu yes/no/N/A) | |||
| 25 | • Operational Need Validation | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 26 | • Requirements Analysis | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 27 | • Stakeholder Engagement | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 28 | • Market Research/Technology Assessment | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 29 | • Risk Assessment | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 30 | • Acquisition Strategy Development | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 31 | • Solicitation Development | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 32 | • Proposal Evaluation | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 33 | • Source Selection evaluation and Award | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 34 | • Other (max 2000 characters): | |||
| 35 | 2. Functional Area (yes/no) | |||
| 36 | • Requirements/Capability Development | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 37 | • Program Management | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 38 | • Contracting | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 39 | • Financial Management/Cost Estimating/Budget Estimation/Auditing | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 40 | • Life Cycle Logistics/Product Support Management (PSM) | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 41 | • Engineering/Model Based Systems Engineering (MBSE)/Technical Management | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 42 | • Test & Evaluation | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 43 | • Security/Counterintelligence | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 44 | • Legal/Compliance | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 45 | 3. Potential AI Tool Type (yes/no) | |||
| 46 | • Workflow Automation | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 47 | • Document Management | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 48 | • Modeling/Simulation | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 49 | • Analytics | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 50 | • Decision Support | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 51 | • Other (max 2000 characters): | |||
| 52 | 4. Required Input (Data and Format) | |||
| 53 | Instructions: Briefly describe the types of data and file formats your tool requires to operate (e.g., SysML models, PDF requirements, UON documents). (max 2000 characters) | |||
| 54 | 5. Produced Output (Data and Format) | |||
| 55 | Instructions: Briefly describe the types of data and file formats your tool produces or delivers (e.g., requirements document in PDF, RFP in Word). (max 2000 characters) | |||
| 56 | 6. Government Purpose Rights (GPR) Confirmation and Proprietary Limitations | |||
| 57 | Instructions: Indicate whether outputs produced by your tool are provided with Government Purpose Rights (GPR) at a minimum. Discuss proprietary aspects and limitations on data rights. | |||
| 58 | • Yes, all outputs provided with GPR | YES/NO/Not Applicable | ||
| 59 | • No (please explain proprietary aspects and limitations on data rights): (max 2000 characters) | |||
| 60 | 7. Hosting Options and Information Boundaries | |||
| 61 | Instructions: Briefly describe the components of the tool and where they are hosted. For example, is the solution a SaaS solution hosted on AWS Gov. (max 2000 characters) | |||
| 62 | 8. Workflow/Integration | |||
| 63 | Instructions: Briefly describe how your tool integrates with other systems or processes, including compatibility with existing workflows and any next-step handoff capabilities. Support your description with specific examples of open architecture capabilities and API strategies. (max 2000 characters) | |||
| 64 | 9. Approach and Performance | |||
| 65 | Instructions: Briefly describe the analytics and algorithms used by your tool and describe the performance. Clearly state the quantitative and qualitative measures used to characterize tool performance and how well the tool performs on these measures. (max 2000 characters) | |||
| 66 | 10. Trustworthiness | |||
| 67 | Instructions: Below is a graphic depicting the NIST AI RMF 100-1 Characteristics of Trustworthy AI Systems. If the tool contains AI components, briefly describe overall alignment to these characteristics. Additionally, elaborate tool alignment with the Explainable & Interpretable and Fair – With Harmful Bias Managed characteristics. Explain how users can understand or interpret the outputs of your model (e.g., what information is provided to show how decisions are made, what transparency tools or documentation are available, and how users can trace or audit model results). If you do not have the bandwidth to provide a detailed explanation, please provide a URL to documentation or resources that describe your tool’s explainability features, and the government will review them. (max 2000 characters) | |||
| 68 | 11. Expected Outcomes/Benefits | |||
| 69 | Instructions: Briefly describe the measurable improvements your tool delivers, such as increased speed, improved accuracy, risk reduction, or other quantifiable benefits. (max 2000 characters) | |||
| 70 | 12. Relevant Example/Case Study | |||
| 71 | Instructions: Provide a summary of a relevant example or case study demonstrating your tool’s effectiveness. (max 2000 characters) You may also attach a supporting document if available. | |||
| 72 | Phase II: Procurement (Contract Execution) through Fielding | |||
| 73 | 1. Supported Activities (Select all that apply) | |||
| 74 | • Contract Management (formal Service Level Agreement (SLA) with infrastructure provider for service scope and Authority to Operate/Authority to Connect (ATO/ATC) inheritance) | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 75 | • System Integration (Cloud Native Computing Foundation (CNCF)-certified Kubernetes/service mesh; artifact repository usage; DoW Centralized Artifact Repository (DCAR) hardened containers) | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 76 | • Financial performance assessments (track cost/benefit and ROI improvements from automation and issue tracking) | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 77 | • Assessing development and developer maturity (DevSecOps Maturity Model assessment per DoW DevSecOps Playbook) | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 78 | • Testing/Evaluation (unit, integration, system, performance, acceptance tests; Static Application Security Test (SAST)/Dynamic AST (DAST)/Interactive ASTIAST; compliance scans) | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 79 | • Training Development and Delivery (team onboarding; DevSecOps concepts/tools; secure coding practices) | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 80 | • Fielding/Deployment (CI/CD automation; post-deployment checkout/smoke tests; rolling update/rollback; security scans; IaC/SaC configuration automation) | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 81 | • Configuration Management (Configuration Management Database (CMDB); Git/versioning; artifact tagging; checksums and digital signatures) | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 82 | • Quality Assurance (test coverage measurement and reporting) | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 83 | • Data Management (data masking; encryption at rest and in transit) | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 84 | • Schedule Management (project tasking and release planning/scheduling) | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 85 | • Risk Management (vulnerability management; dependency/Bill of Material (BOM) checks; Information Security Continuous Monitoring planning) | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 86 | • Supplier/Vendor Coordination (use Cloud Service Provider (CSP) DevSecOps services and DCAR; plan authorization inheritance via SLA) | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 87 | System Performance Verification (logging/telemetry pipeline; operations dashboard readiness) | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 88 | • Other (max 2000 characters): | |||
| 89 | 2. Functional Category (yes/no) | |||
| 90 | • Requirements/Capability Development | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 91 | • Program Management | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 92 | • Contracting | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 93 | • Cost/Budget Estimation | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 94 | • Logistics/Product Support Management (PSM) | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 95 | • Engineering/Model Based Systems Engineering (MBSE) | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 96 | • Test & Evaluation | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 97 | • Security/Counterintelligence | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 98 | • Legal/Compliance | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 99 | 3. Potential AI/DE Tool Type (yes/no) | |||
| 100 | • Workflow Automation | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 101 | • Document Management | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 102 | • Modeling/Simulation | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 103 | • Analytics | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 104 | • Decision Support | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 105 | • Other (max 2000 characters): | |||
| 106 | 4. Required Input (Data and Format) | |||
| 107 | Instructions: Briefly describe the types of data and file formats your tool requires to operate (e.g., test plans in PDF, integration requirements in Excel, training materials in Word). | |||
| 108 | 5. Produced Output (Data and Format) | |||
| 109 | Instructions: Briefly describe the types of data and file formats your tool produces or delivers (e.g., test reports in PDF, training completion certificates in Word, fielding status dashboards). | |||
| 110 | 6. Government Purpose Rights (GPR) Confirmation | |||
| 111 | Instructions: Indicate whether all outputs generated by your tool are provided with Government Purpose Rights (GPR) at a minimum. If not, please explain any limitations or exceptions. | |||
| 112 | • Yes, all outputs provided with GPR (at a minimum) | YES/NO/Not Applicable | ||
| 113 | • No (please explain) (max 2000 characters): | |||
| 114 | 7. Workflow/Integration | |||
| 115 | Instructions: Briefly describe how your tool integrates with other systems or processes, including compatibility with existing workflows and any next-step handoff capabilities. (max 2000 characters) | |||
| 116 | 8. Analytics/Algorithms Description | |||
| 117 | Instructions: Briefly describe the analytics and algorithms used by your tool, including any bias mitigation strategies and explainability features. Specifically, explain how users can understand or interpret the outputs of your model (e.g., what information is provided to show how decisions are made, what transparency tools or documentation are available, and how users can trace or audit model results). If you do not have the bandwidth to provide a detailed explanation, please provide a URL to documentation or resources that describe your tool’s explainability features, and the government will review them. (max 2000 characters) | |||
| 118 | 9. Expected Outcomes/Benefits | |||
| 119 | Instructions: Briefly describe the measurable improvements your tool delivers, such as increased speed, improved accuracy, risk reduction, or other quantifiable benefits. (max 2000 characters) | |||
| 120 | 10. Relevant Example/Case Study | |||
| 121 | Instructions: Provide a summary of a relevant example or case study demonstrating your tool’s effectiveness. (max 2000 characters) You may also attach a supporting document if available. | |||
| 122 | 11. Data Rights Limitations/Vendor Lock Prevention | |||
| 123 | Instructions: Briefly describe how your solution prevents vendor lock-in and any limitations on data rights associated with your tool. (max 2000 characters) | |||
| 124 | Phase III: Product Support/Sustainment | |||
| 125 | 1. Supported Activities (yes/no) | |||
| 126 | • Product Support/Sustainment planning and governance (hardware product support plans; software SAP/DevSecOps model) | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 127 | • Maintenance and updates (hardware preventive/corrective repair; software patches/releases) | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 128 | • Performance monitoring and observability (hardware health/telemetry; software logs/metrics/traces, Service Level Objectives (SLO)) | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 129 | • Cybersecurity and RMF/ATO (hardware STIG/vulnerability management; software continuous monitoring/cATO) | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 130 | • Configuration, interfaces, and change control (hardware baselines/interface control; software Git/versioning, API/schema management) | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 131 | • Reliability, availability, and resilience (hardware Reliability and Maintainability (R&M) analysis; software failover/rollback, Recovery Time Objective (RTO)/Recovery Point Objective (RPO)) | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 132 | • Obsolescence and refresh (hardware End of Life (EoL)/tech insertion; software Operating System (OS)/framework/library EoL) | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 133 | • Supply chain and asset management (hardware spares/inventory hardware BOM; software BOM (SBOM) and license management) | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 134 | • Environment and platform operations (hardware support equipment/facilities; software cloud/containers, Infrastructure as Code (IaC)) | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 135 | • Release, deployment, and operations management (hardware fielding kits/Technical Orders (TO); software CI/CD, staged rollouts, incident/change) | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 136 | • Feedback, metrics, and continuous improvement (hardware user/maintainer feedback; software telemetry, DevOps Research and Assessment (DORA)/ Mean-Time to Recovery (MTTR), retrospectives) | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 137 | • Documentation and training (hardware tech manuals and operator/maintainer training; software runbooks, release notes, Application Programming Interface (API) docs) | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 138 | • Risk management (hardware technical/cyber/supply chain/obsolescence/capacity; software vulnerabilities, supply chain/SBOM risk, technical debt) | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 139 | • Other (max 2000 characters): | |||
| 140 | 2. Functional Category (yes/no) | |||
| 141 | • Program Management | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 142 | • Logistics/Product Support Management (PSM) | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 143 | • Engineering/Model Based Systems Engineering (MBSE) | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 144 | • Test & Evaluation | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 145 | • Security/Counterintelligence | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 146 | • Data Analytics | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 147 | • Maintenance | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 148 | • Quality Assurance | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 149 | • Legal/Compliance | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 150 | 3. Potential AI/DE Tool Type (yes/no) | |||
| 151 | • Workflow Automation | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 152 | • Document Management | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 153 | • Modeling/Simulation | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 154 | • Analytics | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 155 | • Decision Support | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 156 | • Other (max 2000 characters): | |||
| 157 | 4. Required Input (Data and Format) | |||
| 158 | Instructions: Briefly describe the types of data and file formats your tool requires to operate (e.g., maintenance logs in Excel, performance data in CSV, feedback forms in PDF). (max 2000 characters) | |||
| 159 | 5. Produced Output (Data and Format) | |||
| 160 | Instructions: Briefly describe the types of data and file formats your tool produces or delivers (e.g., performance dashboards, maintenance schedules, cybersecurity assessment reports). (max 2000 characters) | |||
| 161 | 6. Government Purpose Rights (GPR) Confirmation | |||
| 162 | Instructions: Indicate whether all outputs generated by your tool are provided with Government Purpose Rights (GPR). If not, please explain any limitations or exceptions. | |||
| 163 | • Yes, all outputs provided with GPR | YES/NO/Not Applicable | ||
| 164 | • No (please explain): (max 2000 characters) | |||
| 165 | 7. Workflow/Integration | |||
| 166 | Instructions: Briefly describe how your tool integrates with other systems or processes, including compatibility with existing workflows and any next-step handoff capabilities. (max 2000 characters) | |||
| 167 | 8. Analytics/Algorithms Description | |||
| 168 | Instructions: Briefly describe the analytics and algorithms used by your tool, including any bias mitigation strategies and explainability features. Specifically, explain how users can understand or interpret the outputs of your model (e.g., what information is provided to show how decisions are made, what transparency tools or documentation are available, and how users can trace or audit model results). If you do not have the bandwidth to provide a detailed explanation, please provide a URL to documentation or resources that describe your tool’s explainability features, and the government will review them. (max 2000 characters) | |||
| 169 | 9. Expected Outcomes/Benefits | |||
| 170 | Instructions: Briefly describe the measurable improvements your tool delivers, such as increased speed, improved accuracy, risk reduction, or other quantifiable benefits. (max 2000 characters) | |||
| 171 | 10. Relevant Example/Case Study | |||
| 172 | Instructions: Provide a summary of a relevant example or case study demonstrating your tool’s effectiveness. (max 2000 characters) You may also attach a supporting document if available. | |||
| 173 | 11. Data Rights Limitations/Vendor Lock Prevention | |||
| 174 | Instructions: Briefly describe how your solution prevents vendor lock-in and any limitations on data rights associated with your tool. (max 2000 characters) | |||
| 175 | Section 3: Pricing | |||
| 176 | Instructions: please provide a summary of your pricing approach, a rough order of magnitude cost estimate for your overall solution, and the format of your cost model. Attach a sample cost model document if available. | |||
| 177 | a. Pricing Approach (yes/no) | |||
| 178 | • Enterprise License | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 179 | • Per User License | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 180 | • Per Transaction/Usage | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 181 | • Subscription | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 182 | • Other (max 2000 characters): | |||
| 183 | b. Rough Order of Magnitude (ROM) Cost Estimate | |||
| 184 | Provide a summary of estimated costs for deployment and sustainment. Include assumptions or variables that may affect cost. | |||
| 185 | c. Cost Model Format (yes/no) | |||
| 186 | • Excel | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 187 | YES/NO/Not Applicable | (Optional) Insert elaboration here. | ||
| 188 | • Proprietary Tool | YES/NO/Not Applicable | (Optional) Insert elaboration here. | |
| 189 | • Other (max 2000 characters): | |||
| 190 | d. Attach Cost Model Document | |||
| 191 | (Optional: Insert supporting cost model file name) | |||
| 192 | Section 4: Additional Comments or Attachments | |||
| 193 | Instructions: Briefly describe the types of data and file formats your tool requires to operate (e.g., SysML models, PDF requirements, UON documents). (max 2000 characters) | |||
| 194 |
https://aida.mitre.org/wp-content/uploads/2025/08/TMaF_TRL_with_OE-I_Critical_Activities.pdfhttps://www.acquisition.gov/dfars/252.204-7025-notice-cybersecurity-maturity-model-certification-level-requirements.https://cic.gsa.gov/basics/cloud-securityhttps://www.fedramp.gov/ (backup) Dropdown Menu Options
| YES |
| NO |
| Not Applicable |
| YES/NO/Not Applicable |
File details come from the government source that posted it. Updated .