Section L - T-BOS DRAFT RFP-07.17.2026.docx

SECTION L – INSTRUCTIONS TO OFFERORS

L-1 PROPOSAL FORMAT

L.1.1. General L.1.1.1. The following Instructions to Offerors (ITO) provide general guidance for preparing proposals, as well as specific instructions on the format and content of the proposals. The Offeror’s proposal shall include all data and information requested by the ITO and shall be submitted in accordance with (IAW) these instructions. Offerors are cautioned that any noncompliance with the terms and conditions of the Request for Proposals (RFP) may cause their proposal to be determined not eligible for award. The offer shall be compliant with all requirements as stated in the PWS and the solicitation, including all attachments.

Offerors are NOT permitted to take any exception to the terms and conditions within the RFP.

L.1.1.2. The Government will evaluate the information presented in the Offeror’s submission. It is the Offeror’s responsibility to provide a submission that enables the Government to effectively evaluate the Offeror’s submission. The Offeror has the burden to provide a submission that demonstrates the Offeror has an accurate understanding of the requirements listed in the solicitation, the Offeror has viable solutions for the requirements, and how the Offeror is able to meet the requirements.

The Government will conduct an initial evaluation of all proposal volumes upon receipt and if considered necessary develop Evaluation Notices (ENs) that will be forwarded to Offerors immediately after the Procuring Contracting Officer (PCO) makes a competitive range determination and opens negotiations. This provides Offerors with the opportunity to revise proposals and address any noted deficiencies prior to delivering their complete cost/price submission.

The Offeror is herewith reminded that the Government reserves the right to award this effort based on initial proposals, as received, without negotiations.

L.1.1.3. The proposal should not simply rephrase or restate the Government’s requirements but rather provide convincing rationale to address how the Offeror intends to meet the solicited requirements, and where appropriate demonstrate specific examples to support the Offeror’s proposal. The proposal shall be clear and concise and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. Offerors shall assume the Government has no prior knowledge of the Offeror’s experience or capability. The Government’s evaluation will solely be based on the information provided in the Offeror’s proposal. Statements that the Offeror will provide a particular feature or objective without specific explanation on how the Offeror proposes to meet that feature or objective are generally inadequate and may adversely impact the Government’s evaluation of the Offeror. While not all inclusive, the following types of statements are also considered inadequate:

L.1.1.3.1. Unsupported statements that the Offeror allegedly understands the requirements.

L.1.1.3.2. Unsupported statements that the Offeror allegedly can or will comply with the requirements.

L.1.1.3.3. Unsupported statements that simply paraphrase the requirements.

L.1.1.3.4. Undefined or unexplained statements such as “best practices will be used,” “standard procedures will be used,” or “well-known techniques will be employed.”

L.1.1.4. Offerors are strongly encouraged to carefully review all Government provided information and documents, to include, but not limited to submittal instructions, the PWS, the technical library data, and Section M - Evaluation Factors.

L.1.1.5. Elaborate brochures, documentation, binding, detailed artwork, pictures, or other embellishments are unnecessary and are not desired.

L.1.1.6. Proposal Acceptance Period. Offeror’s proposals shall remain valid for a minimum of 180 calendar days from the proposal submittal due date specified in this solicitation. The term “acceptance period,” as used in this solicitation, means the time period during which the Government may award a contract. In the event that a final award decision is not made within this period, the Government may request that Offerors in the competitive range extend the acceptance period of their proposals.

L.1.1.7 Proposals that address only a subset of the solicitation may be deemed incomplete and ineligible for award.

L.1.1.8 Oral presentations will not be accepted.

L.1.1.9 If an Offeror believes the requirements in these instructions contain an error, omission, or are otherwise unsound, the Offeror shall immediately notify the Contracting Officer (CO) (identified in Table L.2) in writing with supporting rationale, to include the remedies of the Offeror is requesting the CO considers as related to the error or omission.

L.1.1.10 To assist in the evaluation of proposals, the Government may employ AI tools for tasks such as summarizing content and identifying compliance with solicitation requirements. These tools will be used solely to augment, not replace, the judgment of the Government's human evaluators. All source selection decisions will be made exclusively by Government personnel, and all proprietary and source selection sensitive information will be protected IAW applicable regulations.

L.1.2. Electronic Documents.

L.1.2.1. All referenced documents suitable for public release for the solicitation are available on the Procurement Integrated Enterprise Environment (PIEE) Solicitation Module and the System of Award Management at https://SAM.gov/ to include any future amendments to the solicitation. Potential Offerors are encouraged to subscribe for real-time email notifications when information has been posted to the website related to this solicitation.

L.1.2.2. Amendments to the Solicitation. If the solicitation is amended, all terms and conditions that are not expressly amended remain unchanged. Offerors shall acknowledge receipt of any amendment to this request in the PIEE Solicitation Module by signing and returning the front page of each amendment to the Point of Contacts (POCs) identified in Table L.2 no later than the date and time specified in the amendment(s).

L.1.2.3. Submission, Modification, Revision, and Withdrawal of Proposals. Proposals shall be submitted via these instructions to the POCs identified in Table L.2. Proposals may be withdrawn by written notice received at any time before award.

