HDTRA118R00020002.docx

HDTRA118R0002

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

SECTION L

SECTION L

INSTRUCTIONS, CONDITIONS, AND NOTICES TO BIDDERS

CLAUSES INCORPORATED BY REFERENCE

CLAUSES INCORPORATED BY FULL TEXT

FAR 52.216-1 TYPE OF CONTRACT (APR 1984)

The Government contemplates award of an Indefinite-Delivery/Indefinite-Quantity (ID/IQ) contract resulting from this solicitation containing Firm Fixed Price (FFP), Cost Plus Fixed Fee (CPFF), Cost Plus Award Fee (CPAF) and Cost only- no fee CLINS.

(End of provision)

52.233-2 SERVICE OF PROTEST (SEP 2006)

1. Protests, as defined in Section 33.101 of the Federal Acquisition Regulation, that are filed directly with an agency, and copies of any protests that are filed with the Government Accountability Office (GAO), shall be served on the Contracting Officer (addressed as follows) by obtaining written and dated acknowledgment of receipt from:

Mr. Michael Awadallah Contracting Officer Defense Threat Reduction Agency Contracts-Information Operations Branch, AL-ACN Phone: (703) 767-7894 Email: dtra.belvoir.al.mbx.itss@mail.mil

1. The copy of any protest shall be received in the office designated above within one day of filing a protest with the GAO.

(End of provision)

L.1.0 GENERAL INSTRUCTIONS TO OFFERORS

L1.1 GENERAL INFORMATION

L.1.1.1 Points of Contact

The Contract Specialist (CS) is the primary point of contact for this acquisition.

The CS for this acquisition is:

Ms. Tammy Faulkner Defense Threat Reduction Agency Contracts-Information Operations Branch, AL-ACN Phone: Will be provided at time of award Email: dtra.belvoir.al.mbx.itss@mail.mil

The Contracting Officer (KO) for this acquisition is:

Mr. Michael Awadallah Defense Threat Reduction Agency Contracts-Information Operations Branch, AL-ACN Phone: Will be provided at time of award Emaildtra.belvoir.al.mbx.itss@mail.mil

All questions, concerns, or requests for clarification for this RFP shall be submitted electronically to dtra.belvoir.al.mbx.itss@mail.mil no later than 10:00am EST on 15 March 2018, no phone calls are permitted. No comments, questions or inquiries shall be made of any Government person other than the points of contact listed above. Questions received after this date and time may not be responded to by the Government. All emails shall be clearly labeled in the subject line of the email with the RFP Number: HDTRA1-18-R-0002: ITSS. Offerors shall clearly identify the specific section of the solicitation to which each question relates when submitting questions. Reference should be made to the solicitation Section Heading, page number of the solicitation, and specific location on the page (e.g., third paragraph) in order to facilitate the Government’s response to each question. Questions shall be submitted in a Microsoft Excel file following a format similar to the table below:

Responses to submitted questions will be provided to all Offerors via FedBizOpps at https://www.fbo.gov. If amendments to the solicitation are issued, all Offerors must acknowledge the amendments by signing the accompanying Standard Form (SF) 30 and returning the signed SF 30 for all amendments issued with the Offeror’s proposal submission. Failure to acknowledge all amendments issued by the Government may result in the proposal submitted in response to the solicitation being found non-responsive by the Government.

L.1.1.2 Debriefings

L.1.1.2.1 Pre-Award Debriefings Offerors excluded from the competitive range or otherwise excluded from the competition before award may request a debriefing by submitting a written request to the CS within three (3) business days after receipt of the notice of exclusion from the competitive range. The Government shall make every effort to debrief unsuccessful Offerors as soon as practicable.

L1.1.2.2 Post-award Debriefings Offerors may request a debriefing by providing a written request to the CS within three (3) business days after receipt of the Contract Specialist’s notification. To the maximum extent practicable, debriefings will be conducted within fifteen (15) business days of the Offeror’s request.

