4. Call 0002 eFOIA.pdf

Electronic Freedom of Information Act (eFOIA) Call

Under BES Commercial Solutions Opening (CSO)

NOVEMBER 2026

Contents

COMMERCIAL SOLUTIONS OPENING (CSO) CALL

1.0 Executive Summary & Objective

2.0 Core Technical & Functional Requirements

Capability Area 2.1: Request Intake & User Authentication

Capability Area 2.2: Request Processing, Case Management & Lifecycle Operations

Capability Area 2.3: Request Delivery & Records Management

Capability Area 2.4: Request Publication (Electronic Reading Room)

Capability Area 2.5: Reports, Metrics, and Audit Logs

Capability Area 2.6: Cybersecurity Resilience, Adaptable Scanning & Technical Agility

3.0 Award, Funding & Contractual Information

3.1 Applicable Clauses

4.0 Submission Instructions & Phased Evaluation Process

Phase 1: Solution Brief Submissions

Phase 2: Technical Demonstration & Oral Pitch (By Invitation Only)

Phase 3: Commercial Proposal & Negotiations

5.0 Points of Contact (POC)

COMMERCIAL SOLUTIONS OPENING (CSO)

CALL

CALL NO: FA8770-27-R-B001

UNDER OVERARCHING CSO: Department of the Air Force (DAF) Program Acquisition Executive (PAE) Business and Enterprise Systems (BES)

Focus Area: Compliance

Project Title: Next-Generation Electronic Freedom of Information Act (eFOIA) End-to- End Technology System Issuing Agency: Air Force AFLCMC/GBK Program Office: Electronic Freedom of Information Act Program (eFOIA) Release Date: 06 November 2026 Phase 1 Submission Deadline: 30 November 2026

NAICS Code: 513210

This Commercial Solutions Opening (CSO) Call is issued under the authority of 10 U.S.C. § 3458, as implemented by DFARS Subpart 212.70 and DoD Class Deviation 2022-O0007 (Defense Commercial Solutions Opening)

The Government reserves the right to limit selections at any point during the process. The Government reserves the right to award to some, all, or none of the offerors.

1.0 Executive Summary & Objective

The Air Force is seeking innovative commercial solutions to modernize, streamline, and replace its legacy Freedom of Information Act (FOIA) infrastructure. This Call is issued under the authority of the overarching Department of the Air Force (DAF) Program Acquisition Executive (PAE) Business and Enterprise Systems (BES) Commercial Solutions Opening (CSO) to identify, evaluate, and acquire an Electronic FOIA (eFOIA) Technology System capable of managing the absolute end-to-end lifecycle of a FOIA request.

The objective of this Call is to pilot and scale a secure, cloud-native implementation with the ability to host in Cloud One (Government hosted) and carry out a highly automated software solution that dramatically reduces backlog, speeds up response times, ensures strict compliance with ever-changing federal regulations including a secure cyber posture, and provides an intuitive interface for both agency personnel and public requesters.

2.0 Core Technical & Functional Requirements

Proposed solutions must address all six capability areas of the FOIA request lifecycle described below. Solutions can incorporate modern capabilities such as artificial intelligence (AI), machine learning (ML), natural language processing (NLP) for optical character recognition (OCR), auto-redaction, and automated workflow routing. The solution must be continually compliant with all law, regulations, and policies at the Congressional level down to the Air Force level. The solution must enable the compliance work of FOIA.

Capability Area 2.1: Request Intake & User Authentication The solution must feature a secure, public-facing portal and a structured administrative interface to ingest requests from multiple streams while supporting enterprise identity integration.

• Public Requester Portal & Authentication: A mobile-friendly, secure web interface allowing citizens to submit requests, upload attachments, check real-time status updates, and correspond directly with analysts. The portal must support multi-factor public authentication protocols (e.g., Login.gov or ID.me integrations) and standard web accounts.

