Metis_II_Amendment_1.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 Summary of Changes

1. CONTRACT ID CODE PAGE OF PAGES

S 1 18

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

16C. DATE SIGNED

BY 30-Oct-2015

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 FA7022-15-R-0007

X 9B. DATED (SEE ITEM 11)

23-Oct-2015

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

30-Oct-2015

CODE

AF ISR AGENCY/A7KR

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:

FA7022-15-R-0007

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

The following items are applicable to this modification:

UREASON FOR MODIFICATION:

The purpose of this amendment is to incorporate revisions to the Request for Proposal. Bold letters and a vertical line to the right delineate the revisions.

A. Section J: List of Documents, Exhibits and Other Attachments

1. Attachment 1 and 5 – Basic and Task Order 0001 Performance Work Statements revised.

2. Attachment 4 – Revised, FY16 column added.

Section L: Instructions, Conditions, and Notices to Offerors

1. Section L, Paragraph L.4.2, Section 3 – Table corrected

B. ALL OTHER TERMS AND CONDITIONS REMAIN UNCHANGED.

SUMMARY OF CHANGES

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

The following have been modified:

USECTION J

ATTACHMENT

TITLE

DATE

PAGES

Classified Performance Work Statement (Basic) (Forwarded under separate cover) 29 Oct 2015 14

DD Form 254

29 Jun 2015

Labor Category Descriptions 31 Jul 2015

Labor Category Rates for Task Orders 29 Oct 2015

Classified Performance Work Statement - Task Order 0001 (Forwarded under separate cover)

29 Oct 2015

EXHIBITS

TITLE

DATE

PAGES

A

DD Form 1423-1, Contract Data Requirements List (CDRLs): A001- A009, A00A - A00B

13 May 2015

B

Past Performance Information

N/A

C

Past Performance Questionnaire and Cover Letter

N/A

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

USECTION L

PART IV—REPRESENTATIONS AND INSTRUCTIONS

SECTION L

Instructions, Conditions, and Notices to Offerors

U1.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. Any reference to day(s) stated in the Request for Proposal, attachments and other contractual documents should be considered as “calendar” days unless specifically stated otherwise. Non-conformance with the instructions provided in this ITO may result in an unfavorable proposal evaluation.

(b) The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation of the offeror’s capabilities to perform the requirements outlined in the PWS. 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. 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 Subfactors under Section M, Evaluation Factors for Award.

(c) Elaborate brochures or documentation, binding, detailed artwork, 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.

1.1 General Information

1.1.1 Point of Contact

The Contracting Officer (CO) is the UsoleU 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:

25 AF/PKR

Attn: Kim M. Pattan 10989 South Patrick Drive Patrick Air Force Base, Florida 32925 Email: Ukim.pattan@us.af.milU Telephone: (321) 494-5452 mailto:kim.pattan@us.af.mil

1.1.1.1 Performance Work Statement

The PWS for this acquisition is classified. Procedures for obtaining the PWS will be furnished by contacting AFTAC/TM, Ms. Maria Vasile, (321) 494-8349 or e-mail: Umaria.vasile.3@us.af.mil.U

1.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 preaward 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.

1.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 additional or substitute pages of the initial proposal.

1.1.4 Electronic Reference Documents

All referenced documents for this solicitation are available on the Federal Business Opportunities (FedBizOpps) website at Uhttp://www.fedbizopps.govU. Potential offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

1.1.5 Communications

Exchanges of source selection information between Government and offerors will be controlled by the CO.

E-mail 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 UFAR 2.101U & U3.104U” in the Subject line.

1.1.6 Notice to Offerors

Notice to Offeror(s)/Supplier(s): Funds are not presently available for this effort. No award will be made under this solicitation until funds are available. The Government reserves the right to cancel this solicitation, either before or after the closing date. In the event the Government cancels this solicitation, the Government has no obligation to reimburse an offeror for any costs.

