HR001123R0001 Section L - Amend 01 tracked changes.docx

HR001123R0001 Amendment 0001 Tracked Changes Section L

Section L: Proposal Preparation and Submission

L.1 Solicitation Point of Contact Mary Beth Colavito Contracting Officer Defense Advanced Research Projects Agency Contracts Management Office (DARPA/CMO) 675 N. Randolph Street Arlington, VA 22203-2114 Email: TASSIDIQREQUIREMENT@darpa.mil

L.2 Overview Solicitation HR001123R0001 is a Request for Proposal (RFP) issued by the Defense Advanced Research Projects Agency (DARPA) under North American Industry Classification System (NAICS) Code 541990 “All Other Professional, Scientific, and Technical Services.” DARPA Contracts Management Office (CMO) intends to award approximately seven (7) multiple-award Indefinite Delivery / Indefinite Quantity (ID/IQ) contracts under a single full and open competition solicitation.

The DARPA-wide Technical and Analytical Support Services (TASS) contract will be a centrally managed multiple-award Advisory and Assistance Services (A&AS) ID/IQ contract, with a combination of Fixed Price (FP), Cost-Reimbursement (CR), and Labor Hour (LH) Task Orders (TOs).

L.3 Proposal Due Date Proposals are due by 10:00 am Eastern on Monday, March 13, 2023, via email (Subject Line: TASS ID/IQ Proposal – [Offeror Name]) to DARPA CMO Contracting Officer at TASSIDIQRequirement@darpa.mil.

L.4 Questions Due Date Questions/clarifications to this solicitation are due by 10:00 am Eastern on Wednesday, February 22, 2023. The DARPA CMO Contracting Officer is the sole point of contact for all questions under this solicitation. Offerors shall submit all questions using the Questions Matrix in Attachment 7 via email (Subject Line: TASS ID/IQ Questions – [Offeror Name]) to the Contracting Officer at TASSIDIQRequirement@darpa.mil. Questions will be answered in the form of an amendment to this solicitation and posted electronically on SAM.gov.

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 of less than 180 calendar days will not be accepted.

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 during the Contracting Officer's compliance review may result in the rejection of the proposal.

Offerors shall submit their proposals via email to TASSIDIQRequirement@darpa.mil.

The proposal shall be formatted into a transmittal letter and six (6) separate electronic folders files by volume number and title as follows:

The file shall be labeled with the solicitation number and company 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 (except the file containing the information requested in Section L.8.2(a), which may be encrypted if necessary), 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 10MB.

Offerors shall adhere to Volume numbers, format and/or templates, and page limitations. Offerors shall include their company name or company name abbreviation and Volume number in the filename (e.g., CMPNYA - Vol. II). If page limitations are exceeded, where page limits are expressed, the excess pages will not be evaluated.

Classified submissions will not be accepted.

L.7 Volume I - Proposal Transmittal Letter (3 page limit)

Volume I shall contain a letter formally transmitting the proposal to include the following:

a. Statement of Compliance. Each Offeror shall include a 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.

b. Proprietary Information. Each Offeror shall include a statement indicating whether the Offeror intends to make use of any proprietary information.

c. Format and Content. Each Offeror shall describe any deviations in its 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.

d. Points of Contact. Each Offeror shall include primary and alternative points of contact to include title, mailing address, email, and phone number.

e. Business size status (under NAICS Code 541990).

f. Unique Entity Identifier (UEI) and Commercial and Government Entity (CAGE) Code(s).

L.8 Volume II - Administrative (No page limit)

Volume II shall include all solicitation documents as outlined below and in this order. If an Offeror fails to provide or adequately comply with any of the following requirements, the proposal may be rejected without further evaluation.

L.8.1 Joint Venture/Teaming Arrangements The Offeror shall provide, if applicable, a summary describing the Joint Venture/Teaming Arrangement established for this solicitation and a document establishing the legally binding nature among the joint venture/teaming parties. The Government encourages teaming to the maximum extent practicable required to meet solicitation requirements. The Offeror shall indicate on the summary if any teaming arrangements are exclusive. In order to promote maximum competition, the Government discourages exclusive teaming arrangements.

