CUI P5 SSU Section LTracked Changes.docx

Source Selection Information See FAR 2.101 and 3.104 – CONTROLLED UNCLASSIFIED INFORMATION

SECTION L

INFORMATION TO OFFERORS (ITO)

AND INSTRUCTIONS FOR PROPOSAL PREPARATION

1.0 (CUI) PROGRAM STRUCTURE AND OBJECTIVES

In order to meet current cybersecurity requirements and provide for future implementation of Proficiency Based Training (PBT), a security upgrade must be completed. Headquarters Air Combat Command (ACC) requires implementation of an encrypted P5 Combat Training System (P5CTS) data link to a) protect tactics and training methods and b) allow 4th generation aircraft to engage the F-35 during training missions. The solution identified is a shop-replaceable retrofit kit to replace the obsolete Data Guard Processor (DGP) in the Airborne Subsystem (AS)/pods that consists of a Data Security Module (DSM), and a P5 AS modified End Cap (MEC), interface cable(s) and associated hardware. The DSM shall encrypt data through a National Security Agency (NSA) certified Type 1 encryptor and provide a NSA certified control interface that enables or restricts the access or transfer of information between security domains. The DSM, MEC, associated hardware, software and technical data is referred to as the System Security Update (SSU) kit. The engineering, hardware, software, documentation, and other efforts required to manage and produce the kits is referred to as the SSU program. The P5CTS AS currently transmits unencrypted Controlled Unclassified Information (CUI) over-the-air. Department of Defense’s (DoD's) Risk Management Framework (RMF) requires that classified and CUI information be encrypted. Accordingly, the P5CTS must remedy the obsolescence concern and noted deficiencies to enable continued operations through at least 2030. These kits will be obtained through source selection procedures IAW Federal Acquisition Regulation (FAR) Part 15, Defense Federal Acquisition Regulation Supplement (DFAR) Part 15, Air Force Acquisition Regulation Supplement (AFFARS) Part 15, Defense Federal Acquisition Regulation Supplement Procedures, Guidance and Information (DFARS Subpart 215.3--Source Selection) with the new DoD source selection procedures memorandum revised on 01 Apr 2016.

2.0 (U) GENERAL INSTRUCTIONS

This section of the ITO provides general guidance for preparing proposals as well as specific instructions on the format and content of proposal. To assure timely and equitable evaluation of proposals, the offeror's proposal must include all data and information requested by this ITO and must be submitted in accordance with these instructions. Offerors are required to meet all solicitation requirements, including Terms and Conditions (T&Cs), representations and certifications, and the offer shall be compliant with the requirements as stated in the Statement of Work (SOW) and Contract Data Requirements List (CDRL), and Model Contract. Non-conformance with the instructions provided in this ITO may result in an unfavorable proposal evaluation. Failure to comply with the T&Cs of the solicitation may result in the offeror being ineligible for award. Offerors must clearly identify any exception to the solicitation T&Cs and must provide complete supporting rationale. The Government reserves the right to determine any such exceptions unacceptable. 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.

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

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.

In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals and destroy extra copies (or return extra copies to the offeror, if requested within 15 working days following contract award).

Documents submitted in response to this Request for Proposal (RFP) must be fully responsive to and consistent with the following:

1) Requirements of the RFP and government standards and regulations pertaining to the SOW

2) Evaluation factors for award in section M of this RFP

3) Any limitation on the number of proposal pages. Pages exceeding the page limitations set forth in this Section L will not be read or evaluated. Excess paper pages will be removed from the proposal and returned to the offeror.

2.1 (U) General Information

2.1.1 (U) Point of Contact The Contracting Officer (CO) is the sole point of contact for this acquisition. Address any questions or concerns you may have to Mr. Sean Jones and the buyer, Mr. Carlos Michel, at 6039 Wardleigh Rd, Bldg. 1206 Hill AFB, UT 84056-5838 or via e-mail to the following: sean.jones.2@us.af.mil and carlos.michel@us.af.mil

2.1.2 (U) 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.

2.1.3 (U) 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.

2.1.4 (U) Solicitation Requirements, T&Cs Offerors shall meet all solicitation requirements, such as T&Cs, representations and certifications, and technical requirements, in addition to those identified as factors or subfactors. Failure to comply with the T&Cs of the solicitation may result in the offeror being ineligible for award. Offerors must clearly identify any exception to the solicitation T&Cs and must provide complete supporting rationale. The Government reserves the right to determine any such exceptions unacceptable. By submission of its offer, the offeror accedes to all solicitation requirements, including T&Cs, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors.

