Cities Index.
Agenda packet

City Council and Authorities Concurrent
May 27, 2025

Document
Agenda packet
Meeting
May 27, 2025
Body
City Council and Authorities Concurrent
Pages
107
Original file
250.9 MB
Text extracted from the city's file for reading and search. Open the original on santaclara.legistar.com. That file is the official record.

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions
I) Describe how your solution will address the service requirements and Service Levels associated with providing the city with periodic reports around operation improvement recommendations and innovation through new products and services. Explain how you will address unique attributes and considerations for each C;ty department in making such recommendations.

We report on article usage stats and comments received, and review/analyze the articles linked to tickets created. Our Knowledge Manager analyzes this data along with data on resolution rates and will work with Unisys groups and client SMEs to address any opportunities to increase resolution and/or reduce handle times. The reporting built into ServiceNow along with reports that our Unisys quality department produces allows Unisys to quickly drive to a root cause of any resolution issues and also identify opportunities to further service desk resolution opportunities. As ServiceNow is built upon KCS principles (Knowledge Centered Support), the structure of the database is already correlated to best practices and allows us to further drive excellence in the Knowledge space.

Response
Service improvement and innovation are crucial to the City's success. Doing them successfully requires not only a continuous improvement and innovation mindset but also a structured approach for tracking these ideas from start to finish. The Unisys solution will establish an approach that meets the City's requirements for reporting on operations improvement recommendations and innovation. The approach is known as the Continuous Service Improvement and Innovation Plan (CSIIP). This process is a formal way to identify, review, prioritize, and track improvement and innovation concepts from start to finish. This approach will enable Unisys account leadership to align with City leadership on activities that are approved, funded if required, prioritized, and launched. The process can be tuned to capture departmental impacts to prevent the team from missing out on key departmental improvements.

This process relies on the efforts of key team members and on overall system metrics. The different system components must come together into an effective view that leadership can rely on and use to measure performance and identify opportunities to drive operational improvement and innovation ideas.

The Unisys solution will enable a Service Level reporting approach that allows performance to be tracked at the required level of detail. This approach includes SLAs related to the Service Desk, Field Services, Infrastructure, Applications, and Project milestones. The ServiceNow platform can b_e configured to allow the team to look below an aggregate SLA to see how performance is occurring at a department level so that unique actions that might affect a specific department can be identified.

When service improvement measures are not represented in service data, Unisys will augment that data with surveys or other data collection methods that are tailored to the service. Identification of the service improvement recommendations will be determined through periodic outreach to individual departments or groups with common interests. Exposure of new technology with potential for service improvement will be made part of periodic departmental gatherings that are patterned on product user group meetings and

Page 47 ends

CITY OF SANTA CLARA
Schedule 2- Final Service Tower Solutions
active participation in key product meeting and conferences. We will capture the recommendations and actions as part of our CSIIP process that will track our continuous improvement and innovations actions throughout the year.

Page 48 ends

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions
m) Describe your proposed knowledgebase solution and how you will drive its use across City EndUsers as well as Service Provider staff.

Response
The Unisys proposed Knowledge Management solution will reside within the ServiceNow platform. It is configured to address both "how to" and procedural questions and will reflect views that correspond to a user's access level. The articles will be maintained by a Unisys knowledge manager who will respond to user feedback, work with resolver stakeholders, and read survey and quality analysis data with the operation to receive feedback on knowledge artifacts.

Unisys will develop knowledge articles and documentation to handle issues that are high call drivers during the implementation, by the Transition Knowledge Manager. In addition, we will also address issues that are identified by our team and CSC's SMEs as being important to deliver (high urgency and/or impact). We will partner with CSC contacts to identify who should be consulted to develop the list of important problem types and will develop a process to identify any ongoing knowledge gaps so that the knowledge manager can work to create any documentation that may be missing on an ongoing basis. We have an extensive knowledge base of standard articles (COTS) available in our ServiceNow instance that will be available in Istanbul.

The Transition Knowledge Manager will drive processes and will work with the operation team and CSC SMEs to make sure that any pain points are addressed from the transition kickoff through Hypercare. The steady state KM will continue to maintain and develop the changes in knowledge in partnership with any identified CSC SMEs. This work cannot be done without consultation with CSC resources, as identified by CSC's transition team.

Steady state KM's hold meetings on an agreed-to schedule to discuss normal changes and the progress against them. They will also discuss strategies for improving article usage and first call resolution through identifying proceses the service desk can perform to avoid dispatches or referrals to client resolvers - this effort is perfomed in consultation with operational resources and with client SME's. A set of standard reports produced against knowledge-centered metrics gives the KMs and the delivery teams information about how best to deliver services and to maximize LO and L 1 resolution.

In summary, for the Knowledge Management transition, Unisys will provide the following:
• The top 10 call driver articles
• The top 10 processes with a high urgency and/or impact • The top 10 "how to" articles

Page 49 ends

• The top 10 procedural articles
• The top 1 O Unisys-driven processes to support service delivery.

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions
All of the above will be driven by the Transition Knowledge Manager with a current ticket dump that includes product types, "how to" or instructional data, product types, etc. n) Describe your proposed solution and approach for providing cross-functional Service Integration Services described in Schedule 3A.

Response
Unisys proposes providing the City with an Enterprise Service Management platform, wrapped with endto-end services and support. Our overall Service Management solution includes a new ITSM platform based on ServiceNow. This new ITSM platform, along with the current infrastructure and security monitoring solution, enable the Service Integration Services described in Schedule 3A. The ServiceNow platform will be integrated with existing infrastructure monitoring tools and the Unisys SIEM solution to establish a comprehensive monitoring capability for the City's environment. Automated flow of critical alerts into the ITSM tools as incidents is a key feature; these incidents will be routed with the proper priority to the appropriate resolution teams, including third parties that use the system for resolution. This enables an end-to-end integration of the key components to maintain reliable, high-quality delivery.

The ServiceNow platform has industry best practices for reporting capabilities. This includes various time stamps along the way for incidents and requests to enable analysis to be accomplished at various levels to look for opportunity. Reporting on response and resolution times is a key component that will enable the City to understand the speed at which services are delivered to City employees. The platform also provides a portal that will contain knowledge articles that are available to resolver teams and end users to enable information to be shared in a way that drives a better experience.

The Unisys solution and operational processes are based on a comprehensive set of ITIL-aligned processes for the ITSM functional modules. Our ITIL-aligned processes are certified to ISO 20000, which means that the processes are regularly audited and updated to provide compliance with highest quality standards. Therefore, the City will benefit from a Service Management framework that represents industry best practices.

Page 50 ends

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions
o) Describe how the Enterprise Architect key position will drive value chains across the City's IT environment and what core competencies and methodologies you will bring through your company's expertise in this area?
Response
The Enterprise Architect will drive value chains across the City's IT environment through the delivery of Five Critical Deliverables, including the IT Strategic Plan (ITSP), the Enterprise Architecture Plan (EAP), The Digital Government Plan (DGP), Innovative Products and ServiCElS Report (IPSR), and the Services Strategic Review Report (SSRR).

The Digital Government Plan and the IT Strategic Plan will start with establishing the business goals of each department in terms of the City's Mission and Vision through a.series of focus group meetings.

Drawing upon strategic planning methodologies developed by Gartner and the Meta Group, the ITSP will align business goals, driven by the City's Mission and Vision, to enabling technology components, to create a Future State vision. Gaps between the Current State and the Future State then become the building blocks of future projects which will be prioritized based on technical sequencing, expected value, maturity (adoption readiness), and budget. The EAP will take the conceptual picture of the ITSP and determine requirements based on a framework of architectural domains. By using an EA framework to establish requirements, we ensure that new capabilities are introduced that interoperate with existing systems. Development of the City's EAP will draw upon formal frameworks such as Zachman and FEAF, but at a higher abstraction level to reduce the cost of maintenance and sustainability of the EA program appropriate for a city the size of Santa Clara. The ITSP and the EAP form the foundation for governance of the investment in IT based on business goals aligned to the City's Mission and Vision.

The IPSR will be developed by monitoring industry trends and ideas from other municipalities. The Enterprise Architect will use the IPSR to engage City departments to expand awareness of how technology can be used to realize their business goals. This increased engagement in the identification of future change elements will aid in driving adoption of new capabilities and technologies. The SSRR gives the Enterprise Architect the opportunity to monitor progress toward the realization of business goals, and provide suggestions for remediation of adoption risk. Success metrics introduced in the ITSP will form the basis for this assessment.

The Enterprise Architect will drive value by establishing a clear roadmap of technology enabled capabilities that are aligned to business goals that have been developed through diverse engagements with City departments.

Page 51 ends

CITY OF S ANTA CLARA
Schedule 2 - Final Service Tower Solutions
p) Describe how you will ensure cross-Service Tower collaboration to ensure that the SeNice Provider is delivering IT services in a holistic, integrated fashion.

Response
To enhance cross-service tower collaboration, we will transform the environment to one that is driven by DevOps and Agile (the SAFe methodology). Unisys will first properly baseline the performance and efficiency using clearly defined and granular work type items. Each resource will account for their time, which is categorized into operational and project types. Unisys will also bring Organizational Change Management expertise to enable communication and training plans to be developed to further foster the successful adoption of these practices. These methodologies will be the cornerstone of encouraging cross-service tower collaboration in a climate of change and growth. This holistic and integrated approach will establish a climate that provides a solid foundation for clarity, ownership, shared outcomes, and increased productivity.

Unisys will continue to leverage daily tower checkpoints to verify that everyone is moving toward shared goals, has full understanding, and is accountable for his or her areas of ownership. Additionally, tower leadership meetings will review daily progress and provide further opportunities for adjustment. Metrics will be compared to the baseline to show improvement. Furthermore, project plan milestone dates will be evaluated for change.

Page 52 ends

- I

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions

2.1.2 Cross Functional Solution Overview
Instructions: Provide an overview of the Cross Functional solution you propose to address the City requirements stated in Schedule 3A. Incorporate responses to common solution characteristics and description elements listed above. Limit 5 pages.

Response
• Service area roles
• Dedicated on site staff
• Leveraged staff
o Onsite vs. offsite
o Functions to be performed
• Provider COEs or other Service Provider groups e.g., innovation councils • Split between keep the lights on operations, proactive improvement operations, and projects • Level of effort assumptions included in proposed pricing for each of the following areas:
o Operations
► Keep the lights on operations
► Proactive improvement operations
o Projects
The staffing model elements include roles dedicated or leveraged staffing, splits, COEs, councils, and operational or project effort. They are similar for both the City Approach and the Provider Approach. The clarification for each of these elements is in each section (e.g., 2.1.2, 2.2.2., 2.3.2, 2.4.2, 2.5.2), and included in other applicable sections. Furthermore, definition and clarification of split effort, for both approaches, are in the pricing worksheets.

Unisys has a deep understanding of the essential requirements to design and implement an ITSM platform for our customers. We have developed our own best of class too/sets by introducing proprietary processes and configurations. This deep knowledge and experience is transferable to CSC and is included with our solutions. Our methodology focuses on using highly maintainable configurations of the ServiceNow platform, which means customization is very minimal, if at all. This approach also enables integrations to be created to your external infrastructure systems, through orchestration and automation capabilities (i.e., password reset, SCCM, Nagios, SolarWinds, etc.).

Our goal is not just to replicate what is utilized in our global ITSM system but to implement only what is needed to deliver the required services to CSC that provide business value. With our knowledge of your current ITSM environment, we start by conducting a mapping exercise to compare data fields from the legacy to the new, against CSC's business requirements. We will then draft a data design document that will detail the configurations, from the foundation data to the workflow processes, business rules/logic, UI

Page 53 ends

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions
components, and data tables/interfaces for CSC's specific functional modules. This exercise cannot be done without consultation with CSC resources, as identified by CSC's transition team.

In our experience, we have stepped into multiple deployments where the contractors have over promised and been unable to meet their timelines and requirements for the client. Fast tracking such implementations has led to end-user dissatisfaction with a tool that is not fully ready for deployment and budget overruns.

Outlined below is a representative sampling of our recent engagements that demonstrates our expertise and knowledge from end-to-end.

Major wholesale food chain
• Implemented Service Request Management for the entire enterprise • Managed incident, problem, and asset management
• Minimized service desk workload by optimizing resolution times • Optimized client's investments by completing deployment within schedule • Improved end-user experience via services which consistently met or exceeded KPls.

Automotive distributor
• Legacy system was an outdated version of HP Service Manager • Implemented our Service Desk Optimization and Service Governance solution • Implemented end-user services
• Deployment completed on time and within budget
• Expanding services to ITOM modules (ServiceNow Discovery and Service Mapping).

Science and technology company
• Deployed zBoot (a clean implementation of the ServiceNow platform) • Full asset management, software asset management, Service Desk, and Field Services • Deployment completed on time and within budget
• Existing 6-year version of ServiceNow that was not working as expected.

United States Commonwealth Client
• Implementation for IM, PM, CM, Service Catalog, SLM, and AM • ODS integration for reporting
• Monitoring and Event Management

Page 54 ends

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions
• Discovery and CMDB integration
• SAP integration to Service. Catalog and billing
• Implemented processes to provide consistency and support for their requirements.

State agency (Department of Justice)
• Old version of SM tool
• Deployed Service Desk
• Expanding services to include service catalog deployment and additional usage of ServiceNow • Deployment completed on time and within budget.

Unisys is confident that with our dedicated Service Management team and the ServiceNow platform, this allows us to meet the stated requirements and will provide CSC the flexibility to accommodate changes and growth in the organization. Our partnership with ServiceNow augments our capability with our services.

Yes, the proposal presented to CSC includes all activities needed to implement and perform an initial populating of the CMDB, as well as asset and license management system.

Organizing and managing the application tower activities and resources will be similar as with all other towers. Each resource's knowledge and skills must be shared with at least one other resource. A succession plan is critical for a number of reasons, including removing bottlenecks in the organization.

Unisys will cross train and establish a succession plan with each named resource during transition.

Most important, Unisys leadership will train each person on how to think beyond tasks and establish a vision in their domain. Each person must believe in what they are working on, in order to gain satisfaction in a job well done. As such, they must own objectives rather than only tasks. Unisys leadership will strive toward a culture shift of higher-level objectives and owning a vision, which encourages more thinking that is creative and growth.

The applications team will be organized along with major areas of business functionality, giving City employees a known point of contact who understands their business issues. These major areas include Public Safety (Police and Fire), Finance, HR and Admin (ERP, Recruitment, Budget, Document Management), Utility Management (Utility Billing), Land Management (Permitting, Work Order Management), and Web and Digital (City Websites, SharePoint, Agenda Management and Streaming Video, Social media, Citizen engagement). We will ensure that each application has a primary and secondary person assigned to ensure continuity during planned and unplanned absences.

As technology changes, the team will need to adjust and learn. Unisys will provide team members with access to resources within Unisys. Unisys University has a wealth of training available to employees.

Each team member will have a training plan that can be achieved through Unisys provided tools in

Page 55 ends

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions.
meeting established goals. If there is a specific skill needed beyond what is available, Unisys will mutually agree with the City on those requirements, which may include specific training classes, bringing in new resources, etc. The applications team will also forge strong relationships with the City's vendors to ensure understanding the City's business needs and incorporate those into product roadmaps. This will help with future planning but will also help resolve any immediate issues.Each resource on the applications team, each will define their roles and responsibilities as it applies to the City's transformation goals, principles, mission, and vision. Unisys management will help by doing continual levels of follow up, weekly, against those responsibilities. Furthermore, management will not allow deviance to ensure change happens and cultural habits that prevent growth are quickly broken down.

Work plans will establish milestone dates. Resources are accountable to those milestones, consistently, in order to establish a culture of excellence and high performance. Unisys recognizes that if accountability is not consistent, it will breed a culture of mediocrity. Unisys is committed to moving away from this type of culture by showing improvement with measurable results by the end of the transition phase.

Improvements are shown by establishing metrics, snapshotting a baseline, then showing improved progress over the baseline toward mutually agreed milestones.

The PMO will follow a well-defined and rigorous best practice PMO methodology. For success, scope must be clearly defined and agreed to by all stakeholders. The scoping process is established from a clear definition methodology and charter process. As such, the current charter process will change to providing options with impacts, rather than only establishing constraints. This change will therefore provide the City facts to make the best decisions on priorities. The Jira tool will provide workflow, capacity, and demand management. Furthermore, source control management, test automation, configuration, and environment management are provided and described herein.

Page 56 ends

Response

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions
Unisys agrees to and will use the IT guiding principles in Schedule 3A and understands the importance of having the right skills, relationships, focus, and consistency that are required to deliver cross-functional services that work effectively across towers and personnel. To assume a leading role in driving the alignment of strategy with the City's IT business objectives, we will adhere to the strong teamwork processes described in this response.

Unisys will provide a mix of dedicated and remote staff to provision, deliver, and manage the crossfunctional services in Schedule 3A. Onsite resources include key service provider personnel, as described in Schedule 9. Additionally, onsite resources include application analysts, field engineers, endpoint engineers, security and network engineers, and at least two project managers. Unisys will use offsite resources for other functions such as application packaging activities; infrastructure and security monitoring; Level 1 and Level 2 Service Desk agents; and incident management, problem management, knowledge management, reporting, operational analytics, and change management functions.

Unisys will comply with applicable standards, policies, regulations, and applicable laws. These include ITIL/ITSM, PMP, ISO 27001 , ISO 17799, PII, PCI, HIPAA, CJIS, CMMI Level 3, ISO 2000, ISO 27301 , ISO 21500, and ISO 18770.

Unisys will provide several key tools critical to our solution, and we will leverage other key tools that the City owns today. One of the most critical tools from Unisys will be the ServiceNow platform, which will be deployed as the enterprise ITSM platform and provide core Service Management functionality such as Incident, Request, Problem, Change, Configuration (CMOS), and Knowledge Management. ServiceNow will also provide the end-user portal for access to knowledge articles for self-help and other end user-centric features. Unisys will also use Nagios and SolarWinds for automated monitoring of the core infrastructure and HP ArcSight, which is used for the Unisys SIEM solution. We will provide key Microsoft tools such as Visio and Project as required in the delivery of service to Unisys Team members.

Unisys will use City-provided licenses and tools such as Microsoft System Center Configuration Manager (SCCM) for ~se by our end-point engineers and asset management personnel. Other City-provided tools that Unisys will leverage include SCEP, MDT, Flexera, and AirWatch for mobile device management.

Unisys will continually adjust priorities to meet the City's ongoing requirements and recognizes that needs will shift between strategic initiatives, to projects, to operations. We will help to confirm that changes are well understood, so that the City may make the best decisions for meeting competing schedules. Project management is the art of balancing those competing objectives; therefore, Unisys emphasizes the importance of adhering to a robust Program Management Office (PMO). The PMO will provide a set of policies, processes, and methodologies based on DevOps, SAFe and Project Management Institute that project teams can use to facilitate the implementation of successful projects. These project management tools are identified and deployed as part of the DevOps and SAFe (Agile) transformation with the goal of assuring that stakeholder expectations are clearly understood; issues, risks, and problems are quickly

Page 57 ends

CITY OF SANTA CLARA
Schedule 2- Final Service Tower Solutions
identified and addressed; and complete and open communications with project stakeholders are maintained. No two projects are identical. The project management tools delivered will provide the flexibility needed to accommodate a wide range of project types while providing the controls needed by the PMO to track project status and resource utilization effectively.

The PMO will enable project portfolio management processes and the monitoring of individual projects.

Management reports that clearly identify resource utilization and resource capacity will be published each month. A monthly project portfolio review meeting will be conducted to evaluate project performance, align the project portfolio with strategic objectives, monitor and manage staff capacity, and identify issues and risks. Project timelines will be mutually agreed upon based upon clear scope definition and applicable Project Deliverables. Upon priority or scope changes, the timelines must be adjusted accordingly.

Satisfaction Surveys: Satisfaction surveys are a crucial part of assessing the overall value being delivered across the enterprise. As detailed in our responses to RFP requirements 2.1.1f, 2.1.1g, and

2.1.1 h, Unisys will deploy multiple surveys to enable us to capture appropriate feedback from employees to City leaders. Some of the surveys are transactional and focus on how a call to our Service Desk went (for example); others are at a departmental leadership level to assess how IT is supporting the City's business goals, and others are annual surveys to assess overall performance to the City.

Continuous Service Improvement Process: Continuous improvement and innovation is a mindset that Unisys will drive across the enterprise and towers. Identifying opportunities is an obvious step in this process, but it is just as crucial to evaluate, analyze, decide, prioritize, and track the efforts to completion.

Unisys will use an approach called the Continuous Service Improvement and Innovation Plan (CSIIP) to add structure, reporting, and consistent governance for the ideas so that the overall City and Unisys team are aligned with the priorities and progress to drive value to the City.

Critical Deliverables: The critical deliverables are an important part of the program; a strong governance approach will be established to enable the deliverables to be clearly tracked and continuously visible to the City. These deliverables drive quality, define operational methodologies, and establish the strategy for meeting the City's goals as well as reflect on how the program is performing overall to support the City's objectives. To confirm that a strong focus is placed on the creation of the deliverables, Unisys will leverage dedicated account resources supported by our experts as necessary and foster ongoing maintenance of these deliverables in accordance with Schedule 3A, Section 8.0.

IT Governance: To manage and administer the full portfolio of the required deliverables ·in Schedule 3A, Unisys will develop a leadership framework that fosters a culture of innovation and growth toward higher level business outcomes. We will set priorities in moving toward the City's vision and objectives: to promote a living and working environment that allows for the best quality of life in Santa Clara through technology and innovation. Governance will manage how we listen, innovate, and inspire new technology solutions that demonstrate value to Santa Clara.

Page 58 ends

CITY OF SANTA C LARA
Schedule 2- Final Service Tower Solutions
Tools and Knowledgebase: Effective knowledge management will drive costs down, increase end-user satisfaction, and drive efficiency. Unisys' ITIL process knowledge and partnership with ServiceNow will bring the best service management expertise and tool on the market to meet the requirements for the proper ITSM tools that are described in Schedule 3A. Unisys will use an ITI L v3 compliant framework and operations model that incorporate Lean Six Sigma principles to maximize the value to the City.

Security Services: The information security program integrates security protections and processes throughout the technology services that are delivered. The program will be defined in collaboration with the business units to confirm that it meets their security needs, and a related Cybersecurity Plan will be developed and maintained as part of the program. To define the program, an Information and Cybersecurity policy will align with the City's security plan and provide the necessary governance for the City to achieve its security objectives, such as maintaining regulatory compliance with PCI. The security expertise and services are also forward leaning to provide protection for future cloud services and future convergence of industrial control systems with IT. Security services will include risk assessment, advisory, planning, awareness, SSAE 16 SOC 1 Type 2 reports, SIEM, penetration testing, intrusion detection and prevention, incident response, threat assessments, physical security, environmental controls, Active Directory administration, vulnerability scanning, patch management, and malware prevention. /TLC and Operations Services: Unisys recognizes the importance of adhering to a strong methodology for the life cycle of services, as described in Schedule 3A. Therefore, we will perform Information Technology Leadership Council (ITLC) and Operations Services by confirming that the success criteria are defined to the City's success criteria of the objectives. Additionally, Unisys will start life-cycle plans with the following end goal in mind: how the user will learn and benefit from the new technology. When the ideal use case is understood first, high-quality outcomes are maintained.

Service Delivery: To provide capacity management, availability management, service level management, and other functions that are described in Schedule 3A, Unisys will conduct periodic reviews of each functional responsibility to maintain the highest level of quality on time.

As part of Acquisition and Management Services, Unisys will manage the overall procurement process for hardware, software, and services. Unisys will liaise with hardware vendors to cover administration tasks related to the procurement of new devices and consumables as part of daily operations and refresh projects. This process will be initiated by a service request in ServiceNow, where the fulfillment of a service request will trigger a purchase of a new device or consumable.

The Unisys procurement team will also provide input to a Unisys PMO resource who will liaise with the City to define and maintain the equipment list that can be ordered and confirm that Service Catalog items are current and in line with the respective services. Unisys will not take financial responsibility for the purchased devices; service covers the procedure of facilitating procurement administration on the City's behalf.

Page 59 ends

CITY OF SANTA CLARA
Schedule 2- Final Service Tower Solutions
Another important area for emphasis under service delivery is asset management. Having the best processes and tools in place for asset management is critical so the City has visibility to make decisions, verify compliance, determine the best department business outcomes, and avoid cost overruns.

Asset management includes hardware and software license tracking as well as a strong methodology and set of tools with automation to help with driving an accurate result. Unisys will use the ServiceNow platform as the core component to drive asset management that improves inventory accuracy and leverage tools such as the Unisys instance of AssetTrack and the City's SCCM tool. This will improve the City's IT portfolio management (e.g., Heat Map Report and TIME Analytics) for better data accuracy.

The current Atrium Configuration Management Database (CMDB) data will be moved or integrated with a ServiceNow CMDB, depending on the accuracy of the CMDB as it stands today. ServiceNow has a direct SCCM Connector that we will implement with a MID Server to handle the communications. For the data center servers, we will implement Discovery to feed the CMDB. Unisys will bring in an Asset Management Subject Matter Expert to review and align the existing data model in preparation for any initial data loads or future automated data loads. The SME will also review current processes and documentation and update to suit current city needs. The existing asset data will be analyzed and updated as necessary. The SME will also work with the reporting team to set up the weekly, monthly asset reports as identified in Sche.dule 7. These efforts in combination with the ServiceNow CMDB will help Unisys and the City to improve the quality of the current CMDB data and have confidence in the CMDB as a complete, correct, and compliant single system of record to drive business-critical processes. The ServiceNow CMDB also allows quick and easy visualization of the infrastructure and service configuration information to understand impact and risk, make better decisions, and provide high-quality business services. Unisys will also help the City with business development that includes requirements gathering, development of scope, RFP evaluation, and making recommendations.

To further enhance the input channels to the CMDB, Unisys proposes to continue using the AssetTrack tool. It deployed at the city and will be integrated with ServiceNow CMDB by Unisys integration teams.

Unisys client engineers to capture changes applied to the equipment and report any discrepancies will use AssetTrack. The incoming data arrives into a sandbox, where the Unisys Asset Management Team validates it before allowing it to reconcile with the CMDB data. This ensures the accuracy of the CMDB, by avoiding incorrect data entries.

As part of Software License Tracking services, Unisys will record and maintain software information to track instances of software installed in the city environment and cross-reference this inventory with a defined list of approved software "(Definitive Software Library) and license details provided by the City.

The Asset Management SME will review and work with Unisys teams to perform the initial load of all software installed instances using agreed technologies and methods during the Transition Unisys will:
• Administer software licenses for the supported environment, including the entry of software contracts