L.8.2 Security

a. The Offeror shall provide, as part of this proposal Volume, a copy of its documentation from the Defense Counterintelligence and Security Agency (DCSA) letter from the Defense Security Service, Facility Clearance Branch , or equivalent accreditation agency, that grants its facility and security clearance level at the Top Secret level proving it was granted by time of proposal submission.*

b. Include a statement certifying the Offeror's ability to provide and maintain contractor personnel up to and including a Top Secret/Sensitive Compartmented Information (SCI) minimum with Special Program Access eligibility.

* Note: The Top Secret Facility clearance must be current at time of proposal submission, and the Government will not sponsor facility clearances in anticipation of this award.

L.8.3 Organizational Conflict of Interest

The Offeror shall disclose complete information of any work performed by its company that is in any way associated with the contemplated acquisition or which could result in a potential organizational conflict of interest. Under DARPA organizational conflict of interest policy, without prior approval or a waiver from the DARPA Deputy Director, in accordance with Federal Acquisition Regulation (FAR) 9.503, a contractor cannot simultaneously be a scientific, engineering, technical assistance (SETA) support contractor and also be a research and development performer at DARPA. Therefore, all Offerors must affirm whether it (its organizations and individual team members) are acting as a research and development performer to DARPA through an active contract or subcontract. All affirmations must identify the prime contract number(s). Affirmations shall be furnished at the time of proposal submission by the Offeror on behalf of themselves and all proposed subcontractors and consultants. All facts relevant to the existence or potential existence of organizational conflicts of interest (FAR 9.5, Organizational and Consultant Conflicts of Interest) shall be disclosed. The disclosure shall include a description of the action the Offeror has taken or proposes to take to avoid, neutralize, or mitigate such a conflict. If, in the sole opinion of the Government, after full consideration of the circumstances, a proposal fails to fully disclose potential conflicts of interest and/or any identified conflict situation cannot be effectively mitigated, the proposal will be rejected without technical evaluation and withdrawn from further consideration for award.

If a prospective Offeror believes that any conflict of interest exists or may exist (whether organizational or otherwise) or has questions on what constitutes a conflict of interest, the Offeror should promptly raise the issue with DARPA by sending his/her contact information and a summary of the potential conflict to the Contracting Officer before time and effort are expended in preparing a proposal and mitigation plan.

The Offeror shall acknowledge the requirement for a Non-Disclosure Agreement in the format prescribed by Attachment 2 by including a copy within this Volume submission signed byfor the authorized representative listed in in Section L.8.4. This Non-Disclosure Agreement will be included in successful ID/IQ awards and will be mandatory for all personnel working under task order awards.

L.8.4 Standard Form 33 The Offeror shall complete blocks 12 through 19 of the Standard Form (SF) 33. If any amendments to this solicitation are issued, the Offeror shall acknowledge each amendment number and date in block 14 of the SF 33. The Offeror's legal name and address in block 15A must match the information for the Offeror in System for Award Management (SAM) (http://www.sam.gov), including the corresponding Commercial and Government Agency (CAGE) Code number and Unique Entity Identifier (UEI). The name, title, signature, and date identified in blocks 16, 17, and 18, must be an authorized representative with the authority to commit the Offeror to contractual obligations.

L.8.5 Accounting System The Offeror shall provide proof of a Defense Contract Audit Agency (DCAA)-approved accounting system or must complete the Accounting System Checklist in Attachment 6 and include it within this Volume submission. Offerors should note that if it is awarded an ID/IQ contract without already having a DCAA-approved accounting system, it will not be eligible to submit proposals for task order requirements with Cost-Reimbursement Contract Line Item Numbers (CLINs) until a DCAA Cost Accounting System Audit is performed and approved after ID/IQ award.

