Draft Sections L_M JSF Security.docx

SECTION L – INSTRUCTIONS TO OFFERORS

PART A: GENERAL INSTRUCTIONS

L.1 GENERAL

This Request for Proposal (RFP) is a single award, competitive Unrestricted procurement. The procurement will be conducted in accordance with Federal Acquisition Regulation (FAR) Subpart 15.2, Evaluation and Award.

Proposal Preparation and Submission Instructions:

a) The Government intends to evaluate proposals and award a contract without negotiations with offerors. Therefore, the offeror’s initial proposal should contain the offeror’s best terms from a price or price and technical standpoint. However, the Government reserves the right to conduct negotiations if it is determined by the Contracting Officer to be necessary.

b) Offerors are responsible for submitting proposals that:

1. Clearly demonstrate an accurate understanding of the requirements and associated risks, AND

2. Provide a viable and effective approach to meeting the requirements.

c) Proposals shall be clear, concise, complete, compliant and shall include sufficient detail to allow for effective evaluation and validation of claims. Simply rephrasing or restating the Government’s requirements is insufficient. Instead, Offerors shall provide a compelling rationale that explains how they will meet the requirements and ensure successful performance. To ensure accurate analysis by automated evaluation tools and maintain the integrity of the source selection process, the following restrictions apply:

i. Visible Text Only: All proposal content must be presented as visible text. The inclusion of any concealed text is strictly prohibited. Concealed text includes but is not limited to:

A. Micro-text (text with a font size below 8pt);

B. White text on a white background;

C. Text utilizing colors that render it indistinguishable from the background;

D. Text hidden within images or graphics.

d) For the purposes of this solicitation, the terms ‘complete’ and ‘compliant’ are defined as follows:

1. Completeness: A proposal is considered complete when all information, documents, attachments, and forms required by Section L are submitted. Omission of any required item may result in the proposal being deemed incomplete and therefore ineligible for evaluation.

2. Compliance: A proposal is considered compliant when it adheres to all instructions, conditions, and requirements of the RFP, including but not limited to formatting (e.g., page limits, font), submission deadlines, and use of Government-provided templates. Unauthorized deviations to templates may result in the proposal being deemed non-compliant and therefore ineligible for evaluation.

Key Submission Guidelines:

a) All information, including the Offeror’s best price, shall be included in the initial proposal.

b) Alternate proposals are not permitted.

c) Deviations or exceptions to any terms or conditions of the RFP are not allowed unless explicitly authorized in the RFP. Proposals containing unauthorized deviations may be deemed unacceptable and ineligible for award.

d) Avoid duplicating information across volumes. If overlap exists, include detailed information in the most logical section and provide summaries or references in other areas.

e) Except for Past Performance and the Price volume, no pricing information should appear in any other volume.

The Government intends to enforce all the proposal submission requirements outlined in Section L.

Failure to submit a complete and compliant proposal may result in a “Deficiency”, thereby making an offer Unawardable and the Offeror being eliminated from this competition without further consideration.

L.2 PROPOSAL FORMAT

a) The page limit, as outlined in the table below, applies to the total pages within a file, excluding the table of contents, cover page, and glossary pages (to include acronym lists and lists of figures) as well as government templates. Pages containing text shall use standard letter size (8.5 x 11”) and be formatted in Microsoft Word and Adobe PDF in a searchable format, as applicable. The Government requires both the Word and pdf formats unless it requires altering Government documents (e.g., SF30s, SF33s, or RFP document fill-ins (such as Reps and Certs), templates or official company documents. Text shall be in a minimum 12-point Times New Roman font with margins no less than one inch. Tables and graphics shall use a minimum 10-point Times New Roman font. Drawings or graphics may be reduced in size, provided legibility is maintained.

b) Graphs and tables shall use a minimum 10-point font and include a grid for easy interpretation of values. Graphs and tables fitting on an 8.5” x 14” page will count as one page. Drawings, regardless of size, will also count as one page. Graphic resolution shall be sufficient to ensure clear interpretation of data. Required substantiating and supporting documents in a government-issued format are exempt from these formatting requirements. When using government-supplied templates, no modifications to font or scaling are necessary. All text must apply uniform formatting throughout the proposal. Variations in font size, color, or style that the Government deems manipulate or obscures the readability of content are prohibited. Proposals found to contain concealed or manipulated text will be considered non-compliant and may be rejected

c) All proposal documents shall be compatible with the latest version of Microsoft Office and Adobe Acrobat Reader PDF. ZIP files are not allowed.

d) Offerors shall run an anti-virus scan before submission to ensure electronic proposals are virus-free. Embedded sound or video files (e.g., MPEG) are prohibited. Offerors are encouraged to simplify the color palette in figures, minimize graphic file sizes, and avoid scanned images to reduce file complexity.

L.3 PROPOSAL VOLUMES

a) Offerors shall organize proposal information to allow for a direct comparison between the submission and the Proposal Instructions. Each volume shall be properly identified, numbered, clearly indexed, and logically assembled. Volumes shall include clearly labeled sections, and all pages shall be numbered and include the company name, date, and RFP number in the header or footer.