L.1.2.4. Organization / Number of Copies / Page Limits L.1.2.4.1. The Offeror’s proposal shall include the solicitation number, name, address, telephone numbers, and email address of the Offeror. The Offeror shall prepare the proposals as set furth in the Proposal Organization Table (Table L.1). The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits and with the number of copies as specified in Tables L.1 and L.2. The contents of each proposal volume are described in the paragraphs below:

L.1.2.4.2. Page Limitations. Page limitations for each volume are listed in Table L.1 above and shall be treated as a maximum. Each page shall be counted except for the following: the transmittal letter, cover pages, tab-divider pages, title pages, table of contents, cross-reference matrix (cross-referencing is permitted when it is used within proposal volume; cross-referencing between volumes is not permitted), lists of tables and drawings, glossary or acronyms, Section J, or organization structure. If the proposal exceeds the page limitation, the excess pages at the end of proposals will not be read or considered for evaluation. Page limitations may also be placed on responses to Evaluation Notices (ENs). If negotiations are conducted, the specified page limits for EN responses will be identified in the letters forwarding the ENs to Offerors.

L.1.2.4.3. Page Size and Format. Narrative documentation shall be submitted in Microsoft Word as well as converted into a searchable PDF (version Office 2010 or newer). Page size shall be 8.5x11 inches, except for “foldouts” described in L.1.2.4.4. Text shall be single-spaced, Times New Roman, and not less than 10 font size. Tracking and leading values shall not be changed form the default values of the word processing or page layout software. Use at least 1-inch margins on top and bottom and ¾-inch side margins. Pages shall be numbered sequentially by volume. If negotiations are conducted, these page size and format restrictions shall apply to responses to ENs.

L.1.2.4.4. Foldouts. Legible tables, charts, graphs, and figures shall be used wherever practical to depict organizational structures, system layouts, implementation schedules, and project plans. These displays shall be uncomplicated, legible, and limited to a maximum page size of 11x17 inches. Foldout pages shall fold entirely within the volume and each printed side shall count as a single page. Foldout pages may only be used for large tables, charts, graphs, diagrams, and schematics, and shall not be used for pages of text. For all tables, charts, graphs, and figures, the font shall be no less than Times New Roman 10-point font with normal character spacing.

L.1.2.4.5. Cost or Pricing Related Data Offerors shall ensure that no cost or pricing information is included in any proposal volume except for Volume III (Cost/Price). Technical volumes may include labor hour estimates and material quantities only to the extent required to demonstrate the feasibility of the technical approach or to provide rationale for proposed designs and alternatives.

L.1.2.4.6. Cross-referencing between proposal volumes is not permitted. Each volume shall be written on a stand-alone basis so its contents may be evaluated individually. Information required for proposal evaluation which is not found in its designated volume will be assumed to be omitted from the proposal.

L.1.2.4.7. Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity.

L.1.2.4.8. Indexing. Each volume shall contain a detailed table of content to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections. Tabs do not count against the page limitations for their respective factors.

L.1.2.4.9. Abbreviations and Acronyms. Each volume shall contain a glossary of all abbreviations and acronyms used, and an explanation for each. Glossaries do not count against the page limitations for their respective volumes.

L.1.2.4.10. Labeling. Include a cover page in each volume, clearly marked as to volume number, solicitation identification, and Offeror’s name, office phone (if applicable, cell phone number), and email address for the proposal point of contact.