L.8.6 Subcontracting Plan Small businesses, as defined in FAR 52.219-1 as a Small Business Concern, are not required to submit a Subcontracting Plan. For other than small businesses, the Offeror shall provide a Subcontracting Plan. An individual Subcontracting Plan is preferred, but an Offeror may submit any type of Subcontracting Plan as long as it conforms with FAR 19.704, Subcontracting Plan Requirements, and FAR 52.219-9, Small Business Subcontracting Plan (Deviation 2016-O0009), including a Department of Defense Comprehensive Subcontracting Plan as long as it is approved by the Defense Contract Management Agency. Subcontracting Plans shall reflect the Offeror's commitment, in terms of the value of the total acquisition, to small businesses as proposed in response to Factor 4: Small Business Participation. Subcontracting Plans that do not reflect at least the same small business participation (e.g., percentage and type of small business concern) as proposed in response to Factor 4 will be considered non-compliant with this solicitation.

L.8.7 Meeting Space Capability The Offeror shall provide either proof of existing facilities or proof of a contingency offer within the proposal that can be executed upon ID/IQ contract award to meet meeting requirements outlined in PWS paragraph 7.9.3 by the ID/IQ Period of Performance start date.

L.8.8 Representation, Certification, and other Statements of Offerors The Offeror shall complete representations, certifications, acknowledgments, and statements via the System for Award Management (SAM) (http://www.sam.gov). A completed copy from SAM and any additional Section K information required by this solicitation shall be included in this Volume.

L.8.9 Terms and Conditions The Offeror is required to meet all solicitation requirements, such as terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors. By submission of its proposal, the Offeror accedes to all solicitation requirements, including terms and conditions, representations and certifications, and technical requirements.

L.9 Volume III - Evaluation Factor 1: Technical Experience (15 page limit)

Volume III shall be specific, detailed, and complete to demonstrate clearly and fully that the Offeror has the technical experience to accomplish all requirements of the PWS. Offerors shall document their current, relevant technical experience as it relates to the following exemplar sections of the PWS:

· PWS Section 7.1.2 (Technical Expertise/Subject Matter Expertise (SME))*

· PWS Section 7.2.2 (Program Financial Execution)

· PWS Section 7.9.1 (Event Assistance)

Statements that the Offeror has demonstrated experience to accomplish the listed functions without supporting information or narrative is inadequate. This section shall be written to enable evaluators to make a thorough evaluation as to whether the Offeror has demonstrated experience and shall contain specific descriptions and examples of work performed to include value, complexity, and nature in exemplar PWS Sections 7.1.2, 7.2.2, and 7.9.1, listed in order of importance. The individual PWS Section responses are not to be considered subfactors for evaluation. Each Offeror will only receive a single rating for Factor 1.

*For PWS Section 7.1.2, the Offeror shall show experience across the breadth of the type of technologies performed within technical offices identified in PWS Section 4 (i.e., Biological Technologies, Defense Sciences, Information Innovation, Microsystems Technology, Strategic Technology, and Tactical Technology).

Factor 1: Technical Experience will focus on what work the Offeror has done correlated to this requirement, while Factor 3: Past Performance will focus on how well the Offeror has historically performed. Therefore, Offerors shall demonstrate a direct link between technical experience cited in this factor and contracts submitted for past performance.

Any technical experience referenced must have been performed since January 1, 2018, and must have a contract/order value over $15 million. An ID/IQ contract must have at least one task order exceeding $5 million. All contract values shall be representative of obligation amounts; when submitting for an ID/IQ contract, the obligation amount shall represent the combined obligation of all awarded task orders.

Given the value, complexity, and nature of this procurement, all past or current contract performance referenced as technical experience shall be performance as a prime contractor. All referenced contracts shall be listed in Attachment 4, providing a minimum of the following information: contract number, period of performance (including months/years), contract value, the amount invoiced to date, and Government point of contact (POC).

Attachment 4 will not count against established page limits but shall not include any more information than required.

There is no limit on the number of contracts/orders that can be referenced and listed within Factor 1: Technical Experience. However, all of the past performance submissions (up to six) used for Factor 3: Past Performance must be referenced in Factor 1.

L.10 Volume IV - Evaluation Factor 2: Management Approach (10 page limit) The Offeror shall provide its proposed management approach for delivering high quality support services to accomplish all requirements of the PWS through Sections (a) through (d) below, which are for factor organization purposes only and are not to be considered subfactors for evaluation. Each Offeror will only receive a single rating for Factor 2.

a. Overall ID/IQ Management Plan

· Plan for managing multiple task orders and multiple subcontractors. The plan shall describe how the Offeror is able to manage several orders and several subcontractors across the full range of PWS requirements.

· Program Management Team construct, qualifications, and commitment. The Program Management Team is defined, at a minimum, as the overall Contract Program Manager and any other members required to successfully manage an ID/IQ of this size and complexity (e.g., office leads, functional leads, etc.). Offerors shall provide resumes of the proposed Program Management Team, the type of commitment individual(s) has with the company (e.g., contingent, employed, representative), and letter(s) of intent (if applicable). The proposed Program Management Team will be considered Key Personnel at the ID/IQ level. Note: Resumes submitted are restricted to two (2) pages per individual on the Program Management Team and do not count towards the overall 10-page limit. Letters of intent are restricted to one (1) page per individual on the Program Management Team and do not count towards the overall 10-page limit.

b. Recruitment and Retention

· The Offeror shall describe its overall staffing/hiring methodology to address evolving DARPA needs. The Offeror shall describe what subcontracting and hiring practices will be used and illustrate the process for filling vacancies for extremely technically advanced expertise in a timely manner. Identify how the corporation/team can readily obtain the experience and expertise required to accomplish the full range of PWS support requirements. Offeror shall include the historical average time(s) to execute services subcontracts (i.e., not commodity purchases) for all contracts described in Technical Experience via Attachment 4 (measured as time between Government identification of a new in-scope requirement during the performance of a contract or task order and the date of the subcontract award issued to meet this requirement).

· The Offeror shall describe its plan to incentivize on-site, off-site, and hybrid employees with varying levels of telework available per task order and position.

· The Offeror shall describe a specific detailed plan for effectively retaining Science and Technology (S&T) and Research and Development (R&D) professional support in efforts to minimize the turnover rate to avoid mission degradation.

· In accordance with FAR 52.222-46, Evaluation of Compensation for Professional Employees, the Offeror shall submit a total compensation plan setting forth salaries and fringe benefits proposed for all professional employees (per FAR 22.1102 definition) who will work under the contract. 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. NOTE: Total Compensation Plan does not count towards the overall 10-page limit for Management Approach.

c. Training

· The Offeror shall describe in detail how it plans to quickly and effectively train and mentor new personnel on DARPA procedures, collaboration tools (especially those listed in PWS Section 7.3.5), and policy.

d. Culture

· The Offeror shall describe its methodology for measuring, strengthening, and promoting its organizational culture in a hybrid (in-person and virtual) work environment. Specifically, the Offeror shall describe its approach to promoting its organizational culture among its on-site, off-site, and hybrid employees, including its plan to:

· Rapidly onboard and successfully assimilate new personnel to DARPA culture, and then create, promote, and preserve a sense of community between its personnel, as well as Government and other contractor personnel, in a hybrid environment;

· Facilitate knowledge sharing across multiple contractor and Government teams supporting DARPA; and

· Ensure that provided collaboration tools (especially those listed in PWS Section 7.3.5) are available and maximally leveraged to integrate hybrid personnel.

L.11 Volume V - Evaluation Factor 3: Past Performance (123 page limit)

The Offeror shall submit a Past Performance Volume containing the following information: a) Table of Contents; b) Summary Page; c) Past Performance Information Submissions; d) Contractor Performance Assessment Reporting System (CPARS) and Questionnaire Submissions; and e) Organization Structure Change History, if applicable.

