Attachment K - Roles and Responsibilities.xlsx

XLSX spreadsheet 28 KB Posted Dec 23, 2022

Attached to: Mainframe Cloud Transition Services and Support Federal contract opportunity
Solicitation number: RFP-CIO-30100000-23-001
Issued by: Department of the Treasury Bureau of the Fiscal Service

About this file

Written by GovTribe AI · Dec 30, 2023

This document outlines roles and responsibilities for mainframe cloud transition services and support. Key responsibilities include incident management, system operations, batch job scheduling, batch monitoring and restart, application library management, operating system support, software maintenance and currency management, performance and capacity management, data set management, storage environment management, storage replication management, backup and restore, media management, tape media operations, and network roles. It also covers roles for change management, problem management, hardware management, migration management planning, disaster recovery planning, and disaster recovery testing and execution. Responsibilities are assigned as primarily, jointly, or in a supporting role between the contractor and the government. The related federal contract opportunity is a solicitation seeking a single-award IDIQ contract to establish mainframe cloud transition services and support for the Bureau of the Fiscal Service on an as-needed basis, with a minimum requirement that the cloud mainframe be IBM SmartCloud or equal. Key dates include questions due by January 3rd, 2023 and proposals due by January 9th, 2023.

View the file

Other files for this federal contract opportunity

Other files attached to Mainframe Cloud Transition Services and Support, newest first.
File	Type	Posted
RFP-CIO-30100000-23-001 (Amd. 2).pdf	PDF	Jan 6, 2023
Attachment I (1-3) - Order 1 Pricing (Amd. 1).xlsx	XLSX spreadsheet	Jan 4, 2023
Attachment H - Order 1 PWS (Amd. 1).pdf	PDF	Jan 4, 2023
Attachment E - Pricing Workbook (Amd. 1).xlsx	XLSX spreadsheet	Jan 4, 2023
Questions and Responses (Amd. 1).pdf	PDF	Jan 4, 2023
RFP-CIO-30100000-23-001 (Amd. 1).pdf	PDF	Jan 4, 2023
Attachment E - Pricing Workbook.xlsx	XLSX spreadsheet	Dec 23, 2022
Attachment F - Accessibility Requirements Statement.pdf	PDF	Dec 23, 2022
RFP-CIO-30100000-23-001.pdf	PDF	Dec 23, 2022
Attachment A - Security Requirements.pdf	PDF	Dec 23, 2022
Attachment B - Security Rules of Behavior Agreement.pdf	PDF	Dec 23, 2022
Attachment C - Non-Disclosure Agreement.pdf	PDF	Dec 23, 2022
Attachment G - Small Business Participation Plan.pdf	PDF	Dec 23, 2022
Attachment I (1-3) - Order 1 Pricing.xlsx	XLSX spreadsheet	Dec 23, 2022
Attachment J - Subcontracting Plan.pdf	PDF	Dec 23, 2022
Attachment D - Security Controls Rules of Behavior Agreement.pdf	PDF	Dec 23, 2022
Attachment H - Order 1 PWS.pdf	PDF	Dec 23, 2022

Show all 17

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

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

Roles and Responsibilities

	Attachment K - Roles and Responsibilities	Contractor Responsibility (Use drop-down options to select most appropriate response)