b) To reduce proposal size, page limits for each volume are specified in Part B below. Title pages and table of contents pages and a table of acronyms for each volume are excluded and do not count toward the page limits. Any pages exceeding the specified limit will be disregarded and will not be evaluated. Each volume shall be submitted as specified in the table below, which supersedes the copies requested in Block 9 of Standard Form (SF) 33. All proposal information shall be confined to the appropriate file.

c) The authorized Annexes, with page limitations, are summarized in the table below.

Section L, Table 1

Offerors shall use the format found in the Section J, Attachment L1 SBPCD Template.**

No Page Limit

Technical Approach & Capability Narrative

Offerors shall use the format found in the Section J, Attachment L2 TAC Narrative template.**

ABC.V2.RESUME.XYZ.docx (and .pdf in a searchable format)

ABC.V1.STAFFPLAN.xlsx 10 Pages for Narrative free format (Exclusions: Title Page, Table of Contents, Attachments L3 & L4, and Resumes do not count against the narrative page limit.)

3 Pages per individual resume

Offerors shall use the format found in Section J, Attachment L3 – Key Personnel Resume & Qualification Matrix, and L4 – Staffing Plan. The Staffing Plan (ABC.STAFFPLAN.xlsx) SHALL be submitted in unprotected and unlocked Excel format (xlsx).

ABC.V2.CPAQ.CONTRACTNUMBER.pdf (in a searchable format)*** No Page Limit

PPIF – Offerors shall use the format found in the Section J, Attachment L5 PPIF template.**

CPAQ – If applicable, Offerors shall use the format found in the Section J, Attachment L6 CPAQ template.**

Price Proposal – Offerors shall use the format found in Section J, Attachment L9 – Price Workbook. The Price Workbook (ABC.PRICE.xlsx) SHALL be submitted in unprotected and unlocked Excel format (.xlsx) with all formulas visible in each cell with a value.

Numerical data presented in MS Excel format must not be pictorial. Files received in a format other than requested or MS Excel files with output- type, hard-coded, “value only” cells may not be further evaluated.

(PRICE INFORMATION SUBMITTED IN ANOTHER FORMAT (E.G. PDF) WILL NOT BE EVALUATED)

Annex #1

OCI Declaration / Mitigation Plan (if applicable)

(Optional) Annex #2 Past Performance Support Past Performance Supporting Documents

*Replace ABC in the file name with the Offeror or Subcontractor name.

**Offerors shall utilize Government format but may use their own templates.

***Replace XYZ with the employee’s name.

L.4 RFP QUESTIONS

a) Questions regarding this RFP shall be submitted via the PIEE Solicitation Module. Each question or comment should reference the applicable document, page number, and paragraph number. Offerors shall not include any proprietary information in question(s) because the Government will provide the question(s) and answer(s) via the PIEE Solicitation Module to all potential Offerors. All questions for the RFP shall be submitted no later than 4:00 PM ET on the 14th calendar day after the date that this RFP is issued. The Government is under no obligation to answer questions received after that date but may answer the question if time permits.

L.5 PROPOSAL SUBMISSION INSTRUCTIONS

L.5.1 SUBMISSION METHOD

a) All proposal information must be submitted electronically through the Solicitation Module of the PIEE at https://piee.eb.mil. Submissions via mail, hand delivery, or other electronic systems (e.g., DOD SAFE) are not authorized unless specifically approved by the Contracting Officer, as outlined in paragraph 5.1.5 below.

L.5.1.1 Posting Offers

a) For instructions on how to post an offer, refer to the Posting Offer demo available at https://pieetraining.eb.mil/wbt/sol/Posting_Offer.pdf.

b) Offerors are responsible for following the registration instructions provided on the PIEE website. Offerors and their subcontractors should ensure that the appropriate company points of contact are registered in PIEE based on their CAGE codes and have the correct roles assigned well in advance of the solicitation closing date.

L.5.1.2 Subcontractor Registration

a) Subcontractors are only required to register in PIEE if they intend to submit proprietary proposal information directly to the Government, separate from the prime Offeror.

b) Documents submitted by subcontractors must include the prime contractor’s name, CAGE code, and RFP number on the first page of the document.

L.5.1.3 Confirmation of Submission

a) Offerors are responsible for confirming receipt of proposals and all electronic communications.

b) The Government is not obligated to search for incorrectly submitted proposals in PIEE.

c) It is recommended to take screenshots of the submission to validate that the proposal was successfully accepted in the PIEE system.

L.5.1.4 Submission Deadline

a) All proposal volumes must be submitted no later than the date and time specified in Block 9 of the SF 33 of the RFP.

b) Offerors are responsible for ensuring that proposals, including any modifications or revisions, are received by the designated Government office by the specified deadline.

c) Late submissions, modifications, or revisions will not be evaluated or considered for award, except as outlined in paragraph 4.2.

L.5.1.5 PIEE System Outage

a) If an unanticipated PIEE system outage occurs within 24 hours of the proposal due date and disrupts normal Government processes, the Offeror must:

i. Immediately notify the Contracting Officer in writing prior to the proposal submission deadline.

ii. Verbal notification may accompany the written notification, but verbal notification alone is not sufficient.