a. Table of Contents (No page limit) The table of contents should include page numbers for each CPARS evaluation by contract and applicable Period of Performance.

b. Summary Page (No1 page limit) The Summary Page shall describe the role of the Offeror and each teaming partner, if applicable, for the proposed TASS effort.

c. Past Performance Information Submissions (12 page limit)

Offerors may provide up to six (6) past performance information submissions, of which at least half of the submissions must be from the prime contractor. Given the value, complexity, and nature of the procurement, all past or current contract performance information submitted for the prime or any subcontractors shall be performance as a prime contractor. All submissions shall relate to experience submitted within Factor 1: Technical Experience and shall only be for contracts/orders over $15 million or for an ID/IQ contract with at least one task order exceeding $5 million. All contract values shall be representative of obligation amounts; when submitting for an ID/IQ contract, the obligation amount shall represent the combined obligation of all awarded task orders.

All submissions must be recent, as defined by services performed since January 1, 2018.

Offerors shall provide a two-page summary for each Past Performance Information Submission. The summary shall include the following (in the below order):

i. Identify the full contract number (and task/call order number if applicable – each task/call order is considered a submission) and program/requirement title.

ii. Identify the period of performance to include the months, days, and years (MM/DD/YYYY; e.g., 02/15/2018 – 02/14/2022).

