Task Order 001 Operations and Maintenance Draft.docx

TASK ORDER 001 - ILMS OPERATIONS & MAINTENANCE

Table of Contents

1.0 TASK ORDER NUMBER AND TITLE

· Task Order Number: TO-001

· Title: ILMS Operations & Maintenance

2.0 CONTRACT ADMINISTRATION

2.1 CONTRACTING OFFICER

Christina Black (blackce@state.gov)

2.2 CONTRACTING OFFICERS REPRESENTATIVE (COR)

To be determined.

2.3 GOVERNMENT TECHNICAL MONITOR (GTM)

To be determined.

3.0 PERIOD OF CONTRACT PERFORMANCE

This task order shall include a base period of one (1) year and four (4) 1-year option periods. The first three months (90 days) of the base year have been designated as the transition period. The transition period is anticipated to begin [to be inserted]. The anticipated standard performance start would then begin 90 days later.

The performance period is as follows*:

*To be updated upon award.

The Government is not obligated to exercise the option(s), and the dates as presented above are subject to change. Task order period of performance will be finalized after award.

4.0 Pricing

The following is provided as a sample of the contemplated base year CLIN structure. This structure would be expanded to cover the four (4) option years, with CLINs identical for each performance year.

*A Firm Fixed Price with Award Fee hybrid-type contract shall apply to this task order. Award Fee provisions are under development and will be included in the final RFP. The task order Quality Assurance Surveillance Plan (QASP) shall include a Schedule of Decrements, defined herein elsewhere, which shall be applied to the task order price in the event of failure to achieve satisfactory performance. An Award Fee Plan to be developed and included in the final RFP shall provide for Fee Awards in addition to the task order price in the event that certain performance requirements are exceeded, as defined in the Award Fee Plan.

The final RFP will identify which CLIN the award fee will apply against.

5.0 LOCATION OF CONTRACT PERFORMANCE

This task order requires a mix of on-site support at DOS’s State Annex (SA-15) building (1800 N. Kent Street, Arlington, VA 22209) and off-site at the contractor-site unless otherwise recommended by the contractor and agreed to by the Government. Occasional local travel for meetings in the National Capital Region is required. The government has 85 seats available to the contractor in SA-15. The contractor can determine which resources will work at SA-15 and at the contractor’s site depending on the nature of their work and required interactions with ILMS program government resources. However, at a minimum the program manager and other key personnel will be required to work on-site at SA-15.

5.1 STANDARD WORKWEEK

Non 24x7 personnel must be available business days during the core hours of 9:00 AM to 3:00 PM eastern standard time. Telework is permissible on a case-by-case basis and must be approved in writing by the COR.

6.0 BACKGROUND

This task order is intended to provide ILMS with a base level of operations and maintenance support.

7.0 CLEARANCE, LICENSES, PERMITS

7.1 FACILITY CLEARANCE

A facility clearance at the level of Top Secret is required for this task order.

7.2 Licenses, Permits, and other Official Documentation

Not applicable.

8.0 Statement of Objectives

The Offeror shall note that upon award Section 8.0, Statement of Objectives, shall be replaced with the accepted offeror provided Performance Work Statement.

This SOO addresses DOS’s objectives for operating and maintaining the ILMS Integrated Suite.

Below identified are the performance objectives and areas of service.

8.1 Tasks

Within the below identified tasks, the contractor shall meet identified performance metrics. In the event that performance metrics are not met, the task order price will be decremented in accordance with the Schedule of Decrements contained in the QASP. To be eligible for an award fee, the contractor must exceed specified performance metrics as provided in the Award Fee Plan.

8.1.1 Task 1: ILMS Program Management and Support

The contractor shall support the ILMS program and its overall goals and responsibilities at the Department of State by providing program management and related support services. T0-001 Attachment 1 – Incentives Matrix identifies the objectives and performance incentives and disincentives for this task. This solicitation will identify the required performance incentives and disincentives and will ask the offeror to propose others. [Required performance incentives and disincentives to be completed in final RFP].

The task’s requirements are detailed in Table 2 below. The contractor shall accomplish these tasks in alignment with ILMS’s operational structure.

Table 2 – Task 1 Requirements

As needed, the contractor will be asked to support or participate in certain programmatic activities such as, but not limited meetings and workshops, development of information assets such as fact sheets, researching particular questions, or supplying up-to-date information on supply chain performance.

