Attachment F – Scope of Services

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 client/server and web systems. Endevor SCM must be able to execute within the current SDC hardware and software environments for the mainframe and servers, and Endevor SCM must be compatible with any future upgrades to these environments. A summary of DMV’s technical environments follows:

Mainframe: 1. DMV systems run on the SDC IBM 2097-504 z10 running 1675 MIPS which represents the entire State capacity 2. DMV runs on the z196 mainframe running z/OS 1.11 and JES2 on the ODOT LPAR which is one of three LPARS on the State mainframe 3. The majority of applications are written in COBOL (executing under LE), Assembler, and Easytrieve/Plus (embedded in JCL, and compiled) 4. CICS Transaction Server (release 3.1) hosts the online applications 5. Application code is stored in Panvalet and PDSE’s (Partioned Libraries) 6. Mainframe access is through TSO/ISPF and CICS services 7. Application development and maintenance is done through Panvalet on the mainframe 8. Library and compile services on the mainframe are presented via REXX and CLIST routines 9. Online applications use IBM mapping support (BMS) via 3270 green screen presentations 10. Primary data storage: IBM DB2 (Version 9.1), VSAM, and QSAM files 11. Developers utilize TSO/ISPF utilities and IBM File Manager to work with data 12. DB2 is accessed through IBM File Manager, DB2 mainframe utilities, CA Platinum 13. Testing and debugging products consist of IBM Debug and IBM Fault Analyzer for online and batch 14. Security is managed using RACF 15. Java source runs on UNIX Systems Services Hierarchical File System (UNIX/HFS) 16. IBM Application Performance Analyzer is used for performance monitoring 17. Stress testing is done using IBM Workload Simulator Page 4 of 28 ATTACHMENT F – Scope of Services RFP #730-25400-12 18. Data disguise is done using IBM Optim with Test Data Management 19. Printed forms and other specialized printing is done using PSF 20. Report archiving and viewing uses CA-View 21. JCLCHECK utility is used to check syntax on batch Job Control statements 22. CA-1 Tape Management System is used to manage tape volumes 23. Batch job scheduling is handled using CA-ESP 24. IBM Omegamon is used to monitor CICS 25. SIM2000 date simulation product is used to monitor CICS and DB2 26. MacKinney “Batch to CICS” is used to initiate CICS commands via batch jobs

Client/Server and Web: 1. Applications are written in Cold Fusion, JavaScript, Active Server Pages (ASP), Java, HTML, and MS Access 2. Applications use DB2 Connect to access DB2 on the mainframe 3. Application development and maintenance is done using Macromedia Dream Weaver, Websphere studio, SQL 2008 and Visual studio 4. Security vulnerabilities are detected by using IBM AppScan 5. Application migration is performed by RepliWeb R-1 as well as manually

Work Station: 1. Workstations currently are on the Microsoft XP Professional SP3 platform. ODOT’s strategy is to upgrade to Windows 7 over the next two years 2. Existing servers are typically on the Windows Server 2003 platform, with newly deployed servers being Windows Server 2008R2 3. Attachmate is used for 3270 terminal emulation 4. DB2 is accessed through a Windows based application called AQT via DB2 Connect 5. Utilize IBM CICS Explore (Eclipse based IDE) to access the mainframe and the IBM Developer Tools 6. Beyond Compare is used to compare different versions of source code

Constraints: Any changes to the SOW will impact both timeline and costs constraint. The accessibility of knowledgeable resources, both in-house and Contractor, is an inherent risk and possible constraint.

Page 5 of 28 ATTACHMENT F – Scope of Services RFP #730-25400-12

A.3 DMV Source Control Products and Processes

DMV SCM Products 1. Web products currently in use are Concurrent Versioning System (CVS) and Visual SourceSafe 2. Web Application migration is done using RepliWeb R-1 Console 3. Library Tracking System (LTS), an internally developed mainframe application is our current mainframe SCM system. This product is an ISPF Dialog/REXX based application that supports mainframe source migrations.

DMV SCM Environments, Procedures and Workflows 1. Environment regions and libraries (Appendix 1) 2. Environment chart (Appendix 2) 3. SCM coordinator Rules and Responsibilities (Appendix 3) 4. Migration Paths (Appendix 4) 5. Migration process flow for Projects (Appendix 5) 6. Migration process flow for Maintenance (Appendix 6) 7. Migration Procedures for ISPF Modules (Appendix 7) 8. Migration Procedures for JCL modules (Appendix 8) 9. Migration Procedures for EGOV applications (Appendix 9) 10. Migration Procedures for MS Access applications (Appendix 10) 11. Migration Procedures for Coldfusion applications (Appendix 11) 12. Application Source Component Counts (Appendix 12)

NOTE TO PROPOSERS: The above referenced appendices are not attached to the RFP or this Attachment F. If you want copies of the appendices, please email your request to [email protected] .

A.4 Overarching Approval Criteria for Contractor Deliverables Agency will approve all Deliverables delivered by Contractor to Agency, and the Endevor SCM as a whole, when the Agency verifies that the Deliverables conform to the specifications, functions and performance standards set forth in the Contract, including the SOW and all attachments. Approval will signify that the Agency has found that all approval criteria specified in the Contract, this SOW, and the Deliverable description are completed and free from error or defect that materially impairs their use or accuracy.

To obtain Approval of a completed Deliverable, Contractor shall provide a written statement describing the work or product provided. The information required on the written statement will vary by Deliverable and the information provided on statements is subject to Agency approval.

For Deliverable work that results in an Agency reviewed document, the document itself will be considered the written statement.

Statements describing completed Deliverable work or product may be submitted in an electronic format compatible with Microsoft Office 2003. If Contractor is required to use a specific Agency template, the template will be identified in the Deliverable description and will be provided to Contractor by the Agency.

The Contractor shall track all changes to Contractor Deliverables. Changes from a previous version must be clearly identifiable for Agency review of a Deliverable document.

The default days-durations listed below in the default review and approval processes may vary by Deliverable. These variances (if any) will be identified in the Task or Schedule, respectively. Page 6 of 28 ATTACHMENT F – Scope of Services RFP #730-25400-12

A. 4.1 Default Deliverable Review and Approval Process

Step 1: Contractor shall submit Deliverables to the Agency Project Manager. Step 2: The Agency Project Manager will coordinate the Review Process and return the compiled recommendations and edits to the Contractor within 10 days. If the Deliverable is “Accepted” with no recommended changes, skip to Step 6. Step 3: Contractor shall integrate Agency supplied comments and edits and resubmit Deliverables to the Agency Project Manager within 10 days. Step 4: The Agency Project Manager will coordinate the Agency verification that all comments and edits have been integrated or that any discrepancies or issues identified by the Contractor or Agency have been resolved within 10 days. Step 5: Steps 1 through 4 will repeat as necessary until the Deliverable meets Approval criteria or a Change Request has been submitted by Contractor and approved by Agency. Step 6: The Agency Project Manager will obtain written approval from the Agency Contract Administrator prior to notifying the Contractor about the Deliverable Acceptance. Step 7: When a Deliverable is Accepted, the Agency Project Manager will provide written verification to Contractor that the Deliverable has been Accepted and Approved.