L.1.2.4.11. Communications. All exchanges of source selection information between the Government and the Offerors will be controlled by the PCO. Source selection information will be transmitted to Offerors electronically, e.g., via email, or the Solicitation Module within the Procurement Integrated Enterprise Environment (https://piee.eb.mil/). If transmitted via email, the transmission shall be sent and received encrypted and shall include “Source Selection Information – See RFO 2.101 & 3.104” in the Subject line.

L.1.3. Submissions.

L.1.3.1. All volumes shall be developed in Microsoft Word and Excel (version Office 2010 or newer). Narrative documentation shall be submitted in Microsoft Word as well as converted to searchable PDF. Excel spreadsheets shall remain in Excel (xlsx) format.

L.1.3.2. PIEE Solicitation Module. Proposal volumes shall be submitted using the PIEE Solicitation Module. Registration instructions have been included in the PIEE Vendor Registration attachment. Training videos can be accessed within the web-based training module in PIEE for the use of the solicitation module and the submission of proposals.

L.1.3.3. It is the Offeror’s responsibility to confirm receipt of all formal communications and proposal submission via email.

L.1.3.4. Late proposals will be processed IAW RFO 52.215-1(c)(3), Submissions, Modification, Revision, and Withdrawal of Proposals.

L.2. Distribution L.2.1. Solicitation Questions. The CO is the sole point of contact for this acquisition. Questions pertaining to the solicitation or any of its attachments shall be submitted in writing, using the Solicitation attachment “Question and Comment Form” provided in Section J. Any questions or concerns shall be addressed to all POCs listed in table L.2. below.

Questions pertaining to the solicitation shall be submitted no later than 14 calendar days after the date of the solicitation's release. If this deadline falls on a weekend or a U.S. Federal holiday, the deadline shall be extended to 16:00 Central European Summer Time (CEST) on the next business day. The Government will not be required to answer questions submitted after this deadline.

The Government will post all questions received, along with the Government’s official response, as an amendment to the solicitation on SAM.gov and the PIEE solicitation module. Questions will be published without attribution to the source of the inquiry.

L.2.2. The four (4) volumes shall be submitted IAW the instructions and due dates below. The cover letter is a standalone document and shall be submitted with volumes I and II.

L.2.2.1. Document Submission. All volumes, including the cover letter, shall be submitted via the PIEE Solicitation Module NLT 1600 on 05 October 2026. The Government will not accept proposals or parts of proposals submitted via email. The Past Performance Questionnaire (PPQ) attachment provided in Section J may be submitted directly by the respondent to the POCs listed in Table L.2.

L.2.2.1.1. Offeror Company Information / Cover Letter. The Offeror shall provide a cover letter with all of information listed below:

· Full Company Name

· Company Address

· CAGE Code

· UEI #

· Taxpayer Identification Number (TIN),

· System for Award Management (SAM.gov) registration date

· Proposal validity statements

· Contracting and technical POCs (name, email address, and phone number)

· POC authorized to obligate the company (name, email address, and phone number)

· A statement that the Offeror’s company understands the requirements specified in the PWS will meet the performance standards and requirements therein.

· A statement that the Offeror’s company does or does not take exception to any of the requirements of the PWS, or terms and conditions of the resulting contract. Exceptions taken shall be clearly identified and defined, as applicable.

L.2.2.2. Volumes I through IV shall be submitted NLT 1600 on 05 October 2026 and shall be submitted via the PIEE solicitation module only.

Table L.2. – Distribution / Contact Information Table L.2. – Distribution / Contact Information

For Türkiye Base Operating Support Services (T-BOS) IDIQ – PIEE Solicitation Module and Email

Mr. John McLaurin Contracting Officer (Primary)

764 ESS/PKA

Email: john.mclaurin.1@us.af.mil Ms. Christin Buck Contract Specialist (Primary)

764 ESS/PKA

Email: christin.buck.de@us.af.mil

** All communication shall reference solicitation FA5641-26-R-0005

L.2.2.3. Debriefings. The PCO will promptly notify Offerors of any decision to exclude them from the competitive range IAW RFO 15.204(a). Excluded Offerors may request a pre-award debriefing IAW RFO 15.206, or they may choose to wait for a post-award debriefing IAW RFO 15.301; however, they are entitled to no more than one debriefing per proposal. For Offerors remaining in the competitive range, the PCO will provide notification of the source selection decision IAW RFO 15.204(b). Offerors desiring a debriefing must submit a written request to the PCO IAW the timeframes and requirements specified in RFO 15.206 or RFO 15.301, as applicable.

L.3. Volume I: Past Performance L.3.1. General. The Past Performance Volume shall be prepared and organized IAW the subject instructions and shall be separate form all other volumes of the proposal.

The Government will require a minimum of two (2) but will not evaluate more than five (5) references. For each reference the Offeror shall submit a Past Performance Information Form and a supporting narrative.

The following will apply:

L.3.2.1. The Past Performance Volume shall be organized according to the following outline:

a) Table of Content

b) Summary Page

c) Past Performance Narrative

d) Past Performance Information (PPI) Worksheet (Section J, Attachment PPI) (PPI worksheets do not count against the page limitation (40 pages) for Volume I – Past Performance.

e) Specific Content

f) Subcontractor Letters of Consent / Client Authorization Letters Attachment provided in Section J

g) Organizational Structure Change History

h) Glossary L.3.2.2. Volume I – Past Performance shall contain a detailed table of contents to delineate the subparagraphs within that volume.

L.3.2.3. Summary Page. The summary page is limited to one (1) page. The Offeror shall describe its role and the role of each subcontractor for whom the Offeror is electing to provide Past Performance IAW Section L. The summary page shall also indicate a percentage and type of work the Offeror and subcontractor(s) will perform.

L.3.2.4. Past Performance Narrative The burden of providing clear, concise, and verifiable information rests solely with the Offeror. The Government is not obligated to seek out missing information. A proposal that fails to provide the specific data required to demonstrate recency and relevancy may be rated as Unacceptable.

L.3.2.5. Past Performance Information (PPI) Worksheet. (Section J, Attachment PPI). For each contract reference submitted, the Offeror shall complete a Past Performance Information Worksheet. This Worksheet will require the Offeror to provide general information about the contract, including contract number, customer name, total contract value, period of performance, and a point of contact (name, title, current email address, and phone number) for the customer who can verify the performance information provided. The Offeror shall submit a minimum of two (2) and a maximum of five (5), contract references for projects that are recent and relevant to the requirement in this solicitation, as specifically defined in Section M – Evaluation Criteria. Contracts may include federal, state, and local Government and commercial customers. Each PPI Worksheet must cover recent and relevant performance consistent with the definitions in Section M, paragraphs M 3.4 and M 3.5, in demonstrating their ability to perform the proposed effort. The length of the PPI Worksheets is limited to no more than seven (7) pages. PPI Worksheets do not count against the page limitation (40 pages) for Volume I.

