N00421-15-R-0020-0001.doc

N00421-15-R-0029

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The following have been added by full text:

AMENDMENT 1 SUMMARY OF CHANGES

SECTION I - CONTRACT CLAUSES

The following were previously included by reference and are now included by full text:

252.204-7012 SAFEGUARDING COVERED DEFENSE INFORMATION AND CYBER INCIDENT INFORMATION (DEC 2015)

(a) Definition. As used in this clause -- "Adequate security" means protective measures that are commensurate with the consequences and probability of loss, misuse, or unauthorized access to, or modification of information.

"Compromise" means disclosure of information to unauthorized persons, or a violation of the security policy of a system, in which unauthorized intentional or unintentional disclosure, modification, destruction, or loss of an object, or the copying of information to unauthorized media may have occurred.

"Contractor attributional/proprietary information" means information that identifies the contractor(s), whether directly or indirectly, by the grouping of information that can be traced back to the contractor(s) (e.g., program description, facility locations), personally identifiable information, as well as trade secrets, commercial or financial information, or other commercially sensitive information that is not customarily shared outside of the company.

"Contractor information system" means an information system belonging to, or operated by or for, the Contractor.

"Controlled technical information" means technical information with military or space application that is subject to controls on the access, use, reproduction, modification, performance, display, release, disclosure, or dissemination. Controlled technical information would meet the criteria, if disseminated, for distribution statements B through F using the criteria set forth in DoD Instruction 5230.24, Distribution Statements on Technical Documents. The term does not include information that is lawfully publicly available without restrictions.

"Covered defense information" means unclassified information that --

(i) Is --

(A) Provided to the contractor by or on behalf of DoD in connection with the performance of the contract; or

(B) Collected, developed, received, transmitted, used, or stored by or on behalf of the contractor in support of the performance of the contract; and

(ii) Falls in any of the following categories:

(A) Controlled technical information.

(B) Critical information (operations security). Specific facts identified through the Operations Security process about friendly intentions, capabilities, and activities vitally needed by adversaries for them to plan and act effectively so as to guarantee failure or unacceptable consequences for friendly mission accomplishment (part of Operations Security process).

(C) Export control. Unclassified information concerning certain items, commodities, technology, software, or other information whose export could reasonably be expected to adversely affect the United States national security and nonproliferation objectives. To include dual use items; items identified in export administration regulations, international traffic in arms regulations and munitions list; license applications; and sensitive nuclear technology information.

(D) Any other information, marked or otherwise identified in the contract, that requires safeguarding or dissemination controls pursuant to and consistent with law, regulations, and Governmentwide policies (e.g., privacy, proprietary business information).

"Cyber incident" means actions taken through the use of computer networks that result in a compromise or an actual or potentially adverse effect on an information system and/or the information residing therein.

"Forensic analysis" means the practice of gathering, retaining, and analyzing computer-related data for investigative purposes in a manner that maintains the integrity of the data.

"Malicious software" means computer software or firmware intended to perform an unauthorized process that will have adverse impact on the confidentiality, integrity, or availability of an information system. This definition includes a virus, worm, Trojan horse, or other code-based entity that infects a host, as well as spyware and some forms of adware.

"Media" means physical devices or writing surfaces including, but not limited to, magnetic tapes, optical disks, magnetic disks, large-scale integration memory chips, and printouts onto which information is recorded, stored, or printed within an information system.

"Operationally critical support" means supplies or services designated by the Government as critical for airlift, sealift, intermodal transportation services, or logistical support that is essential to the mobilization, deployment, or sustainment of the Armed Forces in a contingency operation.

"Rapid(ly) report(ing)" means within 72 hours of discovery of any cyber incident.

"Technical information" means technical data or computer software, as those terms are defined in the clause at DFARS 252.227-7013, Rights in Technical Data - Non Commercial Items, regardless of whether or not the clause is incorporated in this solicitation or contract. Examples of technical information include research and engineering date, engineering drawings, and associated lists, specifications, standards, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code.

(b) Adequate security. The Contractor shall provide adequate security for all covered defense information on all covered contractor information systems that support the performance of work under this contract. To provide adequate security, the Contractor shall -

(1) Implement information systems security protections on all covered contractor information systems including, as a minimum --

(i) For covered contractor information systems that are part of an Information Technology (IT) service or system operated on behalf of the Government -

(A) Cloud computing services shall be subject to the security requirements specified in the clause 252.239-7010, Cloud Computing Services, of this contract; and

(B) Any other such IT service or system (i.e., other than cloud computing) shall be subject to the security requirements specified elsewhere in this contract; or

