Mainframe Legacy Application

ATTACHMENT I Mainframe Legacy Application Data Migration Archival Retrieval & Reporting

Contents Statement of Work... 3 SECTION 1 Project Overview... 3 1.1 Project Scope... 3 1.2 Background... 3 1.3 Purpose and Objectives... 4 SECTION 2 Roles and Responsibilities... 5 2.1 Metro IT Responsibilities... 5 2.2 Contractor Responsibilities... 6 SECTION 3 Performance Requirement Summary... 6 3.1 Performance Requirement Summary... 6 SECTION 4 Project Phases and Detailed Requirements... 9 4.1 Project Phases... 9 4.2 Detailed Requirements... 9 Phase I Data Analysis, Tool Installation, Methodology and Implementation Plan... 9 Phase II Design... 11 Phase III Build and Test... 14 Phase IV Full Deployment and Training... 15 Phase V Closeout and Post Implementation Support... 16 SECTION 5 Deliverables... 16 5.1 Deliverables... 16 SECTION 6 Evaluation... 17 6.1 Staff Qualifications... 17 6.2 Proposed Solution... 18 SECTION 7 Other Project Requirements... 19 Project Monitoring and Termination... 19 Personnel substitutions... 19 Period of Performance... 20 Place of Performance/Working Hours... 20 APPENDIX... 21 A. Applications Summary Table... 21 B. Legacy Hardware and Software... 22 MF Legacy Application Data Migration Archival Retrieval & Reporting 2

Statement of Work SECTION 1 Project Overview 1.1 Project Scope This Statement of Work (SOW) sets forth the requirements, roles and responsibilities of the Parties for the Mainframe Legacy Application Data Migration and Archival Services provided under this Agreement. Mainframe Legacy Application Data Migration and Archival Services are the Services and Activities, as further detailed in this SOW required to formulate an enterprisewide data migration and archival strategy and migrate the data in 4 mainframe applications from their current locations to a long-term supportable archival and retrieval system without compromising its original business context. The Service Provider shall be responsible for the identifying, prioritizing, performing safe migration and archival, testing and certifying of all migrated and archived data from the current mainframe environments to the new modern environment. 1.2 Background The Washington Metropolitan Area Transit Authority (Metro) was created by an interstate compact in 1967 to plan, develop, build, finance, and operate a balanced regional transportation system in the national capital area. Metrorail and Metrobus serve a population of 3.4 million within a 1,500-square mile jurisdiction. Metro began its paratransit service, MetroAccess, in 1994 which provides close to 1.5 million trips per year. In 1998 a Metro Information Technology Diagnostic Review revealed that the current state of IT systems was outdated, compartmentalized and under-invested. By December 2000 a plan was developed to replace them with an enterprise-wide solution. The program was called IT ReNEWal and its focus was to replace the aging legacy business systems with commercial-offthe-shelf software. The Information Technology Renewal Program (ITRP) team selected Oracle PeopleSoft as the COTS software of choice for the financial and human resource system, IBM Maximo for maintenance and materials management, and Trapeze for bus and rail scheduling. Over the next three plus years the team configured, tested and placed into production the software being utilized today. Prior to modernizing its IT infrastructure and applications, Metro used business applications that ran on an IBM mainframe computer. Most of these legacy business applications were written in COBOL, CICS and or CA-IDEAL and use VSAM or CA-DATACOM Database (non-sql version) as the file system. This mainframe environment is still a part of the IT infrastructure today and continues to support many active legacy applications. The IT department plans to sunset/decommission the mainframe by June 2010. MF Legacy Application Data Migration Archival Retrieval & Reporting 3