• Internal Personnel Authentication: Full native support for DoD Identity, Credential, and Access Management (ICAM), including Common Access Card (CAC) / Public Key Infrastructure (PKI) single sign-on (SSO) for agency analysts, reviewers, and administrators.

• Multi-Channel Ingestion: Automated ingestion and digitization of requests submitted via web forms, direct email, physical mail (via OCR scanning integrations), and third-party portals (such as National FOIA Portal APIs).

• Identity Verification & Fee Agreement: Standardized fields capturing requester categories (e.g., commercial, educational, news media, other) and structured agreement to pay specified fee ceilings.

• Auto-Triage & Deduplication: AI-driven triage to identify duplicate requests, flag potentially multi-agency requests, and assign unique tracking numbers automatically.

Capability Area 2.2: Request Processing, Case Management & Lifecycle Operations Request processing must support high-volume document management, inter-agency collaboration, and the full administrative lifecycle.

• Workflow Automation & Assignment: Intelligent routing to specific agency offices, divisions, or individual analysts with configurable reminders, escalations, and due-date tracking.

• Agency Consultations & Referrals: Built-in workflows to package and securely transfer responsive records to external DoW components, federal agencies, or Intelligence Community entities for equity review; track independent referral response timelines; and seamlessly ingest incoming external referrals into the Air Force case management workflow.

• Administrative Appeals & Litigation Management: Dedicated tracking modules to manage FOIA administrative appeals, assign appellate review counsel, log legal determinations, and automatically generate structured Vaughn Indices (detailed itemized justification tables linking withheld documents to specific FOIA exemptions) to support federal court litigation defense.

• Robust Search & Deduplication (e-Discovery): Advanced search capability across uploaded document repositories, supporting Boolean queries, fuzzy search, metadata extraction, and automatic identification of near-duplicate files.

• AI-Assisted Redaction Suite: Intuitive manual markup tools for text, images, and embedded metadata. Automated PII (Personally Identifiable Information) masking and pattern-matching redactions (e.g., SSNs, phone numbers, email addresses). Mandatory exemption tagging mapped directly to FOIA exemptions (e.g., Exemption 4 for proprietary business data, Exemption 5 for deliberative process, Exemption 6/7C for privacy).

• Internal and External Collaboration: Secure, shared digital workspaces allowing multiple reviewers, subject matter experts (SMEs), and legal counsel to co-review, annotate, provide, and approve responsive records simultaneously and temporarily for assigned cases.

Capability Area 2.3: Request Delivery & Records Management The system must safely transmit released records back to the requester while preserving records management best practices.

• Secure Delivery Portal: Requesters must be notified via email to log into a secure, encrypted portal to download their released packages, ensuring heavy file sizes do not bounce off agency servers.

• Metadata Scrubbing: Automated scrubbing of hidden document metadata, change histories, or underlying layers on all finalized, redacted PDFs prior to transmission.

• Integrated Fee Calculation: Automated invoice generation, payment processing integrations (e.g., Pay.gov), and fee waiver status tracking.

• Records Retention & Disposition Compliance: Automated scheduling, archiving, and disposition of case files and administrative records in strict compliance with National Archives and Records Administration (NARA) General Records Schedule (GRS) 4.2.

Capability Area 2.4: Request Publication (Electronic Reading Room) To maximize transparency, the system must facilitate proactive disclosure.

• Automated Electronic Reading Room (ERR): An advanced searchable, public library of released documents.

• "Release to One, Release to All" Workflow: Automated triggering and approval workflow for publishing highly requested documents (e.g., documents requested 3 or more times) directly to the public-facing library.

• Compliance Standards: Ensure all published public-facing documents are optimized for search engines (SEO) and conform to Section 508 accessibility guidelines (structured headers, alt-text, readable screen-reader layers).

Automated scanning to ensure no protected or non-releasable content is published.

Capability Area 2.5: Reports, Metrics, and Audit Logs Federal agencies are legally required to report yearly statistics to the Department of Justice (DOJ).

