20R0102 Amendment 3.docx

N6893620R0102

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

GENERAL INSTRAUCTIONS

PART A GENERAL INSTRUCTIONS

1. GENERAL

Offerors are required to submit sufficient information concerning all evaluation factors to enable Government personnel to fully assess the capabilities of the Offeror to perform all requirements. The proposal must be sufficient in detail and scope to enable evaluation and provide the evaluators a clear understanding of the Offeror’s approach, expertise, and capability as required by the solicitation. Proposals must demonstrate that the Offeror has a thorough understanding of all requirements and associated risks and is able, willing, and competent to devote the resources necessary to meet all requirements. The Offeror shall not alter or rearrange the solicitation. The burden of proof for all substantiation within the proposal rests with the Offeror. Offerors are advised that the Government may incorporate any part of the Offeror’s proposal deemed beneficial to the Government, into the final contract, without discussions. Cost information, (e.g., dollar values and/or hourly rates) shall appear only in Volume 4 (Cost), and Volume 5 (Contract Administration). Alternate proposals are not acceptable.

In presenting material in the proposal, the Offeror is advised that quality of information is more important than quantity. Clarity, brevity, and logical organization should be emphasized during proposal preparation. It is the responsibility of the Offeror to present enough information to allow the Government to evaluate its proposal without discussions. Unsubstantiated statements that the prospective Offeror understands, can or will comply with the specifications, or paraphrasing the requirements or parts thereof are considered inadequate and may render a rating of unacceptable.

The Offeror shall include any data necessary to illustrate the adequacy of the various assumptions, approaches, and solutions to problems. There is no need to repeat information in more than one volume. The detailed information must be included in the most logical place and summarized and referenced in other areas if an overlap exists. Do not provide elaborate brochures or other presentation material beyond that sufficient to present a complete and effective proposal.

Throughout these instructions, “Offeror” is defined as the prime contractor with its 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 that is formed for the purpose of responding to this solicitation when the prime contractor consists of more than one legal entity. “JV Team Members” are the entities that make up a Joint Venture. The term “entity” is used to mean any or all of the following: prime contractor, JV, JV team members, any subcontractor, and corporate parent, division, subsidiary, or affiliate (e.g., any contractor with a different CAGE Code/DUNS than the Offeror). The following entities are defined as principal entities and only principal entities will be used in the past performance evaluations: (a) the prime contractor; (b) JV Team Members; and (c) other entities that are proposed to perform at least 20.00% of the proposed total cost for the contract (excluding the Offeror’s fee) or provides one or more Key Personnel. Offerors are advised that in order to demonstrate work commitment, each principal entity must be identified in Volume 4 Cost and associated with a commensurate dollar value.

2. PROPOSAL FORMAT AND SUBMISSION

Proposals should be formatted using a Times New Roman 12 point normal font (no reduction permitted), single-spaced with 1-inch margins all around, and formatted for/printed on standard 8.5 x 11 inch paper. If Government attachments have a different format/font, the Offeror may use the format/font in the attachment as provided. All pages should be numbered with volume, paragraph, and page numbers. If the Offeror uses graphs to convey information, the graphs must show enough detail to easily discern the information described. Graphs and tables should be presented in no smaller than a 10 pt. font. Graphs should contain a grid, which allows values to be read directly from the graph to the same detail that a 10 x 10 to the ½-inch grid provides. Graphic resolution should be consistent with the purpose of the data presented. Text utilized in charts, figures, and graphics should also be no smaller than a 10pt font and may use a font type selected by the Offeror.

2.1 Electronic Submission of Proposal

This section is intended to provide information to the Offeror on the electronic format and application software to be used for submitting proposals. Use of the software and procedures described in this section will reduce the amount of time and effort needed to receive and install proposals onto the electronic evaluation system, and will ensure that the proposals received are suitable for reading electronically.

2.1.1 Electronic Proposal Media

The Offeror should submit all volumes of its proposal electronically through https://safe.apps.mil, compatible with the operating system and applications defined in Section 2.1.2 (Operating System and Applications). The Offeror shall separate the portions of the proposal that contain cost information from the portions of the proposal that do not contain cost information. Volume 4 Cost contains cost information and shall be separate from the remainder of the proposal.

Table G-3 (Proposal Structure) identifies the proposal structure for each volume. The volumes should be clearly marked with the Offeror's name and address, the point of contact's name and phone number, the proposal volumes contained therein, and “Source Selection Information – See FAR 2.101 and 3.104”.