iii. Obtain written approval from the Contracting Officer to submit the proposal via an alternate method.

iv. Alternatively, the Contracting Officer may amend the solicitation closing date following the procedures outlined in FAR 15.106.

b) In the event the Contractor does not provide notification to the contracting officer until after the closing date and time, the rules in FAR clause 52.215-1 apply.

L.5.1.6 Important Notices to Offerors

a) Offerors are encouraged to submit proposals one working day prior to the date specified for receipt of proposals in block 9 of the solicitation to avoid last-minute technical issues.

b) Ensure all required documents are properly formatted and include the necessary identifiers (e.g., CAGE code, RFP number).

c) Late submissions will not be considered unless explicitly authorized by the Contracting Officer due to unforeseen circumstances, such as a PIEE system outage.

d) By adhering to these instructions, Offerors can ensure compliance with the solicitation requirements and avoid delays or disqualification.

L.5.2 LATE PROPOSALS POLICY

L.5.2.1 Definitions

a) Proposal Modification: A change made to a proposal before the RFP’s closing date and time, in response to an amendment, or to correct a mistake before award.

b) Proposal Revision: A change to a proposal made after the RFP closing date, at the request of or as allowed by the Contracting Officer.

c) Time: If stated in days, it refers to calendar days, including Saturdays, Sundays, and legal holidays. If the last day falls on a weekend or legal holiday, the deadline extends to the next working day.

L.5.2.2 Amendments to RFPs

a) If the RFP is amended, all unchanged terms and conditions remain valid.

b) Offerors shall acknowledge receipt of any amendments by the date and time specified in the amendment(s).

L.5.2.3 Submission, Modification, Revision, and Withdrawal of Proposals

a) Submission Requirements:

i. Proposals, modifications, and revisions shall be submitted electronically through the PIEE Solicitation Module to the designated government office by the specified deadline.

ii. Proposals received after the exact deadline are considered late and will not be evaluated unless:

1. The proposal is received before award, and the Contracting Officer determines that accepting it will not unduly delay the acquisition.

2. One of the following conditions is met:

A. Electronic Submission: The proposal was transmitted through an authorized electronic method and received at the initial government entry point no later than 5:00 p.m. one working day before the deadline.

B. Government Control: Acceptable evidence shows the proposal was received at the designated government installation and under government control before the deadline, OR C. Single Proposal: It is the only proposal received.

b) Emergency Situations: If an emergency or unanticipated event interrupts normal government processes, preventing electronic receipt of proposals through the Solicitation Module of the PIEE at https://piee.eb.mil or the designated office, the deadline will automatically extend to the same time on the first working day when normal processes resume.

L.5.2.5 Language and Currency

a) Proposals shall be submitted in English and in U.S. dollars, unless otherwise permitted by the RFP.

L.5.2.5 Modifications and Revisions

a) Offerors may submit revised proposals only if requested or allowed by the Contracting Officer.

L.5.2.6 Withdrawal of Proposals

a) Proposals may be withdrawn at any time before award by submitting written notice to the Contracting Officer.

b) Withdrawals are effective upon receipt of the notice.

L.5.2.7 Award Acceptance

a) A written award or acceptance of a proposal sent to the successful Offeror before the proposal expiration date creates a binding task or delivery order without further action by either party.

L.5.3 RESTRICTION ON DISCLOSURE AND USE OF DATA

a) Offerors that include in their proposals data that they do not want disclosed to the public for any purpose, or used by the Government except for evaluation purposes, shall—

i. Mark the title page with the following legend:

1. This submittal includes data that shall not be disclosed outside the Government and shall not be duplicated, used, or disclosed—in whole or in part—for any purpose other than to evaluate this submittal. If, however, a task order is awarded to this offeror because of — or in connection with — the submission of this data, the Government shall have the right to duplicate, use, or disclose the data to the extent provided in the resulting task order. This restriction does not limit the Government's right to use information contained in this data if it is obtained from another source without restriction. The data subject to this restriction are contained in sheets [insert numbers or other identification of sheets]; AND

2. Mark each sheet of data it wishes to restrict with the following legend:

ii. Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposal.

PART B: SPECIFIC INSTRUCTIONS

L.1 VOLUME CONTENT

L.1.1 LIST OF REQUIRED DOCUMENTS

L.1.1.1 This volume shall include the following required documents with the cited file names.

Small Business Participation Commitment Document (SBPCD):

L1.2 FACTOR 1: SMALL BUSINESS PARTICIPATION COMMITMENT DOCUMENT (SBPCD)

Each Offeror (Large and Small Businesses) shall complete the SBPCD provided as Attachment J1 and submit it as a part of VOLUME 1. The SBPCD shall identify a minimum small business participation goal of 30% of the total proposed estimated task order ceiling value, inclusive of options but excluding the price of FAR 52.217-8 Option to Extend Services clause and list the planned small business participants. Small Business offerors may meet the 30% goal using work they propose to perform themselves along with any similarly situated Small Business subcontractors.