• DOJ Annual FOIA Report Generator: One-click compliance reporting that automatically compiles, formats, and validates the mandatory statistical tables required for the DOJ Annual FOIA Report. The report generator must include rapid adaptability configurable by agency administrators without requiring software recoding or development cycles.

• Customizable Report Generation: Customizable report generation must be possible at any time by authorized users across all system metrics.

• Executive Dashboards: Real-time visual metrics illustrating average response times, backlogs, pending caseloads, fee collections, and processing bottlenecks using scalable levels from individual users to enterprise-wide analytics.

• Comprehensive Audit Trails: Unalterable, time-stamped system logs tracking every user interaction, record modification, exemption applied, and transmission completed to ensure security and compliance.

Capability Area 2.6: Cybersecurity Resilience, Adaptable Scanning & Technical Agility To protect sensitive government records and ensure technological relevance, proposed solutions must exhibit continuous security and configuration agility.

• Dynamic Vulnerability & Code Scanning: The system must natively support or integrate seamlessly with robust application security tools. It must undergo continuous vulnerability scanning and robust code scans aligning with NIST guidelines, including Static Application Security Testing (SAST) and Dynamic Application Security Testing (DAST).

• Agility of Scan Protocols: Because agency cybersecurity frameworks and required scan types are subject to change, the vendor must demonstrate how the system easily adapts to support new, updated, or custom scanning templates and security requirements without disrupting core processing operations.

• Configuration: To prevent stagnation with a rapidly evolving technological landscape, the software environment must utilize intuitive, low-code/no-code administrative controls. This allows the agency to adjust workflow steps, data ingestion pathways, and integration endpoints locally as operational needs fluctuate.

• Legacy Data Ingestion & Migration Strategy: Demonstrated technical capability to ingest, map, and index legacy DAF FOIA case records, historical case metadata, and existing document repositories during initial system onboarding with minimal disruption.

3.0 Award, Funding & Contractual Information

• Expected Award Type(s): Commercial Contract under RFO Part 12 / R-DFARS

212.70

• Anticipated Number of Awards: The government intends to award one (1) contract resulting from this Call, subject to the availability of funds and the quality of submissions. The Government reserves the right to award some, all, or none.

The Government reserves the right to cancel this Call at any time prior to award.

The Government is not responsible for, nor will it reimburse, any costs incurred by offerors in preparing or submitting a response to any phase of this Call.

• Target Contract Award Date: April 2027

• Target Project Duration: 60 months (1 base year, 4 one-year option periods, pursuant to RFO 52.217-9), subject to annual availability of appropriations.

• Available Funding Types: Anticipate Operations and Maintenance (O&M) Funds (3400), obligated annually based on bona fide needs. Funds are not presently available for this effort. No award will be made until funds are certified and made available to the Contracting Officer. The Government's obligation under any resulting contract is contingent upon the availability of appropriated funds from which payment can be made. No legal liability on the part of the Government for any payment may arise until funds are made available to the Contracting Officer for this contract and until the contractor receives notice of such availability, to be confirmed in writing by the Contracting Officer.

• Foreign Influence: The Offeror, and all subcontractors, suppliers, consultants, service providers, affiliates, and other third parties supporting performance at any tier, shall not be foreign-owned. For purposes of this requirement, a foreign-owned entity is an entity in which a foreign person, foreign business, foreign government, or other foreign interest holds, directly or indirectly, any ownership interest. This includes ownership through parent companies, subsidiaries, affiliates, investment vehicles, beneficial owners, or other intermediary entities. An Offeror that proposes, uses, or permits participation by a foreign-owned entity is ineligible for award, or may be found noncompliant after award.

3.1 Applicable Clauses

• Foreign Ownership, Control, or Influence (FOCI) & Supply Chain Security: The

Offeror, including all subcontractors, suppliers, and third-party software components integrated into the proposed solution, must not be under Foreign Ownership, Control, or Influence (FOCI) that presents an unacceptable risk to national security, as determined in accordance with the National Industrial Security Program Operating Manual (NISPOM) (32 CFR Part 2004) and DFARS Subpart 252.204- 7012.