Page 60 ends

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions
• Initiate procurement of appropriate licenses that reflect ongoing demand • Liaise with software vendor regarding license availability and demands on behalf of the City • Monitor license usage to dete~mine the appropriate versions are available and being used • Maintain consistent versions of in-scope software.

The Unisys Asset Management team does software license compliance monitoring by performing a series of steps listed.

The Unisys Asset Management Team uses the reports of Approved software data from DML (Definitive Media Library), the software contract data, and Software licenses data from ServiceNow to determine the number of active contracts, number of contracts reaching expiry, historical contracts, etc. Using the reports from SCCM, the team reviews the license usage of the software contract along with the number of licenses available in the pool. The Asset Management team then determines whether the organization is still in compliance with the license agreement based on the reviews and will create a software compliance report that will be published to the city on a weekly basis.

The service does not include acquisition or financial responsibility for the software licenses or for software license compliance. Software License Tracking is driven by the Service Request Management and Change Management processes. Changes of ownership, configuration changes, relocation, and-other resultant changes to the software asset will be updated in the asset repository.

Unisys will also perform periodic audits of hardware and software assets. Audit could be initiated by the City or initiated internally by Unisys. If any exceptions are discovered during the audit, such as over utilization of licenses, a non-conformance is raised, audit reports are published, and observations are tracked for closure. Based on the audit observations, investigations are initiated and sufficient amounts of licenses are procured or the hardware asset variance is resolved as the case may be.

The Unisys Asset Management solution will deliver a structured and managed approach to provide contracted assets that are collected, captured, and tracked at every stage of the asset life cycle in the asset repository. It will enable tracking of IT equipment from the time it is procured to its disposal. Unisys will track and manage the hardware assets listed in the table below. Unisys will record arid track equipment and software details, such as serial number, model number, make, license number, version, and ownership, as well as builds.

ASSET TYPE QUANTITY
Workstations (Desktops & Laptops) 1022
Mobile Devices (Tablets) 310
Printers and Multi-Function devices 182
Network scanners 2

Page 61 ends

Audio Video equipment
Servers (Physical & Virtual)
Storage devices
Network equipment (switches, routers, firewalls,
wireless controllers)

CITY OF SANTA CLARA
Schedule 2 - Flnal Service Tower Solutions
17 247
6 102
Service Support: Support includes the services described in Schedule 3A, such as incident management, major incident management, problem management, configuration management, and change management. The service desk tower, built under the ITIL processe~, provides incident management, service request management, major incident management, problem management, knowledge management, and ancillary support with metrics and reporting. Automation is included with monitoring systems by Nagios and HP ArcSight that flow through the central event management process for generating incident tickets into ServiceNow.

The City's general responsibility for the steady state operation Service is to provide the discovery toolset (SCCM), which enables consistent and regular scanning of the entire online infrastructure. Unisys will provide ServiceNow ITSM and the CMDB along with ServiceNow discovery for discovering the enterprise assets.

To deliver a structured and managed approach to the maintenance of a configuration model of the service, assets, and infrastructure. Configuration Management records details on the individual configuration items and the relationships between service assets and configuration items. The primary focus of Configuration Management is stability in operations of data center equipment, data center software, and support infrastructure.

Unisys will track devices and their relationships with the ServiceNow Discovery tool, which is used to discover server. network, and other data center devices that are part of the organization's assets and listed in the table above. The ServiceNow Discovery tool will automate the process of populating the CMDB by exploring IT systems to identify hardware and software, and then creating instances of Configuration Items (Cls) and relationships from the discovered data.

As discussed in the Service Delivery section, Asset Management delivers a structured and managed approach that enables the contractual details of contracted assets to be tracked and updated in the asset repository. The assets include physical assets such as desktops, laptops, smartphones, printers, and multifunction displays, audiovisual equipment, servers. and network equipment. Asset details are initially loaded by using agreed technologies and methods. The asset information is collected by using automated discovery technologies that are in place in the City's environment, loaded from the data supplied by the City, or manually collected and loaded for specific and low-volume assets. This data will be migrated into the ServiceNow CMDB. Changes of ownership, configuration changes, relocation, and other resultant changes to the assets will be updated in the CMDB.

Page 62 ends

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions

Page 63 ends

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions

2.2 Service Desk Services (Enclosure D - Schedule 3B)
Summary BAFO:

Further Clarification and milestones of Road Shows
Additional definition, frequency and milestones of Tech Cafe

2.2.1 Service Desk Solution Questions
Instructions: In addition to the General Solution questions in Section 4 above, Service Provider shall provide responses to each of the Service Tower specific questions below. Limit responses to each question to a half page.

Unisys Service Delivery Analytics (SDA) continuously works on identifying opportunities to automate resolution or drive incidents and service requests to a lower cost and faster point of resolution such as First Call Resolution. Unisys will review these opportunities periodically and jointly with the City of Santa Clara in order to present incident types that SDA has detected could be classified as First Contact Resolution.
a) Describe the types of Incidents that your Service Desk will be capable of Resolving on a first contact Resolution basis (i.e., directly Resolving I fulfilling, without the need to escalate to a Level 2 or Level 3 resolver group), and how you will drive First Call Resolution through the Service Desk, including service approach, tools, techniques and any year over year increases in the FCR rate. Describe your approach to continually increase First Call Resolution Rates over the Agreement term.

Response
The Unisys Service Desk will be able to resolve on first contact the following categories of incidents; issues with account administration, password resets and unlocks (where approved by the City), connectivity issues, and documented, common hardware error messages. Also resolvable are "How to" questions for common products, such as Active Directory; Office 365; Outlook; Domain Directory; Windows 10, 8, and 7; Internet Explorer; mobile devices; and antivirus/malware solutions. The Service Desk will also answer basic questions about COTS and specific City of Santa Clara applications based on knowledge articles developed by the City and the Unisys Team and driven by call analysis to address top call drivers.

On a monthly basis, the Unisys Service Excellence Office (SEO) will identify top drivers of incidents, customer dissatisfaction, and high-touch resolutions (l evel 2, Level 3, and deskside visits) on a monthly basis via data from ServiceNow. The SEO will use this analysis to identify high-value training opportunities for our agents and technicians (or in partnership with our knowledge management team) to develop self-help solutions. This will be an ongoing process that also includes our field engineers to

Page 64 ends

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions
maintain movement of a resolution from the field, to the desk, and to self-resolution. Items identified within the Knowledge Management platform as First Call Fix articles will be used by the Service Desk Agent to effectively handle First Call Resolution. In conjunction with the SEO, analytics will be reviewed monthly to determine the effectiveness of articles and new types of activities that can be implemented for the SD as part of FCR articles. The actions to drive improvement will be developed with the operational leads and driven to completion. The actions can be incorporated into monthly operational governance to provide visibility to the ongoing improvements in operations.
b) If you are proposing a remote Service Desk solution, please describe what communication approach you propose to use in order to get the City's End-Users to utilize the remote-based . services.

Response:

The Unisys transition team for the account will work with City IT leadership to develop a communication strategy and a plan that showcases the new features that will be brought to the City's employees as the account transitions to the ServiceNow platform. The key features will remind them of the solution's 24x7 availability and the ability to reach out by phone, web, or chat. The plan will also showcase a new portal that will provide them with access to much more information than they had in the past; including self-help articles and incident and request status. This access will include the ability to use mobile devices to access the new end-user portal. Ongoing communication will be developed to demonstrate the Service Desk's impact on the use of knowledge articles, resolution rates, and other key metrics that will help the City's employees to see the benefit of the Service Desk. The team will also be able to leverage the TechCafe and IT Road Shows to help with showcasing the new portal and features that will improve their experience with IT.
c) Ensuring an intimate experience between end users and the Service Desk is important to the City. How will you close the gap between the locations of the End Users and the remote Service Desk location (i.e., End-Users' fixation around the Service Desk not being on premise)? How will you will address Service Desk staff knowledge of the City's environment and skills (both onboarding and continuing) required to provide Level 1 and Level 2 support as defined in Schedule 38?
Response
The-Unisys solutio·n will provide users with 24x7 access to the Unisys Service Desk and access over optional channels such as phone, web submission, and chat, as well as enable our Service Desk agents to have access to information that will also make the interaction personal, including the use of personabased profiles enabled in the ServiceNow platform. Our soh:Jtion will deploy a new End User portal that will allow City employees to interact with the City IT Department to quickly view the status of their tickets

Page 65 ends

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions
and service requests, view knowledge articles and frequently asked questions, and see important alerts related to IT. These will help to close the gap between the employees and the Service Desk.

When the Service Desk is working with a City employee, it is crucial to have personal insight related to the employee. Unisys will deploy Computer Telephony Integration (CTI) The CTI solution provides functionality that enables Service Desk agents to automatically get a screen populated with relevant caller's details either though automated Call Line Identification (CU) or through the caller entering a unique numeric identifier using the telephone numerical keypad. The user's information is enabled for the agent, who will support the user, with a popup already available on the agent desktop.

Unisys will provide the CTI solution within the ServiceNow platform and telephony environment and the service will be available for the agents.

Preliminary process overview:
• Unisys will liaison with CSC, ITSM Team, and network teams to establish direct access • Unisys Service Desk to get direct access (HTTPS) to ITSM from their desktop browser without any Terminal Service being the intermediate interface.
• Unisys IVR application servers to get direct access (HTTPS/SOAP) to enable Web Services functions with ITSM,· if applicable
• Unisys will co-ordinate and work with CSC and Avaya to ensure the Web Services coding is carried out by Avaya once the Web services request Template is populated as agreed on • The Employee list needs to be extracted and populated into a text file (Token File) containing only employee id without any special characters and characters to be small case, the file needs to be stored in the path specified. The Token file needs to be updated on a definitive interval. • Unisys will ensure the necessary Service Desk agents are trained and ready with the usage of the necessary tools which would enable CTI
• Post Development will be completed and confirmed the completion of Web Services. There will be an internal testing within Unisys and UAT and with CSC
• Post Acceptance of CTI feature working as expected, the CTI feature would be enabled on Production and activated
• Unisys to provide project management and regular reporting on progress per agreed project governance
Unisys has a resilient architecture put in place with CTI supported by backend systems spread across different Unisys locations, each backend servers backin up each other. This runs on Unisys Backbone MPLS Connectivity which has a backup link which acts a failover mode. This is Unisys infrastructure and any client adding on gets plugged to this environment. The base Unisys CTI architecture system is shared on the network diagram below.

Page 66 ends

(...,,..__.. ..
/
I
I
/
I
Unisys Avaya CTI Architecture

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions
___ 0 --v
t.u-1.a tn
~ . ,...,,.,, . ...,. .....
<~•
___ ,, ·
· f'•"""'l~ ')
Example of a ServiceNow Landing Page with a Valid Employee Information (The Name and Email are intentionally masked)
"••b (:,. cs ....... - ·-·- • •• >'}. ,,,,,,,_ · a ~.._,,,._ = '-----'••- 1:1 .....,_,,, _ C ""'--•••1- • 1•--
1---
.. I•• ••-• ,. •• ,.,,.,
, ............
, ''"' ...
c::ltc=l-i::::::l::Z.I :1:1=-•1m:::==-
--- ·--- •-.-····-···· .. · .. -......lhh
·~jtc,
a '&..--11.11.11
____ ,.,,,.,.,,, _____ _
--·-·-- ~---· ea-,,.-.._ . ....... ........ ,.... ......... __ _ Sample Screen of a landing page which would pop with caller information and Incidents created by the user.

Page 67 ends

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions
d) Describe your proposed solution for End-User self-help, including self-help plan and provision approach, platform, features/capabilities, effectiveness monitoring, and identifying and implementing approved recommendations for improved or expanded self-help services.

Unisys will leverage self-help tools through the Self-Service Portal as described below. The Portal is a focal point for tasks available to the end users for self-service. The portal allows users to see previous incidents and requests, as well as check the status of currently open records and provide updates, such as additional information, attachments and close I cancel actions.

Response
The Unisys solution brings the power of the ServiceNow platform, persona-based profiles, and the functionality of self-help together with the experience of Unisys through support of clients around the world.

Our solution is integrated with the applications in the ServiceNow platform, i.e. Incident Management, Problem Management, Change Management, etc. and allows the users to submit and view their incidents and service requests in addition to searching for knowledge articles to self-resolve their own issues, even before contacting the Service Desk. To optimize the ServiceNow Knowledge Management process, Unisys used Lean principles as well as improved screen layouts and field-level functionality to reduce the user input required to log, track, and manage knowledge articles. Our solution has an intuitive, rich, fulltext search functionality.

Additionally, contextual search functionality is enabled throughout the platform and fully accessible from the Portal for self-healing; it automatically displays knowledge search results when users enter the description fields for their new incidents. This helps users to deflect or quickly resolve their issues without involving Service Desk agents.

The Live Feed functionality allows users to add comments and discuss a knowledgebase article. This includes the ability to follow an article to see the updates and comments as they are made. This also helps users to deflect or resolve their issues without involving Service Desk agents. • Knowledge contributors can review and approve the publishing of articles in accordance with the knowledge process flow. The content submitted allows for better self-resolve results. The ServiceNow platform has a strong article analytic engine to track the overall effectiveness of the articles and knowledge environment. Both the City and Unisys will deploy a knowledge content strategy, naming content providers and approvers in both organizations to maintain quality and accuracy of all submitted knowledge articles.

Page 68 ends

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions
Unisys will work with the City on a Knowledge Centered Support (KCS) strategy. KCS practices involve collaborating, sharing, using, and improving knowledge. The goal of KCS is to solve a problem once and use the solution often. To take advantage of the knowledge that is available in the phases of Service Desk operations, KCS makes the knowledge captured by the support process available for reuse throughout the organization. other best practices involve updating articles to enable them to stay relevant and effective and retiring articles that are no longer relevant. Knowledge managers can run reports such as the top 10 articles and those most frequently viewed and used. This ability involves prioritizing and organizing highly frequented or used articles every 6 months.

Knowledge articles and help files will be updated to the knowledge platform in a prioritized fashion. SEO analytics will continue to drive the top issue types to both account for new knowledge articles required to support the City and to maintain up-to-date articles as the environments change. During Transition, Unisys will develop knowledge articles around the top 10 areas as shown in Section 2.1 .1.m.

In summary, the approach for Self-Service will result in improved services for users. The knowledge database will be easy to search and follow, thereby increasing self-help in the organization. The Unisys ESS portal has been optimized for seeking knowledge for self-resolve, the ability to submit and status incidents and requests, chatting online, providing feedback and accessing the users own dashboard all empowers the users to be more self-sufficient in their needs.

2.2.2 Service Desk Solution Overview
Instructions: Provide an overview of the Service Desk solution you propose to address the City Service Requirements stated in Enclosure D - Schedule 3B. Incorporate responses to common solution characteristics and description elements listed above. Limit 5 pages.

Response: Unisys has a deep understanding of the essential requirements to design and implement an /TSM platform for our customers. We have developed our own best-of-class too/sets by introducing proprietary processes and configurations. This deep knowledge and experience is transferable to CSC and is included with our solutions. Our methodology focuses on using highly maintainable configurations of the ServiceNow platform, which means customization is very minimal, if at all. This approach also enables integrations to be created to your external infrastructure systems, through orchestration and automation capabilities (i.e., password reset, SCCM, Nagios, SolarWinds, etc.).

Our goal is to not just replicate what is used in our global /TSM system but to implement only what is needed to deliver the required services to CSC that provide business value. With our knowledge of your current ITSM environment, we start by conducting a mapping exercise to compare data fields from the legacy to the new, ~gainst CSC's business requirements. We will then draft a data design document that

Page 69 ends

CITY OF SANTA CLARA
Schedule 2- Final Service Tower Solutions
will detail the configurations, from the foundation data to the workflow processes, business rules/logic, U/ components, and data tab/es/interfaces for CSC's specific functional modules. This exercise will be performed in consultation with CSC resources, as identified by CSC's transition team.

In our experience, we have stepped into multiple deployments where the contractors have over promised and been unable to meet their timelines and requirements for the client. Fast tracking such implementations has led to end-user dissatisfaction with a tool that is not fully ready for deployment and budget overruns.

Outlined below is a representative sampling of our recent engagements that demonstrates our expertise and knowledge from end-to-end.

Major wholesale food chain:
• Implemented Service Request Management for the entire enterprise • Managed incident, problem, and asset management
• Minimized service desk workload by optimizing resolution times • Optimized client's investments by completing deployment within schedule • Improved end-user experience via services which consistently met or exceeded KPls.

Automotive distributor
• Legacy system was an outdated version of HP Service Manager -• Implemented our Service Desk Optimization and Service Governance solution • Implemented end-user services
• Deployment completed on time and within budget
• Expanding services to ITOM modules (ServiceNow Discovery and Service Mapping).

Science and technology company
• Deployed zBoot (a clean implementation of the ServiceNow platform) • Full asset management, software asset management, Service Desk, and Field Services • Deployment completed on time and within budget
• Existing 6-year version of ServiceNow that was not working as expected.

United States Commonwealth Client
• Implementation for IM, PM, CM, Service Catalog, SLM, and AM • ODS integration for reporting
• Monitoring and Event Management

Page 70 ends

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions
• Discovery and CMDB integration
• SAP integration to Service Catalog and billing
• Implemented processes to provide consistency and support for their requirements.

State agency (Department of Justice)
• Old version of SM tool
• Deployed Service Desk
• Expanding services to include service catalog deployment and additional usage of ServiceNow • Deployment completed on time and within budget.

Unisys is confident that with our dedicated SeNice Management team and the ServiceNow platform, this a/lows us to meet the stated requirements and will provide CSC the flexibility to accommodate changes and growth in the organization. Our partnership with SeNiceNow augments our capability with our seNices.

Response
Solution Summary
The known City objectives and requirements are the base for the proposed Unisys solution. The Service Desk will be delivered from one of our Managed Services Centers (MSCs) in the United States. As required, the support will be in English.

The Service Desk will be the single point of contact for end-user requests, end-user submitted incidents, and infrastructure generated tickets. The Unisys Service Desk in the United States will be staffed and available 24x7
Main solution elements include the following:
• The Unisys ServiceNow platform for incident, service requests, problem, and change requests. • Direct input to ServiceNow interfaces using the web portal and chat. • The Unisys service desk will work with the City's service providers to resolve incidents. With proper entitlement and development of knowledge articles, the Unisys Service Desk will open incidents with

Page 71 ends

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions
vendors on behalf of the City, obtain status of open issues with providers, and relay additional information where appropriate to approved providers.
• Provision of automated password reset functions using Unisys Service Now features where applicable to the City's environment.
• Remote takeover for incident resolution and request fulfillment where applicable, using the Unisys implementation of the LogMeln remote support tool.
• Maintenance of a knowledge database of CSC-specific information, including incorporation of root cause analysis findings from problem resolution.
• Use of the VIP list supplied by CSC when handling user calls. Users that are flagged as VIPs will be handled with a higher priority for service restoration and for other cases where the request requires it be handled at a higher priority.

Service Desk Solution Components
Solution Baseline
With the introduction of the Unisys ServiceNow ITSM tool, users can contact the Service Desk over the phone, by web submissions at the self-service portal, and over chat channels. Unisys staffed agents to enable calls to be answered within 60 seconds. The Unisys solution does not include voicemail as a contact channel.

Unisys considered the following baseline:
• Contract term: 4+2+2 years
• Volume: 620 tickets per month
• Coverage: 24x7
• ITSM tool: Unisys' instance of ServiceNow
• Language: English.

Call Management
This service will provide the technical capability t_o receive calls from end users and route them to the appropriate Unisys Service Desk agents. Calls from end users will enter the Unisys Call Center from tollfree numbers or local direct inbound dialing telephone numbers. Interactive Voice Response (IVR) prompts will route the call to the proper agent or resolver team.

To make themselves known to the system, Unisys Service Desk agents will use a unique ID to log into the Unisys Automated Call Distributor (ACD). This ID defines the queues from which an agent will receive calls.

Page 72 ends

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions
The Call Center's IVR/Announcement capability can play either prerecorded announcements or announcements recorded as needed to advise on outages or extremely high wait times. This prevents wasted time by users and agents who report on incidents they already know. It also reduces call volumes and therefore wait times for widespread outages.

Queue management information will enable call center supervisors and team leaders to track call wait times, queue depth, and agent availability. It also will give them the capability to assign queues to additional agents during peak periods; this is called workforce management.

Call Management Reporting
This service will provide the technical capability to display real-time information and to retrieve historical information from our Call Management System (CMS). It also will provide management and City reporting, as well as information for supervisor and wallboard displays. The CMS will be configured as a High Availability solution with server locations across several Unisys data centers.

Chat Interaction
This service will provide the technical capability to initiate an instant messaging connection with a Service Desk analyst for assistance in case of trouble or questions. This way, a call to the Service Desk will be avoided.

Dashboards and Reporting
Unisys will leverage the reporting capabilities in ServiceNow for enabling all Service Level Reports related to ITSM described in the Schedule 4 Exhibit 1 document of the RFP. We will develop the dashboards and reports during the transition. They will be accessible to the City and Unisys leadership and allow taking early action on deviations and keeping service levels within the agreed parameters.

Incident Management Service
This technical service will provide the technical capability to manage the Incident Management function, allowing for an incident to be created, manipulated, and closed. This service allows for the various state changes needed to track an incident's life cycle, setting the appropriate priority, assigning incidents to the correct resolver group, and confirming that incident notifications are set. Service Desk analysts will use this service to create, update, and close incidents; to confirm that the appropriate state changes are made throughout the incident's life cycle; and to set the appropriate notifications. Service Desk analysts also will use this service to categorize and report on incidents.

Password Management
This service will provide the technical capability to manage policy definition, setting, management, and resetting of a password for access to a domain or defined application. The ServiceNow password reset tool is an available feature that can be used for password reset activities. Password reset will be initiated by a Service Desk agent or directly by an end user to "self-reset" his or her password. Password reset

Page 73 ends

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions
automation will be initially focused on the top 2 password request types identified by the call data and will be confirmed with the city during transition. In some cases, password reset automation may not be in scope due to the lack of standard integration between the environment and ServiceNow. Custom development of B2B integration to drive Password Reset automation is not included in the scope.

Problem Management
This service will identify and drive resolution of IT problems in the environment. The problem management team will use statistical measures and analysis methodologies to identify problems.

Leveraging a set of investigative tools, the problem management team will collaborate with system owners to identify the root cause of problems for all P1 and P2 Incidents. Upon validation of the problem's root cause, the problem management team will maintain oversight of the problem through an action plan and its implementation. Problem Management team hours of operation would be 5*9 during business hours. The turnaround for the Problem Management team would be 5 days for preliminary RCA and 10 days for final RCA
Knowledge Management
This service will provide the activities and tools for maintaining consistent, accurate, and timely documentation to support the City's in-scope products and services. Product or application-specific information will be validated with Unisys and the City content owners and then formatted as required before it is published in the Service Desk knowledgebase. Knowledge articles will be used by Unisys Service Desk agents and other Unisys resolvers for issue resolution and by end users who seek self-help.

The knowledgebase will be updated as needed to maintain consistency in resolution of issues.

Remote Takeover and Diagnostics
To initiate a remote takeover session and gain access to an end user's desktop or laptop, a Unisys Service Desk analyst will use this technical service. The analyst will gain control over the device so that work can be performed. The Service Desk analyst will use this service to perform diagnostic steps on the remote end point, determine the problem, and perform remediation steps on the remote end point. This service will entail the creation and storage of audit logs for each remote takeover session for later review or audit. To provide this service, Unisys will use the LogMeln password reset tool.

Service Level Management Service
This service will provide the technical capability to manage the Service Level Management function. This service will allow the description and capture of Service Level Agreements (SLAs) and to set threshold values and targets for the defined Incident Resolution SLAs described in the Service Level Reports in the Schedule 4 Exhibit 1 document of the RFP. This service will allow incidents and service requests to be tracked and measured against defined SLA metrics. Additionally, when the SLAs are not met, this service will facilitate the creation of notifications and escalations. It will capture actual performance values of the defined systems against the SLA targets.

Page 74 ends

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions
Service Request Service
This service will provide the technical capability to manage the Service Request Management function.

This service will allow a service request to be created, manipulated, and closed. This service will facilitate the various state changes needed to track a service request's life cycle and set the appropriate priority for the service request.

Unisys Service Desk Request Management team (this is a separate team from the L 1 Service Desk) will manage all the Fulfilment requests submitted by CSC end users. However, the requests related to aging tickets or escalation requests will be handled by the L 1 Service Desk team.

Service Excellence Office
The SEO is a global center of excellence at Unisys that coordinates with Unisys service delivery groups.

The SEO's goal is to drive improvement by focusing on the following:
• Resolution Optimization. The analysis of incident data to identify candidates and move resolutions steadily from higher skilled analysts ultimately to Level 0. Improve speed of each transaction through increased resolution at the right level.
• Defect Management. Reporting, analysis, and action plans for service defects, such as incorrectly assigned incidents, incorrect diagnoses, and excessive resolution times. • Customer Satisfaction (CSAT) Management. Improve Customer Satisfaction by eliminating the drivers of end-user dissatisfaction.
• End User Productivity Mean Time To Resolve (MTTR). Drive better end-user productivity by analyzing time taken to resolve across all resolvers.

2.3 End-User Services (Enclosure D - Schedule 3C)
Summary BAFO:
• Persona-based detail in ServiceNow and how it relates to End-User Services. • Detail of endpoint services and level 3 support definition. • Training detail and plans.
• Remedial maintenance service process.

2.3.1 End-User Solution Questions
Instructions: In addition to the General Solution questions in Section 4 above, Service Provider shall provide responses to each of the Service Tower specific questions below. Limit responses to each question to a half page.

Page 75 ends

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions
a) Explain how your proposed solution will address the City's desire to minimize unnecessary handoffs and follow ups of open tickets to Service Provider's End-User support staff due to insufficient knowledge of End-Users' ticket history during support activities.

Response
As the new ServiceNow platform is deployed, focus will be placed on training to capture high-quality information on the tickets. The accuracy and completeness of information captured on each ticket will be crucial to technicians arriving informed and prepared. Service Desk staff will be trained to ·capture as much information as possible by thinking through the eyes of the Field Services staff who will visit the end user. Field Services engineers will thoroughly review the ticket information and the employee's history to confirm a complete understanding before making the visit. Unisys will conduct quality audits of the tickets to verify that ticket information is captured properly. The End User Services (EUS) leader for the City will also enforce and conduct quality audits to verify that our Field Services engineers are taking the time to review ticket information before making visits. The Unisys approach will also focus on misrouted tickets and tickets that could have been handled without a handoff. Quality analysis and efforts for these two areas will lead to fewer mishandled tickets and improved resolution on the first contact or opportunities to improve the self-help features of the end-user portal.