L1.1.3 Discrepancies If an Offeror believes the solicitation, including the instructions to Offerors, contains an error, omission, or ambiguity, or is otherwise unsound, the Offeror shall immediately notify the Contract Specialist and Contracting Officer in writing with supporting rationale at any point prior to the proposal submission deadline.

L1.1.4 Discussions and Final Proposal Revisions IAW FAR 52.215-1 (f) (4) The Government intends to evaluate proposals and award a contract without discussions with offerors (except clarifications as described in FAR 15.306(a)). Therefore, the offeror’s initial proposal should contain the offeror’s best terms from a cost and technical standpoint. The Government reserves the right to conduct discussions if the Contracting Officer later determines them to be necessary. If the Contracting Officer determines that the number of proposals that would otherwise be in the competitive range exceeds the number at which an efficient competition can be conducted, the Contracting Officer may limit the number of proposals in the competitive range to the greatest number that will permit an efficient competition among the most highly rated proposals.

L.1.2 PROPOSAL ORGANIZATION

The Offeror shall organize the proposal as set forth in the table below. The titles and contents of the volumes as well as the page limitations and number of required copies are specified. In the event that the table conflicts with the detailed instructions in the paragraphs that follow, the detailed instructions shall take precedence.

II

ID/IQ FACTOR 1, MISSION CAPABILITY

No Limit

No Limit

No Limit

Key Personnel Resume / Commitment Statement

3 pages combined

III

ID/IQ FACTOR 2, PAST PERFORMANCE

Past Performance References 5 pages per reference (Narrative and Attachment 10)

L.1.3 PROPOSAL FORMAT:

L.1.3.1 Guidance This section of the Information to Offerors (ITO) provides general guidance for preparing proposals as well as specific instructions on the format and content of the proposal. The Offeror’s proposal must include all data and information requested by the ITO and must be submitted in accordance with these instructions. Non-compliance with the instructions provided in the ITO may result in an unfavorable proposal evaluation.

L.1.3.2 Sufficient Detail Proposals shall comply with the following guidelines:

· Be complete and respond directly to the requirements of the solicitation.

· Address the factors, sub-factors, and their related elements as listed in Section M of the solicitation.

· Be clear, concise, and include sufficient detail for effective evaluation and for substantiating the validity of stated assertions. Extraneous, repetitious, or wordy submissions are not desired and could result in lower ratings.

· Do not simply rephrase or restate the Government’s requirements, but rather provide convincing rationale and demonstrated evidence or experience to address how the Offeror intends to satisfy the requirement and provide value or benefit to the government.

· Assume that the Government has no prior knowledge of the Offeror’s capabilities and experience, and will base its evaluation only on the information presented in the Offeror’s proposal.

L.1.3.3 Validity Statement The offeror is requested to complete the proposal validity date in block 12, Section A of the solicitation, with not less than 180 days. In addition, the Offeror shall make a clear statement that the proposal is valid for the duration of the acceptance period. In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain a copy of all unsuccessful proposals.

L.1.3.4 Physical Appearance of Submissions

1. Elaborate brochures or documentation, detailed artwork, or other embellishments are unnecessary and are not desired.

1. Proposals will be submitted in electronic copies only.

1. No models, mockups, or videotapes will be accepted.

L.1.3.5 Page Format Restrictions and Limitations

L.1.3.5.1 Page Size Pages shall be 8.5 x 11 inches. Font size shall be twelve (12) point Times New Roman. Lettering within tables, charts, graphs, and figures shall be no smaller than ten (10) point Times New Roman. Margins on all four edges of each sheet will be at least one-inch. Proprietary statements, security markings, and page numbers shall be placed within the defined margin area. Pages shall be numbered sequentially by volume. In the event discussions are held, these page format restrictions shall apply to the Final Proposal Revisions (FPRs).

L.1.3.5.2 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. The excess pages will be deleted from the electronic proposal. In the event discussions are held, page limitations may be placed on responses to Evaluation Notices (ENs). Page limits, if specified for EN responses, will be identified in the letters forwarding the ENs to the Offerors.

L.1.3.5.3 Pages Counted Each page shall be counted except the following:

· past performance questionnaires

