Attachment_3_-_Section_L_Revised_4.13.18.pdf

DARPA Physical Security Support Services HR001118R0003: Section L – Revised 4/13/18

L-1 Solicitation Point of Contact

Mary Beth Colavito Contracting Officer Defense Advanced Research Projects Agency Contracts Management Office (DARPA/CMO) 675 N. Randolph St.

Arlington, VA 22203-2114 Email: HR0011-18-R-0003@darpa.mil

L-2 Overview

Solicitation HR0011-18-R-0003 is a Request for Proposal (RFP) issued by the Defense Advanced Research Projects Agency (DARPA) and set-aside for 8(a) participants (i.e. 8(a) firms, joint ventures, mentor-protégé joint ventures, or CDC-owned firms) under the North American Industry Classification System (NAICS) Code 561612 “Security Guards and Patrol Services.” DARPA Contracts Management Office (CMO) intends to award one standalone Firm Fixed Price / Cost / Labor Hour hybrid contract.

L-3 Questions Due Date

Questions/clarifications to this solicitation are due by 3:00 PM EDT on April 9, 2018. The DARPA CMO Contracting Officer (CO) is the sole point of contact for all questions under this solicitation. Offerors shall address all questions via email (Subject Line: Physical Security Questions – [Offeror Name]) to the CO via email at HR0011-18-R-0003@darpa.mil. Questions will be answered in the form of an amendment to this solicitation and posted electronically on Federal Business Opportunities (https://www.fbo.gov).

L-4 Proposals Due Date

Proposals are due by 3:00 PM EDT on April 30, 2018 via email to HR0011-18-R- 0003@darpa.mil.

L-5 Offer Acceptance Period

The offer acceptance period is a minimum of 180 calendar days from the proposal due date and should be appropriately represented in Block 12 of the signed Standard Form (SF) 33, Solicitation, Offer and Award. The offeror agrees to hold its offered prices firm for the services solicited herein and to accept any resulting contract subject to the terms and conditions stated herein. If there is a discrepancy between the offer acceptance period requirement in this solicitation and the SF 33, the date entered on the SF 33 will take precedence. Offers with an acceptance period less than 180 calendar days will not be accepted.

mailto:HR0011-18-R-0003@darpa.mil https://www.fbo.gov/

L-6 Proposal Submission Requirements

Offerors are instructed to read the entire solicitation document, including all attachments, prior to submitting questions and/or preparing your proposal. Omission of any information from the proposal submission requirements may result in rejection of the proposal.

The proposal shall be submitted in two volumes as follows:

Volume I – Administrative and Non-Price Evaluation Factors Volume II – Price/Cost and Other Information

File names shall be labeled with the volume number and offeror name. It is the sole responsibility of the offeror to ensure that the electronic files submitted are virus free and can be opened and read by the Government. Submissions shall not be locked, encrypted, or otherwise contain barriers to opening. All proposal documents shall be in Adobe (.pdf) or compatible format except portions of the price submission which shall be in MS Excel 2016 (.xlsx) or compatible format. Attachment file sizes may not be larger than 40MB.

Offerors must adhere to Volume numbers, format and/or templates, and page limitations. If page limitations are exceeded, where page limits are expressed, the excess pages will not be evaluated.

Text shall be at least single-spaced, on 8 1/2 x 11 inch paper, with a minimum one-inch margin all around. Pages shall be numbered consecutively. Any foldout pages beyond 8 ½ x 11 dimensions shall be counted as two (2) pages.

Print shall be of a minimum 10-point font size or a maximum 10 characters per inch (10-pitch, Times New Roman) spacing including graphic presentations and tables. Bolding, underlining, and italics may be used to identify topic demarcations or points of emphasis.

Table of contents and/or compliance matrices are permitted and will not count toward the page limit.

L-7 Volume I – Administrative and Non-Price Evaluation Factors (45 page limit)

L-7.1 Administrative Matters (2 page limit) shall include the below information. If an offeror fails to provide or adequately comply with any of the following requirements, they will be considered non-responsive and the rest of their proposal will not be evaluated.

i. Solicitation number;

ii. Prime contractor, subcontractors, and/or joint ventures;

iii. Date proposal is submitted;

iv. Business Size and 8(a) status (under NAICS Code 561612) confirmation;

v. Prime contractor and subcontractor Data Universal Numbering System (DUNS)

Number(s) and Commercial and Government Entity (CAGE) Code(s);

vi. Prime contractor mailing address;

vii. Other team members (if applicable) and type of business for each;

viii. Contractual and Technical points of contact information (name, title/role, phone number, email address);

ix. Statement indicating complete compliance with this solicitation, or detailed analysis of any objections, exceptions, contingencies, or additions. Any objections, exceptions, contingencies, or additions shall also cross-reference the particular paragraph(s) in this solicitation to which it applies;

x. Statement indicating whether the offeror intends to make use of any proprietary information;

xi. Description of any deviations in their proposal from the specified format of this solicitation. If the content of the offeror's proposal differs significantly from these guidelines, state the differences, and explain the reason for the differences; and

xii. Signature of person with the authority to commit the organization.

L-7.2 Factor 1: Technical Expertise (33 page limit) shall include the following:

i. Management Approach / Staffing Plan

Offerors shall provide a management approach that demonstrates their ability to manage the contract and support the dynamic nature and challenges of DARPA. Offerors shall describe their capability to provide a high quality professional staff/team in a security services environment that can respond to all Performance Work Statement (PWS) requirements and quickly shifting emphases between work areas.

Offerors shall include a staffing plan clearly stating any proposed teaming arrangements, program management structure/authority, how staffing will be completed, the number of full-time equivalents (FTEs) proposed, their labor categories, and their PWS responsibilities. If the number of FTEs proposed deviates from the notional amounts included in the Government-provided pricing spreadsheet, offerors shall explain the associated efficiencies and/or effectiveness of the deviations. (Note: Number and labor categories of Key Personnel may not deviate from PWS specifications.) Offerors shall describe the proposed labor mix planned for the hourly rate positions (not working standard 40-hour work weeks) to fulfill the PWS Section 9.7 “Post Requirements.”

ii. Technical Approach

Offerors shall provide their technical approach for the following PWS sections/subsections as exemplars for the overall contract:

a. PWS Section 3.2 “Visitor Welcome Center and DARPA Conference Center”

b. PWS Subsection 3.6.1“TSCM and TEMPEST Support”

c. PWS Subsection 3.4.2 “Security Control Center”

d. PWS Subsection 3.5.1 “Locks, Keys, and Security Containers”

e. PWS Subsection 3.5.3 “Security Systems Technician”

f. PWS Section 3.10 “Surge Support”

g. PWS Section 9.2 “Provision and Retention of Quality Personnel”

iii. Purchasing System

Offerors shall provide a summary description of their purchasing system or methods (e.g., how material requirements are determined, how sources are selected, when firm quotes are obtained, what provision is made to ensure quantity and other discounts) for potential subcontracting and Other Direct Costs (ODCs) Purchases as required in PWS Section 4.6 “Other Direct Costs”. Also, identify any deviations from the offeror’s standard procedures in preparing this proposal. Indicate whether the offeror has Government approval of its purchasing system, and if so, provide evidence of such approval in Volume II – Other Information.

iv. Key Personnel

Offerors shall provide actual resumes and/or representative resumes for all key personnel specified in the PWS. Only the Program Manager position requires an actual resume with a name specified. Key personnel resumes shall provide information to substantiate the extent to which the individual’s education, knowledge, capabilities, experiences, security clearance, and citizenship, is relevant to and meets or exceeds the functional position descriptions and other minimum personnel qualifications and eligibility requirements.

For the Program Manager position, the resume shall also include employment status (i.e.

whether the proposed individual is currently employed by the prime or subcontractor, is subject to a contingency offer of employment, or other status) and a letter of intent (as applicable).

L-7.3 Factor 2: Past Performance (10 page limit)

Offerors shall submit up to three (3) projects identified by contract number (and task/call order as applicable) that reflect recent and relevant past performance. At least one project must be for the prime contractor.

i. Recent experience is defined as services performed since January 1, 2015.

ii. To be considered relevant:

a. Performance must be similar in scope and complexity to the PWS requirements.

b. Performance must be under Government (preferably Department of Defense) contracts with funded obligations totaling at least $4 million.

iii. For each project (contract or task/call order), offerors shall summarize the following information (in order):

a. Identify the full contract number (and task/call order number if applicable);

Note: Each task/call order is considered a project (maximum of three).

b. Period of Performance to include the months, days, and years

(MM/DD/YYYY; e.g., 02/15/2015 – 02/14/20).

c. Current obligation dollar amount, total contract value, and/or potential ceiling, as applicable.

d. Identify whether the project was performed by the offeror as the prime, by the offeror as a first tier subcontractor, by a proposed subcontractor as the prime, etc.

e. Specify whether the project has a record in the Past Performance Information

Retrieval System (PPIRS), and if so, ensure the full contract number (and task/call order number if applicable) is accurate so it can be searched and found in that database.

f. Identify the Government customer office name for the project and provide the name, title/role, phone number, and email address of a Government customer point of contact (POC) that is knowledgeable of the offeror’s performance on the project.

g. Describe the nature of the project and the specified tasks performed by the offeror.

h. Describe the role, if any, that the proposed key personnel played in the performance of the contract or project. If the individual was assigned to the contract or project on a less than full-time basis, describe the degree of their involvement.

i. Describe any problems encountered on the identified contract or project and any corrective action taken, to include response to any adverse past performance information available to the Government.

j. Demonstrate how the offeror’s or proposed subcontractor(s)’ performance is similar in scope and complexity to the PWS requirements. Similarities including PWS Sections/Subsections listed in Evaluation Factor 1:

Technical Expertise will be considered more relevant.

k. Submit a summary matrix of relevant past performance for each project by contract or task/call order to indicate areas where the offeror or proposed subcontractor has relevant past performance in PWS Area 3.0 “Areas of Responsibility” (PWS Sections 3.1 – 3.17):

Past Performance PWS Relevance Summary Matrix

3.1 3.2 3.3 3.4 3.5 3.6… …3.17 HXXX-15-D-1234 / Task Order 000X √ √ √ None √ √ √ HXXX-16-C-5678 √ None None None None √ None HXXX-17-C-0001 √ √ √ √ √ None √

iv. Note: Even though the assessment of past performance information as a specific evaluation factor is separate and distinct from the determination of responsibility required by FAR Subpart 9.1, Responsible Prospective Contractors, past performance information obtained herein may be used to support the determination of responsibility for the successful offeror.

L-8 Volume II – Price and Other Information (No page limit)

L-8.1 Factor 3 – Price/Cost (No page limit)

i. Offerors shall submit a proposal for the base period, four (4) option periods, and a six-month extension period per Federal Acquisition Regulation (FAR) 52.217-8. The six-month extension shall be included in the total overall price for evaluation purposes only and be equal to half of the Option Period Four (4) price.

ii. Offerors shall include the Government-provided Not-to-Exceed (NTE) amounts for each ODC Contract Line Item Number (CLIN) and include these NTE costs in the total overall price.

iii. Offerors shall propose maximum Labor Hour (LH) rates for all personnel descriptions to be used for the Surge CLIN. Offerors shall include 5% of their proposed total Labor CLIN prices for each proposed total Surge CLIN total estimated NTE price. These LH rates will be incorporated into the contract as a separate attachment.

iv. Proposals shall be submitted using the Government-provided spreadsheet showing 1) PWS section(s) by proposed labor categories, hours, and rates; 2) CLIN totals; and 3) maximum Surge labor rates on separate tabs.

