Attach L-08 - Transition SOO (A0002).docx

By submitting a proposal for Task Order 1000, Transition, the Offeror agrees to furnish all services and items upon which the prices are offered at the price set opposite each item, delivered at the designated point(s), within the time specified in the schedule if this Task Order offer is accepted by the Government anytime from award of the contract resulting from H95001-15-R-0001 through 180 calendar days thereafter.

Period of Performance

Contract Type This is a fixed-price incentive (firm target) (FPIF) task order. The Offeror shall propose a target cost, target profit, and ceiling price. The target cost is inclusive of all cost elements, including labor, material, and other direct costs (ODCs). The ceiling price shall be no greater than 120% of target cost. The share ratio above target cost is 60 (Government)/40 (Contractor). The share ratio below target cost is 40 (Government)/60 (Contractor).

The Offeror’s proposed target profit percentage shall not exceed the profit percentages as proposed on Attachment L-16: Cost / Price Workbook 3, WS3-3: Fee Structure Table.

Payments for contract line item number (CLIN) 0001will be made on partial deliveries accepted by the Government on a monthly basis in accordance with FAR 52.232-1, Payments. Payments for CLINs 0002 and 0003 will be made in accordance with FAR 52.216-7, Allowable Cost and Payment. Payments and the total final price are subject to adjustments in accordance with FAR 52.216.16, Incentive Price Revision—Firm Target, and performance assessments conducted in accordance with the IRES Performance Evaluation and Incentive Plan (Attachment J-06).

CLIN Structure

* Cost Price Workbook 3, WS3-4: TO 1000 Prop

This page intentionally blank

H95001-15-R-0001-0002 Attachment L-08

Jun 20, 2016

IRES

Integrated Research & Development for Enterprise Solutions

Attachment L-08:

IRES Transition Statement of Objectives (SOO)

FOR OFFICIAL USE ONLY

Jun 1, 2016 Table of Contents

Jun 20, 2016 Page i 1000: Transition Task Order

Execute a streamlined, transparent and seamless transition from the current Joint National Integration Center (JNIC) Research and Development Contract (JRDC) to the Integrated Research and Development for Enterprise Solutions (IRES) contract while ensuring uninterrupted Concurrent, Test, Training, and Operations (CTTO).

1.2 Purpose

This SOO provides the objectives for the seamless transition of program assets, responsibilities, and services.

2.0 Background

The JRDC has 20 to 25 task orders that will transition to IRES (as shown in Exhibit 1). Some task orders may merge, or transform, for execution under IRES. Exhibit 2 provides the schedule for proposing and negotiating the IRES task orders. The start date [effective date] of all task orders (other than the Transition TO) will be midnight, TBD, 2017.

Exhibit 1. Legacy JRDC Task Orders that will Transition to IRES during the Transition Window.

Please note that this list of task orders may evolve, merge, or evaporate; the list provided here is current as of publishing of the document.

Exhibit 2. Transition Schedule

3.0 Scope

This SOO encompasses all transition activities (contract award and through the end of the transition window) necessary to transfer all capabilities, responsibilities, and services to the new contract. The incumbent contractor is responsible for mission accomplishment during the transition window with the IRES contractor being responsible to assume 100% of mission accomplishment the day immediately following the transition window.

The IRES contractor will not assume property accountability responsibility until conduct of the contractor’s inventory of existing government property. The inventory will not be conducted under the transition task order; the inventory will be conducted under the Property Management and Accountability task order. Upon accomplishment of the inventory, government property will be transferred to the contractor as government furnished property (GFP). The contractor will assume property management and accountability of approximately 100,000 items under the Property Management and Accountability task order.

4.0 Service Summary Items

In accordance with the IRES Performance Evaluation and Incentive Plan, Service Summary Items (SSIs) 1 through 4 are common [required] on all task orders and will be assessed at the contract level (i.e., all task orders will receive the same rating – one fail all fail model).

SSI 5 (through n) [Technical Performance] captures the specific task order Service Summary Items deemed essential to successful execution of the task order (note: The Technical Performance SSIs are to be developed / defined using the performance measures proposed by the contractor). Exhibit 3 defines the SSIs applicable to this task order.

5.0 Statement of Objectives and Outcomes

The objective of this task order is to efficiently transition work scope currently performed on the JRDC to the Integrated Research and Development for Enterprise Solutions (IRES) contract. The transition must be accomplished without interrupting the Concurrent, Test, Training, and Operations (CTTO) of the MDIOC.

Outcomes are task order requirements that must be captured in the Contractor Performance Work Statement (CPWS). Thresholds which identify a specific performance level must also be incorporated into the CPWS. Desired attributes are both quantifiable and non-quantifiable performance goals/objectives that the Government would like to achieve, and are provided as assistance in developing proposal/CPWS performance thresholds and service summary items. Constraints are limitations on the contractor’s technical or management approach/solution. The contractor's approach/solution must comply with the constraints.

All activities conducted on this task order must adhere to the special requirements identified in the contract-level SOO (Contract Attachment J-1). In the event of a conflict between Section 5.0 of the SOO and the CPWS, Section 5.0 of the SOO takes precedence.

Jun 20, 2016 Page 3 Exhibit 3. SSIs and Weights Applicable to This Task Order

UNACCEPABLE

Performance Threshold

ACCEPTABLE

Performance Threshold

OBJECTIVE

5 QPI

COR: Percent of small business utilization proposed on all task orders negotiated at time of assessment.