· past performance questionnaire point of contact list

· cover pages

· RFP cross-reference matrix

· past performance consent letters

· client authorization letters

· tables of contents

· glossary of abbreviations and acronyms

· lists of figures, tables, or drawings

· tabs/dividers

· blank pages

L.1.3.6 Indexing Each volume shall contain a more detailed table of contents to delineate the sections within that volume. Tab indexing shall be used to identify sections.

L.1.3.7 Electronic Copies Electronic submission of each volume shall be submitted via email to: dtra.belvoir.al.mbx.itss@mail.mil ONLY, no hardcopies will be accepted.

L.1.3.8 Cost Information All cost information shall be addressed ONLY in the Proposal Documentation and Cost Volumes, Volumes I and IV respectively. All labor rates shall be rounded to the nearest penny. All cost information, with the exception of the cost narrative, must lend itself to review and analysis by the Government and must be submitted using the cost proposal instructions provided as Attachment 12. Offerors shall include formulas and working links to the maximum extent practicable.

L.1.3.9 Volume Designation Information required for proposal evaluation that is not found in its designated volume will be assumed to have been omitted form the proposal. Each volume shall be written on a stand-alone basis so that its contents may be evaluated without cross-referencing to other volumes of the proposal. Exceptions to the above include only teaming arrangements, letters of commitment, socio-economic commitment information and Organizational Conflicts of Interest assertions which must be submitted in Volume I but may be cross-referenced in other volumes.

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

L.2.0 VOLUME I –PROPOSAL DOCUMENTATION

Volume I consists of the offer to enter into a contract to perform the desired work and information for the Government to prepare the contract document and supporting file.

L.2.1 VOLUME ORGANIZATION

The volume shall be organized according to the following outline:

1. Table of Contents

1. List of Tables and Drawings

1. Glossary

1. Documents listed in paragraphs L.2.2 through L.2.11

L.2.2 SOLICITATION/CONTRACT FORM

Completion of Blocks 12 through 16 and signature and date for Blocks 17 and 18 of the Standard Form (SF) 33 is required. Signature by the Offeror on the SF 33 constitutes an offer, which the Government may accept.

L.2.3 AUTHORIZED OFFEROR PERSONNEL

Provide the name, title, telephone number, fax number, and e-mail address of the company and division point of contact regarding decisions made with respect to the Offeror’s proposal and who can obligate the Offeror contractually. Also identify those individuals authorized to negotiate with the Government.

L.2.4 GOVERNMENT OFFICES

Provide the mailing address, telephone and fax numbers, and facility codes for the cognizant Contract Administration Office, Defense Contract Audit Agency (DCAA), Defense Contract Management Agency (DCMA) and Government Paying Office. Also provide the name, telephone and fax numbers, and e-mail address for the Administrative Contracting Officer (ACO). The aforementioned information also applies to the prime contractor and major subcontractors/teaming partners.

L.2.5 COMPANY DIVISION ADDRESS, IDENTIFYING CODES AND APPLICABLE DESIGNATIONS

Provide the company’s/division’s street address, county, and facility code; CAGE Code; DUNS number; Taxpayer Identification Number (TIN), size of business (large or small); and labor surplus area designation.

L.2.6 TEAMING ARRANGEMENTS AND/OR LETTERS OF COMMITMENT

In accordance with FAR Subpart 9.6, a contractor team arrangement is defined when two or more companies form a partnership or joint venture to act as a potential prime contractor; or a potential prime contractor agrees with one or more other companies to have them act as its subcontractors under a specified Government contract or acquisition program.

The Offeror shall provide a matrix of all proposed subcontractors/team members and the specific areas within the ID/IQ SOO and Task Orders 1, 2 and 3 for which they will be utilized. The matrix shall clearly identify the CAGE code and DUNS for each team member. Offerors shall also provide an approximate percentage of effort, based on overall price, that each subcontractor/team member will contribute to the overall effort. For purposes of this evaluation, the overall effort shall be for Task Orders 1, 2, and 3. If there are additional subcontractors which are not anticipated to play a role in Task Orders 1, 2, and 3 but may be utilized in the future, the projected future role of these subcontractors should be clearly addressed. This information will be utilized to determine relevancy for the subcontract references.

