Attachment A - Control M SOW.doc
DOC document 93 KB Posted
- Attached to
- Control - M Support Services Federal contract opportunity
- Solicitation number
- CC-08-HQ-Q-0037
View the file
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
Control - M Support Services Performance Work Statement
1. Purpose
The objective of this statement of work is to obtain implementation support services to upgrade Control – M servers and agents for the Office of the Comptroller of the Currency (OCC) Information Technology Services (ITS) organization..
2. Background
The OCC charters, regulates, and supervises all national banks. It also supervises the federal branches and agencies of foreign banks. Headquartered in Washington, D.C., the OCC has four district offices plus an office in London to supervise the international activities of national banks. More information about the OCC can be found at its website www.occ.treas.gov.
The OCC uses information technology (IT) systems to support a broad range of its functions. These systems are produced through collaboration by the business units whose functions they support, the program management offices (PMOs) that manage the business unit’s IT portfolios, and ITS, the centralized IT organization that is responsible for the technology supporting the IT portfolios.
Currently the portfolio of Production Control Activities Workflows (PCAW) is varied in complexity and user intervention. The portfolios contain a mixture of custom coded applications and commercial-off-the-shelf (COTS) applications. These applications are supported primarily by a Microsoft-based architecture, although there are some Lotus Notes data transfer applications and a few applications that are supported by a mainframe architecture. Presently, Control-M 6.1.03 is the scheduling software employed at OCC for this function. Other software and system components currently required to perform the production control function include: PeopleSoft Process Scheduler, DOS Batch files, febooti, PUTTY Suite, MKS Toolkit (Perl), SQR, XML, WinSCP35 (Secure FTP application) Monarch Data Pump.
The Control-M 6.1.03 needs to be upgraded to Control-M 6.3. The documentation received with the Control – M product provides some installation and upgrade support but more specialized support is needed for our Control-M servers and agents.
3. Scope of Work
The OCC requires a contractor to provide on site support,, installation, implementation and knowledge transfer on a labor hour basis. The products supported in this request are: Control –M Enterprise, Control-M CTM, and PeopleSoft CM. Production control functions that need to be addressed during the support are: PeopleSoft Process Scheduler, DOS Batch Files, FEBOOTI, PUTTY Suite, MKS Toolkit (Perl), SQR, and WinSCP35.
The contractor resources are to perform the following activities
3.1 Configure PS Servers with CM
The Contractor shall assess the existing PS Server agents and determine the most efficient process to configure PS Servers upgrades. This includes transfer of knowledge to OCC staff. The contractor shall also identify server configuration parameters and replacement of antiquated code and routines. The Contractor shall support the OCC staff in the configuration and installation of PS CM server upgrade or provide the services.
3.2 Control M Utility Server Agent Server Migration
The Contractor shall assess the existing Control M Utility Server agent and determine most efficient process to migrate existing Control M upgrades and third party components. This includes transfer of knowledge to the OCC staff. The contractor shall also identify needed server configurations parameters and replacement of antiquated code and routines. The Contractor shall support the OCC staff assigned in the configuration, installation and migration of PS CM server upgrade.
3.3 Backup of servers
The Contractor shall provide guidelines on backup processes that are necessary for a success installation and migration with the support of OCC staff existing backup procedures.
3.4 Migration of components to new server (00)
The Contractor shall assess the existing Control-M Enterprise components that was on the 01 server and make sure they are on the 00 server. The Contractor shall provide support in the migration of the existing components that are on the 01 server on to the 00 Enterprise servers. The Contractor shall provide transfer of knowledge regarding configuration, installation, migration and components to OCC staff assigned to project. The contractor shall also identify needed server configurations parameters and replacement of antiquated code and routines. The Contractor shall support the OCC staff assigned in the migration of Control M Enterprise server upgrade.
3.5 Migration of PCA workflows to the new server
The Contractor shall assess the existing PCA workflows and assure that the PCA workflows work properly with the upgrade. If the PCA workflows do not work properly, the contractor shall provide and alternative to the PCA workflow that will perform the same functions. The Contractor shall provide transfer of knowledge regarding PCA workflows to OCC staff assigned to the project. The contractor shall also identify needed modify PCA workflows and the replacement of antiquated code and routines. The Contractor shall support the OCC staff assigned in the migration of Control M Enterprise server upgrade.
3.6 Testing of server connections.
The Contractor shall assist in testing the connections of the Control-M servers and the agents.
3.7 Assist with Control-M upgrades on servers and agents
The Contractor shall assist NOC with the use of Virtual development server. This will include but not exclude necessary processes for: 1) backing up the server; 2) Test Server connections with NOC (monitoring tool); 3) Test Server connections; 4) Test Peoplesoft Server Connections/routines; 5) Test PCA Workflows.
3.8 Assist with Server move to Data Center
The Contractor shall assist in the move of the Control-M Enterprise server to the data center.
3.9 Reporting Status
The Contractor shall report every morning status of activities and next steps to take place; this is to include resolution of risks/issues and any outstanding activities.
4. Constraints
OCC shall schedule resources in segments of no less than forty hours unless agreed to by both the vendor and OCC.
OCC shall provide physical access to facilities consistent with the agreed upon schedule for all resources.
OCC shall continue to maintain their back – up and recovery processes.
5. Deliverables The deliverables under this task order are as follows:
| RefNo. |
| Deliverable |
| Description |
| Due Dates will be based on agreed upon work schedule |
| 3.1 |
| Operational PS CM Server with upgrades |
| PS CM Server shall be working properly with the new upgrade in place and routines executing properly. |
| 3.1 |
| Operational PS CM Server with upgrades. |
| Configuration of PS CM Server documented for repeated use. |
| 3.2 |
| Operations Utility server on the CM Enterprise Server 00. |
| Control-M Enterprise Server working properly with the migration of the Utility server on Enterprise Server 00. |
| 3.2. |
| Operations Utility server on the CM Enterprise Server 00.) |
| Verification that the utility server components are working properly on the 00 server. |
| 3.3 |
| Completion of back up of all servers |
| Before configuration, installation or migrations server are backed up |
| 3.4 |
| Operational components on server 00 |
| Verify all components are working properly. |
| 3.5 |
| Operational PCA workflows scheduled |
| Verify PCA workflows are scheduled and operating properly. |
| 3.6 |
| Operational server connections |
| Verify all server connections are operating properly. |
| 3.7 |
| Completion of Upgrades to servers |
| Verify all upgrades to server is operating properly. |
| 3.7 |
| Completion of Upgrades to servers |
| Verify and test all components. |
| 3.8 |
| Operational Server at Data Center |
| Verify and support Server move to the data center. |
| 3.9 |
| Daily status reporting |
| Report every morning status of activities, risks/issues, and alternatives (mitigations). |
The contractor shall submit deliverables to the designated Contracting Officer and Contracting Officer Technical Representative (COTR) concurrently.
Deliverables are to be prepared using the Microsoft Office suite of products (i.e., Word, PowerPoint and Excel) and/or Visio and/or the production control tools provided by OCC,.
6. Performance Measurements
To be proposed back by vendor.
7. Place of Performance
The contractor shall perform all contract activities at OCC Headquarters, 250 E Street, SW, Washington, DC 20219, OCC Headquarters, 400 Virginia Avenue, SW, Washington, DC 20219, or OCC Headquarters (Data Center), 835 Brightseat Rd, Landover MD 20785.
8. Period of Performance
The period of performance shall be no more than 2 months.
9. Contract Type
The contract will be issued as labor hours.
9.
CONTRACT MANAGEMENT
9.1 Project Manager
The project manager must be identified as key personnel. The Contractor shall identify a Contractor employee to serve as the project manager, the OCC’s primary day-to-day point of contact for technical, schedule or other questions related to the performance of this contract.
10. Hours of Operation
The Contractor hours are 8 am – 5 pm, Monday through Friday.
11. Accessibility
Contractor shall comply with Section 508 of the Rehabilitation Act (29 U.S.C. 794d), as amended by the FY 2001 Appropriation for Military Construction (Public Law 106-246 - July 13, 2000) for Software Applications and Operating Systems. If exceptions apply, these shall be immediately identified to the COTR in writing. Exceptions must provide rationale.
12. Information Security
Government-provided information may take the form of policies, standards, guidelines, technical documentation, or databases. The Contractor shall protect from loss or unauthorized disclosure any materials or information made available to it during the performance of this task order. When not in use, written materials that the COTR or other OCC employee identifies as sensitive or confidential shall be secured in locked receptacles provided by the OCC. No sensitive or confidential materials shall be removed from OCC premises.
Contractor staff will be required to attend government-provided information security awareness briefings or training at the discretion of the COTR
13. Government Furnished Information, Equipment and Services
The OCC shall provide the Contractor with the production control governance documentation, workflow operations manuals, and access to the software, data and hardware needed to perform the production control function.
The OCC will provide sufficient office space, access to the local network for e-mail and public folders purposes, limited office supplies, furniture, access to telephone lines, printers, fax machines, copiers, and other similar facilities for personnel while working on-site. Long distance telephone access shall be limited to OCC business use only.
File details come from the government source that posted it. Updated .