1.2 Organization/Number of Copies/Page Limits

The offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 1.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 copies as specified in Table 1.2. The attachments identified in the table shall be separately bound in three-ring, loose-leaf binders, as necessary. Only one CD-ROM is required, please see paragraph 1.3 (e) below for details. The contents of each proposal volume are described in the ITO paragraph as noted in the table below:

Table 1.2 - Proposal Organization

VOLUME ITO

Paragraph

Number

VOLUME TITLE COPIES PAGE LIMIT

I 2.0 Administrative Paper: Original and 1 copy Unlimited II 3.0 Technical Approach Paper: Original and 3 copies 60 pages mailto:maria.vasile.3@us.af.mil http://www.fedbizopps.gov/

III 4.0 Cost/Price Proposal Paper: Original and 1 copy Unlimited IV 5.0 Past Performance* Paper: Original and 3 copies 1-3 pages per reference V 6.0 Task Order 0001 Paper: Original and 3 copies 10 pages

* Organizational structure change history is excluded from the page limitation of the Past Performance volume

1.2.1 Page Limitations

All material must be contained within the page limit identified for each volume or appendix. The page limitations specified in Table 1.2 above shall be treated as maximums. 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, resumes, glossaries, list of key terms, appendices to Technical volume, consent letters, and client authorization letters, and company financial statements. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal. Page limitations may be placed on responses to ENs. The specified page limits for EN responses will be identified in the letters forwarding the ENs to the offerors.

1.2.1.1 Page Size and Format

(a) A page is defined as each face of a sheet of paper containing information. When both sides of a sheet display printed material, it shall be counted as two pages. Page size shall be 8.5 x 11 inches, not including foldouts. Text type shall be Times New Roman or Arial. Except for the reproduced sections of the solicitation document, the text size shall be no less than twelve (12) point. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least 1-inch margins on the top and bottom and ¾-inch side margins. Pages shall be numbered sequentially by volume. These page size and format restrictions shall apply to responses to ENs.