• Software Bill of Materials (SBOM) & Continuous Monitoring: The vendor must deliver a complete CycloneDX (JSON) encoded, human-readable SBOM with the initial proposal and upon every major software release. The vendor must grant the Government the right to run independent SAST, DAST, and container vulnerability scans. Failure to provide complete software code transparency or cooperate with Air Force cybersecurity monitoring tools shall be grounds for immediate revocation of the system’s Authority to Operate (ATO) and termination for cause.

• Immutable Backups & Disaster Recovery: The system architecture deployed within Cloud One must utilize isolated, immutable backups and support a Recovery Point Objective (RPO) of less than 1 hour and a Recovery Time Objective (RTO) of less than 4 hours. System backups must be logically separated from the primary production environment with strict, multi-party authentication (e.g., dual-custodian controls) so that no single compromised vendor or administrator account can delete or modify historical backup databases.

• Separation of Software and Services: This CSO Call is strictly for the licensing, hosting configuration, software maintenance, and initial data migration of the COTS eFOIA software application. Operational labor roles (such as ISSOs, System Administrators, and eFOIA Help Desk support) are explicitly excluded from this solicitation and will be maintained under separate Department of the Air Force service contracts. The software vendor must provide standard Tier-3 developer support and collaborate with the Government’s designated third-party IT service providers during system integration.

4.0 Submission Instructions & Phased Evaluation Process

The evaluation process under this CSO Call is streamlined to minimize overhead for commercial tech firms and will be conducted in three (3) distinct phases:

4.1 Phase 1: Solution Brief Submissions

• Format: Submissions are limited to either two (2) single-sided pages (12-point font) or five (5) presentation slides, plus a 1 page pdf Rough Order of Magnitude (ROM) high level price (ROM will be used for market research purposes and will not be evaluated in Phase 1).

• Submission: Submit files via the Solicitation module in PIEE by the Phase 1 Deadline 30 November 2026

Required Content:

1. Contact Information:

• Provide Offeror Name, Title, Date, Point of Contact (Name, Email, Phone), CAGE Code, UEI Number, SBA socio-economic status (if applicable), size standards based on the NAICS code, and Company Address.

2. Technical Approach:

• Describe the proposed technology and its relevance to the project description.

Clearly explain your product's architecture, how it addresses the core eFOIA lifecycle areas (Intake, Processing/Appeals, Delivery, Reading Room, Reporting, and Cybersecurity), and your data migration approach.

• Commercial Item Compliance: Clarify how the proposed solution and services meet the statutory definitions of "commercial product" and/or "commercial service."

• Data Rights Strategy: Describe your approach to ensuring the Government retains unrestricted rights to all imported, generated, or derived government data, and identify any proprietary commercial software license restrictions.

3. Execution Plan and Budgetary Estimate:

• Budgetary Estimate (ROM): Provide a Rough Order of Magnitude (ROM) cost estimate broken down by licensing, onboarding/migration, and annual sustainment.

• Execution Plan / Milestone Schedule: Include a high-level milestone schedule demonstrating the implementation timeline, deployment phases, and critical path milestones.

4. Company Profile and Security Posture:

• Cloud One / IL5 Readiness Posture (Mandatory; noncompliance will result in not-selectable status): Demonstrate the company's capability to deploy and operate within a DoD Impact Level 5 (IL5) environment. Offerors must identify current FedRAMP High authorizations, DISA Provisional Authorizations (PA), or provide an architectural compliance plan demonstrating readiness to achieve an Air Force Authority to Operate (ATO) in Cloud One within the proposed deployment schedule.

• Management Team: Identify the key personnel who will execute the effort, including technical leads and relevant experience.

5. Data Rights Assertions:

• Include standard commercial assertions for underlying software, APIs, and commercial item deliverables.

The Government is not responsible for any costs incurred by offerors in the preparation of their Solution Briefs. These costs are not recoverable.

