DRAFT_-_JBADS_DOR_May_2017.pdf

DOR-000X (________Delivery Order 000X) Draft as of 16 May 2017

DRAFT DELIVERY ORDER REQUEST (DOR)

DOR Number: (Insert DOR Number)

Date of Issue: (Insert date)

Description of Services: Joint Biological Agent Decontamination System (JBADS) Development, Production, and Support

Location of Services: Contractor location, Holloman AFB, and worldwide

Questions Deadline: (Insert date)

Closing Date & Time: (Insert date and time)

Incumbent: N/A

1.0 SUMMARY OF DOR.

1.1 This is a DOR for contractor support to be provided under the Joint Enterprise Research, Development, Acquisition and Production/Procurement Program (JE-RDAP) Multiple Award Indefinite Delivery Indefinite Quantity (MA IDIQ) contract. The Joint Program Executive Office for Chemical and Biological Defense (JPEO- CBD) has a requirement for Development, Production, and Support of the Joint Biological Agent Decontamination System (JBADS).

1.2 The delivery requirements documented in this DOR are in accordance with Sections B, C and H of the Basic JE- RDAP contract, W911QY-17-D-TBD (Solicitation Number W911QY-17-R-0010).

1.3 The Offeror’s Delivery Order Proposal (DOP) shall be in full compliance with the instructions in this DOR. The DOP (to include Cost/Price information) shall be valid for a minimum of 150 calendar days.

1.4 This DOR includes the following attachments:

Attachment 1: Performance Work Statement (PWS) Attachment 2: DD Form 1423, Contract Data Requirements List (CDRLs) Attachment 3: JBADS Performance Specification (PSpec) Attachment 4: Concept of Operations and Sample Deployment Information Attachment 5: C-130 Aircraft Dimensions Attachment 6: C-17 Weight load and Dimensions Attachment 7: JBADS Program Schedule Attachment 8: Notional System Design drawings (For Information Only, this does not dictate the design) Attachment 9: Draft Technical Review Action Plan Attachment 10: DD Form 254, Contract Security Classification Guide

Attachment 11: Past Performance Questionnaire

1.5 Delivery Order (DO) Type: The Government intends to award a base and seven options as follows:

Base – Engineering and Manufacturing Development (EMD): Cost Plus Incentive Fee (CPIF) Option 1 – Production: Fixed Price Incentive Fee (FPIF) Option 2 – Contractor Sustainment and Operational Readiness: CPIF Option 3 – Future Capabilities Analysis Cost Plus Fixed Fee (CPFF) Option 4 – JBADS System Deployment (CPFF) Option 5 – JBADS System Operation (CPFF) Option 6 – JBADS Technical Data Package (FFP) Option 7 – JBADS Technical Manuals (FFP)

1.6 In accordance with Federal Acquisition Regulation (FAR) 52.232-28, Offerors may propose performance based payments for the Production and Contractor Sustainment and Operational Readiness CLINS of this DO.

1.7 Period of Performance: (estimated dates – subject to change based on award date):

Base Period: EMD: November 2017-September 2019 (22 Months) Option Period 1: Production: October 2019-September 2021 (23 Months) Option Period 2: Contractor Sustainment and Operational Readiness: July 2019-July 2029 (10 years)

Option Period 3: Future Capabilities Analysis: October 2017-September 2019 (23 months) Option Period 4: System Deployment July 2019-July 2029 (10 years) Option Period 5: System Operation July 2019-July 2029 (10 years) Option Period 6: Technical Data Package 3 Months Option Period 7: Technical Manuals 6 Months

1.8 The award of this DOR is anticipated to be on or about First Quarter Fiscal Year 2017 (November 2017)

2.0 INSTRUCTIONS TO OFFERORS.

2.1 General Information.

2.1.1 Questions regarding this DOR shall be in writing and directed via e-mail to Ms. Yvette Daltorio, yvette.m.daltorio.civ@mail.mil. All correspondence shall reference DOR Number insert DOR Number. The cut-off for questions is insert date, time, Eastern Standard Time (EST). All questions will be answered electronically so that all the JE-RDAP Contractors will see both the questions and the answers. However, the identity of the person or company asking the question will not be disclosed.

2.1.2 The Government will not reimburse costs incurred for DOP preparation, to include pre-award site visits.

2.1.3 The Offeror shall submit an unclassified DOP which demonstrates its ability to perform and meet the requirements in the DO PWS and PSpec.

2.1.4 The DOP evaluation and discussion procedures of Federal Acquisition Regulation (FAR 15.3), Source Selection Procedures, do not apply to this acquisition. The Government will conduct evaluations using the best value trade off approach and will follow FAR 16.505 Ordering, and paragraph 5, Evaluation Criteria, considering solely the Offeror’s response to this DOR.

2.1.5 Although the Government does not intend to hold discussions, the Government reserves the right to conduct discussions if determined to be necessary.

2.1.6 Offerors are cautioned that, in order for a DOP to be considered eligible for award, it shall be in compliance with all the terms and conditions set forth in the DOR.

2.1.7 The value of this DO is expected to exceed $10,000,000; therefore, the Offeror shall be subject to a pre-award compliance evaluation by the Office of Federal Contract Compliance Programs (OFCCP), unless the terms of FAR 52.222-24 have been met. It is anticipated the resultant Delivery Order will include FAR 52.222-26.

2.1.8 Email Submission. The Offeror shall submit its DOP electronically via email to the Contract Specialist identified in 2.1.1. Offerors shall NOT submit DOP via the Federal Business Opportunities (FBO) website.

