ATTACHMENT F – SCOPE OF SERVICES DRAFT STATEMENT of WORK Project Name: Software Configuration Management Implementation & Training Project Location: Driver & Motor Vehicle (DMV) - IS Headquarters Salem Oregon Agency’s System Application Agency’s Project Manager (“APM”) Manager (“SAM”) Name: Name: Address: Address: Phone: Phone: Fax: Fax: Email: Email: A. PROJECT DESCRIPTION and OVERVIEW of SERVICES Agency is contracting for services in connection with the following: implementation, configuration and training of the CA Endevor Software Configuration Management products (collectively “Endevor SCM”) as identified in this Statement of Work (“SOW”). The purpose of this Project is to implement, configure and train Agency personnel on the Endevor SCM products to automate the process of changing, deploying, and restoring software applications (“Project”). This Project will introduce a standardized, automated, regulated discipline of managing, tracking, and configuring most aspects of the application development process for ODOT’s Driver and Motor Vehicles Services Division (DMV). The Contractor shall provide the Project services identified in the SOW which include planning, analysis, implementation, configuration, migration, work process changes, testing, training/knowledge transfer and other activities required to ensure mastery of the products prior to closing the Project. The implementation of Endevor SCM will support and integrate the platforms and architectures to support the existing DMV business systems. The thorough training of administration and development staff is essential to ensure a successful pilot and roll out of Endevor SCM. Endevor SCM supports library management for source control and protection; version control to prevent code overlay; branching and merging capabilities; and will simplify recovery to prior versions of the source. Endevor SCM will automate many processes and reduce manual intervention to move, promote and restore source code. Additionally, the solution will allow retirement of the existing internally developed Library Tracking System (LTS) and other components that will be replaced through the implementation of Endevor SCM. Page 1 of 28 ATTACHMENT F – Scope of Services RFP #730-25400-12 Background: The Driver & Motor Vehicle (DMV) Information System (IS) group currently utilizes a home grown in- house solution called the Library Tracking System (LTS) that integrates with CA Panvalet for their mainframe Software Configuration Management (SCM) process. Some migration activities are manually orientated and do not provide safeguards to overlaying code or versioning. Quality assurance audits on large technology projects frequently result in a recommendation to implement source code controls including check-in/check-out, branching, merging, and version management. They also note that limitations of current products combined with the non-modular design of DMV’s core systems restricts the number of developers and testers that can be working simultaneously. In 2007 the Oregon Secretary of State conducted an audit of application software controls and practices and recommended implementation of a formal change management process that provides comprehensive source code controls. Developers need a more robust process that will help them manage, retrofit and automate their migration processes. Implementation of an industry standard product will automate the entire application lifecycle, enhance application development, improve software reliability and add to the number of projects that can be active concurrently. The Endevor SCM products have been purchased to meet the Agency’s need for an automated code migration management tool set. Purpose: To successfully implement Endevor SCM to support the current mainframe platform and architecture that currently exist today that supports the DMV business systems. The Endevor SCM products/tools, when implemented, will support library management, folder management and server management for source control, migration of code and components between environments and protection from code corruption. The Endevor SCM products/tools will manage the version control to prevent code searching, enhance branching and merging capabilities, and will simplify recovery to prior versions. Many other benefits will result from the successful implementation of the Endevor SCM products/tools including configuration management, identification and maintenance of component and system relationships. The Endevor SCM products/tools will automate many processes and reduce manual intervention to move, copy, migrate, promote, restore and recover systems code. Additionally, it will allow for future retirement of the existing internally developed Library Tracking System (LTS) and CA Panvalet. Page 2 of 28 ATTACHMENT F – Scope of Services RFP #730-25400-12 Objectives: To implement, configure and train Agency on Endevor SCM to automate the entire application lifecycle, allow for shared code during application development and improve software reliability and reporting of change impact. The implementation of the SCM tools/products will meet or exceed the risks addressed in the 2007 Secretary of State audit findings. ODOT Policy ISB-006 Purpose: “To provide standard methods and procedures for Information Systems staff to introduce and execute changes in the ODOT technical infrastructure and applications systems. To provide efficient and prompt handling of these changes in order to minimize the impact of change-related incidents upon IS service delivery and service quality, and consequently to improve the day-to-day operations of the IS organization. To assure open and adequate flow of information about impending changes and their possible consequences to those involved in the change or potentially impacted by the change.” Policy: “ODOT Information Systems shall use a documented change management process for the introduction of changes to user-impacted technical infrastructure and applications.” A.1 Scope of Work: Contractor shall provide and fully implement Endevor SCM to satisfy ODOT DMV’s requirements. Endevor SCM consists of multiple products, and must be tightly integrated with minimal complexity. Specifically, Endevor SCM must ensure that the mainframe implementation and the future implementation of client/server and web source can be managed using one integrated solution. DMV will provide management and oversight of the work performed by Agency staff to ensure that schedules are met by the Contractor and that Deliverables are received and satisfactory. The joint Project team will conduct planning, analysis, construction/configuration, migration, testing, implementation and all other activities required to fully implement the selected solution. Contractor shall implement Endevor SCM to ensure compatibility with Agency systems and technical architecture that supports all development, test, and production environments on the State of Oregon mainframe (only on the ODOT LPAR – DMV only). In Scope: 1. CA Endevor software products to be implemented, configured and trained on are: 1.1. The Mainframe implementation of CA Endevor 15.0 for the DMV, and its updates/patches 1.2. CA Endevor SCM Quick Edit 1.3. CA Change Manager Enterprise Workbench (1 Server) 1.4. CA Endevor Software Change Manager Parallel Development 1.5. CA Endevor software change manager Interface for Remote DB2 for z/OS (collectively “Endevor SCM”) 2. Implementation of Endevor SCM products/tools for promotion, migration and approval activities for all JCL, copybooks/includes, files, all mainframe source, and DB2 stored procedures. 3. Implementation will be hands on by DMV-IS, ET and DAS ETS staff with support from Contractor. 4. Configuration and documentation of all installed Endevor SCM tools/products. 5. Knowledge transfer, training, coaching, and support required to ensure that DMV-IS, ET and ETS staff achieves proficiency in understanding, use, and support for the products. 6. Modification of work processes and existing procedures to simplify and automate workflow (such as code promotion activities and approvals) 7. A 30 day Pilot will be conducted before expanded rollout for DMV-IS. 8. Migration of the current production modules into the respective CA code repository. Page 3 of 28 ATTACHMENT F – Scope of Services RFP #730-25400-12 9. The decommissioning of the LTS as defined by the Agency. 10. The decommissioning of CA Panvalet as defined by the Agency. 11. Expanded Rollout for all DMV-IS 12. Documentation of how to use the Endevor SCM products. 13. Documentation of all workflows, processes and procedures. 14. Documentation of process and standards for Application Development used by Tech Support Team. 15. Facilitate changes in roles and responsibilities to support the agreed upon Endevor SCM solution. 16. Training of administration staff. 17. Training of Application Development Staff. 18. Training of DP Coordinators. 19. Development of security rules for access and authorization of end users of each Endevor SCM product installed. 20. Audit and recovery/backup requirements for the complete lifecycle. 21. Testing of audit and recovery/backup requirements. 22. Scheduled status reports and project briefings. Out of Scope: 1. The conversion of unused, obsolete archived code (from all environments/platforms) is not part of this Project. 2. Integration with DMV Alexis. 3. Any services not identified in the SOW. A.2 Technical Environment DMV’s systems run on multiple platforms. The majority of DMV systems run on a mainframe and fewer are