(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. For tables, charts, graphs and figures, the text shall be no smaller than ten (10) point.

1.2.2 Cost or Pricing Related Data

All cost or pricing data shall be addressed ONLY in the Administrative, Cost/Price and Task Order 0001 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. These limitations shall apply to both electronic and hard copy proposals.

1.2.3 Classified Information

The Government desires that classified information not be included as part of your proposal. If it is absolutely necessary to provide classified information in your response, it shall be provided as a classified supplement and bound in a single classified addendum to the appropriate proposal volume. 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 UDD Form 254U, and the Security http://www.dtic.mil/whs/directives/infomgt/forms/forminfo/forminfopage51.html

Classification Guide provided in this solicitation. Pages in a classified addendum will be included in the page count for the applicable volume.

1.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 without impairing clarity.

The offeror shall provide a Solicitation Cross Reference Matrix indicating by ITO or PWS paragraph number, the corresponding proposal paragraph in that section which addresses the referenced item.

If this matrix conflicts with any other requirement, direction, or provision of this solicitation, the other reference shall take precedence over this matrix. Additionally, to the extent this matrix discloses details as to the extent or manner by which the Government intends to evaluate offeror’s proposals for award, Section M references in the matrix are for information purposes only, and the Government shall be obligated to evaluate proposals solely in conformance with the provisions of the Section M of the solicitation.

An example of the format is shown below:

SOLICITATION CROSS REFERENCE MATRIX

REQ. WORK WBS CLIN Section Section Proposal SOW CDRL IMP SOO

DOC REQ LEVEL L M

3.2.2 Design B 2 0001 N/A

3.3.3 Build A 2 0002 3.B.2 A001

1.2.5 Indexing

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

1.2.6 Glossary of Abbreviations and Acronyms

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

1.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. 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 UFAR 52.215-1(e)U, Restriction on disclosure and use of data, and UFAR 3.104-4U, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information on both the paper copy and the CD.

1.3 Electronic Offers

(a) To enable the Government to successfully view the proposals electronically, the offeror shall submit their proposal in the Adobe Portable Document (PDF), Microsoft Word, or Microsoft Excel format. (Note: See 1.3 (g) for specific instructions for Cost proposal.) These file formats are expected to be exact duplicates of the paper copies. The Government will use the electronic copies in the evaluation process. The Government may use the electronic/CD proposal for all purposes; however, there is no requirement for the Government to compare or verify the consistency of the electronic proposal to the paper proposal. In the case of an identified dispute or variation in content, the paper/hardcopy submitted proposal shall be deemed and treated as the official version for all purposes.

(b) File Preparation. The offeror shall generate “bookmarks” within each PDF file for at least each section and subsection of the document. Bookmarks shall be generated based on indexed entities appearing in the document table of contents. The offeror has the option of generating “thumbnails” within the PDF files as well. The minimum requirement for hypertext links is an overall proposal table of contents linked to each volume and a table of contents within each PDF file linked to each section of the file. Additional hypertext links within the proposal are at the offeror’s discretion. The use of thumbnails or additional hypertext links will not influence the evaluation. The PDF file has a built in security function. The offeror shall set all security options in each PDF file to “allowed.” All text, including table and figure identifiers, shall be indexed and 100% searchable text. All text shall be displayed as a font and not displayed as a bitmap in any proposal volume or appendix to facilitate the ability to copy and paste to another document.

(c) Font and Page Setup. Text font and layout shall be as stated for paper copies. Hypertext links shall be the same minimum font size. The preferred method of implementing hyperlinks is to indicate the hyperlink by blue font color and establishing the hyperlink in Acrobat with “invisible rectangle” with “no outline.” However, the offeror may indicate hyperlinks by any color font or with a visible rectangle.

(d) Other Requirements. 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.

(e) Proposal Format and Structure. Each volume of the electronic proposal shall be in its own subdirectory on one CD-ROM, sequentially labeled Volume 1 through Volume 5.

(f) Proposal Table of Contents file (TBLCONT.PDF). This file serves as a table of contents for the proposal information. The offeror shall provide the capability to “jump” from this file using hypertext links to all other PDF files on the CD-ROM. Also, include the list of key terms used in the proposal with their definitions, and a list of acronyms and abbreviations used in the proposal.

(g) Cost Data File (COST.XLS). Submit an electronically encoded cost/price model in support of the proposed price. 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. Cost/price models submitted must comply with the following format requirements:

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

(ii) Data file should be .XLS file format (MS-Excel 2007 or earlier) compatible format.

(iii) This file must cross-reference to Section B, Contract Line Item Numbers (CLINs).

(iv) Ensure formulas are present in the Excel spreadsheet.

(h) 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 XP Professional operating system, 3) Adobe Reader 7.0, Microsoft Office 2007, and Internet Explorer 7.0.

1.4 Distribution

The "original" proposal shall be identified. Proposals shall be addressed to the CO and mailed or hand carried to the address stated on page 1 of the solicitation.

Submit your proposal to arrive no later than time and date stated on page 1 of the solicitation. All proposals delivered in response to this solicitation shall reflect the following information on the address label:

(1) Solicitation Number FA7022-15-R-0007

(2) The legend, “TO BE DELIVERED UNOPENED TO THE CONTRACTING OFFICER”

(3) The volume and copy numbers contained in each box

Be sure to advise the Administrative Contracting Officer(ACO) and the DCAA for prime and subcontractors that the proposal is "For Official Use Only" and "Source Selection Information--See UFAR 2.101U and UFAR 3.104U".

U2.0 Volume I – Administrative

The narrative summary of the entire proposal should be concise, to include addressing the significant risks, and highlighting any key or unique features, excluding cost/price. The salient features should tie in with Section M evaluation factors/subfactors. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal. Include a master table of contents of the entire proposal.

2.1 Model Contract/Representation and Certifications