(ii) For covered contractor information systems that are not part of an IT service or system operated on behalf of the Government and therefore are not subject to the security requirement specified at paragraph (b)(1)(i) of this clause --

(A) The security requirements in National Institute of Standards and Technology (NIST) Special Publication (SP) 800-171, "Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations," http://dx.doi.org/10.6028/NIST.SP.800-171 that is in effect at the time the solicitation is issued or as authorized by the Contracting Officer, as soon as practical, but not later than December 31, 2017. The Contractor shall notify the DoD CIO, via email at osd.dibcsia@mail.mil, within 30 days of contract award, of any security requirements specified by NIST SP 800-171 not implemented at the time of contract award; or

(B) Alternative but equally effective security measures used to compensate for the inability to satisfy a particular requirement and achieve equivalent protection accepted in writing by an authorized representative of the DoD CIO; and

(2) Apply other security measures when the Contractor reasonably determines that such measures, in addition to those identified in paragraph (b)(1) of this clause, may be required to provide adequate security in a dynamic environment based on an assessed risk or vulnerability.

(c) Cyber incident reporting requirement.

(1) When the Contractor discovers a cyber incident that affects a covered contractor information system or the covered defense information residing therein, or that affects the contractor's ability to perform the requirements of the contract that are designated as operationally critical support, the Contractor shall --

(i) Conduct a review for evidence of compromise of covered defense information, including, but not limited to, identifying compromised computers, servers, specific data, and user accounts. This review shall also include analyzing covered contractor information system(s) that were part of the cyber incident, as well as other information systems on the Contractor's network(s), that may have been accessed as a result of the incident in order to identify compromised covered defense information, or that affect the Contractor's ability to provide operationally critical support; and

(ii) Rapidly report cyber incidents to DoD at http://didnet.dod.mil.

(2) Cyber incident report. The cyber incident report shall be treated as information created by or for DoD and shall include, at a minimum, the required elements at http://didnet.dod.mil.

(3) Medium assurance certificate requirement. In order to report cyber incidents in accordance with this clause, the Contractor or subcontractor shall have or acquire a DoD-approved medium assurance certificate to report cyber incidents. For information on obtaining a DoD-approved medium assurance certificate, see http://iase.disa.mil/pki/eca/Pages/index.aspx.

(d) Malicious software. The Contractor or subcontractors that discover and isolate malicious software in connection with a reported cyber incident shall submit the malicious software in accordance with instructions provided by the Contracting Officer.

(e) Media preservation and protection. When a Contractor discovers a cyber incident has occurred, the Contractor shall preserve and protect images of all known affected information systems identified in paragraph (c)(1)(i) of this clause and all relevant monitoring/packet capture data for at least 90 days from the submission of the cyber incident report to allow DoD to request the media or decline interest.

(f) Access to additional information or equipment necessary for forensic analysis. Upon request by DoD, the Contractor shall provide DoD with access to additional information or equipment that is necessary to conduct a forensic analysis.

(g) Cyber incident damage assessment activities. If DoD elects to conduct a damage assessment, the Contracting Officer will request that the Contractor provide all of the damage assessment information gathered in accordance with paragraph (e) of this clause.

(h) DoD safeguarding and use of contractor attributional/proprietary information. The Government shall protect against the unauthorized use or release of information obtained from the contractor (or derived from information obtained from the contractor) under this clause that includes contractor attributional/proprietary information, including such information submitted in accordance with paragraph (c). To the maximum extent practicable, the Contractor shall identify and mark attributional/proprietary information. In making an authorized release of such information, the Government will implement appropriate procedures to minimize the contractor attributional/proprietary information that is included in such authorized release, seeking to include only that information that is necessary for the authorized purpose(s) for which the information is being released.

(i) Use and release of contractor attributional/proprietary information not created by or for DoD. Information that is obtained from the contractor (or derived from information obtained from the contractor) under this clause that is not created by or for DoD is authorized to be released outside of DoD--

(1) To entities with missions that may be affected by such information;

(2) To entities that may be called upon to assist in the diagnosis, detection, or mitigation of cyber incidents;

(3) To Government entities that conduct counterintelligence or law enforcement investigations;

(4) For national security purposes, including cyber situational awareness and defense purposes (including with Defense Industrial Base (DIB) participants in the program at 32 CFR part 236); or

(5) To a support services contractor ("recipient") that is directly supporting Government activities under a contract that includes the clause at 252.204-7009, Limitations on the Use or Disclosure of Third-Party Contractor Reported Cyber Incident Information.

