Amendment_0001_Mod_Final.pdf

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

See Block 14 Continuation Page

POC: Joyce Hongell

Email: Joyce.Hongell.1@us.af.mil

Phone: 321-494-5206

1. CONTRACT ID CODE PAGE OF PAGES

S 1 16

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

16C. DATE SIGNED

BY 23-Mar-2017

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 FA702217R0002

X 9B. DATED (SEE ITEM 11)

14-Mar-2017

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

23-Mar-2017

CODE

AMIC DET 2 OL/PKA

10989 SOUTH PATRICK DRIVE

PATRICK AFB FL 32925

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

FA702217R0002

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

The following items are applicable to this modification:

BLOCK 14 CONTINUATION

The purposes of this amendment 0001 are to:

a) update Section B CLIN descriptions for CLINs 0009, 1009, 2009, and 3009 to identify Not Separately Priced

(NSP);

b) update Section J, Attachment 2 to incorporate DD254 and VGSA dated 22 Mar 17;

c) update Section L.1.1 to specify ESAS 2 contract ceiling;

d) update Sections L.3.1.2, L.3.1.4, L.3.1.5, and L.3.1.6 to remove the requirement to complete information or fill-ins.

SUMMARY OF CHANGES

SECTION B - SUPPLIES OR SERVICES AND PRICES

CLIN 0009

The CLIN extended description has changed from:

The contractor shall furnish all necessary supplies and services required to deliver technical data and information in accordance with Exhibit A, DD Form 1423, Contract Data Requirements Lists (CDRLs).

To:

The contractor shall furnish all necessary supplies and services required to deliver technical data and information in accordance with Exhibit A, DD Form 1423, Contract Data Requirements Lists (CDRLs). This CLIN is Not

Separately Priced (NSP).

The pricing detail quantity has decreased by 1.00 from 1.00 to 0.00.

The unit of issue Each has been deleted.

CLIN 1009

The contractor shall furnish all necessary supplies and services required to deliver technical data and information in

The contractor shall furnish all necessary supplies and services required to deliver technical data and information in

Separately Priced (NSP).

CLIN 2009

The contractor shall furnish all necessary supplies and services required to deliver technical data and information in

The contractor shall furnish all necessary supplies and services required to deliver technical data and information in

Separately Priced (NSP).

CLIN 3009

IAW FAR 52.217-8 Option to Extend Services. The contractor shall furnish all necessary supplies and services required to deliver technical data and information in accordance with Exhibit A, DD Form 1423, Contract Data

Requirements Lists (CDRLs).

The contractor shall furnish all necessary supplies and services required to deliver technical data and information in

Separately Priced (NSP).

SECTION F - DELIVERIES OR PERFORMANCE

The following Delivery Schedule item for CLIN 0009 has been changed from:

DELIVERY DATE QUANTITY SHIP TO ADDRESS DODAAC /

CAGE

POP 15-MAY-2018 TO

14-MAY-2020

N/A AFTAC/TH - F3KTK1

DONNA MILLER

10989 S. PATRICK DRIVE

PATRICK AFB FL 32925-3002

321-494-0546

FOB: Destination

F3KTK1

DELIVERY DATE QUANTITY SHIP TO ADDRESS DODAAC /

CAGE

POP 15-MAY-2018 TO

14-MAY-2020

N/A AFTAC/TH - F3KTK1

DONNA MILLER

10989 S. PATRICK DRIVE

PATRICK AFB FL 32925-3002

321-494-0546

FOB: Destination

F3KTK1

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

The following have been modified:

EXHIBITS AND ATTACHMENTS

Exhibit/Attachment Table of Contents

DOCUMENT TYPE DESCRIPTION PAGES DATE

Exhibit A CDRLS 38 9 Dec 16

Attachment 1 Performance Work Statement

(Basic PWS)

13 9 Dec 16

Attachment 2

Attachment 3

Attachment 4

Attachment 5

Attachment 6

Attachment 7

Attachment 8

Attachment 9

Attachment 10

Attachment 11

Attachment 12

DD254 and VGSA

TO 0001 PWS

Labor Category Descriptions

FFP Labor Rates

TO 0001 CPFF

Evaluated Price FFP

CPFF Labor Rates

Evaluated Price CPFF

Past Performance Information

Past Performance Questionnaire

Quality Assurance Surveillance

Plan

22 Mar 17

9 Dec 16

28 Feb 17

17 Feb 17

17 Feb 17

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

SECTION L

