Transcript INtools Version 6 - Czech Technical University in Prague

Process, Power and Marine Division
Streamline E&I design schedules
Henk Uiterwijk
09-02-2005
Agenda







SmartPlant Instrumentation
SmartPlant Electrical
Off-Site Projects
AsBuilt / Project environment
Intergration
Benefits
Demonstration
© 2004. Intergraph Corporation. All Rights Reserved.
What is SmartPlant Instrumentation (SPI)?
 SPI is a instrumentation design and
maintenance package.
 SPI is part of the SmartPlant Enterprise.
 SPI is a Client – Server application
 SPI is used world-wide by leading Operating
Owners
© 2004. Intergraph Corporation. All Rights Reserved.
SPI Product Highlights







Supporting Oracle and MS SQL Server
Import/Export data to/from almost any source
Project Environment
Generate documents on-the-fly
Demo
Revision management
Part of SmartPlant Enterprise
Demo
Use of 3rd party suppliers data
© 2004. Intergraph Corporation. All Rights Reserved.
What is SmartPlant Electrical?
An easy and flexible tool for electrical
engineers to design and maintain electrical
power distribution networks.
© 2004. Intergraph Corporation. All Rights Reserved.
What is SmartPlant Electrical?
• Data centric engineering tool
• Creation of consistent data, using reference data,
and conventions.
• Organizing plant / project power consumption
and spare capacity.
• No drawing tool but it creates the main electrical
documents from the database.
• Adding automation and efficiency: Create data
once, use it many times.
© 2004. Intergraph Corporation. All Rights Reserved.
Share data between SPI and SPEL
• Tag Number
• Power Supply
• Wiring Data
• Loop Data
• Panel Data
© 2004. Intergraph Corporation. All Rights Reserved.
 Ability to view and embed SPI loop drawings
in SPEL schematics (and vice versa, ability to
view schematics in SPI)
 Retrieve of PLC card termination data into
Schematics
© 2004. Intergraph Corporation. All Rights Reserved.
© 2004. Intergraph Corporation. All Rights Reserved.
© 2004. Intergraph Corporation. All Rights Reserved.
© 2004. Intergraph Corporation. All Rights Reserved.
© 2004. Intergraph Corporation. All Rights Reserved.
© 2004. Intergraph Corporation. All Rights Reserved.
© 2004. Intergraph Corporation. All Rights Reserved.
© 2004. Intergraph Corporation. All Rights Reserved.
Centralize Databases (Off-Site)
EPC 2
Project A
Country Y
EPC 1
Citrix
Database
Server
EPC 1
Project A
Project B
Country X
Country X
Local
Engineering
Department
© 2004. Intergraph Corporation. All Rights Reserved.
Centralized Database (Off-Site)







Minimize ‘on-site’ employees
No confusion with As-Built data
Consistent Data Entry
No Data Hand-over
Shorter engineering times
Re-use AsBuilt data in a Project.
From Project to Asbuilt < 1 Day
© 2004. Intergraph Corporation. All Rights Reserved.
AsBuilt / Project Environment
Project B
Claimed
data
Project A
AsBuilt Site
© 2004. Intergraph Corporation. All Rights Reserved.
Benefits Project Environment






Check work progress
All parties using same reference data
Correct non-compliancy in early stage
No data hand-over
No document hand-over
Shorter project times
© 2004. Intergraph Corporation. All Rights Reserved.
Why a DCS Interface? – Benefits






Improve engineering performance
Reuse of intellectual investment
Reduce risks throughout the entire plant life cycle
Improved decision support
Automatic generation of project documentation
Single source of information throughout the entire plant life
cycle
SPI providing Validation Rules preventing design mistakes,
such as:

–
–
–
–
incorrect terminal layout including terminal numbering
incorrect channel type for every terminal
Control on naming of different parts to the DCS configuration (e.g.
panel name, nest / rack name, etc.)
Control over other parameters of the card configuration
© 2004. Intergraph Corporation. All Rights Reserved.
When a DCS Interface?

New Greenfield Projects

Exiting Brownfield:
-
Plant Expansion
Plant Revamp / Modification
DCS Upgrade
Plant Upgrade to
Foundation FieldBus
Process Design Changes
Information As-building
Production Changes and
Simulation Re-runs
Etc, Etc,
-
© 2004. Intergraph Corporation. All Rights Reserved.
DCS Current Vendor Alliance status
 Single Direction Interface (SPI >> DeltaV) available since V6.0
Bi-Directional I/F (SPI – DeltaV) dev starting on SPF Adaptors soon...
 Successfully proto-types of AMS – SPI interface using SPI - API
 Bi-Directional I/F (SPI – CS3000) available since V7.0
 Continue improve the interface with tight cooperation with
Yokogawa
 Bi-Directional I/F (SPI – System 800xA) available (V6.0 / V7.0) = PETI
 ABB Catalog Manager available from V7.0.2
 Note - PETI sold only by ABB
 Honeywell standardized on SPI for Global projects
 EPKS Catalog Manager available from V7.0.2
Bidirectional Interface in SPI V8
© 2004. Intergraph Corporation. All Rights Reserved.
The
Interface
Engineering
SP Instrumentation
DeltaV Resources
Configured
Control System
DeltaV System
Select Components
Download Components
DeltaV
Components
SPI
Download DeltaV Configuration Updates (SPI V8.0)
Upload DeltaV Configuration
© 2004. Intergraph Corporation. All Rights Reserved.
DeltaV
Reconcile
File
The CS 3000 Interface
© 2004. Intergraph Corporation. All Rights Reserved.
ROI Sample (1)
© 2004. Intergraph Corporation. All Rights Reserved.
Process, Power and Marine Division
Integrating the
Engineering
Enterprise…