HDTRA1-14-R-0005-0001.pdf

INO139926839

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83)

Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this amendment is to:

1. Update Section C, Statement of Objectives, paragraph 6.0 (changes highlighted) to add an inventory description.

2. Update Section J,Attachment 1, DD254, to that dated 28 Feb 2014 w hich adds the requirements in: (a) Block 10i, Limited Dissemination

Information; (b) Block 11c, Receive and Generate Classif ied Material; (c) Block 11d, Fabricate, Modify, or Store Classif ied Hardw are; and (d)

Updates Block 13 accordingly.

3. Update Section L.1.0, General Instructions, (changes highlighted) to: (a) Add the Contracting Officer's email address to L.1.1.1; (b) Delete the transition approach 'at the end of contract' from L.3.3.2, Section 1; (c) Add 'Roll up costs for STO1 and STO2' to L.5.2; and (d) Add

'Sample Task Order SOWs' to items 6 and 7 of Attachment L-1, Present and Past Performance Information Form.

1. CONTRACT ID CODE PAGE OF PAGES

1 52

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 19-Mar-2014

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X HDTRA1-14-R-0005

X 9B. DATED (SEE ITEM 11)

18-Feb-2014

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE

RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

19-Mar-2014

CODE

DEFENSE THREAT REDUCTION AGENCY/J4C

8725 JOHN J. KINGMAN ROAD, MSC 6201

FORT BELVOIR VA 22060-6201

HDTRA1 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

HDTRA1-14-R-0005

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

STATEMENT OF OBJECTIVES

Defense Threat Reduction Information Analysis Center (DTRIAC) Operations

15 January 2014

1.0 SCOPE

Services to be provided will be for the operations of the Defense Threat Reduction Information

Analysis Center (DTRIAC), located at Kirtland AFB, NM and the support office at Fort Belvoir, VA. Services include conducting analytical activities, preserving and expanding the knowledge base, providing research related to DTRA mission areas, conducting outreach to the Chemical, Biological, Radiological, Nuclear and Explosive (CBRNE) community, on Combating Weapons of Mass Destruction (CWMD) topics, and maintaining the Information Technology (IT) readiness and innovation potential to further advance information sharing.

2.0 BACKGROUND

The DTRIAC manages a vast collection of unclassified and classified knowledge bases. It promotes the use of existing Scientific and Technical Information (STI) to meet Department of

Defense (DoD) research, development, test, evaluation, training, mission rehearsal, logistics, maintenance, and operational requirements. The DTRIAC acquires digests, analyzes, evaluates, synthesizes stores, publishes, and disseminates STI related to all DTRA mission areas.

The DTRIAC provides a CWMD knowledge base and information analysis capability to support

DTRA in all its mission areas, and serves the broader CWMD community of interest (COI). It is required to provide scientific and technical information products and services that may be in the form of studies and analyses to DTRA CWMD customers, and other authorized customers in accordance with DoD policies. The DTRIAC will identify and deliver CWMD information by building tailored, high-tech, open and secure information integration and sharing enterprise solutions to serve the entire CWMD COI.

The goal is to establish the DTRIAC as the leading source of DoD CWMD information.

3.0 OBJECTIVES

3.1 Routine Operations

Provide services to operate DTRIAC, including but not limited to conducting analytical activities on CWMD topics and records management, maintenance, preservation and expansion of the

DTRIAC holdings.

3.1.1 Maintain and Improve the Information Base

Manage the DTRIAC collection and provide services having broad application to DTRA’s

CWMD mission. Expand and update the collection through identification, acquisition, protection, preservation, and storage of classified and unclassified information. Apply data and information analysis and fusion techniques, methodologies, tools, and applications to respond to customer needs. This sub-task also includes performing indexing and data retrieval capabilities, records management, developing enhanced methods to improve cataloging, and coordinating with other IACs for access to their holdings that are relevant to DTRIAC.