25 QPI

COR: Customer Survey: twice annually prior to performance evaluations (mid and final)

25 QPI

Data manager: 100% Inspection: CDRL / Proposal delivery / milestone accomplishment record.

45 QPI

Successfully integrate and coordinate all activity necessary to efficiently execute this task order.

Milestone: Contract Kick-off meeting

5.1.2.2 An Integrated Program Management Report (IPMR) that contains data for measuring cost and schedule performance for this task order. The required IPMR required formats are:

· Format 1 defines cost and schedule performance data by product oriented Work Breakdown Structure (WBS); Format 1 will provide data at WBS Level 4.

· Format 2 defines cost and schedule performance data by the contractor's organizational structure (e.g., Functional or Integrated Product Team (IPT)).

· Format 5 is a narrative report used to provide the required analysis of data contained in Formats 1 and 2.

CDRL C001: TO 1000 - Integrated Program Management Report (IPMR) - Reduced EVM

5.1.2.3 A post-award conference is conducted to discuss the contractor’s standard Cost and Software Data Reporting (CSDR) process that satisfies the guidelines of DoD 5000.04M1 and the requirements in the Government-approved CSDR provided at Attachment J2.

Milestone: Cost and Software Data Reporting (CSDR) Discussions

5.1.2.4 Transition progress reviews with designated government representatives are conducted.

Milestone: Progress Meetings

5.1.3 Desired Attributes

a. Contract Kick-off meeting conducted within 2 days of task order start.

b. IPMR delivered 15 calendar days after close of the first full accounting period.

c. Post-award conference conducted within 10 days of task order start.

d. Weekly transition progress reviews.

5.1.4 Constraints

None.

The transition window will be used to prepare and negotiate 15 – 25 task orders. The offeror must have sufficient bandwidth and expertise to support the integrated team process described in Attachment L-09 – IRES TO Award/Modification Process. Ultimately, the offeror’s transition team is responsible for ensuring the incoming IRES contractor team / workforce is postured to assume full execution responsibility by the end of the transition window.

Milestone: Phase One Task Orders Finalized, 85 DAC Milestone: Phase Two Task Orders Finalized, 130 DAC Milestone: Phase Three Task Orders Finalized, 165 DAC

a. Transparent and seamless transition of work scope from previous task orders to new task orders.

b. Integrated Team Process (ITP) members are knowledgeable of task order subject matter and are empowered to make real-time decisions.

c. Risks / mitigation strategies unique to the offeror’s team are codified.

d. Open, two-way communication that enable informed decisions.

5.2.4 Constraints

a. The Government’s schedule for task order transition cannot be altered / changed by the Offeror.

b. Task order development and negotiations will be accomplished in Colorado Springs, CO.

5.2.5 Workload Data

a. 15 – 25 Task Orders will be migrated from the JRDC to IRES during the transition window.

b. 900 – 1,400 personnel will require security clearances / badges at the end of the transition period / start of the negotiated task orders.

Lessons learned during the transition period are documented for future MDA acquisitions.

5.3.2 Outcomes

Transition task order lessons learned are documented in a concise, informative briefing.

CDRL C002: Transition Task Order Lessons Learned

5.3.3 Desired Attributes

a. Lessons learned identify what went well and the issues that were encountered during the transition window.

b. Lessons learned capture processes and recommended process improvements for future MDA acquisitions.

c. Lessons learned identify process improvements for the IRES TO Award/ Modification Process.

5.3.3 Constraints

None.

6.0 Deliverables

The point of delivery for all CDRL products, except as noted in Exhibit C, is the MDA E-CaRT system. The Contractor shall deliver all such products by saving and profiling them in E-CaRT, with the appropriate notification of delivery letter transmitted electronically to the Government’s Data Management Office. Reference Exhibit C for specific CDRL delivery instructions.

6.2 CDRL Tailoring

Reference Task Order 1000 Exhibit C (Enclosure 1).

Note: DAC = Task Order Period of Performance Start Date

7.0 Government Furnished Equipment (GFE) / Government Furnished Information (GFI) In addition to the GFE / GFI identified in the IRES Contract SOO, paragraph 6.0, the following is applicable to this task order:

· RFP Attachment J-05 - GFP List

· MDA approved SW List 20151207 (Bidders’ Library)

8.0 Special Requirements

In addition to the Special Requirements identified in IRES Contract SOO, paragraph 7.0, the following are applicable to this task order:

· None

9.0 Applicable Directives / Regulations

In addition to the directives and regulations identified in RFP Attachment J-07, the following are applicable to this task order:

· None

10.0 Performance Work Statement (PWS)

The final, negotiated Contractor-Developed PWS will be incorporated into this document.

Note: The CPWS will also serve as the initial or baseline Quality Assurance Surveillance Plan (QASP). The QASP will not be incorporated into this document; a change to the QASP after task order award does not constitute a change to the task order.

11.0 Contractor-proposed Service Summary Item Table

The contractor shall propose service summary items; the weight must total 45%. The final, negotiated SSIs accepted by the Government will be appended to the table in Section 4.0, Service Summary Items.

UNACCEPABLE

Performance Threshold

ACCEPTABLE

Performance Threshold

OBJECTIVE

SSI 5

SSI n

TO 1000 Exhibit C

Jun 20, 2016 Page 9 image1.png image2.png image3.emf

TO 1000 Exhibit C 10May2016.zip