Evaluation Criteria: Solution briefs will be evaluated individually against the evaluation criteria established in this Call. The Government will evaluate individual Solution Briefs against the following evaluation criteria, which are of equal importance:

• Lifecycle of a FOIA request

• Request Intake

• Request Processing & Case Management

• Request Delivery

• Request Publication (Electronic Reading Room)

• Reports, Metrics, and Audit Logs

• Cybersecurity Resilience, Adaptable Scanning & Technical Agility

• Continual Compliance

Categorization & Selection:

Following the evaluation of Phase 1 Solution Briefs, the Government will categorize each submission into one of three categories:

Selectable - Invited: The Solution Brief has met the evaluation criteria with sufficient merit. The Government has determined that the technical approach is highly advantageous to the eFOIA objectives, and the offeror is invited to participate in Phase

Selectable - Not Invited: The Solution Brief has met the evaluation criteria and possesses technical merit, but due to capacity limitations, funding constraints, or the availability of more highly-rated proposals, the offeror is not invited to participate in Phase 2 at this time. The Government reserves the right to "harvest" or request a proposal from this offeror at any point within twelve (12) months of the evaluation date should circumstances change.

Not Selectable: The Solution Brief does not sufficiently meet the evaluation criteria, does not present an adequate approach to solve the objectives of this Call, or failed to affirm the mandatory IL5 capability. The proposal is no longer under consideration for this Call.

The Government reserves the right to limit the number of "Selectable" offerors invited to Phase 2. An invitation to Phase 2 is at the sole discretion of the Government.

Following the evaluation, the Government will notify all offerors in writing of their categorization status.

4.2 Phase 2: Technical Demonstration & Oral Pitch (By Invitation Only)

• Format: Submissions in this phase consist of a live or virtual 60-minute presentation (a 40-minute interactive software demonstration and a 20-minute Q&A session), accompanied by a presentation slide deck (maximum 10 slides).

• Submission: Coordinate presentation scheduling and submit demonstration slides via email directly to the Contracting Officer and Technical Lead listed in Section 5.0 by the deadline established in the Phase 2 invitation letter.

Required Content:

1. Live System Demonstration:

• Provide a live demonstration of a functioning commercial software platform using synthetic, non-attributional data. Demonstrate core user workflows including public submission, CAC/SSO administrative login, triage, auto-routing, and administrative low-code configuration.

2. Detailed Focus Area Walkthrough:

• AI Redaction & FOIA Compliance: Demonstrate real-time AI automated redaction of mock PII (SSNs, names, phone numbers) and proper exemption tagging (e.g., Exemption 4, 5, 6, 7C).

• Consultation, Appeals & Vaughn Indexing: Demonstrate workflows for generating external referral packages, tracking administrative appeals, and automated generation of a Vaughn Index for simulated court litigation.

• Delivery & Reading Room Workflows: Demonstrate finalized package release, automatic metadata scrubbing, and the "Release to One, Release to All" approval process for the Electronic Reading Room.

• Compliance Reports & Audit Verification: Execute a DOJ Annual Report generation within a few clicks demonstrating the ability to break it down by FY, period, or agency. Show the immutability of system audit logs.

3. Evaluator Sandbox Access:

• Provide evaluator access credentials to a secure, commercially hosted, unclassified sandbox environment for up to five (5) business days following the pitch. Evaluators will independently test workflow agility, interface responsiveness, and configuration controls.

4. Key Technical Personnel:

• Present the key software architects, security engineers, and project leads who will directly execute system deployment, onboarding, and sustainment.

of their Technical Demonstrations. These costs are not recoverable.

Phase 2 Evaluation Criteria:

Demonstrations and sandbox assessments will be evaluated based on the following equally weighted criteria:

• Core Demonstration Performance

• AI Redaction Accuracy & Exemption Mapping

• Lifecycle, Appeals & Reporting Agility

• Architecture & Configuration Adaptability

