Attachment_5-_DIB_Development_5th_Edition_-_Section_L_-Final.pdf

FA8730-17-R-0024, Attachment 5, Page 1

RFP ATTACHMENT 5 - SECTION L

INSTRUCTIONS FOR PROPOSAL PREPARATION (IFPP)

(INSTRUCTIONS, CONDITIONS, AND

NOTICE TO OFFERORS)

FOR

DISTRIBUTED COMMON GROUND/SURFACE SYSTEM

(DCGS) INTEGRATION BACKBONE (DIB) DEVELOPMENT

5th EDITION

26 September 2017

Version: Original

FA8730-17-R-0024, Attachment 5, Page 2

REVISION HISTORY

Revision Number Date Description Sections Affected

Original 26SEPT17 Initial Publication N/A

FA8730-17-R-0024, Attachment 5, Page 3

1.0 PROGRAM STRUCTURE AND OBJECTIVES

2.0 GENERAL INSTRUCTIONS

2.1 General Information

2.1.1 Point of Contact

2.1.2 Debriefings

2.1.3 Discrepancies

2.1.4 Notification to Offerors/Organizational Conflict of Interest (OCI)

2.1.5 Cost or Pricing Information

2.1.6 Classified Information

2.2 Organization

2.2.1 Page Limitations

2.2.2 Page Size and Format

2.2.3 Cross-Referencing

2.2.4 Indexing

2.2.5 Glossary of Abbreviations and Acronyms

2.2.6 Binding and Labeling

2.2.7 Electronic Offers

2.2.8 Distribution

2.2.9 Availability of Funds

3.0 VOLUME I - EXECUTIVE SUMMARY

3.1 Master Table of Contents

3.2 Narrative - Summary

3.3 Attachment 1 – Solicitation Cross Reference Matrix

4.0 VOLUME II - TECHNICAL

4.1 General

4.2 Format and Specific Content

4.3 Table of Contents

4.4 Technical and Management Approach

5.0 VOLUME III - COST/PRICE

5.1 Introduction

5.2 General Instructions

5.2.1 Estimating Techniques and Methods

5.2.2 Subcontractors/Interdivisional Transfers (IDT)

5.2.3 Rounding

5.2.4 Cost/Price using Contract Year

FA8730-17-R-0024, Attachment 5, Page 4

5.3 Cost/Price Volume

5.3.1 Cost/Price Volume Organization

5.3.2 SECTION 1: Introduction

5.3.2.1 Estimating System

5.3.2.2 Accounting System

5.3.2.3 Adequate Disclosure Statements

5.3.2.4 Labor Skill Mix

5.3.3 SECTION 2: Other Information

5.3.3.1 Ground Rules and Assumptions

5.3.3.2 Cost Reductions

5.3.3.2.1 Management Reduction

5.3.3.2.2 Commonality with Other Programs

5.3.3.3 Probable Subcontractors

5.3.3.4 Administrative Information

5.3.3.5 Delivery of Cost Proposals

5.3.3.6 Pre-Award Survey (PAS)

5.3.4 SECTION 3: Cost Format Instructions – Submission of Cost Formats

5.3.4.1 Summary

5.3.4.2 B-Table

5.3.4.3 Delivery Order 01 – Initial TRN

5.3.4.4 Sample Epic

5.3.4.5 LH Rates at BEQ

5.3.4.6 Price Track

6.0 VOLUME IV - CONTRACT DOCUMENTATION

6.1 Model Contract/Representations and Certifications

6.1.1 Section A - Solicitation/Contract Form

6.1.2 Section B - Supplies or Services and Costs/Prices

6.135 Section E – Inspection and acceptance

6.1.4 Section F - Deliveries or Performance

6.1.5 Section G - Contract Administrative Data

6.1.6 Section I – Contract Clauses

6.1.10 Section J – List of Attachments

6.1.11 Section K - Representations, Certifications, and other Statements of Offerors

6.2 Exceptions to Solicitation Requirements

6.3 Other Information Required

FA8730-17-R-0024, Attachment 5, Page 5

6.3.1 Authorized Offeror Personnel

6.3.2 Government Offices

6.3.3 Company/Division Address, Identifying Codes, and Applicable Designations

6.3.4 Government Furnished Information (GFI)

6.3.5 Organizational Conflict of Interest Statement and/or Mitigation Plan

ATTACHMENT L-1 (Solicitation Cross Reference Matrix)

ATTACHMENT L-2 (Sample EPIC)

ATTACHMENT L-3 Delivery Order 01 - Initial Task Requirements Notice (TRN)

FA8730-17-R-0024, Attachment 5, Page 6

1.0 PROGRAM STRUCTURE AND OBJECTIVES

The Distributed Common Ground / Surface System (DCGS) Integration Backbone (DIB) Development 5th Edition contract will be a Single Award Indefinite Delivery Indefinite Quantity (IDIQ) contract. The Ordering Period will be for five (5) years utilizing a Labor Hour (LH) contract type. The contract will allow for up to five (5) years of performance from the date of contract award and all orders issued under it must be completed within that five (5) year period.

The DIB is a common set of enterprise services that provide the necessary functionality to interface information services such that the DCGS Enterprise has the capability to exchange data and information.

