PMO Section LM_ver1-27-20_final to post.docx

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 a Cost Plus Fixed Fee (CPFF) contract resulting from this solicitation.

(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:

Ms. Mary Kay Chase Contracting Officer Defense Threat Reduction Agency Contracts-Information Operations Branch, AL-ACS Phone: (571) 616-6159 Email: dtra.belvoir.al.mbx.dtra-rd-services@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.

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/these address(es):

https://www.acquisition.gov/content/regulations

252.204-9000 NOTICE TO POTENTIAL OFFERORS-OFFICIAL DTRA ADDRESSES IN THE NATIONAL CAPITAL REGION (NCR)

1. Offerors are responsible for submitting proposals and any proposal modifications/revisions to the designated office by the date and time specified in the solicitation. For the purposes of this clause, the “designated office” is the office appearing in the attention line of the mailing addresses in paragraph 2 below. Proposals received after this exact time will NOT be considered unless it meets one of the exceptions stated in Federal Acquisitions Regulation (FAR)52.215-1(c)(3).

2. DTRA has 2 official mailing addresses in the NCR. Due to heightened security measures, hand-carried proposals cannot be accepted, therefore offerors are to select one address below based on the method of mailing.

a. The official United States Postal Service (USPS) mailing address for DTRA:

Defense Threat Reduction Agency Attn: AL-ACS/Mary Kay Chase* 8725 John J. Kingman Rd. Stop 6201 Fort Belvoir, VA 22060-6201

b. DTRA cannot accept packages delivered via commercial express and ground carrier to any address other than the one listed below. For all incoming packages to DTRA activities in the Washington DC area (this includes packages sent via Federal Express, DHL, Airborne, UPS and other commercial carriers), use the following address:

Defense Threat Reduction Agency Attn: AL-ACS/Mary Kay Chase* 6200 Meade Road Fort Belvoir, VA 22060-5264

Note: This address shall also be used in all contracts for delivery of supplies/materials.

3. If mailing via USPS, offerors are cautioned to allow 1-2 days for processing and delivery of all proposal information to the designated office after it has been received at the DTRA mailroom. This mail processing delay is unavoidable, so offerors are encouraged to carefully select the mailing method to ensure timely receipt of proposals.

* Mail sent without an office symbol may be misdirected within DTRA. Please use the most current office symbol assigned. If an office symbol changes during the term of this contract, the contracting officer may advise of this change via letter in lieu of a contract modification.

End of Provision

L.1.0 GENERAL INSTRUCTIONS TO OFFERORS

L1.1 GENERAL INFORMATION

L.1.1.1 Point of Contact

Offerors are instructed to address all questions or concerns regarding this solicitation via email to dtra.belvoir.al.mbx.dtra-rd-services@mail.mil with the subject line “Questions Concerning HDTRA1-20-R-0002.” Questions regarding this solicitation must be received no later than 4:00 PM, EST, 18 February. Responses will be posted to betaSAM (www.betaSAM.gov). The points of contact for this acquisition are listed below:

The Contract Specialist (CS) for this acquisition is:

Mr. Ronald Laliberte Defense Threat Reduction Agency Contracts-Information Operations Branch, AL-ACS Phone: Will be provided at time of award Email: dtra.belvoir.al.mbx.dtra-rd-services@mail.mil

The Contracting Officer (KO) for this acquisition is:

Ms. Mary Kay Chase Defense Threat Reduction Agency Contracts-Information Operations Branch, AL-ACS Phone: Will be provided at time of award Email: dtra.belvoir.al.mbx.dtra-rd-services@mail.mil

All questions, concerns, or requests for clarification for this RFP shall be submitted electronically to dtra.belvoir.al.mbx.dtra-rd-services@mail.mil no later than 4:00 PM, EST, 18 February, 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 Questions Concerning HDTRA1-20-R-0002. 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 beta.SAM at https://www.beta.sam.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 Preaward 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 contracting officer within three (3) calendar 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. Refer to FAR 15.505 for further instruction.

L.1.1.2.2 Post-award Debriefings

Offerors may request a debriefing by providing a written request to the KO. The KO 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 KO notification. To the maximum extent practicable, debriefings will be conducted within five (5) calendar days after the Offeror’s request to the maximum extent practicable.

L.1.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 ORGANIZATION/DISTRIBUTION/NUMBER OF COPIES/PAGE LIMITS

The Offeror shall prepare the proposal as set forth in the Proposal Organization Table L.1.2 below. The titles and contents of the volumes, as well as the page limitations 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.

Table L.1.2 – Proposal Organization

(electronic) Unlimited

(electronic)

Sub-Factor A – Management Approach

Incoming Management Plan

Sub-Factor B - Technical Approach

· Key Personnel Resumes

3 pages per resume

· Sample Resumes

3 pages per resume

· Sample Challenge/Task

III

Description Of Team

Present And Past Performance References

5 pages per reference (Narrative and Attachment L-1)

Organizational Change History

Unlimited

1. a. The “ORIGINAL” copy of Volumes I, II, III, and IV of the proposal shall be provided in CD-ROMs. Each volume shall have a cover sheet, clearly marked as volume number, Offeror's name, solicitation title, solicitation number, and proposal date.

b. The electronic copy of each volume shall be submitted in accordance with Paragraph L.1.3.7.

c All proposal volumes shall be provided by mail or commercial express or ground carrier only as prescribed in above DTRA Clause 252.204-9000, “Notice to Potential Offerors – Official DTRA Addresses in the National Capital Region (NCR)”.

d. Present and Past Performance Questionnaires (Attachment L-2) shall be e-mailed in PDF to the team e-mail address shown in Paragraph L.1.1.1, dtra.belvoir.al.mbx.dtra-rd-services@mail.mil.

e. Please note the requirements for submission of proposals contained in FAR 52.215-1 (incorporated by reference as described earlier).

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, subfactors, 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 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.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 one copy of all unsuccessful proposals. Unless the Offeror requests otherwise, the Government will destroy extra copies of 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 shall be submitted in electronic format in CD-ROMs.

1. No models, mockups, or other media 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

· teaming arrangements

· letters of commitment

· past performance consent letters

· client authorization letters

· tables of contents

· revision matrix

· glossaries of abbreviations and acronyms

· lists of figures, tables, or drawings

· Performance Guarantees

· blank pages

L.1.3.6 Indexing

Each volume shall contain a more detailed table of contents to delineate the sections within that volume.

L.1.3.7 Electronic Delivery

a. Each volume shall be submitted on individual CD-ROM(s) in a protective sleeve or case. Each CD-ROM and protective sleeve or case shall be clearly marked as to volume number, title, RFP identification, and the Offeror’s name. Offerors are responsible for ensuring electronic submissions are virus-free.

b. Submit an electronic copy of each volume compatible with the following available Government equipment and software products:

- Adobe Acrobat Reader 2017 (or earlier compatable)

- Microsoft Office Suite (Word, Excel, PowerPoint, and Project) 2016 (or earlier compatable)*

*All cost information, with the exception of the cost narrative, must lend itself to review and analysis by the Government and must be submitted in Microsoft Excel format. Offerors shall include formulas and working links (within the workbook), and refrain from hidden columns and field protection (lock), to the maximum extent practicable.

Note:

The electronic copy shall be in Adobe Acrobat (except for Microsoft Excel) portable document file (pdf) searchable text format

c. Electronic files shall be clearly identified for each volume, section, item, etc. The Offeror shall not embed sound or video (e.g., MPEG) files into the proposal files.

d. Electronic Media additional information:

· 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

L.1.3.8 Cost/Price Information

All cost/price information shall be addressed ONLY in the Proposal Documentation and Contract Cost/Price 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 in Microsoft Excel format. Offerors shall include formulas and working links to the maximum extent practicable (see further format instructions in L.1.3.7). Offerors shall differentiate the Operations and Maintenance costs from the Research and Development.

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 from 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, and letters of commitment which must be submitted in Volume I but may be cross-referenced in other volumes. An additional exception to cross-referencing volumes is that required by L.5.3.1.

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

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 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 PWS 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. If there are additional subcontractors which are not anticipated to play a role 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.

L.2.6.1 Joint Ventures. Offerors that submit a proposal as a Joint Venture shall provide full and complete information on each of the participating members/companies, as well as the proposed organization itself. The Offeror shall describe whether or not the Joint Venture will be populated or unpopulated. The Offeror shall provide a complete copy of the agreement(s) that describe(s) the business arrangement between the entities, including its corporate governance construct that will be utilized to effectively manage and accomplish the work required by this contract.

The Joint Venture Offeror also must provide a fully completed and executed Attachment L- 4 entitled “Performance Guarantee Agreement,” from the ultimate corporate parents, which will become part of the resulting contract as a Section J attachment. In order to consider the financial or other resources of the corporate parent(s), the parent(s) must be legally bound: (i) to provide the necessary resources to the Contractor and assume all contractual obligations of the Contractor; and (ii) to provide guarantees for joint and severable liability for the performance of the Joint Venture contractor.

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

The Offeror must possess, or acquire by the end of the transition period following award, a TOP SECRET facility clearance at the corporate level equal to the classification stated on the Contract Security Classification Specification (DD Form 254) provided as Attachment 2 to this RFP. 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. Contractor information portions of DD254 should also be completed and included. The contract DD-254 also will require access to such information as NATO and Sensitive Compartmented Information. DTRA cannot sponsor offerors for DSS facility clearances until their contract is awarded.

The offeror’s facility should be able to store classified documents up to the SECRET level at the end of the transition period. Should the facility not obtain the required clearance/certifications from the Defense Security Service (DSS) by end of the transition period, storage at an alternate National Capitol Region location is acceptable until DSS clearance/certification is approved.

L.2.8 INFORMATION REQUIRED BY DFARS CLAUSE 252.227-7017 IDENTIFICATION AND ASSERTION OF USE, RELEASE, OR DISCLOSURE RESTRICTIONS (JUN 1995) AND DFARS CLAUSE 252.227-7028 TECHNICAL DATA OR COMPUTER SOFTWARE PREVIOUSLY DELIVERED TO THE GOVERNMENT (JUN 1995)

If applicable, the Offeror shall include 252.227-7017 paragraph (d) chart, in full-text, filled-in/completed. The Offeror also shall attach to its offer the information required by 252.227-7028, if applicable.

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/price, and specific requirements of the solicitation. This information shall be provided in the format and content of Table L.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 L.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 provided in the System for Award Management (SAM) (formerly the Online Representations and Certification Applications ORCA site and the Central Contractor Registration site), https://www.sam.gov/portal/public/SAM.

L.2.11 PREAWARD ORGANIZATIONAL CONFLICTS OF INTEREST (OCIs) AND OCI MITIGATION PLAN

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 RD 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. Moreover, the nature of the work required by this contract could place the awardee in situations where its ability to render impartial advice to the Government could be impaired due to other interests of the awardee. Offerors are advised to review FAR Subpart 9.5 for detailed information concerning organizational conflicts of interest.

b. Because of this unique access, the Government has determined that the A&AS contractor must function in this role as its trusted agent. With the trusted agent approach, the prime contractor and all subcontractors are precluded from participating as a contractor, subcontractor or consultant on future non-A&AS contracts where the RD Directorate is the requiring and/or funding activity, including CWMD IDIQ task orders. This restriction will terminate one year after final payment on the contract. Restrictions upon use of Government information and the requirement to protect proprietary information are permanent. Should the RD A&AS Prime Contractor wish to utilize subcontractors who are not restricted by an IDIQ teaming prohibition, the A&AS Prime contractor shall notify and receive the approval of the DTRA Contracting Officer prior to utilizing any subcontractors in support of CWMD IDIQ evaluation and source selection support. Prior notification and approval is necessary so that the DTRA RFP to the IDIQ contractors can provide the appropriate notifications. For the purpose of this requirement, Systems Engineering and Integration (SE&I) services performed in support of the RD Directorate are considered to be non-A&AS services, and are acquired under separate contract vehicles. The DTRA SE&I support service is defined as the contractor’s capability to integrate diverse and emerging technologies to meet customer needs with a verified product via a systems engineering process.

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 OCIs 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 subcontractor or consultant has a possible OCI.

d. To implement the requirements of clause H.1 of this contract, each Offeror also must include an OCI Mitigation 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 Mitigation Plan shall also ensure that an advantage is not gained by any relationship the offeror may have with current performers of any of the RD Directorate Programs. The written mitigation plan will be incorporated into the resultant contract. At a minimum, the Mitigation 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 thecompanyOrganizational, 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, including electronic firewalls)

