Attachment 5 - Section L Instructions to Offerors.pdf

SECTION L

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS OR RESPONDENTS

FOR

SQUADRON OPERATIONS CENTER ENTERPRISE MULTIPLE AWARD IDIQ

ACQUISITION

SOLICITATION NO: FA489021R0007

16 June 2021

1.0 GENERAL INSTRUCTIONS

This is a best value source selection conducted in accordance with Federal Acquisition Regulation

(FAR) 15.3 and DoD Source Selection Procedures as supplemented.

1.1 This requirement is solicited as a 100% set-aside for Small Business under NAICS 541513 Computer

Facilities Management. Additionally, there will be a partial set-aside for 8(a) IDIQ awardees in accordance with FAR 16.505(b)(2)(F) and FAR 19.805. Task Orders for the following requirements will remain in the 8(a) program and will be exclusively set-aside and competed amongst eligible 8(a)

IDIQ holders in accordance with FAR 19.805-2(b):

1.1.1 Air National Guard (ANG) Contractor Field Service Representative (CFSR) Support. This includes field maintenance services (SME) support required to install, configure, support, maintain, administer and train ANG Remotely Piloted Aircraft (RPA)- Squadron Operation Center

(SOC) hardware and software systems supporting RPA operations at twelve ANG locations and the integration center at Robins AFB, GA. The scope of work includes new sites up to and including a total of 14 sites.

1.1.2 System Program Office (SPO) RPA SOC baselined systems Install/Warehouse Support. This includes the procurement of hardware and software, warehousing of Government procured material, related engineering services, and installation of hardware, software, and equipment at multiple CONUS locations in support of SPO RPA SOC baselined systems.

1.2 Proposal Compliance. The Offeror's proposal shall include all data and information requested by this

Instructions, Conditions, and Notices to Offerors or Respondents (ITO) and shall be submitted in accordance with these instructions. The offer shall be compliant with the requirements as stated in the

Request for Proposal (RFP) Letter, the Performance Work Statement (PWS), Model Contract, and all other parts of this solicitation. If a proposal fails to conform to the instructions provided in this ITO, it may be deemed unacceptable.

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

Offeror’s proposal fails to meet all terms and conditions, it will be determined unacceptable.

1.3 Proposal Clarity. The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. Offerors shall assume that the

Government has no prior knowledge of their experience and will base its evaluation on the information presented in the Offeror's proposal.

Offerors shall not submit elaborate brochures or documentation, binding, detailed artwork, or other embellishments.

1.4 RFP Discrepancies. If an Offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the Offeror shall notify the Contracting Officer (CO) in writing with supporting rationale as well as the remedies the Offeror is asking the CO to consider as related to the omission or error. Questions pertaining to the proposal shall be submitted no later than the date and time identified in Paragraph 5 of the RFP Letter. The Offeror is reminded that the Government intends to award this effort without discussion.

1.5 Point of Contact. The CO is the sole point of contact for this acquisition. Offerors shall address any questions or concerns to the CO. All email communication shall be to the email addresses identified in Section L, Paragraph 1.11.

1.6 Communications. Exchanges of source selection information between Government and Offerors will be controlled by the CO. Source selection information will be transmitted to Offerors electronically

(i.e. via email or DoD SAFE). If transmitted via email, the transmission shall be sent and received encrypted and must include “Source Selection Information – See FAR 2.101 & 3.104” in the Subject line.

1.7 Electronic Reference Documents. All referenced documents for this solicitation can be found on the beta.Sam website at https://beta.sam.gov//. Potential Offerors are encouraged to subscribe for real-time email notifications when information has been posted to the website for this solicitation.

Offerors may contact the CO if they are unable to locate any of the referenced material.

Link: beta.SAM.gov - search for FA489021R0007 postings.

1.8 Proposal Records. In accordance with FAR Subpart 4.8 (Government Contract Files), the

Government will retain one copy of all proposals.

1.9 Debriefings. The CO will promptly notify Offerors of any decision to exclude them from the source selection; whereupon, the Offeror may request and receive a debriefing in accordance with FAR

15.505. Offerors desiring a debriefing shall make their request in accordance with the requirements of

FAR 15.505 or 15.506, as applicable. Offerors are entitled to no more than one debriefing.

