<<Contents>> <<Index>>

General Collaborative Information Server

Specifications
GS 36K01A10-01EN

n GENERAL
The Collaborative Information Server (CI Server) is an integrated operation and monitoring system that can connect
to any equipment and systems in the plant and integrate them.

Support Making Decision by a Fusion of Summarize the Information

and the Business System

Remote Operation Environment Integrated Operation and Monitoring

Environment for Entire Plant

AI

Connection to Various Devices and Systems in the Plant Support Optimization of Information Management of the Entire
Production Activity and the Securely Effectively Operation

Integrated Display for Operation Information of Multiple Plants

F01.ai

Figure Image of grasping and operating the entire production activity by utilizing CI Server

 Integrated Operation and Monitoring and Remote Operation

• Connects every device and system in a plant and grasp current accurate plant situation.
• Monitoring targets can be added, deleted, and modified even while operating the system.
• Since CI Server has dedicated interfaces for controllers widely used on the market and open interfaces that meet
standards, integrated management is possible not only for Yokogawa products but also for other companies'
products.
• Connects with any Cloud environment and IT systems. Supports RESTful API, an interface for calling web systems
via HTTPS to facilitate integration with Cloud applications and IT. (*1)
• Collects the information of devices such as device status and parameter values from Plant Resource Manager
(PRM) and utilizes it. (*2)
*1: Supported by R1.04 or later.
*2: Linkage between PRM and CI Server is supported by PRM R4.06 or later and CI Server R1.02 or later. For details of PRM
connection, refer to "Plant Resource Manager" (GS 30B05A10-01EN).

Yokogawa Electric Corporation GS 36K01A10-01EN

2-9-32, Nakacho, Musashino-shi, Tokyo, 180-8750 Japan ©Copyright Jan. 2021 (YK)
15th Edition Mar. 11, 2025 (YK)
<<Contents>> <<Index>> 2
 Optimize Management System of Information
• Integrate and display operation information of multiple plants and contribute optimization for information
management of entire production activity.
• Behavior at alarm occurrence and how the alarms are represented to users can be configured for each data.
• Creates reports on plant operation information and outputs it whenever requested.
• Saves the operation record as an audit trail.
• By adding an option library, data changes can be made in accordance with the pharmaceutical regulations (e.g.
main parameter change). Supports input of operator and authenticator information and the reason for change
when manipulating important parameters such as CPP (Critical Process Parameter), Alarm limit, Alarm ack. These
operation histories can be saved in the audit trail.

 Security
• Supports safely effectively operation by performing various security measures such as supporting secure
communication.
• The area of operation and monitoring can be set for each user using the system.

n SYSTEM CONFIGURATION
CI Server can flexibly configure according to the plant architecture and business style from standalone configuration,
in which single computer provides environment of data collection, operation, and monitoring, to integrated
configuration, in which multiple servers are hierarchically deployed to perform integrated monitoring of the entire plant.

 Functional Components
CI Server consists of functional components below. The system configuration is determined by allocating these
components on the server computers and client computers.

Functional component Description

Collects, stores, and calculates plant operation data, and links data with other CI Core and
CI Core
other systems.
CI Portal Provides the data collected and stored by CI Core and predefined screens to CI View.
CI View HMI for operation and monitoring, which uses a web browser.
This is a limited-function version of CI Core. It publishes data on OPC UA servers and
CI Gateway shares data with other CI Cores.
CI View cannot be connected directly to the CI gateway.

 Flexible System Configuration

CI Server provides best fit system architectures by setting functional components as required.
Followings are some examples:
• Standalone configuration
• Remote CI Portal/CI View configuration
• Enterprise configuration
• Gateway configuration
• Host-to-host connection configuration
• Yokogawa Cloud configuration (*1)

*1: Yokogawa Cloud is an industrial transformation and IoT platform that accelerates the development and deployment of
industrial cloud applications. It supports the ingestion, processing, and curation of data from various sources, provides
industry-specific algorithms and models, and integrates across applications to support insightful decision-making and
higher levels of automation.
https://www.yokogawa.com/solutions/solutions/digital-transformation/yokogawa-cloud/

All Rights Reserved. Copyright © 2021, Yokogawa Electric Corporation GS 36K01A10-01EN Feb. 12, 2025-00
<<Contents>> <<Index>> 3
Standalone Configuration
In this configuration, data collection, monitoring, operation, and engineering of CI Server are all inclusively run on a
single computer.
Ethernet

CI Core
CI Portal
CI View

Ethernet
PLC

F02.ai

Figure Example of Standalone Configuration

Remote CI Portal/Remote CI View Configuration

This configuration improves system scalability by separating CI Core responsible for data collection and application
execution, and CI Portal used for engineering and operation and monitoring. Multiple number of CI Portal can be
placed according to the number and the placement location of CI View in order to ensure performance for such as
large scale system.

CI View CI View

CI View (HTML5)

WAN

Firewall

CI Portal CI Portal
CI View CI View

Ethernet

CI Core

Ethernet

HIS/ENG PRM server

Field communications server

Vnet/IP

Ethernet
CENTUM etc. PLC

F03.ai

Figure Example of Remote CI Portal/Remote CI View Configuration

All Rights Reserved. Copyright © 2021, Yokogawa Electric Corporation GS 36K01A10-01EN Feb. 12, 2025-00
<<Contents>> <<Index>> 4
Enterprise Configuration
By deploying the functional components on multiple computers, large-scale integrated operation and monitoring
become possible, and only the information required for each business level can be collected.

CI View

WAN
Corporate level

Firewall
CI Portal Enterprise
CI View Engineering Core
Ethernet

HAC
CI Core CI Core
Router Router

CI Servers
under another
CI Portal business unit
Business unit level

CI View level
Ethernet
HAC
CI Core CI Core

WAN WAN

CI Portal CI Servers
CI View
under another
Ethernet area level
Area level

HAC
CI Core CI Core
WAN

Router

CI Portal
CI Server
Process level

CI View
of another
Ethernet process level
Dual-redundant
Platform CI Core CI Core
for Computer

Vnet/IP

Ethernet
CENTUM etc.
PLC

F04.ai

Figure Example of Enterprise Configuration

