Draft RFP Sections L M 8-27-24_Final NHF.docx

Section L - Instructions, Conditions and Instructions to Offerors

FAR 52.252-1 Solicitation Provisions Incorporated by Reference FEB 1998

This solicitation incorporates one or more solicitation provisions by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. The Offeror is cautioned that the listed provisions may include blocks that must be completed by the Offeror and submitted with its quotation or offer. In lieu of submitting the full text of those provisions, the Offeror may identify the provision by paragraph identifier and provide the appropriate information with its quotation or offer. Also, the full text of a solicitation provision may be accessed electronically at this address:

Federal Acquisition Regulation https://www.acquisition.gov/far/part-52

Defense Federal Acquisition Regulation Supplement https://www.acquisition.gov/dfars/part-252-solicitation-provisions-and-contract-clauses

End of Provisions

Data Other Than Certified Cost or Pricing Data

Evaluation

The Government contemplates award of an indefinite-delivery/indefinite-quantity (IDIQ) contract with Cost-Plus-Fixed-Fee (CPFF), Cost Reimbursement (COST) and Firm-Fixed-Price (FFP) task orders.

FAR 52.233-2 Service of Protest SEPT 2006

The Government plans to award a single-award Indefinite Delivery/Indefinite Quantity (ID/IQ) contract for Contractor support for programmatic assistance, exercise support, analytic subject matter expertise support, assessments, and execution of information-based threats and countermeasures for the Strategic Integration (SI) Directorate. The Government also intends to award three (3) Sample Task Orders. The ordering period will contain a one (1) year base period with four (4) 1-year optional ordering periods for a total of five (5) years. Additionally, Task Orders issued under this ID/IQ may be for a duration of twelve (12) months past the last ordering date of the IDIQ contract. The minimum order guarantee is $1,000,000.00. The aggregate total for all SI contracts awarded under this ID/IQ shall not exceed $92,400,000.00.

L.1.1 Specifications

The North American Industry Classification System (NAICS) for this acquisition is 541990 - All other Professional, Scientific and Technical Services, the small business size standard is $19.5M. The Product Service Code (PSC) is R408 – Program Management Support.

The location of work to be performed will be in the United States and its outlying areas and has the potential for work to be performed in any country throughout the world. Refer to the Performance Work Statement (PWS).

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.

CONTENTS

L.1. General Instructions to Offerors L.2. Volume I – Proposal Documentation L.3. Volume II – Factor 1: Mission Capability L.4. Volume III – Factor 1(c): Technical Approach L.5. Volume IV – Factor 2: Past Performance L.6. Volume V – Factor 3: Cost/Price

L.1.2 Communication

The primary point of contact for this draft solicitation is the Contract Specialist (CS), Miss Michelle Etienne; and the alternate is the Contracting Officer (CO), Mrs. Rorri Waters. Both can be reached via using the credentials below.

Defense Threat Reduction Agency Attn: DTRA Contracts, AL-ACB Email: dtra.belvoir.al.mbx.al-acb-si-a-and-as-proposal-submission-fy24-@mail.mil

All questions, concerns, or requests for information (RFIs) or clarification shall be submitted electronically through the mail portal at dtra.belvoir.al.mbx.al-acb-si-a-and-as-proposal-submission-fy24-@mail.mil no later than 12 PM EST on 11 September, 2024. The Government may choose not to respond to questions received after this date and time. Offerors are encouraged NOT to wait until the last few days to submit RFI’s, to provide adequate time to research and respond to queries while staying on the procurement schedule. All emails shall be clearly labeled in the subject line of the email with the Request for Proposal (RFP) Number HDTRA1-24-R-0057.

When submitting questions, Offerors shall clearly identify the specific section of the solicitation to which each question relates, and reference should be made to the solicitation section heading, page number, 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:

Heading, page number, paragraph, etc.

Responses to submitted questions will be provided to all Offerors via Contract Opportunities at https://beta.sam.gov/ and the Solicitation Module at https://piee.eb.mil/sol/xhtml/unauth/index.xhtml.

L.1.3 Pre-Proposal Submission All potential Offerors must submit documentation that details how they are currently working within DTRA, to determine if an Organizational Conflict of Interest (OCI) exists, if they were to be awarded this contract. All potential Offerors must provide this OCI Disclosure Document to the POCs via email no later than 11 September 2024. Information should include, but is not limited to:

L.1.3.1 Offerors must disclose all current contracts that they are performing, which will/may have provided them an unfair competitive advantage – prior to the submission of Offers. Offerors shall submit the following information: a detailed organizational chart that depicts the hierarchal structure of the Offeror’s (and subcontractors) organization on each contract, identify the associated business units that provide non-A&AS support to DTRA, provide a brief description of those activities for the prime/subcontractors, and provide a list of all active and completed DTRA contracts (performed within the last two (2) years) as a prime contractors or subcontract.

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 through appropriate means in order for the Offeror to be eligible for award. This will be addressed in the OCI Avoidance Plan, which is to be submitted with the Offers in Volume II.

L.1.4 Errors, Omissions, or Ambiguities If an Offeror believes the solicitation contains an error, omission, ambiguity, or is otherwise unsound, the Offeror shall immediately notify the CS and CO in writing with supporting rationale at any point prior to the proposal submission deadline.

L.1.5 Requirement Discrepancies If an Offeror believes that the requirements in these instructions contain errors, omissions, or are otherwise unsound; the Offeror shall immediately notify the CS/CO in writing with supporting rationale.

L.1.6 Partnering Agreements/Joint Venture The Offeror may consist of two (2) or more firms that execute a binding Partnering Agreement to perform this requirement. The Partnership will be considered the “Offeror” when there is a signed Partnering Agreement binding both parties to performance under this contract, should it be awarded to the partnering firms. The Partnership or Joint Venture should be a registered in SAM.

L.1.7 Teaming Arrangements The Offeror and its first-tier subcontractor(s) will be considered a “Team” when there is a signed Teaming arrangement or Letter(s) of Commitment unconditionally binding both parties to performance under this contract, should it be awarded to the Offeror. Each entity must have a current registration in SAM. In the absence of one or the other of these documents, the Offeror and its first-tier subcontractor(s) are not considered a “Team” and will not be evaluated as such.

L.1.8 Proposal Format The Offeror shall prepare the proposal as set forth in the Proposal Organization Table 1-2 below. The titles and contents of the volumes, as well as the page limitations and number of required copies shall be as specified in the table. In the event that the table conflicts with the detailed instructions in the paragraphs that follow, the detailed instructions shall take precedence. Offerors are encouraged to resolve any perceived inconsistencies with the solicitation instructions by submitting any applicable questions within the RFP open question period.

TABLE 1-2 – PROPOSAL ORGANIZATION

I

PROPOSAL DOCUMENTATION

1 – Electronic

Unlimited

II

FACTOR 1: MISSION CAPABILITY

40 Total

Subfactor A: Corporate Experience

1) Experience Narrative

2) Organization Chart

6 Total (not including charts/graphics)

Subfactor B: Management Approach

1) Team Description (incl. Organization Structure)

2) Staffing Plan (Labor Matrix, Recruitment and Retention)

3) Surge Support

4) Transition Approach

5) Key Personnel Resumes* 1 – Electronic

(page limit does not include resumes, charts/graphics)

III

Subfactor C: Technical Approach

1) Sample Task Order 1 (PL)

2) Sample Task Order 2 (ST)

3) Sample Task Order 3 (IRO) 1 – Electronic

21 - Not to exceed 7 pages per Task Orders (TOs) (page limit does not include QASP, and PRS documents)

IV

FACTOR 2: PAST PERFORMANCE

1) CPARS

2) PPQs (Attachment L- 1)

3) eSRSs/ISRs/DCMA Subcontracting Audits (Up to 3)

1 – Electronic

(no page limit)

V

FACTOR 3: COST/PRICE

1) Cost/Price Narrative

2) Signed SF Form 33

3) Sample Task Order 1 (PL)

4) Sample Task Order 2 (ST)

5) Sample Task Order 3 (IRO)

PLEASE NOTE THE REQUIREMENTS FOR SUBMISSION OF PROPOSALS ARE CONTAINED IN FAR 52.215-1.

Final Proposal Revisions (FPR’s): Offerors are not limited in the items they chose to revise or modify in their FPR submission. Any and all revisions will be reviewed for strengths, weaknesses and deficiencies in accordance with the evaluation guidelines. FPR's will be submitted in two (2) versions:

· Version 1 will contain a line in/line out revision to any items the Offeror seeks to address/modify within their proposal.

· Version 2 shall be a clean copy of the line in/line out revisions. Page counts for the clean copy shall remain in compliance with the existing page counts posted within this section.