L.3.2.6. Ordering-Type Contracts Submission: For ordering-type contractual vehicles (e.g., Indefinite-Delivery/Indefinite-Quantity (IDIQ) “D” type contracts per RFO Subpart 16.5), the Government recognizes that continuous services are frequently executed via multiple, concurrent Task Orders or Delivery Orders under a single overarching contract vehicle:

a) IDIQ as a Single Reference: An Offeror may submit one (1) PPI Worksheet using the basic IDIQ contract number as a single contract reference, provided the overarching IDIQ includes a defined baseline BOS scope and the combined TOs demonstrate continuous BOS performance for at least one consecutive twelve (12) month period.

b) Consolidation of Task Orders: For the purpose of demonstrating Relevancy (Size/Magnitude and Scope), all TOs/DOs issued under the single IDIQ vehicle within a specified, continuous 12-month period may be consolidated and evaluated by the Government as a single annual performance period.

c) Official Verification: To verify the scope and support the average annual funded value calculation without requiring an exhaustive, page-consuming list of individual TOs, the Offeror shall submit official Government documentation (e.g., annual obligation reports, official contract funding summaries, FPDS-NG data extracts, or a formal certification letter signed by the cognizant Contracting Officer). This documentation must clearly demonstrate the total aggregate dollar value of BOS-related TOs issued under the IDIQ for the specified 12-month period. This supporting documentation shall be included as an appendix in Volume I and will not count against the Past Performance page limits. Detailed TO-level data is not required unless specifically requested by the Government during clarifications or discussions.

L.3.2.7. Recency. To be recent, a contract reference will be considered if the effort is currently ongoing, or if it was completed within the last five (5) years from the date of this solicitation's issuance.

L.3.2.8. Relevancy. A contract will be considered relevant if it demonstrates experience of similar size, scope and complexity to the requirement described in this solicitation. To be considered relevant, a contract must meet, at a minimum, the criteria in paragraphs a), b) and c) below.

a) Size/Magnitude. State the average annual funded value of the contract. Provide verifiable data showing how this value was calculated. For IDIQ/Multiple Award Contract references, this data must be for the specific TOs being submitted. The narrative must demonstrate the referenced contract effort has an average annual funded value of $20 Million or more.

b) Scope and Complexity. Describe the BOS-like functions performed as a prime contractor and state the average size of the direct-hire, unionized workforce managed.

The Government will consider the degree of similarity to the PWS requirements, including experience in areas such as:

1. Management of Civil Engineering and Logistics functions

2. Facility infrastructure and maintenance

3. Management of a unionized workforce of at least 200 direct employees.

c) OCONUS Experience. To be considered relevant, at least one (1) of the submitted contract references must demonstrate the Offeror’s experience as a prime contractor performing services at a major OCONUS installation. A major OCONUS installation is defined as a single, geographically co-located site outside of the Continental U.S. that meets at least two (2) of the following criteria:

1. Support a daily base or campus population of 500 or more personnel. For the purpose of this evaluation, “supported population” includes all assigned military, civilian, and host nation employees, as well as all resident family members.

2. Encompassed a portfolio of at least 250 individual facilities for which the offeror provided direct maintenance and operational support.

3. Provided direct support to a high-tempo operational, industrial, or logistical mission requiring 24/7 emergency response capabilities.

L.3.2.9. Past Performance Submission Instructions. To allow the Government to assess performance quality as defined in Section M the Offeror shall provide the following for each recent and relevant contract reference.

a. CPARS records: For all referenced contracts that have a Contractor Performance Assessment Reporting System (CPARS) record, the Government will download the official reports. The Offeror shall ensure all contract and order numbers are accurate to facilitate the retrieval of these records.

b. Past Performance Questionnaires (PPQ) for Non-CPARS Contracts The Government's preferred method for assessing performance quality is through CPARS. A Past Performance Questionnaire (PPQ) is not required for any contract reference that has a CPARS record. The PPQ shall only be submitted for contract references where CPARS data is not available (e.g., non-U.S. Government, state, local, or commercial contracts). For such references, the Offeror shall::

1. Complete the relevant sections of the PPQ provided as Attachment PPQ to this solicitation.

2. Send the PPQ to the client’s point of contact for that contract.

3. Instruct the POC to complete the questionnaire and email it directly to the PCOs no later than the proposal submission deadline.

4. The responsibility for ensuring the completed PPQ is returned rests solely with the Offeror. PPQs submitted directly by the Offeror will be considered unacceptable.

c. Addressing Adverse Past Performance: If an Offeror has a record of ‘Marginal’ or ‘Unsatisfactory’ (or equivalent) ratings on a recent and relevant contract, the Offeror is encouraged to provide a narrative explanation. (if not already included in the Contractor’s Response section of the CPARs) This narrative should be no more than two (2) pages per occurrence and should address the circumstances of the rating and any corrective actions taken to prevent recurrence. This information should be included in the Past Performance Volume of the proposal.

L.4. Volume II: Technical L.4.1. Subfactor 1: Personnel Management, Leadership and Process Innovation. This subfactor requires the Offeror to submit a series of binding operational plans, processes, and formal commitments that guarantee immediate workforce stability while simultaneously modernizing daily reporting and data integration. The Government requires definitive, actionable commitments that seamlessly execute personnel retention, mandatory training, and low-risk technological integrations (e.g., advanced dashboarding and AI-assisted data synchronization). All proposed timelines, staffing metrics, and technical processes submitted under this subfactor will be incorporated into the resulting contract as binding performance obligations. The Offeror shall provide a comprehensive narrative detailing the following five (5) distinct, actionable elements. Failure to provide complete, definitive plans and commitments for all required elements will render the proposal technically unacceptable and ineligible for award:

L.4.1.1. Element 1: Key Personnel Continuity & Agile Management Plan. The Offeror shall submit a Key Personnel Continuity Plan. The Plan must describe the Offeror’s strategies for:

a) Retention: Describe specific, proactive strategies to ensure the long-term stability of the management team. Provide documented evidence of corporate retention programs and, where available, quantifiable metrics (e.g., historical retention rates for similar BOS efforts)

b) Recruitment and Talent Pipelining: Describe the process for rapidly sourcing and vetting candidates for critical roles, with emphasis on proactive strategies for identifying and pre-screening potential replacements before a vacancy occurs to ensure mission continuity.

c) Key Personnel Position Standards (No Resumes): For each Key Personnel position listed in Clause H2, the Offeror shall provide:

1. A Detailed Position Description: Outlining the specific duties, authorities, and responsibilities of the role within the proposed organizational structure.

2. Minimum Qualification Requirements: Clearly defining the mandatory minimum standards the Offeror will require for an individual to fill the position, to include specific educational degrees, years of relevant experience, and professional certifications L.4.1.2. Element 2: Workforce Training & Certification Plan. The Offeror shall submit a plan detailing:

a) The process for New Employee Onboarding and Initial Training.

b) The proposed system and methodology for Certification Management and Tracking.

c) The approach to Continuing Education and Skill Sustainment.

L.4.1.3. Element 3: Comprehensive PWS Performance Dashboards: The Offeror shall provide high-fidelity visual mock-ups (e.g., Power BI, Tableau, or equivalent) of their proposed Integrated Data Management System (IDMS) dashboards. The mock-ups must visualize, at a minimum, all Key Performance Indicators (KPIs) for each functional area as listed in the table in Section M, Paragraph M.4.3.3. The submission must also include a supporting data dictionary that defines the data sources and calculation methodology for each KPI presented.

a) Optional Advanced Dashboard Capabilities: To be considered for a higher adjectival rating under the "Differentiators" criteria in Section M.4.3.3(a), the Offeror is encouraged to provide mock-ups and supporting data dictionary entries demonstrating advanced capabilities, including but not limited to:

1. Diagnostic & Constraint Visibility (e.g., AWP or resource bottleneck tracking)

2. Proactive Performance & Quality Management (e.g., work order aging or rework/first-time fix tracking)

3. Advanced Analytics & Mission-Focused Grouping (e.g., granular drill-down capabilities or predictive asset degradation analytics) L4.1.4 Element 4: Systems Integration & Data Readiness. The Offeror shall provide a definitive Systems Integration and Data Readiness Plan detailing its exact processes for capturing, formatting, and migrating active operational records, completed and ongoing maintenance logs, and daily service execution data generated in support of PWS requirements into the new operational environment. This plan must be written so that its processes and timelines can be incorporated as binding contract requirements upon award.

To be evaluated as Acceptable, the Offeror’s plan must:

a) Define the Dashboard Hosting Environment, stating and demonstrating that it will be hosted in a secure cloud environment that is, at a minimum, FedRAMP Moderate authorized and possesses a DoW Provisional Authorization (PA) at Impact Level 5 (IL5) for the protection of Controlled Unclassified Information (CUI) extracted from Government systems.

b) Detail the manual or semi-automated Data Synchronization Process for transferring data to Government systems without placing any data entry or administrative burden on Government personnel.

c) Detail the Offeror's operational process to train, clear, and equip its NIPR-cleared workforce to utilize Government-furnished AI tools to process and synthesize exported operational data. The plan must commit to and detail at least one (1) viable process or technological improvement that does not require additional Government funding or new NIPRNet software Authorities to Operate (ATOs).

d) To be eligible for potential additional credit (a Strength), the Offeror’s plan must explicitly detail its exact processes for utilizing Government-furnished Artificial Intelligence (AI) tools (e.g., the GenAI.mil suite). The Offeror must provide a credible, step-by-step operational workflow demonstrating how its workforce will utilize these tools to accelerate data processing, reduce manual manipulation, and verify data integrity within the Government's security constraints. The proposal must define the objective metrics (e.g., hours saved, reduction in step count) the Offeror expects to achieve through this workflow.

L.4.1.5. Element 5: Workforce & Process Innovation Plan. The Offeror shall submit a plan detailing the implementation of low-risk technologies to enhance workforce efficiency. The plan should include specific details on the proposed use of:

a) Augmented & Virtual Reality (AR/VR) for remote expert support and immersive training.

b) AI-Powered Root Cause Analysis using DoD-approved AI capabilities or adopting future Government-furnished AI tools.

Enforceability of Innovations and Contractor Furnished Equipment (CFE): Offerors proposing advanced technological capabilities, dashboards, or process innovations (e.g., Augmented & Virtual Reality (AR/VR)) must explicitly map these capabilities to a specific CDRL deliverable or propose them as a binding supplement to the PWS. Additionally, all costs associated with proposed CFE must be incorporated into the proposed prices in Volume III; no separate CLINs will be provided.