The DIB provides the DCGS systems with data discovery and retrieval services that identify what information is available, where the information is located, and will retrieve specific data selected. Lastly, the DIB provides enterprise-wide software services for security, web access, and other basic features. The DIB is currently based on the Distributed Data Framework (DDF) and Alliance, fully open source software products, and is documented to ensure that any vendor can develop and integrate DIB services as required by the Government.

The DIB is developed and managed by the DCGS Multi-Service Execution Team (MET) Office (DMO) located at Hanscom AFB in Massachusetts. The DIB and the information services implemented in the DCGS Enterprise improve the interoperability that is the key to the collaborative and distributed requirements of the vision described in the Initial Capabilities Document (ICD) for the DCGS. Open and documented standards (commercial and government) are critical to this effort. The intent is to reduce the proliferation of proprietary solutions and interfaces for the DCGS Enterprise. The DIB provides the tools, architecture, standards, and documentation supporting the interfaces for the DCGS Family of Systems (FoS) to achieve a Multi-INT (e.g., IMINT, SIGINT, MASINT, CI/HUMINT), network centric environment with interoperability to allow individual DCGS systems and users access to the information needed to execute their respective missions.

2.0 GENERAL INSTRUCTIONS

a. This section provides general guidance for preparing proposals as well as specific instructions on the format and content of the proposal. The offeror’s proposal must include all data and information requested and must be submitted in accordance with these instructions. The offer shall be compliant with the requirements as stated in the Statement of Work (SOW), Model Contract, including all Exhibits and Attachments thereto, and all attachments to these instructions for proposal preparation (IFPP) including supplemental instructions contained herein. Non-conformance with these IFPP instructions and/or submittal of an incomplete package may result in an offer being considered non-responsive and the package will not be evaluated.

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. The offeror shall assume that the Government has no prior knowledge of the offeror’s facilities and experience, and will base its evaluation on the information presented in the offeror’s proposal.

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

d. The proposal validity period shall be 180 days from the proposal due date. The offeror shall make a clear statement in Section A of Volume IV Contract Documentation that the proposal is valid through this date.

FA8730-17-R-0024, Attachment 5, Page 7

e. Note: Throughout the RFP documents, unless otherwise specified, reference to days will mean calendar days, not business days. In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one complete copy of all unsuccessful proposals. Unless the offeror requests otherwise, the Government will destroy extra copies of such unsuccessful proposals.

f. All the requirements in the RFP are mandatory. By your proposal submission you are representing that your firm will perform all the requirements specified in the RFP. Therefore, it is not necessary or desirable for you to state this in your proposal.

2.1 General Information

2.1.1 Point of Contact

The Procurement Contracting Officer (PCO) is Ms. Patricia Forest. The Contracting Specialist is Mr.

Daniel Dornfeld. These are the sole points of contact for this acquisition. Address any questions or concerns to the PCO and Contract Specialist via email to the addresses listed in the RFP cover letter.

2.1.2 Debriefings

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 Discrepancies

If an offeror believes that the requirements in these instructions or the RFP contain an error, omission, or are otherwise unsound, the offeror shall immediately notify the PCO in writing with supporting rationale. The offeror is reminded that it is the Government’s intent to award without discussions. However the Government reserves the right to conduct discussions if the PCO determines that discussions are necessary and would be in the best interest of the Government.

2.1.4 Notification to Offerors/Organizational Conflict of Interest (OCI) Non-Disclosure Agreements (NDA): Offerors are advised that Non-Government personnel employed by the firms identified below may serve as advisor(s) in the source selection process. Non-government personnel are excluded from determining ratings and rankings of Offeror proposals. The Offeror shall enter into a Non- Disclosure Agreements with the companies employing Non-Government advisors (see FAR 9.505-4(b)). An Offeror is required to enter into a NDA with each Non-Government company that may be used to support the evaluation of proposals submitted. A copy of the NDA must be submitted as part of this proposal for Procurement Contracting Officer (PCO) review. An Offeror must also state that it consents to the Government providing access of its proprietary information to the nongovernment advisor or the company which employs the nongovernment advisor.

Offerors are advised that members of the evaluation team may include a PASS Contractor from the following entities:

Odyssey Systems Consulting Group 201 Edgewater Drive #270 Wakefield, MA 01880 Task Lead: John Barrette, 781-225-9985, john.barrette.1.ctr@us.af.mil

The MITRE Corporation 202 Burlington Road Bedford, MA 01730

Task Lead: Eric Estochen, 781-225-9192, eric.estochen.ctr@us.af.mil

Offerors shall submit an assessment of potential or actual Organization Conflict of Interest (OCI) issues, if any, as related to this Request for Proposal (RFP) and future work, should an award be made to the company. Initial notification shall be made to the Contracting Officer and Contract Specialist as soon as mailto:john.barrette.1.ctr@us.af.mil mailto:eric.estochen.ctr@us.af.mil