1.10 Question Submission. All question must be submitted via email to cortney.young@us.af.mil and tony.burns.6@us.af.mil using the Attachment 15 Question-Comments Matrix no later than 3:00 pm EST on 13 August 2021. Questions will not be answered over the phone or submitted by any other means. Questions received after this date will be addressed at the sole discretion of the contracting officer. All questions impacting the solicitation will be answered in an amendment posted on or around 20 August 2021.

1.11 Proposal Submission. Proposals shall be submitted via DoD SAFE, in accordance with the following procedures. The offeror must send an email to the Contract Manager (CM), Tony Burns, anthony.burns.6@us.af.mil, and the Contracting Officer (CO), Cortney Young, cortney.young@us.af.mil requesting a DoD SAFE Drop Off Link no earlier than 14 days prior to the proposal due date, and no later than 1 day prior to the proposal due date. The offeror will receive an email from DoD SAFE with a link to upload the offeror’s proposal documents. Once the link has been accessed, the offeror shall enter the following email addresses into the “To:” section:

cortney.young@us.af.mil and anthony.burns.6@us.af.mil. In the “Short note to the Recipients section” the offeror shall use the following format: Offeror Name FA489021R0007 SOC-E Proposal.

Proposals must be received no later than 3:00 pm EST on 24 September 2021. Offerors are strongly encouraged to plan accordingly, submit proposals well in advance of the designated submission deadline, and ensure affirmative receipt of proposals. In the absence of confirmation from the CM or

Contracting Officer or other affirmative evidence of receipt, Offerors shall assume the proposal has not been received. Proposals not received by the designated submission deadline will be regarded as

“late” and will not be considered.

1.12 Page Format.

1.12.1 Page Limitations. Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal. Each page shall be counted except the following: cover pages, tables of contents, and glossaries. If evaluation notices (EN) are determined necessary, page limits will be placed on EN responses.

file://///periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/Far02.doc%23T2101 file://///periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR03.DOC%23b3104 mailto:cortney.young@us.af.mil mailto:tony.burns.6@us.af.mil mailto:anthony.burns.6@us.af.mil mailto:cortney.young@us.af.mil mailto:cortney.young@us.af.mil mailto:anthony.burns.6@us.af.mil

1.12.2 General Page Instructions. A page is defined as each face of a sheet of paper containing information. Page size shall be 8.5 x 11 inches unless stated otherwise within this document.

Pages shall be single spaced, and the text size shall be no less than 11 point Times New Roman

Font unless stated otherwise within this document. All proposal text shall be written in English.

Offerors shall use at least 1 inch margins on the top and bottom and ¾-inch side margins unless stated otherwise within this document. Pages shall be numbered sequentially by volume. These page size and format restrictions shall apply to responses to ENs if determined necessary.

1.12.3 Table and Chart Instructions. Legible tables and charts may be used. These displays shall be uncomplicated, legible, and shall not exceed 11 x 17 inches in size. 11 x 17 may only be used for large tables and charts; they shall not be used for pages of text. For tables and charts, the text shall be no less than 10 point Times New Roman Font, and margins shall be no less than ½ inch on all sides unless stated otherwise within this document.

1.12.4 Submission Format. The Offeror shall submit each volume in electronic format. The proposal shall be submitted in a format readable by Microsoft (MS) Office Word 2016, MS Office Excel

2016 or Adobe PDF. Offerors shall use separate folders for each proposal volume. Offerors shall also use separate electronic files for each proposal section listed in Table 1 to permit rapid location of all portions of the proposal. Exhibits, annexes, and attachments which are provided in support of a section shall be included in the electronic file for that section. Offerors shall provide each work sample as a single separate electronic file. If files are compressed, the necessary decompression program shall be included.

1.12.5 Proposal Markings. Proposals shall be marked in accordance with FAR 52.215-1(e), Restriction on Disclosure and Use of Data, and FAR 3.104-4, Disclosure, Protection, and Marking of

Contractor Bid or Proposal Information and Source Selection Information. Offerors shall not include proprietary markings on attachments and documents that will become a part of the contract (i.e. Volume IV documents).

1.12.6 Cross-Referencing. To the greatest extent possible, each volume shall be written on a stand-alone basis so that its contents may be evaluated with no cross referencing to other volumes of the proposal. Information required for proposal evaluation which is not found in its designated volume and/or section will be assumed to have been omitted from the proposal.

1.12.7 Table of Contents. Each volume shall contain a more detailed table of contents to delineate the subparagraphs within that volume. Tables of content do not count against the page limitations for their respective volumes.

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