In addition, the Offeror shall submit a consent letter or statement, executed by each subcontractor, teaming partner, and/or joint venture partner, authorizing release of adverse past performance information to the Offeror, so the Offeror can respond to such information. For each identified effort for a commercial customer, the Offeror shall also submit a client authorization letter, authorizing release to the Government of requested information on the Offeror’s performance.

L.2.7 DEPARTMENT OF DEFENSE (DD) FORM 254 SECURITY REQUIREMENTS

Provide information relative to offeror’s facility clearance and the contact information for the offeror security office. Information relative to subcontractor security requirements shall also be included. Offeror’s shall complete and submit Attachment 5, Department of Defense (DD) Form 254 Contract Security Classification Specification. Contractor shall have final Top Secret facility clearance at time of award.

L.2.8 INFORMATION REQUIRED BY DFARS CLAUSE 252.227-7017 IDENTIFICATION AND ASSERTION OF USE, RELEASE, OR DISCLOSURE RESTRICTIONS (JUN 1995) If applicable, the Offeror shall include 252.227-7017 paragraph (d) chart, in full-text, filled-in/completed.

L.2.9 EXCEPTIONS TO TERMS AND CONDITIONS

Exceptions taken to the terms and conditions of the solicitation, or to any of its formal attachments shall be identified. Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken. Provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule, cost, and specific requirements of the solicitation. This information shall be provided in the format and content of Table 2.9. Failure to comply with the terms and conditions of the solicitation may result in the Offeror being removed from consideration for award.

Table 2.9 – Solicitation Exceptions

L.2.10 REPRESENTATIONS, CERTIFICATIONS, AND OTHER STATEMENTS OF OFFEROR(S) (SECTIONS K AND L) The Offeror is responsible to ensure that all representations, certifications, acknowledgements, and statements provided in accordance with Sections K and L are current at the time of proposal and provided in the System for Award Management (SAM) at http://www.sam.gov/.

L.2.11 PREAWARD ORGANIZATIONAL CONFLICTS OF INTEREST

a. The Contracting Officer has determined this contract may give rise to potential conflicts of interest due in part to contractors currently providing support to DTRA, who may have access to information that could potentially provide an unfair competitive advantage. Moreover, the nature of the work required by this contract could provide the awardee access to information that could potentially provide an unfair competitive advantage for future contracts. Offerors are directed to FAR Subpart 9.5 for detailed information concerning organizational conflicts of interest.

b. Each offeror must include in Volume I of its proposal either;

(1) a statement certifying that, to the best of its knowledge, it is not aware of any facts which create any actual or potential organizational conflicts of interest relating to the award of this contract, or

(2) a statement that describes concisely all relevant facts concerning any past, present, or planned interest (financial, contractual, organizational, or otherwise) relating to the work to be performed under the proposed contract and bearing on whether the offeror has a possible organizational conflict of interest.

c. The Contracting Officer may require further relevant information from an offeror and may, at his discretion, permit an offeror to clarify errors or omissions in relevant information or in a statement required by (b) above. Refusal to provide a statement required by (b) above, refusal to provide further relevant information required by the Contracting Officer, or the misrepresentation of any relevant information will result in disqualification of an offeror from further consideration for award of a contract under this solicitation.

d. Relevant information regarding possible organizational conflicts of interest will not be treated like a separate evaluation factor, however, it will be addressed during the evaluation of proposals. Relevant information regarding each offeror will be analyzed by the Contracting Officer in accordance with FAR 9.5 in order to determine whether a potential conflict exists and if so, what actions are necessary to avoid or otherwise resolve the potential conflict.

e. The Contracting Officer will use all relevant information submitted by the offeror, and any other relevant information known to DTRA, to determine whether a potential conflict exists. If the Contracting Officer determines that a potential conflict exists, the conflict must be avoided or otherwise resolved through the inclusion of a special contract clause or other appropriate means. Although the terms of any special clause are subject to negotiation, it is likely that the contract will include a clause substantially the same as DTRA Clause 252.209-9000 which is included in Section H of the contract.

