1c Function Design Specification - HIS PDF

Spectrum PowerCC
Delhi Airport Metro Express Line (DAMEL)
Functional Specification
Historical Information System
SPC-TS-HIS-04-2-01
Spectrum PowerCC Historical Information System, Technical Specification

SPC-TS-HIS-04-2-01, Edition 12.2008 2
Note
Please observe safety notes and warnings for your own safety.
Disclaimer Copyright
Siemens AG shall not be liable for any incidental or consequential Copyright © Siemens AG 2007. All rights reserved
damages resulting from the performance or use of this product. This document is protected by German Copyright law and
This document has undergone extensive technical approval before international contracts as intellectual property of the Siemens AG.
being released. We review this document at regular intervals, and The document contains confidential information of Siemens AG
include appropriate amendments in subsequent issues. While which are protected by patent, copyright, trademarks or otherwise
every effort has been made to keep the information herein as as inventions, trademarks or creations of Siemens AG. The
accurate and up to date as possible, Siemens AG assumes no reproduction, duplication, transmission or use of this documents or
responsibility for errors or omissions or for damages resulting from its contents is not permitted without express prior written consent
the use of the information contained herein. The content of this of the Siemens AG .
document is for information only and in consequence, Siemens AG
cannot take over liability resulting in any way from the use of this Trademarks
document or parts thereof. Spectrum PowerCC® is a registered trademark of Siemens AG. An
These contents shall not become part of or modify any prior or unauthorised use is not permitted.
existing agreement, commitment or relationship. The sales The remaining descriptions in this documentation/information
contract contains the entire obligations of Siemens AG. The could be trademarks, the use of which by third parties for their aims
warranty contained in the contract between the parties is the sole could infringe upon the owner’s rights.
warranty of Siemens AG. Any statements contained herein do not
create new warranties or modify the existing warranty.
Document Release 03
Edition 04.2007
History Delhi Airport Metro Express Line (DAMEL)
History
Version Date Modification
04-2-01 Dec-2008 First Edition

Preface
Safety Notes
This manual does not constitute a complete catalog of all safety measures required for operating the
product in question because special operating conditions might require additional measures. For
application specific safety measures refer to the respective project documentation. However, it does
contain notes that must be adhered to for your own personal safety and to avoid damage to property.
These notes are highlighted with a warning triangle and different keywords indicating different degrees of
danger as stated in the Warning Conventions.
WARNING
WARNING indicates a potentially hazardous situation which, if not avoided, could result in death or serious
injury.
CAUTION
CAUTION used with the safety alert symbol indicates a potentially hazardous situation which, if not
avoided, may result in minor or moderate injury.
CAUTION
CAUTION used without safety alert symbol indicates a potentially hazardous situation which, if not
avoided, may result in property damage.
NOTICE
NOTICE used without the safety alert symbol indicates a potential situation which, if not avoided, may
result in an undesirable result or state.
NOTE
A note is a tip. The user does not need to follow this statement. However he will have advantages if he
does.
Qualified Personnel
Only competent and authorized personnel should work with this product after becoming thoroughly familiar
with all warnings, safety notices, operating instructions and maintenance procedures.
Use as described
The product must not be used for any other purposes than that described in the technical documentation.
If it is used together with third-party devices and components, these must be recommended or approved
by Siemens AG. The successful and safe operation of this product is dependent on adequate
transportation and proper handling , storage, installation, operation and maintenance.