2.1.8.1 The DOR will be issued electronically, as well as any DOR amendments subsequently issued thereto.

2.1.8.2 Offerors shall be registered in the System for Award Management (SAM) at www.sam.gov with a status of Active and no active exclusion records in order to submit a DOP.

2.1.8.3 The Offeror bears the responsibility to ensure timely transmission of their DOP offer, that the DOP offer is responsive to all requirements set forth in the solicitation, the availability of an open transmission line, and to take into consideration the length of time required to complete an upload transaction prior to the solicitation closing date/time stated in the solicitation. Under no circumstances shall the tender of any DOP offer or other required document that is filed beyond any filing deadline be considered timely. Late filing shall result in an offer/DOP being considered untimely and will not be considered for award.

2.1.8.4 Each complete DOP in response to this DOR shall be submitted individually, and must be separately and correctly identified. Multiple proposals will be accepted.

2.1.8.5 A prospective Offeror shall have sole responsibility for ensuring that all electronic responses are submitted correctly, are properly identified, contain all the information requested by the Government, are responsive, and timely filed.

2.2 Participation of Commercial Firms in the Evaluation Process:

2.2.1 The Government will use the contractor(s) listed below to provide administrative support during the evaluation of proposals submitted in response to this DOR. The contractor(s) is restricted by the “Organizational Conflict of Interest” provision of its respective contract from participating as a contractor, sub-contractor, or consultant on the proposed program other than on a non-competitive basis under a prime contract with the Government. The individual from this company will execute a “Certificate of Non-Disclosure” prior to review of the proposal. By submitting a proposal, the Offeror agrees to permit the contractor(s) listed below to view proposal information to the extent necessary to provide administrative support to the Government’s proposal review process.

2.2.2 Pursuant to FAR Part 9.505-4, and if requested by an Offeror, the contractor listed below must execute an agreement with each Offeror that states that it will protect the Offeror’s information from unauthorized use or disclosure for as long as it remains proprietary, and refrain from using information for any purpose other than that for which it was furnished. To expedite the evaluation process, each Offeror must contact the contractor to effect execution of such an agreement prior to the submission of proposals. Each Offeror shall submit copies of the agreement with their proposal. The Agreement shall be attached to DOP Volume I as an appendix, and will not be included in the page count. The contractor supporting this proposal evaluation process is:

CONTRACTOR NAME

CONTRACTOR ADDRESS

Point of Contact (POC):

2.2.3 The Offeror shall submit DOP information in separate files as specified below, replacing “xxxx” with the Offeror’s name and the date of the proposal. Do not use periods (.) in any document titles as they will be rejected by the Government systems. Example, AcmeTECHNICAL090116.docx/pdf or similar. The Offeror shall ensure that all required documents are included in the DOP. See Table 2-1 below:

Table 2-1. Delivery Order Proposal Content and Structure

(*Note: Résumés and the Sanitized Cost Proposal (paragraph 4.1.4.4 below) do not count toward the page limitation.)

3.0 DELIVERY ORDER PROPOSAL PREPARATION INSTRUCTIONS.

3.1 Format: The Offeror’s written DOP submission shall be clearly indexed and logically assembled. Each volume shall be clearly identified and shall begin at the top of a page. All pages of each volume shall be appropriately numbered and identified by the complete company name, date, and DOR number in the header and/or footer. The following additional conditions apply:

DOP

Volume

Title

File Name

Page Limit

I TECHNICAL

Technical Approach, (Factor 1) Production Approach (Factor 2) xxxx TECHNICALxxxx.docx/pdf xxxx PRODUCTIONxxxx.docx/pdf

II LOGISTICS

Logistics Approach (Factor 3) Operational Mission Support (OMS) (Factor 4) xxxx LOGISTICSxxxx.docx/pdf xxxx OpMissionSupport.docx/pdf

III MANAGEMENT

Management Approach (Factor 5) xxxx MANAGEMENTxxxx.docx/pdf

20*

IV COST/PRICE (Factor 6) Cost Narrative Cost Proposal

Sanitized cost Proposal* xxxx COSTNARR xxxx.docx/pdf xxxx COST xxxx.xlsx xxxx SANITIZEDCOST xxxx.xlsx

Unlimited

V PAST PERFORMANCE (Factor 7) xxxx PASTPERFxxxx.docx/pdf Unlimited

VI SMALL BUSINESS UTILIZATION (SBU)

(Factor 8) xxxx SMALLBUSINESS xxxx.docx/pdf

Unlimited

VII: ADMINISTRATIVE

Section I – Executive Summary Section II –Solicitation Documents Section III – DCMA and DCAA POCs, CAGE, DUNs and TIN and Prime’s financial documents Section IV – Information Other than Certified Cost or Pricing data Section V – Subcontracting Plan Section VI – OCI Mitigation Plan Section VII – System for Award Management

(SAM)

Section VIII- Teaming Agreements xxxx ADMINISTRATIVE xxxx.docx/pdf

Sec I – 5 page limit

Sec II – No page limit Sec III – No page limit Sec IV –20 page limit* Sec V – 35 page limit* Sec VI –30 page limit* Sec VII – 1 page limit

3.1.1 All information the Offeror wishes to have considered must be submitted with the initial DOP and shall be confined to the appropriate volume and within the specified page limitation. The Government will not consider any information that is not included in the appropriate volume as required, or any information that exceeds the number of pages allowed. Pages exceeding the limitation will be removed from the proposal prior to evaluation and will not be considered.