• Complete FOIA Process Demonstration

Following the evaluation of Phase 2 Technical Demonstrations, the Government will categorize each submission into one of three categories:

Selectable - Invited: The Technical Demonstration has met the evaluation criteria with sufficient merit. The Government has determined that the technical approach is highly advantageous to the eFOIA objectives, and the offeror is invited to participate in Phase

Selectable - Not Invited: The Technical Demonstration has met the evaluation criteria and possesses technical merit, but due to capacity limitations, funding constraints, or the availability of more highly-rated proposals, the offeror is not invited to participate in Phase 3 at this time. The Government reserves the right to "harvest" or request a proposal from this offeror at any point within twelve (12) months of the evaluation date should circumstances change.

Not Selectable: The Technical Demonstration does not sufficiently meet the evaluation criteria, does not present an adequate approach to solve the objectives of this Call, or failed to affirm the mandatory IL5 capability. The proposal is no longer under consideration for this Call.

The Government reserves the right to limit the number of "Selectable" offerors invited to Phase 3. An invitation to Phase 3 is at the sole discretion of the Government.

4.3 Phase 3: Commercial Proposal & Negotiations

• Format: Submissions must consist of a single, integrated commercial proposal document (PDF format, maximum 25 pages, excluding pricing schedules and licensing attachments).

• Submission: Submit proposal packages electronically via the PIEE Solicitation Module or via direct secure electronic transmission as specified in the formal Phase 3 Request for Proposal (RFP) letter.

• Proposals must remain valid for 180 days upon receipt.

Required Content:

1. Statement of Work (SOW):

• Provide a detailed, task-by-task SOW outlining specific implementation plan, data migration strategies, configuration timelines, training schedules, and ongoing tier- 3 support structures based on the Government-provided SOO.

2. Comprehensive Technical and Integration Architecture:

• Deliver a complete technical design document, compliance with NIST SP 800- 53 Rev5 security controls, and continuous vulnerability scanning (SAST/DAST) execution.

3. Project Implementation Timeline and Milestones:

• Detail a comprehensive, phased project schedule with a clear Work Breakdown Structure (WBS). The schedule must detail the path to achieving a full Authority to Operate (ATO) and deployment within a DoW IL5 environment

4. Business and Detailed Price Proposal:

• Structured Pricing Schedule: Itemize all costs across the 60-month target duration (1 base year and 4 option years). Pricing must break out software licensing (enterprise vs. seat-based), hosting costs, onboarding/data migration services, training, and yearly maintenance.

• Price Reasonableness & Fair Assertions: Provide commercial sales data, published price lists, or historical contract data to substantiate that the proposed pricing is fair, reasonable, and competitive.

5. Completed Model Agreement & Assertions:

• Submit the finalized commercial license agreement, software maintenance agreement, and finalized data rights assertions, confirming the government’s unrestricted ownership of its data.

of their Full Proposal. These costs are not recoverable.

Phase 3 Evaluation Criteria:

Full proposals will be evaluated on the following criteria to determine the best overall value to the Government:

• Technical & Management Approach

• Implementation Timeline

• Price Reasonableness & Completeness

• Terms & Data Rights Acceptability

Following the evaluation of Phase 3 Proposals, the Government will categorize each submission into one of three categories:

Selectable - Invited: The proposal has met the evaluation criteria with sufficient merit.

The Government has determined that the technical approach is highly advantageous to the eFOIA objectives, and the offeror is invited to participate in Contract Award.

Selectable - Not Invited: The proposal has met the evaluation criteria and possesses technical merit, but due to capacity limitations, funding constraints, or the availability of more highly-rated proposals, the offeror is not invited to participate in a Contract Award at this time. The Government reserves the right to "harvest" or request a proposal from this offeror at any point within twelve (12) months of the evaluation date should circumstances change.

Not Selectable: The proposal does not sufficiently meet the evaluation criteria, does not present an adequate approach to solve the objectives of this Call, or failed to affirm the mandatory IL5 capability. The proposal is no longer under consideration for this Call.