Preface Delhi Airport Metro Express Line (DAMEL)
Purpose
This technical specification provides an introduction to the use and implementation of Historical
Information System in Spectrum PowerCC.
Scope
This technical specification describes the situations in which Historical Information System is used and the
algorithms and data that it uses.
Audience
This technical specification is written for system engineers. However, the Introduction, Functionality, Data
Requirements, and User Interface chapters discuss Historical Information System in terms most readers
should understand. The Algorithms Implemented chapter requires more specialized knowledge.
Prerequisites
This technical specification is designed and written based on the assumption that readers are already
familiar with the Spectrum PowerCC product concepts, design and architecture information, such as
domains and contexts. This information is presented in higher-level overview documents (refer to the
Related Product Documents subsection of this Foreword). It is also helpful if you are familiar with and
understand object oriented application technology.
Organization
This technical specification proceeds from general introductory material to complex mathematical
specifications. The following table outlines the organization of this technical specification by listing chapter
titles and brief content descriptions:
Chapter Contents
Introduction Briefly introduces the Spectrum PowerCC Historical Information System
product module.
Functionality Describes Dispatcher / Operator functions
System Characteristics Describes performance, sizing, and quality of planning of Historical Informa-
tion System.
External Data Interfaces Explains data and information exchanges.
User Interface Describes the user interface design.
Implemented Concepts Describes the implemented algorithms and equations; briefly explains how
they are used and their importance in the application and overall system
operations.
Engineering Provides an overview of the tasks required for the configuration of Historical
Information System (HIS) functions.
Questions?
This manual provides overview information. Historical Information System is one member of a family that
contains a number of other products, some of which may be discussed briefly herein. If you have
questions, either about Historical Information System or other members of the Spectrum PowerCC product
family, please contact your Siemens representative.

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2 Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.2 Data Collection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.2.1 Continuous Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.3 Aggregation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.4 Data Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.4.1 Online Archive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.4.2 Long Term Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.5 Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.6 Data Correction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.7 Data Retrieval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3 System Characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.1 Protection Against Data Loss. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3.2 Scalability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5 Implemented Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.1 Data Collection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

5.2 Aggregation and Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5.3 Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.4 Data Correction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.5 Quality Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
6 Engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.1 ORACLE Partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

6.2 HIS Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
6.3 Data Collection Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
6.4 Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
6.5 HIS Archiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
6.6 Long Term Archiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
7
Introduction Delhi Airport Metro Express Line (DAMEL)
1 Introduction
The Historical Information System (HIS) collects and stores the data of the system in a solid and reliable
RDBMS-based archive. It performs data collection and storage, both periodically and non-periodically
(=spontaneously).
HIS is designed to store high volumes of data.
It supports the following archives:
• Online archives for direct access via the HIS Web UI
• Long-term archives, which store configured data on an external storage medium; these data may later
be reloaded for online retrieval
Data in online archives are available for all authorized users and may also be edited by these users.
The following definitions are required for HIS. These definitions can be made via the Information Model
Management (IMM):
• Data points whose data shall be stored
• The collection rate (periodic or non-periodic)

2 Functionality
Table of Content
2.1 Overview 10
2.2 Data Collection 11
2.3 Aggregation 12
2.4 Data Storage 13
2.5 Calculations 15
2.6 Data Correction 16
2.7 Data Retrieval 17

Functionality Delhi Airport Metro Express Line (DAMEL)
2.1 Overview
2.1 Overview
HIS provides the following functions:
• Collection and storage of the realtime values of:
– analog data
– accumulators
– digital data
(alarms, status information, application messages)
• Aggregation of analog values (minima, maxima, integrals, averages)
• Compression of analog values
• Definition and execution of calculations
• Manual data correction by authorized users (manual update) and recalculation of dependent values
• Web User Interface (Web UI) for e.g.:
– value modifications (manual update)
– viewing stored values (data retrieval)
– definition and execution of calculations

For more information about the HIS Web UI features refer to chapter "User Interface" in this docu-
ment.
• Long Term Archiving tool for configuring the transfer of data to offline archives as well as to reload
these offline data into HIS.
• Convenient integration with ODBC/OLE DB-based tools (such as Microsoft Excel)

2.2 Data Collection
2.2 Data Collection
2.2.1 Continuous Data Collection
One of the following collection types can be configured for a data point (via IMM):
• Spontaneous (data collection rate = 0)
This configuration is used for digital values (alarms, status changes, application messages).
Furthermore this configuration is mandatory for events. If the value and the quality do not change,
they are not archived.
Note that due to the compression algorithm even spontaneous archived values are only maintained
with a minimum 1-sec-cycle.
• Periodic (data collection rate > 0)
This configuration can be used for analog values and accumulators. In this case the system checks
after a configurable time period (= collection rate) whether a value has changed and if so stores this
value. For more details about the influence of the collection rate on value archiving refer to chapter
"Implemented Concepts".
To avoid data loss in case of system stress or disturbance, the collected and not yet stored data are
buffered in files.