INFORMATION TO OFFERORS (ITO) AND INSTRUCTIONS FOR PROPOSAL PREPARATION

L.1.0 Program Structure and Objectives

The ESAS 2 contract will provide research and development support to advance DOD capabilities in NUDET, weapons of mass destruction, and other applied detection technologies. The ESAS 2 contract will provide subject matter expertise in sensor system and technologies across the electromagnetic, optical, and geophysical spectrums to advance the detection technologies. The potential projects will use a mix of Operations and Maintenance (3400), Research and Development (3600), and limited Procurement (3080) funding appropriations. The contract structure will be an Indefinite-Delivery–Indefinite-Quantity task order contract and have the flexibility to use Firm-Fixed-

Price, Cost-Plus-Fixed-Fee, and Cost-Reimbursement Contract Line Item Numbers. It will have a two-year base period with two two-year options for the potential of a six-year contract. The government intends to issue a single award as the task orders will be interrelated and culminate in to a potential NUDET and other proliferation detection capability.

L.1.1 Budget/Funding Information

For consideration in developing your proposal, the ESAS 2 contract ceiling will be $49.8M with no restrictions on the funding distribution. However, historically, the funding distribution was 89% Research and Development, 6%

Operations and Maintenance, and 5% Procurement. The task order funding will be provided by the specific program being supported.

The contract ceiling identified above and at clause 52.216-19 is established based on known mission requirements.

The Government reserves the right to negotiate in-scope changes to this ceiling when mission needs drive such a decision.

L.2.0 General Instructions

(a) The offeror's proposal must include all data and information requested by this ITO and must be submitted in accordance with these instructions. The offer shall be compliant with the requirements as stated in the

Performance Work Statement (PWS), Contract Data Requirements List (CDRL), and Model Contract. Non-conformance with the instructions provided in this ITO may result in an unfavorable proposal evaluation and may be grounds to eliminate the proposal from consideration for contract award.

(b) The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal should not simply rephrase or restate the

Government's requirements but rather shall provide convincing rationale to address how the offeror intends to meet these requirements. Offerors shall assume that the Government has no prior knowledge of their facilities and experience and will base its evaluation on the information presented in the offeror's proposal. Any reference to day(s) stated in the RFP, attachments and other contractual documents should be considered as

“calendar” days unless specifically stated otherwise. Offerors are advised their proposals are presumed to represent their best efforts and most complete responses to this solicitation. Demonstration of capability and qualifications that clearly support the offeror’s claims are essential. The absence of such evidence will adversely influence evaluation of the proposal. Offers will be evaluated using the Factors and Sub-factors under Section M, Evaluation Factors for Award.

(c) Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary and are not desired.

(d) The proposal acceptance period is specified in Section A of the model contract/solicitation. The offeror shall make a clear statement in Section A of the proposal documentation volume that the proposal is valid through this date.

(e) 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 such unsuccessful proposals.

L.2.1 General Information

L.2.1.1 Point of Contract. The Contracting Officer (CO) is the sole point of contact for this acquisition. Address any questions or concerns you may have to the CO. Written requests for clarification may be sent to the CO at the address located in Section A of the model contract/solicitation.

L.2.1.2 Debriefings. The CO will promptly notify offerors of any decision to exclude them from the competitive range; whereupon, they may request and receive a debriefing in accordance with FAR 15.505. Offerors excluded from the competitive range may request a pre-award debriefing or they may choose to wait until after the source selection decision to request a post-award debriefing. However, offerors excluded from the competitive range are entitled to no more than one debriefing for each proposal. The CO will notify unsuccessful offerors in the competitive range of the source selection decision in accordance with FAR 15.506. Upon such notification, unsuccessful offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

L.2.1.3 Discrepancies. If an offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the offeror shall immediately notify the CO in writing with supporting rationale as well as the remedies the offeror is asking the CO to consider as related to the omission or error. The offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussion. This reservation includes matters of omission, errors, additional or substitute pages of the initial proposal.

L.2.1.4 Electronic Reference Documents. All unclassified referenced documents for this solicitation are available on the Federal Business Opportunities (FedBizOpps) website at http://www.fedbizopps.gov. Potential offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation. Additionally, an electronic classified Technical Library will be made available to offerors by point of contact listed in Section A during the proposal preparation period. To ensure all offerors have the same access to the technical library, offerors with the appropriate security clearance will be sent a classified CD for use in proposal preparation. The CD must be immediately returned upon completion of the ESAS acquisition. The classified CD must be properly secured, wrapped, marked, and shipped via registered mail in compliance with DOD 5200.1-R and