Enterprise engineering core for engineering use in enterprise configuration can be utilized for more efficiently
engineering. (*1) Enterprise engineering core engineerings all CI servers at once, loads engineering data, and is
located on network accessible each server.
*1: Enterprise configuration can be architected even if enterprise engineering core is not used.

In case of Enterprise configuration, the following component is used also in addition to “●Functional Components” as
described earlier.

Functional component Description

A dedicated engineering server which is used to build systems in an
Enterprise Engineering Core
enterprise configuration.

All Rights Reserved. Copyright © 2021, Yokogawa Electric Corporation GS 36K01A10-01EN Mar. 3, 2023-00
<<Contents>> <<Index>> 5
• Process level
Refers to the level of direct control of processes, where control systems for each process and CI Server for
integrated monitoring of them are deployed. This level includes local DCS/PLC systems and automated control/
monitoring equipment that interact directly with the process.
• Area level
Refers to the level of integrated monitoring of multiple processes. At this level, the total production in the area is
controlled and production KPIs are provided.
• Business unit level
Refers to the level of integrated monitoring of multiple areas and represents the entire business unit. Data for
optimizing production and asset data are accessed.
• Corporate level
Refers to the level that represents the entire business of the enterprise. At this level, all KPIs of all the business units
are collected and aggregated, and it is responsible for managing the performance of the entire enterprise in real
time.

Gateway Configuration
This configuration passes data to CI Core or in-house/third party systems that summarizes information via CI
Gateway.

CI Core
CI Portal in-house/third party system
CI View
Ethernet Ethernet

WAN WAN
CI Gateway CI Gateways CI Gateway CI Gateways
under another under another
plant plant
Vnet/IP Vnet/IP
Ethernet Ethernet
CENTUM etc. PLC CENTUM etc. PLC

F15.ai
F05.ai

Figure Example of Gateway Configuration (CI Core) Figure Example of Gateway Configuration
(in-house/third party system)

All Rights Reserved. Copyright © 2021, Yokogawa Electric Corporation GS 36K01A10-01EN Feb. 12, 2025-00
<<Contents>> <<Index>> 6
Host-to-host Connection Configuration
Real-time data can be exchanged between CI Core or CI Gateway running independently. This configuration is for a
system which CI Core in the central location communicates to remotely located CI Core.

CI View

Ethernet

CI Core
CI Portal
CI View

Host-to-host Host-to-host
Connection Communication Connection
Device

CI View
Communication Communication
Device Device

Ethernet Ethernet

CI Core
CI Portal CI Gateway
CI View

Vnet/IP Vnet/IP
Ethernet Ethernet
CENTUM etc. PLC CENTUM etc. PLC

F06.ai

Figure Example of Host-to-host Connection Configuration

All Rights Reserved. Copyright © 2021, Yokogawa Electric Corporation GS 36K01A10-01EN Feb. 12, 2025-00
<<Contents>> <<Index>> 7
Yokogawa Cloud Configuration
CI Server can use in a PaaS (Platform as a Service ) format that combines Yokogawa Cloud, a software license, and
maintenance. This solution facilitates the optimized management of production activities across an entire enterprise,
while also providing a remote operation environment to ensure efficient plant operations from any location.

CI View
CI View CI View
(HTML5)

Yokogawa Cloud
CI Core
CI Portal

Ethernet

CI Core
CI Gateway
CI Portal
CI View

Vnet/IP

Ethernet Ethernet

CENTUM etc. PLC

F10.ai

Figure Example of Yokogawa Cloud Configuration

All Rights Reserved. Copyright © 2021, Yokogawa Electric Corporation GS 36K01A10-01EN Mar. 11, 2025-00
<<Contents>> <<Index>> 8
 High Availability
Two types of redundant configurations are available.

HAC
Dual-redundant Platform for Computer
(High Availability Computing)
Active-Standby method Active-Standby method
Dual, Triple, and Quad redundant
Dual-redundant configuration is possible.
configurations are possible.
Features Switchover within 1 second without data loss
Capable of handling large amount of data.
during switching.
Redundant configuration over remote locations Configured with two computers installed in the
is possible (*1) same place.
The two computers have different IP The two computers making up the redundancy
addresses. If a server is switched due to feature are treated as one computer on the
a failure, CI Portal automatically switches system. They have the same IP address, and
connection to the new server on active side, the other computers do not need to be aware of
Handling on the network
so there is no need to switch the connection in the state of redundant operation (for example,
CI View. which computer is the "active side"), and
access can be made in the same way as in a
non-redundant configuration.
Triggers for automatic
Hardware failure, software failure Hardware failure
switching
Specified hardware models No Yes (*2)
Note: It's recommended to use Dual-redundant Platform for Computer common dual-redundant configuration for Yokogawa
system products in case connecting with Vnet/IP.
*1: For Disaster Recovery (response in case of disaster, etc.) purposes, redundancy can be configured regardless of distance
between servers.
*2: The computers used for Dual-redundant Platform for Computer are limited to the models specified by Yokogawa. For
details, refer to "Dual-redundant Platform for Computer" (GS 30A05C10-01E).

CI Portal CI Portal CI Portal CI Portal

CI View CI View CI View CI View

Ethernet Ethernet

Dual-redundant platform
HAC for computer
CI Core CI Core CI Core CI Core

Vnet/IP
Vnet/IP
Ethernet
CENTUM etc. Ethernet
CENTUM etc.
PLC
PLC
F07.ai
F08.ai

Figure Example of HAC Configuration Figure Example of Dual-redundant Platform for

Computer Configuration

All Rights Reserved. Copyright © 2021, Yokogawa Electric Corporation GS 36K01A10-01EN Mar. 3, 2023-00
<<Contents>> <<Index>> 9
n EXTERNAL INTERFACE
CI Server supports industry standards such as OPC UA and ODBC. CI Server supports native communication drivers
to Yokogawa products as well as various controllers of 3rd parties.

 Linkage with External Applications

Interface Option Code Description