FPR's shall contain a summary of changes as part of Volume I Proposal Documentation - the page limit for this summary of changes shall not exceed three (3) pages.

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

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

· Address the factors, subfactors, and their related elements as listed in Section L 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 to address how the Offeror intends to meet the requirements.

· 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.8.2 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 one electronic copy of all unsuccessful proposals.

In the event discussions are held, final proposals shall constitute a legally binding offer for 90 days from the closing date of submission.

L.1.8.3 Appearance of Submissions Elaborate brochures or documentation, detailed artwork, or other embellishments are unnecessary and are not desired. Proposals will be submitted electronically only. Paper copies of the proposal will not be accepted. No models, mockups, or videotapes will be accepted.

L.1.8.4 Page Size Pages shall be 8.5 x 11 inches, not including foldouts. Format the pages using full page, do not use two columns. Except for the lettering that is within a graphic, the font size shall be Times New Roman and no less than twelve (10) points. Lettering within tables, charts, graphs, and figures shall be no smaller than eight (8) points. Margins on all four (4) edges of each sheet will be at least one (1) inch.

Proprietary statements, security markings, and page numbers may 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 also apply to responses to Final Proposal Revisions (FPRs).

L.1.8.5 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 also be deleted from the electronic copy of the proposal. All pages shall be standard size (8.5 x 11), and each page counts towards the page limit. All foldouts shall be single sided. 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.8.6 Pages Required but not Counted Each page shall be counted except the following (or counted as listed):

· Cover pages

· RFP cross-reference matrix

· Partnering Arrangements

· Teaming arrangements

· Letters of commitment

· Past performance consent letters

· Past Performance Questionnaires

· ISRs and/or DCMA Subcontracting Audits

· Past performance questionnaire Point of Contact List

· Client Authorization Letters

· Tables of Contents

· Glossaries

· Lists of figures, tables, or drawings

· Tabs

· Dividers

· Blank pages

· Labor Category Table

· Organization Chart

· Exceptions to terms and conditions

· Resumes for Key Personnel (limited to 2 pages per resume)

· Government Product/Service Accessibility Template (GPAT)

· Quality Assurance Surveillance Plan (QASP)

· Performance Requirement Summary (PRS) L.1.8.7 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. Table of Contents and Tabs are not counted.

L.1.8.8 Foldouts Legible tables, charts, graphs, diagrams, schematics, and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, design drawings, plans, etc.

These displays shall be uncomplicated, legible, and shall not exceed 11 x 17 inches in size. Foldout pages shall fold entirely within the volume. Each printed side of a foldout will count as one page unless the foldout is being used to address one of the exceptions to page limitations listed in L.1.8. Foldout pages may only be used for large tables, charts, graphs, diagrams, and schematics; not for pages of text. Since electronic copies of proposals are being requested, a “foldout” in this case refers to a larger landscape orientation page within the PDF document. For tables, charts, graphs, and figures, the font shall be no smaller than 8 points. All information (except documentation numbers, classification markings, and page numbers) shall be contained within an image area of 9 x 15-1/2 inches.

· All text must be searchable

· Limit colors to 256 colors at 1280 x 1024 resolution; avoid color gradients

· Keep embedded graphics as simple as possible; large graphic files are discouraged

· Minimize the use of scanned images (except for Adobe Acrobat requirements)

· Use of self-extracting archive files (e.g., ZIP files) is allowed

· No linking to resources outside the electronic document L.1.9.2 Volume Designation/Minimum Cross-Reference Each volume shall be written to the greatest extent possible on a stand-alone basis, so that its contents may be evaluated with a minimum of cross-referencing to other volumes of the proposal. Information required for proposal evaluation that is not found in its designated volume will be assumed to have been omitted from the proposal. Teaming Arrangements, Letters of Commitment, Socio-Economic Commitment information and Organizational Conflicts of Interest assertions submitted in Volume I may be cross-referenced in other volumes.

L.1.9.3 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. All acronyms shall be spelled out in the text the first time they are used in each volume.

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

L.1.10.2 Post-award Debriefings Offerors may request a debriefing by providing a written request to the CS/CO. The CS/CO will notify Offerors of the source selection decision within three (3) calendar days after award. Offerors that desire a debriefing must request one in writing within three (3) calendar days after receipt of the CS/CO notification. To the maximum extent practicable, debriefings will be conducted within five (5) calendar days after the Offeror’s request.