1.12.9 Teaming Arrangements. Offerors submitting a proposal as the prime Offeror in response to this solicitation are not permitted to submit a separate proposal under which they would be a

Subcontractor, or team member to another prime. Subcontractors are permitted to support multiple primes.

2.0 PROPOSAL INSTRUCTIONS

2.1 Proposal Organization. The Offeror shall prepare the proposal as set forth in the Table 1, Proposal Organization. The volume folders and section files shall be as defined in this table, all of which shall be within the required page limits specified in the table.

Table 1 –Proposal Organization

VOL ITO SECTION VOLUME & SECTION TITLE PAGE LIMIT

I 2.2 Executive Summary

2.2.2 Offeror Company Information 2 Pages

2.2.3 Other Information

2.2.3.1 Financial/Other Resources No Page Limit

2.2.3.2 Accounting Systems No Page Limit

2.2.4 Organizational Conflict of Interest No Page Limit

II 2.3 Contract Documentation No Page Limit

III 2.4 Past Experience

2.4.1 Work Samples No Page Limit

2.4.2 Self-Scoring Matrix 1 Page

2.4.3 Cross Reference Matrix 20 Pages

2.4.4 Team Structure 2 Pages

2.4.4 Teaming Agreements 30 Pages

VI 2.5 Past Performance

2.5.2 Past Performance Submissions No Page Limit

2.5.3 Subcontractor/Teaming Member Consent

Letter

30 Pages

2.5.4 Organization Structure Change History 5 Pages

2.5.5 Specific Content 5 Pages

NOTE: In accordance with 10 U.S.C. 2305(a)(3)(C)(i), Cost/Price will be evaluated for each individual task order. As a result, Cost/Price information will not be requested within this proposal.

2.2 VOLUME I - EXECUTIVE SUMMARY

2.2.1 Volume 1 Organization. This volume shall be organized according to the Table 1 above.

2.2.2 Offeror Company Information. The Offeror shall complete Attachment 7 - Offeror Company

Information Form. The Offeror shall provide all information on the form. The proposal validity statement shall be valid through January 31, 2022. The Offeror shall be registered in the System for Award Management (SAM.gov) for the duration of the acquisition. If the Offeror’s SAM.gov registration expires prior to the proposal validity date, the Offeror shall assert its intent to renew the registration. The offeror shall identify their approved Facility Clearance (FCL), which must be at least Top Secret to be eligible for award.

2.2.3 Other Information. To assist the Contracting Officer in making the responsibility determination prior to contract award (in accordance with FAR 9.1, Responsible Prospective Contractors, as supplemented by the DFARS 209.1), the following information is requested.

2.2.3.1 Financial/Other Resources. In accordance with FAR 9.104-1(a), the Offeror shall provide a written statement explaining the Offeror’s ability to obtain required resources to perform the contract requirements. The Offeror shall also provide evidence to support the explanation.

Evidence may include, official letter(s) from financial institutions demonstrating that the

Offeror has the financial resources required to cover all financial commitment. In accordance with FAR 9.104-1(e), the Offeror shall provide an explanation of the Offeror’s organizational controls and measures. At a minimum, the Offeror shall address their accounting controls, operational controls, quality assurance measures, and safety program. The Offeror shall also provide evidence to support the explanation. Evidence may include a list of organizational policies or Standard Operating Procedures (SOPs) which demonstrates the organizational controls and measures of the Offeror. If a list is provided, the Offeror shall include the title of each policy or SOP, the date of each document, and a brief description of each document. The

Offeror shall also define which element of FAR 9.104-1(e) the policy or SOP applies to.

2.2.3.2 Accounting System. IAW FAR 16.301, no cost reimbursement contract may be awarded unless the limitations in FAR 16.301-3 are met. One of the limitations cited under FAR 16.301-3 requires that “the Contractor’s accounting system is adequate for determining costs applicable to the contract or order.” The prime shall provide a current (within three (3) years prior to date of proposal submittal) letter or report from Defense Contract Audit Agency (DCAA)/ Defense

Contract Management Agency (DCMA) that the Offeror’s accounting system has been approved, or is adequate for cost-reimbursement contracts. If the prime does not have a letter or report from DCAA/DCMA from within 3 years, the Offeror shall provide the latest letter or report received, and shall provide a statement that the accounting system has not changed since being reviewed. If the accounting system has changed, the Offeror shall provide a

