Section L MQ-9 Instructions Conditions Notices to Offerors or Quoters.docx

PART A GENERAL INSTRUCTIONS

GENERAL

Offerors are required to submit sufficient information concerning the evaluation factors to allow Government personnel to assess the Offeror’s capability to perform the solicitation requirements. The Offeror’s proposal must be sufficient in detail and scope to provide the Government with a clear understanding of the Offeror’s approach, expertise, and capabilities as required by the solicitation. The Offeror’s proposal must demonstrate the Offeror’s understanding of the solicitation requirements and its associated risks with its proposed approach. The Offeror must also demonstrate it is capable and willing to devote the resources necessary to meet the solicitation requirements. The burden of proof for all substantiation within the proposal rests with the Offeror. Alternate proposals are not acceptable.

The Offeror shall arrange its proposal as described in the solicitation to facilitate evaluation of its offer. In presenting material in the proposal, the quality of information is more important than the quantity. The Offeror shall emphasize clarity, brevity, and logical organization when preparing proposals. Offerors are responsible for presenting sufficient information to allow the Government to evaluate the Offeror’s proposal.

The Offeror shall include the data necessary to illustrate the adequacy of its various assumptions, approaches, and solutions to problems. The Offeror shall include detailed information in the most logical place and summarize or reference the information in other areas if an overlap exists. Do not provide elaborate brochures or other presentation material beyond what is necessary to present a complete and effective proposal.

Throughout these instructions, the “Offeror” is the prime contractor with its Commercial and Government Entity (CAGE) code identified in Block 15A on Standard Form (SF) 33, Solicitation, Offer, and Award. A “Joint Venture” (JV) is a partnership or teaming arrangement formed when the Offeror consists of more than one legal entity. “JV Team Members” are the entities that form a Joint Venture. The term “entity” refers to the following: prime contractor, JV, JV team members, subcontractors, or a corporate parent, division, subsidiary, or affiliate (e.g., any contractor with a different CAGE Code/System for Award Management (SAM) Unique Entity ID (UEI) than the Offeror). Principal entities are defined in Section M. To demonstrate work commitment, the Offeror must identify each principal entity in and its proposed workshare percentage in Table KA-1.-.

PROPOSAL FORMATING

2.1 Electronic Formatting and Applications

This section provides information to the Offeror on the electronic format and the appropriate software for drafting and submitting proposals. To ensure that the Offeror’s proposal is suitable for reading electronically, Offeror’s shall use the software and procedures described in this section. The Offeror shall format proposals using a Times New Roman 12-point normal font (no reduction permitted). The Offeror may use 10-point font for Tables and Graphics. The Offeror shall ensure that proposal pages include a volume number and page number. In addition to any marking that the Offeror chooses to include in the proposal in accordance with FAR 52.215-1 ALT I (e), the Offeror shall also mark all proposal information as Controlled Unclassified Information/Source Selection using “CUI//SSEL” and “Source Selection Information-See FAR 2.101 and 3.104” to comply with FAR 3.104-4. The Offeror shall include any additional CUI markings, as applicable.

Table G-1 identifies the proposal structure, file naming conventions, and suggested page counts for each volume.

2.1.1 Operating System and Applications

The Government uses Microsoft Windows 11 Enterprise Operating System and the Microsoft Office 365 suite to access proposals. Offerors shall submit proposal information either using Office 365 or otherwise compatible applications. Offerors shall provide letters and other signed documents as fully searchable Portable Document Format (.pdf) files. Unless expressly authorized, the use of other application software for submission of proposals is unacceptable. Failure to comply with the instructions in this paragraph may render the Offeror’s proposal unawardable.

2.1.2 Hyperlinks

Offerors shall not use hyperlinks within documents and volumes.

2.1.3 Virus Free Electronic Submission

The Offeror shall ensure that its electronic proposal is virus-free. The Government will disqualify any Offeror from the competition if it submits documents that contain viruses or malicious code.

2.1.4 Multimedia

The Offeror shall not embed sound or video (e.g., MPEG) files within its proposal submission.

2.1.5 Graphics

To avoid the need for extensive computer system resources to view graphics, Offerors shall:

a. Simplify the color palette when creating figures and minimize the use of color print or graphics to the maximum extent possible;

b. Minimize size of graphics files; and

c. Avoid scanned images.

2.1.6 File Naming Conventions and Proposal Structure

The Offeror shall follow the file naming convention structure in Table G-1 for electronic file submissions (e.g., proposal volumes, attachments, appendices), where “#” represents the sequential numbering of files. Offerors shall preface files with an abbreviated company name and should keep the file name as short as possible (i.e., under 40 characters) to ensure file accessibility on the Government’s SharePoint system. Files with longer names may become corrupt or inaccessible.