3.1.2 Customer Service and Outreach to the Threat Reduction Community of Interest

Provide customer service support for all DTRA mission areas. This support will include activities such as data/collection identification and acquisition for DTRIAC, coordinating and responding to inquiries, attending meetings/conferences/symposia, developing S&T informational products such as the DTRIAC newsletter, and conducting/hosting tours and visits to the DTRIAC facilities. The overall goal of this sub-task is to promote and foster the exchange of information to raise awareness of the IAC’s capabilities.

3.1.3 Provide STI Program Support

Provide assistance in tracking and processing technical reports, in addition to, providing operational support for day-to-day activities including accessions, information research, cataloging, and collection maintenance. This support also includes inputting technical and R&D funding data into the Unified Research and Engineering Database (URED), as mandated by

DoD.

3.1.4 Information Technology Maintenance and Initiatives

Improve and enhance capabilities of the Scientific and Technical Information Archival and

Retrieval System (STARS) to increase performance and data availability, through continued development and/or other means. Capitalize on new and improving technology to optimize effectiveness and reduce risks.

3.1.5 Transition Planning

Provide transition strategies, schedules and list responsibilities for facilitating an effective transition.

3.2 Technical Value Added

Provide services to conduct studies and analytical activities on all CWMD-related topics.

3.2.1 Provide analysis in accordance with DoDI 3200.14 (“Principles and Operational

Parameters of the DoD Scientific and Technical Information Program”) and perform the following analytical functions: (1) Verify and validate the technical accuracy and reliability of existing data, (2) Generate and evaluate data collection and analysis techniques reported in the literature, (3) Develop alternative approaches to collecting and analyzing the same or similar data for CWMD technical areas (see http://www.dtra.mil for additional information), and (4) Identify and fill voids in existing data or knowledge bases.

3.2.2 Provide CWMD subject-matter experts to provide in-depth analysis and create specialized technical information products (i.e., state-of-the-art reports; handbooks; data books; data sets;

critical reviews; standards and technology benchmarks; problem definitions; and alternative technology analyses) consistent with DTRA Research & Development technical areas.

3.2.3 Conduct preliminary specialized studies and analyses of problems and provide advice on scientific, technical, and operational support topics within the scope of the DTRIAC. Perform other initial unique scientific and technical activities that allow for research of greater depth and specialization related to DTRA’s broad CWMD role. Make accessible subject matter expertise

(e.g., scientists, engineers, information specialists) with the ability to provide expert and unbiased scientific and technical analyses to support the conduct of these preliminary specialized studies and activities. Support Technical Area Tasks (TATs) efforts requiring these preliminary specialized studies and analyses.

3.2.4 Provide interface (to include providing access to resident knowledge and expertise) with performers of TATs as necessary to assist in the performance of TAT efforts, or to provide other support as needed for the TAT performers to effectively and efficiently accomplish their objectives.

3.2.5 Optimize, customize and/or modify existing analytics, search, retrieval, reporting, visualization tools, technologies, methodologies, and/or applications, etc., as required to meet specialized requirements. Such requirements would include specialized customer analytics, search, retrieval, reporting and/or visualization needs, capabilities and/or other customer requirements within the existing DTRIAC framework.

3.2.6 Analyze the existing DTRIAC data collection and the CWMD community areas of focus to ensure that information of value is available within the collection. Continually ensure that information of value is readily discoverable, accessible, and efficiently provided to customers to meet real-time demands. Identify information and data gaps (including inaccurate information and data) within the collection and report these findings to the Government.

3.2.7 Generate scientific, technical, and other related information within the technical scope of this SOO in a timely fashion. Retrieve, organize, and highlight relevant information and prepare bibliographies of selected reference citations in response to technical and customer inquiries. Be prepared to give value judgments on the accuracy and reliability of the data.

3.2.8 Provide all authorized users with focused, expert assistance and unbiased scientific, technical, and operational support information within DTRA’s mission areas.

5.0 DELIVERABLES

Specific deliverables will be specified at the task order level.

http://www.dtra.mil/

6.0 OTHER REQUIREMENTS

Government Furnished Equipment/Facilities/Data

The Contractor will be provided work space in DTRIAC facilities as needed and access to documents, and software/hardware. Government will allow access to government-owned vehicles for use on Kirtland AFB. Government will furnish a forklift for use in DTRIAC’s document warehouse. The contractor will be provided four (4) workspaces at the Defense Threat

Reduction Center (DTRC) at Fort Belvoir, VA.

Contractor shall provide a hand receipt holder to account for government property located in government facilities. The contractor shall utilize the Defense Property Accountability System

(DPAS) for tracking agency inventory. The contractor shall verify the DPAS inventory for accuracy and completeness. Inventory will include but not be limited to Government laptop computers (telephone/internet services), printers, copiers, scanners, approximately 100 workstations/computers/ monitors, 2 Sun Microsystem Network Servers, video production equipment, thin clients, high security shredder, CD/DVD duplicator, optical reader, tape autoloaders, advance storage system and general office supplies.

Contractor shall ensure an appropriate number of personnel are trained and able to write and submit a building/facility work order for issues within DTRIAC spaces.

Security Requirements

Contractor personnel required to carry out these tasks will need appropriate clearances and be authorized access to applicable DoD/DTRA facilities. Contractor personnel tasked to carry out the above tasks will need at least Secret clearances and authorized access to all facilities, documents, and programs necessary to complete the foregoing tasks. An appropriate number of personnel with Top Secret Clearances will be required for both Kirtland AFB, NM and Fort

Belvoir, VA locations. Contractor will comply with all DoD requirements for the handling, storage and transportation of classified documents.

Travel Requirements

Specific travel requirements will be at the task order level.

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

The Table of Contents has changed from:

Exhibit/Attachment Table of Contents

DOCUMENT TYPE DESCRIPTION PAGES DATE

Attachment 1 DoD Contract Security

Classification

Specification (DD254)

6 04-DEC-2013

to:

Exhibit/Attachment Table of Contents

DOCUMENT TYPE DESCRIPTION PAGES DATE

Attachment 1 DoD Contract Security

Classification

Specification (DD254)

6 28-FEB-2014

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

SECTION L

SECTION L

L.1.0 GENERAL INSTRUCTIONS

L.1.1 GENERAL INFORMATION

L.1.1.1 Point of Contact

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

The CS for this acquisition is:

Anne Behne

Defense Threat Reduction Agency

J4CRB

Email address: Anne.Behne @DTRA.mil

The Contracting Officer (CO) for this acquisition is:

Theresa M. Hyman

Defense Threat Reduction Agency

J4CRB

Email address: Theresa.Hyman@dtra.mil

Offerors are instructed to address all questions or concerns regarding this solicitation via email to anne.behne@dtra.mil with the subject line “Questions Concerning HDTRA1-14-R-0005.” Questions regarding this solicitation must be received no later than 16 days after posting of the solicitation.

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. Offerors may request a pre-award debriefing by submitting a written request to the 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.1.2.2 Post-award Debriefings mailto:anne.behne@dtra.mil

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

L.1.1.3 Discrepancies

If an Offeror believes that the requirements in these instructions contain errors, omissions, or are otherwise unsound, the Offeror shall immediately notify the CO in writing with supporting rationale. It is the Government’s intent to award with discussions; however, the Government reserves the right to award this effort based on the initial proposal, as received, without discussions. If, during the evaluation period, it is still determined to be in the best interest of the Government to hold discussions, then discussions will be held with only those Offerors determined to be in the competitive range.

L.1.2 ORGANIZATION/DISTRIBUTION/NUMBER OF COPIES/PAGE LIMITS

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.

Table 1.2 – Proposal Organization

VOLUME VOLUME TITLE PAGE LIMIT

I

3 copies PROPOSAL DOCUMENTATION Unlimited

II

4 copies

MISSION CAPABILITY

Management Approach 15

Technical Approach 7

Sample Task Order #1 10

Sample Task Order #2 10

III

3 copies

PAST PERFORMANCE

Description Of Team 10

Present And Past Performance References

5 pages per reference

(Narrative and

Attachment L-1)

Organizational Change History Unlimited

IV

3 copies COST/PRICE Unlimited

a. The “ORIGINAL” copy of Volumes I, II, III, and IV of the proposal shall be provided under separate cover. The

“original” paper copy shall be formatted as follows:

1. Clearly marked as “Original”.

2. Unbound without any staples.

3. Hole-punched with a standard 2-hole punch at the top of each page.

4. Printed head-to-foot so that each page can be read when placed in a standard 2-hole file folder

(Classification Folder).

5. Placed in a classification folder similar to the one shown in the picture below:

6. Each volume shall have a cover sheet, clearly marked as volume number, “ORIGINAL”, Offeror's name, solicitation title, solicitation number, and proposal date.

7. The “ORIGINAL” copy is not included in the copy count in Table 1.2.

b. An electronic copy of each volume shall be submitted in accordance with Paragraph L.1.3.8.

c. As shown in Table 1.2, additional paper copies of Volumes I, II, III, and IV shall be submitted in separate 3-ring loose-leaf binders, which when open, lay flat. No staples shall be used. A cover sheet shall be posted at the beginning of each volume, clearly marked as to volume number, title, copy number, RFP identification, and the

Offeror’s name. The same identifying data shall be placed on the spine of each binder.

d. 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),” DEC 2007 (the clause is located immediately before Paragraph L.1.0). 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, anne.behne@dtra.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 mailto:anne.behne@dtra.mil

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

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