2.3 Aggregation
2.3 Aggregation
Aggregation is only possible for analog values. Integrals, minima and maxima are so-called aggregation
values. The aggregation values can be determined in periods of 5 minutes and 1 hour. After the
determination, those aggregation values are also stored in the archive.
The aggregation values for other periods and all average values are determined on-the-fly only.
The aggregation values for periods less than 5 minutes are determined by linear interpolation. The
aggregation values for periods greater than 5 minutes are based on the aggregation values of the 5
minutes periods or the 1 hour periods.
The average values are determined using the integrals.
The following periods are supported for data aggregation:

• a calendar day,
• a calendar week,
• a calendar month,
• a calendar year

2.4 Data Storage
2.4 Data Storage

HIS data can be stored periodically as well as non-periodically (spontaneously).
The collected data are stored with:
• the time stamp

(represented in Universal Time Coordinated (UTC))
• the value
• the quality code
(good, entered, blocked, not updated, unusable, initial value)

• the manual update flag
The data are stored in:
• an online archive
• a long-term archive (optionally)
Data Compression of Analog Values

After a configured time (e.g. 2 hours) the stored analog data are compressed. For each data point a
maximum error can be defined via IMM. This error is the maximum difference between the real value and
an interpolated value after compression.
Data compression is achieved using the following methods:
• Linear compression filter based on the Overlapping Cones compression algorithm
• Rounding of values to a configurable number of significant digits
• Compression of the time stamps by a binary representation
For more information about the compression algorithm refer to chapter "Implemented Concepts" in this
document.
Sequence of Events (SOE)

The digital value (status information) of an event burst is received two times. At first (during the critical
phase of the event burst) the status information is received without a time stamp and gets the time stamp
determined by the receiving component. At second time (after the critical phase of the event burst) the
status information is received again, but now with the correct time stamp. The sequence of status
information received at second time is called sequence of events (SOE).
Both sequences are stored. The values of the second sequence are marked as SOE.
2.4.1 Online Archive
The online archive is implemented by a relational database (RDBMS). The online archive consists of the
following tables:
• analog values table
• accumulators table

2.4 Data Storage
• digital values table
• aggregation tables
– 5 minute table
– 1 hour table
The administrator configures:
• the available disk space
• the period how long a data value is retained in the online archive (retention period)
• the periodic transfer to the extended online archive
Data values older than the configured period are either deleted or moved to the long-term archive.
Each database operation is stored in a redo log which can be used for online backup.
2.4.2 Long Term Archive
Configured values are moved to the long term archive (offline files) automatically when they are older than
the specified retention period. Configuration of the data point values to be stored in the long term archive is
done using the Long Term Archiving tool.
The administrator configures:
• the location of the offline files
• the periodic transfer to the long term archive
The length of the offline files results from the configured periodic transfer.
It is recommended that the administrator saves the offline files (binary files) to an offline medium (e.g. on
tape, removable disks or CDs) on a regular basis. The standard MS tools are used for this task.
The saved data and their associated file names are maintained in a list for future retrieval.
The offline files can be reloaded via jobs and then accessed by the Web UI.

2.5 Calculations
2.5 Calculations
The operator can use standard formulas or ad-hoc formulas defined by the HIS Web UI. Calculated values
can also be used as the basis for further calculations. The calculated values are not stored in the archive.
Calculations are performed on demand by the HIS Web UI.

2.6 Data Correction
2.6 Data Correction

Analog values, accumulators, digital values and aggregated values can be modified using the HIS Web UI.
Modified values are marked with the manual update flag and are logged in the audit log with the old value,
the new value, the modification time and the user name.
Data modifications are taken into account for on-the-fly aggregations and calculations.

