|
|
Back
to values
At first glance, it seems the
small world of supervision software publishers escaped the turmoil
due to the burst of the Internet bubble: the players and products
are still (more or less) the same. But when looking closer, various
signs announce deep mutations. After focusing on "creating
value", many publishers were taken over by large groups,
and strategies changed.
Creators started off with the
"values" in their pocket in cash, and managers then
took over, ensuring the return on investment of the "values"
committed. The latter marketed very sophisticated –hence very
expensive- products, able (theoretically) to manage all company
requirements in terms of supervising and monitoring production
data; knowing what these new products provide in addition to the
traditional functions of well-designed supervision software, except
for a few details, remains rather mysterious and obscure.
We at Areal have chosen, without
changing prices, to enhance our products, make them easier and
faster to implement, providing smarter processes, opening them
to integration and data exchange with other applications.
For Areal, creating value means
developing a long-term industrial vision, cultivating know-how,
reinforcing skills acquired throughout the years, providing rugged
software and innovating to anticipate user requirements, i.e.
relying on staff to enhance our products. User satisfaction and
renewed trust are the ultimate drive of success.
|
|
NEWS |

TOPKAPI Matrix  |
|
With
the spreading of network interconnections, IT architectures and
user requirements are multiplying, as the information flow must
be mastered, and data must be processed as close as possible to
its source, station deployment managed, and applications enabled
to evolve daily in a simple way, software must flexible.
TOPKAPI
Matrix is the new distributed
architecture concept for TOPKAPI supervision. More
than a new version, it facilitates networked application deployment,
ensuring the stations collaborate more effectively, providing users
with access to information, wherever they are. TOPKAPI Matrix relies
on the traditional components in the range:
|
 |
Servers
which are self-standing, providing easy interchange, or servers
sharing work within a unique application (multistation version
integrating redundancy) |
 |
Netview local or remote
Client stations,
in a fixed or floating license (Open Client, rights allocated
by the server) |
 |
TS
(Terminal Services) client
stations, with rights allocated by the server, for users having
chosen this technology |
 |
Webserv
components providing access to information using Internet
Explorer |
To facilitate application deployment, TOPKAPI Matrix proposes:
|
 |
Installing the Netview
client by downloading
over the Internet (in the Open version, without dongle protection).
The volume of data transferred for the Setup is 6 MB, i.e.
a remote installation time of 1mn40s with ADSL access at 512
kbps |
 |
Optimized
application synchronization:
remote access no longer requires prior global copy of the
application; we transfer initially only what is strictly required,
then only the items requested. TOPKAPI Matrix stores the static
configuration information on the client, and manages a date
and version number for each basic data file. Upon subsequent
access, a client/server exchange defines whether the local
files are up to date and, if required, sends the updates differentially.
Dynamic processing enables full optimization of remote access,
while guaranteeing high level performance in all circumstances
(synoptic screens are refreshed in less than 2 seconds with
modem access)
|
|

 |
Automatic
transfer of logs as background tasks,
of the event type (alarms) and periodical sampling (curves),
enabling within one or several sites: |
| |

|
offline
viewing of the information |
| |
 |
viewing multi-server
alarm views on a station without logging
on |
| |
 |
the log data transfer
to a central site
for consolidation
and archiving |
| |
 |
producing summary
reports using data from several sites without using
complex procedures |
| |
 |
safety by archiving
logs in geographically remote sites |
 |
Transfer
of alarms between different stations,
offering a modular or centralized organization for standby
management, as well as mutualizing hardware resources
of the stations transmitting calls to improve safety |
 |
More
effective multi-server
alarm views |
 |
Automatic
remote server logon with another station to transmit
data |
 |
Centralized
consolidation of summaries using data
sent by several stations. |
Implementation does not require
sophisticated knowledge, installing plug-ins or DCOM exchanges,
writing queries with an obscure syntax, which are all potential
sources of problems during subsequent maintenance operations.
TOPKAPI Matrix relies on a proven Client/Server structure
using simple functions to achieve the objectives sought: making
up one of the major constituents, interactive and effective,
of the global MES and ERP applications
in the company, and facilitating exchanges
with other specialized applications implemented. The example
of the remote control system at Lyonnaise des Eaux presented
later in this document perfectly demonstrates the benefits
this type of architecture can provide.
 |
|
|
|
RECIPES Module 
The RECIPES module in TOPKAPI
has been fully redesigned to facilitate integration into batch
processing applications.
Used to edit unlimited size recipes, it authorizes the use
of embedded sub-recipes
(subcomponents). Recipes are stored on disk and edited in
forms, whether predefined or customized in the TOPKAPI synoptic
interface; linking with controllers is bidirectional, writing
in the controller, or reading controller data for editing
and backup in the form of recipes.
Traceability is ensured by the TOPKAPI report manager. A built-in
Grafcet generator wizard facilitates writing manufacturing
procedures or batch
processing.
|
|