Attach L-10 - IRES SEPI SOO (A0006).docx

By submitting a proposal for Task Order 2000, SE&PI, 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 cost-plus-incentive-fee (CPIF) / Award Fee (AF) task order. The Offeror shall propose a target cost, target fee, and the award fee pool. The target cost is inclusive of all cost elements, including labor, material, and other direct costs (ODCs). The minimum fee shall be 3% of target cost. The maximum fee shall be 15% 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 fee percentage shall not exceed the fee percentages as proposed on Attachment L-16: Cost / Price Workbook 3, WS3-3: Fee Structure Table.

Payments for all contract line item numbers (CLINs) will be made in accordance with FAR 52.216-7, Allowable Cost and Payment. Payments and the fee payable under the task order are subject to adjustments in accordance with FAR 52.216.10, Incentive Fee, and performance assessments conducted in accordance with the IRES Performance Evaluation and Incentive Plan (Attachment J-06).

In addition to adjustments authorized in accordance with FAR 52.216-10(d), adjustment of the target cost due to a variance in the actual cost incurred when compared to the Government’s plug number (GPN) for other direct costs (ODC) may be considered if actual ODC costs exceed +/- 15%. The adjustment will only be made by the amount the actual cost incurred exceeds the +/- 15% threshold; no adjustments to fee will be made.

The CLIN structure for Task Order 2000 – SE&PI is provided in Table 1: Task Order 2000 – CLIN Structure.

Task Order Award Fee Plan / Evaluation Elements and Weights In addition to the incentive fee, the contractor may earn Award Fee on this task order (CLINs 0080, 0081 and 0082) for above satisfactory (good or higher) performance. In accordance with the IRES Performance Evaluation and Incentive Plan, task orders receiving an evaluation of satisfactory or less will result in zero award fee; satisfactory performance is acknowledged within the incentive target fee.

The IRES Performance Evaluation and Incentive Plan defines the roles, responsibilities and process for evaluating and determining the Award Fee. The evaluation elements and weights for Task Order 2000 – SE&PI are defined in Table 2: Task Order 2000 – SE&PI Award Fee Evaluation Elements and Weights.

Table 1: Task Order 2000 – CLIN Structure

Share Ratio Above Target (Gov/Cont): 60/40 Share Ratio Below Target (Gov/Cont): 40/60

Share Ratio Above Target (Gov/Cont): 60/40 Share Ratio Below Target (Gov/Cont): 40/60

Share Ratio Above Target (Gov/Cont): 60/40 Share Ratio Below Target (Gov/Cont): 40/60

Share Ratio Above Target (Gov/Cont): 60/40 Share Ratio Below Target (Gov/Cont): 40/60

H95001-15-R-0001-0006 Attachment L-10

Sep 21, 2016 Table 2: Task Order 2000 – SE&PI Award Fee Evaluation Elements and Weights

Mitigation plans include alternative or parallel courses of action and nominates preferred solutions. Plans contain sufficient data (e.g., estimated financial impact) to allow the government to make an informed decision.

Very Good plus:

Contractor employs early corrective action(s) and planning to preclude potential mission impacts.

Innovative methods, techniques, technologies and/or process improvements result in increased effectiveness and efficiencies throughout the contract.

Very Good plus:

Effectiveness and efficiencies gained are quantified and documented.

Forecasts are fully traceable within and between reports.

Good plus:

Contractor delivers cost and schedule data that provides clear visibility and traceability from current status to forecasted costs and schedule.

Very Good plus:

Contractor recognizes where cost growth may occur and provides detailed explanations for actual or potential problems; projections and justification are detailed in the variance analysis report.

IRES

Integrated Research & Development for Enterprise Solutions

Attachment L10:

IRES Systems Engineering and Program Integration (SE&PI) Statement of Objectives (SOO)

Sep 21, 2016 Table of Contents

Sep 21, 2016 Page i IRES Systems Engineering and Program Integration (SE&PI)