2.7 Data Retrieval
2.7 Data Retrieval

Stored data can be retrieved and displayed in different formats:
• tabular displays
• charts
• trending displays
For more details refer to chapter "User Interface" in this document.

3 System Characteristics
Table of Content
3.1 Protection Against Data Loss 19

3.2 Scalability 20

System Characteristics Delhi Airport Metro Express Line (DAMEL)
3.1 Protection Against Data Loss
3.1 Protection Against Data Loss

In a cluster system, data collection processes and ORACLE processes can be configured as Hot Standby.
For all transfers of data from SCADA to the archive database the data is buffered in the files. Buffered files
are necessary if the HIS database is not available or is too slow to respond due to a heavy workload. This
ensures that no real-time data that need to be stored are lost.
The data can be stored on mirror disks or by RAID systems.

System Characteristics Delhi Airport Metro Express Line (DAMEL)
3.2 Scalability
3.2 Scalability
The archive system can process very large amounts of data. At the same time, the archive is designed to
scale for systems ranging from tens of MB to hundreds of GB of data. It is possible to configure the archive
for systems of various sizes by simply changing configuration parameters in the Information Model
Manager without any code changes. Sizing parameters are restricted by disc size only.

4 User Interface
The user interface for Historical Information System (HIS) consists of a web-based user interface for
access to the online archive using the Internet Explorer, as well as a Long Term Archiving tool for
configuring the storage of data in offline archives and reloading these data into HIS.
HIS Web UI
The HIS web UI provides the following features:
• tabular displays for archive data (process values, aggregation values, power application values,
disturbance data values) with the following possibilities:
– trending of analog process data (from the past until the current time, the period is selectable)
– charting of analog process data (for the time period defined in the tabular display)
– printing the selected data
– creating a user display
– exporting the selected data to an Excel file
• view data point definitions (changes can only be made via IMM)
• creating formulas and calculations based on these formulas by assigning data points to the formula
variables
• execute calculations and view calculation results
• view alarms
Long Term Archiving (LTA) Tool

The Long Term Archiving tool provides the user interface for performing the following tasks:
• enable/disable Long Term Archiving
• modify the LTA configuration
• create and configure reload jobs
• view, execute and delete reload jobs

5 Implemented Concepts
Table of Content
5.1 Data Collection 23

5.2 Aggregation and Compression 24
5.3 Calculation 25
5.4 Data Correction 26
5.5 Quality Codes 27

Implemented Concepts Delhi Airport Metro Express Line (DAMEL)
5.1 Data Collection
5.1 Data Collection

For each value type (analog, accumulator, etc.) there is a separate data collection process. The data
collection rate determines whether each value that has changed shall be stored (collection rate = 0;
spontaneous), or whether data changes shall only be checked and stored after a certain period has
expired (collection rate > 0; periodic).
The size of the data collection rate determines the time period, after which the archive system checks
whether a value has changed and stores this value.
When the collection rate has expired, the collection engine checks if the value has changed since the last
check, and if so stores the new value together with the time stamp of the change (not with the time stamp
of the time when the collection rate has expired). The following example illustrates the meaning of the
collection rate and its influence on data storage (the example shows the time when a value change has
been received, the value itself, and the value stored in case the collection rate is 10 seconds):
• 12:12:05 -> 3
• 12:12:07 -> 8
• 12:12:09 -> 9
->> the value "9" is sent to the archive (at 12:12:10) with the time stamp 12:12:09
• 12:12:13 -> 11
• 12:12:21 -> 19
• 12:12:27 -> 23
This example shows that only the last value change before the collection rate has expired is considered. If
there was more than one value change during the collection rate all data changes except for the last one
get lost. Therefore the collection rate should be defined according to the frequency of value transmission.

5.2 Aggregation and Compression
5.2 Aggregation and Compression