The Offeror shall organize its submission using one folder for each proposal volume or annex, and include the electronic files requested for that specific volume or annex. Offerors should submit each volume or annex as one file, if possible. Offerors shall not submit each proposal section/paragraph using separate files.

Table G-1 Offeror Electronic File Naming Convention and Proposal Structure*

Table KA-1 Proposed Workshare Summary Table KA-2 Offeror Business System Status Table KA-3 Relevant Contract Summary Vol 1 KA Tables.xlsx

Annexes

The title and table of contents pages, Annexes (except for Annex C), tables, the PP-1 Attachment, Proposed Features and Benefits Matrix, Site Manning Matrix, SBPCD Attachment, and pricing attachments are not included in the suggested page count.

*Table G-1 Note: Offerors may submit PDF files; however, the Offeror shall ensure that the PDF files are fully searchable. Submission of non-searchable PDF files may render the Offeror’s proposal unacceptable. The Offeror shall submit unlocked and unprotected MS Excel files to facilitate the evaluation of the Offeror’s proposal.

PROPOSAL CONTENT AND VOLUMES

The Offeror shall present its proposal information in a manner that facilitates a one for one comparison between the information presented in the proposal volume and the Section L proposal instructions. The Offeror’s proposal paragraph numbering/lettering shall correspond to the Section L instructions paragraph numbers/letters, although the Offeror may add lower tier sub paragraphs.

Information submitted as an Annex to a particular proposal volume may include manuals, specifications, plans, procedures, and company policies, as well as other information requested in “Part B Specific Instructions” and do not count towards the suggested page count.

Offerors shall not include Cost or Price information for this proposed effort, (e.g., dollar values and/or hourly rates) in any volume other than Volume 1 Contract Administration, Volume 4 Price, Volume 5 Small Business, and Annex E (Small Business Subcontracting Plan).

Table G-2 lists the attachments provided to the Offeror within Section L.

Table G-2 Section L List of Attachments

Table KA-3 Relevant Contract Summary Table

PROPOSAL SUBMISSION AND PACKAGING

“All Proposals shall be UNCLASSIFIED.”

4.1 ELECTRONIC PROPOSAL SUBMISSION (Unclassified Data Only)

Note: All proposals shall be valid for 365 days.

The Offeror shall submit its unclassified proposal volumes electronically through the Solicitation Module of the Procurement Integrated Enterprise Environment (PIEE) at https://piee.eb.mil. The Offeror shall not use any other method to submit its initial proposal including any postal delivery service, hand-carried, or other electronic systems (e.g., DOD SAFE or the Contracting Communication Module (CCM) within PIEE). Offerors are encouraged to review the instructions on how to post an offer, using the Posting Offer demonstration on the PIEE website: https://pieetraining.eb.mil/wbt/sol/Posting_Offer.pdf.

It is the Offeror’s responsibility to follow the registration instructions found on the PIEE website. Offerors shall register its company points of contact in PIEE based on its CAGE code and ensure it assigns the correct roles well in advance of the solicitation closing date. If Subcontractors intend to submit proprietary proposal information to the Government, separate from the prime offer, the Subcontractor shall also follow the registration instructions on the PIEE website. Subcontractors that submit documents directly to the Government must include the prime contractor’s name, CAGE, and solicitation number on the first page of the document.

Offerors are responsible for submitting proposals by the date and time specified in this solicitation. Offerors are encouraged to submit documents early to ensure timely receipt by the Government. Submissions received after the exact date and time specified are “late” and will not be evaluated or considered for award. In the event there is acceptable evidence, such as screen shots of the Offeror’s submission to demonstrate timely submission of the proposal in the PIEE system for this solicitation before the closing date and time set for receipt of offers, the Procuring Contracting Officer (PCO) may elect accept the submission. It is also the Offeror’s responsibility to confirm receipt of proposals and its electronic communications. The Government will not search for incorrectly submitted proposals.

The date and time specified in Block 9 of the SF 33 is the submission date for all proposal Volumes in their entirety. However, Offerors are requested to submit Table KA-1, and KA-3 from Volume 1, Contract Administration, Table PP-1 with the proposed contract references from Volume 2-Past Performance, and Annex B, 14 calendar days before the submission date/time specified on the solicitation.

4.2 If there is an unanticipated PIEE System outage within 24 hours of the proposal due date and the outage has interrupted normal Government processes so that proposals cannot be received by the exact time specified in the solicitation, the Contractor shall immediately notify the PCO. This notification shall occur prior to the proposal submission deadline and shall be made in writing via email at Kristina.m.johnson79.civ@us.navy.mil. The notification may be in conjunction with verbal notification, but verbal notification alone shall not be sufficient. The Offeror shall obtain written approval from the PCO to submit the proposal via an alternate method, or the PCO may advise the Offeror that the Government will follow the procedures set forth in FAR 15.208(d) for amending the solicitation closing date.