Page 76 ends

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions
b) The City is interested in moving more toward a people/persona policy based set of standards for its end-users. Please describe how would you propose to implement a people/persona policy based standards approach to manage City end users given the different departments and their differing needs.

From a persona perspective, Unisys will implement three (3) personas: End User, Operations Management, and Executive persona for the Self-Service Portal. • Personas are not roles and are more in the lines of user experience that span across multiple applications. A person with an executive persona has a consistent executive-level experience across the Portal, i.e. dashboards will be displayed. A persona describes key characteristics of users expressing how they view the world; they dictate user experience, roles dictate user access rights to data.
• Roles are typically application specific and are directly tied to data access within the application.

Users could belong to the same persona (user experience) but have different set of roles (data access). Personas will comprise a base set of roles and permissions and admins can assign additional roles for the user for specific access.

Examples of poor candidates for personas: report editor, admin, dept 327 'manager, finance application user, etc.

As stated previously, the three (3) personas that will be implemented for the ServiceNow Portal are:

End Users, Operations Management and Executive personnel. Within the ServiceNow platform, this is achieved by 'group' permissions in the system.

Example:_ Alva.Pennigton is an End User in the system. Alva does not have any permission roles defined in the system to her. When Alva logs in to the Portal, she has the capability to submiUstatus incidents and ervice requests, search knowledge, etc. Bernard. Laboy is an operations user that can approve knowledge articles, approve change requests (via the CAB since he belongs to the CAB approval group), and can work incident tickets. When Bernard logs in to the Portal and/or the back end system, the approval widget and link is exposed to him whereas it is not available to Alva.

Response
The ServiceNow ESS platform provides users with persona-based access to the system, presenting them with the right information that applies to their roles and specific organizational needs. This will allow users to be able to find information faster, work smarter, have a better interaction with IT and business, and ultimately make a right decision. During the transition to ServiceNow, Unisys will lead the City through a process to review the right profiles that will drive the highest impact on the environment.

Persona-based access to information is complemented with role-based access to application features and capabilities in the ServiceNow platform. Role-based security defines user access at the module,

Page 77 ends

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions
form, and field levels, so that the right to read, tailor, create, and take ownership of items such as tickets, configuration items, and service catalog items is configurable according to roles and organizational requirements. This capability can be assigned to specific roles, groups, departments, or positions in the organization.

The Service Catalog automatically displays requests related to end users, depending on how the requests are published and made available. This validates that a user only sees requests that are relevant to his or her role. Further restrictions or additions can also be made based on the end user's role, Unisys will look to evaluate the various user types, grouped by roles and personas; understand the City's needs to create an appropriate design; and provide a suitable portal that will provide City end users with ease of use and benefits.

In summary, general users can see a different catalog based on their role, but a manager can see their teams' access. Executives can be configured to see dashboards and only create VIP requests and incidents, etc. Users can easily be given application permissions to perform certain tasks such as change approval.
c) The City is interested in improving customer intimacy through a Service Provider offering where Service Provider staff would be made available to the City's end-users on a scheduled, recurring basis (similar to a "genius bar"). This venue would provide the end-users with the opportunity to bring issues to the Service Provider (e.g., questions around device functionality, break/fix issues, etc.). Please indicate your proposed approach to providing this solution, including proposed frequencies.

Response
Unisys proposes the deployment of the TechCafe. This TechCafe brings a higher quality touch and intimate experience that City employees will embrace.

Equipped with technical and material resources, the TechCafe delivers a flexible, efficient and intimate service to increase workforce productivity and performance. The TechCafe will provide a range of IT support services targeted at top incidents and requests that are commonly seen in the environment, including:
• Resolution of hardware and application issues for in scope hardware and defined applications • Software installation and configuration of approved software applications • Provide basic questions and answers around common end-user devices and applications.

Unisys will work with the City to identify an ideal central location for the TechCafe- a location with easy access by the largest number of End Users. Based on our experience, Unisys recommends a regular time once each week to ensure consistency with the end-users. The initial duration would start with 4-hour sessions and adjust reasonably based on staffing demand. A communication campaign will be developed to announce the grand opening and periodically remind users of the value of the TechCafe. A key process that will be followed is the use of the ServiceNow platform to capture the interactions at the

Page 78 ends

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions
TechCafe so the demand and impact to the business can be tracked and measured to include customer satisfaction.

The City will be responsible for the facilities, furnishings, equipment, transportation, connectivity, and a secure storage facility.

Page 79 ends

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions
d) The City is interesting in providing City departments with a Service Provider "road show" whereby the Service Provider's End-User staff would visit each department on an established and recurring basis. These enhanced customer touchpoints would provide the department end-users with an opportunity to help with any issues department personnel may be experiencing or answer any questions they may have. Please indicate your proposed approach to providing this solution, including proposed frequencies.

Response
In addition to the TechCafe, Unisys will establish a rotating "road show" with the City that deploys our field engineers to the various departments. This roadshow will provide another outlet to City employees to receive assistance with their top and most common IT issues and requests. Unisys proposes the largest department like PD would be visited once every 4 months, other major departments at least once every 6 months, and the smaller departments once per year. This schedule will be adjusted based on the utilization by each department with some departments being increased in frequency and perhaps others reduced. The schedule will be influenced by the TechCafe proximity and cadence to certain departments and City employees. Additionally, the "road show" format, length and actual participants will be adjusted based on the types of questions being asked and the types of issues being resolved. A communication campaign ½'.ill be developed to announce the schedule and remind users of coming event. Finally, the incidents and requests resolved at the "road shows" will utilize the ServiceNow platform so the demand and impact to the business can be tracked and measured to include customer satisfaction.

Page 80 ends

C ITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions
e) The End-User experience is important to t~e City. At the same time the environment is rapidly changing (e.g., mobility, 0365, personas). As such, end point engineering is foundational to driving many City transformation initiatives and the City requires a strong end point engineering solution. How would you propose to provide an end point engineering team to successfully deliver these critical services?
Unisys will leverage the instance of the AirWatch MOM tool provided by the Department of J~stice to define and enforce City-approved device policies (e.g., security, accessibility, data). The Unisys team will also leverage this tool (for mobile d!:Jvices) along with Microsoft SCCM for laptops and desktop devices in the departments, to make apps available to users when requested/approved apps are outside the core software provided on initial device images.Unisys will provide the following Endpoint Services:
• Desktop Operating System Image Development and Management • Application Packaging Services
• Electronic Software Distribution
• Patch Management
• Endpoint Security Management and Event Monitoring
• Level 3 Engineering Support.

Unisys will deliver these services with an onsite-based dedicated staff of three fulltime Endpoint Engineering Team members with a fourth onsite dedicated team member to provide hands-on EUS technical team leadership and project coordination over the Endpoint and Desk Side engineering staff.

The Endpoint Security Monitoring and Management service will be provided by remote staff to ensure constant monitoring and reliable responses to Anti-Virus and Anti-Malware related events reported while the onsite team members are engaged on projects and day-to-day service delivery of the other Endpoint services. The Endpoint Security Monitoring team will support the currently used tool (SCEP), and if this toolset is replaced, the replacement toolset will be supported for like functionality (Anti-virus and Antimalware).

As new application of technologies like Office 365, Persona's, and mobilization initiatives evolve the End User Experience, the Unisys Endpoint team will support these changes at the departmental level through several means, including: department-specific Image Deployment task sequencing; standardized desktop application configuration management; diligent knowledge management practices, and close collaboration with Level 1 and Level 2 Support to provide effective continuity of services to the departments through all levels of the support process an issue may escalate through. As departments are transformed, Device Images will be adapted to unique departmental application requirements through task sequences that are applied with the image to adapt it to specific requirements within the target

Page 81 ends

CITY OF SANTA C LARA
Schedule 2 - Final Service Tower Solutions
department. When new applications are introduced, Endpoint will coordinate with the Application Team and City Departments to establish and capture standardized app settings and configurations are applied to app packages to be used by the department. As change is introduced and departments evolve, the Endpoint Team will support change processes by harvesting resolution data encountered while solving new and change-related issues into various types of Knowledge Base articles to provide Self-Help, Tips or "Work-Arounds" for Known Problems, and other instructional documents. These will be published and accessible to departmental End Users to assist them through the changes and challenges that surface.

As the End User environment evolves at the City, Unisys Endpoint will ensure device images evolve with it, devices are kept secure through monitoring and patching of vulnerabilities, standardized application configurations ease learning and use of the devices, problems are easily addressed with self-help articles and up to date knowledge-base articles, and effective support through all service levels is readily and proactively provided.

2.3.2 End-User Solution Overview
Instructions: Provide an overview of the End-User solution you propose to address the City Service Requirements stated in Enclosure D - Schedule 3C, as indicated below. Incorporate responses to common solution characteristics and description elements listed above. Limit 5 pages.

Response
Unisys will require certification for the role required to do their function. This training and certification will be part of the Unisys resource performance plan. In addition, Unisys will review the technology roadmap with the City, during each of the mentioned meetings, in determining what upcoming technology skills may be required. Unisys agrees to provide the training and hold the team accountable to complete it. This mirrors our established guiding principle to improve our skills for the effective and strategic use of emerging technologies.

Finally, Unisys will leverage the City specific Knowledge Base and use it as required training, approximately quarterly, with end-user and all help desk staff. All new staff will be required to take the Knowledge Base training prior to engagement.

The Unisys solution will focus heavily on a dedicated onsite team of professional Endpoint Operations engineers and Field Services engineers who are focused on these crucial services. This team will use key tools such as the Unisys provided ITSM platform of ServiceNow. Microsoft System Center Configuration Manager (SCCM}, and AirWatch are City provided tools which the team uses to manage mobility devices.

The ServiceNow ITSM tool captures incidents and requests that require Field Services support and enables connection of the right resources to the right asset or incident. Additionally, our commitment to developing and using best practices drives design efficiencies, promotes reusability, improves performance, and enables expanded capabilities.

Page 82 ends

Endpoint Operations Services Summary

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions
The Unisys onsite dedicated Endpoint Operations team will approach management of end-point devices through a sharp focus on the following:
• Device Image Management - Reliable creation, maintenance, and deployment methodology of base operating system images for devices that are reliable, patched up to date, and configured for an optimal user experience on supported devices
• Enterprise Management Platform - Leveraging Microsoft SCCM, this platform will provide reliable image deployment, electronic software deployment, patch management, inventory data collection, software metering, and related reporting functionality to enable end-point devices to be well managed and equipped to meet CSC's operational requirements.
• Group Policy Management - Management of Active Directory Group Policies designed to enhance and safeguard the end-user experience while providing governance for use of end-user devices • Endpoint Security - Maintenance of a safe computing environment and data integrity through monitoring, response, event management leveraging antivirus, antimalware, and encryption (Microsoft Bitlocker) functions provided by the operating systems and by System Center Endpoint Protection
• Desktop Application Management - The Endpoint Operations team liaises with the Application I Management team to gather optimal configuration settings and requirements of end users and to have those packaged with the commercial software for electronic distribution to end-user devices in a standardized, reliable configuration.

These services will be provided by Endpoint Operations experts who work on site and face-to-face with the end-user community while seeking to drive innovation into the processes and tools used. They will leverage the expertise found throughout our global community of Endpoint Operations experts, including some back office non-client facing expertise provided from various Unisys Service Centers.

Field Services Core Service Areas
Unisys solution assumes that ticket volumes will be consistent with the current environment (approx. 1,490 annually). To the extent such volumes materially change the City and Unisys will review and equitably adjust the City's Field Services requirements and associated pricing.

VIP Support: Unisys will work with the City to define specific onsite support for VIPs in the ServiceNow Platform. For other similar engagements, Unisys recommends a pool of pre-imaged equipment that is stocked at VIP locations. Whenever an incident cannot be (or is not expected to be) resolved within a VIP restore SLA, the VI P's workstation will be replaced to allow the user to continue to work as quickly as possible.

Page 83 ends

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions
Deskside Support Services: Providing support to remediation of software and connectivity issues that cannot be resolved by remote resolution techniques.

Installs, Moves, Adds, and Changes
Installs, Moves, Adds, and Changes (IMACs) occur as ad hoc requests or as planned, large-scale projects. Unplanned or day-to-day !MAC activity is handled in the same way as hardware service requests, with call placement using the standard service request process: individual requests for IMACs go through the Service Desk or the Unisys Request Coordinator. A separate service request will be logged for each device or unit that is subject to the !MAC activity.

IMAC Service includes the following activities:
• Installations and De-installations - Upon equipment arrival, Field Services engineers will check for equipment damage, install and configure the equipment, load the software; and test it for full functionality. If a problem is detected, it will be escalated and necessary actions taken to enable device/system operability. End-user familiarization will be provided for the new equipment and software.

Installation of additional software applications (packaged applications that are not included in the standard City image or applications that cannot be packaged) will be done as a separate !MAC with support materials that the City will provide to perform the installation. • Moves - Field Services engineers will de-install equipment according to the move schedule and prepare it for transportation. Once the equipment is transported to the new location, they will reinstall the equipment and test it for full functionality, using a predetermined installation script. • Adds or Changes - Field Services engineers will unpack the product, conduct a physical inspection, set the equipment up or install new or updated software, and connect and functionally test the equipment.
• Replacement of peripherals and reconfiguration of software • De-installation of the equipment
• Disposal of the equipment is beyond Unisys scope thus a third party will manage • Installation of software when Service Desk agents cannot install it remotely • Project-based refreshes (periodical changes) of desktops and laptops.

Unisys IMACD Coordinators will plan and manage the IMACD schedule as agreed with the City or with individual end users and confirm the correct operation of an installed or modified device. An IMACD procedures guide will be produced and agreed with the City and be part of the operations manual used by Unisys Field Services engineers, which will lead to consistent, repeatable execution of services. IMACD Coordinators will perform the following activities:

Page 84 ends

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions
• Prepare the target location for a trouble-free MAC
• Identify and verify cabling and electrical power
• Document changes or additions to cable and electrical power if required for performing the IMAC • Inform CSC of site changes or additions required
• Understand and documE:nt requirements for equipment connectivity • Report correct IMACD completion
• Act as an internal single point of contact for Unisys Field Services technicians for IMACD activities.

For IMACDs, Unisys IMAC Coordinators will confirm equipment and the Unisys resources needed are available to comply with the contracted SLAs.

Remedial Maintenance Services
Unisys Hardware Support and Repair functions provide the resolution of hardware-related problems with desktops, including repair or replacement of components or entire units, rebooting, isolation from the network, and diagnosis and corrective actions. Our Hardware Support and Repair functions can also be performed remotely by remote control or on site by deskside support or Smart Hands support.

In a hardware failure, the Unisys Service Desk will call the OEM to handle the issue if a unit is under warranty.

If the unit is under warranty, a Unisys Field Services technician will check the unit and decide whether the unit is reparable. If the unit is reparable, our Field Services technician will engage the OEM and adhere to their standard warranty repair process for the unit. If the·unit is irreparable, the City will purchase a new unit, which Unisys will install. In case a hard disk failure, Unisys will reimage the PC with the City image.

Unisys support of printers and mobile devices will extend to third party vendor maintenance when applicable.

Smart Hands Support Service
This service provides Unisys Field Services engineers to assist in the resolution of other enterprise hardware issues that cannot be completed by remote means and require a physical presence. This can include hardware configuration and use, complex how-to requests, and sporadic fault identification and rectification.

TechCafe
Unisys describes our approach to the TechCafe in our response to RFP requirement 2.3.1 c.

Road Shows
Unisys describes our approach to road shows in our response to RFP requirement 2.3.1d.

Page 85 ends

Additional Services

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions
After each field service visit, a Unisys Field Services technician will perform the following activities:
• Check the health of the unit as preventive maintenance • Check the asset record, escalate issues, and update the asset record if necessary • Propose actions for the following items:
o Parts
o Swap units
o Desktop and laptop purchases
• Check the stock level and propose further actions.

Page 86 ends

CITY OF SANTA CLARA
Enclosure A-Appendix A BAFO

2.4 Enterprise Compute Services (Enclosure D - Schedule 3D) Summary BAFO:
• CMP deliverables.
• Business Continuity and Disaster Recovery planning detail and process. • Unisys outside SME provided for design and engineering.

2.4.1 Enterprise Compute Solution Questions
Instructions: In addition to the General Solution questions in Section 4 above, Service Provider shall provide responses to each of the Service Tower specific questions below. Limit responses to each question to a half page.
a) What is your proposed solution to provide cloud orchestration (SI) services for the City's evolving cloud environment (e.g., tools, processes, etc.)?
Response
The City has a "Cloud First" strategy in place for new applications and upgrades to existing applications.

They require that the infr~structure activities performed on premise be available and easy to perform in the various cloud provider environments that are currently in place and those of future providers. Cloud orchestration is essential to continue. to maintain the costs and timeframes to implement new applications and services in the cloud. For orchestration of cloud services, Unisys proposes to enable Infrastructure as a Service (laaS) Solutions and a cloud ecosystem for the City by establishing a robust Cloud Management Platform (CMP). This will be achieved through the development of a City cloud strategy that includes service provisioning that leverages ServiceNow catalogs, orchestration, release management, and security management. Unisys is positioned to bring the Unisys Cloud Management Platform as part of the transformation services. This approach will be vendor neutral if multiple cloud providers are used to provide the lowest cost for performance to manage ongoing infrastructure cost. This approach will remain seamless to the other underlying cloud infrastructure. By leveraging the Unisys CMP, the City will move to a more agile approach that leverages DevOps for infrastructure management.

This orchestration approach will be driven by the Unisys Cloud Infrastructure team, which is jointly led by the applications and infrastructure program managers and supported by Unisys CMP experts. This approach will enable the aspects of the Cloud First strategy such as contractual items, security including Active Directory integration, interoperability, and SLAs to be managed properly. Unisys successfully worked with the City to drive Cloud First initiatives. These initiatives include the migration of City websites from internal hosting to a cloud provider (Vision Internet), Accela Customer Relationship Management (PublicStuff), Questica Budget, and Office 365, which is in progress. Additionally, we supported Public Safety applications such as replacing Patient Care with lmageTrend, CAD-to-CAD, and various other Police Dispatch applications.

Page 87 ends

CITY OF SANTA CLARA
Enclosure A-Appendix A BAFO
Deliverables:
• Installation and configuration of the Unisys Cloud Management Platform (CMP) o Ongoing support and maintenance for the Virtual Appliance o Ongoing support and maintenance for the integrated software components o All licensing for products provided by Unisys within the CMP platform o Configuration of templates and scripting for standardized virtual resources • The CMP services are listed here:
o Orchestration
o Rapid Deployment
o Automated Provisioning
o Self-Provisioning and Self-Service Interfaces
o Third Party Cloud Provider Service Aggregation
o Business Workload Analysis
o Recommendations and Mapping
o Audit Support
o Analytics and Reporting
o Multi Source Integration
o Automated Run Book execution
• Configuration and modification of ServiceNow catalogs to facilitate Service Requests for CMP SelfProvisioning and Self-Service Interfaces o Initial configuration of CMP and ServiceNow Service Catalog objects is provided by a Unisys project team (external to the delivery staff) that specializes in CMP deployments. Postimplementation updates to the catalog will be handled as Service Requests and will be processed by Unisys offsite support teams.

Client Responsibilities and Assumptions:
• The Client will provide virtual resources, CPU, RAM, storage, and network, which meet the requirement for the CMP virtual appliance to be provisioned by Unisys.

Exclusions:
• Licensing for Private Cloud Hypervisor or Operating Systems • Licensing for Client applications

Page 88 ends

CITY OF SANTA CLARA
Enclosure A-Appendix A BAFO
• Migration Services of physical or virtual workloads to or from the Public or Private Cloud. b) Describe your proposed collaboration solution, including setup, maintenance, support, City EndUser training approach.

The Unisys on-site team will work closely with City departments to encourage and seek more adoption of SharePoint (CS/) for collaboration within and between departments.

1. Advise departments of applicable new functionality as it becomes available.

2. Conduct monthly user group meetings to include members from each department to a. Introduce new features
b. Review departmental requests
c. Discuss issues
d. Deliver brief training sessions on relevant functionality . .

3. Conduct deep dives with individual groups to develop detailed requirements and configure and test the solutions.

4. Develop training materials (video, class-room training, FAQ's, QRG's, etc) which can be delivered individually or in a group setting.

5. Redesign the cuffent CS/ (SharePoint) Intranet Portal into SharePoint Online (0365) making sure to:
• Perform a fitgap to become familiar with O365/Sharepoint Online features. • Analyse the City's desired new features for Level of Effort to implement and include in the workplan.
• Cleanup the SharePoint 2010 and prepare for migration to 0365. • Migrate the current content to SharePoint Online.

6. Maintain the current SharePoint 291 O Environment.

7. Maintain a detailed request log, which will be a part of the workplan. This will ensure that requirements are tracked and prioritized and also analysed for LOE.

Response
When faced with a diverse group of end users in 15 departments across the City, it is important to have a strong focus on training to enable the end users to quickly embrace changes to their applications, technologies, and services. Unisys uses Microsoft SharePoint as the collaboration platform to improve productivity and business process automation. We will also leverage the new ServiceNow end-user portal

Page 89 ends

CITY OF SANTA CLARA
Enclosure A-A-ppendix A BAFO
to provide additional opportunities for collaboration and training. As part of our approach to end-user training, we will meet with end users to gather requirements, create a proof-of-concept, conduct a review to identify and make final adjustments, perform testing (with a strong focus on user acceptance testing), and then send the release to production. We will develop customized training material (e.g., video library, quick reference guides, and webinars) that is relevant to the enterprise and the individual user, delivered in a group setting, or conducted one-on-one depending on the requirement. Additionally, to complement our approach to· end-user training, Unisys will conduct a monthly web user group meeting that will be attended by representatives from each of the City's departments and chaired by the IT Department. Our approach to end-user training has led to increased end-user satisfaction. Examples of this end-user satisfaction include team sites for the Finance Department's Comprehensive Annual Financial Report to automate the production of the City's financial statements, an agenda coordinators team to track the status of council agenda items; and the police communications team site to enable sharing of critical information across shifts in Police Dispatch.
c) Describe your proposed mobility solution including requirements development, support of the City's current AirWatch Saas tool, and End-User access approach and security.

Response
The City requires a Mobile Device Management (MOM) solution that can manage mobile devices across various departments, particularly for emergency responders such as the Police and Fire Departments.

This is important because the City's data on devices must be protected. This protection will be achieved through encryption and password protection. Unisys can remotely wipe lost and stolen devices.

Additionally, software deployment can be effectively managed to maintain a common look and feel for devices. Our solution continues the use of the AirWatch Saas tool, which is owned by the Department of Justice to successfully provide this service today. More than 250 devices from various departments are registered and protected from data theft.

Unisys will continue to work closely with the AirWatch product and maintain the MDM solution roadmaps to enable AirWatch and the roadmaps to continue to meet business and security requirements for the City.

2.4.2 Enterprise Compute Solution Overview
Instructions: Provide an overview of the Enterprise Compute solution you propose to address the City Service Requirements stated in Enclosure D - Schedule 30, as indicated below. Incorporate responses to common solution characteristics and description elements listed above. Limit 5 pages.

Response
Unisys proposes to provide the Enterprise Compute Solution illustrated in Exhibit 2.4.2-1.

Page 90 ends

Enterprise Solution Services
-.

CITY OF SANTA CLARA
Enclosure A-Appendix A BAFO
Exhibit 2.4.2-1 . Proposed Enterprise Compute Solution.

The City provides business services to its employees and citizens through a robust and secure enterprise architecture that uses City-owned data centers, Saas solutions with third-party application providers, and increasingly through work packages deployed with cloud providers. This architecture must be secure and available anytime, anywhere 24x7. A highly available, secure, resilient, and redundant enterprise compute environment is a must to enable the critical services that a city like Santa Clara offers to its citizens.

Unisys will provide the City with a systems operational management and project services capability for its data centers, cloud providers, and distributed computing environments. Our Enterprise Computing Services will also include management of systems, network, security, storage, infrastructure, database support, and system consolidation and integration. This will maintain high availability of the City's business applications with little to no downtime beyond planned outages. Unisys successfully demonstrated our commitment to providing and improving this high level of service with our ongoing program to move from a physical server environment, supported by a network with multiple points of failure, to a High Availability virtualized compute environment that is about 85 percent virtualized. We have two data centers that run on a high-speed 10 GB meshed core network that has improved redundancy, availability, and performance. Additional efforts during the rebuild of data centers led to a greener footprint that saves the City 60 percent on power.

Enterprise Computing Services
Unisys Enterprise Computing Services include the following services.

Page 91 ends

CITY OF SANTA CLARA
Enclosure A-Appendix A BAFO
On-Premise Application Infrastructure Management Support: Unisys will provide on-premise application infrastructure management support for critical City applications such as Computer-Aided Dispatch (CAD), PeopleSoft, and Harris Northstar.

Third-Party Cloud Services Support: Unisys leverages Azure for Office 365 and AWS as the cloud provider for the City. We yvill support future cloud providers that will use the DevOps and SAFe approach for the City and departments that serve the c9mmunity. Using the Unisys Cloud Management platform, we will allow for improved orchestration of the cloud infrastructure as it grows to support the City's goals.

This is part of the cloud maturity model and also part of the cloud continuum that is already in progress.

Enterprise Computing Operations: Unisys Data Center Operations Management (DCOM) solution is an ITIL v3 best practice based operation management approach. DCOM uses standardized processes and procedures that enfold the City's IT environment to provide consistent and repeatable support processes.

Moving to ServiceNow will accelerate transformation by providing integrated request management as part of the Service Catalog. ServiceNow integrates with the current on premise environment and with the City's Cloud First strategy. Unisys has successfully implemented and deployed this feature for other clients. This process will drive costs down, improve consistency, and provide a just-in-time approach for systems that require additional resources to meet citizen and department demands. Enterprise computing operations will also organize the communication between different compute towers and coordinate them with project teams for streamlined execution in daily operations and special projects.

Storage and Data Management: The City and Unisys have worked together with storage and data management strategies to support the City's departments and special projects. This includes reviewing ~ the current storage performance and its capacity, as well as evaluating the demand. Unisys will continue to drive data and storage solutions toward the cloud to maintain high availability of data and a scalable infrastructure, as well as improve disaster recovery options.

Physical Database Support: Unisys provides database support for SQL and Oracle engines as part of the current contract. We will continue to provide databases with physical support. This support is provided by remote Unisys staff, but with the continuous transition to the cloud, Unisys will bridge the cloud barrier further. Our expansion of the cloud footprint at the City will further drive the maturity process and continuous improvements in the environment.

Application Support and Web Support: Application and web support is provided by on site staff and remote resources. Unisys will continue to support websites and applications with the same approach. We will keep the current SLA for after-hours support on mission-critical systems. These systems include City websites, PeopleSoft, Public Safety applications, and Utility Billing.