(j) Use and release of contractor attributional/proprietary information created by or for DoD. Information that is obtained from the contractor (or derived from information obtained from the contractor) under this clause that is created by or for DoD (including the information submitted pursuant to paragraph (c) of this clause) is authorized to be used and released outside of DoD for purposes and activities authorized by paragraph (i) of this clause, and for any other lawful Government purposes or activity, subject to all applicable statutory, regulatory, and policy based restrictions on the Government's use and release of such information.

(k) The Contractor shall conduct activities under this clause in accordance with applicable laws and regulations on the interception, monitoring, access, use, and disclosure of electronic communications and data.

(l) Other safeguarding or reporting requirements. The safeguarding and cyber incident reporting required by this clause in no way abrogates the Contractor's responsibility for other safeguarding or cyber incident reporting pertaining to its unclassified information systems as required by other applicable clauses of this contract, or as a result of other applicable U.S. Government statutory or regulatory requirements.

(m) Subcontracts. The Contractor shall --

(1) Include this clause, including this paragraph (m), in subcontracts, or similar contractual instruments, for operationally critical support, or for which subcontract performance will involve a covered contractor information system, including subcontracts for commercial items, without alteration, except to identify the parties; and

(2) When this clause is included in a subcontract, require subcontractors to rapidly report cyber incidents directly to DoD at http://dibnet.dod.mil and the prime Contractor. This includes providing the incident report number, automatically assigned by DoD, to the prime Contractor (or next higher-tier subcontractor) as soon as practicable.

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

The following have been added by full text:

SECTION J

Exhibit/Attachment Table of Contents

DATE

6 June 2016

10 June 2016

15 July 2015

6 January 2015

8 July 2015

13 June 2016

17 December 2014

19 May 2014

18 December 2014

17 December 2014

17 December 2014

10 December 2013

23 December 2014

13 June 2016

2 June 2016

AMENDMENT 1 SUMMARY OF CHANGES

· Update due date for RFP to 12 July 2016

· Update Clause 52.233-2 to Demetrius Green instead of Daniel Chambers

· Section L- 2, paragraph 4.2 - Edit Instructions to indicate numbered notes

· Edit Attachment P-6A to Indicate Subcontractors not Principal Subcontractors

· Update cybersecurity clause : 252.204-7012 Dec 2015

· Update Attachment P-5 (PPQ) requested date on P-5 to 12 July 2016

· #12 Updated SOW page 33, Para. 16.3 Subject Matter Expert II (SOW Paragraph 3.4) under Education: removed “ALLOWABLE SUBSTITUTION: A BS or BA degree and an additional four (4) years of experience can be substituted for an MS or MA degree.”

· (a) Updated SOW Page 3 SECNAV Instruction # from 5239.3B to 5239.3C. Changed Title from Department of the Navy Information Assurance (IA) Policy to Department of the Navy Cybersecurity. (b) Updated SOW page 5 removing 8020.14E from in front of Shore Station Explosives Compliance (ESI) Program and replaced it with 8020.14F. (c) Updated SOW page 5 4161.2M - DoD Manual 4161.2M was replaced with Guidebook for Contract Property Administration. Removed this from under DOD manuals and placed Guidebook under Handbook section. (d) Updated SOW page 5 8500.1 from Information Assurance to Cybersecurity.

· Update SOW page 27, Para. 16 under Engineering/Electronics Technician, Senior (Key) (SOW Paragraph 3.2) to remove “development “from 2nd sentience.

· Updated CDRL A006 Block 5: from SOW Para. 7.0 to SOW Para. 6.0

· Update CDRL A002 Block 5: from SOW Para. 3.2.8/3.3.5/3.5.1/3.5.3 to SOW Para. 3.2.8/3.3.5/3.5.2/3.5.3/3.5.5

· Update CDRL A004 Block 2: from Funds Expenditure Report to Program/Financial Execution Report. Block 3: from Monthly Funds Expended/Hours/NMCI to Monthly Hours/Funds Expended

· Updated CDRL A007 Block 5: from SOW Para. 9.1.1 to SOW Para. 8.1.1

· Updated CDRL A008 Block 2: from Information Assurance (IA) Training Completion Report to Cybersecurity Training Completion Report. Block 3: removed Info Technology Personnel Security Report. Block 5: from SOW Para. 13 to SOW Para. 12

· Updated CDRL A009 Block 5: from SOW para. 8.3 to SOW para. 7.3

· Updated SOW page 3 COMNAVREGMIDATLATIC to COMNAVREGMIDLANT

· Updated SOW page 4 8020.1J to 8020.1K

· Updated SOW page 5 from 5090.5 to 5090.5A

· Updated SOW page 5 from 8010.1B to 8010.1D