2.1.5 (U) Electronic Reference Documents All referenced documents for this solicitation are available on the official website of the United States Government at https://beta.sam.gov. Potential offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

2.1.6 (U) 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 securely and includes “Source Selection Information – See FAR 2.101 & 3.104” in the Subject line. See Attachment L-3 for email encryption instructions. Otherwise, source selection information will be transmitted via postal service.

All inquiries must be submitted via e-mail to the CO, Mr. Sean Jones, at sean.jones.2@us.af.mil and the buyer, Mr. Carlos Michel, at carlos.michel@us.af.mil. Questions will be answered and posted to https://beta.sam.gov as quickly as possible during the proposal preparation period.

2.1.7 (U) Oral Presentations Oral presentations will not be allowed.

2.1.8 (U) Organization/Number of Copies/Page Limits The offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 1 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. The contents of each proposal volume are described in the ITO paragraph as noted in the table below:

Table 1 - Proposal Organization

*See Page Limitations, Section L Paragraph 2.1.8.1, for page count exceptions

Additionally, the offeror shall prepare and identify one Master Proposal containing one copy of each hard copy of each volume identified above in Table 1. The Government will accept an electronic proposal, however if it is hard copy, theThis Master Proposal shall be printed double-sided, flipped on the short end, two-hole punched centered on top of the page, and bound together but not in a binder.

2.1.8.1 (U) Page Limitations Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal and excess paper copies will be returned to the offeror as soon as practicable. Page limitations will 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. Each page shall be counted except the following: cover sheets (not to be confused with the Narrative Summary), Tables of Contents, title pages, glossary of abbreviations, acronym lists, blank pages, and tabbed dividers, and the Integrated Master Schedule (IMS). Each volume shall conform to the numbering, page count, and quantity of copies shown in Table 1 above.

2.1.8.2 (U) Page Size and Format 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. Pages shall be white bond paper written in Times New Roman font, single spaced. Except for the reproduced sections of the solicitation document, the text size shall be no less than 11 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. These limitations shall apply to both electronic and hard copy proposals.

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 by 17 inches in size. Foldout pages shall fold entirely within the volume and will count as a single page, and any hole punches shall not interfere with or delete information. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics and not for pages of text. For tables, charts, graphs and figures, the text shall be no smaller than 10 point. These page format restrictions shall apply to both hard and soft copies as well as responses to ENs.

2.1.8.3 Electronic Offers

The Offeror may submit Volumes I through V in electronic format, using virus-free CD-R/DVD-R. In no cases shall the Offeror use CD-RW/DVD-RW. Re-writable CDs/DVDs (i.e., CD-RW) WILL NOT BE READ, EVALUATED, OR CONSIDERED. Each volume will be on a separate CD/DVD, for a total of 3 CDs/DVDs. If files are compressed, the necessary decompression program must be included. The electronic copies must be submitted in a format readable by Microsoft (MS) Word 2010, MS Excel 2010, and MS-Power Point 2010, as applicable. PDF formats shall not be used. Word documents – Set “save as type” to “Word Document (*.docx)” only. Excel spreadsheets – Set “save as type” to “Excel (*.xlsx)” only. For electronic copies, indicate on each CD/DVD the volume number and title. Use separate files to permit rapid location of all portions, including subfactors, exhibits, annexes, and attachments, if any. The file naming shall specify the appropriate volume.

The Table of Contents of all proposal volumes shall be hyperlinked to the corresponding material within each proposal volume such that clicking the mouse on an item in the Table of Contents will take the reader to the corresponding section within the body of the proposal volume. Any heading or sub-heading appearing in the Table of Contents shall be hyperlinked as described above. The Table of Contents shall include the file names, as well as page numbers where content is cross-referenced between subfactors. Also, any reference within the body of the proposal volume that refers the reader to another location within the referring document shall be hyperlinked in the manner described above. Hyperlinking references between different filenames is not necessary.

Submission of the initial proposal packages via electronic mail will not be accepted. Initial proposal packages shall either be mailed or hand-delivered.

2.1.9 (U) Pricing Related Data All cost or pricing data shall be addressed ONLY in the Price Proposal and Contract Documentation Volumes. Information such as cost tradeoff information, work hour estimates, and material kinds and quantities (excluding dollar amounts/prices) may be used in other volumes only as appropriate for presenting rationale for alternatives or design and tradeoff decisions.

2.1.10 (U) Classified Information No classified proposals shall be submitted. Proposals shall be in compliance with the DD Form 254 and contract security requirements.