L.4.1.5.1. Use of Contractor-Furnished Equipment (CFE) and Innovation Enforceability: If the Offeror proposes the use of CFE (e.g., specialized hardware, software licenses, or ergonomic tools) to execute the process innovations described within the Workforce & Process Innovation Plan, the Offeror must explicitly identify those items within the Technical Volume. The Technical Volume narrative must clearly describe how the proposed CFE provides a tangible benefit to the Air Force mission and must explicitly map the deployment of such CFE to a specific, binding Contract Data Requirements List (CDRL) deliverable or propose it as a binding supplement to the PWS. Note on Pricing: While the technical application of CFE must be detailed in Volume II, Offerors are strictly cautioned that no separate CLINs will be established for CFE acquisition. All allowable, allocable, and reasonable costs associated with the capital investment, lease, or maintenance of proposed CFE must be fully detailed and proposed as direct or indirect costs within the Cost Proposal (Volume III). Proposing technical innovations in Volume II without a corresponding, realistic cost buildup in Volume III will be evaluated as a performance risk under the Government's Cost Realism analysis.

L.4.2. Subfactor 2: Staffing, Compliance & Logistics. (Unacceptable/Acceptable) This subfactor requires the Offeror to demonstrate the realism, sufficiency, and legal compliance of their foundational operational and transition plans. The Offeror shall provide a comprehensive narrative and supporting documentation detailing their approach to staffing the requirement, executing a seamless 90-day phase-in, and securing the mandatory Turkish legal representation required to navigate the host-nation labor environment. The Offeror’s response must clearly address the three (3) distinct elements detailed below. Failure to provide complete and adequate responses to all required elements may render the proposal technically unacceptable and ineligible for award.

L.4.2.1. Element 1: Staffing Plan and Basis of Estimate. The Offeror shall submit a comprehensive Organizational Chart, a detailed Staffing Plan, and a supporting Basis of Estimate (BOE). The supporting Basis of Estimate (BOE) shall be submitted as a separate file with no page limit, as specified in Table L.1.

a) Organizational Chart: The Offeror shall provide an organizational chart that clearly defines the lines of authority and responsibility from the corporate/reach-back level down to the on-site functional leads and supervisory positions. The chart must identify the placement of all Key Personnel positions and must align with the corresponding FTE counts provided in the Staffing Plan. Offerors are encouraged to highlight clear, streamlined lines of authority that maximize workforce resilience and oversight.

b) Staffing Plan: The Staffing Plan must provide the proposed Full-Time Equivalent (FTE) count for each PWS function at the working level, clearly rolling up to the supervisory positions identified in the Organizational Chart. To be considered for a higher adjectival rating under the "Differentiators" criteria in Section M, the Offeror should provide details on any proposed Corporate Reach-Back mechanisms for surge and emergency response, and any formal Turkish Regulatory Compliance and Certification Pipeline partnerships. Any proposed organizational approaches must strictly adhere to the PWS and Turkish Collective Labor Agreement (CLA) prohibitions on dual hatting.

c) Basis of Estimate (BOE): The supporting BOE must clearly describe the Offeror’s methodology for calculating the proposed FTEs and include, at a minimum:

1. Planning Factors: The specific planning factors (e.g., labor hours per task, industry standards) used to convert the Government's workload data into total required labor hours.

2. Productive Hours: The calculation of Productive Hours per FTE, detailing how the Offeror accounted for all non-productive time (e.g., host nation holidays, vacation, leave, training).

3. Final Calculation: The final mathematical calculation showing how the total required labor hours were divided by the productive hours to arrive at the proposed FTE count.

L.4.2.2. Element 2: Phase-In Plan. The Offeror shall submit a comprehensive, binding project plan for the ninety (90) day phase-in period. The plan must include a detailed Integrated Master Schedule (IMS) in Microsoft Project format and a supporting narrative detailing how the Offeror will assume full operational responsibility on Day 91 with zero disruption to the mission. The plan must, at a minimum, address the following five (5) key transition activities:

a) Operational Stand-Up: Detail the schedule and processes for establishing or transitioning local business registration in Türkiye, setting up local corporate banking, securing a Turkish Tax Identification Number (Vergi Kimlik Numarası), and the formal, early engagement of the qualified Turkish legal, tax, and labor advisors proposed under Element 3.

b) Leadership Onboarding and Relocation: Detail the specific timeline and milestones for the mobilization and relocation of all Key Personnel, securing mandatory Host Nation base access, and obtaining all required Turkish work permits, visas, and residence clearances.

c) Incumbent Workforce Capture and In-Processing (Türk Harb-İş CLA Status Notice): Detail the strategy for transitioning, vetting, and in-processing the existing Local National (LN) workforce in strict compliance with Turkish Labor Law (No. 4857) and the active Collective Labor Agreement (CLA) with the Türk Harb-İş Union, specifically addressing the assumption or mitigation of accrued seniority and severance (Kıdem Tazminatı) liabilities.