2.1.2 Operating System and Applications

The proposals will be accessed utilizing the Microsoft Windows 10 Operating System. Proposal information shall be submitted using the following applications: Microsoft Word 2016, Microsoft Excel 2016, Microsoft PowerPoint 2016, and Microsoft Project 2016; however, letters and other signed documents shall be provided as a fully searchable Portable Document Format (.pdf) file. Use of other application software for submission of proposals is prohibited except where specific instructions for non-.pdf or Office 2016 applications are provided.

2.1.3 Hyperlinks

Offerors shall not use hyperlinks in proposal volumes.

2.1.4 Virus Free Electronic Submission

Offerors are responsible for ensuring that its electronic proposal is virus free. The Offeror shall certify, in its proposal cover letter, that all electronic proposal information delivered throughout the evaluation (e.g., original proposal submission, responses to evaluation notices, Final Proposal Revisions) has been or will be checked for viruses and certify that its files are/will be virus free. The Offeror should specify the software, version, and virus definition used/that will be used to check the data.

2.1.5 Multimedia

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

2.1.6 Graphics

Large files require greater computer system resources and are discouraged. The Offeror is encouraged to:

a. Simplify the color palette used in 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.7 File Naming Conventions

Valid extensions for files using their associated applications are listed below in Table G-1 (file Extensions):

Table G-1 File Extensions

The Offeror shall follow the basic structure of the file naming convention in Table G-2 (Offeror Electronic File Naming Convention) for electronic file submissions (e.g., proposal volumes, attachments, appendices), where "#" represents the sequential numbering of files. Offerors shall keep the file name as short as possible (i.e., under 40 characters) so that the files are accessible on Government share drives. Files with longer names may become corrupt or inaccessible.

The Offeror should provide one folder for each volume or annex, containing all electronic files requested within the volume or annex. Please submit each volume, book, or annex as one file if possible. Offerors should not provide each section/paragraph as separate files.

Table G-2 Offeror Electronic File Naming Convention

Table ES-1 Offeror Summary Table ES-2 Relevant Contract Summary Vol 1 ES Tables.xlsx

CA-1 Prime Cost Breakout Spreadsheet CA-2 Subcontractor Cost Breakout Spreadsheet Vol 4 Att L-6 CA.xlsx

Annexes

Please note: The Offeror should provide both a .pdf and .docx version if they are available. If not, a .pdf version only is acceptable.

3. PROPOSAL CONTENT AND VOLUMES

The Offeror must present its proposal information in a manner that facilitates a one for one comparison between the information presented and Section L proposal instructions. Proposal information must be structured such that its paragraph numbers/letters correspond to the proposal instructions paragraph numbers/letters, although the Offeror may add lower tier sub paragraphs.

Each volume and annex of the proposal shall be submitted as specified in Table G-3 (Proposal Structure). Suggested page counts for each volume, if any, are also specified in Table G-3 (Proposal Structure). The title and table of contents pages, as well as tables, are not included in the suggested page count.

Information submitted as an Annex to a particular proposal volume could 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. Additionally, the individual subcontracting reports for the past performance volume is not included in the suggested page count.

Cost information, (e.g., dollar values and/or hourly rates) shall not be included in any volume other than; Volume 4 Cost, and Volume 5 Contract Administration.

Table G-3 Proposal Structure

Technical

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

Table G-4 Section L List of Attachments

Tab-2 Travel-and-Purchase Requests

CA-2 Subcontractor Cost Breakout Spreadsheet

4. PROPOSAL SUBMISSION AND PACKAGING

All Proposals shall be UNCLASSIFIED.

4.1 PROPOSAL SUBMISSION

Clearly mark all packages with the solicitation number. The submission date for all Volumes of the proposal shall be no later than the date and time specified in Block 9 of Standard Form 33 (Solicitation, Offer and Award) of the solicitation. The Government requests that two weeks prior to the proposal due date, offerors should submit one electronic copy through https://safe.apps.mil with the following documents: Table ES-1 (Offeror’s Summary), Table ES-2 (Relevant Contract Summary); Table PP-1 (Past Performance Contract Data); and Annex A (Final Versions of Previous SOW/PWSs/Other Supporting Documentation for Past Performance).