iii. Identify the current obligation dollar amount, total contract value, and/or potential ceiling, as applicable.

iv. Identify contract type(s).

v. Identify whether the submission was performed by the Offeror or a proposed subcontractor as the prime.

vi. Identify the Government customer office name for the submission and provide the names, titles/roles, phone numbers, and email addresses of the following Government customer points of contact (POC) that may be knowledgeable of the Offeror's performance on the submission: Program Manager, Contracting Officer (CO), Administrative Contracting Officer (ACO), and Contracting Officer's Representative/Contracting Officer's Technical Representative (COR/COTR).

vii. Provide a brief description of the effort performed as a prime contractor and any significant portions of the effort performed by key subcontractors.

viii. Demonstrate how the Offeror's or proposed subcontractor(s)' performance is relevant (in scope, magnitude, and complexity) to the PWS requirements.

ix. Describe any problems encountered on the identified contract and any corrective action taken, to include response to any adverse past performance information available to the Government, as well as any efforts to identify and manage program risk.*

*Note: Merely having problems does not automatically equate to a "Limited Confidence" or "No Confidence" assessment, since the problems encountered may have been unavoidable, or an Offeror may have subsequently demonstrated the ability to overcome the problems encountered. The Offeror (or Subcontractor) shall clearly demonstrate management actions employed in overcoming problems and the effects of those actions in terms of improvements achieved or problems rectified. This may give the Offeror a higher confidence assessment rating. For example, submittal of quality performance indicators or other management indicators that clearly support an Offeror has overcome past problems would assist the Government when assigning the confidence assessment rating.

If the Offeror does not have any past performance information, the Offeror must state in this section that it possesses no relevant past performance. Offerors with no relevant past performance will receive a past performance rating of "Neutral Confidence".

In the conduct of its past performance evaluation of Offerors, DARPA may use a variety of sources in addition to information provided by the Offeror. DARPA/CMO may use past performance information obtained from sources other than those identified by the Offeror. These sources may include, but are not limited to, CPARS, Past Performance Information Retrieval Systems (PPIRS), technical reports, evaluator's personal knowledge, commercial or any available published information, and information derived from present or past Government or commercial customers of the Offeror. Those Offerors who have no relevant past performance history will not be evaluated either favorably or unfavorably on past performance. DARPA reserves the right to determine which contracts submitted by the Offeror are relevant to the requirements and to utilize only those references.

d. CPARS and/or Past Performance Questionnaires (No page limit)

For each Past Performance Information Submission, Offerors shall submit ALL Contractor Performance Assessment Reporting System (CPARS) evaluations that were completed for the relevant time period (since January 1, 2018).

If CPARS evaluations are not available, Offerors (or subcontractors) shall request that their Government customer submit past performance information on the Past Performance Questionnaire (PPQ) found at Attachment 5. The POCs identified on the questionnaire must be able to provide information on the quality of the Offeror or subcontractor's performance. Each CPARS evaluation or PPQ must correspond to the past performance experience cited in Offeror's Factor 1: Technical Experience submission. The Offeror's customers must send past performance information to TASSIDIQREQUIREMENT@darpa.mil by the proposal due date. The Offeror shall include in this section proof of correspondence with Government customer requesting past performance information (e.g., copy of date-stamped email).

When CPARS are not available, the Offeror shall request that its Government customer submit past performance information on the Past Performance Questionnaire found at Attachment 5. Each past performance questionnaire must correspond to the past performance experience cited in Offeror's Technical Experience Volume. The points of contact identified on the questionnaire must be able to provide information on the quality of your performance.