Value aggregation and compression are only performed for analog values.
Aggregation reads the raw values of the last but one 5 minute interval and calculates the current value,
integral, minimum and maximum with the respective quality and (in case of extreme values) the respective
time stamp for all analog data points in 5 minute and 1 hour periods. Averages are not calculated, they are
calculated later on-the-fly when reading the integrals. Integrals (and therefore mean values) are always
calculated in one hour periods.
Aggregation results are stored persistently in database tables for 5 minute and hourly values. During
storage a technical compression is performed.
Logical compression reads the raw values of a 5 minute interval with a configurable time shift (usually 2
hours), processes the data as described below, stores the results in a separate table and removes the raw
values from the original table. Compression is interlocked against aggregation - it may not overtake the
aggregation. Aggregation itself is interlocked against data collection and may not overtake the collection.
Logical data compression tries to remove values from the archive whose difference to the previous value is
smaller than a parameterized maximum absolute value.
For performance reasons aggregation as well as compression calculate and store 5 minute grid points. If
no new values arrive for a data point to be archived, the last value continues to be stored every 5 minutes
as grid point.
When reading out the values the data are taken from raw value tables, 5 minute tables or hourly table,
depending on the desired time grid (cycle). Then the following calculations are performed on-the-fly:
• conversion of time stamps and data preparation
• consideration of grid points in compressed or 5 minute tables
• preprocessing of not yet compressed raw data (simulation of step curve)
• propagation of the latest value to the current system time (UTC)
• creation of a time period (cycle); for current values any cycle is possible, for on-the-fly aggregated
values the following rules apply:
– any cycle time is possible for cycles smaller than 5 minutes
– for cycle times greater than five minutes only multiples of 5 minutes are possible
– for cycles greater than an hour only multiples of one hour are possible
• interpolation of data according the selected time grid
• on-the-fly aggregation if desired
• calculation of the average from the integral
• consideration of not yet finished intervals
• temporary storage of the results in database tables
It is also possible to change the extracted values manually. As the changed values may be interpolated
and not stored in the database, the changes are stored in a separate table. For updated values a manual
update flag is set. For periods greater or equal to 5 minutes the changes are also used for larger cycles
and if required the hourly value is recalculated.

5.3 Calculation
5.3 Calculation
Formulas, calculations and the assignment of data points to variables are performed via the HIS Web UI
and stored in the database. They are executed on-the-fly after being started by the user in the Web UI.
Calculation results cannot be aggregated and are not stored persistently. Calculations based on other
calculations are possible.

5.4 Data Correction
5.4 Data Correction

Values may be updated manually by the user. These changes are indicated by a manual update flag and
are also stored in the audit log.
Manually updated values are considered in new aggregations and calculations immediately.

5.5 Quality Codes
5.5 Quality Codes

Initially quality codes are created by SCADA and are represented by a 32 bit field. During data collection
this quality code is evaluated and converted to a 1 character ASCII quality code.
As the 32 bit quality code is converted to an 8 bit code in HIS, this leads to a loss of information and cannot
be reversed.
HIS data compression enters the binary quality code into the raw value table. Persistent aggregation only
uses and stores the 1 character HIS quality code, however.

6 Engineering
Table of Content
6.1 ORACLE Partitioning 30

6.2 HIS Configurator 31
6.3 Data Collection Rate 32
6.4 Access Rights 33
6.5 HIS Archiving 34
6.6 Long Term Archiving 35

Engineering Delhi Airport Metro Express Line (DAMEL)
Online archive engineering comprises the following tasks:
• Partitioning of the ORACLE database
• Configuration of the system using the Configurator tool
• Parameterization of the data collection rate
• Configuration of access rights
• Configuration of Long Term Archiving

6.1 ORACLE Partitioning
6.1 ORACLE Partitioning

ORACLE provides the possibility to partition large database tables. Partitioning leads to a better
performance and improved administrative possibilities but is only sensible for large databases, as the
administration effort increases.

6.2 HIS Configurator
6.2 HIS Configurator

The HIS configurator is used for planning the system. Additionally it can be used to create a parameter file
that contains parameters required for archive installation.
The administrator defines the available disk space using the following parameters:
• HIS input tables
• event table
• 5-minute table
• 1-hour table

6.3 Data Collection Rate
6.3 Data Collection Rate