IT Service Continuity and Disaster Recovery: Service Continuity and Disaster Recovery are limited to using High Availability servers with failover connections and multiple ISP feeds. IT Service Continuity and Disaster Recovery (SCOR) will further enhance the use of cloud providers to spin up mission-critical systems and to support offsite data replication in a secure public cloud. Unisys will test these processes once a year to deliver readiness and to meet the SLAs for the City's SCOR. This advance will improve the

Page 92 ends

CITY OF S_ANTA CLARA
Enclosure A-Appendix A BAFO
support that City citizens receive. It will also provide critical departments with the tools that they must have to continue service if something should happen to the on premise mission-critical systems.

Unisys will provide to the City of Santa Clara Business Continuity and Disaster Recovery Planning (DRP), including the identification and classification of systems that require a Disaster Recovery (DR) plan. The disaster recovery plan, based on the City's RTO and RPO requirements, will include a detailed, step-bystep document which is to be followed during DR testing and/or when a Disaster has been declared. This will require the City to make key technical stakeholders available and responsible to participate in Disaster Recovery Planning Workshops. These workshops will be scheduled within the first three (3) months of the new contract. The Disaster Recovery Plan will be presented back to the City of Santa Clara within 60 days of a successfully completed workshop. The Disaster Recovery Planning is delivered by a separate from the Unisys delivery team but will require input from key technical support staff.

Upon mutual acceptance of the DR plan, Unisys will schedule a test of the DR plan with the City of Santa Clara at a time that will introduce the least amount of impact to the City. Unisys will execute the plan within the first twelve (12) months of the new contract and one (1) time per year for duration of the partnership. Unisys will provide a report with the test results within 15 business days. Upon a DR test failure, Unisys will work to remediate the issue and schedule a retest within 90 days. The Disaster Recovery testing will be led by DRP external team members and Unisys delivery key technical support staff. DR testing is assumed to occur during non-business hours to minimize impact to CSC agencies and constituents. All charges for DR planning and test exercises are included.

Remote Access: Remote access to systems and data for authorized persons is imperative for the City to support the community. This will allow citizens, employees, and City departments to function, especially as the location for these systems shifts from on premise to cloud-based solutions. Reliable remote access is key for the City to meet changing needs and includes the current VPN Client, Direct Access, and Office 365 methods.

Messaging: The Office 365 project is underway. Once this project is completed, Microsoft will continue to enhance it. As new features are added, they will have to be extended to the field for City personnel.

Collaboration: Across City departments and the various projects underway, collaboration and controlled access are important to have inside public buildings and around the City. Controlled access is important to support effective teamwork on the project teams.

Mobility: As already detailed in our response to RFP requirement 2.4.1 c, Unisys worked with AirWatch and MOM while collaborating with the City to create an environment with the ability to support mobile devices. As requirements change, including those for GIS, the Landscape application, and the Public Works Road Conditions application, mobility access will play an important role in achieving effective communication between internal personnel and City of Santa Clara citizens.

Network Services: Unisys will continue to provide a highly available network that allows City employees and citizens to access the applications and services that align with the City's goals. These services will leverage monitoring tools and the ITSM platform to quickly respond to issues and resolve them. This will

Page 93 ends

CITY OF SANTA C LARA
Enclosure A-Appendix A BAFO
include working closely with City telecommunications and fiber partners to maintain a reliable and available network. These are the same services that Unisys provides today and will continue to do so for the duration of the partnership.

Design and Engineering: By leveraging our experience with the design and engineering of network and compute projects, Unisys can recommend a cost-effective approach to meet strategic City project requirements and department goals. We will verify that the right success measurement tools are in place to guide our successful and cost-effective deployment of projects and concurrent operations for the near term and long term. Unisys has included in the services a Unisys Client Architect and technical Subject Matter Experts (SME) to facilitate and oversee design and engineering for the City's IT estate. These individuals are the conduit to the greater Unisys engineering teams and will bring other resources to bear as requested by the City. Reasonable requests for design review or engineering oversight will be handled in this manner. Requests for larger or more complex solutions may require additional staffing which will be reviewed and approved prior to any billable events.

Provisioning: As the City's needs change, the network and security environment will also change. Our network team handles the need to provision new equipment or reconfigure existing equipment to maintain high security. Unisys will use ServiceNow, Nagios, Cisco Prime Infrastructure, Zscaler, SolarWinds, and HP ArcSight to track changes arid monitor the environment. These changes often require cross-technical tower support and confirmation of change in the environment. We will leverage those tools to execute, track, and monitor events. These are the same services that Unisys provides today and will continue to provide for the duration of the partnership. Innovation opportunities will be brought forward to the City as they become available for review.

Transport: Transport of data in the ever-growing, always-connected environment is important for having connectivity and control. The use of mobility and the migration from City-owned to employee-owned environments will imply new challenges for monitoring and managing access. Using tools such as AirWatch integrated with Service Now and HP ArcSight will allow for access and improved security.

Operations and Administration: Several key components make up part of the Unisys approach to operations and administration. Operations and administration follow ITIL v3 best practice principles by leveraging ITSM and ServiceNow, which will deliver enhanced consistency across technical towers.

Monthly operations review meetings and "shift left" analysis will better support first-time resolution and faster resolve time for incidents. Items discovered will be addressed proactively to maintain the highest level of service.

Documentation: Unisys will create, maintain, and update standard operating documents monthly, quarterly, or yearly. These documents include those for mission-critical systems, processes, and procedures.

Security Planning and Operations: Unisys will provide security management and administration across technology stacks for ttie City. We worked with the City to define the initial security policies document.

The initial document incorporates current security policies as well as Unisys experience and best

Page 94 ends

CITY OF SANTA CLARA
Enclosure A-Appendix A BAFO
practices. These security policies are managed under the change control process. As requirements or technology change, Unisys will review each security policy document yearly, thereby improving operational procedures and governance with new knowledge acquired through our ongoing service engagement experience. •
Firewall Management and Security Intrusion Prevention and Detection: Unisys proactively monitors and manages the City's firewalls, network-based intrusion detection system (NIDS) devices, and hostbased intrusion detection systems (HIDS) for suspicious activity and known intrusions. When an event that affects the firewall or the security of the protected assets occurs, Unisys will evaluate the event, prioritize it, inform key stakeholders of the situation, and act accordingly to rectify the problem. We will attempt to notify the City before unplanned changes to the firewall or IDS-related components. However, in particular circumstances, Unisys may need to shut the firewall down to prevent an active attack from damaging City assets or the firewall itself before communicating with authorized contacts. Unless otherwise stipulated, the City will authorize Unisys to shut its firewalls down if we detect a security breach of the firewall that can affect critical systems or confidential information.

Managed Security Services: These services include physical access tracking, prevention of intrusions to enterprise systems security, and detection as part of an ongoing effort to provide the most robust protection possible against physical terrorism and cyberterrorism.

Enterpdse Computing and Network Services follow the same requirements and principles, which include the following:
• A continuous improvement methodology that leverages a service of "shift left," review of Continuous Service Improvement and Innovation Program results, performance metrics, and key performance indicators. This methodology will allow us to establish improvement areas to help find the critical path across technical towers and team with City counterparts to leverage the highest service levels and to meet continuous improvement goals.
• Innovation brings new technologies and methods to help with life cycle management that will support the City's Cloud First initiatives. Unisys will leverage new tools to improve our cloud strategy in the Application Services commercial off-the-shelf software (COTS) portfolio on a case-by-case basis.

COTS will move to the cloud when deemed appropriate. With our mobile strategy, citizen services and overall engagement will be improved. Innovation will include several components such as Wi-Fi capacity, a new CAD Resource Management System, and integration across City departments to better serve the community.

Support requirements: Unisys will provide 24x7 Remote Service. We will perform non-incident and event activities during the City's normal business hours. Normal client business hours are 7:00 a.m. to 7:00 p.m. (Pacific Time), Monday through Friday. Unisys will provide onsite support during normal business hours. We will provide onsite after-hours support for Priority 1 incidents or as otherwise required to meet service levels.

Page 95 ends

CITY OF SANTA CLARA
Enclosure A-Appendix A BAFO

2.5 Application Management, Configuration and Maintenance Services (Enclosure D - Schedule 3E)

2.5.1 Application Management, Configuration and Maintenance Solution Questions
Instructions: In addition to the General Solution questions in Section 4 above, Service Provider shall provide responses to each of the Service Tower specific questions below. Limit responses to each question to a half page.
a) Describe your process for application portfolio assessment activities, including development of the annual evaluation report of the City's business and enterprise application portfolio with recommendations on application priorities, applications roadmap development.

Response
Over the last seven years, Unisys has worked with City departments to create an Application Portfolio.

This portfolio was developed using the Gartner Application Portfolio Management (APM) portfolio assessment methodology. This portfolio currently has 182 business applications identified with an understanding of the health of each application (Business Value Versus Technical integrity) according to the Gartner TIME methodology (Tolerate Invest Migrate Eliminate). This information is socialized and agreed upon with the departments at least once a year to help drive awareness of the health of the applications and to provide input to budget funding discussions. This assessment identifies both business and technical deficiencies. Many facts about an application are reviewed in the~e assessments, including:
• Application age
• Does the current platform (server, OS, database, Client, client OS, physical, virtual) comply with the City's Enterprise Architecture standards?
• Security status - PII, PCI, user security, role based • Vendor management
• Product roadmap
• Are the skills required to support the application in line with the City's stated direction? • Is staff training required?
• Opportunity to rationalize (and save costs) - are there other similar applications in use at the City? • How often is the application used?
• Business impact

Page 96 ends

• Total cost of Ownership, including cost to maintain and support • Interrelationships with other applications.

CITY OF SANTA C LARA
Enclosure A-Appendix A BAFO
The Gartner APM (TIME) model to rank business value and technical integrity for each application is a leading approach and one that drives clarity to the application roadmap.

Unisys will continue to manage the City's application portfolio. Our approach to Application Portfolio Management will include the following activities throughout the engagement:
a. Maintenance and enhancement of the application portfolio to continually assess the health of the applications. Due to changes in the business focus and technology, it may become necessary to track additional information regarding the applications (e.g., Windows 10 readiness, Cloud readiness, etc.).
b. Update applications' portfolio inventory data, based on changes to the portfolio (e.g., new applications, upgrades, retired applications, technical changes (virtualization, DB upgrades, and customizations)), the environment, and the City's business needs. c. Facilitate periodic (annual) portfolio reviews with the departments to review their applications.

Monthly Application Portfolio Assessments will be produced with recommendations on application priorities. The outcomes of our application portfolio assessment activities, including assessment of ROI of addressing current business problems, will be reviewed monthly by producing charts and analysis from the repository. Heat maps will be produced to show various issues such as databases and operating systems that are out of date, security issues, and vendor version issues. These items will be reviewed with the respective City departments. During budget cycles, this information will help to prioritize needed upgrades and replacements.

Page 97 ends

CITY OF SANTA CLARA
Enclosure A-Appendix A BAFO
b) Describe your proposed approach to coordinating application lifecycle activities (e.g., testing, configuration, maintenance), with third party application providers (e.g., COTS, Saas, cloud).

Response
As the incumbent, the Unisys applications team currently performs vendor management activities at all levels in collaboration with department stakeholders and subject matter experts (SM Es).

As part of its strategy for vendor management at the City, Unisys will use the following approach:
• Hold regular executive stakeholder meetings with major application vendors to keep City management current on product road maps and new capabilities. • Proactively engage the third party provider SME/technical experts to ensure that application related best practices and latest patches are incorporated in a timely manner. • Monitor feature release schedules from our vendors, plan for testing cycles, and review and prioritize application vendor issues to maintain high-quality service delivery. • Work with the application vendors to ensure:
o Timely identification and mitigation of risks
o Timely resolution of any application-related incidents/issues (e.g., sudden application dumps/errors), escalation of issues to ensure timely assistance from application vendor management, and timely communication to relevant City stakeholders on progress. • Manage communications and set appropriate expectations and project timelines that are agreed to and effectively communicated to the City, Unisys, and the responsible application partner. • Provide input to contract negotiations; understanding the products and vendors helps to create the correct terms and conditions/statement of work for contracts being negotiated by the city. Negotiating the correct deliverables, timelines, and payment milestones is the foundation of a successful project and vendor relationship.
c) Describe your proposed approach for providing the Business Analysis services in Schedule 3E, including how you will engage City departments to understand their unique business needs and translate them into functional and technical requirements, drive solution evaluation and selection, address reporting needs, develop test plans and End-User training and support plans, develop application roadmaps and strategies, and drive departmental customer satisfaction.

Response
Unisys understands that Business Analysis is one of the key aspects of the overall services engagement with the City. Through our Business Analysis Services, Unisys will effectively assimilate the key requirements/challenges of City departments and build requisite collateral/documentation that helps deliver the capabilities and user experience that exceed expectations and _effectively support the City's business. The on-site team has Business Analysts that have domain knowledge in key areas such as

Page 98 ends

CITY OF SANTA CLARA
Enclosure A-Appendix A BAFO
Finance, Utilities and public safety, ensuring effective communication of departmental needs and vision to the IT department, Unisys and vendors.

Our co~e activities for providing Business Analysis Services for the City's Departments will be:

1. Introduce our tested and globally accepted methodology, based on the concepts of "design thinking" or "conversation to conception" (Kanban) model, for effectively capturing business requirements to drive the overall application roadmap. We will incorporate the relevant elements of our overall DevOps and Agile approach to service delivery, to introduce technology and process elements that make this service more efficient.

2. Conduct regular meetings with the City's departments concerning their respective business functions to discuss the current status of issues, projects, and upcoming needs. As part of this activity, we will manage their requests, including tracking, incorporating detailed and complete documentation, and reviewing requests with departments and vendors to find and recommend best possible solutions (and alternatives). We will research requirements with vendors and institutions, and conduct a regular review of business practices against industry best practices to suggest improvements. An example of this service is the Utility Billing system projects, for which Unisys set up a Project Management Office to manage Utility Billing system projects and priorities of the major stake,holders.

3. Proactively lead and manage all coordination activities with the application vendors and City's IT staff (if needed) to ensure availability of the required support needed to resolve project level issues/ challenges arising out of shortcomings in applications or supporting software. This will include coordination for relevant functionality updates/ business process changes, application patch installation, application upgrade, etc.

4. Lastly, execute an annual scheduled Customer satisfaction survey relating to the Service Provider's Business Analysis services and roles, with distribution restricted to City's end u~ers, department directors, managers, and key subject matter experts (including Customer's IT Department (ITD)).

Page 99 ends

CITY OF SANTA CLARA
Enclosure A-Appendix A BAFO
d) The City is interested in providing business analytics and reporting services to the City departments, on an ad hoc and standing basis. This would be done through extracting data from departments' business applications and packaging the data for reports and analysis. How would you propose to provide this service to the different departments given their differing missions and needs (including staffing approach, and process for report development activities)? Response
Unisys has a thorough knowledge of the current state of data and analytics needs in the City and is working on some key initiatives to help build/deploy robust analytics solutions, such as Microsoft Power Bl. To help deliver reports/analytics services that cater to unique needs of various departments, we will provide this service on a project-by-project basis, with an appropriate "change order'' based on the overall scope and level of effort required to support each department's needs.

As part of its business analytics services for City, Unisys team will perform the following key activities as part of this engagement:

1. Organize need-based meetings/workshops with Department SMEs to understand and document these business reporting/analytics needs.

2. Our analysts will then assess feasibility of these requirements against the available data sets and inhouse analytics applications (e.g., Cognos), prioritize the feasible requirements in collaboration with Department stakeholders, and provide estimation for building these reports.

3. Present estimates (and associated implementation costs) to the relevant stakeholders as Change Orders {CRs) for approval/signoff.

4. Post CR signoff, Unisys analysts will design, implement, test, and deploy the report, and collaborate with stakeholders/SMEs for user acceptance/signoff and training on these reports.

In addition to the regular ad hoc analytics/reporting work for City's Departments, Unisys analysts will perform regular research and assessment. We will provide the City with recommendations on relevant next generation business analytics capabilities that present significant opportunity for the City to easily interpret rapidly growing volumes of complex data and decipher new ways of improving services to citizens. Typical examples of these are:
a. Open Data Portal that facilitates a single point of access to a wide range of data held within various City Departments. This Portal will enable ease of use, reuse, and distribution, and will enable meaningful insights that help drive quick and informed decision-making. Recently we became aware that the City's budget software vendor, Questica, has an open data product under development (Open Book) and arranged a demo and installation of the product for Santa Clara to be part of the product evaluation team.
b. Growing volumes, sources, and complexity of data and the desire of organizations to analyze and report on larger volumes of this data (historical or dispersed) has led to the advent of new data

Page 100 ends

CITY OF SANTA CLARA
Enclosure A-Appendix A BAFO
analytics platforms based on Big Data. We will work to assess and recommend such relevant platforms, including Unisys' cost-effective Advanced Analytics Platform, based on the City's future needs. We will help the City's users derive meaningful insights over a larger base (including social media) to serve the City's citizens much more effectively. e) Describe your company's SharePoint practice and how you would leverage it in the City's environment.

Response
The Unisys 9sc account team has a senior SharePoint!Office 365 subject matter expert and two additional team members who are well-versed in SharePoint and in supporting the City's intranet (CSI).

Our account team domain experts will closely collaborate and work with department stakeholders to redesign and modernize the City's intranet using SharePoint Online, leveraging our experience and expertise from the Unisys global Microsoft SharePoint practice. We will also incorporate best practices for security and enterprise document management, as well as improve business functionality and collaboration. This will be achieved by implementing:
• Customized workflows and forms
• Team sites
• Other SharePoint native functionality, as appropriate.

At Unisys, we continuously maintain and update our Microsoft collateral, best practice information, and lessons learned from our many client engagements. This information is available to our associates on other engagements, such as CSC. We will efficiently reuse this content to deliver solutions to meet and exceed the City's expectations.

We will make our associates aware of the latest trends, including reviewing release notes from Microsoft and configuring new functionality/best practices as needed, and as it becomes available.

Page 101 ends

CITY OF SANTA CLARA
Enclosure A- Appendix A BAFO

2.5.2 Application Management, Configuration and Maintenance Solution Overview
Instructions: Provide an overview of the Application Management, Configuration and Maintenance solution you propose to address the City Service Requirements stated in Enclosure D - Schedule 3E, as indicated below. Incorporate responses to common solution characteristics and description elements listed above. Limit 5 pages.

Response
Our approach to Application Management, Configuration, and Maintenance Services, which is illustrated in Exhibit 2.5.2-1, is driven by our passion and relentless desire to exceed the City's expectations for application services. Unisys clearly understands City's challenges and will use this opportunity to bring in the much needed process improvements and automation in our services offering that will help deliver continuous improvements and innovations and bring in the benefits of improved efficiencies, reduced time to value, and potential cost savings f~r the City.

If • * , ¥fbifill,iJlliiWJJJffifJ\M&i1MlW%ii•~Mlidilli®@@J.jjl =:11 :I
.------ - - --------...%--------- - - -------, ..

I ·.-• I • • •I • • 1• · ... , .- ~ -
~~s:lness Analysis ~
:
1 Services ... ~ '• L..:::===.:====~~====ii'====~==ii==::...===~==~=:::::a.===:..J ... ■ Deslg9i/fh:nking Workfl~w
f'~9Sf.!!~.for Business Analys:s
-Conversation to Conception
Kanban Model (Agllel
li·Mlrlijll
11 1
~---,-
Exhibit 2.5.2-1. Unisys Application Management, Configuration, and Maintenance Services.

As part of this strategy, Unisys team will help transform the current state of services through these key initiatives during our engagement with City::
a. Rationalize and standardize the current processes in place for Application Services by using our expertise and Gold partnership in the renowned Scaled Agile Framework for Enterprises (SAFe). This

Page 102 ends

CITY OF SANTA CLARA
Enclosure A-Appendix A BAFO
. framework combines Agile and Lean principles and values to arrive at the specific practices and roles that are required across the enterprise to succeed on the Agile journey. b. Introduce DevOps to provide the much-needed automation across the application life cycle for improved efficiency, effectiveness, and speed of project delivery. DevOps will bring the needed automation for driving effectiveness in service delivery and drastically reduce potential defects to improve services quality and drive costs down.
c. Through Continuous Service Improvement initiatives, consistently enhance the skills of our associates at the City. This will not only meet our associates' aspirations, but also will set the pace for innovation, growth, and overall efficiency and cost benefits.
d. Evaluate new technologies and recommend enhancements that help to drive continuous improvements in operations, reduce the time to market, drive costs down, drive better user experience, and improve user sentiment. Our recommendations are as follows:
i. Open Data Portal, to facilitate a single point of access to a wide range of data held within various City Departments as opposed to the current environment where information is in silos, spread throughout the city (Refer to our response to RFP requirement 2.5.1d.) ii. Advanced Business Analytics based on Big Data capability, using cost-effective solutions like the Unisys Advanced Analytics Platform to solve complex problems in the future. (Refer to our response to RFP requirement 2.5.1d.)
iii. Agile-based business analysis (refer to our response to RFP requirement 2.5.1 c) to drive process improvements that help design solutions with improved user experience.

Unisys will work to provide all the services listed as in scope for Application Services SOW (Schedule 3E), including the ongoing and project-based application maintenance, configuration, and maintenance services for Customer's application portfolio, in line with City's expected Service Level Agreements (SLAs), with timely and adequate assistance provided by City's stakeholders in resolving dependencies arising out of external factors where Unisys has no control. These external factors are typically:
a. Delays on the part of the City in its required project participation, providing scope changes and in signoff of deliverables, despite timely reminders from Unisys Team b. Delays on the part of the City in procuring applications and software (or patches) or provisioning required infrastructure for the project
c. Delays from the application or software vendors in providing the required patches, despite timely communication from Unisys Team
d. Change in City's .business priorities, and the same resources from Unisys Team are required to address them

Page 103 ends

CITY OF SANTA CLARA
Enclosure A-Appendix A BAFO
e. Delays in provisioning of the required infrastructure (including the correct versions of application, database, etc. for Non-Production and Production environments) or Saas environments to build, test, and deploy
f. Timely and complete participation and signoff on deliverables from assigned City stakeholders in accordance with the Project Plan
g. Product/application and environment, Infrastructure, or Environment (Cloud or in-house) issues h. Upsurge in incident volume from the current volume handled by the Unisys Team.

In such scenarios where external factors come into play, Unisys will work tirelessly in coordination with City and any third-party vendors to ensure timely resolution (or workaround) of such external factors that inhibit service quality and impact smooth running of business. In addition, Unisys will document such instances and their resolutions as lessons learned, so impact of such external factors can be minimized in the future.

Our SAFe Strategy for the City
Unisys will use our team of certified Scaled Agile Program Consultants with deep industry expertise to provide the required consulting needed to enable an Agile way of working. Unisys created a framework to help to assess customer organizational readiness for embarking on an Agile-DevOps journey and identifying improvement areas. We will leverage this framework to help with charting the roadmap for achieving the necessary process improvements.

How SAFe Will Work at the City
Detailed Scaled Agile (SAFe®) and DevOps Implementation Approach is provided in response to Question 4.1 d. This section gives an overview of Unisys' Agile/SAFe® strategy for City. The Agile life cycle conforms to an incremental pattern. Development iterations, termed as sprints, are typically contained in 2 to 4 week increments in which constant progress is demonstrated. This life cycle and the accompanying methodology allow for maximum communication and collaboration with clients and development. Unisys' key Agile elements, combined with our enhanced execution capacity that leverages our DevOps stack, will address the scope of application management and configuration to include the following activities:
• Requirements Management: to establish and maintain agreement with the City and other stakeholders on system requirements. The Agile method defines requirements with the sprint cadence of 2 to 4 weeks and uses a user story-driven approach. User stories allow requirements analysts to focus on the goals for the system· under development and offer a short narrative describing something that a user wants the system to do. • Analysis and Design: to transform the requirements into a design of the system-to-be; to evolve a robust architecture for the system; and to adapt the design to match the implementation environment, designing it for performance.

Page 104 ends

CITY OF SANTA CLARA
Enclosure A-Appendix A BAFO
• Implementation: to define the organization of the code as implementation subsystems organized in layers to implement the design elements as implementation elements (source files, binaries, executables, etc.), to test the developed components as units, and to integrate the results produced by individual implementers (or teams) with an executable system. • Testing: to focus mainly on evaluating or assessing product quality, which is realized through a combination of leveraging DevOps (e.g. Selenium) for improved testing efficiency and effectiveness and the following core Agile practices:
o Document defects in software quality and advise on the perceived software quality o Validate and prove the assumptions made in design and requirement specifications through concrete demonstration
o Validate that the software product works as designed
o Validate that the requirements are implemented appropriately • Deployment consists of the activities for enabling the software solution's availability for its end users. • Configuration and Change Management are essential for controlling the numerous artifacts produced by the many people who work on a common project. Unisys Agile uses CMMl-compliant processes for configuration management.
• Project Management is the art of balancing competing objectives, managing risk, and overcoming constraints to successfully deliver a product that meets the needs of customers and users. That so few projects are unarguably successful is comment enough on the difficulty of the task. Agile Project Management allows Unisys to manage risk and to demonstrate progress early and often. • Organizational Change Management (OCM) enables the organization to efficiently transition through the change impact by identifying the risks and mitigation as it pertains to employees; identifies key messages to push ·using a variety of supporting channels; and tracks usage of the new tools or technologies based on targeted communications as well as appropriate training delivered. As a result of the organizational change management strategy, City of Santa Clara will receive:
o OCM plan that provides strategic approach applied to an evidence-based transformation plan that moves organization from current to future state with high adoption rates. o Communication campaign that supports organizational growth through transition, utilizes CSC current communication channels, and tracks effectiveness.

OCM stakeholder analysis will include a focus on how the transition to DevOps environment impacts current stakeholder groups, and specific treatments (communication and training workstreams) that address and support the transition. We will create performance objectives for fully leveraging DevOps environment including achieving service levels as identified in solution SOW: Performance objectives will be addressed through specific training and coaching plan to fully engage impacted users.

Page 105 ends

CITY OF SANTA CLARA
Enclosure A- Appendix A BAFO
• Environment focuses on the activities necessary to configure the process for a project. It describes the activities required to develop the guidelines to support a project. The purpose of the environment activities is to provide the software development organization with the software development environment- processes and tools- that will support the development team. • Operations and Support is a discipline that is adopted by Unisys Agile. It is the recognition that the work is not complete when the project is delivered. The main goal of the Operations and Support discipline is to operate and support the solution in a production environment.

Application Maintenance and Support:

Our approach to Application Maintenance and Support is driven by the ITIL v3 framework. The model focuses on delivery of services to business stakeholders within a set of well-defined service-level expectations. The changes and benefits that are due to a shift to a unified managed service provide a positive impact across many dimensions. Unisys stands behind our commitment to services that will improve over time and be supported by detailed analytics. Applications management will align incident management, problem management, knowledge management, service request management, and service optimization with the ITIL framework to provide process standardization.

Unisys' partnership with Service Now allows us to bring not only one of the best service management tools in the market but also our world-class ability to deliver services through a fully ITIL v3 compliant framework and operations model. The Unisys strategy for service management is founded on helping clients to focus on a top-down approach for understanding that business value comes from running IT from the business perspective. Although the Unisys solution is partly based on ITIL-certified products, it incorporates Lean Six Sigma principles to maximize the value to the City. The aspects expected as part of the maintenance services will use our strengths as follows:
a) Preventive Maintenance:
i. Use our expertise in ServiceNow for regular analysis of volume trends in incidents and problems to recommend appropriate remediation measures (e.g., enhancements, system changes, and upgrades,)
ii. Work with our enterprise compute team to help with setting up an adequate application performance monitoring mechanism that maintains continuous monitoring of key business applications, thereby providing business continuity by timely prevention and quick resolution of application breakdowns
iii. Work closely with application vendors, given our knowledge of the City's landscape and challenges, to confirm that applications have the best practices and the latest patch updates in place.