A.5 Methodology and General Contractor Expectations

Agency IT Delivery Methodology – Agency’s Information Systems uses a system development methodology based upon Fujitsu Consulting’s Macroscope. Contractor shall use and model Deliverables based on Macroscope unless otherwise approved in writing by APM. Agency will provide Contractor with copies of related templates. Documentation Standards – Contractor shall create documents, unless otherwise approved in writing by APM, using standard Agency office automation products. Contractor shall use the provided templates as guidelines for Project Deliverables. The templates represent minimum information required for each Deliverable. Final Deliverable contents will be mutually agreed upon in writing between the Agency and Contractor. Change Control – Contractor shall use existing Agency issue and change management processes including standard formatted documents coordinated through established approval processes. Agency will provide sample forms, approval process and related information to implement change control. Reassessment – Contractor and Agency shall reassess Project scope, schedule, and Tasks after completion of functional and technical specifications (Tasks 1 to 3). Contractor shall draft and submit to Agency the updated Project Scope, schedule and Tasks that have been negotiated in conjunction with Task 4.

A 5.1 General Contractor Expectations:

Contractor commits to the Project to obtain the greatest long-term value for the State of Oregon, and which reflects the prudent expenditure of public funds within the constraints of the Project and budget. In pursuing this goal, Contractor commits to:

1. Provide implementation/validation, configuration, professional services, training, training manuals, training supplies, technical support, warranties, and other materials and services that are required to fully implement Endevor SCM as outlined in this document. Page 7 of 28 ATTACHMENT F – Scope of Services RFP #730-25400-12 2. In partnership with DMV-IS, conduct planning, analysis, construction/configuration, migration, conversion, testing, implementation, training and other activities required to fully and efficiently implement Endevor SCM. 3. In partnership with DMV-IS, manage project using project management methodology and IT governance to comply with state standards and procedures. 4. Ensure compatibility with DMV systems and technical infrastructure. 5. Support all development, test, and production platforms to meet the requirements specified. 6. Develop a schedule that is appropriate for the context of the Project.

A.6 DELIVERY AND ACCEPTANCE OF DELIVERABLES Contractor shall deliver the Deliverables no later than the date or dates established as part of Task 1. If Agency determines that any Deliverables are not acceptable and that any deficiencies are the responsibility of the Contractor, Agency may utilize remedies in accordance with the Contract.

If the Agency determines that a Deliverable does not meet the specifications or performance standards, Agency shall notify Contractor in writing of Agency’s rejection of the Deliverable, and describe in reasonable detail in such notice the Agency’s basis for rejection of the Deliverable. Upon receipt of notice of non-acceptance, Contractor shall modify or improve the Deliverable at Contractor’s sole expense to ensure that the Deliverable meets such specifications or performance standards, and notify the Agency in writing that it has completed such modifications or improvements and re-tender the Deliverable to Agency. Agency shall thereafter review the modified or improved Deliverable. Failure of the Deliverable to meet the specifications and performance standards after the second set of acceptance tests shall constitute a default by Contractor. Upon such default, Agency may either (i) notify Contractor of such default and instruct Contractor to modify or improve the Deliverables as set forth in this section, or (ii) notify Contractor of such default and instruct Contractor to cease work on the Deliverable, in which case Contractor shall refund to Agency all amounts paid by Agency related to such Deliverable. Such refund shall be in addition to, and not in lieu of, any other remedies Agency may have for Contractor’s default.

A.6.1 Final Acceptance. “Final Acceptance” will occur when, in the Agency’s sole determination, Contractor has met all the requirements of Task 9.

A.6.2 Warranty Period. During the Warranty Period, Contractor will, at no charge to Agency, furnish such materials and services as shall be necessary to correct any defects in any of the Endevor SCM products or configurations implemented and maintain the products in good working order in accordance with the warranties and requirements provided in the Contract.

A.7 Project Phasing, Approach and Milestones: In the event the Agency determines it would be in the best interest of the State to conduct additional phases to the software purchase and implementation, the Agency may, at its sole discretion, draft an amendment to the Contract to provide for a phased approach, add services and to purchase and install additional software packages within the total SCM solution.

Additionally, Agency may, at its sole discretion, draft an amendment to the Contract to purchase annual support and maintenance for the software implemented under the Contract, including adding funds and for a term of years to be negotiated.

A.7.1 Project Approach:

1. Endevor SCM will be implemented and configured on site as an “Out of the Box” setup by the Contractor.

Page 8 of 28 ATTACHMENT F – Scope of Services RFP #730-25400-12 2. Contractor shall give a DEMO of each of the Endevor SCM products/tools and note changes for configurations. The Agency project team will review and assess what features and capabilities are present with each of the Endevor SCM products. 3. Once this basic understanding has been delivered, Contractor and Agency will conduct 2 to 3 JAD sessions to produce a refined functional specification document, technical specification document and work flow processes. These documents will be used to configure Endevor SCM. 4. Contractor shall guide the DMV-IS, DMV-IS Help Desk, ET and DAS ETS staff on the entire implementation and configuration process. Agency will implement and configure Endevor SCM (based on Contractor’s review of Agency’s requirements and JAD sessions) into the development environments. 5. Contractor shall guide Agency support staff through the entire solution confirmation and proof of concept process. This process will cover testing, issue resolution and pilot setup of the mainframe systems based products in the development environments. 6. Upon successful completion of all testing and issue resolution in the development environments, a 30-day pilot will be conducted. 7. At the conclusion and acceptance of the 30 day pilot*** the products will be migrated to the production environment. 8. A 30 day (Severity-1 and Serverity-2 free) Warranty Period for the production environment will begin as well as the Project closure process.

***An option for focusing on a single application for the pilot will be addressed during the initial JAD sessions.

A.7.2 Project Key milestones:

1. Project kick-off 2. Demo of products 3. Scope of work approved 4. Functional Specification and workflow processes approved 5. Mainframe implementation on ODOT’s production LPAR (DMV-only) 6. Configuration of mainframe tools 7. Approval of configurations 8. Training of Pilot Group 9. Pilot 10. Acceptance of Pilot 11. Training (DP Coordinators & Application Staff) 12. Training of support staff 13. Roll-out (Production) 14. Warranty 15. Project closure

B. RESPONSIBILITIES AND FORMAT REQUIREMENTS