Effective systems engineering and program integration that results in a consistent requirements execution methodology and increased mission assurance at reduced program costs. Innovative solutions are desired, but not at the expense of mission success.

1.2 Purpose

Task orders to be issued under the IRES program are dependent, either wholly or partially, on one another. It will be the responsibility of this task order to provide efficient and effective systems engineering processes to deliver integrated solutions across all stakeholders utilizing this contract to execute requirements.

2.0 Background

NOTE: This information is provided as an aid to offerors; it is not intended to direct or influence the proposed solutions or contractor-developed performance work statement submitted in response to this SOO.

Task orders issued on the JRDC that are considered predecessor task orders to this SOO include:

· 8001, Program Execution & Systems Engineering

· 8003, Facility Support, Task B.4

· 6001, Program Execution & Engineering

· 6003, Facility Support, Task B.4

· 5002, Management and Integration

· 5001, Engineering

· 5003, Facility Support, Task H.4

· 4002, Management and Integration

· 4001, Engineering

· 3002, Management and Integration

· 3001, Engineering

· 2002, Management and Integration

3.0 Scope

The task order issued as a result of this SOO will protect Ballistic Missile Defense System (BMDS) baseline integrity while supporting the successful technical execution of all Missile Defense Agency (MDA) events and mission activities performed under the IRES contract.

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.

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

5.0 Statement of Objectives and Outcomes

The MDIOC assets support the BMDS operational, training and test missions; these assets must be protected to ensure their availability and ability to support MDA mission activities. MDA’s BMDS Integrated Master Test Plan (IMTP) establishes the framework for the BMDS test program. The BMDS IMTP is an overarching document that describes the BMDS test environment, supporting test organizations, developmental and operational test programs, and management of MDA test resources, and is the definitive source for detailed test planning and execution guidance. MDA partners with the Services and Combatant Commands to plan and execute the BMDS training, exercise and war gaming missions. Operational BMDS support activities are directed by the war fighting community and strongly influenced by uncertain real-world events.

The systems engineering function performed under this task order ensures that the work provisioned and executed under the numerous IRES task orders is fully coordinated and synchronized, and that the work is executed in accordance with program governance. The program integration function performed under this task order ensures that the technical solutions for task orders in the acquisition pipeline adhere to appropriate governance documents, and are optimized and integrated for maximum effectiveness and performance. Together these functions monitor and govern all work executed under the contract.

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.

Sep 21, 2016 Page 1 Exhibit 1. SSIs and Weights Applicable to This Task Order

UNACCEPABLE

Performance Threshold

ACCEPTABLE

Performance Threshold

OBJECTIVE

25 QPI

EVM Program Analyst: review of the task order schedule(s) and the IMS.

5 QPI

COR: Review of Task Order 2000 – CDRL C012

20 QPI

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

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

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

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

· Format 7 defines the time-phased historical and forecast cost submission.

CDRL C001: TO 2000: Integrated Program Management Report

5.1.2.2 Delivery of the contractor acquired property (CAP) for the SE&PI task order.

CDRL C002: TO 2000: Interim Government Property Inventory Report

5.1.2.3 Initial task order baseline review and monthly task order status reports consisting of significant accomplishments, issues, concerns, and risks.

CDRL C003: TO 2000: Task Order Status Report MILESTONE: Initial Baseline Review

a. Situational awareness of task order activities.

b. Frequent and open communication.

5.1.4 Constraints

None.

An overarching, program-wide perspective is necessary to effectively perform systems engineering in the dynamic operating environment supported by the IRES contract. Events, activities, projects and products conducted or delivered under the numerous IRES task orders must be coordinated to maintain configuration control, reduce execution risk and result in mission assurance. The systems engineering function executes the work processes that cross multiple stakeholders and are considered necessary to provide mission assurance. The systems engineering function also develops, manages, and maintains Department of Defense Architecture Framework (DoDAF) data used in a Federal and Department of Defense (FEA, DODEA) compliant architectural repository for the IRES contract.