FA8730-17-R-0024, Attachment 5, Page 8 they become know. OCI issues include, but may not be limited to, the inability to render partial assistance or advice to the Government, the inability to objectively perform contract work, or the unfair competitive advantaged created by current or previous contractual efforts with the Government. A mitigation plan for such an assessment shall be included. The Contracting Officer will review the submitted mitigation plan and make a determination as to whether the plan adequately meets the issues and provides adequate protection to both the Offeror and the Government. Any OCI assessments and mitigation plans shall be included with the submission of this proposal.

If your proposal in any way involves the above companies, notify the PCO immediately and please submit an Organizational Conflict of Interest Mitigation Plan.

2.1.5 Cost or Pricing Information

All cost or pricing information shall be addressed ONLY in the Cost/Price Proposal and Contract Documentation Volumes. Hard copy and electronic copies of non-Cost/Price Volumes shall be “sanitized.”

“Sanitized,” as used herein, means free of unit prices, total item prices, or other information that would conform to the definition of “Cost or Pricing Data” as defined in FAR Part 2.

2.1.6 Classified Information

Proposals must not include classified information.

2.2 Organization

The offeror shall prepare the proposal as set forth in the Proposal Organization Table 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. The attachments for volumes shall be properly marked and included within the same three-ring binder with its respective volume. The contents of each proposal volume are described in the IFPP paragraphs as noted in the table below.

TABLE 2. Proposal Organization Volume IFPP

Paragraph No.

Volume Title Hard Copies (Including one original)

Electronic Copies

Page Limit

I 3.0 Executive Summary 2 1 3

3.3 Attachment 1 - Solicitation Cross

Reference Matrix

II 4.0 Technical 2 1 15 Volume II - Attachments Attachment 1 – Sample Epic

Must Follow the order below

-Design Approach -Product Backlog **

-Architecture Data -Software Development Roadmap **

Attachment 2 – Software Assurance ** Attachment 3– Integration and

Transition Plan

III 5.0 Cost/Price 2 1 None IV 6.0 Contract Documentation 2 1 None

*Not included in Volume I, 3 page limit **Not included in Volume II, 15 page limit

FA8730-17-R-0024, Attachment 5, Page 9

2.2.1 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 (for paper copies) will be returned to the offeror as soon as practicable.

Page limitations may be placed on responses to Evaluation Notices (ENs), if required. The specified page limits for EN responses will be identified therein. EN responses shall include proposal page revisions as applicable. For all Volumes and Attachments thereto, each page shall be counted except the following:

a. Cover pages

b. Tables of contents

c. Signed Letter of Transmittal

d. Tabs

e. Lists of tables and drawings

f. Glossaries

g. Volume II - Software Development Roadmap

h. Volume II - Attachment 2 (Software Assurance)

i. Acronym Lists

j. Cross Reference Matrix

k. Contractor’s Product Backlog based on Sample Epic

l. Cost Documentation

m. Contract Documentation

2.2.2 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, which shall not exceed 11 x 17 inches. Pages shall be single-spaced. Except for the reproduced sections of the solicitation document, the text shall be Times New Roman and the 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 3/4 inch side margins. Pages shall be numbered sequentially by volume. These page format restrictions shall also apply to responses to ENs. These limitations shall apply to both electronic and hard copy proposals.

b. 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 and no smaller than 9 point font. Arial or Helvetica font will also be permitted for use in charts, graphs or figures. Foldout pages shall fold entirely within the volume, and each

8.5 x 11 surface of a foldout shall be counted as a separate page. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics; not for pages of text. These limitations shall apply to both electronic and hard copy proposals.

2.2.3 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 completed Solicitation Cross Reference Matrix indicating the proposal reference information as it relates to the Section L, IFPP, Section M, Statement of Work, and other references found therein. The Solicitation Cross Reference Matrix is provided at Attachment L-1.

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

FA8730-17-R-0024, Attachment 5, Page 10

2.2.5 Glossary of Abbreviations and Acronyms

Each volume shall contain a glossary of all abbreviations and acronyms used therein. The glossary shall be used only to spell out abbreviations and acronyms, not to provide an expanded definition of terms.

Glossaries do not count against the page limitations for their respective volumes.

2.2.6 Binding and Labeling

Each volume of the proposal should be separately bound in a three-ring loose-leaf binder which shall permit 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 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.

2.2.7 Electronic Offers

The Offerors shall submit Volumes I – IV to the PCO (Patrica.Forest@us.af.mil) and to the Contract Specialist (Daniel.Dornfeld.1@us.af.mil). The content and page size of electronic copies must be identical to the hard copies. In the event there is a difference in content or page size between hard and electronic copies, the Government will base its evaluation on 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 subfolders, exhibits, annexes, and attachments, if any. The offeror shall submit volumes I through IV in electronic format, using a separate read-only CD/DVD for each volume. 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) Word 2010, MS Excel 2010, MS-Project 2010, and MS- Power Point 2010, as applicable. Recommend schedules be produced in MS-Project, but all MS-Project files must be exported to PDF.

2.2.8 Distribution

The "original" proposal shall be identified. See below for how to complete the outside shipping label:

When shipping using FedEx, UPS, DHL, etc. the outside shipping label shall be addressed as shown below:

66 LRS Central Shipping and Receiving (CS&R) Building 1110 (25 Randolph Road) Hanscom AFB, MA 01731-1700

MARK FOR:

Patricia J. Forest, Contracting Officer