AFI 31-401 security guidelines. In order for the government to send the CD to the offeror, the Government will need a point of contact, their Social Security Number for Joint Personnel Adjudication System (JPAS) verification, company cage code and the classified registered mailing address.

L.2.1.5 Communications. Exchanges of source selection information between Government and offerors will be controlled by the CO. Email may be used to transmit such information to offerors only if the email can be sent and received encrypted and includes “Source Selection Information – See FAR 2.101 & 3.104” in the Subject line.

Otherwise, source selection information will be transmitted via fax or mail.

L.2.2 Organization/Number of Copies/Page Limits

The offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 2.2 below). The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits and with the number of paper copies as specified in Table 2.2. The Administrative Volume should not be used to expand information that should be included in other volumes. The attachments identified in the table shall be separately bound in three-ring, loose-leaf binders, as necessary. The contents of each proposal volume are described in the ITO paragraph as noted in the table below:

file://///periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR15.DOC%23b15505 file://///periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR15.DOC%23b15506 http://www.fedbizopps.gov/ file://///periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/Far02.doc%23T2101 file://///periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR03.DOC%23b3104

Table 2.2 - Proposal Organization

VOLUME ITO

Paragraph

Number

VOLUME TITLE COPIES PAGE

LIMIT

I 3.0 Administrative Paper: Original and 1 copy 10 pages

II 4.0 Technical/Technical Risk Paper: Original and 1 copy 50 pages

III 5.0 Past Performance Paper: Original and 1 copy 1-3 pages per reference

IV 6.0 Cost/Price Paper: Original and 1 copy Unlimited

V 7.0 Task Order 0001 Paper: Original and 1 copy 10 pages

L.2.2.1 Page Limitation. All material must be contained within the page limit identified for each volume or appendix. The page limitations specified in Table 2.2 above shall be treated as maximum limits to assist in the evaluation of each proposal. Total page count will be based on the printed proposal submission. Each page shall be counted toward the above page limits except for cover pages; tables of contents; tabs; glossaries; list of key terms;

appendices to technical volume such as tables, charts, graphs, and figures; consent letters; and client authorization letters; company financial statements; model contract, and Small Business Subcontracting Plan. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal and (for paper copies) will be returned to the offeror as soon as practical. Page limitations shall be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the offerors.

L.2.2.1.1 Page Size and Format. These instructions shall apply to both electronic and paper copy proposals.

(a) Page size shall be 8.5 x 11 inches, not including foldouts. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least one-inch margins on the top, bottom and side margins. Pages shall be numbered sequentially by volume. These page format restrictions shall also apply to responses to Evaluation Notices (ENs) and Final Proposal Revisions (FPRs), if required.

(b) Legible tables, charts, graphs, and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, 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. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics; not for pages of text.

(c) Double-sided printing is acceptable, but will count as two pages. Each printed side of foldout pages shall count as two pages each. The background color of each page of the proposal submission shall be white or ivory paper only. These page format restrictions shall also apply to responses to ENs and FPRs.

(d) Text type shall be Times New Roman or Arial. Except for the reproduced sections of the solicitation document, the text size shall be no smaller than 12 point. Text lines will be no less than single-spaced. For tables, charts, graphs and figures, the text shall be no smaller than 8 point. These limitations shall apply to both electronic and hard copy proposals.

L.2.2.2 Cost or Pricing Related Data. Submit an electronically encoded cost/price model in support of the proposed price. All cost or pricing data shall be addressed ONLY in the Cost/Price Proposal and Contract Documentation

Volumes. Cost trade-off information, work hour estimates, and material kinds and quantities may be used in other volumes only as appropriate for presenting rationale for alternatives or design and trade-off decisions. Any cost/price model submitted must be consistent with your approved estimating system and must duplicate the logic and mathematical formulas reflected in the paper copy of your proposal. All cells in the Excel document shall be unprotected and show all formulas used. Cost/price models submitted must comply with the following format requirements:

(a) Data file should be submitted on a CD.

(b) Data file should be MS-Excel 2013 file format or compatible format.

(c) Viewing Environment. The Government anticipates viewing the electronic submittals with the following computer software and hardware: 1) IBM-compatible systems, 128 MB of RAM, nominal 17 inch color monitors, and standard CD ROM readers, 2) Windows 7 operating system, 3) Adobe Reader, Microsoft Office 2013, and Internet Explorer 11.