In the official proposal submission, please indicate any changes made to the information delivered two weeks early in the submission provided on the date and time specified in Block 9 of Standard Form 33 of the solicitation. If no changes are made, please state so at the beginning of Volume 1 (Executive Summary), and Volume 3 (Past Performance).

Method of delivery shall be through the use of https://safe.apps.mil and shall be coordinated with John Faria, the Procuring Contracting Officer (PCO) (760) 793-3476 and/or contract specialist listed below. Initial and Final Proposals shall not be submitted by facsimile or electronically via email.

NAVAL AIR WARFARE CENTER WEAPONS DIVISION (NAWCWD)

ATTN: Code D212000, Ms. Lindsay Cook Solicitation Number: N68936-20-R-0102 1 Administration Circle, Stop 1303 China Lake, CA 93555 Phone: (760) 793-4333 Email: lindsay.cook@navy.mil

Note: SAFE restricts the maximum file submission at 8 GB. In the Comments box put the following information: Offeror name, Solicitation number, POC, Backup POC. When files are encrypted for submission, send an email with the “passphrase” to the PCO and the Contract Specialist as listed on the https://beta.sam.gov website.

Creating a Drop-off for “outside or unauthenticated users”:

In order for an outside user to create a drop-off, they must receive a drop-off request from the PCO or the CS. If interested in submitting a response to the Solicitation, the Offeror must contact the PCO and CS to notify them no later than 10 working days in advance of the proposal submission date. When the PCO or the CS generates a drop-off request for you, you will receive an email with a link to submit your drop-off. This link is good for a one-time submission; ensure that the submission is sent to both the PCO and the CS. 2. For “CAC Authenticated users” Create a “drop-off” with the PCO and the CS as the recipients Offerors are hereby notified that the Government will not reimburse for any costs incurred for solicitation preparation, to include pre-award site visits.

5. CHANGES TO SOLICITATION

For any changes and additional information to the solicitation, please go to website:

https://fbohome.sam.gov/

Search the database for the solicitation number N68936-20-R-0102.

PART B SPECIFIC INSTRUCTIONS

0. VOLUME 1 – EXECUTIVE SUMMARY

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

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

The purpose of the Executive Summary is to provide the Government with an overview of the Offeror’s entire proposal, excluding cost. The Executive Summary volume should be divided into the sections outlined below:

a. Offeror Summary Table

(1) The Offeror shall complete Table ES-1 (Offeror Summary), provided in Attachment L-1 (Executive Summary Tables), according to the instructions within the attachment, and submit it within this section and as a separate electronic file. This table summarizes the Offeror and its entities’ proposed type and level of work, indicating a commitment to that effort during contract performance. Offerors are advised that in order to demonstrate work commitment, each entity identified in Table ES-1 (Offeror Summary) must be identified in Volume 4 (Cost) and associated with a dollar value commensurate with the Percent of Total Proposed Cost identified in Table ES-1 (Offeror Summary). Therefore, this table must be a reflection of what is proposed in Volume 4 (Cost).

(2) For the Past Performance evaluation, contract references that relate to a different CAGE code/DUNS than the proposed entity will be considered if the CAGE code/DUNS was created as a result of a corporate acquisition, reorganization, merger, or other administrative reason and refer to the same division in the same physical location for where the work is being performed or from where the work is being directed in accordance with the proposed roles and responsibilities. All current CAGE Codes/DUNS must appear in Table ES-1(Offeror Summary Table) which indicates a commitment of work for those entities. To facilitate the Relevancy determination for Past Performance, the Offeror shall provide a written explanation if multiple CAGE codes/DUNS for the same physical location are applicable to one entity. The written explanation shall detail the distinct roles and responsibilities for entities with different CAGE codes/DUNS at the same physical location for where the work is being performed or from where the work is being directed. The description shall include all changes in the organization as a result of a corporate acquisition, reorganization, merger, or other administrative reason and explain how the changes impact the relevance of any contract references provided.

Note: “Place of Performance” for this solicitation pertains to the physical location of the prime or other entities that are deploying personnel or responsible for the work; not the Government site where the work is being performed. If work is being performed at a contractor site, then that would also pertain to Place of Performance.

(3) Additionally, if applicable, the Offeror shall provide a description of the legal relationship between JV entities. Note: All joint ventures that are proposed shall provide the Joint Venture legal document with agreement(s) in Annex C (Joint Venture Agreement & Teaming Agreements).

Table ES-1 Offeror Summary

Offeror:

of Entity