2.1.11 (U) Cross-Referencing To the greatest extent possible, each volume shall be written on a standalone 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 government will fill out a portion of the Cross Reference Matrix and the offeror will fill out the remaining sections in Attachment L-2 of this ITO indicating the proposal reference information as it relates to the ITO, SOW, CLIN numbers, and CDRL references found therein.

2.1.12 (U) 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.

2.1.13 (U) 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.

2.1.14 (U) Binding and Labeling Other than the Master Proposal identified in Table 1, 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 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.

2.1.15 (U) Electronic Offers The content and page size of electronic copies must be identical to the hard copies. For electronic copies, indicate on each CD/DVD 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 volumes I through V in electronic format, using recordable CDs/DVDs (CDRs or DVDRs not CDRWs or DVDRWs). Each volume shall be in a different directory on a CD or DVD. If files are compressed, the necessary decompression program must be included. The electronic copies of the proposal shall be submitted in a format readable and searchable by the Microsoft (MS) Office Suite 2010 or Adobe PDF format, as applicable. In the event there are any discrepancies between the hard copies and the electronic copies of the proposal, the hard copies will be used for evaluation.

2.1.15.1 (U) Electronic File Names For electronic submissions, the file naming convention for the proposal volumes is as follows. You may expand on these files names as appropriate; just provide a list of the content of each.

NOTE: .xxx = appropriate default file extension for MS Office suite / Adobe document type

2.1.15.2 (U) Hyperlink The Table of Contents in the soft copies of all proposal volumes shall be hyperlinked to the corresponding material within each proposal volume such that “clicking” the mouse on an item in the Table of Contents will take the reader to the corresponding section within the body of the proposal volume. Any heading or sub-heading appearing in the Table of Contents shall be hyperlinked as described above. In addition, any reference within the body of the proposal volume that refers the reader to another location within the referring document shall be hyperlinked in the manner described above. A Hyper-linking reference between different filenames is not acceptable.

2.1.16 (U) Distribution The original proposal shall be identified.

Hard copy, CD and DVD Pproposals shall be addressed to the CO and mailed or hand carried to:

AFLCMC/PZZKC

Attn: Mr. Sean Jones 6039 Wardleigh Rd, Bldg. 1206 Hill AFB, UT 84056-5838

Any proposal pertaining to this contract is "For Official Use Only" and "Source Selection Information--See FAR 2.101 and FAR 3.104".

3.0 (U) VOLUME I EXECUTIVE SUMMARY

In the executive summary volume, the offeror shall provide the following information:

3.1 (U) Narrative Summary 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. The executive summary is for informational purposes only as any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal.

3.2 (U) Table of Contents Include a master table of contents of the entire proposal.

4.0 VOLUME II - TECHNICAL PROPOSAL

4.1 (U) General The Technical Volume should be specific and complete. Legibility, clarity, and coherence are very important. There will be no reference to rates or price in this volume. Offerors shall assume that the Government has no prior knowledge of their certifications, facilities, and/or capabilities, and will base its evaluation on the information presented in the offeror’s proposal. Your responses will be evaluated against the Technical subfactors defined in Section M, Evaluation Factors for Award. Using the instructions provided below, provide as specifically as possible the actual methodology 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 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. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

4.2 (U) Format and Specific Content

4.2.1 (U) 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.

4.2.2 (U) 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) Technical Proposal (Subfactors)

4.3 (CUI) Technical Factor

4.3.1 (CUI) Subfactor 1 – System Test, Qualification and Certification The offeror shall provide their approach for the system test, qualification and certification requirements. The proposed approach shall thoroughly substantiate all of the following:

4.3.1.1 (CUI) Element A – Test Infrastructure – The offeror shall identify plans to obtain the necessary contractor test infrastructure and personnel required for qualification and certification of the P5CTS system components. The offeror shall address test equipment, support equipment, test plans, personnel training, required Government Furnished Property (GFP), and software (to include diagnostic aids) that will be necessary to successfully conduct the contractor flight qualification, component level testing, and system integration testing as required in SOW sections 2.0, 4.0, 4.1, 4.2, 4.3 and 4.5.9. See Attachment L-4 to provide GFP information.

4.3.1.2 (CUI) Element B – Maintenance Procedures – The offeror shall identify an encryption keying approach that minimizes maintenance actions for field personnel. The offeror shall address how the solution complies with Key Management Infrastructure (KMI) requirements utilizing standard AF Communication Security (COMSEC) equipment, and minimizes maintenance actions. The description shall include keying procedures and timelines, key loading/zeroizing, monitoring status, and retaining key currency (SOW section 4.1.34).