· Updated SOW page 5 from 8020.14E to 8020.15D. Changed from NAS Explosive Safety Self-Assessment (ESSA) Program to NAS Explosives Safety Compliance Program and Self-Assessment Plan.

· Updated SOW Page 5 to remove 8010.2B. Was obsolete and replaced by 8010.1D

· Updated SOW page 5 to remove 8020.14E from in front of Shore Station Explosives Compliance (ESI) Program and replaced it with 8020.14F.

· Updated SOW page 5 from 8020.6D to 8020.6E

· Updated SOW page 22, Para. 9.1.2 to change Information Assurance (IA) to Cybersecurity

· Updated SOW page 23, para. 12.0 to change Information Assurance to Cybersecurity within the title and throughout the paragraph.

· Updated Attachment 5 changing heading from IA to CYBERSECURITY.

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been added by full text:

PROPOSAL INSTRUCTIONS

Section L - Instructions, Conditions and Notices to Bidders

L-1 General Information

1.1 Small Business Considerations

This contract is a 100% Small Business set-aside under NAICS code 541712 and only Small Businesses who meet the Size Standard Exception for Aircraft (1,500 employees), will be considered for award of this requirement. Proposals from other contractors will not be considered.

1.2 Effective Offers

The Government intends to award a single Cost-Plus-Fixed-Fee type contract as a result of this solicitation. Each offeror shall submit a proposal that clearly and concisely describes and defines the offeror’s response to the requirements of this solicitation. Use of general or vague statements such as “standard procedures will be used” will not satisfy this requirement. Unnecessary elaboration beyond that sufficient to present a complete and effective proposal is not desired.

1.3 Offers in Accordance With Instructions