The SBPCD shall provide goals equal to or greater than 30% for Small Business (SB), 5% for Small Disadvantaged Business (SDB), 5% for Women-Owned Small Business (WOSB), 5% for Veteran-Owned Small Business (VOSB), 5% for Service-Disabled Veteran-Owned Small Business (SDVOSB), and 3% for HUBZone Small Business (HUBZone). The SBPCD shall also identify one or more small business participants under item 3 of the SBPCD. Each small business participant identified under item 3 of the SBPCD must have an active registration in SAM or provide a written certification of its small business or socio-economic status applicable under the size standard assigned to this procurement (if the SB is the offeror) or under the size standard assigned by the offeror (if the SB is the subcontractor).

The SBPCD shall be incorporated into the task order as an attachment in Section J.

The Offeror shall ensure its proposal information complies with Part A, L.1.0 above and is sufficient for the Government to evaluate in accordance with Section M.

VOLUME 2: NON-PRICE PROPOSAL

Price information shall not appear in Volume 2. Proposals that fail to separate price information from Volume 1 may not be considered for award.

L.2 VOLUME CONTENT

This volume shall contain the following information (cite the Volume Content file name within Section L, Table 1):

a) A combined cover and title page;

b) Title of proposal and proposal number as applicable;

c) Offeror’s name, address and point of contact;

d) RFP number;

e) Proposal volume number; and

f) Table of Contents (the table of contents shall provide sufficient detail to enable easy location of important elements);

g) Glossary Pages to include list of acronyms and list of figures as applicable.

L.2.1 This volume shall include the following required documents (cite the file names within Section L, Table 1).

a) Facility Clearance Level (FCL)

b) Technical Approach and Capability Narrative

c) Integrated Management & Staffing Narrative

d) Key Personnel Resume and Qualification Matrix

e) Staffing Plan

L.2.2 FACTOR 2 FACILITY CLEARANCE LEVEL (FCL):

The Offeror only shall complete the Security Compliance showing the current Facility Clearance Level (FCL) and ability to meet the FCL outlined on the DD254. The Government requires proof (ex., certificate from the Defense Counterintelligence and Security Agency (DCSA) or screenshot from the DCSA National Information Security System (NISS), copy of a DD254 from a current contract outlining the FCL or other valid proof) to confirm the Facility Clearance Level of "Top Secret” in accordance with the DD254. If the Offeror’s facility does not have an FCL of, "Top Secret” outline your organization’s plan to become FCL compliant by the start of the period of performance. NOTE: Noncompliance will result in an offer determined unacceptable for award.

L.2.3 FACTOR 3 TECHNICAL

The Technical Factor is comprised of the three (3) elements below, which are equally weighed. These elements are not individually rated subfactors; rather, they are evaluated holistically to assess strengths, weaknesses, and deficiencies across the proposal. The Government will assign a single, combined overall Technical rating.

a) The Offeror shall utilize the following Attachments as templates to provide information for this factor:

i. Attachment L1 Technical Approach & Capability Narrative

ii. Attachment L2 Key Personnel Resume & Qualification Matrix, AND

iii. Attachment L3 Staffing Plan

L.2.3.1 Element 1: Technical Approach & Capability Narrative

a) Content: The Offeror shall submit a Technical & Capability Approach narrative demonstrating a comprehensive understanding of the requirements set forth in the Performance Work Statement (PWS) as specified in the following scenarios. The Offeror should not assume that the Government evaluators possess any knowledge or familiarity with its company or approach in its proposal. The Offeror shall therefore fully explain any proposed schedules, processes, or procedures which are relevant to demonstrate the Offeror’s understanding and proposed approach. The Offeror shall submit a detailed and comprehensive response which clearly explains the Offeror’s understanding of the tasking and the strategy that the Offeror would use in accomplishing the below stated scenarios.

b) Each response shall include the following information:

i. Assumptions – Detail all assumptions (as applicable) relative to the scenarios and the technical approach to ensure full understanding of the response by the Government.

ii. Performance Risk Analysis – Identify contingent events inherent to the nature of the effort that could, if they were to occur, endanger satisfactory performance. Focus on critical events that are realistically likely to occur and that would pose serious problems and provide strategies for mitigating potential risks.

iii. Describe the process used to track progress towards the completion of the task.

L.2.3.1.1 Scenario Response

a) The scenarios below represent a notional set of requirements in an awarded TO. The Offeror shall provide the responses as defined in each individual section. Responses to each individual section should be made irrespective of the responses made to the other sections.

L.2.3.1.1.1 Scenario One: Directorate Policy and Procedure Development

a) Focus Area: Security Directorate Support

b) Context: Due to organizational growth and evolving DoD requirements, the Joint Program Office (JPO) Security Directorate requires a comprehensive overhaul and standardization of its policies, Standard Operating Procedures (SOPs), and Process Guides. Administrative bottlenecks in document creation must be eliminated.

c) Requirement: The Contractor must rapidly develop, standardize, and maintain high-quality directorate-level security policies and operational procedures.

d) Offeror Tasks:

i. Describe the Offeror's process for identifying critical policy gaps and the methodology for drafting complex SOPs. The Offeror must include their standard administrative timeline (cycle time) from initial gap identification to the delivery of a government-ready draft.