The purpose of this volume is to provide information to the Government for preparing the contracted document and supporting file. The offeror’s proposal shall include a signed copy of the Model Contract and Sections A through K.

This includes the following:

2.1.1 Section A - Solicitation/Contract Form

Completion of blocks 12-16 and signature and date for blocks 17 and 18 of the SF-33. Signature by the offeror on the SF-33 constitutes an offer, which the Government may accept. The "original" copy should be clearly marked separately and should be provided without any punched holes.

2.1.2 Section B - Supplies or Services and Costs/Prices

Completed pricing information in Section B of the model contract.

2.1.3 Section G - Contract Administrative Data

Complete the fill-in required in contractor’s contract administration. If not applicable, state reason why.

2.1.4 Section H - Special Contract Requirements

2.1.5 Section I - Contract Clauses

Complete fill-ins as applicable.

2.1.6 Section K - Representations, Certifications, and other Statements of Offerors Completed representations, certifications, acknowledgments and statements. (NOTE: Offerors must comply with the Online Representations and Certifications Application (ORCA) requirements of FAR 52.204-8).

2.2 Exceptions to Solicitation Requirements

Offerors are required to meet all solicitation requirements, such as terms and conditions, representations and certifications, and Technical requirements, in addition to those identified as evaluation factors or subfactors.

Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken. Provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule, cost, and specific requirements of the solicitation. This information shall be provided in the format and content of Table 2.2.

Table 2.2 - Solicitation Exceptions

Solicitation Document

Page/ Paragraph

Requirement/ Portion Rationale

SOO, SOW, SPEC, Model Contract, ITO, etc.

Applicable Page and Paragraph Numbers

Identify the requirement or portion to which exception is taken

Describe why the requirement can/will not be met

2.3 Other Information Required

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

2.3.2 Government Offices

Provide the mailing address, telephone and fax numbers, email address (if known) and facility codes for the cognizant Contract Administration Office (ACO), DCMA, DCAA, and Government Paying Office.

Provide the same information for your major subcontractors. Additionally please provide a copy of your proposal to the cognizant DCAA and DCMA offices.

2.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). 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.

2.3.4 Attachments to the Model Contract

The offeror shall provide the following as attachments to the model contract:

2.3.4.1 Government Furnished Equipment (GFE) and/or Base Support Requirements

No GFE assigned to contractor, however, GFE will be provided at the Government facility.

2.3.4.2 Associate Contractor Agreements

Include Associate Contractor Agreements, if applicable.

2.3.4.3 Amendments

Acknowledgement of all amendments (if applicable).

2.3.4.4 Proposal Validity

Block 12 of the SF33 is hereby superseded with the following proposal Acceptance terms: Offeror's proposal is valid for a period not less than U180U days from the date of receipt of proposal.

2.3.4.5 Accounting System

Evidence of a Government-approved cost accounting system.

2.3.4.6 Clearances

Evidence of required personnel clearances.

2.3.4.7 8(a) Status If applicable, provide a copy of the letter from the Small Business Administration (SBA) showing proof of Section 8(a) status.

U3.0 Volume II - Technical Volume

3.1 General

The Technical Volume should be specific and complete. Legibility, clarity, and coherence are very important. Your responses will be evaluated against the Technical subfactors defined in Section M, Evaluation Factors for Award. UUsing the instructions provided below, provide as specifically as possible the actual methodology you would use for accomplishing/satisfying these subfactorsU. All the requirements specified in the solicitation are mandatory. By your proposal submission, you are representing that your firm will perform all the requirements specified in the solicitation. It is not necessary or desirable for you to tell us so in your proposal. UDo not merely reiterate the objectives or reformulate the requirements specified in the solicitationU.

3.2 Format and Specific Content

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