DCAA/DCMA certification indicating that the changes have not impacted the approval or adequacy of the accounting system. If the prime does not currently have an accounting system determined as adequate for determining costs applicable to the contract or order, then the prime shall state that it will work with DCAA/DCMA to obtain the appropriate accounting system approval.

2.2.4 Organizational Conflict of Interest. Offerors shall submit an assessment of potential or actual

Organizational Conflict of Interest (OCI) issues, if any, as related to this contract vehicle and future work. Initial notification shall be made to the Contracting Officer and Contract Specialist as soon as they become known. OCI issues include, but may not be limited to, the inability to render impartial assistance or advice to the Government, the inability to objectively perform contract work, or the unfair competitive advantage created by current or previous contractual efforts with the Government. If an actual or potential OCI exists, the Offeror shall submit a mitigation plan with the proposal. The Contracting Officer will review the submitted mitigation plan and make a determination as to whether the plan adequately resolves the issues and provides adequate protection to both the Offeror and the Government. Submission of mitigation plans are only required if the Offeror is aware of potential or actual OCI issues related to this procurement.

If the Offeror believes no potential or actual OCI issues exist, this shall be so stated.

2.4 VOLUME III –PAST EXPERIENCE

2.4.1 Work Samples. The Offeror shall submit a maximum of ten (10) work samples which demonstrate past experience in the required SOC-E program areas, and which comply with the work sample qualifications established in 2.4.1.2 below. When referring to work samples, the terms “contract” and “task order” shall not be used interchangeably. The term contract shall refer to a stand-alone “contract” action and the term “task order” shall refer to an order issued under an

Indefinite Delivery Indefinite Quantity (IDIQ) contract utilizing FAR 16.505 ordering procedures.

IDIQ contracts are not an acceptable proof of past experience, and shall not be provided as a work sample. However, individual task orders, performed under an IDIQ contract, can be used as a work sample. Multiple task orders issued against a multiple-award IDIQ cannot be combined and counted as one contract reference. Offerors using single-award IDIQ contract numbers as a contract reference shall include BOTH the IDIQ contract number AND the individual task order number(s) in order to verify and validate that the IDIQ being referenced is in fact a single-award

IDIQ contract. A maximum of three (3) task orders issued against a single-award IDIQ can be combined and counted as one (1) contract reference to address the criteria. A method of quality assessment shall be obtainable to the Government (i.e. CPAR/PPQ) for each contract reference.

The work samples shall consist of only official contract documentation which may include

Performance Work Statements, Statements of Work, Contract Data Requirement Lists (CDRLs), etc. When contracts are used for work samples, the Offeror shall, also include the signed cover page associated with the contract. Work samples shall include sufficient information to substantiate each claim in the elements below. If a work sample substantiates multiple SOC-E program areas, each program area must be identified within the work sample. The Offeror shall not create any new documentation, such as project narratives, or project descriptions. Offerors shall only provide official contract documentation.

Offerors shall give each work samples an identifier (i.e. WS1-WS10). All pages within the work samples shall be numbered. Work samples shall be provided in their original format. Font, text size, and margin requirements established in Sections 1.9.2.1 and 1.9.2.2 do not apply to work sample submissions. Work samples shall be in English.

2.4.1.1 Work Sample Cover Sheet. A Work Sample Cover Sheet (Attachment 8), shall be completed for each work sample submitted. Offerors shall follow the instructions provided within Attachment 8.

Each work sample shall provide at least two (2) Government Points of Contact (POC). The

Government may contact the Government POC’s provided. The Government reserves the right to contact additional Government POCs if necessary. For subcontractor work samples, the Offeror shall provide at least three (3) POCs for the prime company. The Government may contact the prime company POCs provided. The Government reserves the right to contact additional prime company POCs if necessary.

2.4.1.2 Work Sample Qualifications. Work samples shall meet these minimum qualifications.

(1) Shall be a United States Government Department or Agency contract.

(2) Shall fall into one of the following categories as specified within each element:

a. Category 1: Prime Offeror work samples. In order to be used, the Offeror shall have acted as the Prime Contractor. If a company is proposing as a joint venture, work of either prime company may be utilized. Primes may also include subsidiaries, or legal entities which fall under the parent corporation. In order to use subsidiaries or legal entities as a prime work sample, (1) the acquisition of the subsidiary or legal entities shall have been finalized as of the date of the RFP Letter, and (2) objective evidence shall be included in the work sample to demonstrate that they are now a legal entity of the corporation. If the criteria above are met, subsidiary or legal entity work samples will be considered prime work samples even if the work occurred prior to the company being acquired.

b. Category 2: Subcontractor work samples may be used. In order to meet this qualification, the Subcontract shall: (1) be identified as a Subcontractor who will be performing work under the SOC program area identified within the Team Structure Form as required in Section 2.4.4; (2) have previously acted as the Prime Contractor on federal contract(s); (3) provide a signed Teaming Agreement as required in Section 2.4.4, stating that the Subcontractor will perform at least 25% of the work in the applicable SOC-E program area.

(3) At least six months of active performance shall have been within the last five years, as of the date of this RFP.

2.4.2 Self-Scoring Matrix. The Offeror shall complete the Self- Scoring Matrix (Attachment 9). Self-scores shall be verifiable using the work samples provided in response to Section 2.4.1. Note that some elements, within Attachment 9, contain category restrictions.

The Offeror shall fill in the Column D “Offeror Proposed Self-Score Points” column on the Self-

Scoring Matrix. The “Offeror Proposed Self-Score Points” shall not exceed the “Maximum Self

Score Points” identified for each element in Column C. The Offeror shall not change, adjust, or manipulate any other cells within the matrix. The Prime Offeror shall accurately rate itself using the scoring instructions for each element, which is described in Sections 2.4.2.1 – 2.4.2.2.

The burden of proof to substantiate the Offeror’s self-score rests with the Offeror. The proposal shall include evidence supporting each proposed self-score. Please note, the Government is not bound by an Offeror’s relevance assessment or proposed self-score.

2.4.2.1 Critical SOC-E task areas, within criteria outlined in 2.4.1.2.

DEFINITION: Of the work samples submitted, the Offeror shall rate itself based on the total number of

Critical SOC-E task areas supported. Critical SOC-E task areas are a subset of task requirements identified in the PWS which the Government views as critical for successful contract performance. The following tasks are considered Critical SOC-E tasks and can be found in Attachment 10 - Cross Reference

Matrix:

From the Program Management task area (PWS para 2.): (1) 2.1.1 Project Management and (2) 2.2.2

Program Management Office.

From the Operations and Maintenance task area (PWS para 3.): (3) 3.1.4 SATCOM Relay Site Operations and Maintenance; (4) 3.2.1 Operations; (5) 3.2.2 System Administration; (6) 3.2.5 System Protection; (7)

3.2.10 Network Administration; (8) 3.2.11 Video Streaming and Distribution; (9) 3.2.17 Risk

Management Framework; and (10) 3.2.21 Configuration Management.

From the Install/Warehousing task area (PWS para 4): (11) 4.1 Warehousing; (12) 4.7.1 Distribution

Services; (13) 4.8 Inventory Management and Control; (14) 4.10 Engineering Services; and (15) 4.11

Installations.

From the SOC-Enterprise Services/Helpdesk task area (PWS para 5.): (16) 5.1.1 Aircraft Control

Network; (17) 5.1.1.4 Circuit-to-Packet (CTP); (18) 5.1.1.7 Virtual Machine Server and Backup Services;

(19) 5.1.2 Sensor Product Dissemination Network (SPDN); (20) 5.1.6 SOC-E Cyber Security; (21) 5.1.8

Help Desk; and (22) 5.1.11 Engineering Support

CATEGORY RESTRICTIONS: The Offeror shall only receive points for Category 1 work samples.

SCORING: To be considered Qualifying, Offerors must demonstrate experience in at least 90% of the

Critical SOC-E task areas, which equates to at least twenty (20) of the twenty-two (22) Critical SOC-E task areas. A maximum of one point may be received for each Critical SOC-E task area listed... Offerors shall not receive extra points for providing multiple work samples which demonstrate past experience within the Critical SOC-E task areas.

2.4.2.2 Standard SOC-E task areas supported, within criteria outlined in 2.4.1.2.

DEFINITION: Of the work samples submitted, the Offeror shall rate itself based on the total number of

Standard SOC-E task areas supported. These Standard SOC-E task areas are a subset of task requirements identified in the PWS which the government views as required for successful contract performance. The following tasks are considered Standard SOC-E tasks and can be found in Attachment 10 - Cross