Page 106 ends

CITY OF SANTA C LARA
Enclosure A- Appendix A BAFO
b) Adaptive Maintenance:
i. Unisys will perform regular research and provide periodic updates of application and solution recommendations, which will fill gaps that might exist between the City's vision and current application landscape.
ii. Once City stakeholders accept our recommendations, Unisys will work with relevant vendors to enable the application to meet the requirements (or gaps) with minimal customization. iii. Hold regular meetings with application vendors to confirm that the solution is regularly updated in line with the City's changing business and regulatory needs. iv. Work with the City IT Department to confirm that required clearances are in place for periodic installation of vendor-recommended patches and changes. c) Corrective Maintenance:
i. Ensure timely resolution of incidents.
ii. Perform necessary break/fix activities.
iii. Drive appropriate and timely communication to relevant stakeholders. d) Perfective Maintenance:
i. Work with the enterprise compute team to confirm adequate application performance monitoring, especially the key business applications (e.g., PeopleSoft) to identify problems that affect expected value to City departments
ii. Regularly analyze applications' performance trends and work with appropriate application vendors to understand and develop roadmaps for recommended maintenance best practices and periodic infrastructure changes to avoid degradation of application performance.

Continuous Improvement: As an innovation-driven organization, Unisys believes in driving this culture of innovation and continuous improvement in our associates who are engaged with the City. We see tremendous value in fostering this culture through our proposed engagement team to consistently deliver benefits and cost savings to the City. The following elements are key to success for this program:
• Effective Knowledge Management to drive cost down and increase end-user satisfaction by driving for the quickest and most effective resolution
• Relentless Training of our associates that includes cross-skilling, up-skilling, and relevant certifications.

Page 107 ends

APPENDIX A

CRITICAL DELIVERABLES
for
CtTY OF SANTA CLARA

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions-Appendix A
Table of Contents
Procedures Manual ........................................................................................................................ 2 IT Strategic Plan ............................................................................................................................ 2 Information/Cy her Sec_urity Plan ................................................................................................. 6 Business Continuity Plan ............................................................................................................... 8 · Disaste1· Recovery Plan ................................................................................................................ 10 Enterprise Architecture Plan ...................................................................................................... 12 Com1nuoications Plan .................................................................................................................. 15 ITIL Service Management Standards ........................................................................................ 17 Enterprise Project Management Standards .............................................................................. 20 Digital Strategy Plan .................................................................................................................... 21 Innovative Products and Services Report and Meeting ........................................................... 25 Operational Efficiencies Improvement Report and Meeting ................................................... 27 End User and Key Department Personnel Scheduled Customer Satisfaction Survey Report and Meeting ..................................................................................................................... 28 Services Strategic Review Report and Meeting ........................................................................ 28 Annual Execution Plan ................................................................................................................ 28 Technology Refresh Plan ............................................................................................................. 29 Overview of Unisys Innovation Workshops .................................. EITor! Bookmark not defined.

Global Expertise and Thought Leadership ................................... Error! Bookmark not defined.

Page A-i
Procedures Manual

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions-Appendix A
f Guide that details the standard operating procedures for all services: This has items such as process based fprocedures such as Incident management as well as functional base tasks such as PC installs.

In October of 2013 a series of guides forming the then Procedures Manual was delivered as part of the original contract Critical Deliverables to the city. These guides in some cases are fully inclusive while others point to shared repositories of documents that contain "how to's" that are frequently used by desktop technicians and other suppo1t staff, both onsite and remote. Examples of these gt1ides include, but are not limited to:
• Change Control Procedures
• Problem Management Procedures
• Incident Management
• Data Center Maintenance Plan
• Database Backup and restore
• Security Procedures
• Operations Guide
• LAN Standard and Procedures
• Windows Design
• VPN Procedures
• Server Build Procedures
• Server Patching Procedures
• Endpoint Installation Procedures
• DSS Processes and Procedures
Since publication, there have been changes to the infrastructure, environment, software and business applications that need to be reflected in these documents to bring them up-to-date.

Furthermore, during the transition process new runbooks and helpfiles will be updated and created. These will also be referenced to the knowledge base and portal as applicable. Once these have been updated by the individual service towers and approved, a process will be put in place to update them regularly through the change management process.

Business IT Strategic Plan
Plan that analyzes the current state of the City's Information Technology utilization, capability, capacity, maturity and cost-effectiveness to mee,t functional business goals and requirements.

Identifies un-met and new business requirements and develops the future state Information Technology landscape, as defined below.

The plan will inc/qde a 2-4 year roadmap to help it achieve the identified future state, goals and objectives.

Elements include:

Current State: review and assessment of business strategy, vision and goals, business services and functional requirements, IT utilization, capability, capacity, maturity and cost-effectiveness to meet functional business goals and requirements. , financials, IT environment, service gaps.

Future State: Un-met and new business requirements, IT trends, IT vision, IT capabilities, policies, standards, processes and organization, enterprise architecture, governance model, performance management
Roadmap: Identification and prioritization of business application refresh projects and IT initiatives for the 2- 4 year horizon. The roadmap will include time-lines, budget needs, high level justification and funding sourc~.

Page A-2

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions- Appendix A
The Enterprise Architect, assisted by Unisys Consultants and SMEs will develop and update annually the Business IT Strategic Plan (!TSP) based on the departmental goals aligned to the City's Mission and Vision. The ITSP serves to align the technology requirements to the City's business goals, functions, services and requirements for information technology and forms the foundation for the other associated strategic plans, information technology organizational, tactical and operating plans. The Future State vision describes the ideal state in high-level terms that forms the foundation for the acquisition of new technologies to support new capabilities. Identified gaps between the Current State and the Future State are selectively organized into projects that are then prioritized based on budget or technology sequencing requirements. As new approaches/capabilities are identified through trends in technology and service delivery, they will become candidates for update to the ITSP and the other strategic plans. As projects are completed, their components and capabilities will become reflected in the Current State as part of the annual update. As new business goals or technology improvements are identified, their components and capabilities will be incorporated into the Future State, and a new gap analysis will be conducted and the Roadmap updated as part of the annual update. (Please refer to 2.1 .1.0.) Unisys will produce a business driven "IT Strategic Plan" in the first year (within 12 months) after "go live", that is intended to provide a high level framework and prioritized roadmap of IT projects and initiatives for a 2-4 year period. Following the initial deliverable, this roadmap document will be revalidated and updated at least once every 12 months to reflect any changes in the City's business priorities and technological advancements and changes.

Unisys will maintain this Strategic Plan and Roadmap and provide effective, monthly communications on progress to ensure that the City makes progress on its vision and goals through the prioritized roadmap.

Deliverable outline
An outline of the "IT Strategic Plan" deliverable that will be produced at the end of a four to six week engagement is outlined below. This is the same work plan as the Digital Strategy Plan insofar as it leverages the same workshops and the same participants. The Digital Strategy is the "envelope plan" whereas the IT Strategic Plan is the "enabler plan". In any case while we develop the interview schedules and the workshops it should be one set that covers the input and planning, deliverable creation for both. # TOC Major Area Content area (sub TOC) Comments
1 City Goals and Vision * City Goals and Visions - Describes City's Goals and Visions * IT and Technology for the City as a whole, and specific Vision and Goals for City departments as perceived by
leadership of City and Department
heads
PageA-3
# TOC Major Area
2 Current State of Digital
Technology in the City
3 Future State
Recommendations

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions-Appendix A
Content area (sub TOC) Comments
* Business s~rvices and Gaps that still exist in order meet the functional requirements City's stated goals and visions. * Current State of Technology Enablers that will be
Technology/ Processes required to fill these gaps with the in various current state
Departments/City
*IT utilization, capability,
capacity, maturity and
cost-effectiveness to meet
functional business goals
and requirements.
* Enablers / Barriers that
exist today
* Existing IT Projects that
are underway and their
alignment with the ITSP
and Digital Gov
*Un-met and new business Prioritized list of Projects and requirements, IT trends, IT Initiatives supported by Financials vision, IT capabilities, (high level) costs and benefits and an policies, standards, implementation plan (high level) in a processes and roadmap for the City
organization, enterprise
architecture, governance
model, performance
management
* Technology Capabilities
Required to support
Future Vision and Goals
"Prioritized list of
business application
refresh projects and IT
initiatives.
* Projects Defined with
High level cost, benefit
and Financial Analysis
* Prioritized list of Proiects
Page A-4
# TOC Major Area
5 Ongoing Governance
Recommendations

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions-Appendix A
Content area (sub TOC) Comments
* Projects/ Initiatives
recommended
"Implementation
Roadmap for 2 to 4 year
timeframe
* Methodology, Templates Visual Tracking of Progress made on and Documents to track various Technology projects and
and monitor ongoing initiatives, including Financial
implementation performance, and progress against
* Monthly Status Report plan
Template
Tasks I Deliverables I Acceptance Criteria
Unisys will use a team of Consultants and Local Government SMEs, and the onsite team of Applications Program Manager, Enterprise Architect to develop and present the IT Strategic plan, which will be updated annually (every 12 months).The Unisys team will work with City stakeholders who will be identified prior to the initial kickoff meeting and will be involved during the interviews, and also both of the workshops that will be conducted during the engagement to produce the final deliverable - IT Strategic Plan.