3.1.2 Indices to include a table of acronyms, a table of contents, and cross-reference matrices between the proposal and the solicitation shall be used to ensure that all pertinent sections of the proposal are addressed. The cross-reference matrix should identify the location of all major topics provided in each volume.

3.1.3 The title page for each volume shall include: volume number, volume subject, and company name.

3.1.4 Volume pages shall not exceed 8.5 inches in width and 11 inches in length; however, foldout pages, as appropriate, not exceeding 11 x 17 inches, depicting such items as charts, matrices, or schedules may be used and will count as a single page. Margins at top, bottom, left and right should equal 1”, with 0” Gutter. Headers and Footers should be 0.5” from page edge.

3.1.5 The Offeror’s proposal shall not exceed the above page limitations and must be printed using a 12 point font (graphics, figures, tables, foldout pages or electronic spreadsheets - 10 point font) with one-inch margins (top, bottom, left, and right). Offerors may utilize six (6) point font for “Use or Disclosure” and export disclaimers in the footer of the document. Pages printed on both sides will count as two (2) pages. The cover page, tables of contents/figures, acronym list, tabs, and cross-referencing matrices do not count against page count limitations.

3.1.6 The Offeror is expected to provide sufficient detail in a clear and concise manner to completely and logically address the evaluation factors and criteria. The Government does not desire excess verbiage, unnecessary and elaborate brochures, or lengthy, repetitious, disorganized presentations. All Offerors are reminded that unsupported promises to comply with the contractual requirements will not be sufficient.

Proposals shall not merely repeat back the contractual requirements, but rather their DOP shall support any statements relating to the proposed performance.

3.1.7 The Government will presume that the DOP received represents the Offeror’s best efforts to respond to the DOR. In the DOP the Offeror shall explain any inconsistency(ies) between proposed performance and cost/price.

3.1.8 The Offeror shall include ONLY cost/price information in Volume IV: Cost/Price. Inclusion of cost/price data in other volumes will result in the removal of each page or tab containing the cost/price data and the pages and tabs will not be evaluated or considered.

3.1.9 Each volume (file) shall be a stand-alone document or workbook (for cost/price data) and clearly and completely provide the required information. The Government will evaluate each file in accordance with the source selection evaluation criteria described in Section 5 of this DOR.

4.0 DELIVERY ORDER PROPOSAL CONTENT.

4.1 Specific Instructions by Volume. The Offeror shall provide their DOP, segregated by volume as follows:

4.1.1 VOLUME 1, TECHNICAL

4.1.1.1 Technical Approach:

4.1.1.1.1 The Offeror shall describe the system to be developed and the technical approach proposed to meet the requirements in the PWS and PSpec. The Offeror’s system description shall include system and component capabilities and technology maturity levels. The Offeror’s system description shall include the proposed methodology to control the environmental conditions necessary to facilitate the bio-thermal decontamination process as well as the potential failure modes, operating parameters, and processes. The Offeror’s shall also include their plan to monitor, record, and submit the operating data to the Government. Additionally, the Offeror shall include a compliance matrix cross-walking the proposed technical approach against the requirements in the PSpec. The Offeror shall provide a description on any approaches that may exceed threshold requirements with little or no impact to cost or schedule.

The Offeror shall include in its proposed system and processes the information described in the subparagraphs below:

4.1.1.1.1.1 A a technical description of the system being offered to include all materials utilized. This description shall include part numbers or National Stock Numbers (NSN), if assigned. Offerors are encouraged to submit product literature that describes commercial make, model number, and any other literature that reinforces the commerciality of the offered item(s). This literature is separate from the Technical Volume and does not count against page limitations. Nonetheless, Offerors should only submit relevant product literature.

4.1.1.1.1.2 Documentation (Certifications /Test Reports). A summary of available test reports to support performance, capabilities, and any risks associated with the offered system’s ability to meet and verify the requirements described in the JBADS PSpec and PWS. The Offeror shall include complete copies of unclassified test reports. The Offeror shall discuss the test results to include clearly differentiating between in-house, independent, and Government testing. The Offeror shall also indicate if it used a Government test procedure. All test data discussed shall include at a minimum the test scope, the location of the test, who conducted the test, the test environment, and a summary of the test results. The Offeror is responsible for presenting the technical information in a manner that is clear, concise and easily understood. The test reports shall be submitted to Ms. Yvette Daltorio, yvette.m.daltorio.civ@mail.mil via the U.S. Army Aviation and Missile Research Development and Engineering Center (AMRDEC) Safe Access File Exchange (SAFE), https://safe.amrdec.army.mil/SAFE/. The test reports do not count towards page limit. Note: Pre-production verification testing may be required if modifications are done to a component(s) to ensure the original component(s) maintain the previously reported performance capabilities.

4.1.1.1.1.3 Drawings to include the approach to integrating all components into a single system.

4.1.1.1.1.4 A description of the system safety concerns involving maintenance, sustainment and operating procedures to include material safety and toxicity. The Offeror shall include as an appendix to this volume all Material Safety Data Sheets (not counted against the page limit of this volume).

4.1.1.1.1.5 A description of how the use of open systems architecture will impact the JBADS systems with regard to cost, schedule, performance, and sustainment independent of the criteria referenced in 4.1.2.1.2.

4.1.1.1.1.6 A description of the Offeror’s strategy to test the JBADS performance to meet the PSpec requirements and Government’s schedule. The Offeror shall describe the strategy and time needed to perform Contractor Specification Testing / PVT-2. Note: Pre-production qualification testing may be required if modifications are done to a component(s) to ensure the original component(s) maintains the previously reported performance capabilities.

4.1.1.2 Production Approach:

4.1.1.2.1 The Offeror shall describe its production approach and the extent to which the proposed system meets or exceeds the requirements as stated in the PWS and the JBADS PSpec. The Offeror shall describe its methods and processes as outlined in the following subparagraphs and shall submit the following documentation and/or details:

4.1.1.2.1.1 A description of the Offeror’s approach to fabrication and inspection associated with the JBADS end item. The Offeror shall provide a Manufacturing Plan that includes production quantity capabilities for the period of performance of the contract.

4.1.1.2.1.2 Identification of production facilities, equipment, quality systems, and critical manufacturing processes that will be used for production, to include identification of critical processes and components produced by subcontractor(s) and their production facilities and equipment. The Offeror shall describe how the production facilities and equipment possess the production capacity to meet or reduce the time required to deliver the JBADS system.

4.1.1.2.1.3 The Offeror shall provide the completed, Vendor sections of the Manufacturing Assessment Questionnaire and supporting documentation to support a Manufacturing Readiness Level (MRL) of 7 (the MRA questionnaire and supporting documentation does not count towards page limit).

4.1.1.2.1.4 A detailed description of its Configuration Management and Risk Management processes to support the requirements as written in the PWS and PSpec, to include how they are implemented. This shall include how the Offeror plans to mitigate technical risk associated with all materials utilized, including those obtained from subcontractors and vendors.

4.1.1.2.1.5 A detailed description of its Quality Assurance (QA) plan, to include management of major suppliers, subcontractors, or teaming partners, and a detailed description of its QA processes and procedures to ensure the manufacture of acceptable products. The Offeror shall include a detailed description of its plan to handle defects, technical shortfalls, and obsolescence.

4.1.1.2.1.6 The Offeror shall describe any requirement for long lead items and time frame to procure the long lead items. Additionally, the Offeror shall describe any requirement to procure parts or components that could jeopardize the program schedule that do not qualify as long lead items.

4.1.1.2.1.7 If an Offeror possesses any certifications associated with production and manufacturing such as ISO, CMMI, etc., a copy of the certification should be included in the technical volume as an appendix. The Certifications do not count towards the page limit.

4.1.1.2.1.8 The Offeror shall provide the terms and conditions of any system or component warranties and evidence if a system warranty is included as part of the system price and will be valid. The Offeror shall also describe if the warranty is valid after any proposed modifications of the components due to integration of the system.

4.1.2 VOLUME II, LOGISTICS

4.1.2.1 Logistics Approach:

4.1.2.1.1 The Offeror shall describe its logistics approach and the extent that the proposed system meets or exceeds the requirements as stated in the PWS and JBADS PSpec while minimizing support and ownership burdens. The Offeror shall describe its methods and processes as outlined in the following subparagraphs and submit the following documentation/and or details:

4.1.2.1.1.1 Comprehensive description of Offeror’s proposed JBADS operating, maintenance, and sustainment procedures.

4.1.2.1.1.2 Description of how the Offeror’s proposed system can attain, as a minimum, the threshold values for reliability, availability, and maintainability metrics as specified in the JBADS PSpec. This description shall include Original Equipment Manufacturer (OEM) reliability information on Commercial-Off-the-Shelf (COTS) items used as major sub-system components (not included as part of page count). Additionally, the Offeror shall provide test reports that include, but are not limited to, the following equipment data:

a. Direct reliability estimates supplied by the OEM.

b. Reliability estimates of modules and components under the same OEM product line.

c. Reliability estimates based on products from other manufacturers of similar items.

d. Reliability estimates based on published product life expectancy.

The test reports discussed shall be included in full as appendices. The summarized discussion of test reports shall include, at a minimum, the test scope, the location of the test, who conducted the test, the test environment, a summary of the test results, and indicate if the test was done for the Government or uses a Government test procedure. The test reports do not count towards this volume’s page limit. These shall be submitted to Ms. Yvette Daltorio, yvette.m.daltorio.civ@mail.mil via the U.S. Army Aviation and Missile Research Development and Engineering Center (AMRDEC) Safe Access File Exchange (SAFE), https://safe.amrdec.army.mil/SAFE/.

4.1.2.1.1.3 Care of Supplies in Storage (COSIS) Plan. The Offeror’s plan shall describe how the JBADS components and equipment will be accounted for and maintained ready to deploy. This plan shall address system support to include the availability of spares and personnel necessary to support the sustainment phase. Additionally, the plan shall include specific actions and personnel required in order to conduct the annual system health inspection and biennial readiness exercise.

4.1.2.1.1.4 Description of the Offeror’s proposed storage and packaging processes and methods. The Offeror shall also describe (or provide) transportation certification of the system and the process for achieving that certification.

The Offeror shall describe packaging materials as defined in the PWS, paragraph 3.1.13. Certifications provided do not count towards the page limit in this volume.

4.1.2.1.1.5 Description of Human Systems Integration (HSI) during maintenance, sustainment, and operation of the JBADS including risks and risk mitigation.

4.1.2.1.1.6 Detailed description of tooling and Material Handling Equipment (MHE) required to operate and maintain the JBADS. Specialized equipment that can only be used in the Offeror's proposed system and that are not readily available commercially should be reduced to the lowest extent possible.

4.1.2.1.1.7 Description of Offeror’s approach to training personnel to accomplish and maintain proficiency in operating the System, assembly/ disassembly of the System, scheduled maintenance and/or repairs of the Systems including any improvements to the aforementioned biennial exercise that reduces cost while maintaining proficiency.