The legacy applications that remain on the mainframe fall into two categories; those that are in the process of being replaced by currently active projects and those that were replaced by the IT ReNEWal program mentioned above but never decommissioned and are still being used for historical look-up. The latter group, replaced Applications, presents the greatest risk to the goal of decommissioning the mainframe and is the primary focus of this statement of work. 1.3 Purpose and Objectives Before the mainframe can be turned off, the data from these replaced applications must be moved to an independent platform for inquiry and reporting. There are four applications that were replaced by the IT ReNEWal program but are still being used occasionally. They are: GEAC a CICS/COBOL/VSAM mainframe system that contains historical accounting, budget, accounts receivable/payable, procurement information CMIS a CICS/COBOL/DATACOM mainframe system containing contract and cost information relevant to major Metro capital projects GENESYS a CIC/COBOL/VSAM mainframe system containing HR & Payroll data that must be maintained for historical research MARS/MMS CICS/COBOL/DATACOM mainframe systems that contain maintenance and procurement records that are kept for litigation and other support purposes Data in the above legacy applications has not been updated since their replacement and end users use these applications in read only mode. The accounting, procurement, audit and legal departments use the GEAC, CMIS, GENSYS, and MARS/MMS mainframe applications to research historical items and resolve disputed claims. As is the case with most obsolete mainframe applications, IT also has extremely limited functional and technical knowledge about the replaced mainframe applications, their data, and whether business rules are contained in the data layer or application layer. Most of the IT employees who had expertise with these applications have retired. Metro has a few personnel who can provide some information about the GENESYS, MARS/MMS, and CMIS applications however there is very little technical knowledge in house about the GEAC application. The overarching goal is to develop an enterprise-wide strategy for archival and retrieval of data in both legacy and current production application systems. The purpose of this project is to migrate/archive all the data in the GEAC, CMIS, GENESYS and MARS/MMS applications to a long-term supportable archival and retrieval system without compromising its original business context to ensure speedy dispute resolution, meet legal and audit compliance requirements, and mitigate risks associated with maintaining obsolete systems that are scarcely used. See Appendix A - Application Summary Table and Appendix B Legacy Hardware and Software for additional details regarding the applications and current mainframe environment. MF Legacy Application Data Migration Archival Retrieval & Reporting 4

The key project objectives are: To implement a data migration/archival methodology that preserves business records in the mainframe legacy applications in an audit-ready, point in time format that reflects the original business context of the data. To identify the data usage requirements of all the major stakeholders of the four mainframe legacy applications. To implement suitable security measures that ensure that migrated/archived data is never tampered with or compromised accidentally due to unauthorized access. To provide standardized and easy to use online search and retrieval mechanisms and reporting capabilities for the migrated/archived data that end users are able to access with minimal support from the IT department. To provide reliable cleanup procedures for any temporarily retrieved archived data so as to eliminate the buildup of redundant data in the reporting system. To ensure that the lack of technical and functional knowledge regarding the mainframe applications specifically the GEAC application is mitigated by the contractor who will provide this missing knowledge or suggest suitable alternatives to overcome this problem. To develop a uniform data migration/archival strategy for ensuring consistency in managing historical legacy data across Metro. To develop suitable data retention policies and data procedures for identifying and archiving data currently in production systems. Provide documentation and training for Metro IT personnel so that the requests of end users for archived data is satisfied in a timely manner. To identify a Standard Reporting tool that will be used enterprise wide for retrieving and preparing reports against archived data SECTION 2 Roles and Responsibilities 2.1 Metro IT Responsibilities a. Provide overall project direction and management. b. Review recommendations and provide final decisions on technical matters. c. Establish a Project Steering Committee. MF Legacy Application Data Migration Archival Retrieval & Reporting 5

d. Review and provide feedback and approval for deliverables within 10 business days, unless otherwise specified in the Contract or Work Plan, after receipt of delivery to the Project Management Office. e. Establish project organization by meeting with Service Provider project management to finalize and document areas of responsibility, personnel reporting relationships and administrative procedures. f. Establish evaluation mechanisms by setting up procedures for day-to-day control of the project as defined by the combined (Metro IT and Contractor) project management team. g. Coordinate other Metro resources as needed (e.g. Office of Property Management) to support the project. h. Obtain appropriate Metro approvals and commitment. i. Provide information and answer questions at Contractor request. j. Perform backups, DBA and IT security functions. k. Provide hardware and infrastructure which is consistent with current WMATA architecture, to be used for installation of Data Management software. 2.2 Contractor Responsibilities a. Provide and implement a state-of-the-art solution using industry best practices. b. Deliver the completed project which meets all objectives and requirements stated in this Statement of Work, on time and within budget. c. Track and manage all issues and problems through to resolution, with appropriate escalation. d. Notify the Metro IT Project Manager about any problems, exceptions or issues that may adversely impact the project schedule or budget in a timely manner. SECTION 3 Performance Requirement Summary 3.1 Performance Requirement Summary Required Service Desired Outcome Performance Measures Enterprise-wide data Migration/ Archival/Retrieval Strategic Plan An enterprise-wide data migration, archival and retrieval methodology and plan for Mainframe legacy applications and Current Business Applications in production. Metro IT Management review for completeness. MF Legacy Application Data Migration Archival Retrieval & Reporting 6