v. The price proposal shall be based on offerors’ understanding of the PWS and any other requirements in the RFP. Supporting price proposal documentation shall also be included to provide a basis for the price including enough information/explanation for the Contracting Officer to evaluate price as fair and reasonable and cost as realistic (e.g., various individual cost elements to include, at a minimum: direct labor rates, General and Administrative (G&A), overhead, subcontractor Material Handling / pass-through costs (if proposal includes subcontracts(s)), and inflation/escalation). Cost realism analysis will be limited to the Firm Fixed Price portion of the proposal, and documentation shall be provided to support that the proposed cost elements are realistic for the work to be performed; reflect a clear understanding of the requirements; and are consistent with the unique methods of performance described in the offeror’s technical proposal. If an offeror fails to provide adequate information to support a cost realism analysis, their proposal may be found unrealistic and unawardable.

vi. In accordance with FAR 15.403-1(b) and 15.403-3(a), information other than cost or pricing data may be required to support a determination of a fair and reasonable price and/or cost realism. If, after receipt of proposals, the Contracting Officer determines that there is insufficient information available to determine price reasonableness and none of the exceptions in FAR 15.403-1 apply, offerors shall be required to submit cost or pricing data. Information shall be provided in accordance with FAR 15.403 through 15.405.

vii. If applicable, the offeror shall submit its cost evaluation of subcontract costs in accordance with FAR 15.404-3(b) and (c). The offeror shall identify any subcontracts’ contract type. Subcontract proposals must contain the same level of detail as the prime contractor’s proposal and may be submitted directly to HR0011-18-R-0003@darpa.mil by the proposal due date if the proposed subcontractor does not wish to send proprietary information to the offeror. Significant subcontractor costs that are not sufficiently addressed so as the offeror can support a determination of reasonableness and realism (competition, forward pricing rates provided, etc.) may be grounds for eliminating a proposal from competition.