OPC DA v2.04
OPC Classic client (*1) (*3)
OPC A&E v1.02
OPC DA v2.04
OPC Classic server (*1) /PCD
OPC A&E v1.02
OPC DA Server/Client, OPC A&E Server Tunneller
OPC Classic Tunneller This function is needed to the computer installed 3rd-parties' OPC Classic
/PCT
(*1) Server/Client to communicate with CI Server via secure communication used
among CI Core.
OPC UA DA v1.04
OPC UA client (*2) (*4) (*3) OPC UA A&C v1.04
Supports redundant communication with OPC UA server
OPC UA DA v1.04
OPC UA server (*2) (*4) OPC UA A&C v1.04
/PCU OPC UA HA v1.04
OPC UA PubSub (*2) OPC UA v1.04
For both process and configuration data, ODBC API conformance level 1, SQL
ODBC server (*1) /PDB conformance level minimum.
32-bit/64-bit is supported
MQTT 3.1.1
MQTT (*3)
Communication with lower and higher targets (IIOT devices) by MQTT protocol.
Supported RDBMS: MS SQL Server 2016 SP2 or later.
Data can be sent and received to/from applications that use RDBMS through the
RDBMS (Relational RDBMS. CI Core connects to the RDBMS and synchronizes data between CI
DataBase Management (*3) Core and the RDBMS. When data in CI Core is changed, the data is copied to
System) connection (*1) the RDBMS.
When the data in the RDBMS is changed, it will be reflected in the data on CI
Server.

*1: Supported on Windows OS only.

*2: Supported on Windows OS and Linux OS.
*3: Supported as standard function and does not need to select any Option Codes when ordering.
*4: The Windows OS of CI Server R1.01.01 or later (model name: CS2CLC) is acquired OPC UA certification from the OPC
Foundation.

Certified profiles R1.01.01 to R1.03.0D

Application Profile Group Category Supported Profiles and Facets
OPC UA Server UACore R1.04 Certified Profiles Standard 2017 UA Server Profile
SecurityPolicy – None
SecurityPolicy – Basic128Rsa15
SecurityPolicy – Basic256
OPC UA Server UACore R1.04 Security Policies
SecurityPolicy [A] Aes128-Sha256-RsaOaep
SecurityPolicy [B] – Basic256Sha256
SecurityPolicy Aes256-Sha256-RsaPss
User Token Anonymous
User Identify
OPC UA Server UACore R1.04 User Token User Name Password
Tokens
User Token X509 Certificates
OPC UA Client UACore R1.04 Certified Profiles Minimum UA Client Profile

All Rights Reserved. Copyright © 2021, Yokogawa Electric Corporation GS 36K01A10-01EN Oct. 18, 2024-00
<<Contents>> <<Index>> 10

Application Profile Group Category Supported Profiles and Facets

Core 2017 Client Facet
Base Client Behaviour Facet
Discovery Client Facet
Subnet Discovery Client Facet
OPC UA Client UACore R1.04 Additional Facets AddressSpace Lookup Client Facet
Entry Level Support 2015 Client Facet
Attribute Write Client Facet
DataChange Subscriber Client Facet
Method Client Facet
SecurityPolicy – None
SecurityPolicy – Basic128Rsa15
SecurityPolicy – Basic256
OPC UA Client UACore R1.04 Security Policies
SecurityPolicy [A] Aes128-Sha256-RsaOaep
SecurityPolicy [B] – Basic256Sha256
SecurityPolicy Aes256-Sha256-RsaPss
User Identify User Token Anonymous
OPC UA Client UACore R1.04
Tokens User Token User Name Password

Certified profiles R1.03.0E or later

Application Profile Group Category Supported Profiles and Facets
OPC UA Server UACore R1.04 Certified Profiles Standard 2017 UA Server Profile
SecurityPolicy – None
SecurityPolicy – Basic128Rsa15
SecurityPolicy – Basic256
OPC UA Server UACore R1.04 Security Policies
SecurityPolicy [A] Aes128-Sha256-RsaOaep
SecurityPolicy [B] – Basic256Sha256
SecurityPolicy Aes256-Sha256-RsaPss
User Token Anonymous
User Identify
OPC UA Server UACore R1.04 User Token User Name Password
Tokens
User Token X509 Certificates
OPC UA Client UACore R1.04 Certified Profiles Minimum UA Client Profile
Core 2017 Client Facet
Base Client Behaviour Facet
Discovery Client Facet
Subnet Discovery Client Facet
OPC UA Client UACore R1.04 Additional Facets AddressSpace Lookup Client Facet
Entry Level Support 2015 Client Facet
Attribute Write Client Facet
DataChange Subscriber Client Facet
Method Client Facet
MDIS Base Client Facet
MDIS Valve Model Client Facet
MDIS Instrument Model Client Facet
MDIS Instrument Out Model Client Facet
MDIS Instrument Arbitration Model Client Facet
MDIS Discrete Model Client Facet
MDIS Discrete Out Model Client Facet
Companion MDIS Discrete Arbitration Model Client Facet
OPC UA Client MDIS 1.03
Facets MDIS Digital Model Client Facet
MDIS Digital Out Model Client Facet
MDIS Digital Arbitration Model Client Facet
MDIS Choke Model Client Facet
MDIS Electric Choke Model Client Facet
MDIS Motor Model Client Facet
MDIS CIMV Model Client Facet
MDIS TimeSync Object Client Facet
SecurityPolicy – None
SecurityPolicy – Basic128Rsa15
SecurityPolicy – Basic256
OPC UA Client UACore R1.04 Security Policies
SecurityPolicy [A] Aes128-Sha256-RsaOaep
SecurityPolicy [B] – Basic256Sha256
SecurityPolicy Aes256-Sha256-RsaPss
User Identify User Token Anonymous
OPC UA Client UACore R1.04
Tokens User Token User Name Password

All Rights Reserved. Copyright © 2021, Yokogawa Electric Corporation GS 36K01A10-01EN Oct. 18, 2024-00
<<Contents>> <<Index>> 11
 External Controller Connection

Interface Option Code Description