AFLCMC/HBBK

Re: Solicitation Number FA8730-17-R-0024 Phone: 781-225-9367

When hand carrying the proposal, proposals shall be addressed to the PCO as shown below:

AFLCMC/HBBK

11 Barksdale Street, Building 1614

MARK FOR:

Patricia J. Forest, Contracting Officer Re: Solicitation Number FA8730-17-R-0024 Phone: 781-225-9367 mailto:Patrica.Forest@us.af.mil mailto:Daniel.Dornfeld.1@us.af.mil

FA8730-17-R-0024, Attachment 5, Page 11

Both electronic and paper proposals shall be received no later than the date and time specified on the RFP letter. If proposals are to be hand-delivered, the Offeror is cautioned that they will need to be processed through the Hanscom AFB visitors’ entrance in order to gain access to the Base and should allow appropriate time. The Offeror should contact the PCO upon arrival to the Base. For hand-delivered proposals, there will a representative in the main lobby of Building 1614, Hanscom AFB, to receive the proposals.

The prime, subcontractor(s) and interdivisional organizations must deliver one (1) CD each of their proposals to the cognizant DCMA/ACO and DCAA offices by the date and time specified in the RFP. Be sure to advise the Administrative Contracting Officer (ACO) and the Defense Contract Audit Agency (DCAA) for prime and subcontractors that the proposal is “For Official Use Only” and “Source Selection Information – See FAR 2.101 and Far 3.104”.

2.2.9 Availability of Funds

FAR 52.232-18 (Availability of Funds) is applicable to this procurement action. Funds are not presently available for this contract. The Government’s obligation under this contract is contingent upon the availability of appropriated funds from which payment for contract purposes can be made. No legal liability on the part of the Government for any payment may arise until funds are made available to the Contracting Officer for this contract and until the Contractor receives notice of such availability, to be confirmed in writing by the Contracting Officer.

3.0 VOLUME I - EXECUTIVE SUMMARY

A signed letter of transmittal shall be included within Volume I (not included in the 3 page limit for the Volume). Within the Executive Summary volume, the offeror shall provide the following:

3.1 Master Table of Contents

Include a Master Table of Contents of the entire proposal (not included in the 3 page limit for the Volume).

3.2 Narrative - Summary

Offeror’s executive summary shall include the following: A concise narrative summary of the entire proposal, including significant risks, and a highlight of any key or unique features, excluding cost/price.

The salient features should tie in with Section M evaluation factors. Any summary material presented in this volume shall not be considered as meeting the requirements for any portions of other volumes of the proposal.

3.3 Attachment 1 – Solicitation Cross Reference Matrix

Complete the Solicitation Cross Reference Matrix, provided at Attachment L-1, indicating the proposal reference information as it relates to the SOW, Section M, Section L, and other references found therein (not included in the 3 page limit for the Volume).

4.0 VOLUME II - TECHNICAL

4.1 General

For this solicitation, the Government has specifically broken down the technical evaluation factor into two subfactors: Subfactor 1: Technical and Subfactor 2: Management approach. In Volume II, offerors are asked to propose a Technical and Management approach in preparation for executing development of the Sample Epic (Attachment L-2) and the Integration Plan. These approaches shall address all the evaluation criteria as specified in RFP Attachment 6 - Section M. Your responses will be evaluated in accordance with Section M. In this detailed proposal, the offerors approach shall also meet the Government’s requirements as defined in the DIB Development 5th Edition Statement-Of-Work and assess the risks in their proposed approach in terms of mission performance, cost and schedule.

FA8730-17-R-0024, Attachment 5, Page 12

4.2 Format and Specific Content

Volume II should be specific and complete. The Offeror “shall not” submit a Contractor SOW. Legibility, clarity and coherence are very important. Volume II shall address both subfactors and the methodology/processes/procedure for accomplishing/satisfying all technical requirements and objectives.

Provide the actual methodology you would use for accomplishing/satisfying the DIB Development 5th Edition Statement-Of-Work. In this volume, your proposed approach shall map to the Technical Factor identified in RFP Attachment 6 - Section M. All the requirements specified in the solicitation are mandatory.

The offeror shall not exceed fifteen (15) pages for this Volume in response to requirements for this acquisition, covering the technical proposal, and SOW. By your proposal submission you are representing that your firm will perform all the requirements specified in the RFP. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation. Information produced in the development of Attachment 1 (refer to paragraph 4.4 below) will be utilized to complete the offeror’s Cost/Price Volume.

4.3 Table of Contents

The offeror shall provide a table of contents of the Technical Proposal that includes a List of Tables and Drawings and attachments included in the Technical Volume. For clarity, each table, drawing, and attachment shall be referenced to its applicable Section, and Sub-section of the Technical Volume.

4.4 Technical and Management Approach

Include each of the following Attachments as part of the Technical Volume. The complete approach proposed will be evaluated against the technical and management approach evaluation criteria in RFP Attachment 6 – Section M.

Attachment 1 – Sample Epic

• Design Approach:

Provide capability decomposition of the Sample Epic provided/described in Attachment L-2 down to the User Story level in sufficient detail as to demonstrate a complete understanding of the requirement and provide a narrative to explain the rationale and/or methodology used. The capability decomposition shall take the form of a product backlog, and should detail the items required in order to successfully deliver a viable product. Provide your approach as a recommendation to the Government Product Owner/Product Owner Team. This approach should include a project completion plan that tentatively identifies pieces of functionality (user stories) that will be earmarked for specific sprints (Note: government is not expecting full functionality of the sample epic to be completed within the 6 month period of performance however whatever is delivered at the end of each sprint should be a working increment). The plan should include a list of sprints that contain all user stories (with acceptance criteria and definitions of done) to achieve the Sample Epic objective. Additionally, include your approach for creating scrum teams, working as part of an integrated development team (as described in SOW pp 2.0 & 3.0) and your involvement approach for members who are subject matter experts in various software disciplines, Scrum Masters, and product owners.

• Architecture Data:

Describe proposed architecture for Sample Epic. This will include the Systems Interface Description, which depicts DIB system views, and the System Communication Description, which depicts the system interconnections. Include in your architecture your understanding of how DCGS Community, full stack open source development, software and web services technologies, building upon an existing end point, metadata neutral taxonomy, and OSGi work into this architecture.

• Software Development Roadmap:

Provide a Sample Epic Software Development Roadmap based upon implementing the Sample Epic. The Software Roadmap shall be defined to the level of detail to which the offeror plans to manage execution of the DIB Development 5th Edition SOW and to successfully meet the requirements of the Sample Epic. The Software Development Roadmap shall reflect external dependencies, risks, technical assumptions and estimated complexity of effort of each backlog item from the Sample Epic in order to estimate hours and provide a timeline for deliverables.

FA8730-17-R-0024, Attachment 5, Page 13

Attachment 2 – Software Assurance The offeror shall describe their overall plan and processes for software assurance, including:

• Secure coding processes and practices that include the use of static (and dynamic) code analysis tools and performing manual code reviews.

• Provide sample output from at least two of the commercial software assurance tools selected by the offeror executed on DDF or Alliance code.

Attachment 3 – Integration and Transition Plan Develop an integration plan that encompasses the path starting at contract award, through transition, completing with your team at Full Capacity in the role as outlined in the SOW. Full Capacity refers to point at which the contractor has the ability to effectively execute development and support tasks similar to that presented in the Sample Epic. The Integration Plan should address procedures to provide sufficient numbers of skilled/cleared employees to assume responsibilities for all contract functions for a successful transition from the incumbent performing this work. The Offeror must address, at a minimum: i.

positioning of its employees (by labor/skill mix) and ii. Training personnel, based on the technical and administrative needs set forth in the SOW. The plan should also describe how your management approach provides for standard workload.

5.0 VOLUME III - COST/PRICE

5.1 Introduction

These instructions are to assist the Offeror in preparing and submitting Data Other Than Certified Cost or Pricing Data required in accordance with FAR 15.403-3. The Government needs this information in order to properly assess the reasonableness and balance of the Offeror's proposed Cost/Price. The information will also be used to assess the Offeror’s skill mix and compliance with the Sample Epic budget constraints. Compliance with these instructions is mandatory and failure to do so could result in the rejection of the proposal. Offers should be sufficiently detailed to demonstrate their reasonableness and balance. The burden of proof for credibility rests with the Offeror. Information beyond that required by these instructions shall not be submitted, unless the offeror considers it essential to support their proposed Cost/Price.

The PCO has made a preliminary determination of “Adequate Price Competition.” Therefore, a Certificate of Current Cost or Pricing Data per FAR 15.403-4 will not be required, and any references to said Certificate or to “PL 87-653” elsewhere in this document are not applicable. In the event that adequate competition does not emerge in response to the solicitation, the PCO may require Certified Cost or Pricing Data in accordance with FAR 15.4.

All information regarding cost or pricing documentation must be included in the Cost/Price Volume III and/or the Contract Documentation Volume IV. Under no circumstances shall any cost or pricing documentation be included elsewhere in the proposal.

5.2 General Instructions

The ground rules and assumptions (e.g., contract type, contract items, delivery schedule, GFI, etc.) of the prospective contract are provided in the appropriate sections of this RFP. For Labor Hour (LH) efforts, Wrap Rates are for both price and contract purposes. Offerors may not propose other labor categories at this time. Assume for pricing purposes a Period of Performance commencing 1 February 2018 for the LH B-Tables.

The Offeror shall provide cost documentation and supporting rationale for all years in the schedule. The effort to be included shall be in accordance with the Offeror’s proposed scope of work.

FA8730-17-R-0024, Attachment 5, Page 14

5.2.1 Estimating Techniques and Methods

When responding to the Cost/Price Volume requirements in the solicitation, the offeror, subcontractor, teaming partner and joint venture partner 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. If necessary, reasonable and supportable allocation techniques may be used to justify the estimated complexity of each backlog item contributing to the sizing of estimated hours. The Offeror shall identify all ground rules and assumptions used in developing the cost documentation.

5.2.2 Subcontractors/Interdivisional Transfers (IDT)

The prime proposal shall uniquely identify Subcontractor and IDT labor hours and LH Wrap Rate. The Prime Contractor shall provide a cost/price evaluation for Subcontractors/IDTs that corroborates the evaluation rationale that leads to the prime’s conclusion that the subcontract price is fair and reasonable.