Data Migration/Archival/ Retrieval tool Security Technical support for mainframe legacy applications Legacy Data Usage Identification Analysis of mainframe legacy applications and Data Legacy Data Migration Legacy Data Archival Procure, install, setup and configure a standardized data migration and archival COTS tool that can be used for obsolete legacy formats as well as existing production systems Controlled access to migrated/ archived data and an easy to use audit trail of data access that includes user name, access time, access mode, etc. Metro IT s limited knowledge about mainframe applications, particularly GEAC is mitigated Interview legacy application endusers and capture data usage of the GEAC, CMIS, GENSYS, & MARS/MMS mainframe applications and classify the data based on the frequency of usage. Technical analysis of mainframe data identifying special formats like packed decimals, signed integers, etc along with inter-relationships between different data fields. Document information required to ensure that the original business context of migrated/archived is captured. Migration of data from obsolete legacy Datacom and VSAM formats to a standardized format that can easily be maintained by existing IT staff skill-sets. Documentation of key criteria used by auditors to evaluate regulatory compliance of migrated data. Archive data in a standardized platform independent format that cannot be altered, is easy to retrieve and can easily be maintained by existing IT staff skill-sets. Documentation of key criteria used by auditors to evaluate Sample migration/archival/retrieval tests for all: Legacy mainframe (GEAC, CMIS, GENSYS, MARS/MMS) components Production (PeopleSoft, Maximo, etc) components Security tests to ensure that the migrated/ archived data cannot be tampered with or compromised accidentally. Audit trail tests. Contractor demonstrates sufficient technical knowledge about mainframe operating system, languages, and data formats Data usage document that will be reviewed and signed off by Metro IT Management. Technical Analysis document that will be reviewed and signed off by Metro IT Management. Tests that demonstrate that the migrated data is secure, retains its original business context, is audit ready and meets all regulatory compliance requirements. Tests that demonstrate that the archived data is secure, retains its original business context, is audit ready and meets all regulatory compliance requirements. MF Legacy Application Data Migration Archival Retrieval & Reporting 7

Reporting tool for archived data Data Retrieval and Reporting Project Management Services regulatory compliance of archived data. Identify a standardized easy to use reporting tool that can be used by all Metro departments for archived data A search engine for migrated/ archived data. Canned reports and ad hoc reporting capabilities that will replace the obsolete methods users currently use to research and access historical data Contractor shall be the focal point for all data migration/archival concerns and ensure problems are identified and mitigated in a timely manner using commercially acceptable best practices and standards. Contractor shall follow PMI standards for managing the triple constraints of scope, schedule, and cost are followed. Provide a detailed project implementation plan broken down through at least the 3 rd level that tracks the work performed and can identify potential problems well in advance. Provide weekly status reports highlighting the amount of work performed, issues, mitigation steps etc Metro IT Management review and acceptance of reporting tool recommendation report. End user testing and signoff for accessing migrated/archived data. Ensure that PMI standards for managing the triple constraints of scope, schedule, and cost are followed. Weekly status reports will be monitored to track the amount of work performed and that the project is on schedule MF Legacy Application Data Migration Archival Retrieval & Reporting 8

SECTION 4 Project Phases and Detailed Requirements 4.1 Project Phases This section describes high level project phases, task details will be defined during Phase I, the analysis and planning phase. The key implementation tasks and deliverables are detailed in subsequent sections. Please note that the Project Management function is an integral part of this project implementation and project management tasks run through all stages of the project. Project execution consists of 5 phases: I. Data Analysis, Tool Installation, Methodology and Implementation Plan This stage of the project entails analyzing the mainframe applications and data, determining the data usage requirements of end users and preparing a detailed Implementation Plan. The data management tool will be installed and configured at this stage. II. III. IV. Design Involves preparing data migration, archival, and retrieval plans. Build and Testing - Involves data migration, data archival, and developing reports, ad hoc queries for the pilot, system and user acceptance testing. Deploy and Train Involves full deployment and user and IT staff training, V. Closeout and Post Implementation Support Involves project closeout and post implementation support. 4.2 Detailed Requirements Formulating an enterprise wide standardized archival/retrieval methodology as well as migrating and archiving data currently in obsolete mainframe formats to modern platform independent formats and storing it in a secure easy to retrieve environment is the goal of this project. Metro IT recognizes that there are several ways to achieve this goal and looks to the contractor to use industry best practices, tools, and a methodology to achieve this goal. Phase I Data Analysis, Tool Installation, Methodology and Implementation Plan 4.2.1 Project Planning and Status Reporting The contractor is required to provide a detailed project plan and schedule covering project management, requirements and design, software (tool) installation and configuration, Pilot, and other implementation tasks within 2 weeks of start of the project. The plan should focus on deliverables and should be broken down at least through the third level of the Deliverable Work Breakdown Structure (DWBS). MF Legacy Application Data Migration Archival Retrieval & Reporting 9