Proposals will be submitted in paper and electronic copies.

Paper copies of the proposal must lie flat when open. Elaborate binding is not desired.

No models, mockups, or videotapes will be accepted.

L.1.3.5 Page Format Restrictions and Limitations

L.1.3.5.1 Page Size

Pages shall be 8.5 x 11 inches, not including foldouts. Except for the lettering that is within a graphic, the font size shall be no less than 10 point. Lettering within tables, charts, graphs, and figures shall be no smaller than 8 point.

Margins on all four edges of each sheet will be at least one-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.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. Printed material shall be on one side of the sheet only (single-sided). In the event discussions are held, page limitations may be placed on responses to 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 tabs dividers blank pages key personnel resumes (2 pages per resume)

L.1.3.6 Indexing

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

L.1.3.7 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. Foldout pages may only be used for large tables, charts, graphs, diagrams, and schematics; not for pages of text. For tables, charts, graphs, and figures, the font shall be no smaller than 8 point. All information (except documentation numbers, classification markings, and page numbers) shall be contained within an image area of 9 x 15-1/2 inches.

L.1.3.8 Electronic Copies

a. Electronic copies of each volume shall be submitted on individual CD-ROMs 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. The CD-ROM(s) will be included with the “original” paper copy of each volume. Offerors are responsible for ensuring electronic copies are virus-free.

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

