https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/work_design/index.html Recent content in 4.3 Task design on JP1 Cloud Service/Operations Integration User's Guide Hugo -- gohugo.io en https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/work_design/catalog_design/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/work_design/catalog_design/index.html Service catalog design involves the creation of a service catalog. (Table) Service catalog design items and overview Item Definition method Key design points Catalog YAML file After identifying necessary catalog items, categorize them based on the patterns such as requests and data records. Then, organize the catalog items based on whether they are displayed or not and the order in which they are displayed. A service catalog consists of several catalog items. https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/work_design/workflow_design/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/work_design/workflow_design/index.html When designing workflows, create a workflow for each task, and use a YAML file to define the content and order for each activity, such as application, approval, or task execution, as well as the roles that can execute the activities. There are various types of activities, including review and approval of applications and automation tasks using Playbook. Also, YAML files can be used to define labels for each step of any workflow. https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/work_design/notice_design/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/work_design/notice_design/index.html Ops I provides two notification function methods: notifications triggered when workflows, schedules, or work items are created, modified, or deleted (hereinafter referred to as “event-based notifications”), and notifications sent at times specified in the workflow definition (hereinafter referred to as “workflow-based notifications”). The design of notifications involves two types of YAML definitions: Notification and Notifier. (Table) Notification design items and outline Item Definition method Key design points ・Notification ・Notifier YAML file Assign an agent to be notified for each workflow step and configure notifications to be sent to the requester upon completion of the request. https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/work_design/document_storage/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/work_design/document_storage/index.html ISO and other standards require work records and trails of various operations. When designing document storage methods, you need to consider how evidence should be stored. In Ops I, create containers for storing evidence based on rules using Attachment definitions. Then, it is possible to distribute repositories for each customer or service using Distribution rules. For details on containers, see “Container”. [Attachment] For Attachment, you define naming rules for containers, folders, etc. https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/work_design/user_acl/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/work_design/user_acl/index.html In designing users and ACLs (Access Control Lists), it is necessary to consider what permissions are needed in the creation of users, groups, and roles. A user’s operating permissions are determined by the role’s access rights, which are assigned directly or indirectly through groups or other roles. (Table) User and ACL design items and outline Item Definition method Key design points ・User ・Group ・Role GUI Create and assign users, groups, and roles. https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/work_design/skill_manage/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/work_design/skill_manage/index.html Ops I has a skill management function that allows you to assign the right users to tasks. The skill management function can be used to define the skills required for operations in YAML files and assign the defined skills to users in the Ops I GUI. In addition, skill sets (combinations of skills) can be defined in YAML files for each activity in the workflow, allowing appropriate users to be assigned to each activity. https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/work_design/design_auto/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/work_design/design_auto/index.html Ops I helps automate operational tasks by using Ansible Playbooks. In addition, when access to operational targets, such as existing systems, is required, the secret management function using Vault allows IDs and passwords to be managed securely. Playbooks are managed in GitLab. For information on secrets, see “Secret management”. (Table) Automation design items and outline Item Definition method Key design points Playbook ・YAML file ・GUI For a workflow of as-needed tasks, classify those tasks that are to be automated and those that are to be manually performed. https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/work_design/ticket_manage/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/work_design/ticket_manage/index.html Ops I enables efficient operation and management of IT services by using tickets to manage responses to requests and incidents that occur during operations. Ticket management is primarily performed from the Ticket tab of the Task or Request application, where tickets are created, reviewed, and updated. It also allows for associations between tickets. By defining YAML files, executing the API, and connecting to the ITSM application OTOBO, you can also customize the ticket window and set up email notifications and receipts according to ticket operations. https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/work_design/schedule_manage/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/work_design/schedule_manage/index.html The design of a schedule involves creating a schedule for each (non-regular/regular) routine and as-needed task, assigning agents, and reviewing and updating the schedule. (Table) Design items and outline of schedule management Item Definition method Key design points Task settings － For each of the tasks identified, examine the groups and agents to assign, repetition patterns, and whether or not it is associated with a workflow. How to add a schedule － Depending on the type of the task (for example, based on whether it is a routine or as-needed task, or whether it is a non-IT operational task), consider whether to add the schedule as a task-based or user-based schedule. https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/work_design/site_manage/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/work_design/site_manage/index.html For site applications, the OSS WordPress can be used to create and provide service portals for each customer or user department. WordPress makes it possible to build websites in an intuitive way. In addition, plugins provide useful functions for site management. For information on the WordPress manuals, versions and editions, see “OSS version/edition and reference manuals” in the Appendix. Hereafter, “service portal” will be referred to as “site” in site management. https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/work_design/knowledge_manage/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/work_design/knowledge_manage/index.html The knowledge function enables you to accumulate insights and expertise gained through the processes of failure response and inquiry handling. Those insights and expertise can be accumulated as knowledge articles and used to resolve issues that might arise. You can categorize knowledge articles and rate those articles in terms of usefulness, so you will be able to use those articles efficiently. You can also implement access control on knowledge articles to grant access rights to specific users. https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/work_design/datamodel_design/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/work_design/datamodel_design/index.html Data model design involves the definition of data models. (Table) Data model design items and outline Item Definition method Key design points Datamodel YAML file Evaluate the type and structure of the datamodel based on your purposes. Also, organize the data records to be managed and design the datamodel, including tables and columns. Datamodels allow you to manage multiple tables collectively within a single datamodel framework. Tables defined in the datamodel can be referenced by user-created applications and by each workflow step by linking them to the UI (UI version 1.