CDRL C004: Event Packages (Assume 35 – 45 annually)

5.2.2.5 A robust Systems Engineering Management Plan (SEMP) that enables full integration of the activities performed under the contract.

CDRL C005: Systems Engineering Management Plan (SEMP)

CDRL C006: Accident / Incident Report(s) (Assume 12-16 annually) CDRL C007: Chemical Inventory and Hazardous Material Usage Report

5.2.3 Desired Attributes

a. Performance measures that demonstrate improved product and services.

b. Situational awareness and health and status for monitored systems and assets.

c. A real-time technical baseline ensuring positive configuration control enabling informed decision making.

d. No mission or event impacts due to lack of thorough systems engineering, configuration management or event coordination of activities.

e. Environmental compliance and safety awareness are integral to all activities.

f. Zero Environmental Notices of Violation (NOVs).

5.2.4 Constraints

None.

Program integration provides for the planning, coordination, technical direction, and surveillance of the activities necessary to assure disciplined work performance and timely resource application to accomplish all task orders issued under the IRES.

Program integration also assures the technical excellence, cost effectiveness, non-duplication of services, and timeliness of all ordered (procured) work and deliverable products/services. The driving requirement is to balance risks and opportunities with clear intent to adjust processes and resources to achieve mission success.

Program-level reports consist of overarching contract requirements as well as a consolidation of reports delivered under various task orders.

5.3.2.1.1 A program management plan that describes the contractor’s organization, assignment of functions, duties, and responsibilities, management procedures and policies, and reporting requirements for the conduct of contractually-imposed tasks, projects, or programs.

CDRL C008: IRES Program Management Plan

5.3.2.1.2 A Contractor Work Breakdown Structure (CBWS) that satisfies the guidelines of DoD 5000.04-M-1 and the requirements in the Government-approved CSDR plan for the contract, Exhibit C - DD Form 2794.

CDRL C009: Contract Work Breakdown Structure (CBWS)

5.3.2.1.3 A Contract Funds Status Report (CFSR) providing funding data about task orders for the purpose of: (a) updating and forecasting contract funds requirements, (b) planning and decision making on funding changes to contracts, (c) developing funds requirements and budget estimates in support of approved programs, (d) determining funds in excess of contract needs and available for de-obligation, and (e) obtaining rough estimates of termination costs.

CDRL C010: Contract Funds Status Report (CFSR)

5.3.2.1.4 A labor hour report in accordance with latest Enterprise-wide Contractor Manpower Reporting Application (eCMRA) directive. This report is designed to collect information on funding source, contracting vehicle, organization supported, mission and function performed, and labor hours and costs for contracted efforts providing services to the MDA. The contractor’s transmittal letter shall contain the following information for all subcontractors required to submit an annual report: Subcontractor, Subcontract Number, Subcontractor Size Classification, and Subcontractor NAICS.

CDRL C011: Enterprise-wide Contractor Manpower Reporting Application (eCMRA)

5.3.2.1.5 A report that provides actual achievements relative to the utilization goals in the Small Business Participation and Commitment Plan and the results of the Contractor’s efforts to (a) expand the pool of qualified small businesses, (b) engage small businesses to serve as second sources, and (c) involve small businesses in each of the IRES HLOs.

CDRL C012: SB Subcontractor Report, IRES Contract

5.3.2.1.6 An IRES Integrated Program Management Report (IPMR) that contains data for measuring cost and schedule performance at the IRES Program Level. This report is a compilation of all IMPRs submitted under individual task orders into a single delivery. This report does not create or develop new data.

CDRL C013: IRES Integrated Program Management Report

5.3.2.1.7 A consolidated IRES program status report that captures (archives) program management reports developed under individual task orders. This report is a compilation of all program management reports submitted under individual task orders into a single delivery. This report does not create or develop new data.