- Adobe Acrobat Reader 10.0

- Microsoft Office Suite (Word, Excel, PowerPoint, and Project) 2010*

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

Note:

The electronic copy shall be in Adobe Acrobat (except for Microsoft Excel) portable document file (pdf) searchable text format and shall be an exact duplicate of the “original” paper proposal. If there are discrepancies between the electronic proposal and the “original” paper proposal, the paper proposal shall prevail.

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.9 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. Offerors shall differentiate the Operations and Maintenance costs from the Research and

Development.

L.1.3.10 Volume Designation

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

Volume I but may be cross-referenced in other volumes.

L.1.3.11 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:

a. Table of Contents

b. List of Tables and Drawings

c. Glossary

d. Documents listed in paragraphs L.2.2 through L.2.10

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, DCAA, and Government Paying Office. Also provide the name, telephone and fax numbers, and e-mail address for the Administrative Contracting Officer (ACO). The aforementioned information also applies to the prime contractor and major subcontractors/teaming partners.

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

Provide the company’s/division’s street address, county, and facility code; CAGE Code; DUNS number; Taxpayer

Identification Number (TIN), size of business (large or small); and labor surplus area designation.

L.2.6 TEAMING ARRANGEMENTS AND/OR LETTERS OF COMMITMENT

Provide all Teaming Arrangements and/or Letters of Commitment from first-tier subcontractors. The Government will consider the Offeror and first-tier subcontractor(s) as a whole “Team” when a signed Teaming Arrangement or