B.1 Agency Responsibilities 1. APM will be responsible for scheduling meetings, scoping trips, and work sessions with internal Agency staff. Page 9 of 28 ATTACHMENT F – Scope of Services RFP #730-25400-12 2. APM will ensure compliance with ODOT (DMV-IS) Project Methodologies. 3. Agency will define Project approach/overview and Agency contact personnel information to Contractor once the Notice to Proceed (NTP) date has been determined. 4. Agency staff will provide review comments to Contractor within 10 business days of receipt of review Deliverable documents. 5. Agency will provide DMV Subject Matter Experts for the Project. 6. Agency will provide migration requirements. 7. Agency will provide network requirements. 8. Agency will provide security requirements. 9. Agency will provide appropriate staff for training. 10. Agency will consolidate all review comments from Agency staff and provide one (1) set of review comments per Deliverable to the Contractor. 11. Agency will resolve conflicting review comments made by Agency staff prior to providing comments to Contractor. 12. Office Space: Work will be primarily performed at Contractor’s offices and on-site at DMV HQ, Salem, OR. If requested by Contractor, Agency will provide office space, desk, and chair, phone, and Agency security badges, at an Agency facility in the Salem area for Contractor staff. 13. PC and Related Equipment: If requested by Contractor, Agency will provide an available workstation that can access the Agency network. 14. Agency will not allow access to ODOT’s network using non-ODOT computers. 15. Agency prefers not to grant remote access to ODOT’s network.

B.2 Contractor Responsibilities 1. Contractor in cooperation with Agency shall coordinate and schedule meetings, scoping trips, and work sessions with APM. 2. Contractor shall submit all Deliverables to APM or designee unless otherwise noted in specific Tasks. 3. Contractor shall process documents that are to be submitted to Agency through Contractor’s internal Quality Control (QC) process prior to submittal. Contractor shall provide one (1) iteration of the documents as a result of the QC process to the APM. 4. Contractor shall coordinate with Agency staff as necessary to revise draft Deliverables to incorporate Agency draft review comments into a single set of consolidated draft review documents. 5. Contractor shall incorporate comments within 10 business days from receipt by Agency and return the Final Deliverable to Agency staff for review and Acceptance, unless a different timeframe is specified for specific Tasks or otherwise agreed to in writing by Agency. 6. Contractor shall create a scheduled plan to complete implementation, configuration, testing and on-site training for review and approval. 7. Contractor shall create a scheduled plan to complete all required documentation and submit for review and approval. 8. Contractor shall submit weekly status reports on DMV’s required schedule per Activity 1.4. 9. Contractor shall conduct planning, analysis, construction/configuration, migration, conversion, testing, implementation, and other activities required to fully and efficiently implement. 10. Contractor shall identify the level of effort to estimate resources (DMV-IS, ET, DAS ETS, DMV- IS Help Desk, DMV DP Coordinators) required (technical and other) for the duration of the Project. 11. Contractor shall coordinate the implementation and configuration of Endevor SCM by DAS ETS, ET, DMV-IS Help Desk and development staff. 12. Contractor shall provide in-depth guidance of required implementation and configuration steps, equipment, features, and components. Page 10 of 28 ATTACHMENT F – Scope of Services RFP #730-25400-12 13. Contractor shall use agreed upon project management methodology and IT governance to comply with state standards and procedures. 14. Contractor shall document workflow processes for each tool and environment for ongoing support. 15. Contractor shall document the tools, processes and procedures relevant for each environment and Agency support (DMV-IS, ET, DAS ETS). 16. Contractor shall conduct analysis and other activities required to fully understand and document reporting needs. 17. Contractor shall provide on-site training to all designated DMV-IS staff, DMV-IS Help Desk staff, ODOT IS staff (includes Enterprise Technology (ET)) and DAS ETS technical staff. 18. Contractor shall provide all training materials, manuals and system user guides. (1 electronic and 10 printed for each document). 19. Contractor shall provide written System recovery process to include application software, database and operating system, back-up process, and archiving systems. 20. Contractor shall provide written Technical requirements of operating system, hardware, and firmware. 21. Contractor shall provide assistance in installation of any Patches, system upgrades and technical support during the implementation. 22. Contractor shall provide Warranty Period of 30 consecutive days free of Severity-1 and Severity-2 issues for the Production Environment. 23. Contractor shall provide issue resolution requirements of Severity-1 through 3 level issues: 23.1. Severity-1 is highest severity and requires immediate attention until resolved; no workaround is available. 23.2. Severity-2 has a workaround available; but must be fixed before 30 day warranty countdown starts again. 23.3. If a Severity-1 or Severity-2 issue occurs the 30 day warranty period starts over (post fix) 23.4. Severity-3 is an issue that is cosmetic in nature and should be fixed by the end of the project. 23.5. Severity-4 issues are errors in the documentation. Contractor will resolve these problems with the next release of the program documentation. 24. Contractor shall provide the first document of each document type as a draft for review and approval. 25. Contractor shall submit all deliverables to the APM or designee unless otherwise noted in specific tasks.

B.3 Format Requirements 1. Draft Deliverables shall be submitted in editable electronic Portable Document Format (PDF) format, Word (DOC) or other electronic format as required by the SOW via e-mail or other agreed upon method (and hard copy if required by specific Task), if draft Deliverables are required in the specific Task. 2. Graphic files accompanying reports shall be submitted separately in .jpg or .tif formats. 3. Final text-based or spreadsheet-based Deliverables shall be submitted in .pdf and Microsoft Office file format (e.g. MS Word, Excel, and PowerPoint). The file format shall be fully compatible with the version used by Agency unless a different format is required in the specific Task. 4. Transmittals must include, as applicable, the Contract # and Project name. 5. Additional format requirements may be listed with each specific task through out the project.

C. TASKS AND ACTIVITIES: Unless the Contract is terminated or suspended, Contractor shall complete all Tasks and provide all Deliverables (collectively, the “Services”) and perform the Services in accordance with the performance requirements and delivery schedules as indicated and specifically stipulated in the Contract.

Page 11 of 28 ATTACHMENT F – Scope of Services RFP #730-25400-12 Contractor shall perform the following Tasks and provide the following Deliverables to the APM or designee. Contractor shall provide copies of all final Deliverables to the APM or designee. Notwithstanding Agency's approval of subcontractors with respect to particular Tasks within the Contract, the Contractor shall be responsible as the prime Contractor for completing all Tasks and providing all Deliverables unless specifically identified as an Agency responsibility. Agency will provide Notice to Proceed(s) (NTP) via email after execution of the Contract. Contractor is not authorized to begin work on any project until receipt of the NTP (e-mail acceptable).

TASK 1: PLANNING AND ADMINISTRATION Contractor shall perform the following activities to ensure that adequate planning and project management are performed for this Project. Contractor shall provide the Project oversight and internal day–to-day coordination and management of the Contractor team. Contractor shall provide administrative support for assigning and scheduling work, monitoring progress, and managing change. Contractor shall develop and maintain a Project Plan as described in Activities below.