The data collection rate can be set during installation. It determines the time period, after which the system
checks whether a value has changed and if so, stores this value.

6.4 Access Rights
6.4 Access Rights

Online archive access rights are controlled using the areas of responsibilities (AOR). These are sets of
data points grouped according to geographic, technical, etc. properties.
There are two possible settings: either no restriction of access rights or static access rights based on data
points. One of them has to be selected during installation, a later change is not possible.
Additionally assignment of read-only access or read/write access is possible.

6.5 HIS Archiving
6.5 HIS Archiving
Following below is the HIS Archiving Scheme
Particulars Entries Retention Period
Messages 1000/day 90 days
Analogs (rate of change 1000 (including spares 7 days

1 minute) for future expansion)
Aggregated Analog 1,000 (including spares 90 days
(5min, 1 hr) for future expansion)
Accumulators 4000 (including spares 90 days
for future expansion)
Disk space reserved for Database backups & 40 GB
Long Term Archive (LTA)
Total disk space requirement for HIS 90 GB

6.6 Long Term Archiving
6.6 Long Term Archiving

After the default time period for storage of data in the online archive has expired (retention period), these
data may be moved to offline archives. All configuration actions regarding long term archiving as well as
reloading data from offline archives into online archives can be performed via the Long Term Archiving
Tool.
The offline archive files can be saved on the Hard Disk till desired (restriction until disk is full) or can be
copied to a suitable media


1c Function Design Specification - HIS PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1c Function Design Specification - HIS PDF

Uploaded by

Copyright:

Available Formats

Spectrum PowerCC

Delhi Airport Metro Express Line (DAMEL)

Historical Information System

Spectrum PowerCC Historical Information System, Technical Specification

Version Date Modification

04-2-01 Dec-2008 First Edition

Spectrum PowerCC Historical Information System, Technical Specification

Spectrum PowerCC Historical Information System, Technical Specification

Spectrum PowerCC Historical Information System, Technical Specification

3.1 Protection Against Data Loss. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

5.1 Data Collection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

6.1 ORACLE Partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

HIS is designed to store high volumes of data.

It supports the following archives:

• Online archives for direct access via the HIS Web UI

• Data points whose data shall be stored

• The collection rate (periodic or non-periodic)

Spectrum PowerCC Historical Information System, Technical Specification

Spectrum PowerCC Historical Information System, Technical Specification

• Collection and storage of the realtime values of:

(alarms, status information, application messages)

• Aggregation of analog values (minima, maxima, integrals, averages)

• Compression of analog values

• Definition and execution of calculations

• Web User Interface (Web UI) for e.g.:

– value modifications (manual update)

– viewing stored values (data retrieval)

– definition and execution of calculations

• Convenient integration with ODBC/OLE DB-based tools (such as Microsoft Excel)

Spectrum PowerCC Historical Information System, Technical Specification

2.2 Data Collection

2.2.1 Continuous Data Collection

• Spontaneous (data collection rate = 0)

Spectrum PowerCC Historical Information System, Technical Specification

The average values are determined using the integrals.

The following periods are supported for data aggregation:

Spectrum PowerCC Historical Information System, Technical Specification

2.4 Data Storage

The collected data are stored with:

• the time stamp

• the quality code

(good, entered, blocked, not updated, unusable, initial value)

The data are stored in:

• a long-term archive (optionally)

Data Compression of Analog Values

Data compression is achieved using the following methods:

• Linear compression filter based on the Overlapping Cones compression algorithm

• Rounding of values to a configurable number of significant digits

• Compression of the time stamps by a binary representation

Sequence of Events (SOE)

2.4.1 Online Archive

• analog values table

Spectrum PowerCC Historical Information System, Technical Specification

• digital values table

The administrator configures:

• the available disk space

• the periodic transfer to the extended online archive

2.4.2 Long Term Archive

The administrator configures:

• the location of the offline files

• the periodic transfer to the long term archive

Spectrum PowerCC Historical Information System, Technical Specification

Calculations are performed on demand by the HIS Web UI.