L.2. VOLUME I – PROPOSAL DOCUMENTATION

Volume I consist of the Offeror or Teaming/Partnering Arrangement (also referred to as the Offeror) that is proposing to enter into a contract with DTRA to perform the desired A&AS work. Also enter all of the information the Government will require to prepare the contract document and supporting file. All Offerors must be actively registered in the SAM database at the time of Offer submission and award.

L.2.1 Volume I Organization The volume shall be organized according to the following outline:

· Table of Contents

· List of Tables and Drawings

· Glossary

· Documents listed in Section L.2.1 to L.2.9 The Cover Page of each volume should include, but is not limited to:

· Volume Number

· Solicitation Name and Number

· Offeror’s (Prime Contractor’s) name

· Full Business Address

· Point of Contact with Authority to commit the organization

· Unique Entity Identification (UEI) Number from SAM.gov

· Cage Code

· Size status, socio-economic category – with proof of active designation

· Signed Partnering or Teaming documentation, as applicable.

L.2.2 Authorized Offeror Personnel Provide the name, title, telephone number, fax number, and e-mail address of the Company and Point of Contact regarding decisions made with respect to the Offeror’s proposal and who can obligate the Offeror contractually. The aforementioned information also applies to the prime contractor and major subcontractors/teaming partners for which there is a teaming arrangement. Also identify those individuals authorized to negotiate with the Government.

L.2.3 Government Offices Provide the mailing address, telephone and fax numbers, and facility codes for the cognizant Office of Defense Contract Audit Agency (DCAA), Defense Contract Management Agency (DCMA) and/or the Government Paying Office; along with the respective name, telephone and e-mail address for the Administrative Contracting Officer (ACO).

L.2.4 Company Division Address, Identifying Codes and Applicable Designations Provide the company’s/division’s street address, county, and facility code; CAGE Code; Unique Entity Identification (ID); Taxpayer Identification Number (TIN), size of business (large or small); and labor surplus area designation for the prime contractor and all subcontractors/teaming partners.

L.2.5 Teaming Arrangements and/or Letters of Commitment Provide all Teaming Arrangements and/or Letters of Commitment accompanied by appropriate explanation of the legal relationship. Paragraph L.1.7 applies.

L.2.6 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. The Offeror shall complete the contractor information blocks on the DD254.

L.2.7 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 provided in the System for Award Management (SAM) www.sam.gov.

L.2.8 Preaward Organizational Conflicts of Interest (OCI’s)

a. The Government has determined that this contract may give rise to potential conflicts of interest. The successful Offeror for this requirement will have unique access, beyond that which is typically afforded to commercial and academic entities, to the SI Directorate. The successful Offeror will be exposed to Government-sensitive and contractor-sensitive / proprietary data as well as to Government employees, equipment, installations and property. The awardee will have access to information that could potentially provide an unfair competitive advantage for future contracts supporting DTRA.

b. Because of this unique access, the Government has determined that that the OCI mitigation plan strategy is the best method of ensuring procurement integrity for this requirement.

c. 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 OCI 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 or a proposed contractor or consultant has a possible OCI.

d. To implement the requirements of clause 252.209-9000 and H.1 of this contract, each Offeror also must include an OCI Avoidance Plan in Volume I of its proposal describing the Offeror’s approach to ensuring the objectivity of its Advisory and Assistance Services, prevention of unfair competitive advantage, and protection of contractor proprietary and Government sensitive information. The OCI Avoidance Plan shall also ensure that an advantage is not gained by any relationship the Offeror may have with current performers of any DTRA Programs. The approved OCI Avoidance Plan will be incorporated into the resultant contract. At a minimum, the Avoidance Plan shall address the following elements:

· Definition of terms used

· Identify the lead person(s) responsible for OCI compliance within the company, and his/her role within the company

· Organizational, physical and financial separation (such as corporate firewalls for business units, etc.)

· Processes and procedures for identifying OCIs (this includes processes for notification and review of Potential bids by any business unit within the proposed team to identify potential OCI issues)

· Processes and procedures for corporate review and adjudication of OCIs in a timely manner (this includes discussion of potential types of OCI situations and mitigation techniques for resolving them, and the extent of insight provided to DTRA during the OCI adjudication process)

· Access to, use and protection of government sensitive and proprietary information (hardcopy and electronic)

· Personnel assignments in and transitions out of firewalled units and separation from the company

· Prime Offeror management, monitoring and enforcement of OCI requirements at the subcontractor level