Incident Management			Perform
1	Engage agreed upon recovery management processes for Priority 1 and Priority 2 incidents.		Assist
2	Manage the incident through service restoration.		No Role
3	Validate severity classification of the problem.
4	Determine the scope of the problem with support input.
5	Escalate as required.
6	Drive problem determination activities.
7	Perform restoration plans.
8	Ensure that Service Management has been contacted to confirm that the service has been restored to the Government's satisfaction (for problems reported by Government).
System Operations
1	Manage production operating system resource availability through console operator monitoring (with dedicated console) and automation monitoring.
2	Perform automated operating system IPL.
3	Perform automated operating system shutdown.
4	Monitor operating system and devices using monitoring/alert tools and console operators.
5	Execute recovery procedures for production operating systems and devices.
6	Execute console commands.
7	Reply to console messages that require operator action.
8	Perform manual startup and shutdown of the production operating system only in trouble situation if automation fails.
9	Ensure mainframe procedures are documented and followed.
10	Take the appropriate, documented recovery actions for the various operational events.
11	Restart failing components after an outage according to documented procedures.
12	Execute production subsystem (e.g CICS, DB2, MQ) started tasks restarts via automation procedures, with Government's backup manual procedures if needed.
13	Monitor and respond to hardware alerts.
14	Receive requests via phone call from Government Help Desk.
15	Open/Update status/Close auto opened tickets or Government Help Desk request in standard problem management tool.
16	Contact Hardware support if required.
17	Contact the appropriate Software support groups for Systems software.
18	Contact Government Help Desk or Technical Point of Contact per the Responsiveness SLA.
19	Document problem and notification timeline, initial job/system log and error information in problem ticket.
20	Detect and take appropriate action on events that require operator action.
Batch Job Scheduling
1	Scheduling of resources.
2	Perform any pre-batch activities.
3	Scheduling batch services (online services supported by Operations).
4	Define, maintain and document a work schedule for running production system batch jobs, and possible started tasks.
5	Maintain procedures and documentation, implement recommendations for improvement.
6	Install and maintain the scheduling program product(s).
7	Manage the scheduling of batch jobs in the job scheduling package.
8	Communicate to the Contractor the Batch Job Scheduling problems and changes that have an impact on overall service, availability, and SLA's.
9	Manage the root cause analysis for scheduling problems.
10	Collect and manage the batch operations measurements on starts/ends, abends, etc.
11	Resolve scheduling conflicts in the production schedule cycles and involve applications when needed.
12	Maintain procedures for users/programmers to make request to the batch job scheduling team.
13	Develop and maintain standards for job acceptance and implementation.
14	Schedule on-request batch jobs that require immediate execution.
15	Understand the impact of window activities to the production schedules.
16	Perform scheduling changes according to the instructions provided and question any inconsistencies.
17	Create/maintain calendars.
18	Suggestion and implementation of improvements.
19	Participate in Disaster Recovery processes/test as required.
20	Provide scheduling support for job scheduling tools that are part of business applications.
Batch Monitoring and Restart
1	Resolve batch scheduling conflicts (non-application) (root cause analysis and change management).
2	Monitor scheduled batch jobs.
3	Monitor user batch jobs outside of the scheduling software.
4	Contact Government Help Desk or Technical Point of Contact with concerns or problems regarding batch jobs.
5	Monitor scheduler related incidents, and develop and recommend changes to the scheduler.
6	Performing required batch setup activities (ad hoc requests).
7	Schedule on-request batch jobs that require immediate execution.
8	Invoke resolution and restart procedures in case of failures in the batch jobs.
9	Notify Console Operations for operating system, hardware, and platform product related issues.
Application Library Management
1	Define and document application code promotion standards and acceptance criteria for moving application code from test libraries into production libraries. Note: application code includes JCL and programs elements.
2	Install and maintain the Application Library Mangement program product(s).
3	Move code from development and / or test environments to production.
O/S Support Activity
1	Install, customize, upgrade and maintain the operating system and agreed upon IBM / ISV (Third Party) program products / operational tools / utilities.
2	Apply corrective services to the operating system and agreed upon IBM / ISV (Third Party) program products / operational tools / utilities.
3	Support the operating system, and agreed upon IBM / ISV (Third Party) program products / operational tools / utilities.
4	Provide support for approved Exits and Usermods.
5	Identify opportunities to remove Government Exits and Usermods.
6	Complete testing for all installs, upgrades and corrective services for the operating system and agreed upon IBM / ISV (Third Party)program products / operational tools / utilities.
7	Provide support for Government testing and pilot support, as required.
8	Investigate problems for the operating system and agreed upon IBM / ISV (Third Party) program products / operational tools / utilities.
9	Provide escalation to vendor support for the operating system and agreed to IBM / ISV (Third Party) program products / operational tools / utilities.
10	Maintain software inventory for the operating system and agreed upon IBM / ISV (Third Party) program products / operational tools / utilities.
11	Complete Root Cause Analysis, as required.
12	Order and install updated product keys for agreed upon program products.
13	Document application and user test schedules. Insure the Government user community performs required testing.
14	Maintain operating system host network IP addressing and routing configurations.
15	Maintain HMC network IP addressing and routing configurations.
Software Maintenance and Currency Activity
1	Complete a quarterly mainframe software review for the base operating system and agreed upon IBM / ISV (Third Party) program products to identify announced support end dates and available new product versions for installed products.
2	Develop a quarterly plan to determine appropriate actions for products with announced support end dates and available new versions.
3	Based on availability and Government’s request, upgrade the Supported Programs at a mutually agreed upon time, but not to exceed every 18 months, except as may be otherwise required more frequently by a third party vendor.
4	Provide information on new product features and possible benefits, prior to operating system and program product upgrades.
5	Provide recommendations, as appropriate, on the exploitation of new features in the operating system and IBM / ISV program product versions.
6	Maintain an inventory of product key expiration dates for agreed upon program products.
7	Review new releases of IBM supported program products for changes in functionality.
8	Document application and user test schedules. Insure the Government user community performs required testing.
9	For ZOS Cloud Environment(s), document the common service maintenance schedule; review and communicate any required changes.
Performance and Capacity Management Activity
1	Document and review Work Load Manager (WLM) service classes, reporting classes and performance goals.
2	Maintain WLM service definitions.
3	Document and review SMF/RMF long-term data collection and configurations.
4	Perform SMF/RMF long-term data collection.
5	Document and review Mainframe Monitoring Tool data collection and configurations.
6	Maintain Mainframe Monitoring Tool configurations.
7	Document and review statistical reporting and data collection.
8	Define and document daily (automated only)/weekly/monthly performance reports.
9	Develop and maintain process to generate daily (automated only)/weekly /monthly performance reports and analysis.
10	Monitor weekly/monthly performance reports for issues and/or concerns.
11	Define and document long-term future trending reports.
12	Develop and generate long-term future trending reports on a quarterly basis.
13	Review and analyze long-term trending reports on a quarterly basis.
14	Create recommendations for future resource requirements.
15	Document recommendations to correct/improve workload performance.
16	Document recommendations to correct/improve system resource utilization.
17	Document and periodically review performance monitor thresholds.
18	Provide problem determination and monitoring for performance impacting events.
Data Set Management
1	Manage data set placement, allocation, and performance monitoring.
2	Monitor and modify DASD resources.
3	Manage and configure storage tools.
4	Manage catalog environment.
5	Make recommendations to improve levels of data protection and efficiencies.
6	Define and Document catalog management requirements.
Storage Environment Management
1	Configure the disk storage arrays, including setting up Raid groups, spares.
2	Configure tape libraries, including setting up different tape drive types, defining library partitions.
3	Define logical volumes in the storage arrays.
4	For zOS Cloud Environment(s), assign VOLSER ranges for the Government.
5	For zOS Cloud Environment(s), assign tape cartridges or virtual tape domains for the Government.
Storage Replication Management
1	Configure and support advance copy services products.
2	Configure and Support Channel extended storage devices.
Backup / Restore
1	Execute backup and recovery procedures for the operating system and program product volumes.
2	Define, document, and execute backup and recovery procedures for non-system volumes.
3	Define, document, and execute backup and recovery procedures for user data files that are outside of the system wide standards.
4	Create, maintain and publish documentation about storage management philosophy, including class selection, data retention, migration, backup and recovery procedures.
Media Management
1	Define requirements for virtual tape retention.
2	Maintain virtual tape retention rules.
3	Measure virtual tape utilization and produce trend reports.
4	Identify application changes that have a potential impact on storage requirements. Jointly determine impacts and actions.
5	Provide sufficient virtual tapes to service required processing needs.
6	Provide a sufficient virtual scratch tape pool to service required processing needs.
Tape Media Operations
1	Maintain a virtual tape library system at Contractor Data Center
Network GBS
1	Ethernet/Network Cabling
2	LAN Switches
3	Purchase and fund equipment
4	Purchase and fund equipment maintenance
5	Deploy/install equipment
6	Monitor and manage through Steady State
7	SOCKS/Proxy Server
Network SMBDI Connectivity at Government site
1	Ethernet/Network Cabling
2	LAN Switches
3	Purchase and fund equipment
4	Purchase and fund equipment maintenance
5	Deploy/configure/test equipment
6	Monitor and manage through Steady State
7	SOCKS/Proxy Server
Network OSA Card - SMBDI at Contractor Data Center
1	Purchase and fund equipment
2	Purchase and fund equipment maintenance
3	Deploy/configure/test equipment
4	Monitor and manage through Steady State
5	Assignment of Public Assigned IP Addresses (InterNIC Registered)
Network LAN Switches at Government site
1	Purchase and fund equipment
2	Purchase and fund equipment maintenance
3	Deploy/configure/test equipment
4	Monitor and manage through Steady State
5	Ethernet Cabling
Network WAN Routers
1	Purchase and fund equipment
2	Purchase and fund equipment maintenance
3	Deploy/configure/test equipment
4	Monitor and manage through Steady State
WAN Circuit(s) between Contractor and Government sites
1	Purchase and fund
2	Deploy/install equipment
3	Demarc Extension(s) inside data center
4	Monitor and manage through Steady State
Network (SMBDI) WAN Circuit(s) between Contractor and Government sites
1	Purchase and fund
2	Deploy/install equipment
3	Demarc Extension(s) inside data center
4	Monitor and manage through Steady State
Network Channel Extenders (a.k.a Edge Routers)
1	FICON Cabling
2	Ethernet Cabling
3	Deploy/install equipment
4	Monitor and manage through Steady State
Network at Contractor Data Center
1	Ethernet/Network Cabling
2	LAN Switches
3	Purchase and fund equipment
4	Purchase and fund equipment maintenance
5	Deploy/install equipment
6	Monitor and manage through Steady State
7	Assignment of Public Assigned IP Addresses (InterNIC Registered)
Network Channel Extenders (a.k.a. Edge Routers) at Contractor Data Center
1	FICON Cabling
2	Ethernet Cabling
3	Deploy/install equipment
4	Monitor and manage through Steady State
Migration Management Planning
1	Development of an overall migration project plan
2	Develop a cut over “Run Book” that details that timing and sequence of activities to occur during Workload Cut Over
3	Develop a plan to quiesce the Government primary source mainframe system to enable a final change synchronization to complete data replication
4	Define the data (DASD volumes) in scope for the migration
5	Develop and implement an approach for network and mainframe workload testing to tolerate the use of duplicate IP addresses on the current Government primary source mainframe system and the Contractor primary data center mainframe system.
6	Plan, develop, and execute test plans for all application testing, including functionality, performance, and latency testing
7	Plan, develop, and execute test plans for all software products for which Contractor is responsible for operation
8	Plan, develop, and execute test plans for all software products for which the Government is responsible for operation
Migration Planning Infrastructure Readiness
1	Buildout Government target site LPARS, DASD and VTS capacity in the Contractor primary data center
2	Install and configure Government current software stack
3	Establish end to end migration circuit connectivity from Government primary data center to Contractor primary data center
4	As required to support the migration strategy, install and configure temporary migration hardware at the Government primary data center
5	As required to support the migration strategy, install and configure the DASD data migration software in the Contractor primary data center
6	As required to support the migration strategy, install and configure the DASD data migration software on the Government primary source mainframe system
7	As required to support the migration strategy, install and configure the Tape data migration software in the Contractor primary data center
8	As required to support the migration strategy, install and configure the Tape data migration software on the Government primary source mainframe system
9	Application of all required toleration (zBC12 to z15) technology migration and hardware/software (e.g. DS8870 and TS7740 storage) compatibility patches on the source Government mainframe prior to the execution of the first Migration Dry Run
10	Develop the batch jobs to control the PPRC replication
11	Configuring backup jobs
12	Executing and monitoring the PPRC replication
Migration Planning Dry Run 1
1	Develop project plan for Dry Run 1
2	Coordinating a review of Government developed test cases, test scripts, and success criteria with Contractor prior to the execution of the first Migration Dry Run.
3	Initial system data copy to the Contractor primary data center target mainframe
4	Execution of an Contractor infrastructure level test plan for Dry Run 1
5	Capture “Discovered Issues”
6	Government application test plan executed
7	Review and update plans
Migration Planning Dry Run 2
1	Develop project plan for Dry Run 2 and incorporate results from Dry Run 1 Contractor infrastructure test and Government application test
2	Implement a mainframe change freeze beginning with the start of Migration Dry Run 2 through the Government Workload Cutover
3	Refresh system data copy to the Contractor primary data center target mainframe DASD and Tape
4	Execution of Contractor infrastructure level test plan for Dry Run 2
5	Perform a test execution of the migration plan within the change window time constraints
6	Test and validate that the mainframe workload is working as expected and Government is ready for the Government Workload Cutover Milestone
7	Government application test plan executed for Dry Run 2
8	Refine the cutover runbook based on the test execution
Migration Planning Cutover
1	Final system data copy to the Contractor primary data center target mainframe DASD and Tape
2	Conducting a production readiness validation for the PaaS environment
3	Make a formal “Go/No Go” Decision in conjunction with Government
4	Perform cutover of production operations from Government primary data center to the Contractor primary data center environment
5	Work with Government to have any connections pointing to Government production, redirected to Contractor primary data center mainframe
6	Post go-live review
7	Provide any required artifacts as input to the Government Authority to Operate (ATO)
Hardware Management
1	Perform device software upgrades.
2	Coordinate and manage device software implementation.
3	Review hardware for changes in functionality.
4	Maintain an inventory of hardware and its licensed internal code levels. Review on a semi-annual basis the availability of licensed internal code updates and schedule any implementation
Change Management
1	Develop and Maintain change management procedures.
2	Coordinate change requirements for the base operating system and agreed upon IBM / ISV (Third Party) program products.
3	Coordinate change requirements for agreed upon system hardware.
4	Conduct Change Management meetings and follow-ups.
5	Open change tickets for all Contractor owned changes.
6	Open change tickets for Government owned changes.
7	Review requested changes during the weekly change meeting.
8	Approve requested changes during the weekly change meeting.
9	Review change tickets, as appropriate, to ensure implementation, test and back out information is included.
10	Complete Root Cause Analysis for failed changes according to change management procedures
11	Conduct Internal peer reviews for changes.
12	Close Contractor owned change tickets with status and implementation detail at completion of change.
13	Ensure software, hardware, monitoring, performance, and operational dependencies are included in change management planning and discussions and conduct internal peer reviews.
14	Document application and user test schedules. Insure the Government user community performs required testing.
Problem Management
1	Develop and maintain problem management procedures.
2	Co-ordinate problem resolution for supported IBM / ISV (Third Party) program products.
3	Co-ordinate problem resolution for program products not supported by Contractor.
4	Co-ordinate problem resolution requirements for the agreed upon system hardware.
5	Open problem tickets for Contractor problems identified or as requested by Government.
6	Open problem tickets for Government problems identified or as requested by Contractor.
7	Take action, as required, to resolve open problems.
8	Ensure resolution detail is included in problem ticket before closing.
9	Provide an agreed upon set of problem status reports.
10	Provide agreed upon problem tracking statistics and trend analysis.
11	Coordinate Problem Management meetings and follow-ups.
12	Provide status updates on problem tickets, as required.
13	Open change tickets for business impacting incidents owned by Contractor.
14	Complete Root Cause Analysis for business impacting incidents for Contractor owned problems.
15	Review problem tickets for process compliance.
16	Document problem and notification timeline, initial job/system log and error information in problem ticket.
17	After problem has been resolved, assign ticket to proper support group so they can research that all preventative measures have taken place to prevent the problem from re-occurring. Ticket will then be closed by that support group after support, Service Delivery Manager, and Government agree that automation implementation or all other measures have been taken to prevent re-occurrence.
General Cross-Functional Responsibilities
1	Participate as needed in DR processes and tests.
2	Participate as needed in problem / change management process.
3	Actively seek process and efficiency improvements as well as feature exploitation.
4	Perform management within Encryption Key Manager.
CICS Specific Roles
1	Review/implement work requests received. Review these requests to ensure security and capacity issues are addressed.
2	Define and document CICS monitoring thresholds.
3	Implement CICS monitoring thresholds.
4	Define and document performance requirements of CICS.
5	Generate reports detailing the performance of CICS.
6	Review and Recommend changes to improve CICS performance.
7	Application problem determination.
8	Communicate to Contractor application design changes that might have an impact to the overall system environment and performance. Jointly determine impacts and actions.
9	Review all application design changes for system resource impact.
DB2 specific roles
DBMS Systems Support
1	Define and document DB2 monitoring thresholds.
2	Implement DB2 monitoring thresholds.
3	Define and document performance requirements of DB2.
4	Generate reports detailing the performance of DB2.
5	Make recommendations for changes to improve performance.
6	Implement performance improvements.
7	Application problem determination.
8	Review and Recommend changes to improve DB2 performance.
9	Define, document and perform DB2 catalog maintenance procedures.
10	Make DB2 catalog performance improvement recommendations.
11	Application DBMS design and administration.
12	Recommend operating system tuning to address DBMS performance issues.
13	Communicate to contractor application database related changes that might have an impact to the overall system environment and performance. Jointly determine impacts and actions.
14	Review all application database related changes for system resource impact.
15	Maintain DB2 Catalog
DB2 Physical DBA
Standard physical DBA support is for production only, with Government retaining physical DBA for development/test environments. Physical DBA for development/test is a custom solution.
1	Comply with security standards as contracted with Government.
2	Perform Security Health Check review and identify remediation requirements. (not applicable for IMS).
3	Maintain production application database security accesses at database object level (not applicable for IMS).
4	Provide prime shift Physical DBA Problem Determination and Resolution for production application databases.
5	Provide 24/7/365 On Call problem resolution support for high severity problems on production application databases.
6	Review production application database monitoring output and provide remediation as necessary (e.g. space, CI/CA splits).
7	Define, schedule and Execute DBMS Utilities in support of production application databases (IMAGE COPIES, REORGS, RUNSTATS, MODIFY, etc. ).
8	Perform Physical Database restores for production application databases to recover from hardware or database product software problems, based on Government input.
9	Maintain production application database backup solution according to Government requirements.
10	Provide production application database statistics as input for Capacity & Performance in support of planning activities upon request (e.g. DB2 explain results).
11	Execute Physical Database changes to existing production application database objects which do not increase support requirements.
12	Provide time estimates for database related tasks within project plans
13	Assess all production application database related changes for technical impact at a physical DBA level, and sign-off changes as per change process requirements.
14	Participate in high severity problem reviews as appropriate where DBA action is required (e.g. Root Cause Analysis – RCAs).
15	Maintain IBM Proprietary Operational Database Documentation (Physical DBA Environment support documentation).
16	Perform database services using IBM or equivalent vendor supported database maintenance products/tools.
17	Provide database services using the defined Contractor Problem and Change Management processes and tools, and Request for Service processes and tools.
18	Provide consultation, as it pertains to contracted physical DBA support activities.
19	Participate in Disaster Recovery test, providing the services are included in the contract.
20	Execute object DDL to create application database objects (i.e. tables, indexes, packages, etc) in Production Environments.
21	Execute object DDL to create application database objects (i.e. tables, indexes, packages, etc) in Dev/Test Environments.
MQ Specific roles:
1	MQSeries Administration (this includes definition of new resources to MQ and use of the ISPF interface).
2	Application problem determination.
IMS Specific roles:
1	Provide IMS application licensing, installation, and patching.
2	Application problem determination.
Common roles for CICS, DB2, MQSeries, and IMS support personnel
1	Provide input to automation groups in an effort to increase system availability, facilitate system monitoring and minimize manual procedures.
2	Supply vendor-provided “sample” JCL procedures and Contractor suggestions to application programmers for the IBM supported program products that we support (if requested).
3	Document application and user test schedules. Ensure the Government user community performs required testing.
4	Install, customize, upgrade and maintain the DBDC subsystem software and agreed upon IBM / ISV (Third Party) program products / operational tools / utilities.
Disaster Recovery Plan
1	Define Disaster Recovery objectives.
2	Develop and maintain the Disaster Recovery Plan.
3	Review and update the Disaster Recovery Plan on a periodic basis or as warranted by business and/or technical changes.
Disaster Recovery Testing
1	Test and validate the mainframe support in the Disaster Recovery Plan as provided for in the Disaster Recovery Plan.
2	Provide report of the test results following each Disaster Recovery Plan test.
Disaster Recovery Execution
1	Perform recovery in accordance with the Disaster Recovery Plan.
Disaster Recovery Assessment
1	Review test result based on objectives.
2	Document and review problems through the problem/change management tracking process.

File details come from the government source that posted it. Updated Dec 23, 2022.