Major Task/ Deliverable Completion I Acceptance criteria 1 Engagement Plan with Interview Project Plan Produced and presented to City Schedule (Kickoff) Stakeholders and approved by the CIO 2 Interviews with Stakeholders of all Interviews completed (Questionnaires and departments (1-2 interviews per interview notes produced·and documented) department)
3 Preparation for Planning Workshop# 1) Planning Deliverable - PPT Deck and Word Document that outlines City Goals/Mission (for
Digital Transformation), Capabilities, Enablers
and Barriers completed and approved by the
ClO and departments
4 Prioritization/Planning Workshop Planning Deliverable (updated)- PPT Deck Completed (#1) and Word Document that outlines City
Goals/Mission, Capabilities Enablers and
Page A-5
Major Task/ Deliverable
5 RoadMap Workshop Completed (#2)
6 Final Presentation and Deliverable
Completed
Periodic Updates and Ongoing Governance

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions- Appendix A
Completion I Acceptance criteria
Barriers completed, with capabilities prioritized
after the Workshop, reviewed and approved by
the City.

RoadMap Deliverable - PPT deck and Word
document that describes Initiatives/Projects and
their priorities, with High Level Financial
Analysis (costs/ benefits), priorities, High level
implementation plan and Roadmap. Completed
and approved by the CIO
Final Presentation to City Stakeholders (PPT
Deck) and Final Deliverable - IT Strategic Plan
Document (Word doc) completed, presented
and approved by the CIO
Monthly Status reports will be produced regarding the progress of various activities and milestones outlined in the IT Strategic Plan. This will be tracked by the Unisys PMO, Applications Program Manager, Enterprise Architect as well as Digital Government SM Es and the City stakeholders.

On an annual basis (every 12 months), the planning process will be repeated, as necessary, to update and maintain the IT Strategic Plan document.
lnformation/Cyber Security Plan
A current information security plan and robust set of policies exist as an input. Service Provider will analyze current security posture, any new business and regulatory compliance requirements and laws, and provide recommendations to address any areas where deficiencies or threats have been identified for both on prem and cloud assets. Result will be an updated written plan, policies, standards and procedures that provide the operational and technical responsibilities associated with the Security table in this SOW (e.g., data security, physical security, security operations, patching, ma/ware prevention, monitoring and Incident management, and threat and vulnerability management).

The Plan must be consistent with the NIST Cybersecurity Framework and any new business and regulatory • compliance reguirements and laws.

A Security Plan exists from 2013 based on the City's business needs and the security and privacy controls listed in the NIST SP 800-53 publication. This plan incorporated the results of an assessment that documented compliance with the controls listed in the NIST special publication. The security plan will benefit by performing a new security assessment, which is included as an optional service in the Page A-6

CITY OF SANTA C LARA
Schedule 2 - Final Service Tower Solutions-Appendix A
proposed information security solution. The optional annu9I risk assessment and requirements review is based on business needs and the complete (most current version) NIST Cybersecurity Framework. (The currently released version 1. 0 consisting of 22 categories and 98 subcategories and draft version 1.1 consisting of 23 categories and 106 subcategories).

If opted for, the assessment will be performed by the Unisys Security Advisory team using currently released version. The results will be used to benefit the Security Plan.

The following are the aspects of the risk assessment process that will enable the development of a plan that conforms to the NIST Cybersecurity Framework, and is based on the City's priorities and areas of risk.
1 . Perform risk assessment
a.

Define scope that includes systems, stakeholders, and compliance requirements.

Understand current state of security controls (based on Data Sensitivity requirements, NIST Cybersecurity Framework and other standards and laws, such as HIPAA, California Public Records act, PCI, DOJ, California privacy laws and guidelines, NERC Standards, etc.)
Conduct interviews and perform walkthroughs of in-scope systems and processes
Perform SWOT Analysis (Strengths, Weaknesses, Opportunities, Threats)

2. Determine desired capabilities and maturity levels

3. Perform gap analysis

4. Generate report that includes:

Revised Security Plan, Policies, Standards and Procedures Revised Citywide security breach response plans
Revised security technical architecture
Prioritized risk ranking
Capability assessment findings
Maturity assessment analysis
Remediation and upgrade recommendations
Security action plan
Page A-7

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions- Appendix A
Business Continuity Plan
The Business Continuity Plan includes working with key stakeholders to re-validate the City's critical business applications an_d infrastwcture assets based on the already defined prioritization framework and updating/enhancing the existing Business Continuity Plan that encompasses all current mission-critical City Applications and the associated IT assets.

The current Business Continuity Plan (BCP) was delivered as part of the original contract Critical Deliverables to the city in January and February of 2014 and consisted of the following documents:
• Business Continuity Program: Information Technology Strategy • Business Impact Analysis
• IT Incident and Communications Management Plan
• Disaster Recovery and Scheduled System Testing
• Data Center Restore Plan
• CSC Information Technology Operations Recovery Plan
• IT Operations Metro Failover Guide
• ITSM Offline Workaround
• CSC - Business Continuity Program Tabletop Test Plan
• CSC - BCDR Risk Assessment Table
• Business Continuity and Information Security Executive Steering Committee Charter.

Since publication, there have been changes to the infrastructure, environment, and business applications that need to be reflected in these. A Business Continuity (BC)/Disaster Recovery {DR) subject matter expert (SME) will facilitate the review, validation, and update of the documents and plans listed above.

There will be a need for the SME to interact with the onsite and in some cases remote staff to obtain updates to the environment and business requirements. The impact on City department resources will be minimized through an effort to reuse discovery and analysis work performed as part of the 2014 deliverable effort. The basic process will be as follows but is subject to revision after the "Create and Review BCP Update Schedule" tasks have been performed:

1. Create and review BCP Update Schedule
a. Review existing BCP documents
b. Assign tasks for data updates
c. Create and review CSC BCP Update Schedule
d. Review the SCP Update schedule with Unisys CSC support team

2. BCP Information Update
a. City of Santa Clara Business Continuity Program: Information Technology Strategy b. Business Impact Analysis based on revised business requirements, RTO and RPO needs
Page A-8

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions-Appendix A
c. Enterprise Architecture
d. VM Mappings to Volumes
e. Hybrid Cloud and Cloud Backup impacts
f. BCDR Analysis
g. Emergency Incident Contact Lists
h. BCP Information Update - Complete

3. Update BCP plans
a. IT Operations Recovery Plan
b. IT Incident and Communication Management Plan
c. DR and Regular CoSC System Testing (MASTER)
d. City of Santa Clara Business Continuity Tabletop Test Plan e. Datacenter Restore Plan
f. BCP plan update complete
g. Sign off by the City and Unisys on the revised BCP

4. Publication of Revised Business Continuity Plan
The current Business Continuity Plan which is the main document contains the following high level layout and table of contents but may be revised during the update process:

1.0 Introduction •

1.1 Purpose

1.2 Scope

1.3 Objectives

2.0 Risk Assessment

2.1 Threat Summary

2.2 Threat Mitigation

2.3 Major Disruption Scenarios

3.0 Business Impact Analysis

3.1 Approach

3.2 Business Function Summary

4.0 City Emergency Operations

4.1 Emergency Operations Plan Priorities

4.2 Emergency Operations Plan Scope

4.2.1 Levels of Response

4.3 City Emergency Operations Responsibilities

4.4 Integration of Departmental Recovery Plans

4.5 The Business Recovery Center

5.0 Business Continuity Framework

6.0 Conceptual Architecture

6.1 High-Availability Architecture

6.2 Disaster Recovery Architecture
Page A-9

7.0 Recovery Approaches
7 .1 Platform Types

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions-Appendix A

7.2 Recovery Techniques

8.0 Plan Maintenance and Testing

9.0 References
Disaster Recovery Plan
This plan is to update and enhance the detailed requirements and design solutions for the recovery of critical IT assets in the event of a major disaster or service disru~tiofl.

Unisys will provide to the City of Santa Clara a Disaster Recovery Planning (DRP) for those Business Critical systems that require DR plans. The disaster recovery plan deliverable, based on the City's Recovery Time Objective (RTO) and Recovery Point Objective (RPO) requirements as defined in the Business Continuity Plan (the subject of a separate deliverable), is a detailed step-by-step document which is to be followed by key Unisys and City staff during DR testing and/or when a Disaster has been declared. Unisys will collaborate with CSC on a yearly·basis to review and update both the Business Continuity and Disaster Recovery Plans.

This will require the City to make key technical stakeholders available and responsible to participate in Disaster Recovery Planning Workshops. These workshops will be scheduled within the first three (3) months of the new engagement. The Disaster Recovery Plan will be presented back to the City of Santa Clara for their acceptance and approval within 60 days of a successfully completed workshop.

Upon the City of Santa Clara's acceptance of the DR plan, Unisys will schedule a test of the appropriate set of Business Continuity Plans and the DR plan with the City of Santa Clara at a time that will provide the least amount of impact to the City. Unisys will execute the plan within the first twelve (12) months of the new engagement and one (1) time per year starting in year 2 for the duration of our partnership.

Unisys will provide a DR test review report with the results of the DR test within 15 business days of completion of the scheduled DR test. If a DR test is not successful, Unisys will provide a Root Cause Analysis (RCA) for the failed DR test. Unisys will remediate the issue (if the root cause identifies that remediation is within Unisys' scope to resolve or provide appropriate remediation requirements to the City for any out of scope issues) and schedule a retest within 90 days of the remediation, as identified in the RCA.

The primary Disaster Recovery Planning staff is an external team to the onsite Unisys delivery team but will require the input from key technical support staff. Disaster Recovery testing will be led by the Unisys DRP external team members and may require onsite Unisys delivery key technical support staff and possibly CSC User Acceptance Test personnel.

DR testing is assumed to occur during non-business hours to minimize impact to CSC agencies and constituents. All charges for DR planning and test exercises, as described above, are included in the Unisys proposal.
• Page A-10

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions- Appendix A
The main Disaster Recovery Planning document proposed high level layout and table of contents would be as follows but subject to change during the development process:

1. Introduction

1.1 Purpose

1.2 Objective

1.3 Scope

1.4 Assumptions

1.5 Applicable Standards and Guidance

2. Concept of Operations

2.1 Four Phases·

2.2 Data Backup Readiness Information

2.3 Site Readiness Information

2.4 Hybrid Cloud Readiness Information

2.5 Roles and Responsibilities

3. Activation and Notification

3.1 Activation Criteria and Procedure

3.2 Notification Instructions

3.3 Outage Assessment

3.4 Incident Team(s)

3.5 End User Messaging/Communications Plan

4. Plan Activation Procedures

4.1 Media Retrieval and Delivery .

4.2 Cloud Backup Data Recovery

4.3 Disaster Recovery Overview

4.2.1 General Application Description

4.2.2 Recovery Contacts

4.2.3 Data Center Overview

4.3 Infrastructure Recovery Procedures

4.4 Critical Business Application Recovery Procedures

4.5 Website Recovery Procedures

4.6 DNS Changes

4.7 Network Recovery Procedures

5. Reconstitution

5.1 Data Validation Testing

5.2 Functional Validation Testing

5.3 Recovery Declaration

5.4 User Notification

5.5 Cleanup

5.6 Returning Backup Media

5.7 Backing up Restored Systems

5.8 Event Documentation

6. Recovery Plan Testing

7. IT Business Restoration (Return to Normal Operations) Plan Appendices:

Key Personnel and Team Member Contact List
Vendor Contact List
Alternate Telecommunications Provisions
Diagrams
Page A-11

CITY OF SANTA CLARA
Schedule 2- Final Service Tower Solutions-Appendix A
Network Configurations
Hardware Inventory
Recovery Plan Test Report
Related Documents
Enterprise Architecture Plan
Develop an analysis, blueprint and implementatjon_plan for the City's data, cffef!_lications, and technology.

The Enterprise Architect will develop and maintain an Enterprise Architecture Plan {EAP) based on an Enterprise Architecture Framework of Architectural Domains, including:
• Business Architecture (BA) - structured around mission critical business capabilities/processes based on departmental goals intended to realize the City's Mission and Vision. • Information Architecture (IA) - Information and analytics needs of the business functions, communities of interest, external stakeholders, business partners, etc. • Data Architecture (DA) - structured around the logical data required to support the BA • Security Architecture (SA) - based on the sensitivity and vulnerability of the data (DA) or services (BA)
• Application Architecture (AA) - based on the approved application technologies required to realize the mission critical business processes. This domain will include all application layers, such as:

Access Channels Layer
Presentation Layer (CX and UX)
Shared Services Components
E-Government on-line services
Enterprise applications
Department Specific applications
Middleware Components - Integration Layer; Web Services; Business Rules, etc. • Communication Architecture (CA) - based on the approved technologies required for communication and delivery of services through voice and network capabilities. • Infrastructure Architecture (IA)- based on the approved product technologies required to support the BA, IA, DA, SA, AA, and CA domains. This includes Business Continuity and Disaster Recovery capabilities.

Page A-12

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions-Appendix A
The EA Framework will be leveraged to guide requirements analysis to ensure that new technology components align with the intended Future Vision. Overall, the EAP will provide a high-level.view of the City's approach to fulfilling the Future Vision of the IT Strategic Plan and a high-level view into the Tower rQadmaps. The EAP will be updated to reflect changes through delivery of projects or CRs and presented as part of the annual update process. (Please refer to 2.1.1.o.).

Deliverable outline
An outline of the "Enterprise Architecture Plan" deliverable that will be produced at the end of the Digital Strategy Plan and IT Strategic Plan development following approval of those deliverables. # TOC Major Area Content area (sub TOC) Comments
1 City Goals and Vision * City Goals and Visions - Describes City's Digital Government Outside in view of how Goals and Visions for the City as a City will serve Citizens whole, and specific departments as and Constituents perceived by leadership of City and
* Digital Government Department heads. This introduction Vision ana Goals for City is taken from the IT Strategic Plan. * business function and
_services requirements
* Information and
Analytics requirements
* IT Architecture Drivers
2 Enterprise Architecture • Description of the Based on the results of the Digital Domain Framework and domains of the Strategy workshops and the IT Domain Descriptions EA Framework Strategy analysis, the EA Domain • Specification of Framework will identify those
the meta-data to Architectural Domains to measure
be captured and
and monitor in order to realize the
maintained within City's goals.
each Domain
• Domain detail
descriptions,
components
(bricks),
standards, five
vear uoarade
Page A-13
# TOC Major Area
3 EA Repository
4 EA Processes

CITY OF SANTA C LARA
Schedule 2 - Final Service Tower Solutions-Appendix A
Content area (sub TOC) Comments
plans.
• Description of The Domain meta-data will be used to
the EA repository measure the gaps to be filled in order to be used to to realize the City's goals. The EA
capture and repository will enable a digital
maintain the modeling capability that will visibly
Domain meta- diagram the alignment of the City's
data goals to the underlying architecture of
the solutions.
• Description of The EA Processes are the methods
processes to be to be applied to ensure that selected
followed in order projects are staying aligned with the to maintain the City's business goals.

EA Domain
Framework in the
EA Repository.

Tasks/ Deliverables / Acceptance Criteria
The Enterprise Architect to develop and present the Enterprise Architecture Plan, which will be updated annually (every 12 months). The Enterprise Architecture Plan will be developed in conjunction with the Digital Strategy Plan and the IT Strategic Plan and will focus on those gaps that must be filled to ensure realization of the City's goals.

Major Task/ Deliverable Completion / Acceptance criteria 1 Draft (Strawman) Enterprise Architecture Following completion of the Digital Strategy Plan Plan (EAP) and the IT Strategic Plan, The Enterprise
Architect will deliver a draft Enterprise
Architecture Plan tailored to the identified gaps
the must be closed in order to realize the City's
Page A-14
Major Task/ Deliverable
2 Presentation and Review of the EAP
3 Finalized EAP
Periodic Updates and Ongoing Governance

CITY OF SANTA C LARA
Schedule 2 - Final Service Tower Solutions-Appendix A
Completion / Acceptance criteria
goals.

Review, discussion and adjustment of the EAP
to address the identified gaps
Enterprise Architecture Plan Document (Word
doc) completed and presented
Finalized document incorporating the comments
and recommendations from the Review.

Approved by the CIO
On an annual basis (every 12 months), following update of the Digital Strategy Plan document and the IT Strategy Plan document, The Enterprise Architecture Plan will be reviewed and updated to address any needed change in Domains or meta-data necessary to address changes to those underlying plans.

Communications Plan
Written plan tha·t provides direction on how the Service Provider will engage with /TD and other City departments on an ongoing basis, including at both the strategic and operational level. The plan wilf define the frequency, audience and format of the communications. • The communication plan will serve to describe the strategic collaboration approach and how Unisys maintains an effective partnership with ITD and CSC departments. The plan includes the governance, roles and responsibilities for proactive and reactive communication between Unisys and CSC as well as publicizes successful rollouts and keeping the departments in touch with the IT strategic roadmap.

Reactive communications are event based. Examples of reactive communications are notification of a system outage, notification of resolution of a system outage, software upgrade, and project milestones reached. These communications are sent out at the time of the event. Proactive communications are sent out on a regular schedule. They include messages such as service level performance, such as uptime reports, service desk recaps, security awareness, the IT roadmap, Projects portfolio and progress on the Annual Execution Plan, and user education including tips and advice. These communications will be scheduled on a staggered basis to ensure frequent contact with end users, stakeholders, and department heads. The frequency of each communication will be defined in the plan, in addition to who will send out the communication. Depending on the subject, communications may be sent monthly, quarterly, or annually.

Page A-15

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions-Appendix A
Communication channels and levels of communication for each stakeholder group are provided in the plan to accommodate the relevancy of information as well as maintain a transparency with ITD/CSC on project progress as well as issues and/or risks and respective mitigation. The communication plan supports the overall project deployment plan and will be updated as needed based on input from Unisys and ITD/CSC.

The communication plan will also define the style and format (templates) of these communications. It is important that they be informative, brief, and professional.

The Communications plan will provide the following benefits:

1. Inform users about events that may affect them Oust in time communications) - upgrade announcements, outage alerts, security bulletins.

2. Publicize IT successes.

3. Transparency of costs.

4. Communicate status of IT initiatives over the long term.

The communication plan provides the following table of contents:

Overview to service management communication objectives o Informing impacted users about events such as upgrades, outages, security awareness; o IT performance success, transparency of costs, IT initiative long term status view Roles and responsibilities for impacted stakeholders
• Schedule of Communications
• Communiciation Content
o Templates
Communication guiding principles & activities
o Project reporting status (including format, review cycle) o Stakeholder/steering committee collaboration
o Communication channels and frequencies
o Communication of issues and risk mitigation
o Approval process
Glossary of terms
Page A-16

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions-Appendix A
ITIL Service Management Standards
Strategy and execution plan for the aeployment and ongoing maintenance of tools, documentation of pmcess necessary to have conststent service management within the enterprise The IT Infrastructure Library (ITIL) is an integrated, process-based, best-practice framework for managing IT services. It provides guidance for creating and operating a service desk that provides efficient communication between the user community and the IT provider. The ServiceNow platform conforms to ITIL v3 processes.

The ServiceNow platform effectively supports ITIL-aligned activities and IT best practices for:
• Incident management
• Problem management
• Knowledge management
• Request fulfillment
• Change management
• Release and deployment
• Service asset and configuration
• Capacity Management
• Financial Management
• Service level management
• Service catalog management.

Unisys deployment/implementation methodology follows the recommended ITIL v3 global processes.

Upon completion of the implementation, a data design document will be provided by the ServiceNow implementation (transition) team. The document will contain the configurations that support the above ITIL processes and CSC's specific business requirements. Any changes to the platform and/or the processes will require the Unisys Change Management process to be followed in order to recognize, control, and communicate the changes, then consequently documented and reviewed.

Key activities associated to the ITIL Processes
Incident management
An unplanned interruption to an IT service or reduction in the quality of an IT service.

Failure of a configuration item that has not yet impacted service is also an incident." Page A-17

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions- Appendix A
The process provides detailed procedural guidance on how different types of interactions should be handled. The primary audience for this document includes Service Desk team, ITIL process team, L2 Support, L3 Support and End users.

Problem management
Problem is an underlying cause of one or more.Incidents.

The goal of Problem Management Process is to identify and eliminate the Root Cause of the Problem through preventive/corrective actions or reduce the impact of problem on recurrence.

In turn, stabilizing the IT environment.

Knowledge management
Knowledge Management Process provides standardized guidelines for creating and managing solutions in an integrated Knowledge Base (KB). This process includes detailed guidelines in subsequent sections to:
• Create or Modify a Knowledge article
Engage the Knowledge Management Team
Review, Approve and Publish a Knowledge Article
Retire Knowledge Article
Retrieve Knowledge Article
Assign articles to Article Owners or Groups
Request fulfillment
Service Request Management is the process responsible for managing the lifecycle of all service requests from the users starting with the registration of the request until the fulfillment and closure of the Service Request.

The goal of Service Request Management is to reduce the complexity· and costs associated with how customers interact with IT at the same time also making sure that the customers are able to request for and obtain services within the lowest possible turnaround time.

Customer service & request processes are streamlined through automating end-user management processes. With the effective Service Request Management, you gain business transparency, visibility, and control across all of .service support.

Change management
Page A-18

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions-Appendix A
Change Management is to ensure that standardized methods and procedures are used for efficient and prompt handling of all changes to control IT infrastructure, in order to minimize the number and impact of any related incidents upon service.

Release and deployment
The Release Management Plan is a high-level description of how the unified Global Process for Release Management is designed and implemented internally within Unisys and externally to our customers, when applicable to the scope of contracted services. The plan provides a framework to design and implement the Release Management activities such as Release Planning, Release Building, Acceptance Testing, Rollout Planning, Release Preparation, Release Deployment and Managing Emergency Releases. This document also lists the various roles and responsibilities in Release Management.

Service asset and configuration
Service Asset & Configuration Management (SACM) is the process responsible for providing accurate and complete configuration information about the infrastructure components, including relationships, to support the other ITSM process.

SACM is one of the lifecycle processes in ITIL and is one of the foundations of IT Service Management. This process manages the assets of the organization in order to support the other ITSM processes, provides a logical model of the infrastructure and manages assets and configuration items by identifying, controlling, maintaining and verifying the versions in existence.

Service level management
The process responsible for formal agreements (e.g., Service Level Agreements (SLAs)) and ensuring the supporting agreements (Operation Level Agreements (OLAs)) and contracts (Underpinning Contracts (UCs)) are accurate and up-to-date. This includes the creation of the agreement (planning), obtaining agreement from the business on the content of the SLA, and reviewing service achievements on an on-going basis.

Relationship management between the service provider and the business/customer is based on the SLA. Service Level Management relates availability, capacity, performance, and costs to business demand.

Service catalog management
Service Request Catalog Management is the process responsible for creating and managing a catalog of all available services from which an end user may submit request. The Service Request Catalog integrated with Service Request Management encircles not just a list of Page A-19

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions-Appendix A
all available services, but also the request forms, underlying approval processes and sequenced fulfillment task components.

The goal of Service Request Catalog Management is to empower the end user to selfsupport, reduce the complexity and costs associated with how customers interact with IT, to Standardize/ Simplify the delivery of critical IT processes and workflows, to reduce work volume, fulfillment time and delivery, through automation. In summary, Service Request Catalog Management improves the effectiveness and efficiency of Service Request Management.

Enterprise Project Management Standards
Strategy and execution plan for the deployment of tools, documentation of processes necessary to advance I proj_ect management methodologies and provide and anterp_rise view of project and the plan of record The Unisys Services and Solutions Delivery Framework (SDF) is the unique One-Unisys framework that is applied to Unisys projects. It is based on the Project Management Institute (PMI) Program Management Book of Knowledge (PM BOK). The SDF provides an effective structure to verify that consistent, highquality management practices and repeatable processes are applied across Managed Services programs and client projects. Unisys will manage projects with standard processes and practices institutionalized in our SDF methodology.

Unisys will continue to use and update the CSC Project Management methodology residing on the City's CSI SharePoint site and that contains the following high level areas of documents, checklists, templates and other artifacts:
• Requirements Management
• Project Initiation, Charter and Funding
• Project planning
• Schedule management
• Financial management
• Risk management
• Contract management
• Change control
• Third party management
• Measuring, assessing and reporting performance
• Program Management
Unisys will update the above documents to reflect the SAFe Agile methodology being adopted.

Ability to implement an approach to holistically managing the Enterprise IT Portfolio, across the technology life cycle. Furthermore, achieve a clearer focus of the business value of IT assets, Page A-20

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions-Appendix A
delivering high-value IT projects that are strategically aligne~ to meet City business requirements.

This will provide visibility to the stakeholders and allow for decision making on the best use of limited funds available for IT and allow for the setting of priorities by the business community.

Overview of Approach
Reflect the SAFe Agile methodology being adopted, which includes but not limited to:

Understand the current state of project and portfolio management in the City Capture desired vision and outcomes from key executives Develop the portfolio management framework and processes Develop and implement a portfolio management repository Develop and execute a rollout plan to encompass the entire portfolio the CIO is responsible for Train appropriate staff
Standard processes for portfolio, demand and resource management will be adhered to across the account.

Standard reporting formats for project progress and monitoring and Dashboard Reports will be created and delivered on a periodic basis to provide city stakeholders with an easy to read update on the status of the IT Project Portfolio.

Digital Strategy Plan
Strategic Plan to address digital areas relevant to ihe City of Santa Clara, including: e-Govemment Portal, lnfonnation Dissemination, Constituent Engagement and Communities, Podcasting, Mobility, Social Media, 'Analytics, Cloud, Digital Transactions, and Open Government/Open Data The plan should include:

Defining the City's customer and their unmet needs and goals Identifying key opportunities and/or challenges
Defining the City's objectives
Financial Analysis
Developing a vision and prioritizing a set of initiatives Plan Execution and Prioritization of Initiatives
Implementation Governance
Please refer to Section 1.0.C for the Digital Strategy Plan.

Page A-21

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions-Appendix A
The onsite Applications Program Manager, Business SMEs, Enterprise Architect, and Unisys Digital strategy experts will develop and present the digital strategy plan, which will be updated annually.

Unisys will produce a "Digital Strategy Plan and Roadmap" in the first year (within 12 months) after "go live", that is intended to provide a high level framework and prioritized roadmap of Digital Government related projects and initiatives. Following the initial deliverable, this roadmap document will be revalidated and updated at least once every 12 months to reflect any changes in the City's priorities and technological changes.

Unisys will maintain this roadmap and provide effective communications on progress to ensure that the City makes progress on its citizen and community engagement goals through th_e prioritized roadmap.

Deliverable outline
An outline of the "Digital Strategy Plan" deliverable that will be produced at the end of a four to six week engagement is outlined below.
# TOC Major Area Content area (sub TOC) Comments
1 City Goals and Vision * City Goals and Visions - Describes City's Digital Government Outside in view of how Goals and Visions for the City as a City will serve its whole, and specific departments as
customers (Employees, perceived by leadership of City and Vendors, Suppliers, Department heads
partners, Stakeholders,
Citizens and
Constituents)
* Digital Government
Vision and Goals for City
* Business services and
constituent requirements
* Information and
Analytics requirements
* Experience - Branding
of the City to ensure
experience is consistent
and compelling.

Page A-22
# TOC Major Area
2 Current State of Digital
Technology in the City
3 Future State
Recommendations

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions- Appendix A
Content area (sub TOC) Comments
* Current State of Digital Use of Digital Technologies in the Government presence, City today to serve all customers - Information Architecture, processes. Gaps that still exist in Technology I Processes order meet the City's stated goals and in various visions for Digital Government.

Departments/City Technology Enablers that wfll be
~ Capabilities Required to required to fill these gaps. support Future Vision and
Goals
* Enablers / Barriers that
exist today
* Existing IT Projects that
are underway and their
alignment with Digital Gov
*Un-met Digital Prioritized list of Projects and
Government needs Initiatives supported by Financials
* Information Architecture (high level) costs and benefits and an {IA) - Information and
implementation plan {high level) in a
analytics needs of the roadmap for the City
business functions,
communities of interest,
external stakeholders,
business partners, etc.
• Prioritized list of
business requirements
* Projects Defined with
High level cost, benefit
and Financial Analysis
* Prioritized list of Projects
* Projects/ Initiatives
recommended
* Implementation
Roadmap for 2 to 4 year
timeframe
Page A-23
# TOC Major Area
4 Digital Technologies
Supplement
5 Ongoing Governance
Recommendations

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions- Appendix A
Content area (sub TOC) Comments
• Description of Projects I Report that identifies innovative Digital Technology products and services in the areas of recommended and how Digital Government, Portals,
they will be applied Information Dissemination, Digital * Latest Trends in key Transactions, Analytics, Mobility, loT, Digital Technologies Collaboration, Websites, Digital
relevant to City - Open Workspace of the Future, Constituent Data/ Open Gov, Cloud, Engagement, Business Operations, Mobility, Social Media, Social Media, Remote connections Analytics etc (in the etc. that are especially relevant to projects included in the fulfilling the City's Goals and Vision in Roadmap) closing the gap with current state
* Methodology, Templates
and Documents to track
and monitor ongoing
implementation
* Status Report Template
Tasks I Deliverables/ Acceptance Criteria
Unisys will use a team of Consultants and Digital Government SMEs, and the onsite team of Applications Program Manager, Enterprise Architect to develop and present the digital strategy plan, which will be updated annually (every 12 months).The Unisys team will work with City stakeholders who will be identified prior to the initial kickoff meeting and will be involved during the interviews, and also both of the workshops that will be conducted during the engagement to produce the final deliverable - Digital Strategy Plan.

Major Task I Deliverable Completion I Acceptance criteria 1 Engagement Plan with Interview Project Plan Produced and presented to City Schedule (Kickoff) Stakeholders and approved by the CIO 2 Interviews with Stakeholders of all Interviews completed (Questionnaires and departments interview notes produced and documented)
3 Preparation for Planning Workshop# 1) Planning Deliverable - PPT Deck and Word Document that outlines City Goals/Mission (for
Diqital Transformation), Diaital Government
Page A-24
Major Task I Deliverable
4 Prioritization/Planning Workshop
Completed (#1)
5 Road Map Workshop Completed (#2)
6 Final Presentation and Deliverable
Completed
Periodic Updates and Ongoing Governance

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions-Appendix A
Completion I Acceptance criteria
Capabilities, Enablers and Barriers completed
Planning Deliverable (updated)- PPT Deck
and Word Document that outlines City
Goals/Mission (for Digital Transformation),
Digital Government Capabilities, Enablers and
Barriers completed, with capabilities prioritized
after the Workshop, reviewed with City, and
approved by the CIO.

RoadMap Deliverable - PPT deck and Word
document that describes Initiatives/Projects and
their priorities, with High Level Financial
Analysis (costs/ benefits), priorities, High level
implementation plan and Roadmap. Completed
and approved by the CIO.

Final Presentation to City Stakeholders (PPT
Deck) and Final Deliverable - Digital Strategy
Plan Document (Word doc) completed,
presented and approved by the CIO.

Periodic Status reports will be produced regarding the progress of various activities and milestones outlined in the Digital Strategy Plan. This will be tracked by the Unisys PMO, Applications Program Manager, Enterprise Architect as well as Digital Government SMEs and the City stakeholders.

On an annual basis (every 12 months), an abbreviated version of the planning process consisting of one facilitated workshop will be conducted to update and maintain the Digital Strategy Plan document.

Innovative Products and Services Report and Meeting
Written report which identifies innovative products and services of potential use to the enterprise and departments to support business objectives and challenges based on trends in local government customer engagement and business operations service delivery and trends in the general IT marketplace The Applications Program Manager, Business SM Es, Enterprise Architect, assisted by Unisys Consultants and Local Government SM Es will develop and present semi-annually the Innovative Page A-25

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions-Appendix A
Products and Services Report (IPSR). The reports will be based on published, general IT marketplace trend data and local government trends in service delivery improvement, such as Smart City initiatives from various municipalities. The IPSR will include products that reflect new ideas or approaches to service delivery or to the introduction of new services which align with the City's Mission and Vision.

Based on feedback from the presentation of the IPSR, Unisys will update supporting plans as part of the annual update process (such as the IT Strategic Plans, Digital Strategy Plan and the Enterprise Architecture Plan) to reflect the change in Future Vision, which in turn will be updated in terms of new gaps/projects to develop the new capabilities annually. (Please refer to 2.1 .1.o.) The initial version of the Report will be produced during the development of the Digital Strategy Plan.

Subsequently, it will be updated every six months. This will be contained as a sub-component of the Digital Strategy Plan so that the report is closely tied to the Future State recommendations, and the ' roadmap developed for Digital Government Transformation.

Content Outline for the Innovative Products and Services Report (Sub Chapter of the Digital Strategy Plan document)
# TOC Major Area Content area (sub TOC) Comments
4 Digital Technologies * Description of Projects / Report that identifies innovative Supplement Digital Technology products and services in the areas of recommended and how Smart Cities, Digital Government,
they will be applied Analytics, Mobility, loT, Collaboration, * Latest Trends in key Digital Workspace of the Future, Digital Technologies Customer Engagement, Business
relevant to City - Open Operations, Social Media etc. that are Data I Open Gov, Cloud, especially relevant to fulfilling the Mobility, Social Media, City's Goals and Vision in closing the Analytics etc (in the gap with current state
projects included in the
Roadmap)
Tasks / Deliverables/ Acceptance Criteria
The initial version will be delivered as a part of the Digital Strategy Plan (refer to this section). Subsequent to the initial version. It will be updated every six months. However, the Digital Strategy Plan document itself will only be updated every 12 months.

Page A-26

CITY OF SANTA CLARA
Schedule 2- Final Service Tower Solutions-Appendix A
Operational Efficiencies Improvement Report and Meeting Written report which provides the enterprise and departments recommendations for operational improvements that increase efficiency and effectiveness through the better use of existing applications and technology or imP,_roved processes
Unisys is committed to delivering quality solutions and services to the City by collaboratively working with them in a structured, formal and transparent manner, with innovation and continual improvement recognized as key to ultimately delivering higher satisfaction.

CSIIP is a program undertaken in collaboration where CSC and Unisys identify and introduce measurable improvements and innovation opportunities. There are increasing demands for organizations to deliver "better, faster and cheaper" services to· the public and business partners. This in turn, requires that Information Technology (IT) deliver innovative and cost-effective solutions when supporting their business communities. Unisys partners with the City to deliver continuous operational efficiencies and improvement for our services and innovation for value realization and boost business performance.

The objective of CSIIP is;
• Deliver a formal plan collaboratively with the City to implement improvements and bring in innovation to services and IT processes;
• Utilizes a formal methodology and tool set to enable the tracking and management of the outstanding transition and refresh issues;
• To facilitate the highest satisfaction by providing one single place to collaboratively manage and log improvement initiatives triggered by Continual Service Improvement & Innovation Initiatives.

All the different list items and tracking sheet info from the disparate activities are consolidated to a single repository, transparent and visible to both parties, and jointly managed The CSIIP program will be formally launched via a collaborative workshop with the City. This validates the strategy and objectives, and identifies/classifies/prioritizes the initiatives and contributive actions required, short-term and long-term, along with respective owners. All of the improvement initiatives, innovation plans/roadmaps and related action items are centrally located and managed through the on-going governance structures.

The goal of the workshops is to:
• Identify innovation ideas;
• Categorize the identified idea in terms of functional areas/ ownership of project execution; • Further classify the ideas so that we understand their technical maturity, level of impact they can bring to the program, and ease of implementation;
• Complete high-level opportunity profiles for each innovation opportunity (including more quantitative assessment of ROI and overall benefits) and suitable timing in terms of implementation;
• Determine how these innovations (including project ideas) can be more effectively built into a future state architecture and roadmap for the program.

The governance of the CSIIP component falls within the overall Account Governance structure.

Innovation ideas will be analyzed for progress against planned results.

Page A-27

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions-Appendix A
Unisys will update the Operational Efficiencies report, which provides the enterprise and department recommendations for operational improvements that increase efficiency and effectiveness through the better use of existing applications and technology. This report will be reviewed quarterly as part of the operational governance meeting. The onsite delivery team, the Unisys SEO office, the service desk, and other Unisys offsite supporting teams will be responsible for creating and updating this report.

End User and Key Department Personnel Scheduled
Customer Satisfaction Survey Report and Meeting
Written report that presents the results of the annual End User and key department personnel scheduled customer satisfaction surveys and recommendations on how to improve areas of customer dissatisfaction.

Unisys will draw from experience and best practices to ensure the survey is planned and executed toward a successful outcome. Unisys and the City will work on a mutually agreeable list of questions for the survey. The survey will be sent to the departments using the ServiceNow framework, which will also collate the results. After a detailed analysis, a report will be provided. The report will include results, provide recommendations, and establish metrics for improvement. Follow-on meetings, as described in the governance processes, will review the metrics, note areas for improvement and action.

Services Strategic Review Report and Meeting
Written report that assesses how Service Provider is performing against enterprise and deparlment strategic objectives of the Agre_ement and provides relevant service imp_rovement recommendations and action p_/an The Enterprise Architect will develop and present annually the Services Strategic Review Report (SSRR) based on the strategic objectives identified in the Enterprise Architecture Plan and the IT Strategic Plan and associated plans, such as the digital strategy. The SSRR will be organized around identified gaps between the Future Vision and t~e Current State of City capabilities which based on the City's departmental goals. These goals form the foundation for technology projects intended to improve the delivery of services to the City's constituents in the fulfillment of the City's Mission and Vision. The SSRR will identify any gaps in expected deliveries and provide recommendations for remediation including steps to be taken to improve delivery and recommendations for process change or other performance improvements. Any approved change in approach or content of deliverables will also be reflected back into the supporting plans as needed as part of the annual update of those plans. (Please refer to 2.1.1 .o.) Annual Execution Plan
Written plan that outlines the major activities, projects and associated schedules that the Service Provider will perform in the coming year to deliver the Services meeting existing Service Levels and to meet enterprise and department business plans and objectives outlined in the IT Strategic Plan (see Schedule 17).

After the IT Strategic plan and associated plans, such as the digital strategy have been developed, it must be translated into a comprehensive execution plan. The Annual Execution Plan (AEP) will clearly outline the objectives of the Strategic Plans execution, the activities that are needed to achieve these objectives, Page A-28

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions-Appendix A
who is responsible for these activities, and when the objectives are to be achieved. The AEP will outline the manner in which the strategic vision is to be achieved. The implementation plan translates the strategy into day-to-day management.

The Applications Program Manager and Infrastructure Program Manager will develop the AEP plan to execute the strategy.

First the strategy will be translated into objectives, which will then be used to create the tasks, activities, and responsibilities that are required to achieve the objectives of the strategy. This forms the AEP, or prescriptive work plans, which will be kept short and action-oriented. The AEP will be translated into roadmaps, project plans, and work plans for the Service Towers, so that progress against the AEP and IT strategic plan can be measured.

The plan will be reviewed monthly as part of the Service Tower Review Meetings and adjustments made as appropriate using the change management process.

Technology Refresh Plan
Written plan that to be developed., maintained, updated, and followed by the Service Provider In periodically replacing or refreshing the technology used to perform the Services or provide the deliverables, or otherwise used by the Service Provider and its subcontractors in connection with the systems. The Plan will be aligned 1 to the City's budgetingprocess. l
The Technology Refresh Plan (TRP) is derived from the IT Strategy, Application changes, and Infrastructure capacity. Each of the main towers hardware and software roadmaps; Applications and Data Repositories, Infrastructure, and End Point are updated throughout the year. The Enterprise Architect will work with each tower lead in providing an updated Technology Refresh Plan detailing the technology impacting the City's budgeting process. As such, any new or augmented technology component needed to fulfill the delivery of services or project deliverables will be detailed in the TRP. This will include both the introduction of new capabilities and the upgrade or refresh of existing capabilities with new technology. The Technology Refresh Plan will align with the City's budgeting process by reflecting the budget categories for capital expense. The TRP will also reflect the roadmaps of the Tower plans, Enterprise Architecture Plan, Digital Government Plan, and the IT Strategic Plan in order to provide concrete budgetary estimates of expected costs.

The TRP provides the following table of contents:

Overview of the TRP objectives
o Reference to road maps and plans that justify the technology proposed that meets the business objectives
Trade-off analysis of why technology was chosen, or reference therein; congruence with the Enterprise Architecture
Budget costs and rationalization
Page A-29

CITY OF SANTA CLARA
Schedule 2 - Final Service Tower Solutions-Appendix A
Schedule of milestones to meet City's timelines
Approval process as applicable
Page A-30
SCHEDULE3A

CROSS - FUNCTIONAL SERVICES SOW

TO MASTER SERVICE AGREEMENT

BY AND BETWEEN

CITY OF SANTA CLARA
AND

SERVICE PROVIDER
Schedule 3A - Cross - Functional Services SOW
Table of Contents
l. OVERVIEW ....................................................................................................................................................... 3

2. SERVICE DESCRIPTION AND MAJOR FUNCTIONS ............................................................................. 3

3. SUPPORTED SYSTEMS AND QUA.i'ITITIES .............................................................................................. 5

4. RESPONSIBILITY MATRIX .......................................................................................................................... 5

5. SUPPORT REQUIREMENTS ......................................................................................................................... 5

6. SERVlCE LEVELS ........................................................................................................................................... 5

7. REPORTS .......................................................................................................................................................... 5

8. CRlTICAL DELIVERABLES ......................................................................................................................... 6

9. CHANGES TO MSA ......................................................................................................................................... 9 List of Exhibits

1. EXHIBIT I - DEFINITIONS ................................................................................................................... 8

2. EXHIBIT 2 - RESPONSIBILITY MATRIX .......................................................................................... 9

3. EXHIBIT 3 - SUPPORTED ENVIRONMENTS AND TOOLS ........................................................... 40

Page 2 of 45 ends

Schedule 3A- Cross - Functional Services SOW

1. Overview
This Statement of Work ("SOW') has been entered into pursuant to the Master Services Agreement (the "MSA") between Customer and Service Provider.

2. Service Description and Major Functions
Service Provider will perform the common services and activities that apply to the provision, delivery, and management of all IT services across all Service Towers (collectively, the "Cross Functional Services").

In addition, Service Provider will be responsible for the development, implementation, ongoing maintenance and management of, and upgrades to, the common set of IT life cycle and ITSM processes and tools that will be utilized across all Customer IT service delivery organizations including third party providers (the "ITSM Suite"), and integration of the ITSM Suite with Customer systems, tools and interfaces. Fees for the Cross Functional Services will be included within the Fees for each Service Tower as specified in Schedule 5 to the Agreement. Service Provider will ensure that (A) applicable Service Towers are integrated and consistent with the Cross Functional Services, and (B) the Services are delivered utilizing the cross-Service Tower processes and tool sets (e.g., tools in the ITSM Suite); provided.

Service Provider's provision of the Services shall comply with all applicable standards, policies, and state and federal regulations and laws (e.g., ISO 27001, ISO 17799, PII, PCI, HIPAA, CJIS). Service Provider's provision of the Services shall be consistent with all applicable standards (e.g., ITIUITSM, COBIT, CMMI Level 3, ISO 20000, ISO 27301, ISO 21500, ISO 19770).

IT Organization Guiding Principles
The following are guiding principles of the Customer that the Customer expects Service Provider to achieve across the IT services environment. These guiding principles will be a key performance measurement as part of a balanced scorecard contract governance approach. These guiding principles will be a key basis for the eighteen-month review detailed in Section 2.1 .3. ■ Roles and responsibilities are well-defined and understood. ■ The right skills and teams in place to meet service requirements. ■ Work is performed effectively in cross-functional groups, not in silos. ■ Sound relationships and teamwork exists between teams. ■ A strong customer focus will be found among team members. ■ Strong and trusted relationships exist with customer groups. ■ Service levels are in place with the business that transcends functional groups. ■ The business understands the value delivered by the Service Provider. ■ A consistent and effective project methodology is in use. ■ A clear set of IT principles underlie decision making. ■ Clarity in who performs decision making.
■ Work priorities are consistent across all IT teams.
■ Resources are well-managed.
■ The organizational structure is the most appropriate to deliver the services.

Across all Services provided,· Service Provider understands that the objective of the relationship is not just for Service Provider to operate the environment, but for Service Provider to take a leading role in driving alignment between IT strategy and Customer IT business objectives with the overall objective of making Customer IT the IT provider of choice for all Customer departments. Each Service Tower will both perform the core responsibilities associated Service operations and driving operational efficiencies as well as contribute to the strategic development of services within Customer's business. At the same time, Service Provider personnel will work seamlessly across Service Towers in such a manner that the Customer I End-User will experience the Services from a seamless perspective (i.e., not siloed by Service Tower). The IT Governance responsibilities section and the associated resources detailed in this SOW provide the core of IT service management but all resources and Services are responsible for contributing

Page 3 of 45 ends

Schedule 3A- Cross - Functional Services SOW
recommendations, expertise and project efforts to continue to transform the services provided to the Customer departments.

Without limiting Service Provider's obligations under the Agreement, including this Schedule 3A and the other Schedules referenced in the Agreement, Service Provider's solution and technical approaches for this Service Area shall conform with the Service Provider's solution and technical approaches as provided in the following documents, as such documents may be amended during the term of this Agreement by the Parties in writing, and which are hereby incorporated into this Schedule 3A by reference. Nothing in the following documents shall limit Service Provider's obligations under the AgrE;lement. If the provisions of this Schedule 3A or any other Schedule (including Appendixes) conflict with one or more of the following documents, the provisions of this Schedule 3A or such other Schedule (including Appendixes) shall control.
• Final Service Area Solutions.docx

2.1.1 Satisfaction Surveys
In addition to the ongoing Service Desk customer satisfaction surveys referenced in Schedule 3B, Service Provider will work with Customer's CIO or their designee to prepare scheduled satisfaction surveys of (1) Customer end users, and (2) Customer department key personnel. These surveys will be distributed to ( 1) Customer end users, and (2) department directors, managers and key subject matter experts (including the Customer's IT Department ("ITD")) on an annual basis and will be used to measure the overall satisfaction with the operational and strategic services being provided by the Service Provider.

Key components of the customer satisfaction surveys shall include measurement of customer satisfaction with Service Provider performance related to:
• Integration of Services across Service Towers (seamless services to the End-Users) • Focus on innovation
• Focus on operational improvements
• Business analysis services effectiveness for Customer departments • Service Provider training in and knowledge of the City's environment (including departments' specific businesses)
• First Call Resolution
• Service Desk's end to end ownership of tickets (regardless of ultimate Incident resolver group or entity that fulfills a Service Request)
• Knowledge of End-User's Service Desk call history and persona • Knowledge of an End-User's ticket history before engaging an End-User for break-fix or Service Request activities
• Knowledge of the Services and Services available to the End-Users (e.g., service catalog) • Transparency and proactive communication in ticket handling Service Requests and Incident Resolution
• Knowledgebase currency and relevancy to End-Users
• Level of End-User disruption and time required for patching and testing • Self-service services
• Online portal for access to Procedures Manual, Service Provider contracted Service Levels, all third party provider documentation (including Service Levels), Customer-provided third party documentation, Service Provider Services reporting, knowledge base, frequently asked questions, self-service services, and an end-user interface for Incident ticket entry and status tracking
Service Provider shall meet with Customer annually and provide a report on its annual End-User and department survey findings to the Customer, including the identification of any areas of Customer

Page 4 of 45 ends

Schedule 3A - Cross - Functional Services SOW
dissatisfaction. Service Provider shall develop, for the Customer's review and approval, service improvement plans as required to address areas of Customer dissatisfaction. This report and meeting is a Critical Deliverable, as set forth in Section 8 below.

Satisfaction Surveys shall meet the associated Service Levels set forth in Schedule 4.

2.1.2 Continuous Service Improvement Process
Service Provider will provide Continuous Service Improvement Processes (Continuous Service Improvement Process at a customer/account-specific level across all Service Towers. Service Provider will foster a culture of continuous improvement where individuals are encouraged to bring ideas based on observations within projects and day to day operations sharing best practices and lessons learned.

As part of its Continuous Service Improvement Process obligations, Service Provider shall be responsible for providing reports to and meeting with the Customer regarding proposed operational improvement recommendations, as well as innovative products and services. These two Critical Deliverables are defined in more detail in Section 8 below.

Additionally, every eighteen (18) months Service Provider will engage a team of Service Provider subject matter experts and management staff to perform a strategic review of the Services and develop a corresponding report to the Customer (the "Services Strategic Review Report''); this written report and related review meeting with Customer will focus on assessing whether Service Provider is meeting the strategic objectives of the relationship and guiding principles of the Customer's ITD as documented earlier in this Section. Service Provider will report on the finding of the review and create action plans for recommendations coming from the review. This activity is' also a Critical Deliverable, as identified in Section 8 below.

3. Supported Systems and Quantities
Not applicable to this SOW.

4. Responsibility Matrix
Exhibit 2 sets forth the Responsibility Matrix for services relevant to this SOW.

The responsibilities defined in the cross functional services matrix apply to all services delivered within the account. •

5. Support Requirements
Support requirements are specified in Section 5 of Schedules 3B - 3E.

6. Service Levels
Service Levels that apply to this SOW are provided in Schedule 4 - Service Levels.

7. Reports
Service Provider shall provide reports relating to the Cross-Functional Services, as set forth in Schedule 7 - Reports. Service Provider will recommend new reports as capabilities and requirements evolve.

Page 5 of 45 ends

Schedule 3A-Cross - Functional Services SOW

8. Critical Deliverables
Customer has identified a number of Services deliverables that it considers to be of particular importance ("Critical Deliverables"). These Critical Deliverables span Service Towers and are foundational to quality IT service delivery and the Customer's goals and objectives the Agreement. Service Provider shall provide these Critical Deliverables to Customer in accordance with the descriptions and timelines set forth in the table below. In some cases, Critical Milestones may be associated with Service Provider's failure to timely provide such Critical Deliverables to Customer (see Schedule 4 for applicable Critical Milestones and Corrective Assessments). Critical Deliverables are not meant to represent all deliverables Customer expects from the Service Provider.

As of the Effective Date of the Agreement, the Critical Deliverables associated with Cross - Functional Services are provided in the table below.

Deliverable Description Timeline
Procedures Manual Guide that details the standard operating Customer approved version before the procedures for all services. This has end of transition items such as process based procedures Updated regularly through change such as Incident management as well as management
functional base tasks such as PC
installs.

IT Strategic Plan Plan that analyzes the City enterprise IT 12 Months from service commencement organization's current state, future state
and develops a 2-4 year roadmap to help Updated annually it achieve identified goals and objectives.

Elements include:
• Current State: review and
assessment of business
strategy, vision and goals,
capabilities and priorities,
financials, IT environment,
service gaps
• Future State: IT vision, IT
capabilities, enterprise
architecture, key processes,
governance model, performance
management
• Roadmap: budgeting,
identification and prioritization of
IT initiatives for the 2-4 year
horizon, and strategic plan
roadmap development
lnformation/Cyber A current information security plan and Before end of Transition, then every 12 Security Plan robust set of policies exist as an input. months thereafter Service Provider will analyze current Updated as required through change security posture and provide management
recommendations to address any areas
where deficiencies or threats have been
identified for both on prem and cloud
assets. Result will be an updated written
plan and procedures that provide the
operational and technical responsibilities
associated with the Security table in this
SOW (e.Q., data security, physical

Page 6 of 45 ends

Schedule 3A- Cross - Functional Services SOW
Deliverable Description Timeline
security, security operations, patching,
malware prevention, monitoring and
Incident management, threat and
vulnerability management).

The Plan must be consistent with the
NIST Cybersecurity Framework.

Business Continuity The Business Continuity Plan project 6 months from go-live • Plan includes working with key stakeholders
to re-validate the City's critical business Updated regularly through change applications and infrastructure assets management
based on the already defined
prioritization framework and
updating/enhancing the existing
Business Continuity Plan that
encompasses all current mission-critical
City Applications and the associated IT
assets.

Disaster Recovery Plan This plan is to update and enhance the 6 months from service commencement detailed requirements and design
solutions for the recovery of critical IT Updated regularly through change assets in the event of a_ major disaster or management • service disruption.

Enterprise Architecture Develop an analysis, blueprint and 12 months from go live and every 12 Plan implementation plan for the City's data, months thereafter applications, and technology.

Updated as required through change
management
Communications Plan Written plan that provides direction on 6 months from service commencement how the Service Provider will engage and every 12 months thereafter with ITD and other City departments on
an ongoing basis, including at both the Updated as required through change strategic and operational level. management
ITIL Service Strategy and execution plan for the 6 months from go-live Management Standards deployment and ongoing maintenance of tools, documentation of process Updated regularly through change necessary to have consistent service management
management within the enterprise
Enterprise Project Strategy and execution plan for the 6 Month from go-live Management Standards deployment of tools, documentation of processes necessary to advance project Updated regularly through change management methodologies and provide management
and enterprise view of project and the
plan of record
Digital Strategy Plan Strategic Plan to address digital areas 12 months from go live and every 12 relevant to municipalities, including: months thereafter mobility, social media, analytics, cloud,
digital transactions, and open Updated as required through change government/open data management
The plan should include:

Page 7 of 45 ends

Schedule 3A- Cross - Functional Services SOW
Deliverable Description Timeline
• Defining the City's customer and
their unmet needs and goals
• Identifying key opportunities
and/or challenges
• Defining the City's objectives
• Financial analysis
• Developing a vision and
prioritizing a set of initiatives
• Plan, execution and prioritization
of Initiatives
• Implementation governance
Innovative Products Written report which identifies innovative Every 6 months during the term of the and Services Report products and services of potential use to Agreement and Meeting the enterprise and departments to
support business objectives and
challenges based on trends in local
government customer engagement and
business operations service delivery and
trends in the general IT marketplace
Operational Efficiencies Written report which provides the Every 6 months during the term of the Improvement Report enterprise and departments Agreement and Meeting recommendations for operational
improvements that increase efficiency Presented at quarterly Operational and effectiveness through the better use Governance meeting of existing applications and technology
or improved processes
End-User and Key Written report that presents the results of Every 12 months during the term of the Department Personnel the annual End-User and key Agreement Scheduled Customer department personnel scheduled
Satisfaction Survey customer satisfaction surveys and
Report and Meeting recommendations on how to improve
areas of customer dissatisfaction.

Services Strategic Written report that assesses how Service Every 12 months during the term of the Review Report and Provider is performing against enterprise Agreement Meeting and department strategic objectives of
the Agreement and provides relevant
service improvement recommendations
and action plan
Annual Execution Plan Written plan that outlines the major Every 12 months during the term of the activities, projects and associated Agreement
schedules that the Service Provider will
perform in the coming year to deliver the Updated regularly through change Services meeting existing Service Levels management
and to meet enterprise and department
business plans and objectives outlined in
the IT Strategic Plan (see Schedule 17).

Technology Refresh Written plan that to be developed., Due each January during the term of the Plan maintained, updated, and followed by the Agreement (to align with the City's Service Provider in periodically replacing annual budget process). or refreshing the technology used to
perform the Services or provide the
deliverables, or otherwise used by the

Page 8 of 45 ends

Schedule 3A - Cross - Functional Services SOW
Deliverable Description Timeline
Service Provider and its subcontractors
in connection with the systems. The Plan
will be aligned to the City's budgeting
process.-

9. Changes to MSA
This SOW does not change any terms in the MSA and its Schedules.

Page 9 of 45 ends

Schedule 3A- Cross - Functional Services SOW
EXHIBIT 1 - DEFINITIONS
See Schedule 1 - Definitions for a list of defined terms and associated definitions.

Page 10 of 45 ends

Schedule 3A - Cross • Functional Services SOW
EXHIBIT 2 - RESPONSIBILITY MATRIX
The Responsibility Matrix below shows which party is responsible for the listed task. It is not the intent of the Responsibility Matrix to absolutely identify or define every process, activity or task to be performed by Service Provider as a managed services function.

The responsibility matrices for Cross - Functional Services is set forth below.

GENERAL RESPONSIBILITIES
IT Governance
No. Function/Responsibility Service Customer Provider
ManaQement and Communication
Manage and Administer the portfolio of service the

1. Customer delivers to its customers through a customer X facinq service cataloq
Interface with users of Customer IT services to

2. understand where opportunities for improvement exist X and make recommendations for portfolio improvements
Interface with other Service Provider customers as
well as IT industry and municipal government user

3. groups to understand technical and strategic direction; X recommend changes to the service portfolio based on
industry best practices and evolution

4. Develop and execute communication plans (e.g. IT
best practices, marketing plans for new services, X project success stories, presentation materials for stakeholder meetinQs)

5. Approve communication plans X

6. Participate in IT Users group meeting, contribute X acienda items and lead select aqenda items

7. Participate in IT executive meetings with Customer
stakeholders, including Customer departments as X
required

8. Participate in other meetings as necessary to support X overall objectives Standards Management

9. Establish and maintain Procedures Manual (e.g., all
operations manuals, support plans, user guides, X
procedures for interactinq with the service provider)

10. Approve Procedures Manual X

11. Proactively amend the Procedures Manual as required to reflect current procedures and other designated X
Procedures Manual content

12. Provide Customer with on line portal access to X Procedures Manual Proiect Manaoement

13. Establish a governance structure for portfolio and X project management

14. Define project priorities for IT enterprise oroiects X

Page 11 of 45 ends

Schedule 3A- Cross - Functional Services SOW
No. Function/Responsibility Service Customer Provider

15. Establish a comprehensive capacity and demand
management planning process to include current X capacity vs. utilization and capacity requirements oroiection for a rollinq one year oeriod

16. Provide business demand projections to support X Service Provider caoacity planninq

17. Review and approve capacity management planning
process
X

18. Define, provide and implement tools that allow for the effective capac_ity monitoring/trending and reporting of X IT infrastructure, aoolications and IT components

19. Identify future business requirements that will alter X capacity requirements (e.g. strategic plan)

20. Participate in all capacity planninQ activities X

21. Assess capacity impacts to all technology when X
adding, removing or modifying Services, applications
and infrastructure

22. Continually monitor IT resource usage to enable X
proactive identification of capacity and performance
issues

23. Capture capacity trending information and forecast X future Customer capacity requirements based on
Customer defined thresholds

24. Assess Incidents/Problems related to throughput X
performance

25. Recommend changes to capacity to improve service X
performance

26. Develop and present to Customer quarterly Capacity X Manaoement plan

27. Review and approve quarterly capacity management X
plan

28. Develop and present quarterly capacity management X executive summary

29. Assess impact/risk and cost of capacity chanqes X

30. Aoorove capacity related recommendations X

31. Maintain capacity levels to optimize use of existing IT X resources and minimize C~stomer costs to deliver
Services at aQreed to Service Levels

32. Ensure adequate capacity exists within the IT X
environment to meet Service Levels taking into
account daily, weekly, hardware and software lifecycle
and cyclical business variations in capacity demands

33. Develop and implement a best practices project X manaqement methodoloqy framework

34. Perform project/sub-project cost estimation for a
specific Service Provider scope of work using agreed
standard and consistent project estimation tools and
techniques that can size projects and can categorize X
them by level of effort (e.g., minimal, medium, difficult).

Coordinate with Customer, third party providers and
other third parties as required

35. Develop and document a detailed project plan and X

Page 12 of 45 ends

Schedule 3A - Cross - Functional Services SOW
No. Function/Responsibility Service Customer Provider
update such project plan on periodic basis as defined
by Customer (e.g., monthly, bi-monthly, weekly). The
initial project plan and updates thereto will be subject to Customer's review and aooroval

36. Manage projects using industry standard best
practices for projects such as infrastructure
deployment projects, application implementation X
projects, and RFP development and vendor selection
projects

37. Provide project management as defined in the project requirements and plan, including Customer, third party X providers and other third parties as required

38. Periodically provide (at the frequency specified by Customer), and review with Customer, Service
Provider project metrics reporting on Service X Provider's achievement of milestones and acceptance of deliverables and other measurements associated
, with each project phase, sub-project, and activity

39. Conduct periodic (e.g., weekly) project status meetings with appropriate Customer stakeholders in accordance
with the project communications plan with Customer X
project manager and other key Customer participants
as Customer mav require

40. Participate in periodic project status report meetings X 41 . Provide written project status reports on a mutually agreed frequency to the Customer project manager,
including status updates of applicable items in the X project plan (e.g. project schedule, budget), in a format agreed to by Customer and documented in the
Procedures Manual

42. Execute projects in accordance with Customer
guidelines and standards and consistent with industry
best practices (e.g., PMI best practices), including X executing standard project life cycle activities (e.g., project initiation, planning, execution, control and
closure, and acceptance)

43. Review and approve all changes of scope, key X
milestones, key assumptions, and project budgets

44. Manage and maintain a central repository and project X management applications/tool-set

45. Maintain a central PMO web site X

46. Maintain an executive dashboard for planned and in X flight projects

47. Maintain the portfolio and proiects repository X

48. Monitor project portfolios and programs, focusing on X the horizontal impact of Customer projects

49. Manage Service Provider resources utilization both for X operations and project usage

50. Coordinate implementation projects with impacted
departments, functional areas and/or vendors and X
other City stakeholders
51 . Work with departments to facilitate alignment of project X work being led by other entities

Page 13 of 45 ends

Schedule 3A- Cross - Functional Services SOW
No. Function/Responsibility Service Customer Provider

52. Prioritize and approve plan of record projects X

53. Manage and execute the project status review data
gathering process, annual assessment of all IT related X projects in the Customer's environment

54. Assist Customer with reviewing and prioritizing capital X IT budget requests

55. Provide support for planned special events during
customer normal business hours and after hours (on X
an exception basis)
Other

56. Conduct administrative and operations clean up
activities on an ongoing basis (e.g., closing inactive X accounts, non-active VPN users)

57. Develop written materials for award applications and presentations for City-attended conferences, as X
requested by the City
Tools and Knowledgebase
No. Function/Responsibility Service Customer Provider
Tools
Provide, manage, maintain, operate and utilize the
integrated ITSM Suite and integrated web portal in
accordance with industry best practices. The modules
will include: ■ Service Desk
■ Incident management/problem management
■ Event management

1. ■ Configuration management X ■ Change management and release management
■ Asset management and CMDB
■ Service Request management
■ Knowledge management
■ Software license management
■ Project manaqement
Develop, document, manage, maintain and utilize

2. cross-Service Tower ITSM processes based on the X
ITSM Suite standard processes
Provide, manage, maintain, operate and utilize the
single secure ITSM web portal for Customer access to
all documentation described in the Agreement (e.g.,

3. Procedures Manual, Service Provider contracted X Service Levels, all third party provider documentation (including Service Levels), Customer-provided third
party documentation, Service Provider Services
reporting)
Provide, manage, and maintain third party provider

4. access to the ITSM Suite, integrated components and X the ITSM web portal for use in the delivery of IT services in their respective service areas

5. Oversee and enforce use of the integrated ITSM Suite, X integrated components and processes and ITSM web

Page 14 of 45 ends

Schedule 3A- Cross• Functional Services SOW
No. Function/Responsibility Service Customer Provider
portal across Service Towers and third party provider - managed IT service areas
Provide Customer and third party provider inquiry and
reporting access into the ITSM Suite via a real-time

6. access reporting portal in exportable and analyzable X format and provide ad hoc and recurring (e.g., monthly) reporting as scheduled or requested by
Customer
Design, implement and maintain the ITSM Suite to

7. allow cross-IT operational tool integration and X
reporting

8. Integrate the ITSM Suite with Service Desk tools and processes
X
Develop ITSM Suite reports and dashboards (e.g.,
performance and balanced scorecard dashboards) to

9. support the execution of responsibilities of key Service X Provider and Customer roles and governance bodies and meetings, as defined in Schedule 17 to the
Agreement

10. Provide and maintain a self service web portal for all authorized Customer end users~English-based EndUser portal that provides and maintains knowledge X base, frequently asked questions, and an end-user
interface for Incident ticket entrv and status tracking

11. Provide licenses required for Customer End-User and X suooort staff to access the Suppler provided toolset

12. Develop a detailed customer facing IT service catalog which details Services offered including all Service
options, pricing, installation timeframes, order process X (e.g., new, change & remove service) and
prerequisites
Knowledge ManaQement and KnowledQebase

13. Develop and execute an enterprise-wide knowledge - management plan across all Service Towers and third X party services, with roles and responsibilities for Service Provider, Customer and third party providers

14. Participate in development of knowledge management X plan

15. Aoorove knowledQe management plan X

16. Develop procedures for knowledge management,
based on Client-approved knowledge management X
plan

17. Approve knowledQe manaQement procedures X

18. Create, maintain and update knowledgebase entries
on an ongoing basis, as such knowledge is developed
(e.g., through Incident Resolution activities, Root
Cause Analyses, event management activities, X
Service Requests, new or modified operational
procedures, any new release of information pertaining
to changes and uoarades)

19. Update knowledgebase as relevant, for knowledge X that is generated by Customer

20. Provide the suooort aQreements with third party X

Page 15 ends

Schedule 3A- Cross - Functional Services SOW
No. Function/Responsibility Service Customer Provider
vendors for access to knowledge bases and Level 3
support
21 . Coordinate knowledgebase updates from third party
providers as relevant, for knowledge that is generated X by third partv oroviders

22. Provide Customer's authorized end users with single X web oortal access for all knowledqebases

23. Maintain accuracy and currency of the
knowledgebases in order to meet associated Service X
Levels

24. Audit knowledgebases to ensure that Service Provider and Customer are following established knowledge X
manaqement orocedures

25. Periodically review knowledgebases and provide X reportina on accuracv of same

26. Create, maintain and regularly update frequently
asked question content for in-scope services available X on the self service portal

27. Make content creation recommendations to the City
and third-party service providers for out-of-scope X
services

28. Provide templates and best practices to the City and/or third-party Service Providers related to the creation of X out-of-scope content

29. Manage and maintain third party provider
documentation in Service Provider managed X
knowledaebase

CROSS FUNCTIONAL SECURITY RESPONSIBILITIES
Sec~rity Services
High-level Security Functions
No. Function/Responsibility Service Customer Provider

1. F orensics/Pentest X

2. Policv Develooment X

3. Policv Comoliance X

4. Security Risk Assessment X

5. Physical Security at Service Provider Service X Locations

6. Recommend environmental controls at X Customer Service Locations

7. Provide environmental controls at Customer X
Service Locations

8. Provide environmental controls at Service X Provider Service Locations

9. Identity and access management (policy, X
orocess, procedures)

10. Access administration & execution X

Page 16 ends

Schedule 3A- Cross - Functional Services SOW
High-level Security Functions
No. Function/Responsibility

11. 12.

13. 14.

15. 16.

17. Participate with security Incident response team
AVERT
securit and non-securit

22. Provide Customer policies and requirements
relatin to securit

23. Participate in Customer information security
awareness ro rams

24. Provide a Service Provider information security
officer that works with Customer or Third Parties
for securit re uirements and activities

25. Remain up to date with current IT security
trends, threats, common exploits and security
best ractices

26. Develop and implement an lnformation/Cyber
Security Plan, to include physlcal and logical
security plans consistent with Customer policies
with respect to security and develop and
provide documentation demonstrating
adherence to Customer policies and
requirements relating to security for Customer's
review and approval. At a minimum, to include a
security framework, end-to-end scope to cover
all systems and data, regular risk assessments
and threat modeling, proactive Incident
response planning, and a committed cyber
security resource leading the implementation
effort

27. Review and approve Information I Cyber
Security Plan, including physical and logical
securit plans

28. Protect Customer data, logically and physically,
when in use, at rest and during transmission
against unauthorized access or modification,
which includes compliance with Customer's
cyber security standards and any other
Customer olicies relatin to data securit
Physical Security at Customer Service
Locations

29. Manage the Customer Service Location
end oints e. . card readers

Page 17 of 45 ends

Service
Provider
X
X
X
X
X
X
X
X
X
X
X
Customer
X
X
X
X
Schedule 3A- Cross • Functional Services SOW
High-level Security Functions
No. Function/Responsibility Service Customer Provider

30. Manage cabling to designated interface points X
at Customer Service Locations

31. Provision and decommission badges as X
required for Service Provider Personnel access
to Customer Service Locations

32. Provide and manage other Customer Service X
Location physical security as required by
Customer (i.e., auards, video recording)

33. Provide, maintain and report approved X
Customer Service Location access list for
Service Provider Personnel to Customer in
accordance with Customer policies and
requirements, for Customer's review and
approval

34. Aporove Customer Service Location access list X

35. Manage third-party access to Service Provider X
zones in Customer Service Locations in
accordance with Customer policies and
requirements relating to security {e.g.,
escortinq, badqina)

36. Define and provide Service Provider access X
zones in Customer Service Locations
Physical Security at Service Provider
Service Locations

37. Provide physical security at Service Provider X
Service Locations in accordance with applicable
Customer policies, requirements and industry
standards
Security ODerations
Securitv lntearitv Advisory

38. Provide security advisory information to X
Customer in an aoreed uoon manner

39. Evaluate security advisories, assign a risk value X and communicate recommended action plan to
Customer
Patch Management

40. Recommend Customer policies related to X
software and security patch deployment and
priority levels

41. Review and approve Customer policies related X
to software and security patch deployment and
orioritv levels

42. Comply with Customer policies related to X
software version control and patch manaqement

43. Review all software and security patches X
relevant to the IT environment and classify
oatches based on Customer policies

44. Install software and security patches in X
accordance with chanoe management process

45. Review and approve security patch X
deolovments

Page 18 of 45 ends

Schedule 3A- Cross - Functional Services SOW
High-level Security Functions
No. Function/Responsibility Service Customer Provider
Ma/ware Prevention

46. Install, configure and operate malware X
protection software on service environment
device endpoints (where possible) for
continuous scanning, eradication and reporting
of detected malware and malware Incident
Resolution

47. Deploy anti-malware updates and patches X
following a Malware Incident per the Customer
patch and change and release management
procedures

48. Provide automated detection and removal of X
malicious code usinq anti-malware software

49. Monitor Service Provider information and X
manage up-to-date information on malicious
code outbreaks and deploy the appropriate
software signature files to protect against the
malicious code

50. Promptly notify Customer on detection of X
malicious code within Customer's IT
environment
51 . Implement the Customer established action X
plan and escalation procedures for a malicious
code event beyond what is automatically fixed
bv the anti-malware software
Security Information and Event Management
(SIEM)

52. Manage security logs and aggregate data X
across Service Tower components (e.g.,
network, security, servers, databases,
applications), and consolidate monitored data to
help avoid missina imoortant security events

53. Review event data for common attributes and X
correlate events into meaningful groups that can
be used for risk identification

54. Provide automated analysis of correlated events X
and alert Customer, Service Provider team and
third oarties as reauired (e.g., dashboard, email)

55. Provide dashboard reporting tool that takes X
event data and turns it into informational charts
to assist in seeing patterns, or identifying
activitv that is not formina a standard pattern

56. Provide automated compliance function that X
gathers compliance data, and produces reports
that adapt to existing security, governance and
auditina orocesses

57. Retain Customer historical data to facilitate X
correlation of data over time and comply with
Customer data retention requirements

58. Provide forensic analysis capability {i.e., ability X to search across logs on different nodes and
time oeriods based on soecific criteria)

Page 19 of 45 ends

Schedule 3A - Cross - Functional Services SOW
High-level Security Functions
No. Function/Responsibility. Service Customer Provider
Monitoring and Incident Management

59. Provide, implement and manage Customer- X
approved security analysis and monitoring tools
and processes, and provide documentation
demonstrating adherenc·e to Customer policies
related to security and reportinq manaqement

60. Report security risks and security Incidents to X
the Customer, in accordance with Customer
policies and consistent with lnformation/Cyber
Security Plan Risk Manaqement provisions

61. Provide documented details of security X
Incidents, including history and management
activities

62. Resolve security risks and breaches originating X
from internal and external sources

63. Coordinate the Resolution of security risks and X
security Incidents (e.g., denial of service
attacks, spoofing, web exploits) originating from
outside the Customer IT environment
System Administrative Privilege Support

64. Disable terminated users or inactive accounts in X
accordance with Customer policies

65. Identify and report to Customer policy violations X originating from administrative IDs (e.g., login
violations, resource access violations)

66. Identify and report to Customer systematic X
attacks (e.Q., attempts to logon)
Security Status Checking and Validation

67. Maintain Service Tower documentation required X
to support security assessments, audits and
internal control and control testinq

68. Support audit activities by providing a security X
assessment audit coordinator to define audit
controls and coordinate audits

69. Provide security assessment audit focal point to X
define audit controls and coordinate audit
activities

70. Provide support for audit activities (e.g., data X
collection, audit software installation, report
qeneration)
71 . Develop plans to remediate audit findings that X
do not comply with the established Customer
oolicies and reauirements related to security

72. Review and approve audit findings and X
remediation olans

73. Implement audit findinas remediation plans X

74. Perform security assessments to identify control X
or security gaps and provide trending problem
reports to Customer, and provide remediation
plans

75. Approve remediation plans X

Page 20 ends

Schedule. 3A- Cross -Functional Services SOW
High-level Security Functions
No. Function/Responsibility Service Customer Provider

76. Conduct security planning and review sessions X
to review results of security assessments and
remediation olans

77. Implement Customer-approved security X
assessment remediation olan
Threat and Vulnerability Management

78. Provide integrated monitoring of threats and X
vulnerabilities for all Configuration Items (Cls)
required for the provision of the in-scope
Services

79. Provide automated alerts to the appropriate X
service delivery teams of pre-defined events,
prior to actual oerformance impact

80. Provide automated creation of Incident records in X the Incident Management tool based on predefined thresholds beinq reached or breached

81. Provide automated recovery, repair, and/or X
remediation of threats and vulnerabilities based
on alerts and ore-defined rules

82. Provide automated identification and suggestion X
of pre-defined recovery, repair, and/or
remediation activities to guide operator activities
in the event that ooerator intervention is required

83. Provide ability to support Customer-directed X
monitoring activities in addition to the predefined
recovery, reoair or remediation activities

84. Provide monitoring and reporting of performance X
trends to support trend analysis

Page 21 of 45 ends

Schedule 3A- Cross -Functional Services SOW

IT LIFE CYCLE (ITLC) & OPERATIONS SERVICES
"IT Life Cycle and Operations Services" means those functions described in this section and will apply to all Service Area environments (e.g., applications, software, network, hardware, services). Service Provider will manage all Service Tower IT life cycle activities in accordance with the following common life cycle and operational services.

Planning and Analysis Services
No. Function/Responsibility Service Customer Provider
Define Customer requirements at the enterprise and X

1. the operating unit level for all Service Towers (e.g., business, technology strategy, functional, Availability, capacity, performance, backup and IT business
continuitv)
Perform Planning and Analysis Services based on X

2. Customer requirements (e.g., functional, Availability, capacity, performance, business continuity and
disaster recovery)
Provide analysis of alternatives and recommendations, X

3. including projects and strategic initiatives, to meet Customer functional and technical objectives and
requirements for Customer's review and approval
Review and approve analysis of alternatives and X

4. recommendations to meet Customer functional and
technical objectives and requirements

5. Execute and provide leadership to deliver on X
Customer approved Projects and strateaic initiatives

6. Provide information and data as available for Planning X and Analysis Services (e.g., business planning reports, enterprise architecture)

7. Monitor technical trends, meet with Customer semi- X annually and provide semi-annual reports on
innovative products and services with potential use for Customer as they align with Customer's business and
technoloav strateav

8. Perform assessments for the implementation of new X
applications and technologies that best meet
Customer requirements and cost objectives, as
reauested by Customer or as otherwise reauired

9. Participate in technical and business planning X
sessions to establish standards, architecture and
project initiatives, as requested by Customer or as
otherwise required

10. Manage, maintain and update technology standards X
for the Customer IT environment (e.g., End-User
devices, computinq devices, network devices)

11. Approve technology standards for the Customer IT X
environment (e.g., End-User devices, computing
devices, network devices)

12. Conduct regular planning and conduct regular X
planning meetings with Customer for technology
refreshes and upgrades, as requested by Customer or
as otherwise required

Page 22 of 45 ends

Schedule 3A- Cross - Functional Services SOW
No. Function/Responsibility Service Customer Provider

13. Participate in regular planning and planning meetings X with Service Provider for technology refreshes and
unarades

14. Perform technical reviews, semi-annually or as X
otherwise required, and provide recommendations for
operational improvements that increase scalability,
reliability, Availability, security, efficiency and
effectiveness or reduce costs

15. Participate in ongoing initial project and strategic X initiative-specific planning activities and provide
proposals in accordance with the IT life cycle services and processes described in this Schedule

16. Provide analyses of business impacts related to X
Service Provider's IT planning and analysis roles and
responsibilities described herein based on Service
Provider's industry knowledge and capabilities and
other business knowledge as applicable (e.g.,
business process improvements resulting from IT
improvement, customer satisfaction improvements,
revenue qeneration, business cost savinqs)

17. Provide input to annual budget for Services to X
Customer

18. Support Customer's budgeting and planning processes X and other requests from Customer Requirements Definition Services
No. Function/Responsibility Service Customer Provider
Provide appropriate technical support staff (e.g., X

1. domain functional experts, solution architects and
engineers) to participate in functional and technical
reauirements develooment
Facilitate, participate in and conduct requirements X

2. gathering activities (e.g., functional and technical) with Customer stakeholders as required to determine I
Service Tower requirements

3. Participate in Service Provider-led requirements X
aathering activities

4. Review and approve requirements with key X
stakeholders

5. Document requirements necessary to deliver the X
Services in accordance with Customer defined formats

6. Ensure requirements meet Customer policies related X to security

7. Document cross-Service Tower and Third Party X
Provider inteqration reauirements

8. Define testing requirements and criteria (e.g., unit X testing, system testing, performance testing,
regression testing, security testing and user
acceptance testinal based on Customer policies and

Page 23 of 45 ends

Schedule 3A - Cross - Functional Services SOW
No. Function/Responsibility Service Customer Provider
procedures for specific events (e.g., production
changes, small enhancements, enhancements,
projects) for Customer's review and approval

9. Annrove testing requirements X

10. Document requirements and testing criteria for X
Customer's review and aooroval

11. Approve testinq criteria X

12. Work with Customer or Third Party Providers for end- X to-end test plan development (e.g., provide testing
reauirements, schedulina)

13. Provide Service Tower and project hours as X
applicable, following requirements gathering activities as required
Design Specifications
No. Function/Responsibility Service Customer Provider

1. Provide a design document standard for which all X
desian oackaqes will be delivered
Document and deliver design specifications, including X

2. cross-Service Tower integration specifications, for
Customer's review and approval

3. Approve design specifications X
Provide Service Tower and project hours as X

4. applicable, following design gathering activities as reauired
Integration and Testing
No. Function/Responsibility Service Customer Provider
Develop functional and/or technical system test plans X

1. and criteria for Changes to Service Tower components le.a., unit, system, inteQration, securitv, rearession) Prepare test plans for proposed Changes to Service X

2. Tower components based on Customer quality
assurance and testing polices and processes for
Customer's review and approval

3. Aoorove test olan X
Assess and communicate to Customer the overall X

4. impact and potential risk to Service Tower components prior to implementinq Chanqes
Evaluate all new and upgraded Service Tower X

5. components, configurations or services for compliance with Customer policies and requirements related to
securitv

6. Implement and suooort test environments as required X

7. Provide test environment reauirements X

8. Approve test environment requirements X

9. Conduct testinq of Chanqes to Service Tower X

Page 24 of 45 ends

Schedule 3A - Cross - Functional Services SOW
No. Function/Responsibility Service Customer Provider
components in non-production environments unless
otherwise annroved bv Customer
Test new releases of supported hardware and X
software in accordance with test plans to ensure

10. required performance and functionality is maintained and in conformance with Customer policies and
reauirements
Plan and proactively communicate test plans to X
11 . Customer in order to minimize Customer/departmental involvement in testing and minimize impact to
Customer's business operations
Provide Customer with test results for Changes to X

12. Service Tower components and configurations for
Customer's review and annroval

13. Approve test results X

14. Document all errors discovered in testing and propose X a remediation plan

15. Approve remediation Plan X

16. Implement known error remediation plan as agreed X
upon

17. Conduct retesting as required to fulfill requirements X and achieve Customer approval
Implementation and Migration Services
No. Function/Responsibility Service Customer Provider
Coordinate and review all implementation and X
migration plans and schedules with Customer in

1. advance, to obtain Customer's review and approval, in accordance with change and release management
procedures

2. Approve implementation and migration plans and X
schedules
Perform Service Tower component upgrades as a X

3. result of new and enhanced applications, architectures and upgrade Plans and reauirements
Perform modifications and performance enhancement X

4. adjustments to Service Tower components as a result
of implementinq Chanaes
Coordinate implementation and migration activities, X

5. including Change communication, with Customer and
Third Parties
Coordinate and support data migration and conversion X

6. by electronic or manual methods as a result of
implementation or miaration (e.g., databases)
Perform appropriate tests as part of implementation X

7. and migration activities (e.g., tests on database
IMACs)

8. Determine user acceptance testing ("UAT") and X
Service Provider testina support requirements

Page 25 ends

Schedule 3A - Cross - Functional Services SOW
No. Function/Responsibility Service Customer Provider

9. Conduct UAT X

10. Support UAT as required or requested bv Customer X
Training and Knowledge Transfer Services
No. Function/Responsibility Service Customer Provider
Develop, for Customer's review and approval, and X
deliver the Customer-approved training program to

1. instruct Customer personnel on the provision of the
Services and the Service Provider-managed Customer
environment (e.g., "rules of engagement", requesting
services)

2. Approve traininQ proQram X
Provide Customer with training related to the current X

3. systems and tools, as well as implementation of new
products and Services as required
Develop and implement a Customer-approved training X
program for each Service Tower to ensure that Service

4. Provider Personnel understand key components of the
Customer business and tec_hnical environment,
Customer culture, and are certified to support specific enterorise and business annlications
Cause Service Provider personnel to participate in X

5. Customer-provided training on Customer's business
~nd technical environment (including Customer culture
trainina\
Conduct new Service (e.g., application system, X

6. technology, third party service) on boarding to prepare for support of new Service
Develop and update technical training materials, X

7. training plan and documentation and provide training to address Customer's evolving IT environment (e.g.,
new systems or functionality)

8. Provide and maintain training materials in a format that X is acceptable to Customer (e.Q., electronic, hard copy) Deposit and maintain training and systems X

9. documentation in Customer designated knowledge
database, training delivery tools or svstems

10. Support End-User training provided by Customer (e.g., X bv providing training materials, trainina scripts)

11. Review and approve all training delivery tools or X svstems and script materials
Prepare for and lead semi-annual meeting to educate X

12. Customer departments on service offerings available under this Agreement, including review of IT service
cataloa

Page 26 of 45 ends

Schedule 3A- Cross - Functional Services SOW
Documentation Services
No. Function/Responsibility Service Customer Provider

1. Recommend cross-Service Tower and Service Tower- X
specific knowledqe management policies
Review and approve Customer project documentation X

2. formats, content standards and document control
orocedures where required
Recommend documentation formats and content in X
3: accordance with industry standards (e.g., CMMI-SW
Software project best practices, IEEE documentation
standards) for Customer's review and approval

4. Approve documentation format X
Define and provide the document control procedures, X
including distribution, document numbering, version

5. control, and naming standards to be used to perform
the Services and the Customer document currency
requirements
Develop, deliver and maintain documentation formats X

6. and content in accordance with Customer-approved
formats, content, and document control procedures
Document Service Tower component specifications X

7. and configurations, including ongoing updates during the course of normal chanqe activities

8. Approve Service Tower documentation formats and X
content
Develop, document and maintain operating X

9. procedures documentation (e.g., run books, boot,
failover, batch processing, backup, systems operations
and scheduling) through normal change or update
activities for Customer's review and approval

10. Approve operatinq procedures documentation X
Provide Customer electronic access (e.g., portal) to X
11 . any Service Provider or Third Party provider
documentation
Maintain documentation and rnetadata in accordance X

12. with Customer policies and requirements related to
knowledae manaqement
Document Service Towers' as-built configurations in X

13. accordance with the configuration management
procedures

14. Review and approve Service Tower configuration as- X built documents
Break/Fix and Maintenance Services
No. Function/Responsibility Service Customer Provider
Develop and implement maintenance schedules for X

1. Changes and preventive maintenance based on
Customer-approved maintenance windows and
blackout dates

2. Provide special dispatch requirements for Customer X Service Locations

Page 27 of 45 ends

Schedule 3A- Cross - Functional Services SOW
No. Function/Responsibility Service Customer Provider

3. Perform maintenance and break/fix support X
Perform diagnostics and maintenance on Service X

4. Tower components (e.g., hardware, software,
oerioherals)

5. Test patches and releases received from third party X vendors

6. Approve service packs, firmware, and Software X
maintenance releases
Perform product patch, "bug fix," service pack X
installation or upgrades to the current installed version

7. in accordance with Customer policies and change and
release management procedures, or oversee and
coordinate Third Party provider installations as
applicable

8. Approve product patch, "bug fix," service pack X
installation or upgrades

9. Coordinate application of patches and maintenance X releases when applied by third party provider Perform enhancement version release installations, or X

10. oversee and coordinate Third Party provider executed upqrades as aoolicable

11. Aporove enhancement version release installations X

12. Perform major release upqrades as a oroiect X

13. Aoorove major release upqrades X
Coordinate with third party vendors to identify any

14. impacted interfaces due to vendor-initiated patches X and maintenance releases and escalate any impacts with the COTS vendor
Work with Third Party Software providers to resolve

15. issues related to third party provider patches and X releases
Perform maintenance-related Software distribution X
and version control (e.g., Software updates,

16. emergency and standard patches) across applicable
Service Provider-supported technology and Service
Towers

17. Approve maintenance-related Software distribution X and version control
Maintain Software release matrices across all X

18. supported IT environments (e.g., development, test, and production environments)
Coordinate with Customer and Third Parties (e.g., X

19. Software service providers and developers) to
develop the software release r:natrix for Customer's
review and approval
Conduct appropriate interactions with Customer users

20. for patching and release activities (e.g., End-User X communication, coordination and scheduling) to
minimize Customer disruption and involvement

21. Aoorove software release matrix X

22. Review Third Party Software upgrades to ensure Nor X N-1 level of currency

Page 28 of 45 ends

Schedule 3A - Cross -Functional Services SOW
No. Function/Responsibility Service Customer Provider

23. Aoprove Third Party Software uparades X
Recommend Software release schedules based on X

24. the Customer Software environment and business
needs

25. Approve Software release schedules X

26. Conduct maintenance and monitoring during warranty X and off-warranty periods
Manage Software, Services to meet Service Levels, X
27, minimize downtime and minimize Customer resource
requirements, and provide related reporting in
accordance with Customer requirements

28. Provide routine and ad hoc break/fix reporting in X accordance with Customer requirements
Technology Refreshment and Replenishment Services
No. Function/Responsibility Service Customer Provider
Update and maintain the Technology Refresh Plan for X

1. each applicable Service Tower in accordance with
Customer policies related to technoloav refresh

2. Perform the necessary services and tasks required to X comolv with the Technoloav Refresh Plans

3. Provide management reports on the progress of the X
TechnoloQY Refresh Plans
Implement the Technology Refresh Plan and provide X

4. status reports regarding implementation status as
reauired
Provide assets for technology refreshment and X

5. replenishment, unless otherwise specified by
Customer

6. Review and approve technology refreshment and X
rePlenishment implementation olans
Periodically review the approved technology X

7.'
refreshment and replenishment implementation plans
to ensure they properly support ongoing Customer
business requirements

Page 29 of 45 ends

Schedule 3A- Cross - Functional Services SOW
Service Delivery
Capacity Management Services
Function/Responsibility Service Customer Provider

1. Create and manage a capacity management plan,
including documentation for thresholds, and process
for identifying, documenting, monitoring, evaluating X and making change recommendations to the infrastructure environment to enable capacity
reouirements are met

2. Manage IT Services environment to capacity
thresholds established in the Capacity Plan and X
associated Service Levels

3. Provide monitoring and trend analysis of the capacity of technology, systems or information technology X
services to identify areas for improvement

4. Provide remedial activities to resolve capacity issues identified by proactive analysis of the IT environment X with resoect to usaqe patterns

5. Provide trend and strategy analysis to review service X capacitv aQainst planned future requirements

6. Estimate the behavior of technology, systems or
information technology services under a given volume X and variety of work utilizing methods such as analytical simulation, baseline modelinq and trend analvsis

7. Estimate the resource requirements to support a
proposed application change or new application to so X
that it meets applicable Service Levels

8. Advise and recommend the strategic direction and
development of information technology infrastructure
environment for the future, encompassing assessment X
and appraisal of new technologies and services in
accordance with business requirements
Availability Management Services
Function/Responsibility Service Customer Provider

1. • Understand Client's Availability requirements in order. to plan, measure, monitor and continuously improve
the Availability of the technology, systems or
information technology services, in accordance with X
relevant Service Levels and identify and agree the
elements of service for which Service Provider is
resoonsible

2. Create and manage an availability management plan
to establish an integrated process for identifying,
documenting, monitoring, evaluating and controlling X
Client's technology, systems or information technology
services

3. Own the end-to-end process across all environments X and coordinate and control the participation in the

Page 30 of 45 ends

Schedule 3A- Cross - Functional Services SOW
process for all service providers, including the
provision, support and maintenance of the Availability
plan for components of this environment

4. Provide input to the Availability plan in relation to Cls X in this environment

5. Analyze and determine the IT environment required to achieve efficient use of resources to deliver service X reauirements

6. Monitor and measure Service Levels and key
performance indicators for Availability in accordance X with the availability management plan and report both status and exceptions

7. Provide monitoring and trend analysis of the
availability, reliability and maintainability of technology, X systems or information technology services to identify areas for imProvement

8. Mark recommendations to improve Availability X

9. Review service Availability in accordance with planned X future reauirements

10. Provide strategy reviews using trend analysis to review service Availability against planned future X
requirements

11. Prioritize and plan for new and enhanced Services in X accordance with forecastina activities

12. Identify threats and vulnerabilities to the ongoing Availability of the Service in accordance with X
diaanosed trends and future problems
Service Level Management Services
Function/Responsibility Service Customer Provider

1. Provide Client service reporting through a web-based X Customer portal

2. Develop and maintain Service Level agreements,
operating level agreements and underpinning X contracts that enable the delivery of the service requirements

3. Obtain data from the various delivery groups who
manage the Services for compilation and analysis X
aaainst the Service Levels

4. Conduct periodic scheduled meetings to discuss past X service performance and future requirements

5. Conduct periodic reporting on all service delivery
components for Services in accordance with Service X
Levels

6. Manage Service Level activities in accordance with the agreed policies and procedures required to support X timely, measurable and repeatable analysis of the service beinq delivered bv Service Provider to Client

7. Work in conjunction with problem and availability
management processes to identify underlying X
difficulties which adversely impact upon service quality

Page 31 of 45 ends

Schedule 3A- Cross - Functional Services SOW

8. Develop appropriate measurements and review points X with respect to service improvement initiatives

9. Engage with Client representatives to understand and analyze the perception of the service offered and X diagnose whether these are reflected in the results of Service Levels
Acquisition and Management Services
No. Function/Responsibility Service Customer Provider
Develop, maintain and periodically provide Service X

1. Provider with roadmap of upcoming Customer
initiatives and projects, including Annual Execution
Plan

2. Develop and issue requests for proposals (RFPs) as X reauired and aporoved bv Customer

3. Manage and lead overall procurement process for X
hardware, software and services

4. Evaluate proposals against clearly defined objective X criteria

5. Provide Customer with detailed pricing proposals for X proposed Service Provider acauisitions, as reauired

6. Review and approve oricina proposals X

7. Negotiate contracts for hardware, Software and X
services

8. Review and approve contracts for hardware, Software X and services

9. Manaae and track Service Provider purchase orders X
Receive and store ordered equipment pending X

10. scheduling of installation at Customer Service
Locations
Expedite resolution of and resolve any and all issues X

11. which may arise related to shipping, damaged goods
or order errors
Arrange for proper processing of product returns X

12. and/or replacement orders by arranging for pickup/delivery and correction or revision of purchasing paoerwork to reflect action taken

13. Coordinate delivery and installation of new products X and services, as reauired

14. Ensure that new hardware complies with established X Customer IT standards and architectures
Review and approve selection of hardware to be X

15. installed in in scope facilities and Software to be installed on in scope hardware

16. Enforce technology standards across the supported X environment (e.g., End-User devices, computing
devices, network devices)

17. Maintain copies of the individual receipts and post to X portal tool used bv Service Provider
Terminate, dispose of according to Customer disposal X

18. guidelines and relocate assets as needed/specified
and provide auarterlv disoosition reports

19. Determine appropriate solution parameters and solicit X

Page 32 of 45 ends

Schedule 3A- Cross - Functional Services SOW
No. Function/Responsibility Service Customer Provider
solution and pricing quotations for off premise
solutions (e.Q., cloud, SaaS)

20. Evaluate solution options and make recommendations X to Client for off oremise solutions (e.g., cloud, SaaS)

21. Approve solution options for off premise solutions X (e.g., cloud, SaaS)
Develop and negotiate SOWs and contracting X

22. mechanisms for Customer approved Third Party off
oremises solutions (e.Q., cloud, SaaS)

23. Review and approve Third Party contracts for third X partv off premises solutions (e.g., cloud, SaaS)
Coordinate implementation, integration and X

24. orchestration of Third Party services with Service
Provider (e.g. Availability monitoring, performance
monitoring)
Perform periodic assessments, and provide X

25. assessment results, of procurement procedures for
conformance with Customer policies

26. Assist in periodic assessment of Service Provider X procurement orocedures
Asset Management
No. Function/Responsibility Service Customer Provider
Deploy and manage an asset management system X

1. that meets Customer requirements and adheres to
Customer policies
Manage the life cycle of all assets from requisition, X

2. ordering, inventory, installation, preventive
maintenance to disoosal
Develop asset type list that would be included in the X asset management system (e.g., infrastructure

3. devices: servers, routers, storage devices, switches, End-User devices: desktops, laptops, printers, mobile
devices, handsets, conference room equipment)

4. Review asset type list and maintain asset types in the X asset manaaement svstem
Provide Customer with inquiry and reporting access X
into the asset management system for all assets,

5. including data access via a real-time access reporting portal in exportable and analyzable format and ad hoc
and recurrinq (e.Q., monthlv) reports
Input, maintain, update, track and report all in-scope X

6. assets throughout the asset life cycle (i.e., acquisition to retirement) via an automated self-discovery tool and manual processes where required
Maintain the accuracy of the data of in-scope assets in X

7. the asset management system, in accordance with
applicable Service Levels

8. Provide extracts from asset management svstem for X

Page 33 of 45 ends

Schedule 3A - Cross - Functional Services SOW
No. Function/Responsibility Service Customer Provider
Customer to implement into its various systems (e.g.,
PeopleSoft)

9. Provide a list of asset data elements to be maintained X Establish, update, maintain and utilize the asset X
management information. At a minimum, the following
asset information shall be tracked:
• Manufacturer
• Model
• Serial number
• Asset identification number
• Asset location
• Ownership organization information (Service
Provider/Customer/Third Parties - lease

10. /purchase)
• Asset cost information (e.g., current residual
value, purchase price, accumulated
depreciation)
• Maintenance information and history including
the age of the asset
• Warranty information
• Other billing information (e.g., lease information,
Customer specific information)
• Transaction edit history (e.g., locations, billing
and user)
• Software version information (as aoolicable)

11. Administer and manage warranty periods for all X
applicable Service Tower-related assets

12. Administer maintenance contracts for End-User assets X within the scone of the Services
Update in-scope asset records during the course of all X

13. change activities (e.g., !MACO activities, break/fix activities, enterprise-reorganization and change and
release manaqement activities)
Perform ongoing asset inventories including at time of X

14. refresh to validate that data in the asset management system is accurate and current and that Customer has
the data it requires
Provide, and upon Customer approval, implement X

15. remediation plans for asset management system and
process deficiencies

16. Approve remediation plans for asset management X
system and orocess deficiencies

17. Review and aoorove phvsical asset inventory reports ·x

Page 34 ends
← All documents from this meeting