b. Relevant Contract Summary Table The Offeror shall complete the Table ES-2 (Relevant Contract Summary) provided in Attachment L-1 (Executive Summary Tables), for all contracts proposed as relevant for Past Performance for the principal entities. The Offeror shall complete the table according to the instructions within the attachment and submit it within this section and as a separate electronic file. The contract references designated in Table ES-2 (Relevant Contract Summary) shall be used in completing Volume 3 Table PP-1 (Past Performance Contract Data). For example, the contracts identified as P1, T1, S1, or C1 in the Relevant Contract Summary Table are the same P1, T1, S1, or C1 contracts identified in the Past Performance Contract Data Table.

Table ES-2 Relevant Contract Summary For Past Performance

Offeror:

Reference

P2

P3

T2

T3

T4

S2

S3

S5

* Contracts deleted should be identified in a narrative paragraph following Table ES-2.

c. Technical The Offeror shall provide a succinct summary of what is proposed for each element, describing the approach and/or the proposed solution. In general, the description should be a short paragraph that provides only the factual description of what is proposed without adjectives or discussions of benefit. In a separate paragraph, identify significant features or approaches of its proposal that exceed requirements, enhance performance or operations, or reduce risk with benefit to the Government. Specifically identity where in the Technical Volume (e.g., paragraph and page number as a minimum) the details of these features or approaches are provided.

d. Contract Administration The Offeror shall provide a summary of any exceptions or deviations, and proposed Section H clauses addressed in Volume 5 (Contract Administration).

N6893620R0102

2.0 Volume 2 - TECHNICAL

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

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

The Offeror shall complete Table T-1 (Technical CRM), provided in Attachment (L-2) and submit it as the first page of Volume 2 (Technical), and as a separate electronic file. The Technical CRM is included to help the Offeror develop its proposal and to ensure traceability of Section L paragraphs to the requirements. The Offeror’s Technical CRM may be identical to the one provided or revised to add 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.

Table T-1 Cross Reference Matrix

In the Technical volume provide the information described below:

Throughout the Technical Volume the Offeror should identify any proposed capability, approach or feature that exceeds a requirement or provides merit associated with a performance or operational benefit to the Government. The Offeror should also identify any proposed capability, approach or feature that reduces risk inherent in the program. Specifically, explain the benefits to the Government in technical terms and the degree of impact it will have to performance, operations and/or risk. Offerors are advised that any offer to exceed a requirement or to provide a feature with performance and/or operational benefits may be included in the resulting applicable Contract within the proposed cost/price.

The Offeror shall provide all information and data required to conduct a thorough and complete technical evaluation. The Offeror shall address the following in the proposal:

2.1 Key Personnel

The offeror shall provide all Key Personnel information in Volume 2 Technical Proposal, in accordance with the content defined in 3.7 Labor Categories of the SOW.

The Offeror shall include the following for each Key Personnel position identified in the SOW (Manager/Operations Managers - Chief Engineer; Executive Program Manager ):

(a) Resumes. For all proposed current or contingent Key Personnel, provide a resume of the work assignments, training, etc., which demonstrates the experience and specialized qualifications of each key person proposed. The Offeror shall provide letters of intent for all Key Personnel who are proposed as contingency hires. Resumes shall contain, at a minimum, the following information:

· Employee name

· Years of employment experience in chronological order (most recent to least recent) including narrative descriptions of duties, responsibilities, and outcomes of work performed

· Current position, title, and employer

· Educational history

· Institution name, degree or certification earned, and year for attainment for all degrees or certifications earned

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

The Government may check educational background to verify degrees or certifications received.

If the qualification (i.e. education, experience) does not readily or easily compare to the minimum qualification stated in the SOW the Offeror shall provide an explanation as to the equality of the proposed qualification to meet the minimum qualification.

2.2 Management Plan

Offerors shall address the following, and may refer to Attachment L-3 WSISS IV Historical Metrics, which provides information to aid offerors in developing the Management Plan:

(a) Management:

(1) The Offeror shall provide an overview of its proposed organization, including an organization chart showing interfaces, physical locations, and lines of communication among the government, the Prime, and its subcontractors. Specifically show where the proposed Key Personnel are located in the organizational chart and their lines of reporting and authority. Also specifically show how proposed lines of responsibility, authority, and communication throughout the tasks will be managed.