Activity 1.1: Develop a Detailed Project Plan and Schedule Contractor, in cooperation with Agency shall develop a draft detailed Project plan and schedule (using MS Project). It is anticipated that this project will have a 6 to 9 month time line. The Project plan and schedule must include fixed delivery dates for the remaining Deliverables. All Deliverables must be completed by the Contractor and accepted by Agency. The Deliverable due dates will be mutually agreed upon during the initial Project meeting and revised during Agency approval of final Project plan and schedule. Contractor shall incorporate Agency’s comments and submit a final Project Plan to APM for approval. The Project plan and schedule must include, but are not limited to: a. Project schedule including Tasks and activities, Deliverables, location of Task and activities, activity duration, resources, sequencing and dependencies b. Project work plan for each Deliverable, including a work breakdown structure c. Completion date for each Task and Deliverable d. Project milestones e. Entrance and exit criteria for specific project phases f. Project organization including a resource plan that defines roles and responsibilities for the Contractor and Agency resources

Deliverables: 1. Detailed Project Management Plan including project plan, resource plan and schedule. The Plan and Schedule must include the above bulleted items included in Activity 1.1. The Project Plan requires MS Project 2007. Updated project plan once a month on the last day of the month. 2. Resource Plan.

Activity 1.2: Develop a Detailed Activities Plan Contractor shall develop a draft detailed activities plan, which includes, but is not limited to, the following Project areas:

a. Communications Plan: Contractor shall identify how communications will be managed between the Contractor and Agency project team members and other stakeholders and governance Page 12 of 28 ATTACHMENT F – Scope of Services RFP #730-25400-12 committees. This activity shall include development of a communication plan which identifies the roles and responsibilities of key stakeholders, including the decision making framework to define and streamline the review process. Identify activities which need to be completed with team members and stakeholders in order to prepare them for the implementation of the SCM solution. Contractor shall detail the activities, resources, recommended timeframes for completion and any special requirements from either Agency or Contractor to ensure the success of the communication activity. All communication plan activities must be reflected in the project schedule, including all Tasks, activities, activity duration, sequencing and dependencies.

b. Risk Management Plan: Contractor shall identify risks and mitigation plans for each Task to ensure that risks are effectively identified, planned for, analyzed, communicated and acted upon. The plan must include a preliminary list of risks that the Contractor has identified, along with the probability of each risk's occurrence, the potential impact to the project if each risk occurs, and a response strategy for each risk.

c. Quality Control Management Plan: Prepare a QC Plan, QC checklist and Plan Review specific to the Project for maintaining quality of the product as changes are made to facilitate the SCM solution implementation. The methodology shall be based upon the Contractor’s Quality Control Plan and include description of quality assurance measures taken to verify compliance as identified below:

I. The QC Plan must include: 1. A definition of the QC procedures to ensure that the design provided is consistent with the intent of the Project and meets all applicable standards. 2. The name of Contractor’s QC manager and reviewers assigned to the Project and a resume for the QC manager and for each person identified as a QC reviewer. 3. A list of all Deliverables included in this document to include the name of the expected reviewer, anticipated QC data, and submittal date. 4. A sample Plan Review Comment Log.

II. The QC Checklist must include, but is not limited to the following: 1. Name of reviewer 2. Delivery date and QC date 3. Description of Deliverable 4. Checklist of items to review 5. Signature box initialed by reviewer

III. The QC Review must consist of: 1. Reviewing all work product and Deliverables for technical and editorial quality. Work products must be clearly written in a professional style and must be consistent in level of analysis, tone, format, and terminology (e.g., abbreviations and names of site features, facilities, geographic features, technologies, etc. will be consistent). 2. Providing both a technical and an editorial review of all work products by qualified staff. 3. Conducting a final review on all work products before delivery. 4. Providing Agency with a written record of the work product QC review process that includes names of all reviewers and dates of their reviews.

d. Change Control: Contractor shall establish and utilize specifications for any change control procedures to be used during the Project.

e. Project Filing System: Establish and develop filing system for all Project related documents, supporting reports and data. Contractor shall maintain files specific to the Project that include all Page 13 of 28 ATTACHMENT F – Scope of Services RFP #730-25400-12 writings, documentation and data resulting from or related to Contractor’s Services under the Contract, including but not limited to: meeting minutes, correspondence, memos, and transmittals. Contractor shall compile and maintain the project files commencing upon receipt of Agency’s first NTP to Contractor, incorporating writings, documentation and data as generated, and continuing through completion and acceptance of the Services, including required Deliverables. Contractor shall make all files specific to the Project available for Agency’s review. Contractor shall submit all files specific to the Project to the APM by the earlier of thirty (30) calendar days following Agency’s request or thirty (30) calendar days following Contractor’s completion of, and Agency’s acceptance of, all Services and Deliverables required under the Contract.

Deliverables: 1. Detailed Activities Plan a. Communications Plan for the duration of the Endevor SCM project. b. Risk Management Plan for the duration of the Endevor SCM project. c. Quality Control Management Plan for the duration of the Endevor SCM project. d. Change Control Plan for the duration of the Endevor SCM project. 2. Project Filing System for the duration of the Endevor SCM project.

Activity 1.3: Project Coordination Meetings Contractor in cooperation with the Agency shall participate in the Project coordination meetings to review and coordinate the Project, to review and coordinate Project status and quality control processes under the Contract with APM, and others as Agency deems necessary, at the times and locations as agreed upon or identified in the Contract. Contractor shall cause Contractor’s key personnel to attend meetings scheduled by Agency. Contractor shall provide input into the meeting agenda for each of the following meetings by email to APM at least three (3) business days prior to the meeting. Agency shall create meeting notes for each meeting and submit them by email to Contractor no later than ten (10) business days after the meeting. Discussion between the APM and CPM may result in cancellation of a scheduled meeting. The Project coordination meeting(s) may include, but are not limited to the following:

1.3.1 Kick-off Meeting Contractor shall prepare for and participate with Agency at the Project kick-off meeting. The purpose of this meeting is to introduce team members to one another, clarify team member roles, review Project scope and objectives, review the overall draft detailed Project plan, and confirm understanding of detailed plans for next steps. Create PowerPoint presentation, input for Agenda and present other documents as required.

1.3.2 Semi-Monthly or Monthly Status Meetings Contractor shall prepare for and participate in the Agency’s Project status meetings with Agency project team at a location to be determined by Agency. Attendance may be in person or via teleconferencing, as determined by Agency. These meetings will follow an agenda developed by the Agency.

1.3.3 Other Project Related Meeting(s), as identified and determined by Agency Contractor shall attend and participate in all Project related meetings, as requested by Agency. Contractor shall prepare materials or briefings for these meetings as requested by Agency. Location of the meeting(s) will be determined by the Agency.

Page 14 of 28 ATTACHMENT F – Scope of Services RFP #730-25400-12 1.3.4 External Quality Assurance (QA) Review Contractor shall participate in the Agency’s external QA review process as determined by the Agency. Contractor in cooperation with Agency will develop responses and action plans to QA findings.

Deliverables: 1. Project Meetings and QA a. Prepare presentation materials (as described in 1.3.1) and conduct Kick-Off Meeting. b. Attend project Status meetings. c. Attend other project related meetings as requested. 2. Participate in external QA reviews.