ii. Provide a Quality Assurance (QA) approach that ensures all drafted policies are 100% accurate, actionable, and require zero structural rework by the Government before approval.

iii. Contingency: The Government rejects a Contractor-drafted SOP for being "operationally unexecutable." Detail the Contractor's corrective action plan to rapidly revise the document, gather SME input, and deliver an acceptable final product within 10 business days.

L.2.3.1.1.2 Scenario Two: Systemic Training Compliance and Incident Mitigation

a) Focus Area: Security Operations

b) Context: The JPO operates in a highly complex environment encompassing numerous independent Special Access Programs (SAP). Historically, this has led to a high volume of data spills and inadvertent disclosures. Furthermore, the organization has consistently struggled to achieve 100% compliance for SAP Annual Security Training across HQ and geographically dispersed operating sites.

c) Requirement: The Contractor must manage comprehensive security education and training programs and provide immediate incident response and mitigation.

d) Offeror Tasks:

i. Describe the operational approach to developing, scheduling, and executing SAP Annual Security Training. Detail the tracking and QA mechanisms used to guarantee 100% verifiable, error-free compliance reporting for approx. 1000 indoctrinated personnel within a strict 60-day window.

ii. Detail a proactive workforce education strategy designed to reduce data spills, including proposed metrics the Contractor will use to measure and prove the effectiveness of this strategy over time.

iii. Contingency: An uncleared contractor inadvertently emails a slide deck containing suspected SAP technical data over the JPO Unclassified Network to a distribution list of 50+ personnel. Provide a step-by-step narrative of the Contractor's immediate containment, reporting, and cleanup actions within the first 4 hours of discovery.

L.2.3.1.1.3 Scenario Three: International Security, FMS Integration, and Staff Assistance Visits (SAVs)

a) Focus Area: International Security

b) Context: The JPO is integrating a new FMS customer. Historically, JPO Security has struggled to successfully execute the required volume of SAVs. Timely production of foundational security documentation is a critical mission enabler, and delays in this area directly impact FMS delivery schedules.

c) Requirement: The Contractor must provide International Security technical assistance, conduct SAVs, and support the release of information to non-US entities.

d) Offeror Tasks:

i. Describe the Offeror's methodology for planning, executing, and reporting on OCONUS SAVs to ensure the FMS customer's facilities meet U.S. requirements.

ii. Detail how Contractor personnel will actively advise and assist the foreign country's security managers. Specifically, describe the approach to guiding the FMS customer through the development, tailoring, and approval process for their Program Security Instruction (PSI) and Access Management Control Plan (AMCP). The Offeror must include a notional milestone schedule demonstrating how they will ensure the rapid, error-free production of these documents to prevent program delays.

iii. Contingency: During an SAV, the Contractor team discovers the FMS customer has been storing CUI and ITAR-restricted technical data on an unapproved network. Detail the immediate reporting, mitigation, and corrective action plan.

L.2.3.1.1.4 Scenario Four: Personnel Security (PERSEC) and PAR Processing

a) Focus Area: PERSEC

b) Context: The JPO processes hundreds of Program Access Requests (PARs) annually across multiple SAPs. Administrative errors and rework in PERSEC packages frequently delay the onboarding of critical engineering and mission personnel.

c) Requirement: The Contractor must manage the end-to-end PERSEC process, including pre-screening, PAR generation, and SAP nomination packages, with absolute administrative precision.

d) Offeror Tasks:

i. Describe the Contractor’s end-to-end workflow for processing a SAP PAR. Detail the strict internal Quality Control (QC) mechanisms used to guarantee a zero-rework standard (first-time pass rate) before the package is ever submitted to the Government Program Security Officer (PSO).

ii. Detail the Contractor's Service Level Agreements (SLAs) for PAR turnaround times from the moment the candidate's initial paperwork is received.

iii. Contingency: A critical SME requires immediate SAP access to resolve an emergent technical grounding issue, but their clearance crossover is stalled in DISS. Detail the Contractor's proactive steps to expedite the issue without relying on Government personnel to intervene.

L.2.3.1.1.5 Scenario Five: Classification Management & Security Classification Guides (SCG) Development

a) Focus Area: Classification Management / OPSEC

b) Context: As the F-35 program evolves with new block upgrades, the foundational SCGs require constant, highly technical revisions to protect new Critical Program Information (CPI).

c) Requirement: The Contractor must actively draft, revise, and facilitate the approval of complex SCGs.

d) Offeror Tasks:

i. Describe the methodology for managing an SCG update. Specifically address how Contractor personnel will autonomously extract required technical data from engineering SMEs and translate it into actionable classification guidance without relying on Government security personnel to write the document for them.

ii. Detail the timeline and project management approach to ensure an SCG revision stays on schedule.

iii. Contingency: During a review, a joint partner disputes a newly proposed classification baseline, claiming it stifles operational interoperability. Detail how the Contractor will facilitate a resolution between the technical authorities and the Foreign Disclosure FDOs.

L.2.3.1.1.6 Scenario Six: Secure Facility Construction and Accreditation

a) Focus Area: Physical Security (PHYSEC)