Each offeror shall submit an offer/proposal and other information in strict accordance with these instructions. Each offeror’s submission shall be screened by the Contracting Officer (KO) or a designee upon receipt to ensure compliance with the instructions contained in the Request for Proposal (RFP). Throughout these instructions, a "principal subcontractor" is defined as a subcontractor who provides at least 15% of the proposed total price/cost (excluding the Offeror's profit/fee), for the contract.

1.4 Questions

Offerors may submit questions requesting clarification of solicitation requirements to the personnel identified in Block 7 of the RFP. It is requested that all questions be received within fifteen (15) days of the date this solicitation was posted. Questions posted after this date may not be answered.

1.5 Estimated Date of Award

For proposal purposes, the estimated date of Contract award is 12 January 2017. The estimated period of performance commences approximately on 1 March 2017. Please note that there is no CLIN associated with the transition period, as the Government will not be reimbursing the contractor for costs associated with transition efforts. Transition costs are considered overhead costs that are not directly charged to the Government, as the incumbent contractor is still performing the tasking under the previous contract during this timeframe.

1.6 Instructions for Submission of Proposals

Proposals shall be submitted electronically via CD-ROM accompanied with 3 hard (paper) copies no later than 1400 Eastern Time on 12 July 2016. In the event of a discrepancy between the electronic and hard copy, the hard copy will take precedence.

In order to maximize efficiency and minimize the effort involved in the proposal evaluation process, all offerors shall comply with the following instructions for proposal format and content. Proposals that do not comply with these instructions may be considered deficient and may render the offeror ineligible for award.

Clearly mark all packages with the solicitation number. Offerors shall submit proposals by hand delivery or via United States Postal Service or through a commercial carrier using the address provided below. Offerors shall not submit proposals by facsimile or electronically via email.

Naval Air Systems Command

Code: AIR 2.5.1.12, Demetrius Green/ Melody Baron

21983 BUNDY ROAD BLDG 441

PATUXENT RIVER, MD 20670-1547

Solicitation Number: N00421-15-R-0029

1.6.1 Proposal Packaging

The Offeror shall package the proposal volumes in cartons or equivalent packaging containers in the most efficient manner possible grouping like volumes to the maximum extent possible. Each container shall be single person portable. Each container should include a packing slip detailing the contents to include the volume number, title, and copy number. Also, each container should be stamped or marked “For Official Use Only” and “Source Selection Information – See FAR-2.101 and 3.104.”

1.6.2 Classified Data

All proposals shall be UNCLASSIFIED.

1.7 Proposal Format

In order to maximize efficiency and minimize the time for proposal evaluation, all offerors shall submit their proposals in accordance with the format and content specified. The electronic proposal shall be prepared so that if an evaluator prints the proposal it meets the following format requirements:

· 8.5 x 11 inch paper

· Single-spaced typed lines

· Newspaper column formatting is not permitted

· 1 inch margins on all sides

· Not smaller than a 10 point font without condensing

· Photographs, pictures or hyperlinks are not permitted

· Files shall be Microsoft Office 2010 compatible

· Tables are permitted

· No ZIP files

· No fold-out pages

· PDF files are permitted

· Hyperlinks are not permitted

· Cost format spreadsheet shall be in Microsoft Excel format with a file name extension of .xlsx

· All file names shall include title of the evaluation factor or subfactor (if applicable)

1.8 Proposal Content

Each proposal shall contain the following volumes/sections:

· Volume 1 Executive Summary

· Volume 2 Technical Proposal

· Volume 3 Past Performance

· Volume 4 Cost/Price Proposal

COST OR PRICING INFORMATION SHALL NOT APPEAR ANYWHERE IN THE PROPOSAL OTHER THAN VOLUME 4.

1.9 Single Offer

In accordance with DFARS 215.371, if a single offer is received, at the Contracting Officer’s discretion, certified cost or pricing data may be required to be submitted subsequent to proposal receipt.

L-2 Proposal Content

The completion and submission to the Government of an offer shall be representative of the Offeror’s unconditional agreement to the terms and conditions of this solicitation. The offer consists of and shall include the following volumes, and shall not exceed the page limits indicated below. Any pages in excess of the stated limit will not be evaluated.

No page limit

Volume 1 – Executive Summary

* Note: No cost/pricing information shall be contained in this Volume.

1.1 Offer Letter

Identify at a minimum the solicitation number; enclosures being transmitted; proposed subcontractors and team members to be utilized under the contract; the CAGE code, DCMA, DCAA, and DFAS for the prime contractor; the CAGE code, DCMA, and DCAA for all proposed subcontractors and team members; acknowledgement of solicitation amendments; and state the length of proposal validity (at least 180 days after proposal submission). Furthermore, offerors are required to acknowledge that, if awarded the contract resulting from this solicitation, all personnel utilized during contract performance will meet the minimum labor category qualifications (including education, experience, and applicable security clearance requirements) outlined in Attachment (1).

1.2 Completed Section K

Complete and submit Section K of the solicitation.

1.3 OCI Disclosure and Mitigation Plans (if applicable)

The offeror shall include an OCI disclosure and OCI Mitigation Plans, if applicable based on offeror’s completion of NAVAIR Provision 5252.209-9511.

1.4 Exclusive Teaming Arrangements that Inhibit Competition

In accordance with NAVAIR 5252.215-9505, offerors are required to:

1. Provide a copy of all teaming arrangements, and

2. Explain why the teaming arrangements do not inhibit competition

Therefore, the offer shall include the information required by this clause in their proposal.

1.5 Business Systems Status

The offeror shall complete a table substantially the same as the one below to identify the current status and or determinations regarding its business systems. If any item is not applicable to the Offeror or for contract performance, state so and provide an explanation. If any item has been determined to be unapproved/inadequate, outline the potential impact on contract execution, mitigation plan, and correction plan. Submit relevant DCAA/DCMA reports, audits, and determinations as necessary within your proposal.

Sample Business Systems Status

Volume 2 – Technical Proposal

* Note: No cost/pricing information shall be contained in this Volume.

2.1 Management Plan

Offerors shall address in sufficient detail the following:

(a) Adequacy of corporate management and resources to support the technical requirements of the solicitation and ability to function as a viable and productive provider of contracted services to the Government;

(b) Proposed lines of responsibility, authority, and communication through which the tasks will be managed;

(c) Procedures to be taken to ensure quality and cost control; and

(d) Identification of potential performance risks and proposed risk mitigation strategies.

2.1.1 Teaming/Subcontracting

Offerors shall present in sufficient detail the following:

(a) Subcontract Management Plan detailing how each subcontractor will be managed to ensure cohesive integration into the overall management approach;

(b) Description of the integration of the team members into the overall management approach and how the Offeror will leverage their strengths to increase value to the Government through technical leadership, quality assurance, and process improvement;

(c) How and why selected subcontractor(s) were chosen, which knowledge and skills they will be acquiring through each subcontract, and the level of subcontract effort expected.

2.1.2 Transition Plan

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 workplace changeover within 45 days from an incumbent with no loss of service and minimal loss of corporate knowledge. The plan should take into consideration the following elements as well as any additional elements deemed necessary by the Offeror:

(a) Work Turnover

(b) Quality Assurance

(c) Training

(d) Risk Mitigation strategies

(e) Security Requirement to include OPSEC, facility clearances, and base access

(f) Data Transfer

2.2 Understanding and Approach

Offerors shall describe how to implement appropriate (NAVAIR, USN, DoD, etc.) instructions / guidance when assisting the Government with the following:

· Prepare for a Weapon Flight Test?

· Develop a Non-Standard Aircraft Store Interface?

· Prepare and conduct an Ordnance Ground Test?

Offerors shall also describe the process to perform the following efforts:

· Acquire fragmentation data and create a fragmentation file to be used for safe escape calculations?

· Determine a drag curve for a ballistic weapon?

· Generate safe escape tables for fleet weapon employment?

2.3 Staffing and Personnel

2.3.1 Workforce

The offeror shall submit a workforce plan which addresses the following:

(a) Recruitment procedures that would provide a qualified workforce;

(b) Description of their process for qualifying personnel to execute the SOW;

(c) Explanation of approaches for maintaining technical competence to to execute the SOW;

(d) Employee retention plan that would provide workforce improvements and upgrade the skills of highly trained and motivated personnel; and

(e) Availability of personnel proposed for this effort at award. This section of the workforce plan shall specifically identify the personnel who are readily available “current employees”, “contingent hires”, or “prospective hires”; including subcontractors. A “contingent hire” is an individual who has committed, under a signed letter of intent, to being employed by the offeror if the offeror is awarded the contract. The letter of intent is a separate written agreement signed by the potential employee(s) to work for the offeror effective at contract award. A “prospective hire” is an individual that the offeror has committed to hiring if the offeror is awarded the contract whose identity may not be known until after contract award. Specific names and a discussion of detailed personnel experience or associated qualifications is not required in the workforce plan; however, offerors are reminded that personnel shall meet the corresponding labor category qualifications during contract performance.

2.3.2 Key Personnel

The Offeror shall provide resumes for the key personnel identified below (see Section 17 of the SOW for more information), identifying their experience, skills, education, training, qualifications, certifications, and security clearances:

(1) Program Manager

(2) Engineering/Electronics Technician, Senior

(3) Systems Analyst, Senior

Volume 3 - Past Performance

* Note: No cost/pricing information shall be contained in this Volume.

3.1 References

The offeror shall submit up to a maximum of five (5) contracts, or those portions of a contract, similar in size, scope, and/or complexity which are ongoing or were completed within the last five (5) years for itself or its principal subcontractors, if any. Commercial contracts may be included. At least two (2) of these contracts should be efforts that were performed by the prime contractor. When providing these references, the offeror shall use the format identified in the Past Performance Matrix below:

Past Performance Matrix

Contract Type

Program Name

Prime or Sub

Contract Value

Period of Performance

Brief Description

Name, Phone & Email of PCO

Name, Phone & Email of COR

Recency1

1Recency: See definition in Section M, paragraph 5.4.3

3.2 CPARS

For the submitted contracts (up to a maximum of 5), Contractor Performance Assessment Reporting System (CPARS) assessments for the last five (5) years will be used to evaluate past performance. For contracts with CPARS that are more than 12 months old, the offeror will complete items numbered 1 through 8 on page 1 of the Past Performance Questionnaire Package for Services (Attachment P5) and forward it to the contract customer’s Program Manager to address only the items numbered 9 to 15 on page 1. For all contracts identified which do not have CPARS, the offeror shall complete items numbered 1 through 8 on page 1 of the Past Performance Questionnaire Package for Services (Attachment P5) and forward the 2 pages to that contract customer’s Technical Point of Contact (TPOC) or Contracting Officer’s Representative (COR). All questionnaires shall be forwarded with enough lead-time so that responses can be received by the Government concurrent with the closing date of the solicitation. The offeror shall include past performance package instructions to the customers. This submittal information is provided at the top of the questionnaires to facilitate the offeror’s effort in meeting these instructions. The offeror shall not conduct follow-up actions with regard to this questionnaire. The Government will ensure that the customers have received and will respond to the questionnaires. The Government may send any other questionnaires as necessary. FOR CONTRACTS THAT ARE CURRENTLY IN THE CONTRACTOR PERFORMANCE ASSESSMENT REPORTING SYSTEM (CPARS), AND FOR WHICH ANNUAL REPORTING HAS BEEN PERFORMED, DO NOT SEND THE PAST PERFORMANCE QUESTIONNAIRE FOR SERVICES TO THE CUSTOMER. FOR CONTRACTS THAT HAVE BEEN COMPLETED AND THE FINAL CPAR HAS BEEN FINALIZED IN CPARS, DO NOT SEND THE PAST PERFORMANCE QUESTIONAIRE FOR SERVICES TO THE CUSTOMER.

3.3 Other Past Performance Data

Offerors are advised that the Government may use and evaluate independently obtained past performance data, such as the Past Performance Information Retrieval System (PPIRS); Past Performance Questionnaires (PPQs); Federal Awardee Performance and Integrity Information System (FAPIIS); Electronic Subcontract Reporting System (eSRS); other databases; interviews with Program Managers, Contracting Officers, Fee Determining Officials, the Defense Contract Management Agency (DCMA), or other individuals; as well as, or in addition to, all recent and relevant past performance data provided by the Offeror. The Government reserves the right to contact, or elect not to contact, any or all of the sources provided by the offeror. Therefore, it is incumbent upon the Offeror to explain the relevance of any past performance data provided. Furthermore, the Government does not assume the duty to search for data to explain or remedy any inconsistencies it finds in the information provided by the offeror. The burden of providing thorough and complete past performance information remains with the offeror.

3.4 No Past Performance

If the offeror does not have any past performance, it shall provide an affirmative statement stating it has no past performance.

3.5 Subcontractor Past Performance

Offerors shall provide written consent from their primary subcontractors that will allow the Government to coordinate their past performance issue(s) with the prime offeror. If offerors do not submit such written consent, then the Government will address any past performance issues directly with the principal subcontractor and the offeror will forfeit the opportunity to participate in any related discussions. Consequently, for any subcontractors that do not provide such written consent, provide a point of contact (name, address, phone number, and email address) with whom the Government may coordinate these issues and obtain any responses as needed.

Volume 4 - Cost/Price Proposal

4.1 Section B - CLIN Pricing

For proposal purposes, the Government will allocate proposed cost and fee totals from the Contractor’s proposed Attachment P-6 to Section B based on anticipated funding. However, the Government reserves the right to re-allocate proposed cost and fee at award and during execution based on anticipated funding. The cost and fee totals proposed in Attachment P6 will be used as the official proposed prices.

4.2 Cost Summary Spreadsheet (Attachment P6)

The cost/price proposal shall be submitted as a separate electronic file via CD-ROM. All cost and/or pricing information shall be contained in Volume 4 only. Offerors shall submit their cost/price proposal utilizing the Cost Summary Spreadsheet (Attachment P6). The offeror shall submit a fully completed Cost Summary Spreadsheet. The file shall be unprotected and unlocked, with formulae intact to show mathematical operations. All data entries in the spreadsheet shall reference information within the workbooks present in the spreadsheet; under no circumstances may any data presented in the spreadsheet be linked to other files. Offerors shall carefully follow the numbered notes provided within the Cost Summary Spreadsheet.

4.2.1 RESERVED

4.2.2 Subcontractor Rate Submittal

Any and all subcontractors shall provide their own Cost Summary Spreadsheet delineating the build-up of all direct and indirect rates directly to the Government. For pricing purposes, subcontractors should disclose their fully burdened labor rates to the prime.

4.3 Required Cost/Price Information

In preparing the cost/price proposal, the offeror shall ensure the submittal includes the following:

4.3.1 Propose to the Requested Level of Effort

As this is a non-performance-based requirement, the offer shall propose level of effort by labor category in accordance with the Government estimate provided in the table below. The total hours proposed, inclusive of prime contractor hours and subcontractor hours, shall be equal to the table below; deviations are not permitted and may render the offer unawardable. The Hours per Labor Category are allocated by SOW Paragraph and further differentiated by Regular or Overtime Hours in the table below to assist offerors in preparing the cost summary.

Base Man-Years Sum of

Base Hours Sum of

OY 1 Hours Sum of

OY 2 Hours Sum of

OY 3 Hours Sum of

OY 4 Hours Sum of

Total Hours

This estimate provides the number of hours the contractor will be required to propose in response to this solicitation; however, actual contract performance may vary from this estimate. Accordingly, the Government cannot guarantee that the contractor will perform either the estimated quantities of hours shown for individual labor categories or the total estimated hours.

4.3.2 Limitation on Subcontracting

This requirement is being set-aside for small businesses. Therefore Attachment P6, the Cost Summary Spreadsheet, will be used to demonstrate how the prime contractor will perform at least 50 percent of the cost of contract performance incurred with its own employees for the duration of the contract in accordance with FAR clause 52.219-14. The cost of contract performance incurred by the prime’s employees will be calculated using the Cost Summary Spreadsheet and will include both direct and indirect (fringe benefits, overhead, G&A) costs which are allocable to direct labor hours.

4.4 Cost Narrative

Provide a narrative that addresses any assumptions made during the preparation of the cost/price proposal and discuss the basis for the cost elements listed below:

4.4.1 Substantiation for Direct Labor Rates by Category

The offeror and proposed subcontractors are required to submit labor rates for proposed individuals. The offeror and proposed subcontractors shall provide payroll verification for currently employed proposed personnel and contingent offer letters outlining salary information for contingent hires. Verification of direct labor rates shall be provided for current employees; this could consist of, for example, screen-captures (or equivalent) from the offeror’s payroll system or a form containing the title, direct labor rate and a signed certification by an authorized representative of the company. Offerors retain discretion with respect to the documentation provided to substantiate the direct labor rates of current employees; however, the Government must be able to calculate the employee’s current hourly rate based on the information provided. If any of the rates utilized by the offeror or any subcontractors differ from the payroll verification, a justification shall be provided for the difference. For any prospective hires, provide information to substantiate the rates proposed. If composite or category averages are proposed, provide a breakdown of how rates are developed. Offerors shall also describe their pricing methodology for overtime hours.

4.4.2 Substantiation for Escalation on Labor

Offerors, including subcontractors, shall address escalation for all labor categories and shall provide rationale for the specific escalation rate used. Offerors that do not include escalation, or provide an explanation as to why it was not included, may be considered unrealistically low and may have their proposals adjusted by the Government to include escalation.

4.4.3 Substantiation for Indirect Costs

Include a description of all indirect pools and bases to which indirect rates are applied (i.e. Overhead, Fringe Benefits, General & Administrative (G&A), etc.). If available, the offeror and proposed subcontractors shall provide the most current DCAA Provisional Billing Rate Approval Letter, DCAA Final Billing Rate Approval Letter, and/or DCAA Forward Pricing Rate Agreement or Recommendation (FPRA/FPRR). If DCAA has not reviewed the rate information for an offeror or one of its subcontractors, the offeror shall submit a detailed justification of the proposed indirect rates. If any of the rates utilized by the offeror or any subcontractors differ from the DCAA information, a justification shall be provided for the difference, including any supporting cost data (i.e, budget information). Finally, prime contractors and all subcontractors shall provide the last three (3) years of actual indirect rate information.

4.4.4 Substantiation for FCCOM

When the offeror or any subcontractor elects to claim Facilities Capital Cost of Money (FCCOM) as an allowable cost, the offeror shall submit a DD Form 1861 and show the calculations of the proposed amount.

4.4.5 Substantiation for Fee

The offeror and subcontractors shall identify the fee rate, total amounts proposed, and the various cost elements to which the fee is being applied. All fee rates, as applicable in Section B, shall be clearly distinguishable. Fee shall not be applied to ODCs.

4.4.6 Substantiation for Other Direct Costs (ODCs)

Offerors shall utilize the Not-To-Exceed (NTE) amounts provided by the Government in Section L-3, paragraph 1.0 for ODC CLINs. If it is the contractor’s accounting practice to apply (and invoice for) indirect rates (burdens) against ODCs, then the contractor shall apply these burdens within the NTE amounts provided by the Government. The NTE amounts are fully inclusive of expected industry burdens, fees, taxes, and other associated costs; the offeror shall not propose any additional fees or burdens to the NTE amounts.

4.4.7 Additional Substantiation as Necessary

Should it be necessary, offerors may submit any other information needed to adequately explain the offeror’s or subcontractor’s estimating practices.

4.4.8 Substantiation for Subcontractor Information

If subcontractors are proposed, provide the same information required for the prime contractor. The proposed subcontractors are required to submit their cost/price proposal directly to the Government via CD-ROM. The cost/price proposal shall be unprotected and unlocked, with formulae intact to show mathematical operations. For pricing purposes, subcontractors should disclose their fully burdened labor rates to the prime.

4.4.9 Substantiation for Accounting System

Because this requirement contains cost type CLINs the offeror shall also provide documentation verifying that it has an approved Cost Accounting System or state that its Cost Accounting System has not been approved. It is the prime contractor’s responsibility to ensure that each subcontractor with a proposed cost-reimbursement subcontract type has an adequate accounting system. If a subcontractor does not have an adequate accounting system, they should be priced on a Firm-Fixed-Price (FFP) or Time-and-Materials (T&M) basis. The prime contractor shall provide a list of all subcontractors by name and shall specify the type of subcontract (i.e., CPFF, FFP, T&M, etc.). For those subcontractors who will be priced on a cost-type basis, documentation verifying possession of an approved Cost Accounting System shall be provided.

4.4.10 Total Professional Employee Compensation Plan

The Offeror shall provide a Total Compensation Plan in accordance with FAR 52.222-46 for each proposed professional employee. The Plan shall include, but not limited to, the following items:

(1) The proposed direct labor rate for each professional employee proposed;

(2) The total cost of the proposed fringe benefits package for each professional employee proposed, including:

(a) list and brief…