L.2.2.3 Classified Information. Where classified information is required in your response, it shall be provided as a classified volume or a classified supplement and bound in a single classified addendum. If a classified supplement is used, each entry in the classified addendum shall be referenced to the proposal volume, page number, and paragraph number to which it applies. Similarly, a reference shall be placed in the unclassified volume where the classified insert applies, giving the page and paragraph numbers within the addendum where it can be found.

Binding shall conform to the same directions as those given in this ITO for unclassified portions. The classified addendum shall be separately bound with an applicable security designation color cover, conforming to the DD

Form 254. Pages in a classified addendum will be included in the page count for the applicable volume. The classified addendum shall be submitted according with DoD 5220.22-M National Industrial Security Program

Operating Manual, also the company must provide CAGE Code which can be verified using the Industrial Security

Facilities Database (ISFD). Classified information will be clearly marked and shipped in accordance with DoD

52200.22-M and AFI 31-401 to this address:

“Outer Address”

DEPARTMENT OF THE AIR FORCE

AFTAC/SO

10989 South Patrick Drive

Patrick AFB, FL 32925-3002

“Inner Address”

AMIC Det 2 OL/PKA (Patrick AFB, FL)

ATTN: Joyce Hongell

L.2.2.4 Cross-Referencing. To the greatest extent possible, each volume shall be written on a stand-alone basis so that its contents may be evaluated with a minimum of cross-referencing to other volumes of the proposal.

Information required for proposal evaluation, which is not found in its designated volume, will be assumed to have been omitted from the proposal. Cross-referencing within a proposal volume is permitted where its use would conserve space and/or improve clarity.

L.2.2.5 Indexing. Each volume shall contain a detailed table of contents to delineate the subparagraphs within that volume. Paper copies shall use tab indexing to identify sections. The indices will not count against the page count.

L.2.2.6 Glossary of Abbreviations and Acronyms. 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.2.7 Binding and Labeling. Each volume of the proposal should be separately bound in a three-ring, loose leaf binder permitting the volume to lie flat when open. Staples shall not be used. A cover sheet should be bound in each book, clearly marked as to volume number, title, copy number, solicitation identification, and the offeror's name. The same identifying data should be placed on the spine of each binder. Elaborate format and binding are http://www.dtic.mil/whs/directives/infomgt/forms/forminfo/forminfopage51.html http://www.dtic.mil/whs/directives/infomgt/forms/forminfo/forminfopage51.html neither necessary nor desirable. All unclassified document binders shall have a color other than red or other applicable security designation colors. Be sure to apply all appropriate markings including those prescribed in accordance with FAR 52.215-1(e), Restriction on disclosure and use of data, and FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information on both the paper copy and the CD.

L.2.3 Electronic Offers.

The content and page size of electronic copies must be identical to the hard copies. For electronic copies, indicate on each CD the volume number and title. Use separate files to permit rapid location of all portions, including subfactors, exhibits, annexes, and attachments, if any. The offeror shall submit all volumes in electronic format, using recordable CDs. Each volume shall be in a different directory on a CD. If files are compressed, the necessary decompression program must be included. The electronic copies of the proposal shall be submitted in a format readable by Microsoft (MS) Office Word 2013, MS Office Excel 2013, MS Office Project 2010, and MS Office

Power Point 2013, as applicable. The offeror shall not embed sound or video files into the proposal files. Minimize the use of scanned images and keep embedded graphics as simple as possible. In the event that paper copies and electronic copies of a proposal are submitted and if there are any discrepancies between the paper copies and the electronic copies of the proposal, the hard paper will be used for evaluation.

L.2.4 Distribution.

L.2.4.1 Submit your proposal to arrive no later than time and date stated on the first page of the solicitation. The

"original" proposal shall be identified. Proposals shall be addressed to the CO and mailed or hand-carried to (If the proposal is classified, use paragraph 2.2.3 for mailing.):

AMIC Det 2 OL/PKA (Patrick AFB, FL)

ATTN: Joyce Hongell

L.2.4.2 All proposals delivered in response to this solicitation shall reflect the following information on the address label:

(a) Solicitation Number: FA7022-17-R-0002.

(b) Legend, “TO BE DELIVERED UNOPENED TO THE CONTRACTING OFFICER”

(c) Volume and copy numbers contained in each box.

IMPORTANT NOTICE: PAGES OR SECTIONS, WHICH DO NOT MEET THE FORMAT REQUIREMENTS

TO INCLUDE FONT SIZE, MAY NOT BE EVALUATED.