Any price adjustments to the Subcontractors and IDTs proposed prices that are included in the prime proposal submission, including discounting or expected decreases to be achieved in negotiations, shall be fully identified and explained.

5.2.3 Rounding

All dollar amounts provided shall be rounded to the nearest dollar. All LH Wrap Rates shall be rounded to the nearest penny.

5.2.4 Cost/Price using Contract Year

Proposals shall be based on the Contract Year (CY). The CY is as follows (Period of Performance dates below are estimated and may change based on contract award)

Kick off Mtg & Observation 1 February 2018 – 16 March 2018 CY1 17 March 2018 – 16 March 2019 CY2 17 March 2019 – 16 March 2020 CY3 17 March 2020 – 16 March 2021 CY4 17 March 2021 – 16 March 2022 CY5 17 March 2022 – 31 January 2023

5.3 Cost/Price Volume

The Cost/Price Volume shall provide comprehensive narrative support for the cost proposals. The Offeror shall provide a summary description of the standard estimating system and methods used. The Offeror shall identify any deviations from these standard estimating procedures in preparing this proposal.

5.3.1 Cost/Price Volume Organization

The Cost/Price volume shall specify, by page number, where each cost format and each piece of narrative data is located. The Cost/Price Volume shall consist of the following sections:

SECTION 1: Introduction SECTION 2: Other Information SECTION 3: Cost Format Instructions - Submission of Cost Formats

5.3.2 SECTION 1: Introduction

The Offeror shall prepare a proposal summary that includes an introduction, table of contents, overview, index, summary descriptions of estimating and accounting systems, and, if applicable, changes to approved/disclosed estimating and accounting systems.

5.3.2.1 Estimating System

The Offeror shall provide a summary description of your standard estimating system or methods. Also, identify any deviations from your standard estimating procedures in preparing this proposal volume.

FA8730-17-R-0024, Attachment 5, Page 15

Indicate whether you have Government approval of your system and if so, provide evidence of such approval.

5.3.2.2 Accounting System

The Offeror shall provide a summary description of its Accounting System and methods. The Offeror shall identify any deviations from its standard procedures in preparing this proposal. The Offeror shall indicate whether the Government has approved the accounting system and, if so, provide evidence of such approval.

5.3.2.3 Adequate Disclosure Statements

As this acquisition is a small business set-aside, IAW FAR Part 30 and FAR Appendix 9903.201-1(b)(3);

Cost Accounting Standards (CAS) do not apply to small business concerns. Therefore, this contract is CAS exempt and an adequate Disclosure Statement is not required.

5.3.2.4 Labor Skill Mix

The Offeror shall explain how the proposed labor hour’s skill mix has been derived and how the skill mix on this proposal compares with the overall plant skill mix. The Offeror shall explain why an average, higher, or lower than average skill mix is required, as applicable. If the Offeror’s normal estimating system uses a plant wide average for proposal purposes, the Offeror shall state.

5.3.3 SECTION 2: Other Information

This section shall include other information that will further support the Offeror's cost volume. The Offeror shall include other information such as, but not limited to, base support, and Government furnished information.

5.3.3.1 Ground Rules and Assumptions

The Offeror shall include a general discussion of the ground rules and assumptions used to develop the proposed prices. All assumptions, scope limitations and/or qualifications of the cost/price proposal shall be addressed and explained. The Offeror shall list each exception to the instructions provided in the solicitation and each qualification of the Cost/Price Volume, if any. The Offeror shall provide complete rationale for any exceptions.

5.3.3.2 Cost Reductions

5.3.3.2.1 Management Reduction

If estimated costs to perform the proposed effort have been decreased due to a management decision, the Offeror shall provide a summary of the reduction and complete rationale for the reduction.

5.3.3.2.2 Commonality with Other Programs

Any cost reductions made in the Offeror’s proposal that are attributed to commonality with other programs, company-funded efforts, or capitalization of equipment shall be supported with the following information:

(a) Commonality The Offeror shall identify the specific program(s) and why it is applicable.

The Offeror shall address the cost allowability and allocability of this action per FAR.

(b) Company-Funded Efforts

The Offeror shall identify the specific efforts, the planned start and end dates, the applicability to the current solicitation, the source of company funding and how they plan to account for or allocate these costs in accordance with generally accepted accounting principles.

(c) Capital Equipment

The Offeror shall identify the specific item(s) capitalized and what other applications exist for the equipment, provide corporate approvals for each action, address the cost allowability and allocability of the action per the FAR.

FA8730-17-R-0024, Attachment 5, Page 16

5.3.3.3 Probable Subcontractors

The Offeror shall submit a list of the proposed probable Subcontractors and IDTs showing the following:

the supplier, description of effort, type of contract, price and hours proposed by each, price and hours included in Prime’s proposal to the Government, method for choosing each vendor (i.e., competitive, non-competitive method, etc.), any increases or decreases applied to the proposed costs and associated supporting rationale, and commercial item/service determination support, if applicable.

5.3.3.4 Administrative Information