/FCA or /FCS
CENTUM VP R5.01.20 or later
Yokogawa Vnet/IP (*1) /SCA or /SCS
ProSafe-RS R2.02 or later
/UGA or /UGS
Yokogawa STARDOM (*1) (*3) FCN/FCJ R2.01 or later
Yokogawa DAQSTATION (*1) Please contact Yokogawa for details.
Yokogawa DAQMASTER (*1) Please contact Yokogawa for details.
Yokogawa SMARTDAC+ (*1) Please contact Yokogawa for details.
Yokogawa FA-M3 (*1) Please contact Yokogawa for details.
Modbus slave (*1)
Modbus master (*1)
AC Gateway client
Yokogawa Vnet/IP softstack (*1) /DVN Dedicated Virtualization platform
IEC 60870-5 client (*1) /DEC IEC 60870-5-101/102/103/104
Supports MMS specifications and can read and write from/to tags.
IEC 61850 client /DEP
Includes SISCO stock layer software.
DNP3 master /DDN
WITS level 0 slave (*1) /DWS Well site Information Transfer Specification (WITS)
WITS level 0 master (*1) /DWM Well site Information Transfer Specification (WITS)
HEX repeater /DHE
Rockwell Allen Bradley CIP, Rockwell Allen Bradley DF1,
Rockwell Automation (*1) /DRC
Rockwell Allen Bradley DH+, Rockwell Allen Bradley PLC5
Siemens 3964R, Siemens SAPI-S7
Siemens (*1) /DSE
(SIMATIC.NET SAPI-7 software package is required.)
/DBB Emerson Bristol Babcock, BSAP
Emerson
/DFR Emerson Fisher ROC
MELSEC (*2) /DME
OMRON /DMR OMRON FINS
Telemetry integration environment /DTE Telemetry Integration Environment (TIE870-5 client)
HART router /DHA
Beckhoff ADS /DBA
Beckhoff BK8100 /DBK
Bachmann M1COM /DBM
Note: Please contact Yokogawa for connectable versions.
*1: Supported on Windows OS only.
*2: Supported on Windows client OS only.
*3: Supported as standard function and does not need to select any Option Codes when ordering.

All Rights Reserved. Copyright © 2021, Yokogawa Electric Corporation GS 36K01A10-01EN Oct. 18, 2024-00
<<Contents>> <<Index>> 12
n SECURITY
Security-related functions include IT security function, encrypted communication, user management, and audit trailing.
In addition, Yokogawa's Endpoint Security Service can be applied.

 IT Security Function
This function uses the security function of Windows OS to fortify the CI Server components. IT Security Tool is
provided to configure this feature. This tool is commonly installed in Yokogawa system products and enables
configuration of security settings. The following threats are addressed:

Threat Description
Threats from unauthorized persons through networks, which affect the system or steal
Attack over the network
important data.
Threats from unauthorized persons who operate terminals, which affect the system or
Direct attack by terminal operation
steal important data.
Computer/data theft Threats where computers with important data are stolen.

The applicable security measures are classified into the following types.

Measure Description
Access control Restricts access to files, folders, registries, and programs.
Personal firewall tuning Controls communications among computers on the network.
Stopping unused Windows services Stops programs and services that are not in use.
Changing IT environment settings Enables strong Windows security measures.
Enables centralized management of security policies for computers connected to the
Applying group policy settings
same domain.

 Encrypted Communication
The following encrypted communications are supported:
• Encryption of communications among CI Servers
Communication between CI Portal and CI View: Secure Sockets Layer (SSL) is used.
Communication between CI Core and communication between CI Core and CI Portal: Secure UDP communications
and public/private keys are used.
• Encryption of OPC UA communication
By using the encryption function of OPC UA, secure and reliable communication is available.

 User Management
The following authorizations can be set by users:
• Operating and displaying windows
• Operating devices and data
• Generating reports and trends
• Alarm management, notification, and acknowledgment
• Operation log (automatic or manual)
• Scope of engineering

The following user authentications are available:

• Authentication by CI Server (Authentication by Windows can be used together)
• Integration with Windows user authentication process and account settings
Single sign-on (SSO) can be used by integrating with Active Directory. Using the Simple and Protected GSS-
API Negotiation mechanism (SPNEGO), which is a standard method for user authentication of web servers, web
authentication by SSO is supported for HTTP requests.

All Rights Reserved. Copyright © 2021, Yokogawa Electric Corporation GS 36K01A10-01EN Oct. 18, 2024-00
<<Contents>> <<Index>> 13
 Audit Trail
Logon/logout history and operation records for data are saved as an audit trail. Audit trail data can be displayed on the
screen and output as reports. Also, the operations and data to save as an audit trail can be defined.

Items saved are as follows:

• Events
-Login, logout, login failure
-Insert, change, delete data (by operator or application)
-Alarm acknowledgment (by operator or application)
-Alarm shelving and un-shelving operations
• Event occurrence time stamp
• Name of the user who operated
• Name of the computer on which the operation was performed
• Values before and after the change (For example, when changing data, the values before and after the change will
be saved.)
• Event related items
-Data name
-Program name
-Alarm notification destination
-Users to notify of alarms
-User profile
-Controller interface
• Name of the program that generated the event
• Information for each application (if any application is created in the project)
 Endpoint Security Service
Yokogawa's Endpoint Security Service is provided to reduce the risk of malware infection on Windows PCs and
servers and helps maintain system health throughout the life cycle.
Anti-virus Software
The anti-virus software is dedicated for Yokogawa control systems based on the Trellix's intrusion prevention
technologies. This product is used as standard anti-virus software for Yokogawa IA systems.
Whitelisting Software (*1)
The whitelisting software is the security measure software using the Trellix's application control technologies and with
whitelist method provided with the optimum settings for Yokogawa control systems. This product is used at malware
measure service for Yokogawa IA systems.

For more details, please refer to the GS 43D02T30-02E "Endpoint Security Service".

*1: The whitelisting software is not supported on Windows 11 Pro or Windows 10 Enterprise LTSC 2021 (including IoT version
for OEM use).

All Rights Reserved. Copyright © 2021, Yokogawa Electric Corporation GS 36K01A10-01EN Oct. 18, 2024-00
<<Contents>> <<Index>> 14
n HMI FUNCTION
 Features