· 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, subcontractors and consultants

· 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 contracts in which RD is the requiring and/or funding activity (i.e., contracts awarded prior to the RFP response date) (reference L.2.11c(2))

e. In addition to the OCI Mitigation Plan, offerors shall submit the following information separately from 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 that provide non-A&AS products and/or services relevant to the RD Directorate activities described in the Performance Work Statement, 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 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.

f. The KO 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 KO, 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 possible OCIs 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 KO 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.

h. The KO 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 KO determines that a potential conflict exists, the conflict must be avoided or otherwise resolved through appropriate means in order for the Offeror to be eligible for award.

i. The OCI Mitigation Plan will be addressed during the evaluation of proposals, but it is not a separate evaluation factor.

L.2.12 REVISION MATRIX

If it is determined to be in the best interest of the Government to hold discussions and Final Proposal Revisions (FPRs) are submitted, the contractor shall submit a revision matrix after the table of contents in each volume where revisions have been made. This matrix must include the following: Location of change: At a minimum the page number, but more specific indicators (section, paragraph, etc.) are strongly encouraged Change: A very brief summary of what changed.

L.2.13 SECTION 508 COMPLIANCE

L.2.13.1 Section 508 Program Need Requirements for accessibility based on Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. 794d) are determined to be relevant for the following program need: "Security and Counterintelligence Support Services."

