Attachment 6_Closed Call AoI_Data Repository and Dashboard.pdf

Closed Area of Interest (AoI) for SPEED CSO

1.0 Issued By

Program Office: Air Force Civil Engineer Center (AFCEC) Contracting Office: 772nd Enterprise Sourcing Squadron

2.0 AOI Identifiers

AOI Title: AFCEC Enterprise-Wide Contracting Data Repository and Dashboard CSO AOI Number: Closed – 26 – 06. POC: Mr. Charles Kelm AOI Release Date: 03/13/2026 Responses: See FA890326SC001 for submission instructions in addition to paragraph 5.0 below

3.0 AOI Information and Background

This Area of Interest is soliciting for a proposed solution to develop and implement a centralized data repository and corresponding dashboards. The purpose of this system is to consolidate all pre- and post-award contracting information from every Air Force Civil Engineer Center (AFCEC) directorate and branch.

With AFCEC managing approximately 12,000 to 14,000 contracts/orders, critical contracting data is currently housed in disparate systems and platforms across the organization, which creates significant challenges in data aggregation, enterprise-wide visibility, and strategic decision-making. The proposed solution will establish a single, authoritative source for all contracting data, thereby enhancing operational efficiency and providing leadership with the critical insights needed for the effective management of AFCEC resources.

AFCEC requires a comprehensive and unified view of its contracting activities across its seven directorates:

• Business Information Systems & Mission Support (CB)

• Facility Engineering (CF)

• Installations (CI)

• Air Force Office of Energy Assurance (AF OEA/CN)

• Operations (CO)

• Readiness (CX)

• Environmental Management (CZ)

AFCEC’s current decentralized approach to data management—with each directorate utilizing its own database, SharePoint Site(s), or other platforms—creates significant operational inefficiencies. This data fragmentation hinders the ability to perform enterprise-level analysis, track project status effectively, and ensure data consistency. A significant portion of historical and current data is locked within static PDF documents across these internal databases, making manual extraction impractical at scale.

To address these challenges, the proposed repository will capture and consolidate key data for each AFCEC project, contract, or order. The data points should include, but are not limited to, the following:

• AFCEC Directorate/Branch

• Project Title and Description

• Current Contract Number (for follow-on actions)

• Anticipated Dollar Value

• Contract Period of Performance

• OCC, PSC, and NAICS codes

• Anticipated Set-Aside Decision

• Contract Vehicle (e.g., Task/Delivery Orders)

• Anticipated Solicitation Date

• Anticipated Award Date

The system shall feature a suite of dashboards to provide intuitive and customizable visualizations of this data, enabling an at-a-glance understanding of the AFCEC contracting landscape.

AFCEC is not obligated to extend a request for proposal or make an award as a result of posting this AOI; all awards are subject to the availability of funds and successful negotiations.

This CSO AOI is not an authorization to begin performance, and in no way obligates the Government for any costs incurred by the Offeror associated with developing a Response.

Prior to commencement of any activities associated with performance under this CSO AOI, the Government will issue a written directive or contractual document signed by the Contracting Officer with appropriate consideration established. ACC-RRAD reserves the right to modify the requirements of this CSO AOI.

The authority to issue this AOI is derived from the AFIMSC SPEED Commercial Solutions Opening FA890326SC001, dated 21 JAN 2026. The CSO authority is Section 803 of the National Defense Authorization Act for FY2022, Public Law 117-807, and Class Deviation 2022-O0007.

3.1 AI-Powered Data Integration

A critical component of this solution will be the integration with existing AFCEC data sources. The Offeror must propose an Artificial Intelligence (AI) solution capable of mining data directly from PDF documents stored within each directorate's internal database or SharePoint environment. This AI-driven process will be essential for extracting the required data points from unstructured files, minimizing manual data entry, and ensuring the timeliness and completeness of the data ingested into the central repository.

3.2 Data Validation and Integrity