(2) A description of how the offeror plans to manage the following contract functions/activities. Contract support personnel may either support a single or multiple functions, and offerors should identify those functions, if any, where a single individual will support multiple functions. The Offeror should specify whether the personnel supporting specific functions will be charged direct or indirect and justify the benefit to the Government. Offerors are to provide information on their proposed approach to perform the following functions:

a. Contracts

b. Business Finance

c. Human Resources

d. Task Order Processing/Reporting

e. Facility Security Officer

f. Travel Coordination

g. Material and/or ODC Purchasing The information on the proposed approach to performing the listed indirect functions shall include:

· Total number of personnel across all functions

· How each individual maps to a functional area (where applicable)

· Hierarchical structure within each function

· Specific position titles/roles occupied by each individual

· Physical location for each individual

· Brief description of expected routine operations for each function, referencing duties and authority of specific positions

· Provide the qualifications for the lead positons of each functional area referenced in Section L, Part B 2.2a (2a-g) in the management strategy. If an area consists of one individual, assume the individual to be the lead of that functional area. Qualifications should include education, years of experience, and description of work experience required.

(3) Procedures to be taken to ensure quality and cost control.

(b) Staffing: The Offeror shall address the following:

(1) Describe the processes used in hiring, recruiting, retaining, and training personnel throughout the life of the contract. Address the Offeror’s intentions regarding hiring the incumbent personnel during the transition period, percentage of incumbents to be hired, and process for determining rate of pay and benefits for personnel occupying professional labor categories as well as labor categories subject to the Service Contract Labor Standards (SCLS).

(2) Describe the approach to and timeframes for hiring personnel in order to take on new requirements by keeping up with the rapidly changing threat environment and compliance regulations within the contract

(c) Transition Plan: The Offeror shall address the following:

(1) The services under this solicitation are vital to the Government and must be continued without interruption. The Offeror is required to submit a written narrative delineating a transition plan that ensures a smooth transition of on-site personnel at multiple Government locations and employees working remotely (as described in Attachment L-3 WSISS IV Historical Metrics), tasking, and operations from an incumbent with no loss of service and minimal loss of corporate knowledge. For proposal purposes, estimate a 45-day transition plan. The plan should take into consideration the following elements as well as any additional elements deemed necessary by the Offeror:

a. Work Turnover

b. Workforce hiring

c. Training

d. Risk Mitigation Strategies

e. Security Requirement to include OPSEC, Facility clearances, and Base Access

f. Data Transfer

(d) Subcontract Management: The offeror shall address the following:

(1) Provide its subcontract management strategy for assembling teams, selecting subcontractors, maintaining subcontractor relationships, communicating information to subcontractors, managing subcontractor performance, and resolving problems. Where subcontractors have been chosen to fulfill specific areas of expertise, state the subcontractors’ specific capability areas, and describe any technical trade-off decisions used to determine the subcontractor as a best value teaming partner.

(2) Discuss its approach to determining the work to be performed in-house and the work to be subcontracted.

(3) Describe how its subcontract management strategy supports the Prime Contractor in overall accomplishment of the work. In describing its subcontract management strategy, the Offeror shall also address those aspects that will be accomplished through a subcontracting approach, including how the subcontract management strategy will be employed consistent with the processes.

(4) Describe the value that will be added by proposing subcontractor(s) and how the use of subcontractor(s) will not add unnecessary levels of management, impede communication, or delay work completion.

(5) Describe the internal process to pay subcontractors and how that process ensures timely subcontractor payments with no loss of productivity to the Government.

2.3 Scenario/Sample Task Technical Approach

The Offeror shall respond to the scenario below. The scenario response shall demonstrate a feasible solution for accomplishing the scenario within the IPT environment, and shall include reasonable assumptions underlying/supporting the approach toward accomplishing the scenario tasking.

The F/A-18 IPT has just received an emergent requirement from the Program Office (PMA) to integrate, test, and field an Air-to-Surface missile that is already in use by the fleet on another tactical aircraft platform onto the F/A-18 E/F Super Hornet. Threat intelligence indicates Early Operational Capability (EOC) with a simple targeting mode must be achieved in 3 years, and a Full Operational Capability (FOC) consisting of an advanced targeting mode achieved no later than 12 months after EOC.

2.3.1 The offeror’s response to the Scenario, shall include the following information and outline below:

a. Team - Identify the contractor team members that need to participate in the effort; also, describe the teaming arrangements, roles and responsibilities of any subcontractors, partners, JVs, or other organizations required to perform the work.

