Common use of Implement Clause in Contracts

Implement. Conduct one (1) workshop to review Change Management OOB processes, application functionality and introduce configuration areas. • Conduct one (1) workshop to gather and document functional and technical specifications for Change Management • Review Change Management requirements/configuration parameters and obtain Fort Bend County approval signoff prior to ServiceNow configuration/development • Configure the Change form to ensure appropriate information is being captured and accessible, including up to five (5) new fields to capture client-specific information • Configure up to five (5) automated email notifications for Change Assignment, Approval, Commenting, and Closure using fields captured on a Change Request • Review / leverage the three (3) OOB Change Management Processes (Types): Standard, Normal, Emergency • Configure one (1) Standard Change Process with up to five (5) Standard Change Templates • Configure one (1) Normal Change Process with the support of Technical Approval, CAB (Change Advisory Board) Approval, Implementation, Post-Implementation, and Review steps • Configure one (1) Emergency Change Process with the support of CAB (eCAB) Approval, Implementation, Post-Implementation, and Review steps • Configure up to five (5) Change Approvals to be managed through groups • Configure up to five (5) Maintenance Windows for Change Management • Configure up to three (3) Risk Conditions for Change Management • Review/leverage OOTB Change Management Dashboard • Review/leverage OOTB Change Management reports • Configure up to six (6) new Change Management reports • Fort Bend County does not require the use of CAB Workbench, additional Change Request Types, or Risk Assessments • Knowledge Management (KM) orchestrates the knowledge lifecycle, helps capture knowledge, increases knowledge sharing, and presents relevant information to support the various ITIL processes.

Implement. Conduct one (1) workshop to review Change Management ServiceNow KM OOB processes, application functionality and introduce configuration areas. • Conduct one (1) workshop to gather and document functional and technical specifications for Change Knowledge Management • Review Change Management requirements/KM requirements and configuration parameters and obtain Fort Bend County approval signoff prior to ServiceNow configuration/development • Configure up to two (2) Knowledge Bases will be configured to support Service Desk and Self-Service Knowledge Functionality • Configure up to ten (10) Knowledge Categories per Knowledge Base • Review and leverage the Change form to ensure appropriate information is being captured Knowledge baseline publishing and accessibleretirement workflows • Review/leverage baseline functionality for user feedback on Knowledge Articles, including up commenting, '5- star' rating, and the ability to five (5) new fields mark an article as helpful • Configure the ability to capture client-specific information draft Knowledge Articles upon Closure of an Incident • Configure/integrate Knowledge Portal functionality into the Employee Center to as to provide a fluid user experience • Configure up to five (5) automated email notifications for Change Assignment, Approval, Commenting, and Closure using fields captured on a Change Request KM • Review / Review/leverage the OOTB KM Dashboard(s) • Review/leverage OOTB KM reports • Configure up to three (3) OOB Change new KM reports • InSource will work with the Knowledge Managers to migrate up to five (5) Knowledge Articles; this will transfer knowledge to the client’s team so they can provide ongoing support for KM • Fort Bend County does not require the migration of existing Knowledge Articles from existing Knowledge solutions to ServiceNow • The Service Catalog establishes standardized catalogs of goods and services provided to the organization’s supported business units and employees. It also enables online browsing of requests for goods and services. Implement • Conduct one (1) one workshop to review Service Catalog/Request Management Processes processes, application functionality and introduce configuration areas • Conduct one (Types): Standard, Normal, Emergency 1) one workshop to gather functional and technical specifications for the configuration of the Service Catalog/Request Management applications • Review Service Catalog/Request Management requirements / configuration parameters and obtain Fort Bend County approval signoff prior to ServiceNow configuration / development • Configure one (1) Standard Change Process with Service Catalog to support Self-Service browsing, submission, and tracking of Requests (through ServiceNow standard interface and Employee Center) • Utilize the baseline Request Management forms (Request, Requested Item and Catalog Task) to display appropriate information • Configure up to five ten (510) Standard Change Templates Service Catalog Items. Each Service Catalog Item may include: • Configure one Up to ten (110) Normal Change Process with request form variables to collect information from the support user submitting the request (requestor) • Configuration of Technical Approval, CAB (Change Advisory Board) Approval, Implementation, Post-Implementation, and Review steps • Configure one (1) Emergency Change Process with User Criteria to only expose catalog items to those who can request the support of CAB (eCAB) Approval, Implementation, Post-Implementation, and Review steps service • Configure up to five (5) Change Approvals unique fulfilment flows each with up to ten (10) flow activities (approvals/catalog tasks/notifications) • Flows will be managed through groups created using Flow Designer • Configure up to five (5) Maintenance Windows automated email notifications for Change Request Creation, Approval, Assignment, Commenting, and Closure of a Request • Configure up to two (2) Order Guides (catalog item bundling into a single request) • Review/leverage OOTB Request Management Dashboard(s) and reports • Configure up to three (3) Risk Conditions for Change Management • Reviewnew Service Catalog/leverage OOTB Change Management Dashboard • Review/leverage OOTB Change Management Request reports • Configure up to six (6) new Change Management reports If Cart, Wish List, Quantity, Cost, Bundles, and/or Delivery Time functionality is desired, they will be implemented using baseline functionality • Fort Bend County does not require the use of CAB WorkbenchIntegrationHub or any integrations to 3rd party systems in the fulfillment of a Request/ requested Item • ServiceNow Employee Center portal is a standard multi-department, additional Change Request Types, or Risk Assessments • Knowledge Management (KM) orchestrates the knowledge lifecycle, helps capture knowledge, increases knowledge sharing, dynamic portal for service delivery and presents relevant information to support the various ITIL processesemployee engagement.