The Offeror shall provide names and addresses of the cognizant Defense Contract Management Agency/Contract Administrative Office (DCMA/CAO) and the Defense Contracting Audit Agency (DCAA) representatives, if applicable.

5.3.3.5 Delivery of Cost Proposals

In addition to submitting the cost proposal to the Contracting Officer, the Prime Contractor, Subcontractors and IDTs shall deliver a copy of each proposal in the format of a CD to the cognizant DCMA/CAO and DCAA representatives by the date and time specified in the RFP.

5.3.3.6 Pre-Award Survey (PAS)

The PCO may have DCMA conduct a PAS of all identified offerors. The PAS may assess the offeror’s financial capability, accounting system, and quality assurance program. The results of the PAS would be used in the Contracting Officer’s determination of responsibility, and problems in the PAS could result in a determination that a company is not awardable. If a current PAS (within six months) is available from DCMA it may be used in lieu of conducting another survey.

5.3.4 SECTION 3: Cost Format Instructions – Submission of Cost Formats Offerors shall submit cost formats using an electronically submitted format compatible with Microsoft Excel 2013 (“.xlsx”) containing embedded formulas that provide insight into the build-up of the Offeror’s cost proposal. An illustration of this format is provided in RFP Attachment 7 – Cost Formats of this document. Offerors may make adjustments to the Cost Formats (add additional rows or columns to worksheets), if needed, to be consistent with their Accounting/Estimating System. Below is a description of each section of the Excel file Cost Format.

5.3.4.1 Summary

Table 1 in this worksheet provides a summary of Delivery Order (DO) 0001 - Initial TRN. For LH CLIN 0001, a formula is included that references Total CLIN 0001 from the “Delivery Order 01 - Initial TRN” worksheet. The CR CLINs (0003 and 0004) will be evaluated at the following Government established values:

CLIN Govt Est Value 0003 $5,000 0004 $5,000

Table 2 in this worksheet provides a Total Price for the CR CLINs. The CR CLINs will be evaluated at the following Government established values:

CLIN Govt Est Value 0003 $100,000 0004 $100,000 0006 $100,000 0007 $100,000 0009 $100,000 0010 $100,000 0012 $100,000 0013 $100,000

FA8730-17-R-0024, Attachment 5, Page 17

0015 $100,000 0016 $100,000 0018 $100,000 0019 $100,000 0021 $100,000 0022 $100,000 0024 $100,000 0025 $100,000

Table 3 in this worksheet provides a Total Price for the Sample Epic, which a formula is included that references Total Sample Epic from the “Sample Epic” worksheet. The Total Price for Sample Epic will not be included in the Total Evaluated Price (TEP).

Table 4 in this worksheet provides a summary of the LH Rates at BEQ at the Total Evaluated Price (TEP) in accordance with Section M, paragraph b.(6)e for CY1, CY2, CY3, CY4, and CY5. Table 3 intentionally has “#DIV/0!” under the TEP column; however, once the B-Table LH Wrap Rates are input, this error will be corrected and the appropriate value will be automatically populated.

5.3.4.2 B-Table

The offeror shall input their LH Wrap Rates, along with any subcontractor/IDT LH Wrap Rates, for the applicable Delivery Order 01 - Initial TRN and CYs as prescribed in Section L, paragraph 5.2.6. The LH Wrap Rates should be rounded to the nearest penny. The proposed LH Wrap Rates for the Prime Contractor and any proposed subcontractor/IDT will be incorporated into the contract at time of award. A LH Wrap Rate must be proposed for each labor category.

5.3.4.3 Delivery Order 01 – Initial TRN

The offeror shall input the proposed hours for the appropriate labor categories for the Prime Contractor and any subcontractor/IDT for Delivery Order 01 – Initial TRN. The “Wrap Rate” column references the applicable Wrap Rates from the “B-Table” worksheet from Initial TRN. The “Total Price” column includes formulas to calculate the prices by multiplying the proposed hours to the Wrap Rate for the Prime Contractor and the subcontractors/IDT. The “Total Price” utilizes the Excel ROUND function to the nearest dollar. The Total Price for the Prime Contractor and the subcontractors/IDT is then summed up in the last Total Price column.

5.3.4.4 Sample Epic

The offeror shall input the proposed hours for the appropriate labor categories for the Prime Contractor and any subcontractor/IDT for the Sample Epic. The “Wrap Rate” column references the applicable Wrap Rates from the “B-Table” worksheet from CY1. The “Total Price” column includes formulas to calculate the prices by multiplying the proposed hours to the Wrap Rate for the Prime Contractor and the subcontractors/IDT. The “Total Price” utilizes the Excel ROUND function to the nearest dollar. The Total Price for the Prime Contractor and the subcontractors/IDT is then summed up in the last Total Price column. The Total Price for the Sample Epic shall not exceed $3,000,000.

The Total Price for Sample Epic will not be included as part of the Total Evaluated Price.

5.3.4.5 LH Rates at BEQ