CHANGES TO SOLICITATION

For any changes and additional information to the solicitation, please go to website: https://sam.gov/content/opportunities or https://piee.eb.mil Search the database for the solicitation number listed in block 3 of the SF-33.

TECHNICAL LIBRARY

A competition library of applicable documents related to this solicitation is available upon request to the Contract Specialist, Ms. Sharina Miller, sharina.n.miller.civ@us.navy.mil and the Contracting Officer, Ms. Kristina Johnson, kristina.m.johnson79.civ@us.navy.mil. The data contained in the competition library is for informational purposes only. The Government does not guarantee the accuracy or completeness of the information. The Offeror will receive an email from the SAFE system to gain secure access to the data through the website https://safe.apps.mil.

PART B SPECIFIC INSTRUCTIONS

VOLUME 1 – CONTRACT ADMINISTRATION

The following is a list of Section L Attachments that the Offeror shall use to provide information for this volume:

The primary purpose of the Contract Administration Volume is to provide the Government with information to facilitate the PCO’s responsibility determination and the need to communicate and/or obtain information related to an Offeror’s responsibility does not constitute discussions. The Offeror shall complete Attachment L-1, according to the instructions within the attachment, and submit them in accordance with Table G-1.

The Offeror shall divide the Contract Administration volume into the Sections outlined below:

a. Proposed Workshare Summary Table KA-1

(1) The Offeror shall complete Table KA-1 (Proposed Workshare Summary) to summarize the Offeror and its entities’ pertinent information by CAGE code/SAM UEI including the proposed type and level of work to indicate a commitment of work for entity identified. Offerors shall demonstrate the proposed work commitment for each entity in Table KA-1 (Proposed Workshare Summary) in Volume 4 (Price) by associating a dollar value commensurate with the Percent of Total Proposed Price reflected in Table KA-1 (Proposed Workshare Summary). The Offeror shall ensure that each CAGE code/SAM UEI is correctly associated with the entity proposed.

(2) For Joint Venture arrangements, the Offeror shall submit the legal document that established the Joint Venture and provide the associated agreements detailing the roles/responsibilities of each member of the JV. Note: All proposed Joint Ventures shall provide the Joint Venture legal document with agreement(s) in Annex A (Joint Venture and Teaming Agreement(s)).

(3) Additionally, Prime Offerors shall provide a copy of all teaming arrangements. Offerors shall provide all teaming arrangements in Annex A (Joint Venture and Teaming Arrangements). The documentation should include but is not limited to: structure of the teaming arrangement, responsibilities, and liabilities; financial responsibility; managerial responsibility and accountability; and applicable legal documents.

b. Business Systems Status Table KA-2 The Offeror shall complete Table KA-2 (Business Systems Status) showing the current status and or determinations regarding its business systems. The Offeror shall submit relevant DCAA/DCMA reports, audits, and determinations in Annex F (DCAA/DCMA Reports, Audits, and Determinations). Information in the Business Systems Status Table (KA-2) is to facilitate the PCO’s responsibility determination and the need for the PCO to discuss information related to responsibility does not constitute discussions.