CDRL C014: IRES Program Status Report

5.3.2.1.8 Delivery of the Data Accession List (DAL), providing a medium for identifying contractor internal data which has been generated under the various task orders.

CDRL C015: IRES Data Accession List (DAL)

5.3.2.1.9 Cybersecurity Risk Management Plan that includes threat analysis, system exposure to threats, integration of Cybersecurity risk management with other systems engineering process areas, and Cybersecurity risk mitigation.

CDRL C016: Cybersecurity Risk Management Plan

5.3.2.1.10 Cybersecurity Controls Statement(s) of Compliance that detail policies, procedures and standards for protecting critical unclassified information (CUI) from unauthorized access from both internal and external sources. A statement of compliance is required for all team members that may access CUI.

CDRL C017: Cybersecurity Controls Statement(s) of Compliance

5.3.2.1.11 Cyber Incident or Compromise Report(s) reporting as much of the information defined in DFAR Clause 252.204-7012 (d)(1) as can be obtained within 72 hours of any reportable cybersecurity incident.

CDRL C018: Cyber Incident or Compromise Report(s)

5.3.2.1.12 Verification that the contractor workforce performing cybersecurity functions are in compliance with the guidelines found in DoD 8570.01-M (chapters 3, 4, 5, 10 and 11).

CDRL C019: Cybersecurity Workforce Management Report

5.3.2.2 Program-level plans and programs are documented and deployed.

Program-level plans and programs provide overarching contract governance, contributing to mission assurance.

5.3.2.2.1 A quality assurance program that contains processes to enable the workforce to efficiently and effectively perform the myriad tasks required to successfully execute the efforts issued the IRES contract.

CDRL C020: Quality Assurance Program Plan

5.3.2.2.2 A robust risk management program that identifies, tracks and mitigates (to the extent possible) mission execution and performance risk.

CDRL C021: IRES Risk Management Plan

5.3.2.2.3 A comprehensive configuration management plan / program that enables the identification and management of critical asset lists, facility/IT modifications, project designs and proposals, and test architectures.

CDRL C022: IRES Configuration Management Plan

5.3.2.2.4 An environmental program that addresses Environmental Compliance, Pollution Prevention, and Conservation and is in accordance with Federal, State, Schriever AFB, and MDA environmental laws and regulations. Specific programs include, but are not limited to:

· Hazardous/Universal Waste Management

· Hazardous Material (to include HAZMART pharmacy and Green Procurement)

· Qualified Recycling Program

· Energy/resource conservation

· Ozone-depleting chemicals (ODC’s)

· Emergency Planning and Community Right-to-Know (EPCRA)

· Hazardous Material Spill Response CDRL C023: Environmental Program Plan

5.3.2.2.5 A mishap prevention and program safety plan that addresses safety of IRES-managed facilities (MDIOC), equipment and workforce.

· Compliance with the requirements of the designated Air Force HAZMAT authorization and tracking system, which is currently the Enterprise Environmental, Safety, and Occupational Health – Management Information System (EESOH-MIS).

· Mishap Prevention and Safety Plan that addresses lock-out/tag-out, confined space entry, electrical safety, mishap investigation and reporting, safety risk assessment, safety education and training, Hazard Communication Program, and other areas that ensure full compliance with 29 CFR 1910.1200, Hazard Communication Program.

· Documented ergonomic procedures that ensure that the MDIOC workforce are reasonably accommodated to perform their individual work activities.

· MDIOC Facility Evacuation Plan.

· Documented regular safety and fire protection inspections at the MDIOC followed by corrective action plans.

CDRL C024: Mishap Prevention and Safety Plan CDRL C025: MDIOC Facility Evacuation Plan

5.3.2.3 Task order close-out documentation is provided