L.3.0 VOLUME II – FACTOR 1, MISSION CAPABILITY

L.3.1 GENERAL

The Factor 1 Mission Capability Volume should describe the Offeror’s capability to satisfy the requirements of this solicitation. The proposal should be prepared simply and economically, providing straightforward, concise delineation of the management approach and technical capabilities to satisfactorily perform the contract being sought. Particular proposal strengths or unique approaches should be emphasized. Asserted capability and/or intent to meet the requirements must be supported by detailed descriptions of approach, qualifications, and experienced-based evidence of the benefits or value of the proposed approach. The Government will not assume that an Offeror possesses any capability unless specified in the proposal.

Offeror responses will be evaluated against the Mission Capability sub-factors and their related elements defined in Section M, “Evaluation for Award.” Using the instructions provided below, provide as specifically as possible the actual methodology that would be used by the Offeror for accomplishing and satisfying these sub-factors. All the requirements specified in the solicitation are mandatory. By submitting a proposal, the Offeror is representing that its firm is capable and committed to performing all the requirements specified in the solicitation.

L.3.2 VOLUME ORGANIZATION:

The volume shall be organized according to the following outline:-

1. Table of Contents

1. List of Tables and Drawings

1. Glossary

1. RFP Cross-Reference Matrix

1. Section 1, Sub-Factor A - Management Approach

1. Section 2, Sub-Factor B - Task Order 1, IT Service Provisioning and Operations; Technical Approach

1. Section 3, Sub-Factor C - Task Order 2, Cybersecurity Support Services; Technical Approach

1. Section 4, Sub-Factor D - Task Order 3, Test, Transition, and Integration Support Services; Technical Approach

L.3.3 FORMAT AND SPECIFIC CONTENT

Mission Capability shall describe, in narrative form, the Offeror’s proposed approach to meeting the requirements of each Mission Capability sub-factor and their related elements, as well as their intended strategy for fulfilling the requirements of the contract. The Offeror shall include the mission capabilities of their team members and other intended subcontractors. The proposed teaming structure, team member roles and responsibilities, experience working as a team, and anticipated portion (by percentage, type of work, geographical, etc.) of work effort for each team member should be discussed or clearly delineated.

L.3.3.1 RFP CROSS-REFERENCE MATRIX (RCRM)

The Offeror shall fill out an RCRM indicating where the proposal addresses the solicitation requirements. An example format is shown below. The purpose of the RCRM is to show critical interrelationships and dependencies among the documents. The matrix ensures that all requirements are addressed, requirements do not conflict, and proposal sections are internally consistent. This matrix only applies to Volume II.

Example Format:

SOLICITATION CROSS REFERENCE MATRIX

Solicitation Section/Paragraph

Section/Paragraph Proposal Volume/ Section/Paragraph

L.3.3.2 SUB-FACTOR A, MANAGEMENT APPROACH

The Offeror shall submit a comprehensive and detailed Sub-Factor A Management Approach to manage the full scope of work at the ID/IQ and TO levels. In this Sub-factor the government will evaluate the viability of the proposed approach to effectively manage the ID/IQ contract and the subsequent TOs to be issued against the contract. This will include a review of the staffing structure, the proposed labor mix, the qualifications of the Key Personnel, the Offeror’s corporate support structure, and the offeror’s approach to quality control. This will include the following:

· Key Personnel

· Staffing Approach

· Mission Understanding

· Approach to Quality Control

· Integration

· Ability to Support the Full Range of Contract Types

· Facility Clearance

· Transition Plan

L.3.3.3 SUB-FACTOR B, TASK ORDER 1; IT SERVICE PROVISIONING AND OPERATIONS; TECHNICAL APPROACH The Offeror shall describe its practical application of the processes, procedures, and approaches to perform the PWS which is included in Attachment 2. The contractor shall provide technical expertise and support for the DTRA IT service integration, provision, and operation. The Offeror’s proposal shall demonstrate a sound understanding of the complexities and scope of the task order (TO), as well as experience-based evidence of the benefits or value of the proposed technical and management approach to satisfying the requirements of the TO PWS and performance standards. This will include the following:

· Technical Approach

· Staffing Plan

· Staffing Risk

L.3.3.4 SUB-FACTOR C, TASK ORDER 2; CYBERSECURITY SUPPORT SERVICES; TECHNICAL APPROACH The Offeror shall describe its practical application of the processes, procedures, and approaches to perform the PWS which is included in Attachment 3. The contractor shall provide the full range of cybersecurity support services (to include, information assurance (IA) planning and computer network defense (CND)). The goal is to provide an integrated delivery of cybersecurity services and solutions to support IT requirements across the agency. The Offeror’s proposal shall demonstrate a sound understanding of the complexities and scope of the task order (TO), as well as experience-based evidence of the benefits or value of the proposed technical and management approach to satisfying the requirements of the TO PWS and performance standards. This will include the following:

· Technical Approach

· Staffing Plan

· Staffing Risks

L.3.3.5 SUB-FACTOR D, TASK ORDER 3; TEST, TRANSITION, AND INTEGRATION SUPPORT SERVICES; TECHNICAL APPROACH The Offeror shall describe its practical application of the processes, procedures, and approaches to perform the PWS which is included in Attachment 4. The Offeror’s proposal shall demonstrate a sound understanding of the complexities and scope of the task order (TO), as well as experience-based evidence of the benefits or value of the proposed technical and management approach to satisfying the requirements of the TO PWS and performance standards. This will include the following:

· Technical Approach

· Staffing Plan

· Staffing Risks

· Transitioning and Integrating New Capabilities into the DTRA IT Infrastructure

L.3.3.6 SUB-FACTOR B, C, AND D TECHNICAL APPROACH QASP ATTACHMENT;

As an attachment to the technical approach for each Task Order (Sub-Factors B, C, and D) offerors shall include a proposed QASP to address the performance requirements identified in the PWS. The contractor shall complete the table below to satisfy the QASP requirements for each TO. The proposed QASP will be included in the awarded contract as an attachment.

