Precise Ensemble Network Communications Allowing PNT (Positioning, Navigation, and Timing)

The Air Force Research Laboratory (AFRL/RF) issued a two-step Advanced Research Announcement (ARA) FA2377-26-R-B014 for the Precise Ensemble Network Communications Allowing Positioning, Navigation, and Timing (PENCAP) program. This ARA seeks white papers and proposals for experimentation and test efforts, with an estimated program cost of $9.3 million and an anticipated single award. The process involves an initial white paper submission by July 17, 2026, followed by a proposal request for selected offerors. The effort has a 36-month performance period and requires deliverables including software (algorithmic models, source code) and hardware (PENCAP Card Prototypes). Foreign prime contractor participation is not authorized, and proposals must adhere to specific formatting and content guidelines, including detailed cost breakdowns and data rights assertions. Key evaluation criteria include the uniqueness of the technical approach, understanding of the effort, technical soundness, and affordability.

The document, Solicitation FA2377-26-R-B014 Attachment 1, outlines a Placeholder Statement of Objectives (SOO) for Precise Ensemble Network Communications Allowing Positioning, Navigation, and Timing (PENCAP), dated June 15, 2026. This SOO is classified as CONTROLLED UNCLASSIFIED INFORMATION (CUI) and is exclusively available to qualified U.S. contractors. Eligibility is defined by DoDD 5230.25, which requires a certified DD Form 2345 (Militarily Critical Technical Data Agreement). Contractors interested in obtaining the SOO must contact Contract Specialist Gabriel Berner (gabriel.berner@us.af.mil) and Contracting Officer Kathryn Skaleski (kathryn.skaleski@us.af.mil), attaching a current and certified DD Form 2345. Upon verification of eligibility, the SOO will be distributed via the DoD Safe Website, accompanied by a separate decryption password.

This government solicitation attachment outlines supplemental requirements for contractors, covering critical areas such as disclosure of information, packaging and marking of deliverables, and the role of the Government Program Manager, Brandon Kalbfliesh. It details strict protocols for patent rights, including reporting inventions via DD Form 882. The document also specifies U.S. citizenship requirements for contractor employees accessing USAF bases and IT networks, with a waiver process for non-U.S. citizens. Emphasis is placed on Operations Security (OPSEC) training and compliance, along with Science and Technology (S&T) protection plans and Risk Identification and Security Countermeasures (RISC) reviews for senior/key personnel. Contractors must adhere to comprehensive test safety and planning requirements, including support for test reviews, mishap investigations, and airworthiness assessments. The attachment prohibits the use of Class I Ozone Depleting Substances (ODS) and provides information on an ombudsman for dispute resolution, emphasizing that initial concerns must go through the contracting officer.

This document is a Request for Proposal (RFP) FA237726RB014, issued by the USAF AFMC AFRL PZL AFRL RYKS, for "Precise Ensemble Network Communications Allowing Positioning, Navigation and Timing (PENCAP)" research. The solicitation seeks proposals for experimentation, evaluation, and assessment (CLIN 0001), hardware delivery (CLIN 0002), and computer software delivery (CLIN 0003), all under a Cost Plus Fixed Fee (CPFF) pricing arrangement. The work involves conducting research in accordance with a Statement of Objectives dated June 15, 2026. Key terms include a 36-month performance period for research and 33 months for hardware and software deliveries. The document also details inspection and acceptance procedures, payment instructions via Wide Area WorkFlow (WAWF), and specific security requirements for Air Force Research Laboratory (AFRL)-managed facilities, including prohibitions on certain personal networks and devices. The NAICS code is 541715 with a 1000-employee size standard.

Attachment No. 4, titled "Section K Representations, Certifications and Other Statements of Offerors," is a critical document for solicitations like FA8650-25-R-B014. It outlines essential RFO/R-DFARS provisions that offerors must complete and return, supplementing the annual representations from SAM.gov. The document emphasizes reviewing full text provisions from acquisition.gov and acq.osd.mil. Key provisions cover independent price determination, System for Award Management registration, offeror identification, responsibility matters, tax certifications, arms control treaties, trafficking in persons, and foreign procurements. It also details cost accounting standards, security prohibitions, and deviations. Offerors must certify various aspects, including foreign government ownership, performance-based payments, safeguarding defense information, and compliance with cybersecurity maturity model certification (CMMC Level 2). Additional sections address nontraditional defense contractors, reporting performance outside the US, business operations with certain regimes, and prohibitions on specific foreign procurements and IT network designs. The document concludes with a signature block for offerors to attest to the accuracy and completeness of their representations.

The DD FORM 1423-1, FEB 2001, outlines the Contract Data Requirements List for federal government contracts, detailing various data items and their submission requirements under contract number FA2377-26-R-B014. Key data items include Scientific and Technical Reports, Funds and Man-Hour Expenditure Reports, Spend Plans, Contract Funds Status Reports, Status Reports, Presentation Material, Computer Software Products (source code), Software User Manuals, Software Design Descriptions, Interface Design Descriptions, Test Plans (Flight and Taxi Test Plan), Security Plans, Science and Technologies Protection Implementation Plans, and R&R Annual Updates.Each data item specifies the requiring office (AFRL/RYWN), submission frequency, distribution, and critical remarks regarding tailoring, format guidelines (e.g., ANSI-based AFRL Format Guidelines), submission timelines, and electronic submission requirements (encrypted or password protected). Distribution statements (Type B for US Government agencies only, Type D for DoD and US DoD contractors only) and export control warnings are consistently included for technical data. The document also provides instructions for government personnel and contractors on completing the form, including pricing groups for data items.