Letter(s) of Commitment is submitted with the proposal. In the absence of these documents, the Offeror and its first-tier subcontractor(s) will not be considered a “Team” and will not be evaluated as such.

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

The Offeror must possess, or acquire prior to award of a contract, a facility clearance equal to the classification stated on the Contract Security Classification Specification (DD Form 254) provided as Attachment 1 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 will require a Top Secret facility clearance and accesses to such information as NATO and Sensitive Compartmented Information.

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 2.9. Failure to comply with the terms and conditions of the solicitation may result in the Offeror being removed from consideration for award.

Table 2.9 – Solicitation Exceptions

Solicitation Document Paragraph/Page Requirement/Portion Rationale

Statement of Objectives

(SOO), Solicitation

Section, Attachment, etc.

Applicable Page and

Paragraph numbers

Identify the requirement or portion to which the exception is taken

Justify/explain the basis for exception and impact on contract

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

L.2.11.1. The Government has determined that this contract may give rise to potential conflicts of interest. The successful offeror for this requirement will have access to contractor-sensitive / proprietary information that could potentially provide an unfair competitive advantage for future contracts. Moreover, some of the work required by this contract potentially 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 directed to FAR Subpart 9.5 for detailed information concerning OCIs.

L.2.11.2. Preaward Organizational Conflicts of Interest https://www.sam.gov/portal/public/SAM

a. 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 has a possible OCI.

b The CO 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 CO, 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.

c. 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 CO 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.

d. The CO 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 CO 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.

L.2.11.3. OCI Mitigation Plan

a. To implement the requirements of clause 252.209-9000 of this contract, each Offeror also must submit a separate

OCI Mitigation Plan in Volume I that addresses internal processes and procedures for identifying, evaluating and resolving potential, real and apparent OCIs at the task order level. The 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 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 parent organization 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.

b. The OCI Mitigation Plan also shall include a detailed organizational chart that depicts the hierarchal structure of the Offeror’s 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 are most likely to perform task orders under this contract fit within the hierarchal structure.

c. The OCI Mitigation Plan will be addressed during the evaluation of proposals, but it will not be treated like 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.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 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 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.” Using the instructions provided below, provide as specifically as possible the actual methodology that would be used by the Offeror for accomplishing and satisfying these 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 SOO or task order SOWs with a statement of intent to perform does not reflect understanding of the requirements or capability to perform.

L.3.2 VOLUME ORGANIZATION:

b. List of Tables and Drawings

c. Glossary

d. RFP Cross-Reference Matrix

e. Section 1, Management Approach

f. Section 2, Technical Approach

g. Section 3, Sample Task Order #1

h. Section 4, Sample Task Order #2

L.3.3 FORMAT AND CONTENT

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

Proposal Volume/

Section/Paragraph

Solicitation

Section/Paragraph

Proposal Volume/

Section/Paragraph

L.3.3.2 SECTION 1: MANAGEMENT APPROACH