To ensure the highest level of data accuracy, the system will incorporate a robust checks-and-balances mechanism. This process will validate the repository's data against external, authoritative sources. The system will be designed to interface with and cross-reference data from other authoritative government contracting systems—such as the Federal Procurement Data System (FPDS-NG), USAspending.gov, and the System for Award Management (SAM.gov)—to confirm the accuracy and completeness of the captured information.

4.0 Scope of AOI

AFCEC is seeking a phased approach to the development and deployment of the AFCEC Enterprise-Wide Contracting Data Repository and Dashboard.

4.1 Phase 1: Discovery and Planning

In this initial phase, the Offeror will work closely with the designated Points of Contact (POCs) from each of the seven AFCEC directorates. The Offeror will conduct a thorough analysis of AFCEC’s existing data structures, platforms, and business processes. This will involve mapping their current data fields to the required fields for the new repository and identify any gaps.

4.2 Phase 2: Development and Integration

Based on the findings from the discovery phase, the Offeror will design and build the central repository and the associated dashboards. The Offeror will then work to establish secure and reliable connections to each directorate’s data source. For directorates with missing or incomplete data, the Offeror will collaborate with AFCEC to establish and implement processes to ensure the necessary data is captured, either through manual entry or automated population.

4.3 Phase 3: Deployment and Training

Once the system is fully developed and tested, the Offeror deploy it to the AFCEC enterprise.

The Offeror will provide comprehensive training to all 38 (thirty-eight) AFCEC divisions to ensure they are able to effectively utilize the new repository and dashboards.

5.0 Purpose and Objectives of AOI

The overall purpose of this effort is for an Offeror to design, develop, deploy, and sustain a comprehensive, enterprise-wide contracting data repository and visualization capability for AFCEC. The solution shall provide a single, authoritative source of truth for all pre- and post-award contracting data across AFCEC's seven directorates, enabling enhanced data accuracy, operational efficiency, and strategic decision-making.

The Offeror shall achieve the following key objectives:

5.1 Objective 1 Conduct Comprehensive Discovery, Analysis, and Solution Design

The Offeror shall perform a thorough analysis of the existing AFCEC data environment to inform the design of the new solution. At the conclusion of this objective, AFCEC shall have a complete understanding of the current data landscape and a detailed architectural design for the proposed solution. Key outcomes include:

• A comprehensive analysis of the data structures, platforms, and business processes currently in use across all seven AFCEC directorates.

• A detailed data mapping plan that identifies the sources for all required data points listed in Section 3.0 and identifies any data gaps.

• A complete and finalized System Design Document (SDD) for the proposed repository and dashboards, including the technical architecture, data model, and integration strategy.

5.2 Objective 2 Develop and Integrate a Centralized Repository and Dashboards

The Offeror shall build and deliver a fully functional, secure, and scalable data solution based on the approved system design. At the conclusion of this objective, AFCEC shall have an operational system that automatically consolidates and visualizes its enterprise contracting data. Key outcomes include:

• A secure, centralized data repository that captures all required data points.

• Automated data integration pipelines that reliably extract data from the various directorate sources (e.g., SharePoint, AFCEC Internal databases) into the central repository.

• A robust data validation mechanism that automatically cross-references and validates repository data against external authoritative systems (FPDS-NG, SAM.gov, etc.).

• A suite of interactive and customizable dashboards that provide intuitive visualizations of the contracting data for leadership and program managers.

5.3 Objective 3: Deploy the Solution and Provide Comprehensive Training

The Offeror shall successfully deploy the solution to the AFCEC enterprise and ensure all users are equipped to utilize it effectively. At the conclusion of this objective, the system shall be fully deployed and AFCEC personnel shall be proficient in its use. Key outcomes include:

• Successful deployment of the production system into the required government-approved environment.

• Development and delivery of comprehensive training materials (e.g., user guides, quick reference guides, computer-based training modules).

• Execution of a training plan for all 38 AFCEC divisions, ensuring all relevant personnel are trained on the use of the repository and dashboards.

• Delivery of complete system and administrative documentation to allow for government sustainment, if required.