c. Relevant Contract Summary Table KA-3 The Offeror shall complete the Table KA-3 (Relevant Contract Summary) for the principal entities identified Contract References (CRs) for Past Performance. The Offeror shall label CRs consistently throughout its proposal volumes and tables, including in Volume 1, Contract Administration, Table KA-3 (Relevant Contract Summary); and Volume 2, Table PP-1 (Past Performance Contract Data. For example, if the Offeror identifies a CR as P1, T1, or S1 in KA-3, the Offeror shall consistently identify that CR as P1, T1, or S1 in Table PP-1. If the Offeror makes changes to information submitted early, the Offeror shall identify any changes (e.g. addition or deletion of a CR) and briefly explain the rationale for the change in Table KA-3 with the final proposal submission.

d. Offeror Representatives and Information Offerors shall provide the name, title, phone number and email address of the Offeror’s principal point of contact for the solicitation. In addition, the Offeror shall identify those individuals authorized to negotiate with the Government and contractually bind the Offeror. The Offeror shall provide its company/division’s street address, county and facility code; CAGE code; UEI; and size of business (large or small).

e. Government Agency Information Offerors shall provide the mailing address, telephone, email address, and facility codes for the Offeror’s local Defense Contract Management Agency (DCMA), Defense Contract Audit Agency (DCAA), and Government Paying Office. In addition, Offeror’s shall provide the name, telephone number, and email address for the Administrative Contracting Officer (ACO) at DCMA.

f. Model Contract Documents:

1. Original signed SF-33 (Solicitation, Offer, and Award) cover page of the solicitation and a signed SF-30 cover page of each amendment (as applicable) with all applicable Blocks completed and acknowledgement of receipt of each amendment (as applicable) to this solicitation. The SF-33 Block 12 “fill-in” (proposal validity date) shall be completed in accordance with (IAW) Section A (Solicitation/Contract Form);

2. Signed Representations, Certifications, and Acknowledgements or System for Award Management (SAM) reference;

3. Section B with proposed pricing;

4. Section F with delivery dates filled in;

5. A completed copy of all Federal Acquisition Regulation (FAR), Defense Federal Acquisition Regulation Supplement (DFARS), Naval Air Systems Command (NAVAIR), and special clauses and provisions requiring contractor fill-ins.

6. A written plan describing how it will continue to perform the essential contractor services listed in Section J Attachment (1), Performance Work Statement, during periods of crisis in accordance with the provision at DFARS 252.237-7024. The Offeror’s submitted document will become an attachment to the awarded IDIQ contract.

g. Terms and Conditions:

Submission of a signed offer to the Government constitutes agreement and acceptance of the terms and conditions of the solicitation.

An exception to the terms and conditions or proposed deviation is a deficiency. A deficiency renders the Offeror’s proposal unawardable. An exception occurs if/when an Offeror states it will not comply with a solicitation requirement, usually involving contract terms and conditions. A deviation is where an Offeror states it will not comply with a solicitation requirement but proposes an alternative to meet the intent of the requirement, usually involving a PBWS requirement.

h. Organizational Conflict of Interest (OCI) Declaration and Mitigation Plan

In accordance with KTXT.209-5911 “Conflict of Interest Representation” the Offeror shall identify and address in its proposal all actual or potential conflicts of interest (personal or organizational) situations with itself, subcontractors, partners, or any other Offeror as it applies to this solicitation or state that there are no known potential conflicts. If there are no known potential conflicts, the Offeror shall include a statement affirming that there are no known actual or potential conflicts within this section. If any actual or potential conflicts are identified, then the Offeror shall submit an OCI Mitigation Plan in accordance with LTXT.203-9512 “Conflict of Interest Requirements” as Annex G. The PCO will determine if any unmitigated risk exists and whether the offeror shall be eligible for award.

i. Financial Responsibility:

Offerors shall provide current financial records, documents, and statements (e.g. annual reports to shareholders, Letters of Credit, surety bonds, etc.) demonstrating the capacity to maintain positive cashflow during performance of the contract.

j. Small Business (SB) Subcontracting Plan:

Large Business Offerors shall provide their Small Business Subcontracting Plan conforming to the requirements of FAR 19.109 and DFARS 219.109 as part of Annex E (Small Business Subcontracting Plan). The SB Subcontracting Plan of the successful Offeror(s) will be reviewed as well as approved by the PCO prior to contract award as part of the responsibility determination. See FAR 19.109(a)(1)(i) Statutory requirements, regarding failure of the apparent successful Offeror to negotiate and submit a SB Subcontracting Plan or submit a Comprehensive or Commercial SB Subcontracting Plan acceptable to the Contracting Officer. The successful Offeror’s approved Subcontracting Plan will be incorporated into the resultant contract and contractor performance against the plan will be monitored by the Government during contract execution.

VOLUME 2 – PAST PERFORMANCE

Note: This volume shall not contain any reference to the cost or price aspects of this offer. Although the Offeror shall not reference cost/price aspects of the current offer for this solicitation in this Volume, Offerors may include cost/price information that relates to contract references provided under this Past Performance volume.

The following is a list of Section L Attachments that the Offeror shall use to provide information for this volume:

For this volume, the Offeror shall identify all relevant CRs (where for the purpose of these instructions the term CR also refers to delivery order [DO] or task order [TO]), or those portions of a CR, that meet the definition of recency (defined in Section M) for the principal entities, identified in Table KA-1 (Proposed Workshare Summary). The relevant CRs provided for each principal entity shall be relative to its proposed role and responsibilities identified in Table KA-1 (Proposed Workshare Summary). Offerors shall also identify relevant CRs that had any show-cause notices, cure notices, or termination for default.

The Offeror shall provide substantiating documents to support Past Performance in Annex B. Annex B shall include searchable .pdf copies of the Offeror’s Previous Statement of Work (SOW)/Performance Work Statement (PWS)/Other Supporting Documentation (e.g. CDRLS and Specifications) that support the relevancy claims for each CR identified in Table KA-3 (Relevant Contract Summary), and all Level II and above Corrective Action Requests (CARs) generated under the CR. Offerors shall ensure that the most current/conformed documents are provided for each CR. For CRs where the Offeror or Principal Entity performed as a subcontractor, the Offeror shall also provide a searchable .pdf copy of the subcontractor SOW/PWS or other documentation that clearly defines the portions of the work the Offeror performed on the Prime’s SOW/PWS.

For all CRs identified that do not have an assessment Report in CPARS, or where the last assessment for a CR in CPARS is more than 12 months old, the Offeror shall forward a copy of Attachment L-3 Past Performance Questionnaire (PPQ) to that CR’s PCO, Administrative Contracting Officer (ACO), and Program Manager (PM); or commercial contractor equivalents. Please forward PPQs within 14 calendar days from this solicitation’s release date to allow adequate time for the recipient to respond.

The Offeror should not reference this solicitation’s number when distributing PPQs to customers. The Offeror should include instructions for the customers to send completed PPQs within 14 calendar days of its receipt via e-mail to kristina.m.johnson79.civ@us.navy.mil and sharina.n.miller.civ@us.navy.mil. The Offeror shall ensure that points of contact are current and include an email address and phone number. The Offeror shall not conduct follow-up actions regarding the PPQs, other than to confirm receipt by the recipient. The Government may contact customers identified by the Offeror to obtain follow-up Past Performance Information, as needed.

Offerors are reminded that the Government reserves the right to use information to evaluate past performance obtained from sources other than those identified by the Offeror. The Government may send additional questionnaires and/or obtain information from sources identified by the Government evaluation team, including but not limited to, the Supplier Performance Risk System (SPRS) in accordance with DFARS 252.204-7024.

2.1 Authorization Letter(s)

Offerors are requested to submit a signed “Release of Adverse Past Performance Authorization Letter(s)” with written consent from each principal entity (including JV team members), authorizing the release of adverse past performance information to the Prime. The Offeror shall provide the signed letter(s) in Annex D. This authorization letter allows the Government to coordinate past performance issues(s) with the Prime Offeror. The Offeror shall provide point of contact information for principal entities (including JV team members) that do not provide an authorization letter with such written consent. The contact information shall include a name, address, phone number, and email address (including JV team members), with whom the Government may coordinate performance issues and obtain responses as needed. The Government will address any past performance issues directly with the principal entity (including JV team members), and the Offeror will forfeit the opportunity to participate in any related discussions if it does not submit the Release of Adverse Past Performance Authorization Letters with written consent.

2.2 Relevant Contract Data

For each CR identified for past performance in Table KA-3 (Relevant Contract Summary), the Offeror shall complete Table PP-1 (Past Performance Contract Data), according to the instructions within the attachment and submit it within this section as a separate electronic file. Each Table PP-1 tab shall summarize the principal entities’ relevant contract data. The Offeror shall provide its detailed information and comparative analysis of the past performance CRs to this solicitation’s requirements in Volume 2 (Past Performance), Section 2.3 (Contract Reference Data), of the Offeror’s proposal. The Offeror shall use the same CRs designated in Table KA-3 (Relevant Contract Summary) to complete Volume 2 (Past Performance) with CRs numbered the same throughout the Offeror’s other proposal volumes (i.e., the CRs identified as P1, S1, T1, etc.)

If a contract has DOs/TOs, the Offeror shall provide a separate CR and separate PP-1 tab for each DO/TO. The Offeror may use one reference number/PP-1 tab for multiple DOs/TOs if they cover the same work effort and are assessed under the same CPAR; however, the Offeror shall identify the dollar amount and period of performance for each order. Do not provide a CR for the basic contract.

If the Offeror is proposing as a JV, the Offeror should provide the relevant CRs for the JV as a whole, and for each team member of the JV.

2.3 Contract Reference Data

The burden of providing thorough and complete past performance and systemic improvement information remains with the Offeror.

For each CR identified in Table PP-1 (Past Performance Contract Data), the Offeror shall provide contract data regarding relevancy, past performance information, and demonstrated systemic improvement as described below, organized by CR. As this information is presented in the proposal, demonstrate the relevancy of the principal entities past performance with respect to this solicitation’s requirements. For any CR where the principal entities are aware of problems, the Offeror shall describe the issues in section 2.3.b (Past Performance Information). For each past performance problem identified, describe the status of the systemic improvement efforts in section 2.3.c (Demonstrated Systemic Improvement).

a. Relevancy: Offerors shall explain what aspects of identified CRs relate to the solicitation’s relevancy definitions in Section M. To facilitate the Government’s relevancy analysis, Offerors shall provide a comparative analysis for each CR to explain how the CR relates to the solicitation’s requirements. Within the comparative analysis, Offerors should identify the pertinent portions (sections, paragraphs, and page numbers) of the CR’s SOW/PWS (Annex B) to clearly identify how past efforts performed are similar to this solicitation’s requirements. Offerors shall identify the referenced sections of the CRs SOW/PWS and not break out the full text separately from the complete SOW/PWS.

The CR(s) provided shall relate to each principal entity’s proposed role/responsibility identified in Table KA-1 (Proposed Workshare Summary) rather than the whole solicitation.

Offerors should be advised that the CAGE Code /SAM UEI for each referenced contract is considered as part of the Relevancy determination, which determines if the CR will be included in the Past Performance evaluation. Note: The evaluation will not consider predecessor companies as part of its evaluation. CRs for principal entity contracts that are for a different CAGE/SAM UEI should not be submitted as part of the Past Performance Volume.

CRs assessed as not relevant by the Government will not be considered in the Past Performance assessment.

b. Past Performance Information: For each CR, the Offeror shall provide a brief description of its performance meeting the requirements of that CR. Offerors shall include information that substantiates the performance obtained, and where available; provide quantifiable measures/trends to demonstrate past and current performance. Also describe past problems, including when they occurred, the circumstances surrounding the situation, and consequences that resulted from the problem. If the past problem is associated with a CAR included in Annex B the Offeror shall identify the reference in this portion of the Past Performance Volume.

c. Demonstrated Systemic Improvement: The Offeror shall identify systemic improvement actions taken to resolve past problems described in 2.3.b (Past Performance Information). Offerors shall describe the techniques, elements, and tools used to correct problems that occurred on the CR and, if applicable, how it would apply those corrective actions to the prospective contract award resulting from this solicitation. The Offeror shall also provide quantifiable evidence or metrics, preferably in Government record systems, that substantiate or demonstrate claims of improvement and to demonstrate that the past problem was corrected and has not reoccurred. It is the Offeror’s responsibility to explain the relevance of the data provided and substantiate that improvements from past performance problems have been made. Additionally, the Offeror shall explain why the past performance problem previously experienced will not occur during performance of this prospective contract.

VOLUME 3 - TECHNICAL

Note: This volume shall not contain any reference to price aspects of the offer.

The following is a list of Section L Attachments that the Offeror shall use to provide information for this volume and supplement the Government’s evaluation:

The Offeror shall complete and submit Table T-1 (Technical CRM), provided in Attachment (L-4) and submit it as a separate file within Volume 3 (Technical). The Technical CRM is included to help the Offeror develop its proposal and to ensure traceability of Section L paragraphs to the solicitation requirements. The Offeror’s Technical CRM may be identical to the one provided or revised to add pertinent information. For example, the Offeror’s Technical CRM may cross-reference its proposal volumes, paragraph numbers, and pages to specific solicitation requirements identified within the table, as well as other parts of the proposal that contain relevant information.

Offerors shall complete and submit Attachment L-5 to summarize the proposed benefits or features of its proposal for the Government to consider when evaluating the Offeror’s proposal. Offerors shall provide a summary of those aspects of its proposal that meet the definition of a Significant Strength, Strength, or Risk Reducer based on the Section M definitions. Offerors shall also thoroughly explain the proposed benefits or features in the relevant section of its proposal.

Offerors shall complete and submit Attachment L-6 to provide a clear depiction of the proposed manning support for the maintenance and aircrew approach included in the Volume 3 narrative. Offerors should ensure that the labor mix included in L-6 is consistent with what is described in the narrative.

In addition to completing the above referenced attachments, the Offeror shall provide a narrative description of its approach to successfully performing the contract as part of this volume. The burden of proof rests with the Offeror to demonstrate the extent to which its proposed capabilities will meet the requirements within this narrative. The extent and the type of substantiation may vary, but each paragraph in the Technical Volume must be substantiated. The method of demonstration is at the discretion of the Offeror.

The following information shall be addressed within the Volume 3 Narrative:

3.1 Maintenance Approach

Describe the Offeror’s approach to achieve both a 75% Mission Capable Aircraft Required rate and a 50% Full Mission Capable Aircraft Required rate, as defined in the COMNAVFORINST 4790.2E NAMP and a 90% Aircraft Operational Availability Rate (OAR), as defined in the PWS paragraph 6.0 Performance Metrics. The maintenance approach shall address:

1. The organizational structure by department: For each department include the labor category, title, shift, number of personnel, required certifications, collateral duties, and associated responsibilities for on-site and off-site personnel listed. The Number of Personnel shall be identified in the form of full-time equivalents (FTEs) along with an identification of the number of productive hours (time that an employee would be working and completing tasks in direct support of maintenance on this contract) used to establish an FTE for each position. The FTEs, positions, and collateral duties used in this section shall match those included in the L-6 Site Manning Matrix; and

2. Supporting rationale for the organizational structure that identifies how it will be applied to meet PWS requirements. This shall demonstrate how the proposed manning, including skill sets and skill levels, or any other elements of the proposed approach will meet the requirements of this solicitation; and

3. Any proposed capability, feature, or element of its maintenance approach that meets the definition of Significant Strength, Strength, or Risk Reducer via an in-context and thorough explanation.

3.1 3.2

3.2 Aircrew Approach

Describe the Offeror’s approach to achieve 96% Aircrew Availability rate at each operational site that requires aircrew IAW PWS paragraph 2.1, Work Location and paragraph 6.0 Performance Metrics. The aircrew approach shall address:

1. The number of aircrew personnel with the qualifications required to meet PWS requirements, identified by labor category and shift. The Number of Personnel shall be identified in the form of full-time equivalents (FTEs) along with an identification of the number of productive hours (time that an employee would be working and completing tasks in direct support of flight operations of this contract) used to establish an FTE for each position. The FTEs and positions used in this section shall match those included in the L-6 Site Manning Matrix; and

2. Any proposed capability, feature, or element of its maintenance approach that meets the definition of Significant Strength, Strength, or Risk Reducer via an in-context and thorough explanation.

3.2

3.3 Key Personnel

For all proposed current or contingent Key Personnel, the Offeror shall provide a resume that demonstrates the specialized experience of each proposed key position identified below:

(i) Program Manager: 1 – No specific location required

(ii) Site Manager: 1–Yuma, AZ (VMU-1); 1-INDOPACOM (VMU-1); 1-Kaneohe Bay, HI (VMU-3); 1-INDOPACOM (VMU-3); 1-Cherry Point, NC (VMUT-2); 1-Yuma, AZ (VMX-1)

The Offeror shall provide letters of intent for all proposed Key Personnel. The contractor shall demonstrate relevant experience of the proposed Key Personnel in tasks similar to those outlined in the PWS by submitting resumes (contractor format acceptable). If the experience does not readily or easily compare to the required experience stated in the PWS, the Offeror shall provide an explanation as to the equality of the proposed experience to meet the requirement. The following minimum information shall be contained within the submitted resumes:

· Employee name

· Years of employment in chronological order including narrative description of duties and responsibilities

· Current position/title and employer

· Educational History (Institution name, degree or certification earned, and year for all degrees or certifications earned)(site managers only)

· Current level of security clearance and status (Final, interim, or pending)

If the proposed candidate does not have a final clearance at the required level, the Offeror shall provide a status identifying the status of the investigation (date started and date completed).

VOLUME 4 – PRICE

4.1 General Information

The following is a list of the Section L Cost Attachments that the Offeror shall utilize to provide Cost/Price information as required for this Volume:

L-7: Vol 4 Price/Cost Attachments

The Cost and Price documentation requested is not considered certified cost or pricing data and shall not be certified in accordance with FAR 15.406-2. However, should adequate Price competition not exist after receipt of proposal submissions, the PCO shall obtain certified cost or pricing data as necessary from the Offeror for applicable Entities, pursuant to DFARS Part 215.371-3. By providing a price proposal submission, the Offeror authorizes the Government the right to examine records that form the basis of the pricing proposal. This examination and review can take place at any time before contract award.

The Offerors shall only provide proposed Cost and Price information in Section B of the model contract; Volume 1, Contract Administration; Volume 4, Price; the SBPCD; and the Annex E Small Business Subcontracting Plan. The Government is required to evaluate each proposal relative to the Price criteria submitted in response to Section M. The Offeror shall ensure that it properly presents and adequately supports its proposal with documentation to ensure the Price volume is efficiently evaluated and the Offeror’s assumptions are understood. The Offeror shall ensure that the price included in Attachment L-7 is consistent with the pricing submitted in section B of the Model Contract. The burden of proof for Price credibility rests with the Offeror.

The Government is not soliciting Offeror investments. However, in order to properly assess a proposed price that appears low or decreases program costs due to a corporate decision to absorb costs (e.g., company investment or management challenge or a contribution of resources and/or equipment), the Offeror shall fully identify and explain its investments. Additionally, if investments are proposed, the Offeror shall also propose a Special Contract Requirement for inclusion in Section H that clearly identifies what equipment and/or material, associated data, and data rights are conveyed to the Government under the terms of the proposed investment.. The Offeror shall identify its liability in the Ground Rules and Assumptions section of its proposed Cost/Price volume, and in Volume 1 Contract Administration.

4.1.2 Ground Rules and Assumptions

The Offeror shall provide an explanation of its ground rules and assumptions that affect the Cost or Price estimates, inclusive of supporting documentation and shall explain appearances of unbalanced pricing. If the Offeror’s proposed approach is contingent on usage of Government Furnished Property (GFP) in addition to what is identified in the solicitation, the Offeror shall describe the type and quantities of GFP required. The Offeror shall explain

4.2 Price Volume Detailed Instructions

In addition to completing Attachment L-7, the Offeror shall identify the proposed price for each FFP CLIN in Section B of the model contract. The Cost Reimbursable CLIN Values included in the Government Provided L-7 Attachment shall not be adjusted.

VOLUME 5 –SMALL BUSINESS

5.2 SMALL BUSINESS PARTICIPATION COMMITMENT DOCUMENT Comment by Osborne, Paige E CIV USN COMNAVAIRSYSCOM PAX (USA): LB Note in SBPCD, discuss

5.1.1. Other Than Small Business (OTSB) Offerors shall complete the Small Business Participation Commitment Document (SBPCD) provided as Attachment L-8 which shall be completely stand-alone, and not require any reference to another source, volume, or proposal section. The Offerors should submit it as a part of VOLUME 5 SMALL BUSINESS (ref FAR 52.219-8 and DFARS 215.304). The SBPCD is separate from a Subcontracting Plan that is required from Other Than Small Businesses (OTSB). Small Business Offerors are not required to submit a SBPCD.

5.1.2. OTSB Offerors shall complete the SBPCD sections as follows:

SBPCD Section 1: Enter the contract and subcontracting total values. Identify a minimum small business participation goal of 18% of the total proposed price, inclusive of options. The goals and dollar values shall be calculated to the second decimal place and can be rounded.

SBPCD Section 2:

OTSB Offerors shall identify goals for each small business socioeconomic category. The Offeror should provide the dollar figure and percentage (i.e., do not enter “N/A” or “-” to indicate a zero goal; instead enter $0 and 0%, as applicable) for each category. All values must be mathematically correct and calculated to the second decimal place when rounded.

SBPCD Section 3:

OTSB Offerors shall list its proposed Small Business entities who are proposed as parties to the execution of the contract and who’s technical and/or pricing information has been used in the preparation of the proposal, including 1st-tier Small Business subcontractors and Small Business Joint Venture partners.

Offerors are not required to include specific small business source(s) planned for provision of incidental items such as commercial piece parts, commercial supplies and/or incidental services.

Representations Of Small Business Entity Size. In accordance with FAR 19.302-2(a)(1)(ii), Offerors shall ensure that each small business entity listed under section 3 of the SBPCD provides either:

A copy of the active registration in SAM for each entity that is current, accurate, and complete as of the date of the subcontract offer. The copy found in the entity’s SAM profile’s Reps & Certs section (FAR 52.219-1, Small Business Program Representations) shall be expanded to display the full text of the provision, showing the NAICS code assigned by the Prime Offeror; or

A written representation of its small business status applicable to the size standard of the NAICS assigned by the Offeror. In accordance with FAR 19.302(a)(ii)(A), Offerors providing written representations (signed letter/memorandum) from a first-tier subcontractor listed as a small business entity in Section 3 of the SBPCD applicable to the size standard of the NAICS code assigned by the Prime Offeror, confirming its size status as a “small business;” the written representation shall be provided as part of the Offeror’s Small Business Volume, and include the following:

(i) A statement showing the NAICS code assigned by the Offeror for the services or supplies being acquired from the Small Business entity and confirming that the subcontractor does not exceed the size standard for the assigned NAICS code; and

(ii) A statement confirming that this representation is current, accurate, and complete; and

(iii) Full company name, mailing address, Dun & Bradstreet Data Universal Numbering System (DUNS) of each proposed Small Business entity; and

(iv) Signed and dated by a senior company representative of the Small Business entity.

Note: See additional instructions provided in the “Instructions” column of the SBPCD Template at Attachment L-8.

5.2 SUBCONTRACTING PLAN (OTSB ONLY)

OTSB Offerors shall provide an Individual Subcontracting Plan (ISP) conforming to the requirements of FAR 19.109 and DFARS 219.109. The ISP must be consistent in terms of goals (dollars and percentages) identified in Section 2 of the SBPCD. OTSB Offerors are advised that the acceptability of the content of the Subcontracting Plan is part of the responsibility determination assessment and not part of the evaluation.

If the Offeror is subject to a Commercial Subcontracting Plan (see FAR 19.206) or is a participant in the DoD Comprehensive Subcontracting Test Program specified in DFARS 219.109, the offeror shall submit a copy of the signed and current applicable plan.

The Offeror shall submit its Subcontracting Plan as a part of Annex E. See FAR 19.109(a)(1)(i) Statutory Requirements, regarding failure of the apparently successful offeror to negotiate and submit a Subcontracting Plan acceptable to the Contracting Officer.

5.3 INSTRUCTIONS FOR SMALL BUSINESS OFFERORS

Small Business Offerors are not required to submit any of the information requested in paragraphs 5.1 and 5.2 above. Instead, Small Business Offerors shall provide their current System for SAM profile. This shall include FAR 52.219-1 (Small Business Program Representations) expanded to display the full text of the provision, showing the NAICS code for this solicitation.