The offeror shall submit a comprehensive integrated management approach to accomplish the overall program and contract objectives. The approach should provide details on the offeror’s proposed organizational structure (to include lines of authority, responsibility, and participation and management of subcontractors) and transition approach (both initial transition and at the end of the contract) to meet the requirements of the contract statement of work. The offeror shall also provide a separate detailed Recruitment, Retention, and Surge Support Plan for managing the contract requirements of the SOO. This plan shall include a plan of action to provide “surge support” personnel and replacement of personnel due to loss by resignation within the desired 90 day timeframe.

The management approach shall address the following areas:

Personnel. The offeror shall describe:

o The strategies that will be developed and implemented to provide oversight, leadership and quality control measures to ensure successful performance of the contract.

o How the offeror will effectively recruit and retain qualified personnel to meet SOO requirements, to include personnel with appropriate CWMD, knowledge and expertise. How the offeror will ensure personnel maintain active appropriate security clearances (up to TOP SECRET, and with

NATO, RD and CNWDI access).

o The ability to rapidly obtain necessary and appropriate personnel and expertise to meet rapidly changing, surge, short notice and/or quick response requirements.

o The adequacy of the assembled team of personnel to perform and meet all requirements of the

SOO.

o How it will ensure synergy between the Technical Value Added and Routine Operations tasks as described in the SOO.

Programmatic (Cost/Schedule/Performance). The offeror shall describe:

o How it will identify proposed risks for the overall DTRIAC program and how the offeror will manage and mitigate those risks. The processes that it will develop and implement to ensure quality, timeliness, and cost effective performance.

o Its incoming transition plan detailing the process by which the Offeror will take over responsibility for DTRIAC operations from the incumbent in an efficient and effective manner.

The plan should include expected time frames and assumptions of what will be provided by the incumbent during the transition period.

Regulation and Other Compliance. The offeror shall describe:

o The security procedures to that it will develop and implement to effectively minimize or eliminate potential security risks and meet all contract security requirements.

o Its understanding of and ability to comply with relevant DoD and USG directives, requirements and other guidance relating to DTIC, NARA and Information Assurance.

L.3.3.3 SECTION 2: TECHNICAL APPROACH

The technical approach shall address how the Offeror will accomplish the SOO Objectives with an acceptable level of risk, including the following:

Describe understanding of the scientific and technical complexities of the SOO and the approach to accomplishing all tasks and subtasks.

Describe the appropriate capabilities to develop and test new software and hardware for intended use with DTRIAC assets. This would include but not be limited to “mirror” or other realistic assets to test new items before being integrated and used with the actual operational parts of DTRIAC systems.

L.3.3.4 Sections 3 and 4: Sample Task Orders

The Offeror shall describe their practical application of the processes, procedures, and approaches provided in

Volume II, Mission Capability, Sections 1 and 2, towards each sample Task Order. The Offeror shall provide resumes for key personnel and provide a separate technical proposal for each sample Task Order that describes how the Offeror will carry out the sample Task Order. Key Personnel resumes are not counted against the page limit;

however, resumes are restricted to two pages each (as stated in Paragraph L.1.3.5.3). Each response to the sample

Task Order shall be organized as follows:

Table of Contents

List of Tables and Figures

Glossary

Key Personnel (Resumes): Describe the ability to identify and assign key personnel with relevant experience and expertise.

Management Approach and Risk Management: Describe the ability to manage the specifics of each sample

Task Order in consonance with the processes and procedures described in L.3.3.2. Include a Proposal Risk

Matrix (The required format is shown in Table 3.3.4).

Technical Approach: Describe the ability to successfully perform and complete the specific work of each sample Task Order in consonance with the processes and procedures described in Paragraph L.3.3.3.

Table 3.3.4

PROPOSAL RISK MATRIX

Risk

Factor/Rational

Impact Current Risk

Level

Mitigation Post-Mitigation

Rating

Risk

Ownership

Quantitative estimates on cost are allowed here

High, Medium, Low (Choose

One)

High, Medium, Low (Choose

One)