As a task order period of performance ends, task order close-out documentation will be delivered. This documentation includes, at a minimum: identification of primary companies contributing to the execution of the task order; a summary of significant accomplishments; status of work in progress; task order cost data; a list of CDRLs delivered; a list of data accession list items (DAL) produced; a task order level labor hour report, similar to the Enterprise-wide Contractor Manpower Reporting Application (eCMRA) directive; and a task order level Small Business Subcontractor Utilization Report. Assume approximately 200 task orders will be issued over the life of the contract.

CDRL C026: TO TBD: Task Order Close-Out Report CDRL C027: TO TBD: Final Contractor Acquired Property Report

5.3.2.4 Information management system

A program-level, on-line, searchable management information system that captures all products (i.e., CDRLS) developed / submitted (i.e., Data Ascension List (DALs)) on the contract.

CDRL C028: IRES Program Information Management System Documentation

5.3.3 Desired Attributes

a. Situational awareness of program activities.

b. Reliable forecasts that can be used for management decisions. Realistic performance baselines that facilitates early identification and mitigation of risk; baseline integrity is maintained and changes are fully documented.

c. The Contractor Work Breakdown Structure efficiently supports the tenants of MIL-STD-881c.

d. Small business reports capture both the quantitative performance measures (e.g., subcontracting dollars / percentages) as well as the qualitative performance measures (e.g., contributions to mission execution).

e. The program status reports capture accomplishments, issues, concerns at both the task order and program level. The report documents cost control initiatives implemented at the task and project level.

f. The prime contractor collects / consolidates team members Cybersecurity Controls Statement(s) of Compliance into a single document for delivery.

g. Program plans are applicable to all task orders issued under the contract.

· Processes that are streamlined, well-defined, transparent to the customers and incorporate performance measures.

· Processes that can be tailored, as necessary, by an innovative and creative workforce to respond to immediate and unique needs of customers.

· Non-value added process steps and outdated, bureaucratic processes are systematically eliminated.

· Program plans are reviewed and updated annually.

h. The management information system is accessible to the MDA workforce with no access restrictions.

5.3.4 Constraints

None.

5.3.5 Workload Data

a. Nine active stakeholders, but IRES is an Agency-level contract vehicle and therefore is available to all MDA two-letters.

b. 20 – 25 active task orders; formal EVMS may not be required on all task orders, however all task orders will be required to report cost data on IPMR formats 1 and 2.

c. Historically, 350-450 CDRLs and 1,000-1,500 DALs have been provided annually; development of CDRLs and DALs is accomplished under the various task orders.

Services delivered under this contract are vital to the Government and must be continued without interruption upon contract expiration. In the event a follow-on contract is awarded to other than the IRES incumbent, the contractor shall cooperate fully to the extent required to permit an effective, orderly, and successful transition from IRES to the follow-on contract(s). The contractor shall furnish sufficient orientation, training, and equipment/system familiarization required by any follow-on Contractor(s). This may include a collective daily discussion between the contractor, follow-on contractor(s), and the Government on the status of the phase-out/phase-in.

5.4.2 Outcome

An IRES contract phase-out plan that provides for an orderly and effective transition of products and services to the follow-on contractor(s) with no interruption or impact to mission.

CDRL C029: Program Phase-Out Plan

5.4.3 Desired Attributes

a. Products and services are transitioned from IRES to the follow-on contractor(s) with no interruption or impact to mission.

b. Task order continuity logs are maintained in a manner that minimizes learning curves.

c. The legacy of projects that transcend / extend over multiple task order performance periods is retained.

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 2000 Exhibit C (Enclosure 1).

Note: DAC = Days after 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:

· CFR, Title 29, Subtitle B, Chapter XVII Part 1910.1200, Hazard Communication Program

· 50th Space wing Instruction 32-2001, Emergency Services

10.0 Contractor-developed PWS (CPWS)

The final, negotiated CPWS will be appended to 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 2000 Exhibit C

Sep 21, 2016 Page 15 image1.png image2.emf

TO2000 Exhibit C 31May2016.zip