<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>1. Outline on JP1 Cloud Service/Operations Integration User&#39;s Guide</title>
    <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/outline/index.html</link>
    <description>Recent content in 1. Outline 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/outline/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>1.1 Ops I outline</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/outline/opsi_outline/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/outline/opsi_outline/index.html</guid>
      <description>Ops I is a SaaS operation integration platform that allows for the construction of a mechanism for standardization and automation of tasks for service requests utilizing various public cloud infrastructures. Ops I improves the efficiency of multi-cloud operations through unified operation windows for service catalogs, request forms, and so forth, management of documents such as operational histories and checklists used for operations, and facilitation of automation.
(Figure) Ops I outline</description>
    </item>
    <item>
      <title>1.2 Ops I features</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/outline/opsi_forte/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/outline/opsi_forte/index.html</guid>
      <description>Feature 1: Unified operation windows that reduce learning costs for operational tasks
In many cases, operation infrastructures are built by combining different tools such as management and automation tools for service catalogs, workflows, and documents. This is not efficient because of the different operation windows and the number of transitions and steps between the operation windows. Using Ops I, operation windows can be standardized and learning costs for operational tasks can be reduced.</description>
    </item>
    <item>
      <title>1.3 Outline of usage</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/outline/method/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/outline/method/index.html</guid>
      <description>Customer users can use Ops I to request task services.
Operation managers and operation agents can use Ops I to check input parameters, review execution logs, register checklists of tasks, and approve tasks in response to requests from customer users.
The following environments are required to use Ops I.
Network environment with HTTPS connection Web browser to connect to the Ops I portal Relay server (for access from Ops I to an external private network) Smart devices and MFA-enabled applications (when using multi-factor authentication) (Figure) Image of use of Ops I</description>
    </item>
    <item>
      <title>1.4 Use precautions and temporary restrictions</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/outline/note_restriction/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/outline/note_restriction/index.html</guid>
      <description>This section describes the use precautions and temporary restrictions.
Section structure
1.4.1 Use precautions
1.4.2 Temporary restrictions</description>
    </item>
  </channel>
</rss>