b) Context: Upon contract award and issuance of the baseline Task Order, the Contractor assumes responsibility for supporting the ground-up construction and accreditation of three (3) new facilities. The overwhelming majority of these requirements are Special Access Program Facilities (SAPF), with a standard start-to-finish timeline of 2-3 years.

c) Requirement: Under PWS Section 3.6.2, the Contractor shall provide long-term Guidance and Documentation to Facilitate DoD/ICD Compliance, monitor requirements, and prepare accreditation requests for Government processing across the multi-year lifecycle.

d) Offeror Tasks:

i. Provide a proposed long-term teaming/staffing plan for all three locations, detailing how the Offeror will manage personnel retention, continuity of operations, and required certifications over the 36-month construction lifecycle.

ii. Provide a narrative execution approach for developing Construction Security Plans (CSP) and Fixed Facility Checklists (FFC) in accordance with ICD 705. Detail the Contractor's Quality Assurance (QA) measures to ensure these complex documents are defect-free upon first submission, maximizing first-time accreditation approval without Government rework.

iii. Contingency: Provide a narrative response detailing how the Offeror will address a 6-month delay in the Fort Worth, TX SAPF construction due to critical supply chain shortages (e.g., shielding materials), and a subsequent failure during the Telecommunications Electronics Materials Protected from Emanating Spurious Transmissions (TEMPEST) assessment phase in year two.

L.2.3.1.1.7 Scenario Seven: DD 254 Processing for Collateral, SAP and TS-SCI

a) Focus Area: Industrial Security / Security Operations

b) Context: JPO Security manages several hundred Prime and sub-contractor DD 254s. Efficient processing is required to prevent administrative backlogs that delay contract execution.

c) Requirement: Contractor must articulate the rapid and accurate steps to complete a DD 254 at each access level.

d) Offeror Tasks:

i. Describe the DD 254 preparation process for Collateral, SAP and TS-SCI contracts, including the Contractor's internal Service Level Agreements (SLAs) and QA checks to guarantee rapid turnaround times and error-free processing.

ii. Describe the differences between a Collateral, SAP and TS-SCI DD 254 to include signatories.

iii. Contingency: Describe the DD 254 close-out procedures when the PoP has expired, including rapid remediation steps if a subcontractor fails to return classified material.

L.2.3.1.1.8 Scenario Eight: SAPF Accreditation Inspections for Partner and FMS Customers

a) Focus Area: Physical Security (PHYSEC)

b) Context: The Physical Security and TEMPEST team conduct accreditation inspections on behalf of the PSO. This inspection is highly detailed, and administrative or preparatory failures cause significant schedule slips.

c) Requirement: Contractor must write the inspection requirements and timeline for accreditation of the SAPF.

d) Offeror Tasks:

i. Describe the inspection requirements and procedures for electronic security systems. Detail the Contractor's pre-inspection Quality Control (QC) process utilized to maximize the first-time pass rate and avoid unnecessary, costly re-inspections.

ii. Describe the TEMPEST inspection items that are required to be inspected.

iii. Contingency: Describe the rapid reporting process to capture inspection deficiencies discovered during the initial site visit and how these items are conveyed to the Partner/FMS security manager for immediate remediation.

L.2.3.1.1.9 Scenario Nine: Aircraft Mishap and Incident Response

a) Focus Area: Security Operations / Program Protection

b) Context: During the execution of the baseline PWS for Program Protection (P2) Security Support, an F-35 aircraft mishap occurs at an OCONUS location.

c) Requirement: The Contractor must provide immediate onsite coordination and execution of security operations to protect Critical Program Information (CPI), Mission Critical Components (MCC), and Mission Critical Functions (MCF).

d) Offeror Tasks:

i. Provide a Work Breakdown Structure (WBS) demonstrating the initial 72-hour operational response plan upon notification of the mishap, including strict internal timelines for mobilizing personnel and the rapid, accurate reporting cadence to JPO leadership.

ii. Identify the specific personnel/labor categories to be deployed, verifying their capability to travel globally on short notice and perform required physical operations.

iii. Contingency: The mishap occurs in a non-F-35 partner country (e.g., an emergency divert to a sovereign nation with no F-35 bilateral agreements). Provide a narrative response detailing the Contractor's rapid operational actions or guidance provided to the U.S. recovery team and Embassy officials if local, uncleared foreign authorities attempt to access the mishap site to remove restricted hardware before the U.S. team arrives.

L.2.3.1.1.10 Scenario Ten: Foreign Disclosure - Document Sanitization and Review

a) Focus Area: Foreign Disclosure Office (FDO)

b) Context: A joint staff component requests to share a multi-page operational summary with a non-traditional partner nation. The document contains embedded CUI and restricted planning data.

c) Requirement: The Contractor must conduct comprehensive, error-free reviews of documents to ensure unauthorized information is removed.

d) Offeror Tasks:

i. Detail the Contractor's methodology for executing proper redaction techniques (or generating a tear-line report), including processing timelines and the internal "double-check" QA process used to guarantee 100% accuracy in redactions.

ii. Describe the records management process to ensure all disclosure actions are accurately documented in the approved system within 24 hours of release.

iii. Contingency: The original document is updated by the joint staff component 48 hours before the scheduled release, introducing new classified sources. Describe the Contractor's accelerated review process to meet the deadline with zero security spillage.