Activity 1.4: Written Weekly Project Status Reports Contractor shall draft and submit written weekly project status report(s) (P050) to APM unless a different delivery schedule is stipulated in the Contract. Progress reports must include, but not be limited to, the following: a. Status of Contractor’s Services required under the Contract by Activity breakdown and percent complete b. Changes and reason for change in Project’s scope, schedule or budget c. Description of unanticipated problems encountered and their proposed and actual resolutions d. Summary of Tasks and activities to be accomplished during the next reporting period e. All issues that need to be addressed f. Quality Control status g. Updated MS Project time line showing percentage completed, Tasks assigned, completed and remaining h. Identification and description of all issues i.e. potential schedule slippage and proposed changes and strategy for resolution that may delay the delivery schedule. Schedule changes must be approved by APM. i. Contractor Key Personnel or other staff assigned and their location/schedule j. Agency and other State resources required for activities during the next time period k. Resource allocation percentages including planned versus actual by Project Task

Deliverables: 1. Weekly status report to include tasks completed, new and out standing issues, identified risks, tasks that are behind schedule and work effort for next reporting period in writing. Status report must be reported on the P050 template unless another agreement is made. All bulleted items above are required for reporting each week.

Activity 1.5: Monthly Invoice Contractor shall provide and submit a monthly invoice with copies of the weekly status report(s) to the Agency for services rendered and identified in the Contract for the Project.

Deliverables: 1. Provide a timely invoice per the contract schedule. Status report must be included for services rendered per the project contract.

Page 15 of 28 ATTACHMENT F – Scope of Services RFP #730-25400-12 TASK 2: DEMONSTRATION OF ENDEVOR PRODUCTS Contractor shall give a full demonstration of each Endevor product to be implemented for the Agency. The full functionality, features and capabilities of each of the Endevor products to be implemented must be presented.

Activity 2.1: Develop a Demonstration that will feature each of the Endevor products Contractor shall develop a demonstration for Agency that will give an in-depth understanding of the Endevor SCM products that will be installed and configured. This demonstration must highlight the features and capabilities of the Endevor products, including: a. Provide a detailed overview of products b. Demonstrate the configuration options c. Demonstrate the impact of changes d. Demonstrate the Recovery and Back-out processes e. Demonstrate security features f. Create reports g. Highlight the features and capabilities of each product

Deliverables: 1. A demonstration with an in-depth understanding of each of the Endevor products to be implemented at the Agency. Each area bulleted above must be included. 2. Provide Overview materials.

Page 16 of 28 ATTACHMENT F – Scope of Services RFP #730-25400-12

TASK 3: FUNCTIONAL AND TECHNICAL REQUIREMENTS Contractor shall document the SCM solution implementation requirements, configuration, security authorizations, modifications, and process changes. The activities to retire the existing systems (where applicable), their products, and utilities will be included in order to complete the Project. Contractor shall provide the following activities: Activity 3.1: Functional and Technical Specifications Contractor shall conduct working sessions in cooperation with Agency to jointly review and clarify the scope, objectives and functional requirements for the SCM solution. Contractor shall be on site (at DMV- IS designated site) for these working sessions in order to review, document and discuss Agency requirements, and must demonstrate how the software functions can be configured to meet Agency’s needs. The working sessions must include the review of existing process flowcharts, product workflow, DMV workflow and business rules associated with the implementation of the SCM solution. Contractor shall recommend (with Agency approval) the most effective way to operate during planning, analysis, and SCM solution implementation before the solution is moved to a pilot or production state. The new workflows and processes must recommend and identify best practices and consider future modernization. The goal is to continue to operate simultaneously using both the existing products and procedures and the new solution in order to ensure a smooth transition and minimize business and operational disruptions.

Contractor shall document an understanding of the AS-IS Agency technical environment and products used to manage source on State platforms that are utilized by ODOT. Contractor shall describe in writing any differences between Agency requirements and the Contractor’s SCM solution which includes, but is not limited to: a. Hardware/Software prerequisites (if any), understanding that the product must run on the technology platform defined in Section A.2, Technical Environment. b. Implementation Requirements c. Configuration requirements d. Conversion requirements for all programs, libraries, databases, utilities, and any other components or processes that may be impacted e. Database set-up requirements f. Process changes required by Agency in order to utilize Endevor SCM g. Changes in roles and responsibilities and a description of what and how they should change and any related transition activities h. Identify activities and methods to retire the Agency’s current systems and utilities that must be replaced by the Endevor SCM i. Verify hardware is accessible and operational as required (includes desktops) j. Ensure system readiness, such as checking port assignments and other security/logistical details k. Review the software assets that are to be uploaded. Provide guidance for “scrubbing” and migration/upload readiness. l. Focus on creation, review, and approval of the design of the solution m. Provide documentation addressing configuration, reporting, and data migration and mapping. Analyze current testing environments and paths to production.

Page 17 of 28 ATTACHMENT F – Scope of Services RFP #730-25400-12 Since Endevor SCM will replace existing systems, procedures, and work processes, the Contractor shall recommend the course of action to implement Endevor SCM that supports Agency’s multiple platforms and successfully integrates and supports all Agency systems. Contractor shall develop new processes and procedures which must support all transition activities including creation of written documentation, proposing work process changes and configuring Endevor SCM to support workflow processes. Contractor shall train Agency’s Information Systems, DMV-IS Managers and other stakeholders on responsibilities and use of Endevor SCM to fulfill those responsibilities. Contractor shall recommend the testing/training necessary and environments required to implement Endevor SCM. Contractor’s determination must include the identification of any additional pieces of hardware or software that will need to be acquired by Agency in order for Endevor SCM to be fully implemented. Contractor shall document all issues that are identified through the working sessions as well as all agreements/resolutions reached between the Contractor and Agency. Deliverables: 1. Functional and Technical Specifications documents, including: a. Data Conversion Strategy. b. Identification and documentation of any additional hardware or software required. c. Identify and document changes in procedures and roles/responsibilities. d. Document method and activities to retire the current systems and utilities.

Activity 3.2: Create a System Solution Configuration Plan Contractor shall develop an Endevor SCM configuration plan and present the plan to Agency. The plan must be presented in Contractor-facilitated working sessions that enable the joint revision, scheduling and acceptance of the plan. Contractor shall document the Tasks required to implement the Endevor SCM to satisfy the Agency requirements. Upon completing all the Tasks in the plan, Endevor SCM must be ready for integration testing and user acceptance testing. The plan must cover, at a minimum, the following: a. Description of current system features/components and infrastructure/environments to be modified or configured b. Description of future workflows and work processes (including Diagrams) c. Description of system implementation requirements and configuration activities d. Description of application implementation requirements and configuration activities e. Location (environment/region) where modification/configuration must occur f. Document detailed configuration requirements g. Process for Application Development as used by the Tech Support Team h. Schedule for modification/configuration activities i. Implementation requirements for all in-scope Endevor SCM software j. Identify the Number / Size of Conversion Artifacts (Jobs, Reports, Exits, Data) k. Determine the names and locations of the applications to be converted l. Identify the security requirements for the test, pilot and production applications m. Address any application specifics for: o Application Life Cycles o Library Structure o Naming Conventions o Security Implementation Strategy n. Any Maintenance procedures o. Any back-out and recovery procedures