4.1.2.1.2 The Offeror shall describe its approach to Open System Architecture within the JBADS by addressing the information requested in the following paragraphs.

4.1.2.1.2.1 The Offeror shall propose the extent to which the rights in Technical Data (TD), Computer Software (CS) and Computer Software Documentation (CSD) offered to the Government ensure unimpeded, innovative, and cost effective production, operation, maintenance, and upgrade of the JBADS throughout its life cycle; allows for open and competitive procurement of JBADS enhancements; and permits the transfer of the JBADS non-proprietary object code and source code to other contractors for use on other systems or platforms. The Data Rights and Licenses offered shall be provided as an attachment to the Logistics Volume, but shall not count against the page limit.

4.1.2.1.2.2 The Offeror shall describe its plan for making design and interface information available as soon as possible after it is defined or established. The Offeror shall describe how it plans to establish and maintain a process that will provide “early and often” design disclosure directly to the Government or to third-party contractors via Government-established access.

4.1.2.1.2.3 Rights in Noncommercial TD, Noncommercial CS, and Noncommercial CSD. The Offeror shall provide a list identifying all Noncommercial TD, CS, and CSD that it asserts should be delivered with other than unlimited rights. Specific instructions and requirements concerning this list are set forth in the DFARS 252.227- 7017 “Identification and Assertion of Use, Release, or Disclosure Restrictions” (January 2011) provision. If the Offeror is awarded a contract, the List shall be attached to the contract (hereinafter referred to as the 7017 List).

4.1.2.1.2.4 The Offeror shall attach to its offer and provide a statement, entitled “Supplemental Information— Noncommercial Technical Data, Noncommercial Computer Software, Noncommercial Computer Software Documentation” (the statement) that, for each item of Noncommercial TD, CS, or CSD that the Offeror asserts should be delivered with specifically negotiated license rights or other non-standard rights (as discussed at DFARS 252.227-7013 “Rights in Technical Data –Noncommercial Items” and/or DFARS 252.227-7014 “Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation”), sets forth a complete description of all such proposed non-standard restrictions on the Government’s ability to use, modify, release, perform, display, or disclose such TD, CS, or CSD. This information may be provided by referencing any proposed non-standard license agreement that is attached to the statement. The Offeror shall submit the statement as an attachment to its offer/DOP, dated and signed by an official authorized to contractually obligate the Offeror. If no information is to be included in the statement, the Offeror need not submit the statement. If the Offeror is awarded a Delivery Order, any statement provided will be attached to the DO.

4.1.2.1.2.5 Rights in Commercial TD, Commercial CS, and Commercial CSD. The Offeror shall provide a list, entitled “Commercial TD, Commercial CS, and Commercial CSD-Government Use Restrictions” (the Commercial Restrictions List), that provides the following information regarding all commercial TD, CS, and CSD that the Offeror (including its sub-offerors or suppliers, or potential sub-offerors or suppliers, at any tier) intends to deliver with other than unlimited rights:

4.1.2.1.2.6 Identification of the technical data or software; (2) basis for asserting restrictions, such as licensed products including open source software; and (3) name of the entity asserting restrictions. For any item designated as Non-Developmental Item (NDI), the Offeror is requested to provide details of the Agency and level therein that paid for development and the contract number(s) and dates wherein payments were received. For each entry in the list citing an asserted rights category other than the standard license rights applicable to commercial TD as set forth in the DFARS 252.227-7015 “Technical Data – Commercial Items” (February 2014) clause, the Offeror shall provide a complete description of the asserted rights, e.g., a specially negotiated license, open source software license, or any license customarily offered to the public; this information may be provided by referencing any proposed nonstandard or commercial license agreement that is attached to the list, but in all cases, the non-standard or commercial license will be attached for Government review. The Offeror shall submit the Commercial Restrictions List as an attachment to its DOP, dated and signed by an official authorized to contractually obligate the Offeror. If there is no information to be included in the Commercial Restrictions List, the Offeror shall submit the list and enter “None” as the body of the list. If the Offeror is awarded a DO, the Commercial Restrictions List shall be attached to the DO.

4.1.2.2 Operational Mission Support (OMS):

4.1.2.2.1 The Offeror shall describe its approach to providing OMS to facilitate worldwide deployment of JBADS and explain the extent to which the proposed system meets the requirements as stated in the JBADS PSpec and PWS. The Offeror shall describe its methods and processes to:

a. support the JBADS Concept of Operations (ConOps)

b. respond to the sample deployment location information (provided as Attachment 4)

c. enable OMS as outlined in the following subparagraphs:

4.1.2.2.1.1 A detailed description of the Offeror’s approach/plan for providing OMS. The description should demonstrate sufficient understanding of the process required to facilitate worldwide deployment of JBADS in a military environment to include coordination with the USAF and ensuring that Offeror personnel are able to deploy within the time requirements specified in the PWS, PSpec, and ConOps. The description shall thoroughly document the activities, methods, processes, and manpower required to assemble, operate, repair, disassemble, repackage, and redeploy the JBADS, to include risks and mitigations.

4.1.2.2.1.2 A detailed description of the transport configuration of the system and an analysis of material requirements to prepare and transport the systems from the storage location at Holloman AFB to the sample deployment location(s) (in Attachment 4). The analysis shall include weight and cube of a JBADS packed for transportation and the number of C-17 aircraft required to transport the system to deployment locations from the storage location to include risks and mitigations.

4.1.3 VOLUME III, MANAGEMENT

4.1.3.1 Management Approach:

4.1.3.1.1 The Offeror shall include a discussion of its overall Program Management approach and how its approach stays within the cost, schedule and performance requirements of the JBADS PSpec and PWS. The Offeror shall discuss its approach for identifying, managing, and mitigating the technical, schedule, and cost risks associated with the requirements of the PWS and PSpec.

4.1.3.1.2 The Offeror shall include an organizational chart to include subcontractors. The organizational chart shall include alignment to higher level corporate structure, JBADS program management, identification of subcontractors, and other participating entities to meet the JBAD program needs as stated in the PWS and PSpec. The Offeror’s proposed structure shall clearly identify roles and responsibilities (of personnel and subcontractors), clearly define lines of authority and span of control, and provide adequate alignment with the PWS. The Offeror shall also describe its approach to managing subcontractors.

4.1.3.1.3 The Offeror shall propose a Contract Work Breakdown Structure (CWBS) to two or more levels that is consistent with the Offeror’s business processes and is cross referenced to the PWS and PSpec (does not count towards page limit).

4.1.3.1.4 The Offeror shall provide an Integrated Master Schedule (IMS) defining the Offeror’s proposed time phasing of detailed tasks for the contracted effort segregated by option to meet the needs of the PWS and PSpec. The IMS shall define dates and time frames for all contract tasks, milestones, reviews, and deliverables. The IMS and CWBS shall include a brief description of the resources required to complete each task which should align with information provided in the Sanitized Cost (uncosted).

4.1.3.1.5 The Offeror shall identify the necessary technical resources and expertise to support the initiation and completion of the program including planning, execution, management, and responsibility for total system performance and the ability to integrate subcontractor products. The Offeror shall provide any certifications it possesses that are associated with its management approach; a copy of any certification shall be included in the management volume as an appendix and does not count against the volume page limit.

4.1.3.1.6 Property Management. The Offeror shall provide a Property Management Plan, in accordance with FAR 52-245-1(f)(1)(i-x), describing its approach to managing government property throughout the performance of the DO (two-page limit and which does not count toward page count Management proposal page limit). The Offeror shall provide a brief overview addressing the following ten outcomes:

(1) Acquisition. How property acquisitions are documented, per FAR 52.245-1(f)(1)(i).

(2) Receipt. How property receipt is documented, recorded, and identified per FAR 52.245-

1(f)(1)(ii).

(3) Records of Government Property. How property records are created and maintained, per FAR

52.245-1(f)(1)(iii).

(4) Physical Inventory. Methods to perform, record, and disclose physical inventory results, per FAR

52.245-1(f)(1)(iv).

(5) Subcontractor Control. Whether contractual terms and conditions are flowed down to subcontractors, per FAR 52.245-1(f)(1)(v)(A); how subcontracts are properly administered; and, when reviews of subcontractor Property Management Systems are performed, per FAR 52.245- 1(f)(1)(v)(B).

(6) Reports. The process to create and provide property-related reports, per FAR 52.245-1(f)(1)(vi).

(7) Relief of Stewardship Responsibility and Liability. The process to recognize, investigate, and report losses of Government property, per FAR 52.245-1(f)(1)(vii).

(8) Utilization. How Government property is to be used, consumed, moved, and stored, per FAR

52.245-1(f)(1)(viii).

(9) Maintenance. How Government property is to be maintained, and when property requiring replacement and/or capital rehabilitation is to be reported to the Property Administrator, per FAR 52.245-1(f)(1)(ix).

(10) Property Closeout. How property closeout is performed and when it is reported to the Property Administrator, per FAR 52.245-1(f)(1)(x).

4.1.4 VOLUME IV, COST/PRICE

4.1.4.1 Cost Narrative.

4.1.4.1.1 Purpose. The Cost Narrative shall include documentation and rationale that shows how specific proposed costs and rates were determined. Offerors are generally discouraged from duplicating tables shown in the Offeror’s Excel Cost Proposal as Cost Evaluators will have access to both the Cost Narrative and the Excel Cost Proposal.

4.1.4.1.2 Attachments. The Government prefers that the Offeror provide required cost narrative contents within one file; however, if doing so adversely affects readability due to technical constraints (e.g. the file size would be too large to smoothly navigate the file), then Offerors may employ the use of attachments.

4.1.4.1.3 Narrative Contents. The Cost Narrative shall contain sufficient documentation necessary to adequately support and explain the rates and costs proposed in the Offeror’s Excel Cost Proposal as required below:

4.1.4.1.3.1 Identifying Information. The name and address of the Offeror; name, e-mail address, and phone number of the point of contact and alternate; and a list containing either the Data Universal Numbering System (DUNS) number or the Government and Contractor Entity Code (CAGE) code for the prime Offeror and each subcontractor.

4.1.4.1.3.1.1 Accounting System. An Offeror shall state whether the proposal is consistent with its approved cost accounting system (CAS) and/or disclosed practices.

4.1.4.1.3.2 Price Summary. The Offeror shall provide a one (1) page, summary-level break-out showing CPIF for the based period of performance and the contract type for each of the options, through 5 (reference paragraph 1.5).

4.1.4.1.3.3 Direct Labor. The Offeror shall provide the following to support proposed direct labor:

4.1.4.1.3.3.1 Initial Rates: Data or documentation that shows the basis of estimate for direct labor rates, including one of the following: 1) Payroll data such as actual average labor rates for labor categories; 2) Internal wage statistics; 3) Paystubs; 4) A Forward Pricing Rate Agreement (FPRA) signed by DCMA; 5) A Forward Pricing Rate Recommendation (FPRR) signed by DCMA; 6) A DCAA audit or DCMA review of actual rates; 7) “Letters of Intent” to include the position and pay rate; 8) SCA schedule rates OR 9) market research/statistical data (e.g.

http://data.bls.gov/oes/).

4.1.4.1.3.3.2 Escalation: How escalation is to be applied and if the method presented is in accordance with a standard company policy.

4.1.4.1.3.3.3 Premium Pay: Any monetary compensation employees would receive above their labor rates (e.g., danger pay, post hardship differential, cost of living allowances, etc.). For each type of pay premium the Offeror intends to use, the cost narrative shall state: 1) proposed rates, and 2) how proposed rates will be applied (i.e., rate* direct labor). Offerors may propose premium pay as ODC as in accordance with its disclosed practices.

4.1.4.1.3.3.4 Service Contract Act (SCA): The Offeror and any subcontractor(s) shall be responsible for ensuring compliance with the SCA for all applicable labor categories. If the Offeror believes that labor categories are subject to the SCA, they shall identify such labor categories as “SCA Labor” in their proposal. The Offeror shall also disclose the state and county in which the proposed SCA labor categories will be performing its effort, the Wage Determination Schedule used for its proposed SCA labor rates, and the Occupation Code and Title for each proposed SCA labor category.

4.1.4.1.3.4 Indirect Expense Rates: The Offeror shall support that indirect expense rates proposed are realistic estimates. Acceptable support includes providing 1) an FPRA signed by DCMA; 2) an FPRR signed by DCMA; 3) a recent DCAA audit of indirect rates; 4) a DCMA review of indirect rates; 5) actual indirect expenses by expense account and base expense costs for the past three fiscal years; OR 6) An agreement to cap reimbursable indirect expense rates (See FAR 42.707). Note that 1) provisional billing rates are not acceptable documentation unless DCMA or DCAA explicitly states that they are applicable or appropriate for estimating or proposal preparation purposes, and 2) an FPRP is not acceptable unless it is supplemented by one of the methods listed in this paragraph for all proposed indirect rates. All proposed indirect expense rates shall be supported to be determined realistic.

4.1.4.1.3.5 Subcontracts: The Offeror shall provide the following for each proposed subcontractor:

4.1.4.1.3.5.1 Quote: A quote for each subcontract identifying the agreed to price and contract type. Offerors shall describe/explain any differences between the quoted price and the subcontractor breakout in the Excel Cost Proposal.

4.1.4.1.3.5.2 Price Analysis: The prime contractor shall, IAW 15.404-3(b), conduct a price analysis [cost analysis is not required, as certified cost or pricing data are not anticipated to be required IAW FAR 15.404-1(a)(2&3)], and include the results of this analysis in the narrative. See FAR 15.404-1(b)(2) for common price analysis techniques.

4.1.4.1.3.5.3 Basis of Estimates for Rates and Costs: Cost reimbursable subcontractors exceeding 10% of the Offeror’s proposed cost shall submit the same level of detail as is required of the prime to support proposed rates and costs (e.g. direct labor, indirect expense rates, etc.). If this level of detail is considered to be proprietary, subcontractors may provide a separate Cost Narrative and Cost Proposal directly to the Government. Fixed Price and Time and Materials (T&M) subcontract types do not require this level of detail. Offerors shall describe what, if any, contractual controls would be in place to help ensure proposed costs are reliable estimates (such as a “Not to Exceed” price or ceiling rates effective for the effort).

4.1.4.1.3.6 Materials, Equipment, and ODCs. All proposed materials, equipment, and ODCs (such as shipping or warehousing costs) that contribute more than $10,000 in total proposed value per item shall be supported by vendor/supplier quotes, catalog pricing, or historical pricing documentation. Item is defined as having the same part number or same series number or same description from same vendor/source (i.e. Maximo License at $1,100 each and a quantity of 10 equated to $11,000 in total value is required supporting documentation). Proposed DBA insurance rate(s) shall be supported by either a quote specific to the DOR or previously obtained quotes for similar efforts.

4.1.4.1.4 Government Furnished Property (GFP): If GFP is required in the performance of this DO, other than specified in this DOR, the Offeror shall include a table in its cost narrative identifying: 1) what property is needed,

2) the acquisition cost of each item, and 3) the duration (in months) that the GFP would be in its possession for performance on this effort.

4.1.4.1.5 Travel: Quotes and per diem rate schedules are not required to support proposed travel costs and need not be addressed in the cost narrative. Offerors should be aware that travel costs should follow the guidelines in the Joint Travel Regulations (JTR), and they will only be reimbursed for reasonable, allowable, and allocable expense.

4.1.4.1.6 Certified Cost or Pricing Data: In the event that adequate price competition does not result from this DOR, the Government will require a Certificate of Current Cost and Pricing Data from the Offeror prior to award.

4.1.4.2 Cost Proposal (Excel Format).

4.1.4.2.1 The Offeror shall not include citations for or linkages to websites and external files in its cost proposal.

Cost Proposals shall contain the following:

4.1.4.2.1.1 Summary Tab: This tab shall rollup every proposed CPFF price to arrive at the overall proposed price for the TO.

4.1.4.2.1.1.1 In accordance with CLIN 0022 and Section H, paragraph H.9 of the basic contract, travel and ODCs shall be non-fee bearing. Offerors shall separate non-fee bearing costs and fee bearing costs prior to compute fee amounts. Target, Minimum, Maximum fee in term of percentages shall be applied to fee bearing costs only.