The contractor will provide the appropriate information or expertise to support ILMS requests for information, financial management (including budgeting), strategic planning, risk management, schedule and cost management, resource management, as well as what is needed for the independent verification and validation reviews conducted by a separate contractor.

The contractor shall support the program’s ability to accurately and consistently respond to individual taskers. These taskers may originate externally or internally and include but are not limited to:

· Quarterly software capitalization reporting on ILMS development efforts.

· Periodic requests for ILMS investments by the DOS ITEC.

· Periodic budget reporting and Budget Resource Request formulation.

· Periodic requests for ILMS program overview, financial, and performance information.

The contractor shall support and facilitate strategic planning as needed for the ILMS program. The contractor shall collaborate with DoS and the ILMS Independent Validation and Verification (IV&V) contractor to address current and future program needs.

The contractor shall work with the government program management team to develop and execute a communications and engagement strategy that proactively engages ILMS stakeholders, effectively communicates program benefits and accomplishments, and helps advocate for key initiatives.

The contractor may be asked to develop and disseminate program reports (including reports to Congress and DOS leadership), manage working groups, plan and execute program-wide events, and create and maintain artifacts such as fact sheets, video clips, and other media types.

The contractor shall assist the ILMS program with developing and advancing its vision and strategic plan to revolutionize supply chain operations and strategy by bringing industry standard best practices and driving innovations. As part of analyzing potential innovations, the contractor shall develop an analysis of alternatives which includes a cost benefit analysis and justification of the benefits.

The contractor shall also assist in updating the ILMS Value Realization Plan which captures the program’s on-going benefits.

The contractor shall be responsible for the following performance management activities or products as well as any additionally relevant activities or products that will help the contractor and ILMS manage performance:

· Service Level Agreement self-assessments

· Dashboards to monitor performance

· Measures

· Contracting Officer Representative contract meetings and reviews cycle

· Data readiness

The contractor shall propose a work breakdown structure for each task in an awarded task order. In constructing the proposed structure for each authorized work element, the contractor shall consider OMB standards for IT projects which have increased considerably in since 2019. In particular, OMB and the Department of State require greater specificity and detail in an IT project’s WBS. The Government requires a clear cross-walk between the completion of key milestones and the functional delivery of a capability. As the Government moves towards an agile framework, milestones of six months or shorter are common. In preparing the proposed WBS and underlying project plan, the contractor shall meet with the A/LM/PMP/SYS prior to establishing a baseline.

The contractor shall provide monthly program status reports and present program status at regular ILMS program and financial management review meetings.

The contractor shall conduct program management and earned value management reporting using an earned value management system in compliance with federal ANSI 748-A and DOS standards. The contractor shall conduct value engineering for the contract in compliance with OMB Circular A-321 and DOS Value Engineering policy.

The contractor shall support Information Technology Executive Council reporting in support of OMB information technology Investment reporting.

The contractor shall support an annual Integrated Baseline Reviews (IBRs), to include a presentation with supporting materials, an overview of active tasks, the established baselines, cost performance planned, deliverables, Service Level Agreements (SLAs), key activities, and key assumptions. The baseline review establishes the baseline for the ILMS program for the duration of the task. The baseline is added to when new work is authorized. The baseline is subtracted from when a previously authorized task is terminated.

The contractor shall devise a satisfactory invoice format so the Government can adequately review and approve invoices for their projects only, without the inclusion of other resources who may be supporting work on a similar contract CLIN.

The contractor shall develop, maintain, and distribute the ILMS Program Master Schedule contained in the Contractor Program Management Plan, and the work breakdown schedule approved in the Integrated Baseline Review.

As an attachment to the Contractor Program Management Plan, the contractor shall develop, execute, and maintain a management and Staffing Plan that outlines how the contractor will manage resources to ensure sufficient coordination across all of the contractor teams, including for task orders sponsored by other DOS organizations (e.g., Diplomatic Security or Overseas Building Operations), but managed by the ILMS program. For each team under the contractor, the plan shall include the organizational structure, staffing and skillset requirements, personnel resources, planned hours. In addition, the plan shall include cross team coordination processes, resource retainment and replacement processes, and on-going training requirements and plans.

As part of the Contractor Program Management Plan, the contractor shall provide a program organizational chart. The organizational chart should identify roles and responsibilities, identify management and key personnel, and show how the proposed organization aligns to the government’s ILMS programmatic functional areas outlined in the introduction. In addition, the organizational chart should identify key lines of communication and critical points of coordination across the various teams.

At a minimum, the contractor shall maintain the key personnel with the required qualifications listed in Solicitation Attachment J.