5.4 Objective 4 Provide Ongoing Sustainment and Enhancement

(Optional/Post-Deployment)

The Offeror shall provide the necessary technical support and system sustainment to ensure the long-term operational viability and effectiveness of the solution. Key outcomes include:

Ongoing operational support, including system monitoring, maintenance, and help-desk support.

Implementation of bug fixes, security patches, and system updates as required.

Execution of enhancements and new feature development as prioritized by AFCEC leadership.

6.0 Governance and Technical Requirements

6.1 AFCEC Enterprise Governance Framework

The Offeror shall develop, deliver, and sustain the system in accordance with the overarching A4 Governance Landscape and AFCEC's enterprise capability development process. The Offeror acknowledges that all system change requests, innovations, data/analytics efforts, and modifications to Information Technology (IT) or Operational Technology (OT) fall under this governance structure.

6.1.1 Capability Request Submission and Analysis

All proposals, including responses to a government Area of Interest (AOI), shall be treated as a Capability Request (CR). The government will initiate the CR within its designated portal, using the Offeror's proposal as the basis for the submission.

6.1.1.1 Proposal Content Requirements

To facilitate the CR process and proactively address governance concerns, the Offeror's proposal must provide the detailed information outlined below. A proposal may be deemed non-responsive if this information is not provided.

Category Details Required

Business Case

A comprehensive Business Case Analysis (BCA) and a clear Return on Investment (ROI) analysis.

Financials A detailed breakdown of full lifecycle costs, to include but not limited to:

acquisition, sustainment, fielding, and all associated user training costs.

This constitutes the Total Cost of Ownership (TCO).

Technical Plan

A technical overview that includes the proposed system architecture, a comprehensive data management strategy, and the cybersecurity approach, which must align with sections 6.3 below.

Strategic Alignment

A clear explanation of the proposed solution's alignment with the broader A4 portfolio and any relevant Program or Functional Management Offices

(PMO/FMO).

6.1.1.2. Government's Integration Execution Office

The Government's Integration Execution Office will analyze the CR, evaluating it against the criteria listed above, as well as governance, portfolio management, enterprise architecture, and functional management requirements.

6.1.2 Adjudication and Acquisition Pathways

The Offeror shall provide all necessary technical documentation, analysis, and support to facilitate the Government's review of the capability. The Government will route the solution through the appropriate enterprise pathways for adjudication, which may include the AFCEC Requirements Engagement and Acquisition Panel (REAP), the Basing and Logistics Analytics and Artificial Intelligence Steering Team (BLAAST), and relevant Functional Requirements Working Groups (FRWG).

6.2 Technical Requirements & Constraints

All proposed solutions must adhere to the following technical requirements and constraints.

The proposal must explicitly address how the solution will meet each requirement.

6.2.1 Hosting Environment and Approved Platforms

The solution must be designed for and deployed within a DoD-approved cloud environment accredited to handle, at a minimum, Impact Level 5 (IL5) data. The proposed solution shall be based on either Microsoft Azure Government or Amazon Web Services (AWS) GovCloud.

The Offeror will be responsible for provisioning, configuring, and securing the environment in accordance with all DoD and Air Force policies.

6.2.2 Technology Stack

The solution shall, to the maximum extent practicable, be developed using the Microsoft Power Platform and native Microsoft Azure services to leverage existing enterprise agreements.

6.2.2.1 Preferred Components

It is anticipated that the solution will primarily consist of: Power BI, Microsoft Dataverse or Azure SQL Database, Power Apps, and Azure Data Factory or Power Automate.

6.2.2.2 Justification for Alternatives

Offerors may propose components outside of this stack but must provide a detailed justification demonstrating superior value based on technical performance, lower TCO, or clear benefits to security and the Authority to Operate (ATO) process.

6.2.3 Data Integration and Interoperability

The solution must be capable of securely connecting to various data sources.

6.2.3.1 Internal Interfaces

The solution must securely interface with existing AFCEC SharePoint sites and databases residing on the .mil network to automatically extract data.