• Operability
CI Server enables users to freely create operation and monitoring windows based on ergonomics and the guidelines
stipulated by companies or in projects, and supports efficient operation and monitoring. Screen operations such as
zooming and scrolling are also provided as standard functions.
• HTML5 support
Operation and monitoring windows support HTML5 format for displaying on Web browser and mobile devices
• Flexible Graphic Deployment
The operation and monitoring windows are freely configured by combining the standard parts such as process data,
alarms, historical trends, real-time trends, faceplates, reports, and event history, and parts created for each project.
Multiple layers and visibility groups can be set for each window, and they can be shown or hidden according to user
authorizations, process conditions, and the zoom level.
• HMI with high visual effect
The built-in ISA-101 compliant symbol library enables easy creation of HMI with high visual effects. Advanced
Operating Graphics (AOG), a consulting service provided by Yokogawa, is supported.
• Various data sources
Dashboard screens can be easily displayed because of the ability to display information from a variety of data
sources such as video streaming (such as camcorders) and websites.
• Multi-node input
Data collected from multiple CI Core can be integrated and displayed on a single operation and monitoring window.
For example, it is possible to collect from each CI Core only the data requested in a certain management level and
display them.

 Trend Graph
Real-time data and historical data are displayed seamlessly. The user interface is easy to operate and allows for
efficient trend configuration.
Pen assignments to the trend graphs, display items, and display format may be configured both at the engineering
stage and during operation and monitoring. From the trend screen, it is possible to save the configuration data for
multiple trends and call up the trends.

Key features:
• Maximum number of pens: 50 per one trend component
• Minimum displayable time unit: 1 ms
• Minimum update cycle: 1 second
• Maximum display time span: No limit
• Number of storable trends: Depends on disk capacity
Save, call up, print, and protect trends
• Export trend data and images (bitmap, CSV file)
• Setting accessible users
• 2D/3D/tabular rendering
• Line segment graph/steps graph/scatter chart/area chart
• XY plots
• Show/hide legend and scale
• Reversing of time and value axis
• Scale fonts
• Trend display in absolute time/relative time and shift time span
• Display alarm status on the hairline
• Linked display of trend and alarm overview
• Pen assignment by drag-and-drop
• Range-scale and time-scale zoom function (XY-axis simultaneous zooming with rectangular selection is also
possible)
• Show/hide value slider, time slider, time control, 3D control, hairline, and pen panel
• Micro Trend (small size simplified trend available for ISA-101-compliant screens)
• DTS Trend (trend display of 3D data acquired from Yokogawa DTSX optical fiber temperature sensor devices, that
is, temperature, distance, time data collected at each point along the optical fiber cable)
• Sequence of events logging (SOE-logging) (*1)

*1: Please contact Yokogawa if this function is used.

All Rights Reserved. Copyright © 2021, Yokogawa Electric Corporation GS 36K01A10-01EN Oct. 18, 2024-00
<<Contents>> <<Index>> 15
n HISTORICAL
 Historical Data
All data handled in CI Server can be saved as historical data. The types of data are as follows:
• Data (data collected from the systems and controllers, internal calculation data)
• Alarm
• Audit Trail
• System log

Historical data can be output to the following:

• Screen display
• Trend
• Report
• Text file

The following timing can be specified to save historical data:

• Save periodically
• Save on event (when the value changes, etc.)

 Aggregations
The aggregation calculation function is provided for creating daily reports, monthly reports, etc.
• Aggregation cycle
30 minutes, hourly, shift-based, daily, weekly, monthly, and yearly aggregation
• Aggregation function
Minimum, maximum, mean, integral, standard deviation, counter, and differential summation

 Report
Historical data and configuration information can be output as tabular or time-series reports.

Item Description
Format Freely configurable
Output destination Selectable from graphic display, file, and printer by report
Automatically created at the specified time, fixed cycle, or event occurrence.
Generation timing
On-demand manual creation is also possible

 Excel Add-in Report

Reports can also be created by using Excel Add-in. Making it easy to create reports such as daily and monthly reports
and analyze process data because data in CI Core can be acquired via a work book. Since the range of accessible
data can be limited by each user, secure data retrieval is ensured.

All Rights Reserved. Copyright © 2021, Yokogawa Electric Corporation GS 36K01A10-01EN Oct. 18, 2024-00
<<Contents>> <<Index>> 16
n ALARM
 Alarming
Alarms which have been generating are listed on a current alarm overview screen that can operation such as alarm
confirmation.
History of alarms are listed on a historical alarm overview screen. Alarms can be notified by e-mail and SMS.
CI Server generates and displays alarms on its own. Alarms generated outside the CI Server (e.g. CENTUM system)
can be captured and displayed via OPC A&E or OPC UA A&C. V net alarms can be handled as OPC UA alarms also.
Alarms can only be viewed and manipulated by authorized users.
The alarming functionality consists of the following functions.

Category Function Description

Judges the presence of an alarm condition based on the high/low limit
Judgment by limit
values of the item value.
OPC A&E alarm detection Captures alarm information from an OPC A&E server.
Alarm detection OPC UA A&C alarm
Alarm information is taken from OPC UA A&C server.
detection
Alarm information is directly taken from Vnet/IP and converted to the
V net alarm detection
OPC UA alarm format. V net alarms are handled as OPC UA alarms.
Alarm acknowledgment Alarm acknowledgment Operators perform the operation to acknowledge important alarms.
Alarm overview Lists active alarms or alarms that were active in the past.
Alarm sound Plays the alarm sound according to the alarm that has occurred.
Area of Interest Filters the alarms by the label attached to the data.
Alarm selection area Filters alarms by conditional expression.
Alarm display/operation
Alarm shelving Temporarily shelves low-priority alarms to respond to high-priority alarms.
Alarm link display From the alarm overview, calls up the window related to the active alarm.
Export to file Exports alarms to a file.
Alarm inhibition Alarms can be turned off for each data or device.
First-out group Shows only the first alarm in the group. Multiple groups can be nested.
Alarm group
Alarm collection group Manages alarm states collectively for grouped alarm sources.
Alarm notification Alarm notification Sends alarm notification by email or SMS.
Report Report function Outputs alarms as reports.

The alarming functionality consists of the following functions.