The transition-in plan shall address the following components and any other activities deemed necessary or important by the offeror:

· Badging/Security Clearance

· Orientation to the contract

· Knowledge transfer

· Kick-off approach/cadence The contractor’s transition-in plan and execution shall ensure timely transfer of responsibilities with the least amount of disruption to current activities.

The contractor shall develop a transition-out plan within 30 days of the CO’s request. The contractor shall execute the plan in coordination with the new contractor’s transition-in plan and ILMS, modifying the plan as necessary.

Section F.8 of the IDIQ solicitation describes the transition-out plan requirements for the IDIQ. The Task Order 1 transition-out plan shall address these requirement with particular emphasis on the following components and any other activities deemed necessary or important by the offeror.

· Knowledge transfer plan and schedule

· Knowledge transfer materials

· Knowledge transfer execution

8.1.2 Task 2: Tier 3 Support

The contractor shall provide Tier 3 production support that helps address and resolve more complex customer support issues that cannot be resolved by Tier 1 and Tier 2 customer support personnel for ILMS, Secure ILMS, SAMS, and myServices. As part of Tier 3 support, the contractor shall provide functional support to end users, implement software break-fixes, and implement small enhancements. This includes providing personnel with the knowledge, skills, and abilities to accomplish functional and break-fix technical support as well as minor enhancements across ILMS’s technology stack. T0-001 Attachment 1 – Incentives Matrix identifies the objectives and performance incentives and disincentives for this task. This solicitation will identify the required performance incentives and disincentives and will ask the offeror to propose others. [Required performance incentives and disincentives to be completed in final RFP].

The task’s requirements are detailed in Table 4 below.

Table 4 – Task 2 Requirements

The contractor shall perform an impact assessment that will identify the level of effort, cost, and risks associated with each requested break-fix or enhancement for Government review and approval.

Using Agile development methodologies (including establishing scrum teams and using sprints to release software changes), the contractor shall develop and implement software changes based of government prioritization of the backlog. As part of the Agile process, the contractor shall coordinate with government product owners, IV&V contractor, and user community stakeholders throughout the design and development process to ensure optimal design and common understanding or changes.

The contract shall work with IV&V to coordinate IV&V testing and identify testing scenarios and data for all software changes.

The contractor shall conduct user acceptance testing for break-fixes changing business processes.

The contractor shall conduct performance testing to ensure changes did not negatively impact system performance.

The contractor shall use automated testing tools to conduct regression testing to ensure break-fix is not impacting other ILMS components.

The contractor shall work with configuration management resources to manage release related configuration items and transition of configuration items from development, testing, and production environments.

For each break-fix or enhancement, the contractor shall review production readiness and obtain a Government Go/No-Go decision before deployment begins.

5.3: Training The contractor shall communicate upcoming training to the user community and provide training on new functionality and features as needed. This communication is focused to keeping users informed of planned process improvements. Whereas strategic communications focuses on developing and employing an engagement strategy that proactively engages ILMS stakeholders, effectively communicates program benefits and accomplishments, and helps advocate for key initiatives.

The contactor shall communicate and train Tier 1 and Tier 2 resources on the use of the new functionality and features.

8.1.3 Task 3: Technology Management

The contractor shall provide end-to-end technology management services to manage and maintain the ILMS program’s technology stack for ILMS, Secure ILMS, SAMS, and myServices, and ensure system reliability, availability, and flexibility. The contractor’s technology management approach shall align with ILMS’s overall product management (Capability Area 2) and data management and analytics (Capability Area 3) requirements to ensure effective coordination of interdependent activities.

T0-001 Attachment 1 (Incentives Matrix) identifies the objectives and performance incentives and disincentives for this task. This solicitation will identify the required performance incentives and disincentives and will ask the offeror to propose others. [Required performance incentives to be completed in final RFP].

The task’s requirements are detailed in Table 6 below.

Table 6 – Task 3 Requirements

The contractor shall manage the ILMS, secure ILMS, myServices, and SAMS systems’ technical architectures and infrastructures—maintaining appropriate supporting documentation and coordinating with product and data management teams as needed.

The contractor shall maintain ILMS, secure ILMS, myServices, and SAMS software and hardware components, providing fixes and repairs as required, and applying patches and upgrades to ensure compliance with DOS security policies to all production and non-production environments.

The contractor shall provide database administration for ILMS, secure ILMS, myServices, and SAMS production and non-production environments.