The contractor is required to provide weekly status reports and updated schedules. The status reports should mention work that was scheduled to be performed along with work that is actually performed and deviations should be highlighted. Work expected to be performed before the next status report is due should also be mentioned. Key milestones should be mentioned along with anticipated and/or unforeseen problems. 4.2.2 Migration/Archival Tool Installation and Configuration This task may be performed in parallel with other project tasks. The contractor is required to perform the following tasks for the COTS data migration/archival (data management) tool that will be used to migrate and archive the legacy data: a. The contractor is required to provide technical specifications of hardware and software that is required to run the tool. b. The contractor is required to prepare an Installation and Configuration document consisting of: i. The physical and logical architectures of the tool ii. Technical details about all major components and tiers of the migration/archival tool architecture iii. Detailed installation steps iv. Detailed configuration and setup tasks and steps. v. Specifications and details about adapters and other objects that may currently be needed for mainframe data files as well those required in future for PeopleSoft, MAXIMO and other production systems. The installation and configuration document should be detailed enough for Metro IT staff to restore and configure the archival and retrieval environment in the event of a catastrophic disaster. c. The contractor is required to provide, install and configure the migration/archival tool. d. The contractor is required to demonstrate accurate functioning of all migration/archival/retrieval components of the COTS tool that are required for: 1) Legacy mainframe (GEAC, CMIS, GENSYS, MARS/MMS) applications 2) Current Production (PeopleSoft, Maximo, etc) applications 4.2.3 Data Usage End users currently access the mainframe data by logging into the mainframe application. Since these applications have been replaced it is assumed that there are no data updates and users use the data in read only mode. The contractor is required to work with Metro IT staff, Subject Matter Experts (SMEs) and end users and identify data usage, means of access, reports and queries etc for each of the 4 mainframe legacy applications. For each of the 4 legacy applications the contractor is required to: MF Legacy Application Data Migration Archival Retrieval & Reporting 10

a. Identify data usage and examine the reports and screens that are used to access the data. b. Perform analysis in order to determine whether the business context is reflected in the data only or if it resides in the application layer. c. Prepare a data usage report that lists the key data being used by end-users and includes: i. The reports, inquiry screens, and other mechanisms that end-users use to access the data. ii. Information about whether the business rules reside in the data layer, the application layer, or a combination. iii. Information about data access frequency and categorize data based on access frequency. 4.2.4 Data Analysis The contractor is required to examine the technical information about the data for each of the four mainframe applications and prepare a data analysis report. The report should include: a. Data layouts and field formats b. Copy book names, data dictionaries and mappings of data file descriptions to data dictionaries where applicable. c. Information about special field formats like signed integers, packed decimals, etc where applicable. d. Interrelations between data in different files. e. Information relevant to maintaining the original business context of the data should be stressed. Phase II Design Formulating an enterprise-wide data archival and retrieval plan for all Metro IT applications including replaced applications and applications currently in production is a key objective of this project. While the contractor is only required to perform data migration, archival, and reporting tasks for data in the GEAC, GENSYS, CMIS, and MARS/MMS applications the contractor must formulate a Strategic Data Migration, Archival, and retrieval plan that will cover all Metro IT applications. The contractor is required to prepare specific design documents that detail the methodology and steps that will be followed for migrating and archiving data in the GEAC, GENSYS, CMIS, and MARS/MMS applications. The contractor is also required to prepare a data retrieval design document detailing search capabilities, inquiry and reporting capabilities etc for archived data. Based on the strategy formulated the contractor is also required to identify a Common Reporting tool that will be used for all archived data across Metro. MF Legacy Application Data Migration Archival Retrieval & Reporting 11