Page 18 of 28 ATTACHMENT F – Scope of Services RFP #730-25400-12 Deliverables: 1. System Solution Configuration Plan, including: a. The Solution Architecture Models - Including Solution components and component interface specifications b. The Physical Architecture Models – Provide diagrams, system specifications and configurations mapping current functions and procedures (AS IS) to the proposed solution (To Be). One for each environment. c. The Validation Approach - Providing a high level description of how the Solution’s requirements and configuration will be validated with a set of walkthroughs to be performed based on use cases d. Solution Phasing - Describe the sequence of phases to roll out the Solution and the high level integration plan e. Migration Strategy – Describes the data migration to the CA Endevor products f. Solution Constraints – Describe design and technical constraints and the impact the solution will have on personnel, processes (including any policies) and technology g. Resource Plan requirements for each phase of the project

Activity 3.3: Create a SCM Conversion Strategy and Plan Contractor shall develop a conversion strategy which describes the overall conversion approach including any limitations and restrictions that affect the conversion as well as any testing activities to verify the correctness of the conversion. Contractor shall also develop a conversion plan which identifies all detailed activities necessary for completing the conversion.

The Conversion plans must include: a. The Solution Architecture Models including Solution components and component interface specifications b. All environments (including verification of accessibility) c. Configuration tasks per the solution design are confirmed d. A complete test plan e. Step by step instructions to validate the solution (including data) with a set of walkthroughs to be performed based on use cases f. Verification of the conversion/migration g. The non-functional requirements h. Verification of any external interfaces i. The defined systems, subsystems, types and processor groups j. All necessary processes k. Development of any DB2 processes l. Documentation of any manual tasks m. Define how comparison to current LTS/Panvalet will be done n. Identification of exceptions o. Remediation of exceptions p. A time table for conversion q Identify the anticipated number of conversion cycles to execute r. A review all components and fine tune conversion strategy (verify all configurations and security) s. Update documents/instructions as necessary t. Identify Agency tasks and resource requirements

Deliverables: 1. Conversion Strategy Plan. Page 19 of 28 ATTACHMENT F – Scope of Services RFP #730-25400-12

TASK 4: GOVERNANCE CHECK

Activity 4.1: Governance Check Contractor shall refine the Project Plan and schedule to reset the baseline for the Project. Contractor shall create a Business Release Review document which may include revising the training plan, if necessary. Upon receipt of Agency comments, Contractor shall revise the Project plan and schedule and submit the final Project plan and schedule to APM for approval. Contractor shall perform the following activities:

a. Define the training requirements and plan for end-users, identify the critical Tasks that must be completed before go-live, revise project plan based upon the requirements, business releases, and progress to date on the Project

b. Revise the Project plan schedule based on information from previous Tasks.

Deliverables: 1. Revised Project Plan and schedule. 2. Business Release Review document (Observations, Findings, and Recommendations). 3. Training Requirements and Plan.

TASK 5: PRODUCT IMPLEMENTATION AND CONFIGURATION Agency will install and configure the software in the ODOT LPAR specifically for the State’s environments. Contractor shall assist Agency with the implementation and configuration, to ensure compatibility with the State’s systems. Contractor shall confirm the designed technical architecture will support all development and production environments on the State’s mainframe (only on the ODOT LPAR).

Activity 5.1: Implementation Activities Contractor shall be on-site as needed to provide support services during the implementation of the Endevor SCM tools. Contractor shall provide written instruction, oversight, and mentoring for Agency and ETS staff involved in implementation activities to ensure a complete, accurate, and supportable Endevor SCM installation. Implementation activities must tie to the Functional and Technical Specifications.

Agency will install the Endevor SCM products cited below: a. The Mainframe implementation of CA Endevor 15.0 for DMV and any updates or patches b. CA Endevor SCM Quick Edit c. CA Change Manager Enterprise Workbench (1 Server) d. CA Endevor Software Change Manager Parallel Development e. CA Endevor software change manager Interface for Remote DB2 for z/OS

Deliverables: 1. Written implementation instructions for each Endevor SCM product. a. Provide the written instructions at least 2 weeks prior to arrival.

Page 20 of 28 ATTACHMENT F – Scope of Services RFP #730-25400-12 Activity 5.2: Configure Endevor SCM Contractor shall provide support services during configuration of the Endevor SCM solution according to the specifications agreed upon with Agency, on site as needed, as detailed in the Functional and Technical Specification and the System Configuration Plan Deliverables Tasks. ETS and ET will perform the actual system and application level configuration activities for the Endevor SCM solution with guidance from the Contractor. For each CA Endevor product listed in 5.1 above (both development and production environments), Contractor shall work with Agency to: a. Validate successful down load and install of all CA Endevor files b. Validate configuration and integration tasks per the accepted solution design c. Validate access and security levels d. Validate any conversion tasks (both system and manual) e. Validate Quality Assurance check f. Validate the full system install and configuration g. Document any changes and update Documentation

Deliverables: 1. Written configuration instructions for each Endevor SCM product, including: a. Work with Agency staff to create and refine authority permissions for the Endevor SCM products. b. Test and refine the Endevor SCM tools to insure the configuration is accurate. c. Conduct knowledge transfer for administrators of each Endevor SCM product. 2. Participate in a Technical acceptance of systems (implementation & configuration) and applications for Agency sign-off.

Activity 5.3: Implement Conversion Plan Contractor shall be on-site to support the conversion activities for a pilot application for Endevor SCM during the conversion and implementation. Contractor shall work with Agency to assist re-configuration of Agency’s existing build scripts.

For Conversion of Panvalet data, LTS and mainframe, Agency will perform the following with the Contractor’s assistance: o Execute conversion plan created in Task 3.3 o Run conversion utilities o Validate conversion o Validate security access

Deliverables: 1. Contractor shall support Agency’s implementation of the Conversion Plan, including: a. Validation of conversion document(s). b. Validation of security access document(s).

Activity 5.4: Demonstrate Configured Endevor SCM Contractor shall plan and conduct walk-through demonstrations of the fully configured Endevor SCM solution to confirm the solution completely fulfills all requirements, functionality, workflow, processes and other components approved in Task 3, Functional and Technical Requirements. The demonstrations Page 21 of 28 ATTACHMENT F – Scope of Services RFP #730-25400-12 will occur in Agency’s environments. If corrections are required, Contractor shall instruct the Agency in how to make the requested corrections (including documentation) and conduct additional demonstrations (not to exceed a total of five) at no additional expense until Agency approves Endevor SCM to be ready to enter Acceptance Testing. Deliverables: 1. Successful demonstration of the fully configured Endevor products including: a. Repeat demonstration, if necessary. b. Updates to documentation and configuration materials (if needed).

