<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>4.2 Organizing tasks on JP1 Cloud Service/Operations Integration User&#39;s Guide</title>
    <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/required/index.html</link>
    <description>Recent content in 4.2 Organizing tasks on JP1 Cloud Service/Operations Integration User&#39;s Guide</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language><atom:link href="https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/required/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>4.2.1 Identifying routine/as-needed tasks</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/required/required_work/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/required/required_work/index.html</guid>
      <description>Identify and organize IT operations and other necessary tasks to be performed in Ops I.
For routine tasks, identify whether they will be performed on a regular or irregular basis and whether they are associated with workflows. For as-needed tasks, identify necessary tasks as a service catalog, and then identify patterns of agents and workflows for each task.
The following shows examples of routine and as-needed tasks.
(Table) Examples of routine/as-needed tasks</description>
    </item>
    <item>
      <title>4.2.2 User management</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/required/required_user/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/required/required_user/index.html</guid>
      <description>Organize tasks that each user can perform.
The following is an example of tasks that each user can perform.
(Table) Example of tasks that each user can perform
Worker Task that can be performed Requester View the service catalog window and request the operations agent to perform a task. Operations agent Review and perform the request from the requester and check the results.
If the request is inadequate, send back the request to the requester.</description>
    </item>
    <item>
      <title>4.2.3 Skills required for operation</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/required/required_skill/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/required/required_skill/index.html</guid>
      <description>The skill management function allows you to assign skills or tasks to agents. To do this, it is necessary to organize skills possessed by each agent, as well as skills and skillsets (combinations of skills) required to perform tasks. Depending on the nature of the task, consider dividing a skill into several levels. Once organized, define the skills and skillsets in YAML files.
For information on the operational design for skill management, see &amp;ldquo;Skill management&amp;rdquo;.</description>
    </item>
    <item>
      <title>4.2.4 Organizing handled documents</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/required/required_document/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/required/required_document/index.html</guid>
      <description>Documents (procedure manuals and attachments used in operations) can be managed with the document function. At first, you need to organize how to manage documents. for details on the document function, see &amp;ldquo;Documents&amp;rdquo;.</description>
    </item>
  </channel>
</rss>