b. Assumptions - Detail all assumptions relative to any interpretations made of the sample scenario and your technical approach to ensure full understanding of your response by the Government. Offerors shall assume the Government (F/A-18 & EA-18G IPT) will fulfill the lead integrator role, and should state herein any decision points/approvals expected to be provided throughout the lifecycle of the project by the IPT, Program Office, and/or other Government entity.

c. Technical Approach - Provide a detailed description of the technical approach including a step-by-step procedure and methodology which would be used in accomplishing the scenario. Included in the technical approach should be areas that will need to be investigated and information identified in order to perform the work. Describe how to leverage modern software development approaches and other proven methodologies to reduce risk and ensure a quality product that satisfies the fleet need.

d. Performance Risk Analysis - Identify contingent events inherent to the nature of the effort that could, if they were to occur, endanger satisfactory project performance. Focus on critical events that are realistically likely to occur and that would pose serious problems (do not try to identify every event that could cause some minor difficulty).

e. Roadmap/Schedule - Provide a schedule of events and milestones that communicate the delivery of capability for the duration of the project and key interdependencies.

f. Models & Tools - Identify the models and / or other tools that would be utilized to perform the task.

VOLUME 3 - PAST PERFORMANCE

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

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 contracts (where for the purpose of these instructions the term contract also refers to delivery order or task order), or those portions of a relevant contract, whose performance is within five years of the proposal due date for the principal entities, identified in Table ES-1 (Offeror Summary). The relevant contracts provided for each principal entity shall be relative to its proposed role and responsibilities identified in Table ES-1 (Offeror Summary). Commercial contracts may be included. Offerors shall also identify relevant contracts within the past five years of the proposal due date that had any show-cause notices, cure notices, or termination for default. The Offeror shall complete Table ES-2 (Relevant Contract Summary For Past Performance provided in Attachment L-1 (Executive Summary Tables), for all contracts proposed as relevant for Past Performance.

In Annex A (Final Versions of Previous Statement of Work (SOW)/Performance Work Statement (PWS)/Other Supporting Documentation for Past Performance), the Offeror shall provide electronic copies of the complete final versions of the SOW/PWS or other supporting solicitation/contract documentation from each contract or delivery/task order reference identified in Table ES-2 (Relevant Contract Summary). For contract references that contain delivery/task orders, additionally provide the work description for each specific delivery/task order. For contract references where the Offeror performed as a subcontractor, the Offeror shall also provide a complete electronic copy of the SOW/PWS or other documentation of the agreement between the prime and subcontractor that clearly defines the portions of the work effort of the Prime’s SOW/PWS that the Offeror performed as a subcontractor.

Contract Performance Assessment Reporting System (CPARS) and Questionnaires will be the primary customer feedback data used to evaluate the Offeror’s past performance. The Past Performance Information Reporting System (PPIRS) will be the primary method used to retrieve the CPARS for this source selection. For all contracts identified that do not have a CPARS, the Offeror shall forward a copy of Attachment L-4 Past Performance Questionnaire to that contract’s Procuring Contracting Office (PCO), Administrative Contracting Officer (ACO), and Program Manager (PM); or commercial contractor equivalents. Please forward all questionnaires within two weeks from this solicitation’s release date to allow adequate time for the recipient to respond. Note that the Offeror should not reference this solicitation’s number when distributing the past performance questionnaires to customers. The Offeror should include instructions for the customers to send completed questionnaires within two weeks of its receipt via e-mail to the PCO/Contract Specialist, identified in 4.1 (Proposal Submission). The Offeror shall ensure that all points of contact are current and include an email address and phone number. The Offeror shall not conduct follow-up actions with regard to this questionnaire, 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.

0. Authorization Letter(s)

The Offeror should 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 signed letter(s) should be included in a separate tab within Volume 3 (Past Performance). This authorization letter allows the Government to coordinate past performance issue(s) with the Prime Offeror. For any principal entity (including JV team members) that does not provide an authorization letter with such written consent, the Offeror shall provide point of contact information for each principal entity. This contact information shall include a name, address, phone number, and email address (including JV team members), with whom the Government may coordinate any issues and obtain responses as needed. Offerors are advised that if it does not submit the Release of Adverse Past Performance Authorization Letters with written consent, then 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.

3.2 Relevant Contract Data

For each contract identified for past performance in Table ES-2 (Relevant Contract Summary) provided in Attachment L-1 (Executive Summary Tables), the Offeror shall complete Attachment L-5 Table PP-1 (Past Performance Contract Data), according to the instructions within the attachment and submit it within this section and as a separate electronic file. Please note that this form is a summary of the principal entities’ relevant contract data. All detailed information and comparative analysis of the past performance contract references to this solicitation’s requirements shall be provided in Volume 3 (Past Performance), Section 3.3 (Evaluation), of the Offeror’s proposal. The contract references designated in Table ES-2 (Relevant Contract Summary) shall be used in completing Volume 3 (Past Performance) and all contract references shall be numbered the same throughout all of the Offeror’s proposal volumes (i.e., the contracts identified as P1, S1, T1, C1 etc.)

If a contract has D.O.s/T.O.s, provide a separate contract reference and separate PP-1 tab for each D.O/T.O. The Offeror may use one reference number/PP-1 tab for multiple D.O.s/T.Os if they are the same work effort and performed under the same CPAR; however, identify the dollar amount and period of performance for each. Do not provide a contract reference to the basic contract.

In general, recent performance will be considered a better indicator of future performance. If the Offeror is proposing as a JV, the Offeror should provide the relevant contracts for the JV as a whole, and for each team member of the JV.

3.3 Evaluation

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

For each contract identified in Attachment L-5 Table PP-1 (Past Performance Contract Data), the Offeror shall provide contract data regarding relevancy, past performance information, demonstrated systemic improvement as described below, organized by contract reference. 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 contract references where the principal entities are aware of problems, the Offeror shall describe the issues in section 3.3.b (Past Performance Information). For each past performance problem identified, describe the status of the systemic improvement efforts in section 3.3.c (Demonstrated Systemic Improvement).

a. Relevancy: Offerors are required to explain what aspects of the referenced contracts are deemed relevant, as defined by Section M, to this solicitation’s requirements. To demonstrate relevancy, Offerors shall provide a comparative analysis to the scope, magnitude, and complexity or similarity of this solicitation’s requirements. Within the comparative analysis, Offerors should identify the relevant portions (sections, paragraphs, and page numbers) of the referenced contract’s SOW/PWS (Annex A) to clearly identify how past efforts performed are similar to this solicitation’s requirements. In addition, the referenced sections only need to be identified and the full text does not need to be broken out separately from the complete SOW/PWS.

The reference contract(s) provided should be relative to each principal entity’s proposed role/responsibility identified in Table ES-1 (Offeror Summary) versus relative to the whole solicitation. For example, a subcontractor who is being proposed to perform only software has a past contract whose total work is software. Even though the software effort is only 10% of the hypothetical solicitation’s effort, the previous contract relates to 100% of the subcontractor proposed effort for the hypothetical solicitation and therefore the reference contract would be considered Very Relevant vice Somewhat Relevant.

For a discussion on CAGE Code/DUNS, refer to section 1.0 Volume 1 (Executive Summary). Offerors should be advised that the CAGE Code/DUNS for each referenced contract is considered as part of the Relevancy determination, which determines if the contract reference will be included in the Past Performance evaluations. Note: Any information regarding CAGE Code/DUNS should be included within Volume 1 (Executive Summary) and does not need to be repeated here.

Offerors are advised that contracts assessed as not relevant by the Government will not be considered in the Past Performance assessments.

b. Past Performance Information: For the relevant contracts provide a brief description of past performance in delivering quality services. Include in these descriptions any information that demonstrates the level of performance obtained, where available; provide quantifiable measures/trends to demonstrate past and current performance. Also describe past problems, including when they occurred, what the circumstances were surrounding the situation, and what the consequences were as a result of the problem.

c. Demonstrated Systemic Improvement: Identify systemic improvement actions taken to resolve any past problems identified in 3.3.b (Past Performance Information). Provide the records of such results and indicate where they are documented, preferably in Government record systems. Describe the techniques, elements, and tools used to correct problems on the reference contract and, if applicable, how these techniques, elements, and tools may be used for the contract to be awarded as the result of this solicitation. Provide quantifiable evidence or metrics that substantiate or demonstrate claims of improvement and to demonstrate that the past problem will not occur on the contract to be awarded as the result of this solicitation. It is incumbent upon the Offeror to explain the relevance of the data provided and substantiate that improvements from past performance problems are being made. The Government does not assume the duty to search for data to cure the problems it finds in the information provided by the Offeror. Consideration for discounting problems may be given when those problems are addressed through demonstrated systemic improvement. Demonstrated systemic improvement may be indicated by information as it relates to preventing recurrence of past problems, including: identification of the root cause of a problem, a corrective action plan that systemically addresses the past problem, how and when the plan was implemented, documented timeframe to demonstrate when corrective action was implemented and became successful; and performance data, preferably through Government records, to show performance improvements. With regard to performance improvement data, explain the likelihood to which the problem will not reoccur on during the performance of this prospective contract based on the amount of time that good performance was sustained in consideration of the nature of the past problem and effort.

4. VOLUME 4 – COST

4.1 General Information

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

Section L, Attachment (L-6) Cost Attachments, which includes the following:

All costs shall be contained in RFP Section B, N68936-20-R-0102 (see Section 5 Model Contract), and the cost proposal. The Government is required to evaluate each proposal relative to the cost criteria submitted in response to Section M. Proper presentation and adequate supporting documentation will ensure the cost proposal is efficiently evaluated and all assumptions are understood. The burden of proof for cost credibility rests with the Offeror.

Adequate substantiation is necessary for the Government to evaluate the cost and scope of the Offeror’s estimate for realism and completeness, and to ensure all required labor categories, associated hours, and Government provided cost totals for Travel, Materials and ODCs by year are included in the cost proposal. Proper presentation and adequate supporting documentation will ensure the cost proposal is efficiently evaluated and all assumptions are understood. The burden of proof for cost substantiation and credibility rests with the Offeror.

The information required in these cost instructions applies to the Offeror, any JV Team Member, and any subcontractor.

All subcontractors must complete and submit Attachment CA-2 (Subcontractor Cost Breakout Spreadsheet) and provide substantiation to support all proposed rates as described in this Cost section. Prime Offerors must account for these subcontractors in their CA-1 (Prime Cost Breakout Spreadsheet) in the subcontractor’s section by providing each of the labor categories proposed by the subcontractor, the hours associated with the proposed labor categories, and the fully burdened labor rate for the proposed categories by contract year. The Prime Offeror must provide justification of the reasonableness of each subcontractor's proposed fully burdened labor rates. A discussion for the basis of this determination is required. The proposed fully burdened rates of the Prime Offeror and all subcontractors will be subject to the NAVAIR tripwires described in Section M of the solicitation.

Due to the proprietary nature of company rates, rate information may be presented separately for each Offeror and JV Team Member/subcontractor, provided that the Offeror identifies the data and contractor in its proposal. Each JV Team Member/subcontractor that is required to provide a separate volume shall submit their cost breakdown data on Attachment CA-2 (Subcontractor Cost Breakout Spreadsheet). The proposed subcontractor costs in the CA-2 Attachment must be consistent with the proposed cost for that subcontractor/JV Team Member in the Prime Offeror’s CA-1 Attachment, prior to the Prime Offeror’s application of burdens or pass through on the subcontractor/JV Team Member labor.

The Government is not soliciting any Offeror investments. However, in order to properly assess a proposed cost 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 any such investments. Additionally, the Offeror shall propose an H-clause that clearly identifies what equipment and/or material, and the associated data and data rights that are conveyed to the Government, and that also specifically states the fiscal adjustment(s) and identifies the Offeror’s liability in accordance with Volume 5 (Contract Administration), paragraph (e)(3). In addition, any Ground rules and Assumptions associated with an investment shall be submitted in Volume 4 Section 4.3.2, (Cost Narrative). At the discretion of the PCO, this may be a contractually binding clause.

As this procurement will result in a cost type contract, Offerors shall provide documentation verifying that their company has an Accounting System approved in accordance with DFARS clause 252.242-7006, or state that its Accounting System has not been approved by DCAA. If subcontractors or JV Team Members are being proposed, the prime Offeror shall disclose the contract type (e.g. CPFF, T&M, FFP, etc.) that is proposed to be utilized with each of their subcontractors/JV Team Members. If the subcontract with a proposed subcontractor or JV Team Member will be a cost type contract (e.g. CPFF), the subcontractor or JV Team Member must also provide documentation verifying that it has an approved accounting system.

4.2 Cost Proposal Guidelines

4.2.1 As this is a non-performance-based requirement, the Offeror shall propose a level of effort in accordance with the Government provided labor categories and hours (by year) as shown in Attachment CA-1.