viii. Offerors shall provide a total compensation plan per FAR 52.222-46 setting forth salaries and fringe benefits proposed for the professional employees who will work under the contract. Supporting information shall include data such as recognized national and regional compensation surveys and studies of professional, public and private organizations, used in establishing the total compensation structure. The compensation levels proposed should reflect a clear understanding of work to be performed and should indicate the capability of the proposed compensation structure to obtain and keep suitably qualified personnel to meet mission objectives. The salary rates or ranges must take into account differences in skills, the complexity of various disciplines, and professional job difficulty.

L-8.2 Other Information (No Page Limit)

i. Offerors shall provide identification of and/or mitigation plans for any potential perceived or actual organizational conflicts of interest. Offerors are encouraged to provide and discuss any potential organizational conflicts of interest with the Contracting Officer prior to submission of a proposal.

ii. Offerors shall include a statement certifying that they possess a Top Secret facility clearance. Offerors’ CAGE codes will be used to verify the Top Secret facility clearance level with the Defense Security Service, Facility Clearance Branch. (Note: The Government will not sponsor facility clearances in anticipation of this contract award.)

Also, include a statement certifying the offeror’s ability to provide and maintain contractor personnel in accordance with PWS Section 9.3.2.

iii. Offerors shall provide a copy of their licenses and/or permits as required in PWS Section 1.3.1.