This worksheet provides a summary of the LH Wrap Rates at the Best Estimated Quantity (BEQ) for CY1, CY2, CY3, CY4, and CY5. The “Wrap Rate” column references the applicable Wrap Rates from the “B-Table” worksheet. This worksheet is formulated to calculate the “BEQ Extension” for each labor category for the Prime Contractor and the subcontractors/IDT by multiplying the proposed Wrap Rate by the BEQ. The “Total Price” is the summation of the “BEQ Extension” for the Prime Contractor and the subcontractors/IDT. The “# Rates Proposed” column includes a formula that will calculate the number of rates proposed which will be used in the determining the Total Evaluated Price (TEP). The “TEP” is then calculated by dividing the “Total Price” by “# Rates Proposed”. The “BEQ Extension” and “TEP” utilizes

FA8730-17-R-0024, Attachment 5, Page 18 the Excel ROUND function to the nearest dollar. The “TEP” intentionally has “#DIV/0!” as once the B- Table LH Wrap Rates are input, this error will be corrected and the appropriate value will be automatically populated.

5.3.4.6 Price Track

This worksheet is used to summarize the impact of changes (e.g., revised labor hours, Wrap Rates, etc.)

that were made to the Offeror’s proposal in developing the Final Proposal Revision (FPR), if required.

Dollars in this format shall be rounded to the nearest dollar. The CR CLINs were intentionally omitted from the Price Track since it is a Government provided value.

Any changes in the Offeror’s proposal from initial to final shall be reflected through profit. The headings on the “Changes” column are for illustrative purposes only. The Offeror is free to delete those headings and substitute more appropriate headings that may be more descriptive of specific reasons for changes between Initial and Final proposals. The Offeror shall provide rationale to support each FPR adjustment.

6.0 VOLUME IV - CONTRACT DOCUMENTATION

6.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 one (1) signed copy of the Standard Form (SF) 33, Solicitation Offer and Award, and Sections A through K. The original shall be clearly marked and should be provided without any punched holes. Fill in all blanks in the Model Contract and in Sections A through K with either specific information or with “N/A” as applicable.

The following items are provided as informational only, and are not required to be provided as part of the offeror’s Volume IV, except for Section A, SF 33 and Attachment 4, DD 254 – Contract Security Classification Specification, which should be included as part of the offeror’s Volume IV submission.

6.1.1 Section A - Solicitation/Contract Form

Completion of blocks 12 through 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 under separate cover and should be provided without any punched holes. The proposal validity period shall be 180 days from the proposal due date.

6.1.2 Section B - Supplies or Services and Costs/Prices

Completed pricing information in Section B of the model contract.

6.135 Section E – Inspection and acceptance

See FA8730-17-R-0024 Section E for contract clauses pertinent to this section.

6.1.4 Section F - Deliveries or Performance

Period of performance

6.1.5 Section G - Contract Administrative Data

Contract administrative data

6.1.6 Section I – Contract Clauses

See FA8730-17-R-0024, Section I, for contract clauses pertinent to this section.

6.1.10 Section J – List of Attachments

Exhibit A - Contract Data Requirements Lists (CDRL) A list of CDRLs will be provided by the Government

FA8730-17-R-0024, Attachment 5, Page 19

Attachment 1 - Statement of Work (SOW) The DIB Development 5th Edition Statement of Work is provided by the Government.

Modifications to this document are not allowed.

Attachment 2 – Task Requirement Notices

A description of DIB Development 5th Edition TRN preparation and execution process. Appendix included: TRN Template.

Attachment 3 – Labor Category Descriptions

No additional labor categories may be proposed.

Attachment 4 – DD Form 254 – Contract Security Classification Specifications

The Offeror shall fill in all appropriate information in the DD Form 254, Contract Security Classification Specification. The Offeror’s proposed DD Form 254, when accepted by the Government, will be placed on contract at award.

Attachment 5 – Section L – Instructions For Proposal Preparation

Attachment L-1: Cross Reference Matrix Attachment L-2: Sample Epic Attachment L-3: Delivery Order 01 - Initial TRN The offeror shall fill in all appropriate information to complete the Initial TRN. The completed TRN will be used during Cost/Price proposal preparation and is intended to be the first TRN awarded for this contract as an attachment to the Initial Delivery Order.

Attachment 6 – Section M – Evaluation Factors for Award

Attachment 7 – Cost Formats

The following items should be included as part of the Offeror’s Volume IV submission.

6.1.11 Section K - Representations, Certifications, and other Statements of Offerors The offeror shall follow the instructions cited in Section K, FAR 52.204-08, DFARS 252.204-7007 and complete all representations, certifications, acknowledgments and statements in the System for Award Management (SAM) as part of responding to this RFP. If a representation, certification, acknowledgement or statement cited in this Section K cannot be found in SAM, then the offeror shall submit that Section K representation, certification, acknowledgement or statement. Failure to adhere to these instructions shall render an offeror as being ineligible for award.

6.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. Failure to meet a requirement may result in an offer being ineligible for award. 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 6.2.

FA8730-17-R-0024, Attachment 5, Page 20

TABLE 6-2. Solicitation Exceptions

Solicitation Document

Page/ Paragraph

Term and Condition

Rationale

SOW, Model Contract, RFP, etc.

Applicable Page and Paragraph Numbers

Identify the Solicitation Term and Condition or portion to which exception is taken

Describe why the Solicitation Term and Condition can/will not be met

6.3 Other Information Required

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