L.2.13.2 Section 508 Service Requirements The anticipated information content deliverable includes topics that address EIT products or EIT-related services. Delivered information content must include data and/or knowledge appropriate and responsive to the functional performance criteria detailed in 36 CFR part 1194 Subpart C, as well as any technical provisions of 36 CFR part 1194 Subpart B applicable to the specific type of EIT addressed in the delivered information content. Solicitation respondents must describe how their proposed information content deliverables meet at least those requirements identified as applicable in the attached L-5 Government Product/Service Accessibility Template (GPAT).

The anticipated information content deliverable is intended to be posted to a website. Delivered information content must consider the specific Section 508 accessibility requirements detailed in 36 CFR part 1194.22 and the functional performance criteria detailed in 36 CFR 1194 Subpart C. Solicitation respondents must describe how their proposed information content deliverables meet at least those requirements identified as applicable in the attached GPAT.

The anticipated labor hour deliverable is expected to involve tasks that relate to or require the use of EIT. Delivered labor hours must include knowledge and capabilities in the functional performance criteria detailed in 36 CFR part 1194 Subpart C, as well as any technical provisions of 36 CFR part 1194 Subpart B applicable to the specific type of EIT involved in the expected tasks. Solicitation respondents must describe how their proposed labor hour deliverables meet at least those requirements identified as applicable in the attached GPAT.