L.4.0 VOLUME III –PAST PERFORMANCE

L.4.1 VOLUME ORGANIZATION

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

b. Description of Team

c. Present and Past Performance References

d. Present and Past Performance References for Task Order #1

e. Present and Past Performance References for Task Order #2

f. Organizational Structure Change History

L.4.2 DESCRIPTION OF TEAM

The offeror shall provide a matrix of all proposed subcontractors/team members and the specific areas within the proposed SOO, and each sample task order SOW, for which they will be utilized. 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, and/or joint venture partner, authorizing release of adverse past performance information to the Offeror, so the Offeror can respond to such information. For each identified effort for a commercial customer, the Offeror shall also submit a client authorization letter, authorizing release to the Government of requested information on the Offeror’s performance.

L.4.3 PRESENT AND PAST PERFORMANCE REFERENCES

The offeror shall identify a minimum of three and a maximum of five references for the prime offeror as well as a minimum of one and maximum of two references for each of the subcontractors/teaming partners expected to perform aspects of the effort that the Offeror considers critical to the overall success of the program. The references shall represent recent contracts (within the past five years) that the Offeror considers most relevant in demonstrating the

Offeror’s ability to perform the proposed effort. For each reference, the offeror shall provide a narrative describing the effort and the results of the Offeror’s performance. For each reference, the Offeror shall complete a Present and Past

Performance Information Form (attachment L-1). For a description of the characteristics or aspects the Government will consider in determining relevance, see Section M, Paragraph M.2.3, Factor 2: Past Performance.

For each Task Order, the offeror shall identify a minimum of three and a maximum of five references for the prime offeror as well as a minimum of one and maximum of two references for each of the subcontractors/teaming partners expected to perform aspects of the each Task Order effort that the Offeror considers critical to the overall success of the Task Order. It is acceptable if some of the references for the Task Orders are the same as those for the overall contract. For each Task Order, the Offeror shall provide a matrix of all proposed subcontractors/team members and describe the specific areas within the Task Order SOW for which they will be utilized. Offerors shall also provide an approximate percentage of effort, based on cost, that each subcontractor/team member will contribute to the overall sample task order effort. This information will be utilized to determine relevancy for the subcontract references.

In addition to the information provided in the Past Performance Volume, the offeror shall ensure that each reference identified completes a Present and Past Performance Questionnaire (PPPQ) (Attachment L-2). This questionnaire shall be submitted directly to the government from the reference; questionnaires received from the Offeror will not be considered. However, the responsibility to send out and track the completion of the PPPQs rests solely with the

Offeror. Completed PPPQs shall be emailed in PDF format to the Contracting Officer and Contract Specialist at the e-mail addresses shown in Paragraph L.1.1.1.

L.4.4 ORGANIZATIONAL STRUCTURE CHANGE HISTORY

Many companies have acquired, been acquired by, or otherwise merged with other companies, and reorganized their divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the time of performance of relevant present or past efforts or between conclusion of recent past efforts and this source selection. As a result, it is sometimes difficult to determine what past performance is relevant to this acquisition. To facilitate this relevancy determination, include in this proposal volume a “roadmap” describing all such changes in the organization of the Offeror for the past 5 years and also include a “roadmap” for all team members identified in a

Teaming Arrangement or Letter of Commitment for their efforts. As part of this explanation, show how these changes impact the relevance of any efforts the Offeror identifies for past performance evaluation and performance confidence assessment. Since the Government intends to consider present and past performance information provided by other sources as well as that provided by the Offeror, these “roadmaps” should be both specifically applicable to the efforts the Offeror identifies and general enough to apply to efforts on which the Government receives information from other sources. These “roadmaps” will not count toward the page limitations of Volume

III.

L.5.0 VOLUME IV – COST/PRICE

L.5.1 GENERAL

The Offeror shall provide a cost proposal for each sample task that is consistent with the technical…