The Government reserves the right to limit the number of "Selectable" offerors invited to a Contract Award. An invitation to a Contract Award is at the sole discretion of the Government.

5.0 Points of Contact (POC)

• Agreements / Contracting Staff: Kate M. Compton, CO, kate.compton@us.af.mil ;

Katherine Cokonougher, katherine.cokonougher@us.af.mil ; Kristina Hodgkinson- Heltzel, katherine.cokonougher@us.af.mil ; Eric Brown, eric.brown.86@us.af.mil

• Technical Lead / Program Manager: Kelsey Bryant, PM, kelsey.bryant.3@us.af.mil

For inquiries regarding this Call, submit questions via email to the POCs listed above with the subject line "QUESTIONS: CSO-CALL-FA8770-27-R-B001- eFOIA" no later than 16 November 2026.

6.0 Submission: Solicitation Module Instructions

Step 1: Register and Assign Roles (First-Time Setup)

Before you can interact with the Solicitation module, you must have the correct permissions.

New PIEE Users

1. Go to the PIEE Portal and click Register

2. Select Vendor and follow the prompts to create credentials, security questions, and your user profile.

3. Under the Roles step: Select SOL - Solicitation from the dropdown.

4. Select the Proposal Manager role (allows submission) or Proposal View Only (only allows viewing).

5. Click Add Roles, enter your company's CAGE Code as the location code, provide a justification, and submit.

6. Await activation by your company's Account Administrator.

Existing PIEE Users

1. Log in to PIEE.

2. Navigate to My Account (top-left) and select Add Additional Roles.

3. Complete Steps 3 to 6 above to add the SOL - Solicitation / Proposal Manager role.

Step 2: Search for a Solicitation mailto:kate.compton@us.af.mil mailto:katherine.cokonougher@us.af.mil mailto:katherine.cokonougher@us.af.mil mailto:eric.brown.86@us.af.mil mailto:kelsey.bryant.3@us.af.mil

Once your role is active, you can search for posted Department of Defense (DoD) solicitations.

1. Log In: Log into the PIEE Portal.

2. Open the Module: Click the Solicitation icon on your home dashboard.

3. Run a Search: Navigate to the Search section and look up the solicitation using parameters such as:

• Solicitation Number

• Response Date Range

• Set-Aside Status

• Contracting Office DoDAAC

4. Access the Notice: Locate the solicitation in your search results and click on the Notice ID hyperlink to open the details.

Step 3: Submitting Your Offer (Proposal Manager Only)

Once you have retrieved the correct solicitation notice, you are ready to compile and upload your proposal.

1. Open the Offer Tab: Inside the active notice, click on the Offer tab.

2. Select CAGE Code: Select the applicable CAGE Code for which you are submitting the offer. (The list is pre-filtered based on CAGE codes approved in your user profile).

3. Enter Offer Details: Provide your unique Offer Identifier and acknowledge any solicitation updates/amendments if prompted.

4. Upload Attachments: Click Choose Files (or Add Files) to upload your proposal documents.

• Note: PIEE supports up to 1.9 GB per file with no limit on the number of files. If uploading large files, divide them logically and label them clearly.

5. Set Signature Date: Enter the signature date.

Step 4: Digital Signing and Confirmation

Because PIEE operates in a highly secure environment, you must sign your submission electronically.

1. Click the Signature button.

2. A Sign Document pop-up window will appear.

3. Enter your Digital PIN. (If you sign with a User ID and password, you must establish a self-defined 6-digit Digital PIN).

4. Enter the One-Time Password (OTP) sent to your registered email or generated via your authorized authenticator app (e.g., Google Authenticator, Microsoft Authenticator).

5. Click Sign and Submit.

6. Confirmation: Upon success, a confirmation message will be displayed on the screen verifying the timestamp of receipt.

https://www.google.com/url?q=https%3A%2F%2Fpiee.eb.mil%2F