L.3.0 Volume I – Administrative

L.3.1 Model Contract/Representations and Certifications. The purpose of this volume is to provide information to the Government for preparing the contract document and supporting file. The offeror's proposal shall include a signed copy of the offer and Sections A through K. The "original" copy should be clearly marked under separate cover and should be provided without any punched holes. This includes:

L.3.1.1 Section A – Solicitation/Contract Form. Complete blocks 13 through 18 of the SF 33. In doing so, the offeror accedes to the contract terms and conditions as written in the RFP Sections A through K, which constitute the model contract. Note: An official having the authority to bind the offeror contractually must sign the SF 33.

One copy of SF 33 must bear an original signature.

file://///periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR52.215.doc%23b522151 file://///periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR03.DOC%23b31044

L.3.1.2 Section B – Supplies or Service and Cost/Prices.

L.3.1.3 Section F – Deliveries or Performance. Acknowledge content of Section F.

L.3.1.4 Section G - Contract Administrative Data.

L.3.1.5 Section H – Special Contract Requirements. Not Applicable.

L.3.1.6 Section I – Contract Clauses.

L.3.1.7 Section K - Representations, Certifications, and other Statements of Offerors. Completed representations, certifications, acknowledgments, and statements. (Note: Offerors must also comply with the System for Award

Management) requirements of FAR 52.204-8);

L.3.3 Other Information Required

L.3.3.1 Authorized Offeror Personnel. Provide the name, title, and telephone number of the company/division point of contact regarding decisions made with respect to your proposal and who can obligate your company contractually. Also, identify those individuals authorized to negotiate with the Government. Finally, please provide the name, title, and telephone number of the CEO, Division President, or Vice President of the offeror.

L.3.3.2 Government Offices. Provide the mailing address, telephone; fax number, e-mail address (if known), and facility codes for the cognizant Contract Administration Office and DCAA for the prime contractor and major subcontractors. Also, provide the name and telephone and fax number for the Administrative Contracting Officer

(ACO).

L.3.3.3 Company/Division Address, Identifying Codes, and Applicable Designations. Provide company/division's street address, county and facility code; CAGE code; DUNS code; TIN; size of business (large or small); and labor surplus area designation. This same information must be provided if the work for this contract will be performed at any other location(s). Provide the same information for your major subcontractors. List all locations where work is to be performed and indicate whether such facility is a division, affiliate, or subcontractor, and the percentage of work to be performed at each location.

L.3.3.4 Attachments to the Model Contract. The offeror shall provide the following as attachments to the model contract:

L.3.3.4.1 Participation of Small Disadvantaged Businesses (SDB). Pursuant to the requirements of FAR 52.219-24, each offeror must provide, with its offer, targets, expressed as dollars and percentages of total contract value, for

SDB participation in any of the North American Industry Classification System (NAICS) Industry Subsectors as determined by the Department of Commerce. NAICS codes and titles are posted at:

http://www.census.gov/epcd/naics02/naicod02.htm. The targets may provide for participation by a prime contractor, joint venture partner, teaming arrangement member, or subcontractor; however, the targets for subcontractors must be listed separately.

L.3.3.4.2 Subcontracting Plan – Participation of Small Business (SB), Historically Black Colleges and Universities, or Minority Institutions (HBCU/MI). If the offeror is other than a small business, the offeror shall submit a Small

Business Subcontracting Plan in accordance with FAR 52.219-9 that also identifies and specifies the extent of offeror's commitment to the participation of small businesses (SB), historically black colleges or universities

(HBCU) and minority institutions (MI), whether as joint venture members, teaming arrangement partners, or subcontractors. If applicable, submit a copy of your approved Master Plan. In the event the offeror has negotiated a comprehensive subcontracting plan pursuant to DFARS 219.702, the offeror must submit the information that identifies and specifies the extent of its commitment to the participation of SB, HBCU and MI.

file://///periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR52.215.doc%23b5221924 http://www.census.gov/epcd/naics02/naicod02.htm file://///periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR52.215.doc%23b522199

L.3.3.4.3 Associated Contractor Agreements (ACAs). Include Associated Contractor Agreements, if applicable.

(Note: ACAs for existing AFTAC contractors which are not part of the offeror’s teaming partners may be accomplished after contract award.)

L.3.3.4.4 Acknowledgment of all amendments issued (if applicable);

L.3.3.4.5 Statement of the period for which the proposal is valid (not less than 180 calendar days);

L.3.3.4.6 Statement/documentation of current facility clearance and key personnel clearances in place;