L.2.13.3 Section 508 Evaluation Factors Offerors shall submit adequate information to document their responsiveness to the Section 508 requirements (i.e. a completed GPAT or VPAT or equivalent). DTRA’s assessment of each offeror’s responsiveness to the Section 508 requirements will be included as part of the Factor 1, Mission Capability Sub Factor 1A evaluation rating.

If the deliverable proposed in response to this solicitation includes features and functions in addition to those identified as requirements, these features and functions also need to conform to relevant Section 508 technical provisions, functional performance criteria, and information, documentation and support. The accessibility of these additional features and functions should be described in the completed GPAT, VPAT or equivalent supporting information.

L.2.13.4 Section 508 Acceptance Criteria Supplies or services delivered as a result of this solicitation will be accepted based in part on satisfaction of identified Section 508 requirements for accessibility.

If the deliverable includes features and functions in addition to those identified as requirements, these features and functions also need to conform to relevant Section 508 technical provisions, functional performance criteria, and information, documentation and support.

L.3.0 VOLUME II – MISSION CAPABILITY

L.3.1 GENERAL

The 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 needed 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 and applicable past performance. 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.” Using the instructions provided below, provide as specifically as possible the actual methodology, processes, procedures and any proposed tools, capabilities, etc., 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. Offerors are cautioned that “parroting” of the Mission Capability requirements (described below) or the PWS with a statement of intent to perform does not reflect understanding of the requirements or capability to perform.

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