TASK 6: ACCEPTANCE TESTING Contractor shall fully exercise Endevor SCM through various scenarios and take corrective action as needed to ensure that the system satisfies all required functionality and requirements. Contractor shall train an initial (pilot) team of Agency testers to prepare for pilot acceptance test activities.

Activity 6.1: Provide Pilot Test Plan and Scripts Agency will conduct Acceptance Testing. Contractor shall recommend a robust test plan and corresponding test scripts, which must enable Agency to test the entire Endevor SCM solution. Testing must be done in environments established by Agency that simulates a production environment. Testing must exercise all functions of a fully implemented Endevor SCM solution and must exercise all Agency required functionality and processes. Contractor shall provide Agency with a detailed report for defect tracking. The Pilot Acceptance Test Plan must include, but is not limited to: a. Procedures for conducting Acceptance Testing (AT) b. Procedures for documenting results c. Procedures for reporting defects to the Contractor d. Method by which Pilot AT training must be conducted with each user group (i.e., System Administrators, Developers, Manager/Approvers, Business Analyst/Testers) e. Copies of AT training materials by pilot group f. Copies of procedures and other documentation that must be used as part of Pilot AT to capture results and defects g. A description of the problem reporting and resolution process including estimated time to resolve issues based on problem type and severity h. Metrics for measuring effectiveness of overall training in order to make improvements in training materials prior to delivery of end user training

Deliverables: 1. Detailed step-by-step Test Plans and Test Scripts, including: a. Written procedures/scripts for testing b. Training Materials c. Training Metrics d. Problem Reporting Template

Activity 6.2: Pilot Acceptance Test Training Contractor shall provide on site training to Agency designated Pilot Users prior to beginning AT. The Pilot AT training must include, but is not limited to: use of the application(s) to exercise all features to Page 22 of 28 ATTACHMENT F – Scope of Services RFP #730-25400-12 control source code; support parallel development activities; support test activities; support electronic approvals; and to perform code migrations based on rules established in the approved requirements document. Agency will provide the location for the training and identify the number of Pilot Users to the Contractor prior to the start of the training. Pilot User groups include, but are not limited to:

a. Mainframe Programmers/Analysts c. Release Management Analysts d. Application Development Managers e. Operations & Production Managers f. Business Analysts/Testers g. Librarians h. System Administrators i. Database Administrators

Deliverables: 1. On site training for each identified pilot group. 2. Update manuals and training material as identified during the training.

Activity 6.3: On-Site Support with Pilot Acceptance Testing Contractor shall provide on-site involvement and support services to Agency during the Pilot Acceptance Testing performed by Agency’s Technical Staff, Agency IS Managers, Agency Team Leads, Agency Business Users and DP Coordinators. Testing will be done in an iterative fashion, performing as much testing as possible between revisions and then repeating the preparation and testing as needed until all results are satisfactory to Agency. All issues and defects will be tracked for resolution. Contractor shall monitor the Systems operations for a minimum of 14 business days during the pilot acceptance testing. Agency may increase the number of days for this Task based on the following acceptance criteria:

a. All Systems and applications must be stable for 14 business days during the pilot acceptance testing. For these criteria “stable” means without any reported Severity 1 or Severity 2 issues.

b. If a Severity 1 or Severity 2 issue is detected, Contractor shall: o Provide the solution to fix the identified issue o Assist Agency with implementation of the identified solution o After the solution is implemented, the System must be stable for 14 business days with no open or reported Severity 1 or Severity 2 issues. In the event Endevor SCM solution requires any revisions or changes, or require corrective action to ensure Endevor SCM solution is fully functional and production ready, the Contractor shall, at no additional charge, outline all necessary changes, configurations and adjustments until Pilot AT is passed or rejected. Agency will provide Approval/Signoff to move to the production environment, if passed, pursuant to Section A.6.

Deliverables: 1. On site support during Pilot Acceptance Testing, including: a. Document Test results. b. Tracking document for defects and issues. c. Update manuals and procedures as necessary. Page 23 of 28 ATTACHMENT F – Scope of Services RFP #730-25400-12 d. Outline any necessary changes, configurations, and adjustments. e. Provide solution(s) to fix all the Severity 1 and Severity 2 issues. f. Meet acceptance criteria. 2. Provide Lessons Learned.

TASK 7: TRAINING Contractor shall provide Agency resources with the necessary training and materials to effectively utilize, maintain and support Endevor SCM. All training courses and materials must be oriented towards user groups or roles determined by Agency and include training on all Endevor SCM functions that a given user group or role will need to know to successfully perform its duties. All training provided by the Contractor shall be conducted on-site at Agency training facilities and must be hands-on training to include up to 50 individuals. (25 programmers, 10 Tech Support staff, 6 DP Coordinators, 4 System Administrators, 5 Managers/Approvers/Testers). Final groups to be determined by Agency after implementation, configuration and Pilot AT.

Activity 7.1: Provide a Training Plan and Schedule Contractor shall develop a draft training plan and schedule to deliver training sessions and submit to APM during the kick-off meeting identified in Task 1. Contractor shall draft a template for feedback on training classes and submit to APM for approval. Contractor is responsible for training the Agency’s current staff, and identified ETS staff, and ET staff on Endevor SCM tools. Contractor shall provide recommendation on the roles and responsibilities. Agency will determine who will attend the end user training sessions. Contractor’s training plan and schedule must include but not be limited to: a. Session goals b. User profile and prerequisites c. System functions and processes covered in the session d. Examples of practical exercises to be used during the session e. Identify hours required for each session f. Course outlines and training materials by type of training and user group with time allocations for each topic g. Metrics for measuring effectiveness of overall training

Deliverables: 1. Training Plan and Schedule a. Training Materials for each group b. Training Feedback template

Activity 7.2: Endevor SCM Implementation Support Training/Mentoring Contractor shall provide implementation and configuration support services for Endevor SCM in the Agency identified environments. The support services include on-site training, as needed, and mentoring of ETS, DMV-IS Tech Support and ET staff on technical implementation and configuration. These support services will include up to five individuals.

Page 24 of 28 ATTACHMENT F – Scope of Services RFP #730-25400-12 Deliverables: 1. On-Site training/mentoring as needed a. Implementation and Configuration Instruction Guide 2. Feedback template

Activity 7.3: Provide System Administrator Training/Mentoring Contractor shall provide system administrator on-site training, as needed and mentoring services for a maximum of five Agency staff. Contractor shall provide end user screen shot documentation, training/mentoring outlines, and any other materials customized to the system administrator role. Contractor shall mentor the Agency staff which includes one-on-one guidance and support to foster an understanding of Endevor SCM and processes required to support Endevor SCM. Training/Mentoring services must cover, but is not limited to: a. Setting up new users b. Adding/changing/deleting user passwords and authorities c. Adding/changing/deleting workflow rules d. Setting up security profiles e. Procedures for setting up projects/systems/branches f. All other Tasks that a system administrator will need to perform in order to fully understand how to use system functions and perform all required post implementation Tasks. Deliverables: 1. On-Site training/mentoring as needed a. Implementation and Configuration System Administrator Guide 2. Feedback template