Performance Requirement (PWS Para #) Performance Standard Performance Metric Acceptable Quality Level (AQL) Surveillance Method & Frequency

L.4 VOLUME III – PAST PERFORMANCE

L.4.1 VOLUME ORGANIZATION

The volume shall be organized according to the following outline:

1. Table of Contents

1. Description of Team

1. Past Performance References

1. Organizational Structure Change History

In addition, the Offeror shall submit a consent letter, executed by each subcontractor, teaming partner, and/or joint venture partner, authorizing release of adverse past performance information to the Offeror, so the Offeror can respond to such information. For each identified effort for a commercial customer, the Offeror shall also submit a client authorization letter, authorizing release to the Government of requested information on the Offeror’s performance.

L.4.2 Description of Team Include references for all Teaming Arrangements and/or Letters of Commitment as referenced in H.3 & L.2.6.

L.4.3 PAST PERFORMANCE REFERENCES

The offeror shall identify a minimum of three and a maximum of five references for the prime offeror as well as a minimum of one and maximum of two references for each of the subcontractors/teaming partners expected to perform aspects of the effort that the Offeror considers critical to the overall success of the program. The references shall represent recent contracts (within the past three years) that the Offeror considers most relevant in demonstrating the Offeror’s ability to perform the proposed effort. For each reference, the offeror shall provide a narrative describing the effort and the results of the Offeror’s performance. This narrative shall include rationale supporting the assertion of relevance and should be supplemented with a completed Past Performance Information Form (Attachment 10). For a description of the characteristics or aspects the Government will consider in determining relevance, see Section M, Paragraph M.2.2, Factor 2: Past Performance.

In addition to the information provided in the Past Performance Volume, the offeror shall ensure that each reference identified completes a Present and Past Performance Questionnaire (PPPQ) (Attachment 11), CPARs are acceptable in lieu of PPPQs. This questionnaire shall be submitted directly to the government from the reference; questionnaires received from the Offeror will not be considered. However, the responsibility to send out and track the completion of the PPQs rests solely with the Offeror. Completed PPQs shall be emailed in PDF format to the Contracting Officer and Contract Specialist at the e-mail addresses shown in Paragraph L.1.1.

L.4.4 ORGANIZATIONAL STRUCTURE CHANGE HISTORY

Many companies have acquired, been acquired by, or otherwise merged with other companies, and reorganized their divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the time of performance of relevant 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 the Offeror for the past 5 years and also include a “roadmap” for all team members identified in a Teaming Arrangement or Letter of Commitment for their efforts. As part of this explanation, show how these changes impact the relevance of any efforts the Offeror identifies for past performance evaluation and performance confidence assessment. Since the Government intends to consider past performance information provided by other sources as well as that provided by the Offeror, these “roadmaps” should be both specifically applicable to the efforts the Offeror identifies and general enough to apply to efforts on which the Government receives information from other sources. These “roadmaps” will not count toward the page limitations of Volume III.

L.5.0 VOLUME IV – COST

L.5.1 GENERAL

The Offeror shall provide a cost proposal for each Task Order that is consistent with the technical approach provided in Volume II. The proposals should be prepared simply and economically, providing straightforward, concise delineation of capabilities to satisfactorily perform the contract/task orders being sought.

These instructions are to assist the Offeror in submitting data other than certified cost or pricing data that is required to evaluate the reasonableness, realism, and completeness of the proposed costs. Compliance with these instructions is mandatory and failure to comply may render the Offeror’s proposal ineligible for award. Offers should be sufficiently detailed to demonstrate their reasonableness. The burden of proof of credibility of proposed costs and prices rests with the Offeror.

Data beyond that required by this instruction shall not be submitted unless the Offeror considers it essential to document or support the cost position. All information relating to the proposed cost and price, including the required supporting documentation must be included in the section of the proposal designated as the Cost Volume (Volume IV). Under no circumstances shall this information and documentation be included elsewhere in the proposal.

In accordance with FAR 15.403-1(b) and 15.403-3(a) and as detailed below, data other than certified cost or pricing data is not required. However, if after receipt of proposals it is determined that adequate price competition does not exist, certified cost or pricing data may be required (reference FAR 15.403-4). The Offeror shall provide current, complete, and accurate cost or pricing data within the calendar days specified in the Contracting Officer’s request.

L.5.2 VOLUME ORGANIZATION

The volume shall be organized according to the following outline:

1. Table of Contents

1. Glossary

1. Cost Narrative

1. Cost or pricing information and supporting data, to include estimating methodology

L.5.3 COST NARRATIVE

L.5.3.1 Assumptions The Cost Narrative shall identify all assumptions derived by the Offeror relating to estimated cost and shall reference the applicable paragraph and page number in the Mission Capability Volume (Volume II) of the proposal that provides a corresponding discussion of the particular assumption.

L.5.3.2 Inconsistencies A cost proposal is presumed to represent an Offeror’s best effort to respond to the solicitation. Any inconsistency, whether real or apparent, between promised performances and cost, shall be explained in the cost narrative. For example, if the intended use of new and innovative techniques is the basis for an abnormally low estimate, the nature of these techniques and their impact on cost should be explained. Any significant inconsistency, if unexplained, which raises a concern on the fundamental understanding of the nature and scope of the work required may be grounds for rejection of the proposal or grounds for adjusting the probable cost. The burden of proof as to cost-credibility rests with the Offeror.

L.5.3.3 Government Furnished Property (GFP)/Government Furnished Equipment (GFE) The cost narrative shall include a discussion of any GFP or GFE that the Offeror is assuming to be provided and timelines associated with receipt of GFP or GFE.

L.5.3.4 Contractor Systems The cost narrative shall include information for the prime contractor and any subcontractor/teaming members on the following contractor systems:

L.5.3.4.1 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, Direct Labor, Indirect Costs, Other Direct Costs, Overhead, G&A, etc.). Also identify any deviations from the standard estimating procedures used in preparing this proposal or future task order proposals under this contract. Indicate if the Offeror has Government approval of its system and if so, provide evidence of such approval. Offerors shall indicate whether there are any Forward Pricing Rate Agreements (FPRAs) in place and identify the applicable DCAA office of the prime contractor and major subcontractors/teaming partners.