Reference Matrix:

From the Program Management task area (PWS para 2.): (1) 2.1.2 Meetings; (2) 2.1.3 Technical Expert

Status Accreditation; (3) 2.1.5 Advisory; (4) 2.2.1 Personnel; (5) 2.2.3 Site Management; (6) 2.3.1

Quality Management System; (7) 2.5 AF Records Management; and (8) 2.8 Data Management System

(DMS).

From the Operations and Maintenance task area (PWS para 3.): (9) 3.1 SATCOM Relay Sites; (10) 3.1.1

ArcLight; (11) 3.1.2 SATCOM Remote Video Terminal; (12) 3.2.3 Intelligence System Support/Multi-Int

Analysis Archive System (MAAS); (13) 3.2.4 Troubleshooting; (14) 3.2.4 Troubleshooting; (15) 3.2.9

Long-Haul Communications; (16) 3.2.12 Interfaces; (17) 3.2.13 Intercom Systems; (18) 3.2.15

Maintenance Support; (19) 3.2.18 Training; (20) 3.2.20 Users’ Guides; (21) 3.2.23Technical Assistance;

(22) 3.2.25 Circuit Support; (23) 3.4 Cable System; and (24) Engineering Support.

From the Install/Warehousing task area (PWS para 4): (25) 4.7.3 Project Management; (26) 4.7.5

Receiving/Inspection; and (27) 4.9 Kitting.

From the SOC-Enterprise Services/Helpdesk task area (PWS para 5.): (28) 5.1.1.5 Firewalls; (29) 5.1.1.6

High Assurance Internet Protocol Encryptor (HAIPE); (30) 5.1.3 SATCOM Relay Monitoring; (31) 5.1.5

RPA-Low (SIPRNet); (32) 5.1.7 Configuration Management; (33) 5.1.9 Master Station Log (MSL); (34)

5.1.10 Circuit Support; and (35) 5.1.12 Testing and Evaluation Support.

CATEGORY RESTRICTIONS: Category 1 and Category 2 contracts are authorized.

SCORING: To be considered Qualifying, Offerors must demonstrate experience in at least 75% of the

Standard SOC-E task areas which equates to at least twenty-seven (27) of the thirty-five (35) Standard

SOC-E task areas. A maximum of one point may be received for each Standard SOC-E task area listed.

Offerors shall not receive extra points for providing multiple work samples which demonstrate past experience within the Standard SOC-E task areas.

2.4.3 Cross Reference Matrix. The Offeror shall provide a Cross Reference Matrix which clearly identifies the exact location of the substantiating data within the work samples. The Cross

Reference Matrix shall be completed using Attachment 10 – Cross Reference Matrix. The Offeror shall identify the type of document provided as a work sample in Column E. The Government has included a list of sample documents within Column E, Document Type; the Offeror is not limited to this list of documents. The Offeror shall include a work sample identifier (i.e., WS1-WS10), SOC-E program area, document title, document date, page(s), paragraph(s), table number(s) (if applicable), and block(s) (if applicable) within Column F, Reference. A reference shall be provided for each

SOC-E program area in order to receive a point. Offerors shall not utilize “keyword” searches for references. Offerors shall submit references that illustrate experience in SOC-E program areas.

Each SOC-E program area shall receive a separate reference. If the Offeror uses a subsidiary or legal entity as a prime work sample the Offeror shall be sure to include a reference to the objective evidence which demonstrates that they are a legal entity of the parent corporation. Offerors are encouraged to verify the accuracy of each reference.

The Offeror shall assume the Government has no prior knowledge of its capabilities, and experience.

2.4.4 Team Structure. The Offeror shall identify the team structure it will use to meet Government requirements. The Offeror shall identify the team structure within Attachment 11 – Team Structure.

The Offeror shall:

(1) Identify the team member’s name, address, CAGE code, and DUNS number.

(2) Identify the relationship between the prime, each team member.

(3) Identify SOC-E program areas in which the prime intends on utilizing team member(s) for performance.

(4) Provide verification of prime status for proposed team members. Offeror’s shall provide contract reference(s) that illustrate the team member acting as a prime.

The Offeror shall provide signed teaming agreements between the Prime Offeror and each team member. The teaming agreement shall identify the percentage of work to be performed in each

SOC-E program area, and shall identify the percentage of work to be performed.