L.2.3.1.1.11 Scenario Eleven: Foreign Disclosure - Coalition Request for Information (RFI)

a) Focus Area: FDO

b) Context: An allied coalition partner submits an RFI requesting technical specifications of a DoW communications system to ensure interoperability during an upcoming joint exercise. Time is of the essence.

c) Requirement: The Contractor must rapidly process RFIs, verifying "Need to Know" and applying National Disclosure Policy (NDP-1) and Delegation of Disclosure Authority Letters (DDL) parameters.

d) Offeror Tasks:

i. Describe the process for consulting the relevant DDL, determining releasability, and drafting the response. Include the Contractor's internal SLAs for rapid turnaround times and the QA steps taken to guarantee zero unauthorized disclosures.

ii. Detail how the Contractor will efficiently route the request to the technical SME for equity review prior to release.

iii. Contingency: During a multinational working group, a foreign representative asks a DoW briefer a direct question requiring prohibited information. Detail how the observing Contractor FDR will rapidly intervene and pivot the conversation without causing diplomatic friction.

L.2.3.1.1.12 Scenario Twelve: Foreign Disclosure - Foreign Visit Processing

a) Focus Area: Foreign Disclosure Office (FDO)

b) Context: A delegation of foreign military attaches submits a short-notice Foreign Visit Request (FVR) to tour a DoW training facility.

c) Requirement: The Contractor must rapidly review and adjudicate FVRs for foreign nationals, confirming visit parameters align with established DDLs.

d) Offeror Tasks:

i. Describe the process for reviewing the facility's security posture and verifying the attaches' credentials, highlighting rapid adjudication timelines for short-notice requests.

ii. Detail the steps for approving the visit within DDL limits and drafting an accurate memo outlining approved briefing boundaries.

iii. Contingency: Upon arrival, two members of the foreign delegation are identified who were not on the approved FVR manifest. Detail the immediate, zero-defect actions the Contractor will take to adjudicate or deny access while maintaining protocol.

L.2.3.2 Element 2: Integrated Management & Staffing

a) Content: The Offeror shall submit an Integrated Management & Staffing narrative that describes their organizational structure, proposed Key Personnel, and comprehensive staffing strategies. The narrative must address:

i. Management and Resources Approach: The overall management structure, team roles, communication flows, and methods for quality control and price monitoring.

ii. Key Personnel (Leadership positions): Provide resumes and a completed Attachment L3 (Key Personnel Qualification Matrix). Demonstrate that all Key Personnel possess the required security clearances or have a concrete plan to obtain them.

iii. Staffing and Retention Strategy: Detail the methodology for recruiting, hiring, and retaining qualified personnel. Provide a completed Attachment L4 (Staffing Plan) and describe the "day one" staffing posture, including clearance status and work locations.

b) Prohibitions: No Prospective Hires for Key Personnel: Proposed Key Personnel must be either current employees of the Offeror (or teaming partners) or contingent hires with signed letters of intent. Proposals with prospective (To be determined/TBD) hires for key positions may be found deficient.

L.2.4 FACTOR 4 PAST PERFORMANCE

The Offeror shall utilize the following Attachments as templates to provide information for this volume:

Attachment L5 Past Performance Information Form (PPIF) Attachment L6 Contractor Performance Assessment Questionnaire and Instructions (CPAQ)

L.2.4.1 Submission of Past Performance References Offerors shall identify up to three (3) relevant contracts performed within five (5) years of the RFP issuance date. Each contract shall include at least one (1) year of completed performance by the RFP closing date. Offerors shall provide a detailed explanation of how each contract is relevant to the RFP requirements. Offeror shall identify the specific section(s) of the Statement of Work (SOW) or Performance Work Statement (PWS) provided with the reference that support the claimed relevant experience.

a) Definition of a Contract: A contract is defined as a single contract or task order under an ID/IQ contract, Blanket Purchase Agreement (BPA), or Federal Supply Schedule (FSS). Offerors shall not submit the overarching IDIQ, BPA, or FSS contract as a reference.

b) Combination of Orders: Offerors may submit a combination of up to three (3) delivery orders (DOs), task orders (TOs), technical direction letters (TDLs), or technical area tasks (TATs) under an ID/IQ or BPA as one of the three references. Each order in the combination shall meet the five-year recency and one-year performance requirements. For combinations, Offerors shall specify the experience claimed, period of performance, and dollar value for each order. Only one combination of DOs, TOs, TDLs, or TATs is allowed to constitute one identified relevant contract.

L.2.4.2 Subcontractor Past Performance

a) If a Subcontractor’s past performance is included, the Offeror shall specify the percentage and type of work the subcontractor will perform under the RFP. The submission shall clearly describe the Subcontractor’s role in the RFP. Submissions lacking this detail may not be evaluated. Subcontractor past performance for major or critical aspects of the RFP may be considered as relevant as the Offeror’s past performance.

b) If the Offeror or a Subcontractor submits a reference where they acted as a Subcontractor, the submission shall clearly describe the work performed and the dollar value of that work. References that fail to differentiate between the overall contract effort and the Subcontractor’s contribution may not be evaluated.