e. Organization Structure Change History (No page limit)

Many Offerors have acquired, been acquired by, or otherwise merged with other companies, and/or reorganized its divisions, business groups, subsidiary companies, etc. In many cases, these changes have occurred during the performance of relevant past efforts or between conclusion of recent past efforts and source selection. As a result, it is sometimes difficult to determine what past performance is relevant to this procurement. To facilitate this relevancy determination, include in this proposal Volume (if applicable), a "roadmap" describing all such changes in the company within the past seven (7) years. As part of this explanation, show how these changes impact the relevance of any efforts identified 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, the Offeror's "roadmap" should be specifically applicable to the efforts identified but general enough to apply to efforts on which the Government receives information from other sources. This information is required for the Offeror and any teaming partner(s) being used for past performance information submissions. The Government reserves the right to exclude sources due to conflicts of interest.

Determination of Responsibility: 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 9.1, Responsible Prospective Contractors, past performance information obtained herein may be used to support the determination of responsibility for successful Offerors.

Note: Subcontractors, in order to protect proprietary information, may send CPARS evaluations or responses to adverse past performance directly to TASSIDIQREQUIREMENT@darpa.mil, but it shall conform to the requirements of this solicitation and be received by the proposal due date.

L.12 Volume VI - Evaluation Factor 4: Small Business Participation (5 page limit) All Offerors, with the exception of small businesses, shall submit a Small Business Participation Plan separate from the subcontracting plan. The Small Business Participation Plan shall:

a. Identify specific small businesses, their role, and the type of commitment between the prime and small business.

b. Describe the expertise, variety, and appropriateness of work small businesses are to perform.

c. List extent of participation of small business by small business type (e.g., service-disabled veteran-owned, HUBZone, small disadvantaged, and women-owned small businesses) in terms of value of the total acquisition. DARPA's minimum small business subcontracting goal is 24%, with the desired goal of 30%, of the total value of the acquisition.

d. Provide Offeror's past performance in complying with the requirement at FAR 52.219-8, Utilization of Small Business Concerns, and FAR 52.219-9, Small Business Subcontracting Plan.

L.13 Volume VII - Evaluation Factor 5: Price (No page limit)

The Offeror shall submit information other than cost or pricing data that is required to evaluate the fair and reasonableness of the Offeror's proposed price for maximum Labor Hour rates. Compliance with these requirements is mandatory and failure to comply may result in rejection of the Offeror's proposal. Price fair and reasonableness and price or cost realism (as applicable) of fixed price or cost-type requirements for task orders will be evaluated at the task order level.

This Volume shall be a complete and detailed breakdown and shall include all elements of cost, and other data as considered appropriate, to support the Offeror's proposal. Particular emphasis will be placed upon the reasonableness of applied fringe and burden of the labor rates, along with any pass-through fees. The straight time hourly rates shall use a forty-hour week for the conversion of salaried employees to the hourly basis and shall be inclusive of loading factors (i.e., vacation, sick leave, holidays, overhead, General and Administrative rates (G&A), fee, etc.). Offerors shall submit their cost/price for Labor Hour labor rates via Attachment 3, using 1920 hours as a baseline and shall not convert it to a .pdf file.

L.13.1 Estimating Techniques and Methods

When responding to the Price Volume requirements of this solicitation, the Offeror and associated subcontractor(s) may use any generally accepted estimating technique, including contemporary estimating methods (such as Cost-to-Cost and Cost-to-Non-Cost Estimating Relationships, commercially available parametric cost models, in-house developed parametric cost models, etc.) to develop its estimates.

L.13.2 Cost or Pricing Information Requirements

Information beyond that required by this solicitation shall not be submitted, unless the Offeror considers it essential to document or support its cost/price position. All information relating to the proposed cost/price, including all required supporting documentation, must be included in the section of the proposal designated as Volume VII Price Proposal. Under no circumstances shall this information and documentation be included elsewhere in the proposal unless expressly stated otherwise.