· OCI training/awareness for employees and subcontractors

· Nondisclosure agreements

· Contractor self-audits

· DTRA access to records

· Reporting and remedies for accidental and intentional OCIs.

· Mitigation approach for potential OCIs or perceived OCIs for current performer contracts in which SI Directorate is the requiring and/or funding activity (i.e., contracts awarded prior to the RFP response date)

f. The Contracting Officer may require further relevant information from an Offeror and may, at his/her discretion, permit an Offeror to clarify errors or omissions in relevant information or in a statement required by (a) above. Refusal to provide a statement required by (a) 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.

g. 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.

L.2.8.1 OCI Avoidance Plan. It has been determined that the best Organizational Conflict of Interest (OCI) plan for this requirement is one of Avoidance. Offerors will submit their proposed OCI Avoidance Plan for consideration. Offerors will list the participants of their Team, identify any OCI Disclosures that may present a conflict of interest; and propose how they plan to completely avoid any OCI that may be present. Offerors are encouraged to be detailed and specific in their proposed plan. The plan may be revised to meet Government specifications and/or standards, prior to acceptance.

Offerors shall submit the following information in the Plan:

(1) A detailed organizational chart that depicts the hierarchal structure of the Offeror’s (and subcontractors’) organization from the “top down,” which identifies the various business units and the interrelationships among the various business units. The chart should depict where the business unit(s) which will be responsible for A&AS support fit within the hierarchal structure.

(2) Identification of the business units (other than the unit(s) that will provide A&AS support) that provide non-A&AS products and/or services to DTRA, and a brief description of those activities for the prime Offeror and its subcontractors and their affiliates.

(3) A list of active DTRA contracts and orders (and contracts/orders completed within the last two years), performed either as a prime or a subcontractor. The list should include active and completed contracts for the prime Offeror and its proposed subcontractors and consultants. This includes contracts/orders issued by another Government agency on behalf of DTRA, where DTRA provides funding plus primary oversight, technical direction and performance evaluation of for the contracted effort. The list must identify the prime contract number, the name of the prime contractor (if the firm is/was a subcontractor or consultant), and the DTRA directorate/branch or other Government agency office responsible for program management of the contract.

L.2.9 Section 508 Compliance Requirements for accessibility based on Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. 794d) are determined to be relevant for this Strategic Integration (SI) Directorate Advisory & Assistance Support Service (A&AS) requirement at the Defense Threat Reduction Agency (DTRA). It is the Offeror’s responsibility to ensure that services and products will be compliant with 36 CFR part 1194 and that Electronic and Information Technology (EIT) deliverables meet at least those information, documentation, and support requirements identified as applicable in the attached Government Product/Service Accessibility Template (GPAT). Offerors shall submit adequate information to document their responsiveness to the Section 508 requirements (i.e. a completed GPAT or VPAT or equivalent).

L.3. VOLUME II – FACTOR I - MISSION CAPABILITY

L.3.1 General The Mission Capability Volume is divided into three (3) Subfactors that require the Offeror to describe their capability to satisfy the technical 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. Specific 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 and personnel qualifications. 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 subfactors and their related elements defined in Section M, “Evaluation for Award.” Provide complete information as requested or, provide as specifically as possible - the actual methodology that would be used by the Offeror for accomplishing and satisfying these subfactors. 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 II Organization Each volume shall be organized according to the following outline:

a. Table of Contents

b. List of Figures, Tables and Drawings

c. Glossary / Acronym List

d. RFP Cross-Reference Matrix

e. Mission Capability

· Subfactor A – Corporate Experience

· Experience Narrative (as a Prime for Similar Projects)

· Organization Structure (Including fully executed Partnering Agreements)

· Subfactor B - Management Approach

· Team Description and Org Chart (including executed Teaming Agreements, Commitment Letters, and subcontractors)

· Staffing Plan (including Recruitment, Retention and Surge Support Plan)

· Labor Matrix (include lines of authority, responsibility, participation, and management of subcontractors)

· Transition Approach

· Subfactor C - Technical Approach

· Sample Task Order 1 - PL

· Sample Task Order 2 - ST

· Sample Task Order 3 – IRO

L.3.3 Format and Specific Content The Offeror shall describe, in narrative form, the Offeror’s proposed approach to meeting the requirements of each Mission Capability subfactor 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.4 RFP Cross-Reference Matrix (RCRM) The Offeror shall complete 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