3.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 UDoDU 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 the successful accomplishment of other contract requirements (for example: PWS or specification 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.

3.2.2 Volume Organization

The Technical volume shall be organized according to the following general outline: 1. Table of Contents

2. List of Table and Drawings

3. Glossary

4. Cross Reference Matrix

5. Short introduction and summary

6. Subfactor One, Two, etc.

7. Risk Matrix

3.2.3 Subfactor 1: Demonstrated nuclear terminology recognition Contractor must provide a qualifications summary identifying a team with the following capabilities: This section should provide insight into the technical ability of the offeror to use an understanding of and experience with nuclear terminology associated with nuclear treaty monitoring in the identification of key words and phrases relating to the AFTAC nuclear mission during data capture. The offeror should describe their experience in collections, analysis, or mission support to AFTAC or a similar nuclear treaty monitoring organization. The offeror should list the years of experience to include collections, analysis, or mission support to AFTAC or a similar nuclear treaty monitoring organization or laboratory of each data capture employee who will be assigned to the proposed project.

The offeror shall describe plans to acquire, manage, and otherwise prepare to become fully operational and assume complete contract responsibility. This proposal shall include, but is not limited to:

1. Identify tasks, events, and milestones required for start-up activities.

2. How the offeror operates program management, quality control, and change management.

3. Describe provisions made for the acceptance, assembly, installation and configuration of computers, database, software, including projected times to begin activities outlined in Section M.

4. Describe any other aspects of the plan needed to clearly demonstrate a viable approach to full-scale maintenance and support within thirty-one (31) days after the contract start date.

5. Include a phase-in (31 days) plan, which provides specific definition of how the risks associated with service transition will be addressed; especially during the phase-in period and first quarter thereafter.

Clearly and fully describe how you propose to mobilize, train, observe, and retain personnel qualified to accomplish contract requirements. This plan shall separately address, but not be limited to, the following factors:

1. Describe in detail how you propose to accomplish training, indoctrination, and orientation of all employees.

2. How the offeror plans to provide the initial base of personnel qualified in the skills/background listed in PWS.

3. How the offeror plans to recruit and retain a qualified base of personnel and to maximize talent as the contract matures. Specifically address plans for one-time & recurring recruitment and cross training.

4. Résumés for the program manager down to, and including, the technical personnel. Provide evidence of commitment for all personnel whose résumés are submitted.

3.2.4 Subfactor 2: Demonstrated data capture experience

Contractor must provide a qualifications summary identifying a team with the following capabilities:

This section should provide insight into the technical ability of the offeror to perform capture and transfer of reports of various formats including hardcopy, microfiche, and film into electronic media format. The offeror should list the years of experience in data capture and format transition of each data capture employee who will be assigned to the proposed project. It should provide insight into the technical ability of the offeror to perform human and automated Optical Character Recognition (OCR) including 100 percent review of OCRed documents to identify and correct OCR errors of key words and phrases. The offeror should list the years of experience with OCR and content enhancement including the addition of metadata of each data capture employee who will be assigned to the proposed project. The response should document experience scanning and OCRing poor quality documents such as old (> 20 years) typewritten pages.

3.2.5 Subfactor 3: Demonstrated software development and testing experience Contractor must provide a qualifications summary identifying a team with the following capabilities:

This section should provide insight into the offeror’s technical ability to perform software development, validation, and testing for a web-based electronic archive. The offeror’s proposal must demonstrate their capability to maintain and enhance COTS/GOTS software and perform software programming and implementation using multiple developmental and computing platforms to include, but not limited to the following systems and languages: XML, NoSQL & SQL Databases, Java, Java Script, XPath, XQuery, XSLT, HTML, CSS, NetOwl Entity Extraction, LINUX/RedHat, Sun Coolstack Tomcat, & Adobe Flash.

The offeror should demonstrate in-depth knowledge by listing years of experience in the maintenance and enhancement of system administration tools for management of an electronic archive, the years of experience working with unstructured or semi-structured data technologies such as Mark Logic XML server and NetOwl entity extractor, and the years of experience developing, enhancing, or maintaining web-based interfaces for customer interrogation of an electronic archive of each software enhancement employee who will be assigned to the proposed project. The offeror should describe any existing software certifications currently held.

3.2.6 Subfactor 4: Demonstrated software sustainment, configuration, and operational experience Contractor must provide a qualifications summary identifying a team with the following capabilities:

The offeror should describe their approach to sustaining legacy software, tools, and databases while integrating system upgrades due to new data streams and requirements. The offeror should list the years of experience working with TS/SCI computer systems and the years of experience working with operational computer systems including responding to operational problems and patch installations within prescribed customer timelines of each software maintenance employee who will be assigned to the proposed project.

The offeror should describe their experience with DoD Architecture Framework and configuration control requirements.

3.2.7 Subfactor 5: Local Site Assistance, Security and Facilities Requirements This section should provide insight into the offeror’s capability to obtain/maintain the necessary security clearances to meet the contractual requirements. The offeror will be evaluated on the proposed approach and feasibility to provide on-site local O&M support at AFTAC located at 10989 South Patrick Drive, Patrick Air Force Base, Florida. The offeror must have the ability to have TS/SCI cleared personnel on-site to support software deliveries, testing, trouble shooting, training, connecting to other databases, document scanning and optical character recognition and tool related issues with the ability to provide assistance within four hours of request. The offeror's proposal must identify personnel with the appropriate Technical skills and security clearances to support the AFTAC mission for database, training or programming related issues as well as all software delivery and testing on site. The proposal must demonstrate that the personnel are familiar with DoD security procedures for protecting classified material and working on secure systems at the Top Secret SCI, SECRET, and unclassified level in a controlled TS Sensitive Compartmented Information Facility (SCIF), as well as the ability and transportation to access a United States Air Force Installation. The personnel must have the ability to obtain an authorization to courier-classified data to and from secure facilities. The offeror must also have safeguarding at the SECRET level for the storage of classified documents. Specifically, the proposal must demonstrate the following:

1. How the offeror can meet security requirements as required per the PWS.

2. How the offeror plans to establish and maintain security clearances for required personnel.

3. How the offeror plans to provide personnel for on-site assistance in required timelines as identified in the

PWS.

3.2.8 Subfactor 6: Program Management

The offeror should address their approach to program management. This section should provide insight into the offeror’s capabilities, subcontract management, quality, and personnel practices to ensure successful support to the mission throughout the life of this contract. The section should 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. The offeror should discuss plans for staffing levels/cross-utilization to accomplish PWS tasks, recruitment, retention, incentives, training, and compensation plan to maintain a robust and high skilled technical workforce. The response should document a minimum of three (3) years experience in managing large ($5M +) and complex software development efforts. The offeror must include a phase-in plan which provides specific definition of how the risks associated with service transition will be addressed; especially during phase-in period and first quarter thereafter. The offerors proposal must demontrate how program management, subcontract management, and personnel will be used to ensure operational mission activities will be completed as scheduled; a suitable corporate management ability to monitor, control, and assure quality of staff and quality of deliverable items; the ability to have personnel with appropriate technical skills locally available for onsite support and maintenance; and adequate ability to commence task performance rapidly and efficiently to meet mission objectives; the ability to respond quickly and efficiently to requirements by providing an adequate approach to accounting and traceability procedures for cost, schedule, and performance.

3.2.9 Subfactor 7: Task Order 0001

See paragraph 6.0 below (include in separate volume).

U4.0 Volume III - Cost/Price

Cost/Price Reasonableness and Realism. This section is to assist you in submitting information other than cost or pricing data that is required to evaluate the reasonableness (and, if applicable, realism, balance, and/or affordability) 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 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 (and, if applicable, realism, balance, and/or affordability). The burden of proof for credibility of proposed costs/prices rests with the offeror.

4.1 General Instructions

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

4.1.2 Cost/Price Data

Data beyond that required by this instruction shall not be submitted, unless you consider it essential to document or support your cost/price position. All information relating to the proposed price, including all required supporting documentation must be included in the section of the proposal designated as the Cost/Price volume and Administrative volume. UUnder no circumstances shall this data and documentation be included elsewhere in the proposal except where instructed.

4.1.3 Cost or Pricing Data Requirements

The Contracting Officer has determined that certified cost or pricing data is not required for this solicitation; however, IAW FAR 15.403-5(b)(1),(2), and (3), the offeror's format for submitting such information should be used unless the Contracting Officer decides that use of a specific format is essential and the format has been described in the solicitation.

In accordance with FAR 15.403-1(b) and 15.403-3(a), data other than cost or pricing data may be required to support price (or cost, as applicable) reasonableness (and, if applicable, cost realism). Data shall be provided in accordance with FAR 15.403-5. If, after receipt of proposals, the Contracting Officer determines that there is insufficient information available to determine price reasonableness and none of the exceptions in FAR 15.403-1 applies, the offeror shall be required to submit cost or pricing data.

4.1.4 Rounding

All dollar amounts provided shall be rounded to the nearest whole dollar. All loaded labor rates shall be rounded to the nearest penny.

4.2 Volume Organization

The Cost/Price volume shall consist of the following sections:

Section 1 – Table of Contents, summary descriptions of estimating, purchasing, and accounting systems, changes to estimating, accounting practices, or Cost Accounting Standards (CAS) Disclosure Statement.

The offeror will submit cost data for the period of performance: Ordering period (1 March 2016 – 31 December 2020) Show totals for each Fiscal Year.

• Direct Labor and Indirect Labor Rates. Completed schedules which display the proposed rates for direct labor (each category), fringe, overhead, G&A, Facilities Capital Cost of Money (FCCM), and other applicable burdens listed by Government fiscal year (1 October – 30 September). The allocation base for each direct and indirect rate should be in the proposal.

• Uncompensated Overtime. The decision to propose labor rates, which are based on hours in excess of 40 hours per week for employees who are exempt from the Fair Labor Standards Act, is the offeror’s decision.

If offeror chooses to include uncompensated overtime in the proposal, compliance with requirements of FAR 52.237-10 is mandatory.

• Compensation Plan for Professional Employees. In accordance with FAR 52.222-46, Evaluation of Compensation for Professional Employees, provide a total compensation plan setting forth the proposed salaries and fringe benefits for professional employees working on the contract.

• Inflation Rates/Factors. Provide the inflation rates used and the basis used to arrive at those rates and what sources were used.

• Other Direct Costs. Document direct cost items not covered elsewhere. Any consultation labor should be proposed as Other Direct Costs.

Section 2 - Offerors shall also include cost or pricing data and supporting data, to include estimating methodology to support a reasonableness determination and the Government's understanding of the proposed labor hour rates.

Provide supporting Forward Pricing Rate Recommendations and/or Agreements issued by DCMA or supporting audits issued by DCAA. If applicable, provide supporting documentation showing the development of composite and/or average rates from contractor fiscal year to Government fiscal year. If applicable, provide supporting documentation (DD 1861 and CAS-B) for proposed Facilities Capital Cost of Money.

Provide any other pricing data believed to be prudent and necessary to justify the cost/price proposal.

NOTE: All rates in Attachment 4 will be used to price subsequent task orders. Additionally, offeror is allowed to propose labor categories and indirect rates not listed.

Section 3 - Offerors will provide separate cost proposal for Task Order 0001 (CPFF). The cost proposal should be aligned with the PWS paragraphs and level of effort proposed to satisfy Technical Capability Factor 1. The offeror will provide a summary of total labor cost, total ODCs with G&A costs, and total proposal cost with all dollar amounts rounded to the nearest whole dollar. The rates provided in Attachment 4 will be used to price the task order.

The proposed Task Order 0001 price will be used for execution of this task order at the time of contract award.

4.3 Estimating Methodology

4.3.1 Estimating System

Provide a summary description of your standard estimating system or methods. The summary description shall cover separately each major cost element (e.g., Direct Material, Engineering Labor, Manufacturing Labor, Indirect Costs, Other Direct Costs, Overhead, G&A). Also, identify any deviations from your standard estimating procedures in preparing this proposal volume. Indicate whether you have Government approval of your system and if so, provide evidence of such approval.

4.3.2 Purchasing System

Provide a summary description of your purchasing system or methods (e.g., how material requirements are determined, how sources are selected, when firm quotes are obtained, what provision is made to ensure quantity and other discounts). Also, identify any deviations from your standard procedures in preparing this proposal. Indicate whether you have Government approval of your system and if so, provide evidence of such approval.

4.3.3 Accounting System

Provide evidence of either a DCMA or DCAA rating that its accounting system is adequate for determining costs applicable to the contract. Offerors lacking such a rating will be ineligible for award. Additionally, identify any deviations from your standard procedures in preparing this proposal.

4.3.4 Explanation of Estimating Methods Used

Explain the methodology used to estimate each cost element. As a minimum, provide the following information for each cost element. If a portion of the required information is not applicable for a particular cost element, so state.

4.3.4.1 Past Experience-Based Estimates

Where cost estimates are based upon past experience, identify the past experience, explain how the past experience relates to the current effort, including similarities and differences, and how cost data available from the past experiences was adapted to the current effort.

4.3.4.2 Labor Hours

If labor hours have been estimated based upon other than past experience, provide detailed rationale on how they have been estimated.

4.3.4.3 Labor Hour Skill Mix

Explain how the proposed labor hour skill mix has been derived and how the skill mix on this proposal compares with the overall plant skill mix. Explain why the cost element requires an average, higher, or lower than average skill mix, as applicable. If your normal estimating system uses a plant wide average for proposal purposes, so state.

4.4 Other Information

4.4.l Schedule of Hours by Labor Skill Mix Submit a schedule showing total proposed hours summarized by labor skill mix. This schedule is to include (but separately identify) subcontractor(s) and inter-divisional transfer(s) hours. In addition, provide labor classification statements for each category of labor proposed (prime, subcontracts, and inter-divisional) describing position qualifications (education, years of experience, etc).

4.4.2 Cost Summary by Cost Elements

Provide a cost summary by major cost elements by CLIN, offeror must Uuse the format shown belowU (and separately identify costs for Other Direct Costs including travel costs) seen below:

Cost Summary Performance Period:_______________________________

CATEGORY Period (1) Period (2) TOTAL Labor Category (CLIN) 0001 Hrs Rates Dollars Hrs Rates Dollars Hrs Dollars

XXX

XXX

XXX

XXX

XXX

XXX

XXX

Total Direct Labor Overhead & Fringe Overhead % Fringe % Total Overhead & Fringe Total Direct Labor, Overhead, & Fringe G&A (on Direct Labor and OH % Total Estimated Labor Cost Profit % Total Estimated CPFF Other Direct Costs (CLIN) Materials Subcontractor Costs Travel G&A TOTAL Estimated ODC Cost

TOTAL PRICE

(1) Provide breakdown according to contractor fiscal year. Use both blocks if proposal period falls into different fiscal years.

(2) Provide vendor quotes or Subcontractor proposals.

Note: Provide similar spreadsheet for each subcontractor.

(3) Provide breakout of Travel on separate document to support Travel:

Trip Destination # Persons Days Nights Air Fare Lodging Per diem Rental Car Airport Transportation Parking fees

IMPORTANT: Please include ALL formulas in the Excel spreadsheet.

4.4.3 Cost Summary by Cost Elements

Submit a list of the proposed probable subcontractors and inter-divisional transfers showing (a) the supplier, (b) description of effort, (c) type of contract, (d) price and hours proposed by each, (e) price and hours included in prime’s proposal to the…