L.3.3.4.7 Evidence of a Government-approved cost accounting system;

L.3.3.4.8 Organizational Financial Information. Submit copies of your latest available financial statement covering the organization(s), which will perform the contract. Include any information, which may have a bearing on your ability to handle the financial management of the contract. If you are proposing a joint venture, describe how you will handle financial matters.

L.3.3.4.9 GFP and/or Base Support Requirements. If the offeror requires the use of Government furnished items other than those specified in the ESAS 2 or Task Order 0001 PWS(s), the offeror shall provide a listing including quantity, federal stock number, nomenclature, date needed and duration of availability, rental value per FAR 45.1 and 45.2, reason for need, and cross reference to cost/price volume paragraphs which pertain to GFP and/or base support. The offeror shall also provide the written authorization from the cognizant ACO, as applicable. The offeror shall supply this information in the format shown in Table 3.3 below.

Table 3.3 - Required Information for Using GFP/Base Support

Quantity

Federal

Stock #

Nomen-clature

Duration of Need

Rental

Value

Reason for Need

Cross Ref. to

Cost Prop

L.4.0 Volume II – Technical Volume (Factor 1)

L.4.1 General

L.4.1.1 The Technical Volume must be specific and complete. Legibility, clarity, and coherence are very important.

Your responses will be evaluated against the Technical Volume subfactors defined in Section M, Evaluation Factors for Award. Using the instructions provided below, provide as specifically as possible, the actual methodology/approaches you would use for accomplishing/satisfying these subfactors. All the requirements specified in the solicitation are mandatory. By your proposal submission, you are representing that your company will perform all the requirements specified in the solicitation. It is not necessary or desirable for you to tell us so in your proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation

L.4.2 Format and Specific Content

L.4.2.1 Technical. In the technical volume, address your technical solution for meeting or exceeding the

Government’s minimum performance or capability requirements of each technical subfactor. The information provided should be in sufficient detail to allow the Government to assess the offeror’s understanding of and capability to perform the work required by the PWS(s). Your proposal must describe the capability of your organization to perform this contract including pertinent aspects of the proposed approach such as teaming or subcontracting arrangements. Offerors shall assume that the Government has no prior knowledge of their facilities and experience, and will base its evaluation on the information presented in the offeror’s proposal. It is your responsibility to ensure the completeness of your proposal. The Government evaluation team has been instructed to file://///periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR45.doc%23s451 file://///periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR45.doc%23s452 evaluate on the basis of the information provided in the proposal. The Government shall not assume that an offeror possesses any capability unless specified in the proposal.

L.4.2.1.1 Technical Risk. Address technical risk associated with those aspects of your proposed technical approach you consider to have the potential for disruption of schedule, increased costs, degradation of performance, the need for increased Government oversight, or the likelihood of unsuccessful contract performance. Classify each risk in accordance with DoD Source Selection Procedures Table 3, Technical Risk Rating. Provide the rationale for each risk and its rating, including quantitative estimates of the impact on cost, schedule, and performance. Describe the impact of each identified risk in terms of its potential to interfere with or prevent successful accomplishment of other contract requirements (for example: PWS requirements), whether or not those requirements are identified as subfactors. Propose a realistic “work-around” or risk mitigators for identified risks that will eliminate or reduce risk to an acceptable level. Identify and classify any new risks introduced by such risk mitigation.

L.4.2.2 Volume Organization. The Technical Volume shall be organized according to the following general outline:

(1) Table of contents to include list(s) of Tables/Drawings/Matrices

(2) Glossary of key words and acronyms

(3) Short introduction and summary

(4) Cross Reference Matrix

(5) Subfactor 1

(6) Subfactor 2

(7) Subfactor 3

(8) Subfactor 4

(9) Subfactor 5

(10) Subfactor 6

L.4.2.3 Evaluation Subfactors.

(1) Subfactor 1: Demonstrates scientific and modeling expertise for NUDET and other directed technology detection applications and phenomena. The offeror should provide a separate section for their expertise with NUDET, directed technology detection, ground-based detection, and subsurface detection. This section should provide insight into the offeror’s expert technical knowledge of nuclear weapon design, physics, and the ability of the offeror to work with and use NUDET and directed technology detection applications and phenomena in the development of analytical models and simulations. The offeror shall identify business and key personnel to demonstrate this knowledge and expertise required. The offeror shall include their technical approach to performing PWS tasks to include modeling of various signal sources and the sensor outputs. The offeror shall describe any models the offeror may have developed or used to perform these functions. This section should also address the offeror’s collaborative efforts demonstrated within the community to resolve scientific and technical challenges associated with phenomena modeling and the integration of emerging technologies and sensor data streams.