4.1.4.2.1.2 CPIF, and CPFF, FFP, FPIF Breakout Tabs: Each tab shall contain a rollup of proposed costs by cost element (e.g., direct labor, indirect expense rates, etc.) for the Base, Option 1, Option Year 2, Option 3, Option 4, Option 5, and Option 6. Offerors do not need to breakout costs by WBS; however, overall proposed resources (e.g., Program Manager’s hours) shall be traceable to and match aggregate quantities broken out by WBS in the Offeror’s uncosted (Sanitized) volume. Common cost elements for this breakout shall include: labor categories; hours by category; direct labor rates by category; each indirect expense rate; materials; material quantities; material unit prices; references to overall travel costs and subcontract costs which are further broken out on other tabs; Other Direct Costs (ODC) quantities and unit prices.

4.1.4.2.1.3 Travel Tab: This tab shall provide a breakout of proposed travel that falls under CPFF and CPIF CLINs.

4.1.4.2.1.4 Subcontractor Tab(s): Each subcontractor’s proposal shall be broken out on separate tabs of the prime Offeror’s “Cost Proposal” workbook with the subcontractor’s name and contract type as the tab’s name (e.g., “ABC Tech – T&M”, etc.).

4.1.4.2.1.4.1 Fixed price and T&M type subcontracts (e.g., FFP, T&M, FFP Level of Effort (LoE), etc.): This tab provides uncosted elements (e.g., hours by category, trips, materials, equipment, ODC quantities, etc.) and fully loaded rates (which may include profit). No further breakout is required.

4.1.4.1.4.2 Cost reimbursable type subcontracts (e.g., CPFF, CPIF, etc.): (Excel Format) This tab provides the same level of detail required of the prime Offeror. If the prime Offeror is unable to provide this level of detail due to the subcontractor deeming this level of detail to be proprietary, then the Offeror shall, at a minimum, provide uncosted elements and fully loaded rates that the subcontractor is proposing; then, the subcontractor shall provide the required level of detail directly to the Government by the date and time that the proposals must be delivered.

4.1.4.2.1.5 Material, equipment and ODC Tab(s): This tab shall provide a breakout of proposed materials, material quantities, material unit prices, and ODC quantities of UoM and unit prices. Materials and ODCs may be provided in separate tabs.

4.1.4.3 Sample deployment pricing. Offerors shall use the sample deployment contained in Attachment 4, Concept of Operations and Sample Deployment Information as the basis for costs for CLIN 0005 and CLIN 0006 . Costs shall include any relevant costs for transportation and per diem for preparing the JBADS for deployment as well as the actual deployment itself.

4.1.4.4 Sanitized Cost Proposal (Excel Format). Offerors shall provide a sanitized copy of the Cost/Price proposal (Excel Format), and its subparagraphs, with all costs removed. Offerors shall remove the CLIN Price Summary tabs/worksheets from the sanitized copy. Proposals that fail to separate cost information from the Technical Volume may be determined to be non-responsive and may not be considered for award.

4.1.4.4.1 The Government will use information presented in this workbook to determine if proposed uncosted elements are realistic for the Offeror’s technical approach, with results incorporated in the Cost Realism Analysis.

4.1.4.5 Labor Category (LCAT): Offerors shall ensure there are no labor rates included in the sanitized copy, to include a LCAT tab that lists the following for each labor category/individual for both prime Offerors and subcontractors (if proposed):

4.1.4.5.1 A Descriptive Labor Category: Only labor categories specific to job functions shall be presented (e.g., “Chemist”, “Environmental Scientist”, and “Physicist” are all sufficiently descriptive; whereas, “Scientist” is not specific to the job function).

4.1.4.5.2 Indicate if the individual identified by the labor category is part of the Offeror’s current workforce or would be a new hire. The Offeror shall also indicate whether the individual identified is employed by the prime or subcontractor and the place of performance of that individual (CONUS or OCONUS).

4.1.4.5.3 Job Function: Provide a short description of job duties and/or competencies.

4.1.4.5.4 Typical Experience Level: Identify a typical level of education and experience for this category (e.g., 4 year degree in engineering and 5 years of experience). Note, that while some individuals can reach an experience level quicker than others and some individuals stay at an experience level longer than others, typical experience levels identified shall represent the Offeror’s best estimate of the experience and education of an average individual within the category.

4.1.4.6 Equipment, Materials, and Other Direct Costs (ODC): Offerors shall ensure there are no unit prices included in the Equipment, Materials or ODC tab(s).

4.1.4.7 Cohesion with Other Required Files: To ensure traceability between required files, the Offeror shall ensure that uncosted elements are identically named between documents (e.g., “Mechanical Engineering Technician II” would be identified as such on all other required files).

4.1.5 VOLUME V, PAST PERFORMANCE

4.1.5.1 The information contained in this volume will be used to evaluate whether the Offeror’s present/past performance is recent and relevant to the DOR requirements and to determine how well the Offeror performed on the contracts. This volume shall be organized into the following sections:

4.1.5.1.1 Section 1 – Contract Descriptions. This section shall include the following information:

4.1.5.1.1.1 The Offeror shall submit with its proposal contract descriptions representing its recent and relevant performance under Government and/or commercial contracts. The past performance information may be from predecessor companies, key personnel who have relevant experience, or subcontractors that will perform major or critical aspects of the effort. “Relevant” means performance that demonstrates the Offeror has developed, designed, and manufactured a biological decontamination system for aircraft or produced a system that used Bio-Thermal Decontamination to decontaminate biological agents. “Recent” means any contract under which any development, design or manufacturing has taken place within the last five (5) years of the issuance of this DOR.

4.1.5.1.1.2 For large multi-function firms, all past performance…