L.5.3.4.2 Purchasing System Provide a summary description of the Offeror’s purchasing system or methods (i.e., 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 its standard procedures in preparing these or future task order proposals under the contract. Indicate if the Offeror has Government approval of its system and if so, provide evidence of such approval.

L.5.3.4.3 Accounting System In order to be considered for award of this contract and subsequent cost-type task orders awarded hereunder, the offeror shall provide evidence that it has an adequate financial management and accounting system and fund tracking procedures in accordance with FAR 16.301-3(a)(3). Offerors who have not had an Accounting System Review(s) by DCAA or DCMA may, at the offeror's expense, submit information from an Independent Certified Public Accountant (CPA), verifying that the offeror's accounting system complies with the requirements stated within the DCAA Contract Audit Manual (DCAAM) Chapter 5-202, Preaward Survey of a Prospective Contractor's Accounting System and Standard Form (SF) 1408. Also identify any deviations from Offeror’s standard procedures in preparing this proposal. Any Offeror’s accounting systems not approved by DCAA, DCMA, or an equivalent commercial Certified Public Accountant (CPA) will be ineligible for award.

The Offeror shall provide the following DCAA information:

· Completed Pre-Award Survey of Prospective Contractor Accounting System Checklist, Attachment 7.

· DCAA point of contact with a current e-mail address or phone number.

· DCAA Provisional Billing Rate Approval Letter.

· DCAA Final Billing Rate Approval Letter.

· DCAA/DCMA approved Forward Pricing Rate Agreement/Recommendation.

· DCAA audit and findings that the contractor’s accounting system is adequate for determining costs applicable to cost-reimbursable awards; or,

· Certification from an independent CPA that accounting system complies with DCAA requirements.

L.5.4 COST OR PRICING INFORMATION AND SUPPORTING DOCUMENTATION

The offeror shall provide a detailed cost proposal for accomplishing the requirements of Task Orders 1, 2, and 3 that is consistent with the technical approach provided in Volume II. The cost proposal shall delineate labor hours, labor categories, indirect costs, (to include base and percentage used in calculation), other direct costs, G&A, and fee. All dollar amounts shall be rounded to the nearest dollar. The cost proposal shall be itemized by Task Order. In addition, each Task Order shall be costed by Base period and Option period. Task Orders 1, 2, and 3 will be Cost Plus Fixed Fee (CPFF).

If subcontractors are utilized, the offeror shall provide the results of the analysis conducted by the offeror (prime contractor) establishing reasonableness of proposed subcontract prices (reference FAR 15.404-3(b) and (c)).

L.5.5 PROFIT OR FEE

Offerors shall include their proposed fee (dollar amount and percentage) for each Task Order and shall specify the base upon which the fee percentage is applied. Per DTRA Clause 252.216-9005, there will be no profit or fee on travel and ODCs.

L.5.6. TASK ORDER PRICING ASSUMPTIONS

For purposes of preparing a cost proposal, offerors shall make the following assumptions:

The baseline travel amounts are included in the table below by year of the contract. The travel amounts below cover only the travel expenses (per diem, air fare, car rental, hotel, etc.) Applicable burdens are not included and therefore shall be applied to the amounts provided in the table. Offerors are reminded that Section G, DTRA clause 252.216-9005, establishes travel as a non-fee bearing cost element. No fee shall be applied to travel, ODCs, and Mission Essential Hardware/Software amounts.

NTE Amounts*

*NOTE: Any indirect rates associated with travel shall be applied by the offeror to the base-line amounts above to arrive at the total proposed travel cost. The indirect rates applied shall be clearly delineated in the proposal.

End of Section L

(End of Summary of Changes) image1.wmf