CLA STATUS NOTICE & PRICING INSTRUCTIONS: Offerors are hereby notified that the next iteration of the Türk Harb-İş CLA is currently under bilateral negotiation and has not yet been finalized. For the purpose of preparing initial proposal volumes and cost build-ups, Offerors shall utilize the current, existing CLA (inclusive of all active amendments and wage tables) provided in Section J, Attachment [X]. Once the new CLA is finalized and executed by the coordinating authorities, the Government will formally incorporate the updated CLA, wage rates, and benefits tables into this solicitation via a formal RFP Amendment. Offerors will be given adequate opportunity to adjust their Technical and Price proposals accordingly prior to the submission of Final Proposal Revisions (FPRs)

d) Government-Furnished Property (GFP) and Historical Data Transfer: Detail the joint inventory schedule and processing workflows for taking 100% accountability of all GFP and historical operational data files in coordination with the incumbent contractor and the Government.

e) Supply Chain Transition and Local Vendor Agreements: Detail the processes for transitioning critical local vendor agreements, securing required local subcontractors, and establishing secure supply chains within Türkiye to guarantee seamless logistical support on Day 91.

L.4.2.3. Element 3: Turkish Labor Law and Legal Counsel. The Offeror shall submit documented proof of a commitment from a Turkish-licensed attorney or attorney partnership established in the Republic of Türkiye to provide dedicated legal counsel and representation regarding Turkish labor relations upon contract award. The Offeror shall submit the following executed documents to demonstrate compliance:

a) Conditional Agreement or Letter of Commitment: A complete copy of a signed Letter of Commitment, Memorandum of Agreement (MOA), or Conditional Retainer between the Offeror and a Turkish-licensed attorney or attorney partnership established in the Republic of Türkiye This document must be signed by authorized representatives of both parties and must explicitly state that the the attorney or attorney partnership commits to providing legal representation on matters concerning the applicable Türk Harb-İş Collective Labor Agreement (CLA) Turkish Labor Law No. 4857 and Unions and Collective Labor Agreement Law No. 6356 contingent upon, and effective immediately at, contract award.

b) Qualifications Statement: A capability statement or professional profile (maximum 3 pages, excluded from the overall Technical Volume page limit) from the retained attorney or attorney partnership demonstrating:

1. Proof that the attorney is actively licensed to practice law in the Republic of Türkiye or in the case of an attorney partnership that the partnership is duly established in accordance with Turkish law and the attorneys assigned to perform the services are duly admitted to practice law in Türkiye

2. A minimum of five (5) years of direct corporate experience representing corporate or government clients in Turkish labor courts, specifically handling labor disputes, union negotiations, or employee terminations under the jurisdiction of Turkish Labor Law.

L.4.2.4 Element 4: Systems Integration & Security. The Offeror shall provide a clear, executable roadmap detailing their process for securely integrating operational data. The roadmap must demonstrate how operational data moves from the point of origin (e.g., a technician’s mobile tablet in the field) to the Offeror's dashboard system, and ultimately how it is synchronized with mandatory Government systems like NexGen IT. For the purpose of this proposal, Offerors shall assume that no new, third-party, contractor-provided software (e.g., Robotic Process Automation (RPA) bots, middleware) will be granted an Authority to Operate (ATO) on the Government's NIPRNet.

The Offeror's roadmap must, at a minimum:

a) Define the Dashboard Hosting Environment: Explicitly state and provide supporting rationale demonstrating that the proposed dashboard system will be hosted in a secure cloud environment that is, at a minimum, FedRAMP Moderate authorized and possesses a DoW Provisional Authorization (PA) at Impact Level 5 (IL5) for the protection of Controlled Unclassified Information (CUI) extracted from Government systems.

b) Detail the Manual Data Synchronization Process: Provide a detailed, step-by-step description of the manual or semi-automated process for synchronizing data between the contractor's system and the Government's NIPR-based NexGen IT system. This plan must explicitly demonstrate how the data transfer will be accomplished securely and without placing any administrative or data entry burden on Government personnel. Acceptable methods include, but are not limited to, the use of scheduled, formatted CSV spreadsheet uploads or other secure flat-file transfer techniques.

L.5. Volume III: Price Critical Compliance Notice: This volume contains mandatory instructions for the preparation of the Price/Cost Proposal. Offerors must strictly adhere to the structural, mathematical, and systems requirements detailed herein. Failure to provide fully active formulas, complete cost build-ups, or required system adequacy evidence may result in a determination of non-responsiveness and exclusion from evaluation.

L.5.1.1. Table of Content: The Offeror shall include a detailed table of contents at the beginning of this volume, mapping all major sections, subsections, tables, and appendices to their respective page numbers.

L.5.1.2. Glossary of Terms and Abbreviations: The Offeror shall provide a comprehensive glossary defining all terms, acronyms, and abbreviations utilized throughout this Price/Cost volume to ensure clarity and consistent interpretation by the Government evaluation team.

L.5.1.3. Estimating System: The Offeror shall provide a summary description of its standard estimating system or methodology. The summary description shall cover separately each major cost element, including but not limited to:

Direct Labor Indirect Costs (Fringe, Overhead, and General & Administrative) Other Direct Costs (ODCs) Identify any deviations from stated standard estimating procedures in preparing this cost proposal volume. Indicate whether Government approval of the stated system was obtained and, if so, provide formal evidence of such approval.