4.2.5 Data Migration/Archiving Strategic Plan The contractor is required to prepare a data migration/archiving plan for data in each of the four mainframe applications based on the data usage and data analysis reports. The contractor is required to provide details about the following in the plan: A. How the original business context of the data will be preserved. B. Data security provisions to prevent tampering or accidental compromising of the data. C. The techniques that will be used for signed integer, packed decimal and other special formats to ASCII conversion. D. Steps to ensure referential integrity of the data where applicable. E. Data formats and other storage specifications of the target destinations of the migrated and archived data. F. How the plan can be extended to other mainframe data migrations. G. How the plan can be extended to current production systems 4.2.6 Design Documents The contractor is required to prepare a design document that includes the approach and detailed steps that will be used to migrate and archive data from the mainframe to the new environment. Search capabilities, ad hoc and canned reports and all aspects pertaining to retrieval mechanisms that will be used to access the migrated and archived data should also be described in detail. Clean up mechanisms for temporarily restored archived data should also be described in detail. The design document should also include Functional as well as technical aspects of the migration, archival and retrieval mechanisms along with security details that will prevent unauthorized access and/or tampering of the data. 4.2.6.1 Data Migration Design Document Data from the mainframe data files needs to be migrated to the target environment in the format determined by the contractor s strategic plan. The contractor is required to prepare a data migration design document that contains: a. Data mapping information that includes: i. Source and target field names. The source and target field names will often be the same however the contractor needs to identify data fields that may be described in other related data dictionaries and use those descriptions for the target fields where necessary. ii. Source and target field types. Mainframe data types could be alphabetic, alpha numeric, numeric, integers, signed integers, decimals, packed decimals etc. Source data types should be identified and any special conversion requirements should be specified in this step. Data fields that have constraints like ranges or other validation characteristics should also be noted in this step. b. Data interrelationships needed to maintain referential integrity c. Data conversion and/or data validation requirements where necessary. d. Information required to retain the original business context of the data MF Legacy Application Data Migration Archival Retrieval & Reporting 12

e. Steps that will be performed to move the data from the mainframe to the target f. Security related information that prevents unauthorized access and/or data tampering 4.2.6.2 Data Archival Design Document Data archival deals with moving historical data to secondary offline storage. The legacy applications have been replaced by other applications therefore all the data in the 4 legacy applications is deemed historical in nature. The contractor s archival strategy will determine whether the mainframe data targeted for archival will be archived to the target format directly off the mainframe or via an intermediate tier. Similar to the data migration design document the contractor is required to prepare a data archival design document that contains: a. Data mapping information that includes: i. Source and target field names. The source and target field names will often be the same however the contractor needs to identify data fields that may be described in other related data dictionaries and use those descriptions for the target fields where necessary. ii. Source and target field types. Mainframe data types could be alphabetic, alpha numeric, numeric, integers, signed integers, decimals, packed decimals et1. Source data types should be identified and any special conversion requirements should be specified in this step. Data fields that have constraints like ranges or other validation characteristics should also be noted in this step. b. Data conversion and/or data validation requirements where necessary. c. Data interrelationships needed to maintain referential integrity d. Information required to retain the original business context of the data e. Steps that will be performed to move the data from the mainframe to the archive f. Security related information that prevents unauthorized access and/or data tampering of archived data In addition to the above the archival design document should determine a strategy for data identified as frequently accessed in Stage I that may be candidates for data archival and determine if it should be kept in online storage or if it should be archived to offline storage along with the rest of the historical data. (For example end users lookup Payment Information more frequently than other information available in GEAC so it may be better to keep payment information in online storage and the other less accessed data in offline secondary storage) 4.2.6.3 Data Retrieval Design Document Metro expects the contractor to recommend a common reporting tool that will be used enterprise-wide for all archived data. The contractor should identify such a tool and provide suitable justifications for the recommendation in the data retrieval design document. The capabilities, strengths and weaknesses of the reporting tool should also be described detail. MF Legacy Application Data Migration Archival Retrieval & Reporting 13

