Attachment 3 - Transition.doc
DOC document 61 KB Posted
- Attached to
- Application Support Services Federal contract opportunity
- Solicitation number
- A10006
About this file
Attachment 3 - Transition PWS
View the file
Other files for this federal contract opportunity
Show all 30
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
A10006 Attachment 3
Task Order 0001 Performance Work Statement – FFP Provide Transition Support Services
INTRODUCTION
This Task Order is issued under the U.S. Department of the Treasury, Application Support Services Contract to perform the Transition Tasks described herein to successfully (1) complete the readiness activities necessary to assume the existing work performed under the current contract; (2) transition the work; and (3) assume control and management of the work described in this PWS within a ninety (90) day transition period.
DESCRIPTION OF SERVICES
There are two distinct sets of services required under this task order defined as follows:
1. ASSC Contract Transition Planning; and
2. ASSC Contract Transition Execution
The contractor shall perform the transition of the on-going application support services from the incumbent contractor to its own organization. The contractor shall provide all technical and management labor, supplies, tools, processes, techniques, and methodologies to successfully effect this transition within the 90-day performance period.
2.1 Development of the TRANSITION PLAN
Contractor shall amend, update and finalize the draft Transition Plan submitted with their proposal.
Contractor shall deliver a final, executable Transition Plan that will be incorporated by reference into the resulting contract. The plan shall:
· Demonstrate the contractor’s understanding of the requirements and describe their strategy to assume program control, administrative and operational control responsibility, ongoing maintenance, and the transition of all open in-process work from the prior contractor.
· Place specific emphasis upon program controls, risk mitigation, quality assurance and testing methodologies in the development and execution of the final plan.
2.1.1
DELIVERABLE: FINAL TRANSITION PLAN
Contractor’s transition plan shall demonstrate:
· A workable strategy to assume operational control and administration of existing applications, in-process work, and the existing Treasury business model.
· Contractor’s approach to effectively transition program management, task management, and individual or groups of applications.
· Contractor’s approach to coordination, collaboration, and communication with all parties involved (the incumbent; COTR; Government program and client contacts; ACIO-TM Infrastructure contractor representatives; and the ACIO-TM management team).
· Contractor’s intent and approach to sub-contracting.
· Contractor’s approach and methodology to mitigate transition risks.
2.1.2
FINAL TRANSITION PLAN SUBMITTAL AND REVIEW
No later than 5 calendar days after task order award, the contractor shall attend a Post-Award Conference with the Contracting Officer (CO), Contracting Officer’s Technical Representative (COTR), representatives of the ACIO-TM’s Office and the incumbent contractor to discuss time-lines, target-dates and appropriate topics leading to an orderly transition in order for the contractor to assume operational control and administration of existing applications and support functions.
No later than 10 calendar days after the award of this Task Order, the contractor shall amend/update the draft Transition Plan based upon the results of the Post-Award Conference. The Government will provide comments on the draft transition plan within 5 calendar days.
Within 10 calendar days after receipt of the Government’s comments, the Contractor shall deliver the final transition plan. The Government will provide approval within 5 calendar days after receipt.
2.2 Transition to and Assumption of Control of thE installed Base
The Contractor shall perform all services, tasks, and any other support activities required to transition from the current ASSC contract to the new ASSC contract. The existing services under this contract are vital to Treasury’s mission and must continue without interruption. The Contractor agrees to exercise best efforts and cooperation to affect an orderly and efficient transition phase after award.
In accordance with the approved Transition Plan, the contractor shall:
· Begin the transition;
· Assume ongoing operational support and services for the installed base;
· Complete the in-process work from the incumbent contractor per the Transition Plan;
· Undertake any other activities that ensure seamless continuity of operations and maintenance of the installed base; and
· Demonstrate in accordance with the approach presented in the Transition Plan its ability to assume full responsibility for the ASSC environment at the completion of the Transition period.
Furthermore, the contractor shall also transition and assume the license agreements established within the incumbent ASSC Contract. The contractor shall not be responsible for the acquisition of these licenses but provide support to maintain inventory, support OCIO for renewal, replacement, or termination of license agreements listed in the table below.
| COTS Software Administered |
| Version |
| Product |
Interface
Client Application Systems
| Kofax Ascent used for OFAC and OFS Document Capture |
| Version 7.5 in production, 8.0 under development |
| Government COTR |
| Hummingbird Searchserver for TACT |
| Searchserver 5.3 |
| Government COTR |
| SAS for CFO Vision |
| SAS Version 4.3 |
| Government COTR |
| Penrose svc for SAS authentication |
| Penrose 1.1.2 |
| Government COTR |
ASSC Developer COTS
| Microsoft Project Server |
| 2003 and 2007 |
| Government ITIMS COTR |
| Microsoft SharePoint development tools |
| Versions 2003 and 2007 |
| Government ITIMS COTR |
| Microsoft Visual Studio |
| Versions 2003, 2005, 2008 |
| Government ITIMS COTR |
| Serena Version Manager (Client/ Server interface) |
| PVCS Professional 9.4 |
| Government ITIMS COTR |
| Serena Team Track |
| PVCS Professional 9.4 |
| Government COTR |
| Serena SourceBridge |
| PVCS Professional 9.4 |
| Government COTR |
| Microsoft SQL Server DBA functions |
| 2000, 2005 with BI, 2008 with BI |
| Government COTR |
| Oracle DBA tools |
| 9i, 10g, 11g |
| Government COTR |
| Java |
| SE 1.4.3 |
| Government COTR |
| Eclipse |
| 3.3.1 with My Eclipse plug-in 6.0.1 |
| Government COTR |
Other
| VMware Workstation |
| Workstation 6.5.2 |
| Government ITIMS COTR |
| VMware Server |
| Server 1.08 and 2.01 |
| Government ITIMS COTR |
| VMware Converter |
| Converter 3.0.3 |
| Government ITIMS COTR |
3.
DELIVERABLES
The Contractor shall provide the following deliverables during the performance of this task order.
| Deliverable |
| Initial Due Date |
| Estimated Length |
| Format / Standard |
| Number of Copies |
| Update |
Frequency
| Transition and Assumption Control Plan |
| 10 calendar days following award of funded Task Order for Task 0001 |
| 10 – 15 Pages with supporting details in appendices |
| Contractor format/ MS Office (Word, Excel, and Project) |
| 4 hardcopies |
1 electronic None
4 Period of performance The period of performance will be the award date plus ninety (90) days.
Task Order 0001
File details come from the government source that posted it. Updated .