6.2.3.2 External Interfaces

The solution must securely connect to external, internet-accessible government systems (e.g., FPDS-NG, SAM.gov) via approved Application Programming Interfaces.

6.2.4 Data Sensitivity and Handling

All data processed, stored, and transmitted by this system shall be considered, at a minimum, Controlled Unclassified Information (CUI). The system shall not be designed to handle or store any information classified at the Secret or Top-Secret level.

6.3 Cybersecurity and Compliance

6.3.1 Governing Policies

The design and development of the system shall be in accordance with the principles and controls outlined in Department of the Air Force Guidance Memorandum (DAFGM) 2024- 32-01, Civil Engineer Control Systems Cybersecurity. The Offeror shall coordinate with the Integration Execution Office's Cybersecurity team to ensure compliance. All services and software must also be in full compliance with the Defense Federal Acquisition Regulation Supplement (DFARS).

6.3.2 Security Compliance and Accreditation

The system must achieve and maintain a formal Authority to Operate (ATO) through the Risk Management Framework (RMF) process.

6.3.2.1 Offeror Responsibility

The Offeror shall be responsible for developing all required RMF documentation, implementing all necessary security controls, and supporting the system throughout the entire assessment and authorization process.

6.3.2.2 Compliance

The solution must be compliant with all applicable Security Technical Implementation Guides (STIGs) and DoD cybersecurity policies. Any commercial components must be listed on or eligible for the Air Force Evaluated Products List (AF EPL).

6.3.3 Zero Trust Architecture

The system architecture shall be designed and implemented in alignment with DAF Zero Trust Architecture (ZTA) principles, assuming no inherent trust for any user or device. This includes, but is not limited to, micro-segmentation, strict access control policies, and continuous monitoring.

6.3.4 Identity and Access Management

User authentication and access must be managed through government-approved mechanisms.

6.3.4.1 Authentication

The system must integrate with the DoD enterprise identity system to provide Single Sign- On (SSO) for all users via Common Access Card (CAC) authentication.

The solution must implement Role-Based Access Control (RBAC) to ensure users can only access data and functionality appropriate to their assigned roles and directorates (e.g., leadership view, program manager view, administrator view).

7.0 Required Deliverables

Deliverable No.

Deliverable Title Due Date / Frequency

1 Project Management Plan (PMP) 30 Days After Contract Award (DACA)

2 Monthly Status Report (MSR) Monthly, NLT 10th of following month

3 System Design Document (SDD) 90 DACA

4 Data Interface Control Document (ICD) 90 DACA

5 System Security Plan (SSP) and RMF Package Draft due 180 DACA

6 Test and Evaluation Plan & Report TBD; Report upon test completion

7 Training Plan and Materials TBD; Materials 30 days prior to training

8 Fully Deployed Operational System TBD

8.0 AOI Constraints

Offerors must be registered in SAM.gov.

9.0 Submission Requirements

A Spiral 2 Presentation/Pitch/Demo Basis of Evaluation along with proposed cost for future prototype should be communicated and scheduled with the POC listed in paragraph 10.0 using the title “AFCEC Enterprise-Wide Contracting Data Repository and Dashboard” by the date and time this AOI closes - 5:00 P.M. (CDT) on 14 April 2026.

Spiral 2 Presentation/Pitch/Demo Basis of Evaluation received after the specified due date and time will be discarded and not be evaluated by the Government unless schedule by the contracting officer after the specified date.

In addition to the technical solution proposed, we require the inclusion of a Rough Order of Magnitude (ROM) for the total cost associated with the delivery of a functional prototype.

This estimate should encompass all necessary resources to achieve the capabilities described herein and will be a key factor in our assessment of your response.

10.0 Points of Contact

Questions may be sent to:

Contracting Officer:

Michael Grasso at michael.grasso.3@us.af.mil

Contracting Specialist:

Krystle Zapata at krystle.zapata.1@us.af.mil mailto:michael.grasso.3@us.af.mil mailto:krystle.zapata.1@us.af.mil