Activity 7.4: Provide End User Training Contractor shall provide on-site training by end user role type. Contractor shall prepare the training to ensure the Agency can operate Endevor SCM at an enterprise level and across all functional areas of the solution. Training must focus on educating the end user on how to operate the solution from the perspective of their role and responsibilities within the solution. Contractor shall provide training guides, course outlines, and other materials customized to the role for delivering training to the following user groups estimated at 60 individuals. Roles may be grouped together when appropriate. a. Mainframe Programmers/Analysts b. Release Management Analysts c. Application Development Managers d. Operations & Production Managers e. Business Analysts/Testers f. Librarians g. Database Administrators h. ETS Systems Programmers and Support staff

Deliverables: 1. On-Site training/mentoring a. Course Outlines b. Training Guides 2. Feedback template

Page 25 of 28 ATTACHMENT F – Scope of Services RFP #730-25400-12

TASK 8: DOCUMENTATION Contractor shall provide Agency with documentation and materials which details a comprehensive understanding of Endevor SCM solution from both a technical and functional perspective.

Activity 8.1: Provide a Complete Set of Documentation Contractor shall provide written documentation which details a comprehensive understanding of Endevor SCM products and tools. Contractor shall provide access to the electronic versions of the Endevor SCM technical and functional documents. The documentation must include, but is not limited to, the following topics: a. End User Screen Shot Documentation that matches Agency’s implementation and configuration b. User Manuals c. Product Implementation Manuals d. Technical Reference Manuals e. Glossary of Terms f. System Administration Guide, including: 1. System Control Tables 2. System Set-Up Option 3. System Configuration Options 4. System Reporting/Analyzing Options 5. System Workflow and processes 6. System operational and maintenance procedures g. System Utilities, including Backup and Recovery Utilities h. System Data Dictionary i. System Process and Related Entity Diagrams, and interfaces j. Other documentation required to understand, implement, and become proficient with the SCM solution.

Deliverables: 1. Editable electronic documentation a. One for each procedure b. The current agency configuration(s) by system platform c. System Administration Guide d. User Manuals e. System Diagrams

TASK 9: PRODUCTION IMPLEMENTATION Contractor shall be on-site, as needed, to provide support services during the Go Live implementation and deployment of Endevor SCM. Contractor shall provide instruction, oversight, and mentoring for Agency, ET and ETS staff involved in the implementation activities to ensure a complete, accurate, and supportable Endevor SCM installation. Agency will install and configure, with oversight from the Contractor, the Endevor SCM products below:

Page 26 of 28 ATTACHMENT F – Scope of Services RFP #730-25400-12 a. The Mainframe implementation of CA Endevor 15.0 for the DMV and any updates or patches b. CA Endevor SCM Quick Edit c. CA Change Manager Enterprise Workbench (1 Server) d. CA Endevor Software Change Manager Parallel Development e. CA Endevor software change manager Interface for Remote DB2 for z/OS

Activity 9.1: Production Implementation Strategy and Planning Contractor shall develop and document a production implementation plan which includes, but is not limited to: a. Implementation Activities, Plan and Schedule b. Implementation Procedures c. Communication and Contact Information d. Back-out and recovery Procedures e. Go/No-Go Decision Criteria f. Go-Live checklist that includes preparation and validation activities, includes dates, times, and resources, for go live preparation and go live support. g. Conversion/Load into the production environment h. Set up users i. Validate systems j. Review the readiness of the system, administrators, support teams, and users for go live k. Assist in registering administrators for customer support and instruct on how to interact with Contractor’s Technical Support Services. (ongoing maintenance, troubleshooting etc) l. Develop a skills-based certification process to validate that the Agency staff have acquired the skills necessary to operate and support the SCM solution.

Deliverables: 1. Implementation Plan and Schedule a. Systems Validation Reports b. User skills assessments (certification process) c. Go No/Go checklist d. Go No/Go decision criteria template

Activity 9.2: Implementation Support Contractor shall provide on-site support services during production implementation and during the first two (2) weeks of post production support. Contractor shall develop and submit a frequently asked questions document during DMV’s production implementation and operation. Contractor’s on-site availability and support services must include, but are not limited to: a. Resolution of technical issues b. Support and assist all user groups on any of the Endevor SCM products c. Identification of common issues to determine if they are related to SCM solution implementation, configuration or training d. All Systems and applications must be stable for 14 business days. For these criteria, “stable” means without any reported Severity 1 or Severity 2 issues.

e. If a Severity 1 or Severity 2 issue is detected, Contractor shall: 1. Provide the solution to fix the identified issue 2. Implement the solution

Page 27 of 28 ATTACHMENT F – Scope of Services RFP #730-25400-12 3. After the solution is implemented, the System must be stable for 14 business days with no open or reported Severity 1 or Severity 2 issues.

In the event Endevor SCM solution/implementation requires any revisions or changes, or requires corrective action to ensure Endevor SCM solution is fully functional in production, the Contractor shall, at no additional charge, outline all necessary changes, configurations and adjustments until implementation is passed or rejected. Agency will provide Approval/Signoff to move to the production environment, if passed, pursuant to Section A.6. a. Resolution of all issues to Agency’s satisfaction to gain Agency approval to close out the Project b. Conduct the skills certification process for Agency staff

Deliverables: 1. On site implementation support/mentoring as needed a. FAQ document (common tips/tricks and troubleshooting) b. Run Systems Validation Reports c. Resolution of all Severity 1 and Severity 2 issues d. Plan and acceptance for all non Severity 1 and Severity 2 issues 2. Provide Lessons Learned

Activity 9.3: Final Acceptance Upon completion of Project activities identified in this document, the Contractor shall develop and submit a written Project completion report for final acceptance to the Agency APM for review and approval. Contractor’s report must describe and demonstrate how all the work defined in this document was delivered and fulfills all Agency requirements. Acceptance will be in accordance with the Final Acceptance criteria (Section A.6.2). Deliverables:

1. Contractor shall provide a fully functional System that is complete and operating correctly according to the Agency’s Requirements. 2. The Endevor SCM Systems implemented must be stable for 30 consecutive days. For these criteria “stable” means without any reported Severity 1 or Severity 2 issues. 3. The Contractor shall provide paper and electronic copies of all Deliverable documents to the Agency. The Agency must approve any exceptions to the delivery dates in writing. 4. Project Completion Report a. The Contractor shall verify, along with the Agency, to ensure that all Deliverables for the Project were completed as outlined in the SOW

Page 28 of 28 ATTACHMENT F – Scope of Services RFP #730-25400-12