The contractor shall provide system administration and monitoring of the ILMS, secure ILMS, myServices, and SAMS systems to ensure 24x7 system availability and assurance for all production and non-production environments. Activities include:

· Providing system administration and monitoring for all application components.

· Conducting interface/integration administration and monitoring.

The contractor shall provide configuration management for ILMS, secure ILMS, myServices, and SAMS production and non-production environments, including:

· Managing configuration items using configuration tools for all software environments, including development, test, staging, and training.

· Managing separate integration environments as required.

· Conducting code and data migrations using automated configuration tools. Refer to Solicitation Attachment 4 for the number of migrations performed on an annual basis

· Conducting data refreshes as required.

· Installing, maintaining, and updating server configuration settings as required. Maintaining server configuration documentation.

· Supporting Information Technology Change Control Board requirements and submissions when required for the addition of new software and hardware components.

The contractor shall provide performance monitoring and tuning for all ILMS, secure ILMS, myServices, and SAMS application and integration components, including:

· Conducting end-to-end performance monitoring and testing—tuning components based on results of monitoring and testing.

· Conducting network and application performance monitoring using Oracle Enterprise Manager tool.

· Collecting and reporting performance statistics.

The contractor shall develop and execute a comprehensive plan for ILMS Integrated Suite Architecture, System Management, and Configuration Changes Management. This plan shall address how the offeror will:

· Manage and maintain the ILMS Integrated Suite architecture

· Maintain high-availability services (99.9% uptime)

· Manage necessary configuration changes

Security Authorization and Acceptance:

The contractor shall support security authorization and acceptance activities. Activities include:

· Verifying system releases fall within DOS policy.

· Supporting Certification and Authorization (C&A) for new application components and recertifications to obtain Authority to Operate on the DOS network for new components/systems and systems previously certified.

· Conducting annual Contingency Testing and documenting results.

· Conducting annual Security Controls testing (Information Resource Management (IRM)/Information Assurance (IA) mandated security testing) and documenting the results.

· Conducting penetration testing.

· Providing supporting documentation (including but not limited to System Security Plan (SSP), Contingency Plan, and test results).

· Maintaining acceptable iPost security scoring for all systems as defined by the service level agreement standard for this task.

· Creating and Managing Plan of Action and Milestones (POA&Ms) for all systems.

· Conducting IRM/IA mandated security testing.

Security Audit Support:

The contractor shall provide security audit support. Activities include:

· Supporting internal and external audits as required.

· Establishing an internal procedure to provide Standard Audit Requests (SARs) to system ISSO.

Security Management:

The contractor shall provide general security management activities required to maintain an acceptable security posture of all systems. Activities include:

· Performing Privacy Impact Assessments (PIA), documenting findings and recommendations.

· Proactively supporting and information release management activities by performing a Security Impact Assessment and Risk Analysis for all releases, and advising release teams on security best practices to ensure these are taken into account during the analysis and design phases of new efforts.

· Creating, updating, and maintaining system security documentation.

· Conducting independent reviews of system components to identify weaknesses to remediate in order to maximize system security posture.

· Maintaining Splunk security monitoring infrastructure and dashboards and implementing enhancements to or introducing new Splunk dashboards.

Contingency Planning:

The contractor disaster recovery operations and support for all ILMS, secure ILMS, myServices, and SAMS systems. Activities include:

· Maintaining the disaster recovery site.

· Maintaining Continuity of Operations Plan.

· Developing, updating, and executing step-by-step procedures for system of application component failover.

· Ensuring contingency planning for disaster recovery is current and tested.

· Developing and updating a system recovery execution plan.

· Supporting and testing data retrieval from back up tape or servers.

· Implement software patches and COTS upgrades as required to ensure secure operations, continued vendor support, and ability to leverage new functional and technical features

· Continuously identify new and emerging technologies potentially relevant to supply chain

· Assess the ability of new and emerging technologies to meet requirements and help DOS achieve its long term goals

· Manage and maintain existing technology licenses and agreements to ensure no gaps

· Help acquire and implement new technology, including obtaining necessary security approvals such as an ATO, if needed.

8.1.4 Task 4: Customer Support Desk

The contractor shall be responsible for operating a 24x7 customer support desk for ILMS, Secure ILMS, SAMS, and myServices that is capable of supporting the global user base, including on holidays.