Note: The cost or price information in the Subcontracting Plan (Section L.8.6), Factor 4: Small Business Participation, and Total Compensation Plan (Section L.10.b) are not included in this restriction.

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 the price reasonableness of proposed maximum labor hour rates. 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, the Offeror shall be required to submit cost or pricing data. Information shall be provided in accordance with FAR 15.403 through 15.405.

L.13.3 Volume Organization

The Price Volume shall contain the following:

· Table of contents;

· Summary descriptions of estimating, purchasing, and accounting systems;

· The most recent Forward Pricing Rate Proposal, Recommendation, and/or Agreement (FPRA) for prime (as available);

· Changes to estimating, accounting practices, or Cost Accounting Standards (CAS) Disclosure Statement (as applicable), cost/price information;

· Supporting data; and

· Completed Attachment 3

L.13.4 Estimating Method

a. Estimating System Provide a summary description of the Offeror's standard estimating system or methods. The summary description shall cover separately each major cost element (e.g., Direct Material, Engineering Direct Labor, Indirect Costs, Other Direct Costs, Overhead, G&A, etc.). Also, identify any deviations from the Offeror's standard estimating procedures in preparing this proposal Volume. Indicate whether the Offeror has Government approval of its system, and if so, provide evidence of such approval.

b. Purchasing System Provide a summary description of its 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). Also, identify any deviations from the Offeror's standard procedures in preparing this proposal Volume. Indicate whether the Offeror has Government approval of its system and if so, provide evidence of such approval.

c. Explanation of Estimating Methods Used Explain the method used to estimate each cost element used to derive final Labor Hour rates and include pass-through fees that will be used for subcontractor labor.

L.13.5 Price Fair and Reasonable

The Offeror shall propose ceiling rates for Labor Hour task orders by completing the Labor Hour Labor Category Pricing Spreadsheet (Attachment 3) with the proposed hourly labor rates for each labor category listed. The Offeror shall provide a loaded hourly rate for the National Capital Region for each labor category. The Offeror shall assume that the personnel proposed under these rates will receive Government furnished facilities and equipment in accordance with PWS Section 8. Proposed loaded hourly labor rates will be the maximum allowable rates used throughout the life of this contract for the aforementioned labor categories only on Labor Hour task orders. However, the contractor may discount rates for individual task orders. Actual rates for Fixed Price, Cost-Reimbursement, or any combination thereof, will be established via competition or negotiation at the task order level.

L.14 Submission Format Details

Each Volume shall be complete in and of itself. Unless otherwise specified, any form of presentation may be used, such as narrative, pictures, tables, graphs, schematics, logic and other functional block diagrams to provide a concise description of information. The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal shall not simply rephrase or restate the Government's requirements, but rather shall provide a convincing rationale to address how the Offeror intends to meet the areas to be evaluated. 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.

L.14.1 Text 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. A page printed on both sides shall be counted as two pages. No foldout pages shall be used. Pages submitted in excess of the page limitations stated throughout this document will be removed and not evaluated.

L.14.2 Illustrations and Tables Legible tables, charts, graphs and figures should be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays should be uncomplicated, legible, and shall not exceed restrictions in Sections L.14.1 and L.14.3.

L.14.3 Font Size 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.

L.14.4 Page Limits Page limits are identified below. The page limits do not include cover/title pages, tables of contents, response matrix, index, and/or glossary.

L.15 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 subfactors or 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. During the evaluation of proposals, the Government may determine a proposal is "Unacceptable" and ineligible for award without further evaluation. DARPA reserves the right to waive informalities and minor irregularities in proposals received in accordance with FAR 52.215-1(f)(3).

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.16 Exceptions/Assumptions

Offerors are prohibited from modifying, in any way, shape, or form, any documents, printed or electronic, associated with this solicitation or any amendment(s) thereto unless specifically authorized to do so. The electronic solicitation documents, as posted on http://www.SAM.gov, shall be the official documents for this solicitation.

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 rejecting the proposal. Clarification of Government requirements shall be resolved by submitting questions/recommendations by the date specified in Section L.4.

L.17 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) 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.18 Incurring Costs

DARPA/CMO shall not be obligated to pay any cost incurred by the Offeror in the preparation and submission of a proposal in response to this solicitation. The Offeror is 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.