Name Description
Displays active alarms. Alarm acknowledgement operation is performed
Current alarm overview
on this screen.
Displays the records/history of alarms that occurred and returned to
Historical alarm overview normal in the past, and acknowledgement operation and other alarm
operations performed.
Displays alarms that have been shelved and moved from the current
Shelved alarm overview
alarm overview.

Filters can be used for alarm display/operation and alarm notification. Two types of filters are available:

Type Description
Filter by date and time Filters by specifying the date and time or specifying the period.
Filter by conditions Filters by data name, area of interest, or alarm selection area.

All Rights Reserved. Copyright © 2021, Yokogawa Electric Corporation GS 36K01A10-01EN Oct. 18, 2024-00
<<Contents>> <<Index>> 17
The following display behavior can be set for alarms.

Type Description
Displays as an alarm only when the alarm state continues for a certain
Delayed alarm
period of time.
Displays as an alarm at specified time intervals if the specified time
Repeated alarm
elapses while the alarm state remains.
With the alarm grouping function, the situation where many individual alarms are raised can be avoided to reduce the
load of the operator responding to alarms. There are two types of groups:

Type Description
This is a mechanism to avoid that the alarm overview becomes a flood of
alarms by displaying only the first raised alarm in the group, suppressing
First-out group
the alarms in the group that would otherwise be raised after that. Multiple
groups can be nested.
Active/acknowledged/reset states are managed collectively for grouped
Alarm collection group
alarm sources.

 Alarm System Performance Analysis (ASPA)

ASPA is a function that analyzes alarm data history and creates reports. ASPA provides performance analysis
according to EEMUA191 and ISA18.2, which are guidelines for ensuring the quality and effectiveness of alarm
systems, and displays the analysis results in graphs and charts. By taking measures according to the analysis results,
the load on the operator and the risk of critical alarms being overlooked can be reduced to avoid making mistakes or
delays in making decisions to ensure safety.

Main analysis items:

• Operator load KPI (EEMUA191 section 4.1.1)
• Operator load performance (EEMUA191 section 4.1.2)
• Alarm rate and alarm flood (EEMUA191 appendix A12.7)
• Top ten alarm factors (EEMUA191 appendix A12.6)
• Long-standing alarm (EEMUA191 appendix A12.8)
• Correlation of serious alarms (EEMUA191 appendix A12.11)

 V net Alarm Gateway (VAGW)

VAGW is a function that receives alarm events or alarm status information from Vnet/IP, and converts them into an
OPC UA A&C format that CI Server can process. FCS/UGS/UGS2 (*1) of CENTUM VP and SCS (*2) of ProSafe-RS
alarms are handled as the OPC UA alarms. Moreover, the alarm acknowledgement operation can be synchronized
with station from which alarms occur through Vnet/IP.
*1: For FCS, V net stations connected to CI Server via V net router are also subject to obtaining alarms.
*2: SCSs that are integrated with CENTUM VP are subject to obtaining alarms.

VAGW supports CENTUM VP R6.07.10 or later. Regarding CENTUM VP's system alarm messages, process alarm
messages, and operation record messages related to the operation and monitoring function (hereafter referred to
as messages), the following messages are not eligible for reception by the CI server. The main items not subject to
reception are shown below. For details, refer to TI 36K01A15-01EN.
Messages to be checked by the operation and monitoring function of the relevant HIS.
• Messages for the status and operation of HIS
• Messages for HIS settings and engineering

Others
• Messages for UACS
• Messages for CENTUM XL, μXL (HF bus / RL bus)

All Rights Reserved. Copyright © 2021, Yokogawa Electric Corporation GS 36K01A10-01EN Mar. 11, 2025-00
<<Contents>> <<Index>> 18
 APPLICATION
 Linkage with GIS
This function links to a Geographic Information System (GIS) and acquires map images from an external Web
mapping server to display various information of CI Server on the map by superimposing the symbol graphics of CI
Server.

 DTSX Function
Distributed Temperature Sensor (DTSX) is a sensor that uses a fiber-optic cable to measure temperatures along the
length of the cable. CI Server can acquire data from the Yokogawa DTSX module and display it on the trend screen.

 AGA Calculations
The AGA (American Gas Association standards) calculation function consists of a set of functions.
The AGA calculation function covers the following standards:
• AGA3: Orifice metering of natural gas and other related hydrocarbon gases
• AGA7: Measurement of natural gas by turbine meters
• AGA8: Compressibility factors of natural gas and other related hydrocarbon gases
• AGA9: Measurement of gas by multipath ultrasonic meters
• AGA10: Speed of sound in natural gas and other related hydrocarbon gases
• AGA11: Measurement of natural gas by Coriolis meter
• V-Cone: Measurement of natural gas by V-cone
• Water-Cone: Measurement of natural gas by Water-cone
Further, the following additional calculations are supported:
• Gross heating value, relative density and compressibility factor for natural gas mixtures from composition analysis
by AGA5 or GPA2172 method
• Atmospheric pressure depending on latitude and altitude

 ENGINEERING FUNCTION
 Features
CI Server provides engineering environment for re-using engineering data, operation and monitoring windows, and
graphic components of operation and monitoring windows. Engineering in a remote environment and engineering
using text files are also possible. Engineering can be performed efficiently even for large scale system. All items in the
following " List of Engineering Items" can be defined while the CI Server is running.

 List of Engineering Items

• User definition
Define the users who perform operation and monitoring and the user and the authority for the one who performs
engineering. Define user's authority to an authority group and assign a user to the authority group.
• Controller connection definition
Set controllers to be connected and communication protocols for the connection.
• External interface definition
When using external interfaces, define each external interface.
• Operation and monitoring data definition
Define the hierarchical structures, names, and attributes of the data that CI Server will handle.
The below is examples of attributes.
-Data type, engineering unit
-Mapping with data in the controller
-Alarm settings for each data (limit value, display color, group, acknowledgement type, etc.)
• Data processing definition
CI Server can start a program created in advance according to the timing of events (changes in collected data, etc.)
or a defined schedule. Two programming languages are available: Java and language specific to CI Server. Various
calculations and process control operations that use multiple data can be programmed.
• Alarm definition
Define the items described in " Alarming" above.
• Definition for historical data management
Define the data saved as historical data, and the settings (fixed cycle/event base and saving period). Define the
settings to a historical group and assign the saving data to the historical group.
• Audit trail definition
Define if there are items that need to be saved as an audit trail in addition to the default save items.
• Report definition
Define the format, output timing, and output destination of reports.
• Operation and monitoring window definition
Create windows for operation and monitoring.