L.3.5.2 Organization Structure (Including fully executed Partnering Agreements and/or Teaming Arrangements). Clearly show the organization structure of the company that is proposing on this work. It should show all parent and subordinate company associations, which may/will be used to demonstrate experience.

1. Provide a thorough description of the management structure and division of responsibility that demonstrates the ability to effectively control the full range of support services.

1. Demonstrate the ability to effectively utilize its workforce to begin accomplishing the entire scope of the effort in accordance with the PWS.

1. Demonstrate the ability to effectively recruit, hire, and retain a highly qualified and capable workforce that can accomplish the requirements of the PWS.

1. To allow flexible assignment of personnel as well as the rapid reassignment of personnel to satisfy multiple evolving tasks.

1. Demonstrate the ability to provide a comprehensive approach to monitoring and assessing contract performance strengths and weaknesses, in order to provide internal recognition of areas for improvement.

1. Demonstrate the ability to effectively provide a training and education program to be used to ensure minimum requirements of various disciplines are fulfilled and maintained. The Offeror demonstrates its training and education plan is tied to retention and continual benefit to the contractor during the performance of the contract.

1. Demonstrate the ability to effectively measure and evaluate its execution of the PWS; to plan, track and forecast success in its mission, and in anticipation of contractor’s future work needs as outlined in the PWS. The Offeror’s plan must clearly define the types and nature of the metrics to be used, the nature of the inferential data to be collected and processed, and the plan for utilizing these for continual process improvement.

1. Demonstrate the ability to support all elements of the PWS at full capacity. The Offeror’s Transition Approach shall include a 30-day transition period. The Transition Approach should be both effective and efficient.

1. The Offeror demonstrates the ability to ramp up activities and identify personnel available to support initiation of Task Orders for all of the departments simultaneously and maintain performance and support throughout the 5-year ordering period.

1. Demonstrate the ability to meet all security and clearance requirements prior to Task Order execution.

1. Propose key personnel for Directorate and Departments/offices who meet or exceed requirements for those key personnel positions.

1. Demonstrate responsiveness to Section 508 requirements.

L.3.6.2 Staffing Plan and Surge Support. The Offeror shall also provide a detailed Staffing Plan that includes a Recruitment, Retention, and Surge Support Plan describing a thorough, complete, and effective approach to manage the contract requirements of the PWS, to include a plan of action for replacement personnel. The Staffing Plan should include how the Offeror will:

· Acquire and retain any additional workforce needed to be capable accomplishing the requirements of the SOO as the focus of the mission changes globally.

· Utilize methods and tools to recruit and retain qualified employees.

· Utilize an approach to technical assignment/reassignment of personnel, to include short notice actions, to satisfy multiple and evolving requirements.

L.3.6.3 Transition Plan. Offerors will describe how they will transition the work from the old vendor to the new vendor; during entry and exit from this contract. Approaches that show a seamless, comprehensive and complete transition in the smallest amount of time may be rated higher. All aspects of the transition approach should be addressed to include, but not limited to:

· How the incoming contractor will be organized structurally during the individual task order transition period

· What personnel specialties will be required during the individual task order transition period.

· What the incoming contractor identifies as their critical learning and action processes.

· Equipment, documentation, records and information technology systems the incoming contractor will need to coordinate with the incumbent during the transition period.

· Physical infrastructure.

· How the incoming contractor intends to comply with DTRA entrance/exit and information technology security procedures during the individual task order transition period.

· Schedule for transition and integration.

· Upon end of transition period, utilize a workforce capable of immediately accomplishing all the requirements in the SOO in accordance with the 3 Sample Performance Work Statements (PWSs).

L.4. VOLUME III – FACTOR I - SUBFACTOR C: TECHNICAL APPROACH

The technical approach submittal shall include three (3) tabs, one (1) for each SI Office/Department’s Sample Task Order. The Offeror shall submit the following for each Task Order: a comprehensive technical approach that outlines how they propose to meet the requirements outlined in the Task Order Statement of Objectives (SOO). The submission shall include a proposed Performance Work Statement (PWS) for each Task Order, the Key Personnel Positions or equivalent in at least each of the Sample Task Orders (with Resumes), the proposed Staffing Plan, and any innovative approaches to completing the required work over the period of performance. The Technical Approach recommendations should demonstrate that the Offeror has a clear technical understanding of each of the SI organizations and offers a proposal that is responsive to meeting each aspect of the corresponding technical requirements of each Office/Department’s Statement of Objectives (SOO).