The data retrieval design document should describe all data retrieval mechanisms in detail focusing on how the authenticity and original business context of retrieved data will be maintained. It should describe online search mechanisms that will be used to search and access archived data. End users currently login to the mainframe applications in order to access the mainframe data and are accustomed to fairly quick turnaround times. The retrieval design document should describe how end users currently access the data and the corresponding solution in the new migrated/archived environment. Inquiry capabilities, ad hoc reporting capabilities, and canned reports should also be described in detail. 4.2.7 Environments The contractor is required to provide Metro IT the detailed hardware and software specifications for the development, test, production and other environments. They are also required to work with Metro IT to setup these environments. Phase III Build and Test Data Migration and Archival Services are the activities associated with the execution of the plans and strategies developed in earlier stages. The contractor will build a pilot to demonstrate the migration, archival and retrieval capabilities of the system. System and user acceptance testing will also take place during this phase. 4.2.8 Pilot The contractor is required to perform a full life cycle pilot migration, archival, retrieval, and testing that includes developing reports and inquiry mechanisms with a limited portion of the data before performing large scale migrations and archivals. End-user signoff will be required before proceeding with full deployment. 4.2.9 Data Migration Data migration is the physical move of mainframe business data, configuration data and metadata currently in obsolete VSAM/DATACOM formats from the mainframe to the target environment in a modern state-of-the-art format. The contractor is required to move the mainframe data from its source to a modern state of the art format that will be easy to access and easy to maintain. 4.2.10 Data Archival Data Archival is the physical move of data to secondary storage. Data may be archived either from the target environment to the secondary storage or directly from the mainframe to the secondary storage depending on the contractors methodology. a. The contractor is required to provide mechanisms to access data in offline secondary storage and provide response times needed for accessing the archived data. MF Legacy Application Data Migration Archival Retrieval & Reporting 14

b. If the contractor s strategy entails loading archived data from offline secondary storage to online storage the contractor is required to provide suitable mechanisms to remove the restored archived data from the online storage in order to prevent the online storage to be cluttered with redundant data. 4.2.11 Data Retrieval and Reports The retrieved data should be authentic and reflect the original business context of the data in order to satisfy legal, audit, and research requirements. a. The contractor is required to provide suitable mechanisms that end users can use to access the migrated and archived data with minimal support from Metro IT. b. The contractor is required to provide for ad-hoc as well as canned reports c. The contractor is required to provide search mechanisms for archived data using a search engine or other inquiry mechanisms. d. The contractor is required to ensure that retrieved data can be easily printed. 4.2.12 Testing The contractor is required to prepare detailed test plans for each of the 4 legacy applications. The test plan should: a. Clearly describe all the functionality that will be tested. b. Have sections for expected test results and actual test results. c. Include means to document test results d. A User Acceptance section Overall moves will be considered successful when established baseline, operational, and acceptance tests are completed and meet or exceed the test plans. Phase IV Full Deployment and Training After a successful pilot, the contractor will provide and execute an implementation plan for full system deployment. The contractor is required to manage and monitor the physical data moves during migration and archival based on the migration and archival plans established in earlier stages. The contractor is required to train Metro IT support personnel on the migration/archival tool and end-users on data retrieval tasks. The contractor is also required to provide suitable enduser and technical support training material for end-users and Metro IT support staff. 4.2.13 Data Migration, Archival and Retrieval of remaining applications At the completion of the pilot Metro IT will review all data, test results, documents and measure the success of the pilot based on the following criteria: a. The pilot is completed on time and within budget MF Legacy Application Data Migration Archival Retrieval & Reporting 15

b. Successful operational tests were conducted c. User Acceptance test sign off and go ahead to proceed The procedures followed in the Pilot may be modified if necessary and applied to data in each of the remaining 4 legacy applications to complete the migrated and archival retrieval mechanisms. End user signoff will be required to complete this stage of the project. 4.2.14 The contractor is required to provide a document or report that lists criteria that an independent evaluator would use to certify the validity of the migrated/archived data in order to ensure regulatory compliance. The contractor is also required to provide a written certification that the migrated/archived data is audit ready and will pass regulatory compliance inspection by an authorized evaluator. 4.2.15 The contractor will provide training documentation and end user training for users of the 4 legacy applications and ensure that they are able to successfully retrieve data for research purposes and satisfy queries from regulators, auditors, and external entities. 4.2.16 The contractor will provide technical documentation and technical training for Metro IT staff who will be maintaining the migration and retrieval system. Phase V Closeout and Post Implementation Support In this phase the contractor will provide Post Execution Documentation, which shall include a summary of the migration, archival, and retrieval processes that were employed and list the metrics and measurements against success factors and detailed disposition of each service provided. 4.2.17 The contractor will provide 1 week of post production support to address any problems or issues that might arise after production implementation. 4.2.18 The contractor shall complete all open or punch list items during this phase. 4.2.19 The contractor will provide documentation and technical instructions that will enable System Administrators and DBAs to migrate and/or archive data from existing production systems as the data becomes candidates for archival. 4.2.20 Post Implementation will be deemed successful and signed off based on an audit of the completion documents and success metrics. A formal sign off will be required with a hand over to Metro IT. SECTION 5 Deliverables 5.1 Deliverables Where documents are required, the contractor shall provide electronic documents to the COTR using standard Microsoft Office Suite applications unless otherwise agreed to. Where phases have been specified for completion dates, actual dates will be determined based on agreed upon project schedule. MF Legacy Application Data Migration Archival Retrieval & Reporting 16