All Rights Reserved. Copyright © 2021, Yokogawa Electric Corporation GS 36K01A10-01EN Oct. 18, 2024-00
<<Contents>> <<Index>> 19
Main definition items:
- Placement of components (graphics, text, data display, bar graphs, etc.)
- Placement of symbols (graphics of equipment such as pumps and tanks, ISA symbols, etc.)
- Placement of HMI components (alarm overview, trends, reports, etc.)
- Attribute settings (display/setting data, window expansion, color change, animation, etc.) of each placed
component
The tool for creating windows has various mechanisms for efficient window creation.
In the tool, graphics commonly used for equipment and devices are registered as reusable symbols. Symbols can
be created and registered.
- Window parts called components are provided.
- Template windows can be created.
- The windows and parts (symbols, components, etc.) on the window are easily copied.

 List of Engineering Tools

Engineering tool Define items / Description

User definition
Controller connection
Operation and monitoring data definition
Data processing definition
Engineering Module
Alarm settings
Definition for historical data management
Audit trail definition
Report definition
Edit Module Operation and monitoring window definition
Setup File Editor Basic configuration of the system
Quick Load Tool All items (Configuration import/export)
Extract necessary information from the CENTUM VP project database and converts to CI Server
CI Exchange for CENTUM VP
database
Extract necessary information from the CCC Prodigy project database and converts to CI Server
CI Exchange for Prodigy
database

n APPLICATION CAPACITY
Item Specification Remarks
In the case of HAC, the number of CI Core actually
Maximum number of CI Core (*1) 4095 stations installed is counted. If more than 4095 CI Core are
needed, please consult Yokogawa.
Maximum number of controllers that can be connected
10000 stations
to one CI Core
Maximum number of CI Core hierarchy layers 128 levels
Maximum number of CI Portal that can be connected to
4095 stations
one CI Core (*1)
Maximum number of CI View that can be connected to Includes the CI View that run on the same computer as
500 stations
one CI Portal CI Portal and HTML5 clients.
Maximum number of monitors that can be connected to
4 stations
one CI View
Maximum number of data items that can be defined 16 million data
Maximum length of data name 256 characters Includes the dots (.) delimiting the levels in the name.
Maximum number of levels in data hierarchies 128 levels
Maximum length of a data hierarchy level name 31 characters
Number of HMI screens Unlimited
100 millisecond
Update cycle of HMI screen display This value can be changed.
(default)
Maximum number of users Unlimited
Maximum number of user groups Unlimited
*1: The total number of nodes (= computer stations) in one domain may not exceed 4095 (computer stations with only a Cl
View installed are not counted as a Node).

All Rights Reserved. Copyright © 2021, Yokogawa Electric Corporation GS 36K01A10-01EN Oct. 18, 2024-00
<<Contents>> <<Index>> 20
n OPERATING ENVIRONMENT
 Software Operating Environment
OS

Platform Name
Windows 10 Pro (64-bit)
Windows 11 Pro (64-bit) (*1) (*2)
Windows 10 Enterprise (64-bit)
Microsoft Windows Windows 10 Enterprise LTSC 2019 (including IoT version for OEM use)
Windows 10 Enterprise LTSC 2021 (including IoT version for OEM use) (*1)
Windows Server 2019 Standard (including IoT version for OEM use)
Windows Server 2022 Standard (including IoT version for OEM use) (*1)
Red Hat Enterprise Linux 9.4 (64-bit) (*3) (*4)
Linux
Ubuntu 24.04 LTS (64-bit) (*5)
Note: For software of other companies that runs on Windows or Linux, there are limitations on the combination with the CI Server
software and usage, so please contact Yokogawa.
Note: Please contact YOKOGAWA for using CI Server with Linux.
Note: CI View, the operator interface, is supported only on Windows OS.
*1: Supported by R1.03 or later
*2: MELSEC (/DME) is supported by R1.04 or later.
*3: supported by R1.02 or later.
*4: Red Hat Enterprise Linux 8.1 (64-bit) is supported by R1.01 only (not supported by R1.02 or later).
*5: supported by R1.04 or later
IT Security Tool

IT Security Tool Supported OS

Windows 10 Enterprise LTSC 2019 (including IoT version for OEM use)
Windows 10 Enterprise LTSC 2021 (including IoT version for OEM use)
IT security version 2.0
Windows Server 2019 Standard (including IoT version for OEM use) (*1)
Windows Server 2022 Standard (including IoT version for OEM use)
*1: Support by R1.02 or later

Vnet/IP

Windows 10 Enterprise LTSC 2019 (including IoT version for OEM use)
Windows 10 Enterprise LTSC 2021 (including IoT version for OEM use)
Vnet/IP
Windows Server 2019 Standard (including IoT version for OEM use) (*1)
Windows Server 2022 Standard (including IoT version for OEM use)
*1: Support by R1.02 or later

Dual-redundant Platform for Computer

Windows Server 2019 Standard (*1)

Dual-redundant Platform for Computer
Windows Server 2022 Standard (*2)
Note: For more details, please refer to the GS 30A05C10-01EN “Dual-redundant Platform for Computer”.
*1: Supported by Dual-redundant Platform for Computer R2.02 and CI Server R1.02 or later.
*2: Supported by Dual-redundant Platform for Computer R2.03 and CI Server R1.03 or later.

Web browser (for CI View Operator Interface)

Google Chrome 130.0

Web browser (for CI View Operator Interface) Mozilla Firefox 131.0
Microsoft Edge 130.0

All Rights Reserved. Copyright © 2021, Yokogawa Electric Corporation GS 36K01A10-01EN Mar. 11, 2025-00
<<Contents>> <<Index>> 21
Web browser (for CI View HTML5)

Web browser (for CI View HTML5) Google Chrome 130.0