L.2.4.3 Joint Venture (JV) Past Performance

a) For joint ventures, the Government will consider work performed by individual JV members, regardless of size, and the JV itself. References shall meet the five-year recency and one-year performance requirements. JV members shall clearly describe their contributions and dollar value. References that fail to differentiate between the overall effort and the JV member’s contribution may not be evaluated.

b) The Government will consider the large business member’s past performance as JV past performance, but evaluators will look closely at whether the small business protégé’s experience is sufficient to demonstrate capability.

c) If a large business is not a JV member but instead proposed as a Subcontractor, then its past performance will be treated as Subcontractor past performance.

L.2.4.4 Required Documentation (cite the file names within Section L, Table 1).

a) PPIF – Offerors shall use the Past Performance Information Form (PPIF), Attachment L5 for each reference.

b) Written Letters of Consent from subcontractors and JV members shall be submitted with L7, Offer Letter, allowing the Government to address past performance issues directly with them. If consent is not provided, the Government will contact the Subcontractor or JV member directly, and the Offeror will forfeit the opportunity to participate in related discussions. For Subcontractors or JV members without written consent, the Offeror shall provide their contact information (name, address, phone number, and email).

c) CPAQ – Offerors shall include a “Contract Effort Description” narrative (see PPIF template) explaining how each reference aligns with the relevancy criteria in Section M.

d) For each reference, Offerors shall submit one electronic copy of the SOW or PWS) as Annex #1. For classified contracts as defined in FAR 2.101, Offerors shall submit a CPAQ (Attachment L6) to the Assessing Official or Prime Contractor (if they acted as a subcontractor), who will send it directly to Joy McBride at joy.a.mcbride2.civ@us.navy.mil by the RFP due date.

L.2.4.5 Addressing Past Performance Issues (If applicable) Offerors shall provide a narrative describing systemic improvement actions taken to resolve past performance issues. This narrative shall include:

a) Records of the actions taken and where they are documented (e.g., Government record systems).

b) Techniques, tools, and processes used to address and correct issues.

c) Quantifiable evidence or metrics demonstrating improvement.

Offerors shall explain the relevance of the data provided and substantiate that improvements have been made. The Government will not search for additional data to address deficiencies in the Offeror’s submission. Demonstrated systemic improvement may include:

a) Identification of the root cause of the issue.

b) Implementation of a corrective action plan.

c) Documentation of the timeframe for corrective actions and evidence of success.

d) Performance data, preferably from Government records, show measurable improvements.

The Government may consider discounting past performance issues if the Offeror demonstrates correction of past problems through systemic improvement.

VOLUME 3: PRICE PROPOSAL (Firm-Fixed-Price Level of Effort, FFP LOE) This procurement is being conducted in accordance with FAR Part 15 using the Sequential Evaluation source selection methodology. Adequate price competition is anticipated. Under the Sequential Evaluation source selection methodology, the Government will first rank all proposals from lowest to highest in total proposed price. Next the Government will review all proposals for Completeness and Compliance against the requirements in Section L as a pass/fail gate. Any proposal that is incomplete or non-compliant may be deemed Deficient and removed from further consideration. Then the Government will conduct a sequential evaluation of non-price factors. Finally, the Government will evaluate proposed price in accordance with the process outlined in Section M.2 to determine if the price is fair and reasonable.

Award Without Negotiation (FAR 15.203 & FAR 52.215-1):

The Government intends to evaluate proposals and make an award without negotiation. Therefore, the offeror’s initial proposal should contain the offeror’s best terms from a price and technical standpoint. However, the Government reserves the right to conduct negotiations and establish a competitive range if the Contracting Officer later determines them to be necessary. If the Contracting Officer determines that the number of proposals that would otherwise be in the competitive range exceeds the number at which an efficient competition can be conducted, the Contracting Officer may limit the number of proposals in the competitive range to the greatest number that will permit an efficient competition among the most highly evaluated proposals.

The price documentation requested is not considered certified cost or pricing data and shall not be certified in accordance with FAR 15.403-3. If adequate price competition does not exist after receipt of proposal submissions, or if the Contracting Officer determines that the price of the highest technically rated offeror is not fair and reasonable, the Contracting Officer reserves the right to obtain additional data as necessary from the Offeror and Other Entities to determine price reasonableness. This may include certified cost or pricing data pursuant to FAR Part 15. By providing a price proposal submission, the Offeror and any subcontractor(s) grants the Contracting Officer, or authorized representatives, the right to examine records that form the basis of the price proposal. This examination and review can take place at any time before contract award.

L.3.1 VOLUME CONTENT

This volume shall contain the following information (cite the Volume Content file name within Section L, Table 1):

a) A combined cover and title page

b) Title of proposal and proposal number as applicable

e) Offeror’s name, address and point of contact

f) RFP number

g) Proposal volume number

h) Table of Contents (the table of contents shall provide sufficient detail to enable easy location of important elements), AND

i) Glossary Pages to include list of acronyms and list of figures as applicable.

L.3.1.1 REQUIRED DOCUMENTATION

This volume shall include the following documents (cite the…