Solicitation FA8650-25-R-B014, Attachment 6, outlines the Air Force Research Laboratory's (AFRL) Security Risk Review process for proposals, aiming to protect Department of the Air Force Science and Technology (S&T) from undue foreign influence. All proposals will undergo a Security Risk Review prior to award selection, focusing on Senior/Key personnel and "Covered Individuals." The review uses information from submitted questionnaires, public data, and government databases, with nationality or citizenship not being a factor. AFRL's holistic decision-making process considers technical and security factors to determine an appropriate Risk Acceptance Level. Applicants must submit specific documentation, including a Research and Related Senior and Key Person Profile Worksheet, Security Program Questionnaire, and Privacy Act Statement consent forms. Non-compliance or identified security risks exceeding acceptable thresholds may lead to award decline. During the performance period, annual resubmission of personnel profiles and immediate notification of foreign government talent program participation or foreign components with strategic competitors are required. Failure to comply may result in government remedies, and these provisions must be flowed down to sub-awardees.

The Security Program Questionnaire is designed to evaluate the security practices of institutions receiving research funding, typically as part of federal grants or RFPs. It requires applicants to detail their plans for physical and information security, including storage, transmission, disposal, and reproduction of effort-related information. The questionnaire also covers safeguards for personnel, protection of Government Furnished Equipment/Information (GFE/GFI), cybersecurity, operations security, insider threat mitigation, and incident response for compromised information. Additionally, it assesses the applicant's willingness to provide annual AFRL S&T Protection training to all authorized personnel. The objective is to ensure robust security measures are in place to protect sensitive research information and prevent unauthorized access or compromise.

The document outlines a standardized Research and Related Senior and Key Person Profile Worksheet, designed for federal government RFPs, federal grants, and state/local RFPs. This worksheet serves to collect essential information for various project personnel, including the Project Director/Principal Investigator (PD/PI) and up to five additional Senior/Key Persons. Each profile requires details such as first name, last name, position/title, organization name, email address, and project role. Optional fields include middle name, suffix, department, division, phone number, LinkedIn profile, and other project roles. The consistent structure across all profiles ensures comprehensive data collection for individuals involved in research and related contracts, particularly those based on FAR (Federal Acquisition Regulation) guidelines.

The Air Force Research Laboratory's Privacy Act Statement outlines the authority, purpose, and routine uses for collecting information related to federal grants, cooperative agreements, contracts, and other research agreements. Authorities include various Public Laws, U.S. Codes, Executive Orders, and DoD Instructions, emphasizing national security and protection of science and technology. The collected data ensures responsible parties receive Department of the Air Force awards. Routine uses involve sharing information with contractors, grantees, and law enforcement for agency functions and legal violations. While providing information is voluntary, non-compliance with disclosure requirements, particularly under 42 U.S. Code § 6605, may lead to application rejection. The document also includes sections for acknowledging consent from covered individuals and institutional representatives.

This USAF Rider outlines critical terms and conditions for a software license agreement between the U.S. Air Force and a contractor, specifically for the Air Force Research Laboratory supporting the Name of the Program under contract FAXXXX-XX-X-XXXX Task Order FAXXXX-XX-X-XXXX. It clarifies that the attached Licensor’s Software License Agreement is incorporated by reference but only to the extent consistent with Federal Law. Inconsistent clauses, particularly those concerning contract formation (requiring warranted contracting officer signatures), termination (governed by FAR/DFARS and the Contract Disputes Act), governing law/jurisdiction (Federal Law and the Contract Disputes Act), licensee indemnities, future fees/penalties (prohibited by the Anti-Deficiency Act), and advertisements/endorsements (prohibiting use of U.S. Government names/logos), are deemed deleted and unenforceable. The Rider also addresses limitations on damages, force majeure events, remedies (FAR 52.233-1 Disputes), and establishes that the overarching contract, not the software license agreement, represents the entire agreement.

This document provides clarification on solicitation FA2377-26-R-B014 for the PENCAP program, answering three vendor questions regarding the upcoming laboratory demonstration and security classification requirements. Regarding the laboratory demonstration, the Government clarifies that the precise number of timing sources and receiving platforms will not be set until post-award kick-off meetings with the selected awardee. Consequently, submitting vendors should focus their white papers on demonstrating scalable methodologies for both timing sources and the proposed dissemination architecture. Addressing security and data classification concerns, the Government explains how Link-182 can be utilized within an unclassified scope of work. While the link itself operates on secure networks, this contract remains entirely unclassified because development and testing are restricted to processing timing data after it has transitioned from the classified (Red) side to the unclassified (Black) side of the encryption boundary. The associated card, networking method, and ensemble will also remain completely unclassified.