The Offeror shall identify Task Order Key Personnel or equivalent and provide detailed resumes by position and qualifications. At a minimum, the Key Personnel Resumes shall contain the following information:

· Identification and Proposed Position (Name of key personnel, title of position, narrative position description)

· Summary of Professional Experience (A brief description of relevant education, experience and training that makes key person particularly suited for the proposed position)

· Education and Training (Institution, City, State, Degree, Month, Year, Field of Study)

· Current and Past Positions and Employment (Years, Position or Job Title, Institution, City, State and Narrative Description including responsibilities and relevance)

· Qualifications cross reference to the applicable Disciplines and Skill sets of the SOO.

In response to each attached SOO, the Offeror shall provide the A&AS support scope for these efforts as summarized below:

· Draft a proposed Performance Work Statement (PWS) that outlines how the vendor will provide services to DTRA for this specific work element.

· Propose staffing levels and types, to include hours, background experience and educational requirements.

· Provide management approach for each of the Sample Task Orders.

· Provide a Performance Requirements Summary that will identify each performance requirement, applicable PWS section, performance standard and acceptable quality level (AQL), method of surveillance, and any applicable remedies

· Provide Deliverables that will be provided, and the timeliness and quality standard.

· Provide a proposed Quality Assurance Plan that will outline the areas of contractor performance that will be monitored, how the monitoring will be accomplished, the metrics that will be used, who will collect the data, and how the findings will be recorded

The Offeror shall provide a matrix of all proposed subcontractors/team members and the specific areas within the IDIQ, including Sample Task Order 1, 2, and 3; for which they will be utilized. Letters and Agreements demonstrated firm commitments by Subcontractors may be rated higher.

Offerors shall also provide an approximate percentage of effort, based on overall contract cost ceiling, that each subcontractor/team member will contribute to the overall effort. The overall effort shall consist of the overall PWS, including Sample Task Order 1, 2, and 3. This information will be utilized to determine relevancy for the subcontract references.

In addition, the Offeror shall submit a consent letter, executed by each subcontractor/teaming 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.1 Tab 1 – Technical Approach Sample Task Order 1 (PL) The Strategic Integration (SI) Directorate focuses the Agency’s operations, activities, and investments in a way that maximizes their cumulative effect in support of all of our warfighting customers. Strategic Plans and Exercises (SI-PL) assists DTRA senior leadership in their decisions by providing Countering Weapons of Mass Destruction (CWMD) focused expertise. SI-PL provides regional and global planning/exercise support to maximize strategic alignment of DTRA Combat Support Agency and Defense Agency capabilities against the needs of the current operating environment in planning, exercises, doctrine, strategy, and opportunity analysis for the Agency, Combatant Commands (CCMD), and other DoD components, in coordination with interagency and international partners, while enhancing mission readiness through collective staff training. The work effort that supports the Strategic Plans and Exercises Department is outlined in the Statement of Objectives (SOO) for PL (see Attachment 2).

L.4.2 Tab 2 - Technical Approach Sample Task Order 2 (ST) The Strategic Trends Office, SI-ST, underneath the Strategic Integration Directorate, advises senior leaders and workforce personnel on actions to shape U.S. and ally/partner responses to probable future WMD and emerging technology threats. Strategic Trends develops analysis and reporting with specific interest in advising the Agency, DoD, and CWMD community on recommended courses of action to combat WMD and emerging technology threats. Analysis is centered on developing concepts/ideas of future adversarial WMD development and use that helps to orient and spur action in the combatting WMD community. Tipping/cuing occurs from a number of internal and external sources to allow for a holistic view of the future threat. Analysis seeks to combine disparate pieces of information to inform and shape their reporting – anticipating adversarial use of CBRN and technology that could be synergistic or novel. Staff that is assigned to this effort will integrate concepts/ideas from numerous areas – including our funded research and events held with the community and DoD. The work effort that supports the Strategic Trends Office is outlined in the Statement of Objectives (SOO) for ST (see Attachment 3).

L.4.3 Tab 3 - Technical Approach Sample Task Order 3 (IRO) The SI Directorate focuses the Agency’s operations, activities and investments in a way that maximizes their cumulative effect in support of all our warfighting customers. The Information Resilience Office (IRO) assists DTRA by enduring DTRA and its partners are resilient in the information environment, connecting messaging to action to achieve integrated deterrence.