Key deliverables and activities are shown in the table below: No Deliverable 1 Project Plan and Schedule with a Deliverable Work Breakdown Structure and milestones Completion Date/Stage 2 weeks from start of project 2 Periodic Status Reports Weekly 3 Data Migration/Archival Strategic Plan document 3 weeks from project start 4 Migration/Archival Tool Installation and Configuration Phase I document 5 Acquisition, Installation and Configuration of Migration/Archival tool Phase I 6 Data Usage document (include all reports and inquiry Phase I requirements) 7 Data Analysis document or report Phase I 8 Data Migration Design document Phase II 9 Data Archival Design document Phase II 10 Data Retrieval and Reporting Design document Phase II 11 Test Plans Phase II 12 Independent Certification Criteria document Phase II 13 Pilot Migration, Archival, and Reporting Phase III 14 Pilot Test Results documentation and Signoff Phase III 15 Implementation and Roll Back Plan Phase III 16 Test Results documentation and Signoff of above Phase III 17 Signoff from all stakeholders Phase III 18 Full Migration, Archival, and Reporting Phase IV 19 Certification of migrated/archived data Phase IV 20 End user training and related documentation Phase IV 21 Technical support training and related documentation Phase IV 22 Post Implementation support Phase V 23 Post Execution Document summary of activities Phase V SECTION 6 Evaluation 6.1 Staff Qualifications The contractor will be responsible for providing appropriately skilled staffing for the Data migration, archival, retrieval and reporting requirements of this project. The experience of the provider s company as well as its employees, especially those working on this proposed implementation is critical to the success of this project. The required qualifications are mentioned below. MF Legacy Application Data Migration Archival Retrieval & Reporting 17

6.1.1 Qualifications of Project Manager The project manager must have implemented at least one (1) such project that involved mainframe VSAM, DATACOM (non-sql version) or equivalent file types. The Project Manager should be well versed with Project Management techniques and the use of Industry Standard Project Management tools. PMI certification is a definite plus. 6.1.2 Qualifications of Mainframe Technical Specialist/Data Management Analysts The migration/archival analyst must have implemented at least one (1) such project that involved mainframe VSAM, DATACOM (non-sql version) or equivalent file types. The Analyst should have extensive IBM mainframe experience with expertise in COBOL, CICS or other mainframe languages and Datacom, DB2, VSAM or other mainframe file systems. The Analyst should be well versed in data management best practices and familiar with regulatory compliance, audit, and legal requirements. The analyst should be able to work with end-users, understand their business needs and be able to translate these into technical specifications, which when implemented meet user requirements. 6.1.3 Qualifications of Data Archival/Retrieval Technical Specialists The migration/archival Technical Consultants should implemented at least one (1) such project that involved mainframe VSAM, DATACOM (non-sql version) or equivalent file types. The Technical Specialist should be a product expert, with expertise in installation, configuration and setup of any tools that may be required for migration, archival and retrieval purposes. The Specialist should be well versed in data management best practices and familiar with regulatory compliance, audit, and legal requirements. Technical Specialist should have demonstrated experience in performing data migrations, data archival, data retrieval and report writing. 6.2 Proposed Solution The contractor should include the technical approach, software and hardware requirements, staffing plans, tools suggested etc in their proposal. The contractor should also provide a high-level Implementation Plan consisting of Management and Technical components. The section related to Project Management should include the proposed implementation plan, managerial oversight and control, managerial reporting mechanisms and tools to be employed. The Technical proposal should include the technical architectures for the proposed migration, archival and retrieval solution. The architecture should include security and error handling components. Information regarding the provider s past mainframe legacy data migration experience and client references play a crucial role in evaluating the provider along with the other technical and managerial factors mentioned. MF Legacy Application Data Migration Archival Retrieval & Reporting 18