The contractor shall provide 24x7 Tier 0, 1 and 2 customer and user technical support using multiple support channels (e.g., chatbots, voice, in app, etc.) for the ILMS, Secure ILMS, myServices, and SAMS systems. The contractor shall be responsible for managing all aspects of global customer support desk operations, including issue management to provide customers and users comprehensive support services. Tier 0 through Tier 2 support shall be tightly integrated to ensure seamless and timely resolution of customer’s issues, providing transparency of issue status and visibility for global customers. In addition, the contractor shall be responsible for the ensuring all customer support desk personnel have the required technical and interpersonal training to provide appropriate levels of service. As the primary face to customers, the contractor shall answer questions, fulfill requests or facilitate request fulfillment, deliver program communications, and ensure timely, accurate resolution.

Excellent customer service is a priority on this program, and as such, an innovative and creative approach is expected. Consequently, the contractor’s approach shall incorporate industry best practices and include innovative processes and technology.

T0-001 Attachment 1 – Incentives Matrix identifies the objectives and performance incentives and disincentives for this task. This solicitation will identify the required performance incentives and disincentives and will ask the offeror to propose others. [Required performance incentives to be completed in final RFP].

The task’s requirements are detailed in Table 9 below.

Table 9 – Task 4 Requirements

The contractor shall maintain and update Tier 0 support vehicles such as chatbot and embedded intelligent application assistance tools.

The contractor shall monitor the chatbot operations to ensure issues are properly logged and escalated to Tier 1 if they cannot be resolved by Tier 0.

Through Tier 1 support, the contractor shall perform full incident and problem lifecycle management following industry best practices. This includes but is not limited to logging all inquiries that are received by the CSD and addressing less complex issues such as ticket referrals, basic error handling and basic application “how-to’s”. Specific activities include:

· Serving as the single point of contact for all ILMS issues (including requests for adding new users, vendors and locations)

· Identifying and tracking incidents

· Classifying and prioritizing incidents

· Diagnosing and resolving incidents

· Closing incidents

· Monitoring incidents and communicating incident status (including notifying the user of both cause of the issue and the action taken)

· Processing user account management requests such as password resets and resolving account lockouts.

The contractor shall use automated incident response tools to capture specific information about the calls and e-mails received.

The contractor shall be responsible for managing application configuration updates due to DOS personnel role changes, business process modifications, and software updates.

Tier 2 shall support the more complex issues such as resolving more complex incidents and problems logged by Tier 1. These include but are not limited to performing root cause analyses, identifying system changes, and escalating to Tier 3. Specific activities include:

· Identifying issues

· Conducting root cause analysis.

· Resolving issues in a timely manner.

· Escalating issues to Tier 3 as appropriate in a timely and documented manner.

· Maintaining access request forms.

· Conducting incident trend analysis of all Tier 0 through Tier 2 issues.

· Subsume support for new modules 3 months after dedicated functional support ends.

· Processing request for the creation of new user accounts and user permission changes across all ILMS, Secure ILMS, myServices, and SAMS modules,

· Processing user request for adding and updating configuration data in ILMS for vendors and office locations.

· Providing updates to vendors and established production catalogs.

· Process Ariba workflow configuration changes.

· Fully addressing customer requests that cannot be resolved by Tier 1, such as adding new users to the system Tier 2 shall be tightly integrated with both Tier 1 and Tier 3.

9.0 Travel

This task order does not contain travel requirements. Travel charges for attendance at National Capital Region (NCR) meetings will not be reimbursed.

10.0 Personnel

10.1 Personnel Clearances

See the below breakdown, by area of performance under the task order:

· National Crime Information Center (NCIC) Review: Roles that do not require any system or facilities access.

· Moderate Risk Public Trust (MRPT): Roles that do not require OpenNet / System or facilities access, such as AWS development and unit testing environments.

· Secret: Roles needing access to OpenNet and/or DOS facilities to fulfill their job responsibilities. Also required for roles traveling overseas to Posts.

· Top Secret/Sensitive Compartmented Information (TS/SCI): Roles requiring ClassNet Administrator access or for accessing OpenNet Amazon & Azure cloud environments.

10.2 Position Description and Qualifications

See IDIQ Solicitation Attachment 6 for personnel descriptions and qualifications.

11.0 Key Personnel

The key personnel specified in this contract are considered to be essential to work performance. The Contractor shall assign the following key personnel to this task order:

POSITION/FUNCTION

NAME

Program Manager

Procure to Pay Subject Matter Expert (SME)

Transportation and Warehouse SME

Courier and Mail SME

Fleet SME

Property and Asset Management SME