e. Sub-Factor A - Management Approach

f. Sub-Factor B - Technical Approach

· Key Personnel Resumes

· Sample Resumes

· Sample Challenge/Task

L.3.3 FORMAT AND CONTENT

Mission Capability 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 program management office 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 management approach, plan and milestones for the contract PWS.

L.3.3.2.1 Management Approach

The offeror shall submit a comprehensive, well-structured management approach, plan and milestones that covers the transition approach, plan, resources and milestones, along with the post-transition management approach in a management plan, demonstrating the ability to successfully transition all existing PMO functions, data and objectives to the PMO management structure, as well as manage all PWS program objectives and requirements set forth in the PWS post-transition. The Offerors shall describe the management processes, techniques, organizational structure and resources to:

· Team and Structure: Provide a transition organizational structure and a post-transition organizational structure needed to execute the program objectives listed in the PWS; to include a management team composition with description of duties during these two phases. Provide the final proposed organizational structure to support the program objectives listed in the PWS, to include milestones for filling the management team composition by the end of the transition period in accordance with the PWS requirements and schedule.

· Project, Program, Portfolio Integration: Demonstrate the approach, processes, tasks, milestones and team lead(s) for how the Offeror plans on ensuring integration within the Offeror team across the divisions, department, front office and the directorate level. Demonstrate how the Offeror plans on ensuring integration with, to include integration touch points, with the associate contractor (SME S&T A&AS) and the government team during and after the transition period.

· Leadership Support: Demonstrates the approach, milestones and team leads to effectively work with RD leadership during the transition time period and post-transition program execution time period to define strategic vision, provide leadership, oversight, and technical direction to divisions in program execution; resulting in a PMO workforce and team that is prepared to meet the PWS objectives, support, and represent RD to the Congress, Department of Defense, other U. S. Government agencies, and leaders and representatives of foreign countries as well as help leaders at all organizational levels to achieve maximum effectiveness in their operations.

· Innovation/Continuous Improvement: Demonstrate the approach and ability to continue to innovate and improve existing processes, plans, methodologies across the RD Directorate, Front Office, Departments and Divisions in support of providing the needed technical capabilities to the warfighter.

· Problem Solving, Communications and Rapid Response: Demonstrate approach, tasks, timeline and lead(s) to communicate with RD Directorate, Department Chiefs and Front Office leads to ensure understanding of required tasks and activities and identify specific requirements with respect to specific knowledge, skill and ability sets and capabilities, to include tools and processes needed to support the different program management office objectives. Demonstrate process and points of contact to respond rapidly to maturing specific requirements and needs both during the transition period and during the execution of the contract. Demonstrates ability to respond rapidly to changing requirements and circumstances while meeting customer needs and providing innovative and improving capabilities. Specifically, to respond to verbal requests during normal working hours in near real time, and to provide surge and reach-back capabilities as dictated by the urgency of the tasking. Demonstrates ability to identify and solve problems, integrate and incorporate lessons learned across organizational boundaries, and provide for a routine means of communicating issues, corrective actions, and standard reports to the Government. Demonstrate approach and ability to continually innovate and improve existing methodologies, processes, procedures and tools to ensure and maintain ability to problem solve, communicate needs both strategically and tactically, respond rapidly while providing innovative capabilities.