Microsoft Excel (for Excel Add-in reports)

Microsoft Excel
Support OS
Version Edition
Windows 10 Pro (64-bit)
Office2019 Standard Windows 10 Enterprise (64-bit)
(32-bit / 64-bit) Professional Plus Windows 10 LTSC 2019 (including IoT version for OEM use)
Windows Server 2019 Standard (64-bit)
Windows 10 Pro (64-bit)
Windows 11 Pro (64-bit)
Semi-Annual
Microsoft 365 Windows 10 Enterprise (64-bit)
Enterprise Channel
(32-bit / 64-bit) Windows 10 LTSC 2019 (including IoT version for OEM use)
2022 / 2208
Windows 10 Enterprise LTSC 2021 (including IoT version for OEM use)
Windows Server 2022 Standard (64-bit)

PDF reader (for viewing Instruction Manuals)

PDF reader (for viewing Instruction Manuals) Adobe Acrobat Reader DC

 Hardware Operating Environment

CI Core/CI Gateway
Hardware requirements for CI Core are shown below.
CI Core/CI Gateway runs on computers with the following specifications.

Table CI Core/CI Gateway hardware operating environment

CPU Mandatory Intel Core i7 3.40 GHz or higher

Main memory Mandatory 8 GB or more (*1) (*2) (*3)
Storage Mandatory HDD/SSD with a capacity of 1 TB or more
Mandatory VI702 (control bus interface card)
(In case Vnet/IP connection) PCI Express
Communication device
Mandatory
Ethernet compatible network port (*4)
(In case Ethernet connection)
A drive supported by the OS used. An external DVD-ROM drive
DVD drive Mandatory
can also be used.
Note: If the hardware capacity satisfies the required performance, it is not mandatory to meet the described specification in the
above table.
*1: When 30 or more controllers (FCS / UGS / SCS) are connected using VAGW, adding 8 GB of memory is required.
*2: When using OPC UA Server, adding the memory is required according to the following number of Items.
- less than 20,000 Items: no addition
- less than 100,000 Items: adding 8 GB
- less than 200,000 Items: adding 12 GB
- more than 200,000 Items: adding 4GB per 100,000 Items
*3: When using ASPA, adding 8 GB of memory is required.
*4: Please prepare the number of this according to the network configuration. When using HAC, using a dedicated network
port for HAC is recommended.

All Rights Reserved. Copyright © 2021, Yokogawa Electric Corporation GS 36K01A10-01EN Feb. 12, 2025-00
<<Contents>> <<Index>> 22
CI Portal
Hardware requirements for CI Portal are shown below.
CI Portal runs on computers with the following specifications.

Table CI Portal hardware operating environment)

CPU Mandatory Intel Core i7 3.40GHz or higher

Main memory Mandatory 8 GB or more (*1)
Storage Mandatory HDD/SSD with a capacity of 1TB or more
Communication device Mandatory Ethernet compatible network port (*2)
A drive supported by the OS used. An external DVD-ROM drive
DVD drive Mandatory
can also be used.
Peripherals Mandatory Sound function (*3)
Note: If the hardware capacity satisfies the required performance, it is not mandatory to meet the described specification in the
above table.
*1: When using ASPA, adding 8 GB of memory is required.
*2: Please prepare the number of this according to the network configuration.
*3: Required only when using audio output such as alarm sound.
CI View
Hardware requirements for CI View are shown below.
CI View runs on computers with the following specifications (IBM PC/AT compatibles).

Table CI View hardware operating environment (when CI Core and CI Portal run on different computers)

CPU Mandatory Intel Core i7 3.40GHz or higher

Main memory Mandatory 8 GB or more
HDD/SSD with a capacity of 500 GB or more and free space of
Storage Mandatory
1 GB or more
Communication device Mandatory Ethernet compatible network card 1 Gb (*1)
A drive supported by the OS used. An external DVD-ROM drive
DVD drive Mandatory
can also be used.
Peripherals Mandatory Sound card (*2)
Note: The hardware also that doesn't meet performance described in the above can be used as CI view if its performance meets
a purpose of a project according to the screen contents; in case the CI view is not used as a main component of operation
and monitoring or is used with a tablet device.
Note: CI View, the operator interface, is supported only on Windows OS.
*1: The number of ports including onboard Ethernet. Prepare as many as needed according to the network configuration.
*2: Required only when using audio output such as alarm sound.

 Virtualization platform (R1.02 or later)

CI Server runs on Yokogawa IA System Products Virtualization Platform.
For details, refer to the GS "IA System Products Virtualization Platform" (GS 30A05B10-01EN)

 Dual-redundant Platform for Computer (R1.01 or later)

CI Server runs on Dual-redundant Platform for Computer.
For details, refer to the GS "Dual-redundant platform for computer" (GS 30A05C10-01EN)

All Rights Reserved. Copyright © 2021, Yokogawa Electric Corporation GS 36K01A10-01EN Feb. 12, 2025-00
<<Contents>> <<Index>> 30
 Examples of License Selection
The MS code of CI Server license is consisted as combination the part of CI Core function and the part of the other
necessary optional function.
An example of MS code used for the system consisted with CI Core, CI Portal, and CI View is in below.
Please make sure to place an order for a product maintenance license “CI Server Software Maintenance” after CI
Server software license purchased.
In case of Standalone Configuration
Ethernet

CI Core
CI Portal
CI View

Ethernet
PLC

F09.ai

Node Option Codes Item Description

CI Core CI Core for Windows /CE 1 CI Core Max Item Numbers: 16,000
Note: Modbus communication interface is included as standard in case CI server communicates with PLC via Modbus.

Please specify the following MS Code;

CS2CLCD-L11/CE01

In case of Remote CI Portal/Remote CI View Configuration

CI View CI View
(HTML5) (HTML5)

CI Portal 1 CI Portal 2
CI View CI View
CI View CI View

Ethernet

CI Core CI Core Example 1: Dual-redundant Platform for Computer

Example 2: HAC

Vnet/IP

Ethernet

CENTUM etc. PLC

F12.ai

All Rights Reserved. Copyright © 2021, Yokogawa Electric Corporation GS 36K01A10-01EN Feb. 12, 2025-00