Technical Infrastructure and Architecture Lead

Cyber Security Specialist

See Solicitation Attachment J for key personnel position descriptions.

During the first 180 days of performance (including transition period), the Contractor shall make no substitutions of key personnel unless the substitution is required due to illness, death, or termination of employment. The Contractor shall notify the Contracting Officer within 5-calendar days after the occurrence of any of these events and provide the IDIQ Section H.3 required information.

After the first 180 days of performance, the Contractor may substitute a key person if the Contractor determines that it is necessary. The Contractor shall provide notice at least 45 days prior to diverting any of the specified individuals to other programs or contracts (or as soon as possible, if an individual must be replaced, for example, as a result of leaving the employ of the Contractor), the Contractor shall notify the Contracting Officer and shall submit comprehensive justification for the diversion or replacement request (including proposed substitutions for key personnel) to permit evaluation by the Government of the impact on performance under this contract. The proposed substitute shall possess qualifications comparable to the original key person and meet the minimum standards set forth in the contract.

The Contractor shall not divert or otherwise replace any key personnel without the written consent of the Contracting Officer. The Government will modify the contract to reflect any changes in key personnel.

See IDIQ Section H.3 for additional information on key personnel.

12.0 Reporting

Reporting requirements shall be as defined in the PWS and shall additionally include requirements specified in the basic IDIQ as applicable at the task order level. Reports shall be as further described in and delivered in accordance with Section 13.0 below.

13.0 Deliverables

All dates are calendar days unless otherwise stated.

Section 7.0 deliverables are identified below.

Task 1 / 1.1

Task 1 / 1.1

Task 1 / 1.2

Updated annually.

GTM & COR

Task 1 / 1.4

Updates as Required.

GTM & COR with a copy to the CO

Task 1 / 1.5 Task Order Program Management Plan

Updated annually.

GTM & COR with a copy to the CO

Task 1 / 1.5

Task 1 / 1.5

If the final FMR varies from the “ILMS program actuals” work products (which supports iMatrix reporting), the vendor will highlight those differences in a separate appendix.

Monthly, No later than the 25th of the month for the prior month.

In cases when an FMR meeting is scheduled less than 3 business days after the 25th, vendor will provide a draft copy to the ILMS IV&V 3 business days prior to the FMR meeting.

GTM & COR

Task 1 / 1.5

Task 1 / 1.5

Task 1 / 1.5

Task 1 / 1.5

Task 1 / 1.5

Task 1 / 1.5

Updated annually or as needed based on evolving requirements GTM & COR with a copy to the CO

Task 1/ 1.5

Initial 30 days after contract award Updated annually or as needed based on evolving requirements

GTM & COR with a copy to the CO

Task 1 / 1.5

Updated annually or as needed based on evolving requirements

GTM & COR

Task 1 / 1.6

Days after Award

GTM & COR

Task 1 / 1.6

Task 2 /

2.1 - 2.5

Updates as Required.

GTM & COR

Task 2 /

2.1 - 2.5

Updated annually or as required to incorporate new technologies.

GTM & COR

Task 3/ 4.1

Task 3/ 4.2

Task 3/ 4.2

Task 3/ 4.2

Task 3/ 4.2

Task 3/ 4.2

Task 3/ 4.2

Task 3/ 4.2

Task 3/ 4.2

Task 3/ 4.1

Task 3/ 4.3

Updates as Required.

GTM & COR

Task 4/ 5.1

Task 4/ 5.1

Task 4/ 5.1

Task 4/ 5.1

Task 4/ 5.1

Task 4/ 5.1

All other task order deliverables are identified below.

Submitted to: CO and COR By first Wednesday of the month

Submitted to: COR Before performance, as applicable

Submitted to: CO Before performance, as applicable

Submitted to: CO, COR, and OSDBU Every 6 months, from award

Submitted to: CO and COR Semi-annual

14.0 Quality Assurance Surveillance Plan

QASP shall be developed by the contractor and subject to final approval by the government. Plan contents and specifications shall include a Schedule of Decrements corresponding to each SOO requirement and each parameter of Table 8 – Task 1 Minimum Performance Levels, which Schedule shall apply in the event of any failure to meet required performance standards.

15.0 Attachments

· Attachment 1- Incentives Matrix

· Attachment 2 – Task Order Management Plan (to be incorporated upon award)

· Attachment 3 – Quality Assurance Surveillance Plan (to be incorporated upon award)

· Attachment 4 – Award Fee Plan (to be provided with final RFP)