4.3.1.3 (CUI) Element C – NSA Certification Status – The offeror shall demonstrate that their proposed technical solution has been previously certified for an airborne application (either by the offeror or the Original Equipment Manufacturer (OEM). The offeror shall provide certification status of their DSM solution. The offeror shall address documentation of the certification status, such as NSA approval. (SOW sections 2.0, 4.1, 4.1.1, 4.1.2 and 4.2.6).

4.3.2 (CUI) Subfactor 2 – DSM Technical Solution The offeror shall provide their approach for the DSM technical requirements. The proposed approach shall thoroughly substantiate all of the following:

4.3.2.1 (CUI) Element A – NSA Compliant DSM Architecture – The offeror shall demonstrate their proposed DSM architecture meets current red/black separation requirements with a NSA compliant architecture. The offeror shall address all hardware and software enhancements to the P5 AS architecture they propose, as well as key system attributes their solution offers to meet current NSA security requirements, including current Foreign Military Sales (FMS) releasability status, as well as risks associated with FMS exportability. (SOW sections 1.0, 2.0, 4.1, 4.1.1, 4.1.1.1 and 4.1.1.2).

4.3.2.2 (CUI) Element B – Future Growth Opportunities – The offeror shall identify future growth opportunities of their DSM technical approach. The offeror shall address how key system attributes will allow implementation of future United States Air Force (USAF) initiatives, such as PBT, Performance Evaluation and Tracking System (PETS), and Multiple Levels of Security (MLS). (SOW sections 1.0, 2.0, 4.1, 4.1.1, 4.1.1.1 and 4.1.1.2).

4.3.2.3 (CUI) Element C – Rights in Data and Software Identification and Assertion – The offeror shall provide a completed Section J, Attachment L-6, Government Rights in Data (GRID). The offeror (including their subcontractors or suppliers, or potential subcontractors or suppliers, at any tier) shall identify all technical data and computer software that they propose to be delivered or otherwise provided and the data and license rights with which each item will be delivered. The offeror shall complete all tables and appendices in the GRID attachment of the solicitation, including the addition of any CDRLs that are proposed in addition to those listed. The GRID shall address the technical data and software CDRLs and the applicable license right assertions for the technical data and software CDRLs. The offeror shall describe how the proposed technical data and software CDRLs and the applicable license rights assertions for the technical data and software CDRLs in the GRID will impact the Government’s ability to sustain and maintain the system through future full and open competitive sustainment actions, and reduce life cycle costs. The offeror's failure to submit, complete all tables, or sign the identification and assertions required by DFARS 252.227-7017, Identification and Assertion of Use, Release, or Disclosure Restrictions with their offer may render the offer ineligible for award (SOW sections 4.4, 4.4.2, 4.7.3.1, Appendix B sections 2.0, 3.0, 6.0 and 7.0).

4.3.3 (CUI) Subfactor 3 – Program Schedule The offeror shall provide their approach for the program schedule. The proposed approach shall thoroughly substantiate all of the following:

4.3.3.1 (CUI) Element A – DSM Component Readiness Levels – The offeror shall demonstrate the Technical Readiness Levels (TRL) and Manufacturing Readiness Level (MRL) for DSM component candidates that satisfies program requirements. The offeror shall provide their self-assessment of the current TRL and MRL for their DSM components in the format specified by ISO 16290-2013 and the MRL Deskbook. The proposal shall provide a detailed assessment of the technical and manufacturing maturity of each DSM component, and include data that supports the self-assessment. In addition, the proposal shall identify items as developmental or non-developmental components (SOW sections 1.0, 2.0, 4.1, 4.1.1, 4.1.1.1, 4.1.1.2, 4.3, 4.3.1, 4.3.2 and 4.6.11).

4.3.3.2 (CUI) Element B – NSA Certification Schedule – The offeror shall demonstrate the NSA certification schedule of their encryption device for use in the P5CTS. The offeror shall provide the NSA Certification Section of their Integrated Master Schedule (IMS) that addresses certification events and milestones for Government review (SOW sections 2.0, 4.2.6 and 4.5.5).

4.3.3.3 (CUI) Element C – Integrated Test Schedule – The offeror shall demonstrate a test schedule that successfully completes qualification and certification tests within the SOW requirements. The offeror shall provide the Test Section of their IMS describing the qualification and certification timeline for test events and milestones, and address how that supports air worthiness certification, SEEK EAGLE approval, and the kit production decision within program timelines. (SOW sections 2.0, 4.0, 4.1, 4.2, 4.3 and 4.5.5).

4.3.3.4 (CUI) Element D – Kit Production Schedule – The offeror shall demonstrate a production timeline that satisfies program requirements. The offeror shall provide the Production Section of their IMS describing events and milestones addressing their kit production schedule. (SOW sections 4.1, 4.3, 4.3.1, 4.3.2, 4.3.3, 4.5.5).

5.0 VOLUME III – SMALL BUSINESS PARTICIPATION

5.1 (CUI) General The offeror shall describe their SB participation approach to address the goals within SOW para 4.5.3. The SB participation approach shall also include the extent to which such firms are specifically identified in proposals and the extent of commitment to use such firms. The SB participation approach is not to be confused with an offeror’s SB Subcontracting Plan.

The SB Participation Volume should be specific and complete (See Attachment L-5 for SB Participation formatting). Legibility, clarity, and coherence are very important. There will be no reference to rates or price in this volume. Offerors shall assume that the Government has no prior knowledge of their business partnerships, and will base its evaluation on the information presented in the offeror’s proposal. Your responses will be evaluated against the SB subfactors defined in Section M, Evaluation Factors for Award. 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. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

5.2 (CUI) SB Participation In the SB Volume, address your SB participation for meeting or exceeding the Government’s minimum requirements of each SB participation subfactors.

5.2.1 (CUI) Subfactor 1 – FAR Part 19 Firms Identified The offeror’s proposal shall identify the firms as defined in FAR Part 19 (SOW section 4.5.3).

5.2.2 (CUI) Subfactor 2 – Identification of SB Participants The offeror shall demonstrate substantive commitment to SB firms, such as, letters of commitment, Joint Ventures, mentor/protégé agreements, or other demonstrations of commitment (NOTE: binding commitments will become enforceable/contractual requirements) (SOW section 4.5.3).

5.2.3 (CUI) Subfactor 3 – Identification of Type and Variety of Work The offeror shall identify the type and variety of the work small firms are to perform (SOW section 4.5.3).

5.2.4 (CUI) Subfactor 4 – Extent of SB Participation The offeror shall identify the extent of SB participation in terms of the value of the total acquisition (total contract value) (SOW section 4.5.3).

6.0 (CUI)VOLUME IV – PRICE

6.1 (CUI) General Instructions The primary purpose of the price proposal volume is to provide the CO and the team evaluators an understanding of how the price proposal was developed. The price evaluation criteria of balance, reasonableness, and Total Evaluated Price (TEP) as defined in section M of the RFP will be assessed from the offeror’s information provided in this volume.

Submit the price proposal in MS Word and MS Excel worksheets as appropriate. Word documents and Excel spreadsheets must be editable and not password protected. Each disk shall be clearly labeled. The paper and electronic copies shall be clearly identified. Scanned documents in PDF files are NOT acceptable for the price proposal volume.

6.2 (CUI) Price Reasonableness and Balance This section is to assist you in submitting information other than pricing data that is required to evaluate the reasonableness of your proposed price. Compliance with these requirements is mandatory and failure to comply may result in rejection of your proposal. The burden of proof for credibility of proposed prices rests with the offeror.

6.3 (CUI) Estimating Techniques and Methods When responding to the price proposal 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.

6.4 (CUI) 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 data relating to the proposed price, including all required supporting documentation, must be included in the section of the proposal designated as the price proposal volume. Under no circumstances shall this data and documentation be included elsewhere in the proposal.

6.5 (CUI) Cost or Pricing Data Requirements The CO has determined there is a high probability of adequate price competition in this acquisition. Upon examination of the initial offers, the CO will review this determination and if, in the CO’s opinion, adequate price competition exists no additional data will be requested and certification under FAR 15.406-2 will not be required. However, if at any time during this competition the CO determines that adequate price competition no longer exists; offerors may be required to submit cost data to the extent necessary for the CO to determine the reasonableness of the price. In accordance with FAR 15.403-1(b) and 15.403-3(a), data other than certified cost or pricing data may be required to support a determination of price reasonableness. Data shall be provided in accordance with FAR 15.403-5. If, after receipt of proposals, the CO determines that there is insufficient data available to determine price reasonableness and none of the exceptions in FAR 15.403-1 apply, the offeror shall be required to submit pricing data.

6.6 (CUI) Total Evaluated Price (TEP) The offeror’s TEP will be calculated for use in evaluation of offers and will be a consideration in the best value award decision. The TEP will be the summation of Firm-Fixed Priced (FFP) contract line items to include the SSU Pricing Workbook located in Section J, utilizing Government notional quantities. Notional quantities will not be disclosed and will be used for evaluation purposes only. The Government will utilize the offeror’s SSU Pricing Workbook in its evaluation. The TEP is for evaluation purposes only and does not become a contractually binding amount after contract award; however, the unit prices within the SSU Pricing Worksheet and each individual CLIN shall be contractually binding. Offerors shall populate the pricing and cost cells in Section B, SSU Pricing Workbook per the instructions tab. The offeror shall complete and return this in MS Excel format. The TEP is for evaluation and award determination purposes only and will be a consideration in the best value award decision. This is dependent upon all the proposed prices being considered balanced and reasonable.

6.7 (U) Accounting System Indicate whether you will be issued other than fixed price type work and have Government approval of accounting systems and if so, provide evidence of such approval. Also, identify any deviations from your standard procedures in preparing this proposal.

6.8 (U) Rounding All proposed dollar amounts shall be rounded to the nearest dollar.

7.0 (U) VOLUME V CONTRACT DOCUMENTATION

7.1 (U) 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 Model Contract, and Sections A through K.

7.1.1 (U) Section A - Solicitation/Contract Form Completion of blocks 13 and 15 and signature and date for block 27of the SF 1447. Signature by the offeror on the SF 1447 constitutes an offer, which the Government may accept. In signing the SF 1447, the offeror accedes to the contract terms and conditions as written in the RFP Sections A through K. The "original" copy should be clearly marked under separate cover and should be provided without any punched holes.

7.1.2 (U) Section B - Supplies or Services and Prices The offeror shall complete the SSU Pricing Workbook in accordance with the instructions tab found in the Pricing Worksheet for CLINs 0003 and 0004. All other CLINs shall be priced separately on each individual CLIN.

7.1.3 (U) Section F - Deliveries or Performance The Period of Performance will be identified on each individual task order.

7.1.4 (U) Section G - Contract Administrative Data Contract Administrative Data Section G of the Model Contract will include all fundcites and dollar amounts for the contract. The offeror is not required to fill in this information

7.1.5 (U) Section I - Contract Clauses The offeror shall complete necessary fill-ins in Section I and submit only pages that require a fill-in. The offeror shall comply with the clauses specified within Section I of the Model Contract. Furthermore, any reference of a clause and/or provision in the solicitation will be adhered to and included in the resulting contract. All laws, regulations, and statutory authorities will also be applied within the model contract.

7.1.6 (U) Section K – Representations, Certifications, and other Statements of Offerors The offeror shall provide completed representations, certifications, acknowledgments, and statements.

7.2 (U) Exceptions to Solicitation Requirements Offerors are required to meet all solicitation requirements, such as T&Cs, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors. Failure to meet a requirement may result in an offeror being ineligible for award. Offerors must clearly identify any exception to the solicitation T&Cs 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.

Table 2 - Solicitation Exceptions

will not be met

7.3 (U) Other Information Required

7.3.1 (U) Authorized Offeror Personnel Provide the name, title, email address 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.

7.3.2 (U) Government Offices Provide the mailing address, telephone and fax numbers and facility codes for the cognizant Contract Administration Office (CAO), Defense Contract Audit Agency (DCAA), and Government Paying Office. Also, provide the name and telephone and fax number for the Administrative Contracting Officer (ACO).

7.3.3 (U) Company/Division Address, Identifying Codes, and Applicable Designations Provide company/division's street address, county and facility code; Commercial and Government Entity (CAGE) code; Data Universal Numbering System (DUNS) code; Taxpayer Identification Number (TIN); size of business (large or small). 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.

7.3.4 (U) Applicable Documents A list of Applicable Documents has been provided to the offerors as an annex to the SOW attachment in the solicitation, which includes a minimum list of Government Compliance Documents. The offeror shall provide a list of any offeror, industry, commercial, and tailored Government standards, specifications, processes, and/or practices selected as compliance documents. The offeror shall also provide a list of all Government compliance documents intended to be used as compliance documents during the course of this contract. The offeror shall submit a list of these documents, including any tailoring instructions, as an annex to the proposed SOW. The offeror shall submit the completed Proposed Compliance Documents as part of Volume V.

Source Selection Information See FAR 2.101 and 3.104 – CONTROLLED UNCLASSIFIED INFORMATION