6.2.1 Technical Approach/Solution The contractor shall submit a proposal outlining the approach that will be used to meet the requirements in this RFP. The proposal should include the technical solution, the project management approach and staffing mix as a response to this RFP. The evaluation criteria will include: Suitability of the solution, including the suitability of application software, hardware, and technical services to meet the specified requirements Proven reliability of all products at established user sites Price/Performance, including one-time and on-going costs Ease of use and the degree of security control provided GEAC Experience specifically experience with its data dictionary, data layouts, and processes Stability and Maintenance costs these should be extremely low. Archived data should not be affected by upgrades to retrieval software. High backward compatibility. 6.2.2 Past Performance Past Performance contains three sub factors which are of equal importance to each other; (1) Quality of Service (2) Timeliness of Performance and (3) Business Practices/Customer Satisfaction. The contractor shall provide contract references (at least 3) both for itself and for any major subcontractor to enable Metro to assess the quality of the contractor s /major subcontractor s past performance. The referenced contracts shall be similar in scope, magnitude and complexity to that contemplated in this RFP. The following information shall be included for each contract: Name and address of contracting activity, state or local government agency or commercial customer Contract type (fixed price/cost reimbursement) Contract Value Brief description of service required under the contract, including performance location(s) and performance period Name and telephone number of individual (administrative contracting officer/program manager) able to provide information about contractor s past performance. SECTION 7 Other Project Requirements Project Monitoring and Termination The provider will be monitored as per the plans mentioned in the Deliverables and the work description. Personnel substitutions Voluntary substitution of any of the proposed personnel is unacceptable and may be grounds for contract termination. Substitutions of personnel for reasons other than voluntary substitutions will be permitted MF Legacy Application Data Migration Archival Retrieval & Reporting 19

provided the replaced candidate has equivalent or better experience and qualifications. The provider has full authority over all other decisions related to their personnel. Period of Performance The period of performance for the Mainframe Data Migration, Archival and Retrieval project is not to exceed 6 months from the start date of the project. Place of Performance/Working Hours The place of performance is primarily at Metro Headquarters, 600 Fifth Street NW, Washington, DC, the Jackson Graham Building. Some off-site work may be permitted with approval from the Metro Project team. Contractor shall perform the required services Monday through Friday between 8:30 AM and 5:30 PM. MF Legacy Application Data Migration Archival Retrieval & Reporting 20

APPENDIX A. Applications Summary Table Application Description Replaced by Application GEAC GENESYS MARS/MMS CMIS Legacy Financial Management System PeopleSoft Finance Legacy HR/Payroll System PeopleSoft HCM Legacy Maintenance and Reliability System Maximo Cost Management Information System PeopleSoft Finance Replaced On 7/1/2004 7/1/2005 5/31/2006 7/1/2004 Data Retention 7 Yr. 7 Yr. 7 Yr. 7 Yr. MF Data Format VSAM VSAM CA-Datacom/DB CA- Datacom/DB Language CICS/COBOL CICS/COBOL CICS/COBOL/IDEAL CICS/COBOL CICS Name DNBCICS PRODADF IMSCICS CMIS CICP1AS CICP1AL CICP1AT CICP1AP Database Size 20GB 10GB 14 GB 2 GB Storage Media Disk and Tape Disk and Tape Disk and Tape Disk Archived Data Location Application Status Offsite Offsite Onsite Onsite Frequency of use 5-10 times/yr Monthly Weekly Once in 2 months No of Users 4-6 10-12 10-12 6-8 Mode <-----Read only----> Code <-----Frozen----> Access Mode <-----Mainframe Terminal Emulation----> MF Legacy Application Data Migration Archival Retrieval & Reporting 21

B. Legacy Hardware and Software Hardware: IBM Z890 MVS version: Z/OS 01.03.00 CICS version: CICS TS 1.3 COBOL version: VS COBOL II 1.4.0 IDEAL version: CA-IDEAL V2.2 Datacom version: CA-Datacom/DB V10.0 SP03 (non-sql version) MF Legacy Application Data Migration Archival Retrieval & Reporting 22