IP.

21 Development
Environment
Preparation & New
Digitization in
OLPIS
 IP.21 Overview
• IP.21 is primarily the real time Data Historian.
• IP.21 Data historian is mapped to different plant control
systems via the PLC’s at the plant and the data flows in a
periodic manner into the IP.21 database.
• The data historian of IP.21 is a real time database and runs
in the physical memory of the server system. The data is
recorded in a periodic manner per the configuration set in
the IP.21 Administrator.
• The data stream can be archived on to the server memory
and is stored in a custom format by IP.21.

Usefulness and Dependency on this application:

IP.21 Application is a very critical Application.

• Daily monitoring.
• Historical Records overview and analysis(Excel Add in / Aspen SQL Plus).
• Graphical Trends analysis of Tags(Aspen Process Explorer).
• Even different model preparation IP.21 Data is used.
• Calculated Tag overview(Aspen Calc / Aspen Graphic Studio).
• Plants reporting system like Tag wise data extraction from IP.21 Database.
• Other daily routine activities fully depends on this Application.
• OLPIS Application is fully dependent on this.
 Activity for IP.21 Application

Activity 1:
• This is very critical and useful IP.21 Application runs only in IP.21 Production Server(10.1.1.136).
• There had not previously any Development Environment Set up for IP.21 Application.
• But we have now set up IP.21 Application Development Environment in different server
(10.1.1.248) which is of similar to IP.21 Production Environment.
• In IP.21 Production server where total Analog Tags count approximately 29,881, total Discrete Tags
count 3,000, total Text Tags count approximately 500 and these tags data per minute wise data are
historizing in IP.21 Database. Thus, there is a very much dependency towards this Production server.
• Now we have a backup i.e. new development environment ready for IP.21 Application.
• By making this environment, we can do different type of testing activities here first before proceed
to IP.21 Production Environment.
• Some of the testing activities like:
 New Tag creation(Analog/Discrete/Text) here first.
 New Plant Integration first here and then after proper testing we will proceed to Production
Environment.
 Security Patch Installation.
 New License file installation / upgradation (if required) for testing purpose.
 For any kind of new activities or checking we can do in IP.21 Development Environment first.
Some of the screenshots of IP.21 Application in Development
Server (10.1.1.248)

IP.21 Administrator

IP.21 Manager
Aspen Process Explorer
 Cost Savings for Activity 1

• For any kind of IP.21 Migration activity (version upgradation),

Vendor charges(Helium) for more than 7 lakhs.
• Attached a commercial offer which has been taken by HPL from
Helium during version upgradation from V9 to V11.1.
• Above all, for this IP.21 Development Environment set up we
did not have to purchase any additional tokens. We have
utilized present tokens of IP.21 Production Server to keep
development environment running.
• We have used tokens from IP.21 Production server license file as
Development server IP.21 Application is not need to always
running, we used it for testing purpose for new activity.
 Activity for IP.21 Application

Activity 2:

• In IP.21 many tags data are stored over the minute interval thus the old historical data getting archived when it
goes to a limit of threshold frequency of 95% so that those data cannot be lost. It gets auto backup. But that data
was in Offline mode and not user readable format(arc.dat) and with that a generating key (arc.key) file also
created.
• There has been two set of archive / backup data available.

• Data retrieval from archive:

The auto-backup was configured for the new IP21 server in August 2020 for both HIS_NCU and HIS_OTH_PLNS
following the V11.1 migration and upgrade project as part of post-upgrade configurations. This data can be restored for
usages purpose in IP21.

• Data retrieval from backup data:

The restoration of the past 2-3 years data (2017-2020) can be done using the backup files available in the system.
This backup was taken manually for IP21 server by HPLIT during V9 to V11.1 migration activity.
 Historian
Following are the four repositories currently running on InfoPlus.21 server.
Repository Name Number of File Location
File Sets

TSK_DHIS 40 \\HPLIP21\IP21g200His\
TSK_DHIS_AGGR 3 C:\ProgramData\AspenTech\InfoPlus.21\c21\h21\TSK_DHIS
_AGGR\
HIS_NCU 135 D:\WORKING_FOLDER\HIS_NCU\
HIS_OTH_PLNS 547 D:\WORKING_FOLDER\HIS_OTH_PLNS\
Following is the back-up location for the repositories:
Table 3a: Repository location
Repository ACTIVE SHIFTED Back-up Location
Following are the properties of filesets in the HIS_NCU repository: Name
Parameter Value HIS_NCU D:\AutoBacku D:\AutoBackup\ D:\WORKING_FOLDER\HIS_NCU\BKUP\
p Shifte d
Path D:\WORKING_FOLDER\HIS_NCU\<arc number> \Active
Maximum Size 1000 MB HIS_OTH_PL D:\AutoBacku D:\AutoBackup\ D:\WORKING_FOLDER\HIS_OTH_PLNS\
NS p OTH_ Backup\
Timespan (DDDD HH:MM: SS) 30 00:00:00 \OTH_PLNS\ PLNS\Shifted
Active
Threshold 0.95 Table 3d: Auto Backup Details

Table 3b: NCU Repository Details

Following are the properties of filesets in the HIS_OTH_PLNS repository:
Parameter Value
Path D:\WORKING_FOLDER\HIS_OTH_PLNS\<arc
number>
Maximum Size 1000 MB
Timespan (DDDDD HH:MM:SS) 30 00:00:00
Threshold 0.95
Table 3c: Other Plants Repository Details
Archive and Back
Up data mapped in
IP.21 Administrator
• There are 357 repository has been created under
HIS_OTH_PLNS.
• This repository threshold frequency set has been
created.
• Each of the repository has been mapped with
the old backup data having key file and data
file.
• Generating log if the repository goes in Queue
mode.
• IP.21 Manager stopped.
• Started each of tasks related to IP.21
Application.
• Different .exe file executed during the process,
and several startup had been done in IP.21
Manager.
Archive and Back Up
data available for
extraction from IP.21
Administrator

• Created a script Query which

would be useful for data
extraction from IP.21
Database.
• All the historical records has
been mapped in IP.21
Development environment.
• Now, at a time user can get 5
years old historical data.
Cost Savings for Activity 2
• For the IP.21 Backup retrieval and make it available for
online Vendor has opted for 7,80,000/-.
• We have completed this and make the backup and archive data
available to online.
 Digitization of OLPIS from 01st January to March (Till Now)

Major Changes:

• Utility Balancing Page Steam section

schematic modification / changes:
• Few Graphical Changes.
• Total Generation, Consumption
and Export also has been
displayed.
• PRDS Valve opening and closing
has been included, It would
display “Green” for Opening and
“Red” for Closing . Percentage
also can be seen.
 Digitization of OLPIS from 01st January to March (Till Now)

• Utility Balancing Page Steam section

schematic modification / changes:
• Few Graphical Changes.
• Total Generation, Consumption
and Export also has been
displayed.
• PRDS Valve opening and closing
has been included, It would
display “Green” for Opening and
“Red” for Closing . Percentage
also can be seen.
Digitization of OLPIS from 01st
January to March (Till Now)

• Incorporation of parameters made available

online and mapping in Specific
Consumption Sheet of CPP Print sheet.
• This CPP Print sheet users of CPP can
download from their specific Plant report
sections.