· Subcontract Management: Demonstrate approach, tasks and timelines to integrate and maintain the subcontractors into an integrated team environment across all levels of the RD Directorate (RD Front Office, Departments, Divisions, Offices) and successfully manage the team activities.

· Workforce Recruitment and Retention: Demonstrate a sound methodology and approach by which the Offeror can readily identify, recruit, hire, train and retain highly qualified employees with the required domain (CBRNE, CWMD, CTNm C-ED) and programmatic knowledge, skills, ability and expertise required to accomplish the range of tasks described in the PWS both during the transition period and during the contract execution, to include the ability to ensure the continuation of services during personnel absences due to sickness, leave and termination such that the impact to the Government is minimal.

· Risk Management: Describe the planned approach to sustain a robust risk assessment, quality control and risk management process to achieve each of the critical milestones both during the transition time period and contract execution.

· Personnel Security. Describe the offeror’s team plan to include approach, processes, milestones and team lead(s), including subcontractors and consultants, to identify recruit, hire and train the required personnel needed to comply with security requirements and timelines stated in the PWS.

· Quality Control: Demonstrates the ability to track, and meet performance and quality metrics while ensuring the quality (timeliness, adequacy, accuracy, etc.) of products and services.

Note: This information is submitted as part of Volume I, Proposal Documentation, but shall be evaluated as part of the overall management approach.

L.3.3.3 SUB-FACTOR B: TECHNICAL APPROACH

The Offeror shall submit key personnel resumes, sample resumes for listed sample job descriptions (see attachment L-3), and their challenge task approaches to the sample tasks in support of the PWS.

L.3.3.3.1 KEY PERSONNEL RESUMES

The Offeror shall provide Key Personnel resumes by position and qualifications to effectively implement the requirements of the contract PWS. No more than three personnel for the overall team may be designated as key. At a minimum, the resumes must contain the following information:

· Identification and Proposed Position (Name of key person, 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)

· Professional Memberships, Honors and Certifications (Year(s), Position or Award/Honor, Institution, City, State)

· Provide Letters of Commitment (not to exceed one page)

L.3.3.3.2 SAMPLE RESUMES

The Offeror shall provide sample resumes by position and qualifications to demonstrate understanding the task requirements (knowledge, skills, ability, and expertise) of the contract PWS for the following positions:

C-IED Program Integrator/Senior Advisor System Integrator for RD-TT Nuclear Survivability Program Manager Nuclear Effects Integrated Tool Set Technical Program Manager Test Support Scheduling and Planning Program Manager Chemical & Biological Technical Program Manager

At a minimum, the resumes must contain the following information:

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

· Education and Training (Degree, Year, Field of Study)

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

The purpose of these sample resumes is to demonstrate the offeror’s understanding of the required knowledge, skill, abilities and expertise required to fill the job. These sample resumes DO NOT indicate any agreement to provide any specific individuals called out in these resumes. Do not include individual names, actual or otherwise. The intent is to demonstrate the types of individuals you would recruit to meet the task requirements.

L.3.3.3.3 SAMPLE CHALLENGE TASK

The Offeror shall submit their approach to include methodologies and plan, required staffing to accomplish task, the KSA of personnel required to perform the work, to include domain (CBRNE, CWMD, CTN, C-IED) and programmatic expertise based on department/division supporting, along with any tools or capabilities required to accomplish the sample challenge task which demonstrates the offeror’s understanding of the required domain expertise (CBRNE, CWMD, CTN, C-IED) and programmatic expertise to fulfill these duties.

CHALLENGE TASK:

Sample Task 1: [Challenge in development]

Sample Task 2: [Challenge in development]

Sample Task 3: [Challenge in…