iv. Offerors shall provide evidence of Government approval of its purchasing system, if applicable.

v. Offerors shall provide all solicitation-specific provisions, representations, or certifications not previously uploaded to the System for Award Management.

vi. Offerors shall provide any information or documents required by the solicitation but not provided for in other areas including an executed copy of the solicitation cover page (Standard Form 33).

L-9 Evaluation of Proposals

All information provided in proposals is subject to evaluation. The Government will evaluate proposals in accordance with the evaluation criteria set forth in Section M of this solicitation.

This solicitation includes all evaluation criteria that the Government will use to evaluate offerors’ proposals. There are no unstated evaluation criteria. In evaluating an offeror’s proposal under any of the evaluation criteria, the Government may use the solicitation and all of its attachments, including the PWS, to evaluate the offeror’s understanding, approach, and demonstrated performance to meet the Government's requirements. In evaluating an offeror’s proposal, Government evaluators may also rely on their professional experience, including their experience with the offeror.

The Government may summarily reject any proposal not substantially in compliance with the terms and conditions of the solicitation. The Government may reject any or all proposals if such action is in the public interest and waive informalities and minor irregularities in proposals received.

All proposal information is subject to verification by the Government. Falsification of any proposal submission, documents, or statements may subject the offeror to civil or criminal prosecution under Section 1001 of Title 18 of the United States Code (making false statements).

L-10 Discussions

The Government reserves the right to award without discussions; therefore, offerors are advised that taking exception to any requirements specified in this solicitation may result in the Government finding the proposal unacceptable.

L-11 Use of Non-Government Advisors

Offerors are advised that technical and price data submitted to the Government in response to this solicitation may be released to non-Government advisors that have signed non-disclosure agreements for review and analysis. Any objection to disclosure shall be provided in writing to the Contracting Officer within ten (10) calendar days of solicitation issuance and shall include a detailed statement of the basis for the objection. The detailed statement shall identify the specific portions of the proposal the offeror objects to disclosure to non-Government advisors.

L-12 Incurring Costs

DARPA/CMO shall not be obligated to pay any cost incurred by offerors in the preparation and submission of proposals in response to this solicitation. Offerors are advised that the Contracting Officer is the only person who can legally obligate DARPA/CMO for the expenditure of public funds in connection with this procurement.