(2) Subfactor 2: Demonstrates sensor data analysis integration and fusion expertise. This section should provide insight into the technical ability of the offeror to use and tailor digital signal processing analytical tools and applications and develop algorithms, methods, and tools to improve the analysis of multi-phenomena and multi-platform data sets associated with detection from relevant satellite, ground, and subsurface sensors. The offeror shall describe their knowledge of sensor data analysis associated with their technical approach to performing PWS tasks to include algorithm, methods, and tools the offeror may have developed or used to perform data analysis and the development of the resulting technical/scientific reports. The offeror shall describe their expertise of sensor data fusion to include algorithm, methods, and tools the offeror may have developed or used to improve data analysis for the resulting technical/scientific reports. The offeror shall identify business and key personnel to demonstrate this knowledge and expertise required. The response should also address the offeror’s collaborative efforts demonstrated within the community to resolve technical problems associated with the integration and fusion of emerging technologies and overcoming large data collection analytics and reduction obstacles in the development of analytical algorithms, methods, and tools.

(3) Subfactor 3: Demonstrates software development and test expertise in cross domain solutions. This section should provide insight into the offeror’s expertise in systems engineering, software development, system verification/validation, information assurance, interoperability, and configuration management processes in compliance with current DoD policy and best commercial practices. The offeror should describe their ability to move a capability from a research concept at a Transition Readiness Level (TRL) of 3 to an operational capability.

The offeror shall describe their technical ability to accomplish requirements analyses and decomposition of performance requirements into derived technical requirements. This section should include the offeror’s expertise with baselines, hardware and software system development, testing, and metric. Insight in to the offeror’s expertise in data processing technologies for the integration and correlation of multi-source data types used in integrated cross domain prototypes and systems should also be provided. The offeror shall identify business and key personnel to demonstrate this knowledge and expertise required. The offeror shall include their technical approach associated with the development of modular open software architectures and information technology enterprise strategies in conformance to DoD mandated software development requirements and industry software standards. Describe any existing software and information assurance certifications currently held by the offeror and provide recent appraisal results or appraisal disclosure statements describing software engineering expertise in relevant process areas.

Offerors are cautioned that a simple statement or claim of a maturity level, e.g. CMMI Level 4, is not considered sufficient to describe the offeror’s software engineering process area maturity.

(4) Subfactor 4: Program management including Subcontracting Plan and Small Business Participation.

The offeror shall address their approach to program and risk management. This section should include the offeror’s capabilities, labor categories, subcontract management (including small business and SDB concerns provided in

Section L paragraphs 3.3.4.1 and 3.3.4.2), quality, risk mitigation, and personnel practices to ensure successful support to the mission throughout the life of this contract. The section shall describe how the offeror will provide flexibility to meet changing workloads, priorities, contingencies, surge capabilities, and quick response requirements while still ensuring a quality service will be delivered to meet the requirements. The offeror shall include plans for recruiting and retaining a robust, highly skilled technical workforce that is in low density and high demand to accomplish the PWS tasks.

(5) Subfactor 5: Proposed Technical Approach for Task Order 0001. See paragraph L.7.0 below. (Include as a separate volume).

(6) Subfactor 6: Security Clearance Requirements. This section should provide insight into the offeror’s capability to obtain/maintain the necessary security clearances to meet the contractual DD 254 requirements at

Attachment 2. The offeror must possess a Top Secret facility clearance on the first day of contract performance.

The offeror’s key personnel must be cleared for Top Secret information and eligible to be granted access to

Sensitive Compartmented Information (SCI) based on a single scope background investigation completion on the first day of contract performance. The proposed staff for Task Order 0001 must have the appropriate clearance for the work to be performed on the first day of contract performance. The offeror shall provide a list of key personnel and the staff proposed for Task Order 0001 with their security clearance access and PWS paragraph they will support.

L.5.0 Volume III - Past Performance (Factor 2)

L.5.1 General

Each offeror shall submit a past performance volume with its proposal, containing past performance information in accordance with the format contained in Attachment 8. This information is required on the offeror and all subcontractors, teaming partners, and/or joint venture partners who are proposed to perform 15 percent or more of the proposed effort based on the total proposed price or perform aspects of the effort the offeror considers critical to overall successful performance. Offerors are cautioned that the Government will use data provided by each offeror in this volume and data obtained from other sources in the evaluation of past performance.