2.4.5 Burden of Proof The burden of proof for substantiating points in the self-score system rests with the Offeror. The proposal shall contain sufficient data to substantiate the points claimed by the

Offeror. All proposal information is subject to verification by the Government. Falsification of any proposal submission, documents, or statements may be subject the Offeror to disqualification from this source selection. Please note, the Government is not bound by an Offeror’s relevance assessment or proposed self-score.

2.5 VOLUME VI - PAST PERFORMANCE

2.5.1 Volume III Organization. This volume shall be organized according to the Table 1 above.

2.5.2 Past Performance Submissions. A Past Performance Submission consists of a Past Performance

Information Sheet, Contractor Performance Assessment Reports and Past Performance Questionnaire, when applicable. Past Performance Submissions may reflect work accomplished by the prime, subsidiary, legal entity, subcontractor or team member. The Offeror shall submit a maximum of five

(5) contract references for the Past Performance Submission. Offerors shall only utilize contract references from submitted work sample pool (i.e. WS1 – WS10). Offerors shall not submit new contract references for the Past Performance Submission.

2.5.2.1 Past Performance Information (PPI) Sheet. Offerors shall submit a PPI sheet (Attachment 12) for each work sample.

2.5.2.2 Past Performance Questionnaire (PPQ). Offerors shall send a PPQ with a PPQ Cover Letter to the Points of Contact (POCs) identified on each of the PPI Sheets. POCs may be the same or different than the POCs identified in the Work Sample Cover Sheet (Attachment 8). Offerors shall use the Government provided PPQ (Attachment 13), which includes the Government provided PPQ

Cover Letter. The POC on the PPI and the PPQ shall be the same person. Offerors shall fill in

Section I of the PPQ prior to sending the PPQ to the POC. Government/Client completed PPQs must not be submitted to the Offeror. POCs submit completed PPQs directly to the CO per instructions in the PPQ Cover Letter. When completed CPARS or similar reports are submitted to reflect past performance data on a work sample, the PPQ is not required. PPQs shall only be submitted in instances when CPARS information is unavailable (i.e. subcontracted work or initial CPAR report is not finalized)

2.5.2.3 Contractor Performance Assessment Reports (CPARS). The Offeror shall provide all completed CPARS reports related to the work sample. Offerors shall clearly mark each evaluation report with the associated work sample identifier (i.e. WS1-WS10).

2.5.3 Subcontractor/Teaming Member Consent Letter. Past Performance Submissions cannot be disclosed to non-Government parties without the information owner’s consent. If one of the Past

Performance Submissions is provided by a team member, the Government will need the team member’s consent before disclosing PPI to the Prime during exchanges. The Subcontractor/Teaming

Partner Consent Letter shall be signed by an individual who has the authority to sign for and legally bind the company. Completed Subcontractor/Teaming Partner Consent Letter (Sample

Subcontractor/Teaming Partner Consent Letter at (Attachment 14) shall be submitted as part of the

Past Performance Volume.

2.5.4 Organizational Structure Change History. Many companies have acquired, been acquired by, or otherwise merged with other companies, and/or reorganized their divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the time of performance of relevant past efforts or between conclusion of recent past efforts and this source selection. As a result, it is sometimes difficult to determine what Past Performance is relevant to this acquisition. To facilitate this relevancy determination, include in this proposal volume a "roadmap" describing all such changes in the organization of your company, if necessary. A pamphlet or other commercial document describing such reorganizations may be used to describe the changes. As part of this explanation, describe how these changes impact the relevance of any efforts you identify for past performance evaluation/performance confidence assessment. Since the Government intends to consider Past Performance information provided by other sources as well as that provided by the

Offeror(s), your "roadmap" should be both specifically applicable to the efforts you identify and general enough to apply to efforts on which the Government receives information from other sources.

2.5.5 Specific Content. Additional information may be included to discuss the Offeror’s efforts to resolve contract performance problems encountered on prior contracts as well as past efforts to identify and manage program risk. Merely having problems does not automatically equate to a “Limited

Confidence” or “No Confidence” rating, since the problems encountered may have been on a more complex program, or an Offeror may have subsequently demonstrated the ability to overcome the problems encountered. The Offeror is required to clearly demonstrate management actions employed in overcoming problems and the effects of those actions in terms of improvements achieved or problems rectified. This may allow the Offeror to be considered a higher confidence candidate.