L.5.1.4. Ground Rules and Assumptions: The Offeror shall provide a detailed explanation of the ground rules and assumptions necessary to fully understand the cost estimates. Topics to be addressed should include, but are not limited to: business base, labor and overhead rates, cost-sharing arrangements, prime-subcontractor relationships, and Price/Cost escalation.

L.5.1.6. Cost Accounting Standards (CAS) Disclosure Statement Offerors shall include a current Cost Accounting Standards (CAS) Disclosure Statement as part of this volume.

L.5.1.7. Subcontractor Information The Offeror shall provide a comprehensive list of all subcontractors supporting this effort.

L.5.2. Submission Guidelines and Proposal Adequacy Although not required for other than certified cost or pricing data, the Government recommends Offerors utilize Table 15-1 – Instructions for Submitting Cost/Price Proposals When Certified Cost or Pricing Data Are Required, located at RFO 15.408-2 and the Proposal Adequacy Checklist located at DFARS 252.215-7993 (DEVIATION 2026-O0048) in the development of the cost proposal. In the event certified cost or pricing data becomes required, the Offeror shall conform to the Proposal Adequacy Checklist.

L.5.3. Page Limitations: The Price/Cost volume contains no page limitations. However, all information provided must relate directly to Price/Cost. Price/Cost information submitted outside of the designated Price/Cost proposal volumes will not be evaluated.

L.6. Price/Cost Proposal L.6.1. Cost Model Format The Price/Cost Proposal shall consist of a Price/Cost Narrative and a Price/Cost Model (Microsoft Excel spreadsheet). The Offeror shall submit a Microsoft Excel cost model in their own format. While the Government does not prescribe a rigid template, the Offeror’s Excel model must adhere to the following strict mathematical and structural standards to be considered complete:

· Formula Integrity: All formulas, calculations, mathematical relationships, and sheet-to-sheet links must be visible, active, and unlocked. Hard-coded values are strictly prohibited for any calculated field (e.g., subtotals, totals, indirect applications, or fee calculations).

· Traceability: The Government must be able to trace all calculations from the lowest level of detail (e.g., base labor rates and hours) through the indirect rate and fee applications, up to the final CLIN prices.

· Unlocked File: The Excel file must not contain any hidden rows, hidden columns, hidden sheets, password protections, or locked cells.

L.6.2. Separation of FFP, CPFF, and CR CLINs The Offeror's cost model and accompanying Cost Narrative must clearly differentiate between Firm-Fixed-Price (FFP) CLINs, Cost-Plus-Fixed-Fee (CPFF) CLINs, and Cost Reimbursable (CR) CLINs. The following table outlines the specific submission and evaluation requirements for each CLIN type:

L.6.2.3. Required Other Than Certified Cost or Pricing Data (CPFF CLINs Only) The Price/Cost Proposal must be strictly aligned with the Offeror’s Technical Volume. All resources, tools, labor hours, and materials proposed to execute the technical approach must be clearly accounted for in the Price/Cost Proposal. Inconsistencies between the resources proposed in the Technical Volume and the costs proposed in Volume III may negatively impact the Cost Realism evaluation and may result in upward adjustments to the MPC. To support the Cost Realism evaluation of the CPFF CLINs IAW Section M of the solicitation, the Offeror’s Excel model must include separate, clearly labeled worksheets for each CPFF CLIN and include a full cost buildup detailing the following cost elements:

· Direct Labor: Detail the proposed labor categories, unburdened hourly rates, and proposed hours and period of performance. Provide a clear Basis of Estimate (BOE) for the proposed labor categories and hours, and supporting documentation for the base labor rates (e.g., actual payroll records, signed letters of intent, or salary surveys).

· Other Direct Costs (ODCs): Provide a detailed cost buildup of all ODCs with a clear Basis of Estimate (BOE) (e.g., travel, materials, equipment, etc.).

· Subcontractor: Provide a prime contractor price evaluation report and full cost build-up for all subcontractors supporting CPFF CLINs. (Subcontractors supporting CPFF CLINs must submit their own detailed, active Excel models).

· Indirect Rates: The cost model shall specify each individual indirect rate (e.g., Fringe, Overhead, G&A) and contain Excel formulas that indicate the exact base to which each rate is applied and each separately calculated indirect cost. To substantiate the proposed indirect rates, offerors shall provide a copy of the current DCMA Forward Pricing Rate Agreement (FPRA) or Forward Pricing Rate Recommendation (FPRR) if applicable, or Independent Accounting Firm Audit Reports supporting proposed indirect rates, or three (3) to five (5) years of historical indirect rate actual cost data. Offerors without an FPRR/FPRA, independent audit reports, or historical rate actuals shall submit a detailed, forward-looking budget and projection of indirect cost pools and allocation bases for the upcoming fiscal years, supported by a clear narrative explanation.

· Fee Worksheet: Clearly indicate the Fixed Fee rate and the calculation of the proposed Fixed Fee cost, ensuring it is calculated only on appropriate cost bases and does not exceed statutory fee limitations at RFO 15.404-9(c)(4).

L.6.2.4. Unbalanced Pricing Prevention Offerors are cautioned against submitting unbalanced pricing.