Along with the information required in this paragraph, 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.5.2 Early Proposal Information

To permit the Past Performance evaluation team to conduct its assessment more efficiently, early submission of the past performance volume before the required submission date for the rest of the proposal is desirable. The questionnaire should be sent directly to the Government Contracting Officer. Each offeror is requested to submit

Volume III, Past Performance, on 17 April 2017. Failure to submit early proposal information will not result in offeror disqualification.

L.5.3 Relevant Contracts

Submit information in accordance with Attachment 10: Past Performance Information on a maximum of three (3) recent contracts that you consider most relevant in demonstrating your ability to perform the proposed effort. Also include information on 2 recent contracts performed by each of your teaming partners and significant subcontractors that you consider most relevant in demonstrating their ability to perform the proposed effort. Include rationale supporting your assertion of relevance. For a description of the characteristics or aspects the Government will consider in determining recency and relevance, see Section M002(c). Recent contracts, for the purposes of this solicitation, are defined as those where work was performed, at some point, during the last three (3) years from RFP release date. Past performance information that fails this condition will not be evaluated.

L.5.3.1 Specific Content. Offerors are required to explain what aspects of the contracts are deemed relevant to the proposed effort and to what aspects of the proposed effort they relate. This may include a discussion of efforts accomplished by the offeror to resolve problems encountered on prior contracts as well as past efforts to identify and manage program risk. Merely having problems does not automatically equate to a limited or no confidence rating, since the problems encountered may have been on a more complex program, or an offeror may have subsequently demonstrated the ability to overcome the problems encountered. The offeror is required to clearly demonstrate management actions employed in overcoming problems and the effects of those actions in terms of improvements achieved or problems rectified. This may allow the offeror to be considered a higher confidence candidate. For example, submittal of quality performance indicators or other management indicators that clearly support that an offeror has overcome past problems is required. Categorize the relevant information into the specific Technical subfactors and Cost/Price factor used to evaluate the proposal.

L.5.3.2 Questionnaires. The Government requests the offeror send out past and present performance questionnaires

(Attachment 11) to each of the points of contact (POCs) identified in the past performance volume. Offerors are recommended to encourage agencies to complete the questionnaire and return it directly to the Contracting Officer

NO LATER THAN 17 April 2017. Once the past and present performance questionnaires are completed by the

POCs, the information contained therein shall be considered sensitive and shall not be released to you, the offeror.

A cover letter should be used for transmitting the questionnaire to each POC to ensure it is routed properly.

L.5.3.3 Organizational Structure Change History. Many companies have acquired, been acquired by, or otherwise merged with other companies, and/or reorganized their divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the time of performance of relevant 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 your company. A pamphlet or other commercial document describing such reorganizations may suffice. As part of this explanation, show how these changes impact the relevance of any efforts you identify for past performance evaluation/performance confidence assessment. Since the Government intends to consider past performance information provided by other sources as well as that provided by the offeror(s), your "roadmap" should be both specifically applicable to the efforts you identify and general enough to apply to efforts on which the Government receives information from other sources.

L.6.0 Volume IV – Cost/Price (Factor 3)

L.6.1 General Instructions

L.6.1.1 Cost/Price Reasonableness and Realism. This section is to assist you in submitting data other than certified cost or pricing data that is required to evaluate the reasonableness of your proposed cost/price. Compliance with these requirements is mandatory and failure to comply may result in rejection of your proposal. Note that unrealistically low or unreasonably high proposed costs or prices, initially or subsequently, may be grounds for eliminating a proposal from competition either on the basis that the offeror does not understand the requirement or has submitted an unrealistic proposal. Additionally, unbalanced pricing poses an unacceptable risk to the

Government and may be a reason to reject an offeror’s proposal. Offers should be sufficiently detailed to demonstrate their reasonableness. The burden of proof for credibility of proposed costs/prices rests with the offeror.

L.6.1.2 Estimating Techniques and Methods. When responding to the Cost/Price Volume requirements in the solicitation, the offeror and associated subcontractors may use any generally accepted estimating technique, including contemporary estimating methods (such as Cost-to-Cost and Cost-to-Non-Cost Estimating Relationships

[CERs], commercially available parametric cost models, in-house developed parametric cost models, etc.), to develop their estimates.

L.6.1.3 Cost/Price Data. Information beyond that required by this instruction shall not be submitted, unless you consider it essential to document or support your cost/price position.