smartplant instrumentation product roadmap

SmartPlant Instrumentation Product Roadmap

Alex Koifman

SPI Product Manager

October 7, 2009

SmartPlant Instrumentation Product Roadmap AgendaIndustry and product challengesv.2007 - Meeting project execution and plant challengesv.2009 - Quality and integrationV.2012 - Taking on engineering and integrationMajor initiatives under considerationExternal validation and calculation mechanism

2

Industry and product challengesPrior to summer 2008 – unprecedented industry boom followed by the energy business contractionSmartPlant Enterprise uptake is shifting customer and Intergraphfocus from individual design tool functionality to integrated workflowsCost structure and savings drive project and operating facilities IT strategies in opposite directions affecting upgrades; operating facilities cycle is extending to 3 to 5 years per version, encouraging companies to leap-frog versions.SPI product strategy is to find the balance between short term business objectives and long term initiatives

3

2007 – Where are weMajor release

Broadly used by the new customers and for many new projectsMost deployments in Europe, Asia and South America

Service packs SP7 is planned for H1 2010 as a combination of HF’s from SP6

Hot fixesReleased on scheduled as needed basis every few weeksLatest HF’s available on eCustomer Web page

Pre v.2007Last v.7 service pack in H1 2010 – a round up of the hot fixes.

4

2007 – Productivity enhancements in progressFew of the functional enhancements in v.2007 SP’s include:

Bi-directional Emerson Delta V interface, change tag classes between Fieldbus and conventional, Support Office 2007, support AutoCAD 2007 and 2008, Fieldbus data on Profibus PA, replace third-party PDF generation tools with internal library, support Vista OS, many enhancements to Calibration module and Fluke calibration interface, default browser view persistence, typical tags support Fieldbus and soft tags, reduce calls to .INI file, updated documentation delivered in each SP, Panel-Strip as multi-strip reports, cross-form browsers and so on.

Integration enhancements in v.2007 SP’s include:View file format selection; DDP for SP3D: units of measure for dimensions, status and library extension, improved ToDoList, etc.

5

2009 – Reliability, integration, operationsReliability: Focus on improving initial release quality, upgrade, comparative performance testingIntegration: Working on Inter-Company Collaboration (ICC), extending ability to publish SPI data to SPF and on to other tools Operations: Streamlining and complementing As Build (O/O) domain operationsContent: New instrument specification library with 90+ formsContinued process: Expect continued enhancements also within 2009 releasePlanned release date: End of October 2009

6

2009 – Release quality effortQuality focus

None or minimal regression vs. previous versionNew functionality working correctlyRelease postponed to maintain quality

UpgradeIntergraph’s commitment to support direct upgrade from late v.7 SP’s to v.2009 bypassing v.2007Testing upgrade process on multiple customer databasesTesting post-upgrade operations

7

2009 – Release quality effortPerformance testing

Retesting all macros post drawing generation transition to the Data DictionaryBeta testing: Intergraph offices and few select customers (will start soon)

8

Example of the performance / memory testing of v.2007 SP6 vs. 2009

2009 – Integration and collaborationContinued work on Inter-Company Collaboration (ICC) extending engineering project execution from connected (Citrix) to disconnected work-share – brownfield projects, sub-contractors to main EPC’s, converting from EPC to engineering project, etc.; Certain workflows will be supported in v.2009 and 2009 SP’sExtending SPI data available for publish from Browsers – OOTB and custom browsers data will be available for publish, will require proper mapping on both sides.Filtering of the scope of published data will allow better control of what data gets published

9

2009 – Filtering of the published index scope

10

2009 – New FeaturesAs Built

Allow merge from projects into the As Built without requirement for exclusive database access As Built certification additional priority focusRoll-up of the v.7 and v.2007 changes into v.2009

Adding contentNew complimentary specification library in addition to existing specificationsWill also be available in v.2007

External validation and calculations and moreImportant: SPI v.2009 will use SPLM v2010

11

2009 – Continuous enhancementsIntegration

Extend SPI electrical equipment model for improved workflowsEnhance adapter to handle relief valve line association logicMake obtaining revision from SPF optionalEnable publish/retrieve of SPPID ControlSystemFunction to soft tag

ReportingESL Custom mode: updating symbols, improve default arrangement, split strip, alternative terminal sequencing, automated off-page connector reference to other loopsScaling ESL generated drawings for output(in v.2009) Add CAD macro functions and extend them to ESL generation

12

2009 – Continuous enhancementsComposite specifications

Allow creating multiple specifications for a single tag - both single specifications and composite specifications – and possibly different spec forms for different P.D. casesAPI to support composite specifications for access by SPEx and external applications

Vendor integration and extending contentRe-work NE100 interface (NE-100 will not be available in v.2009 initial release)Extend DDP content – groups with the maintenance aspect

Domain ExplorerAdd unit level cable and panel folders (also in v.2007)

13

2009 – Continuous enhancements - continuedAdditional enhancements

Improve loop layout assignment access rights managementReplace old symbol browser with the new to resolve symbol drag-and-drop save problemsSupport cross-plant wiringEach Hot Fix will be a full Setup directly applicable on the RTMProvide command for disabling and enabling user login to domainsAdditional UOM’s including specific for nuclear industry..and there will be more including continuous quality improvement effort.

14

2012 – Infrastructure, engineering and collaborationInfrastructure

New platforms support (MSS2008, Oracle 11)Complete transition to the Data DictionaryAccess rights management overhaul

Engineering functionalityCalculations (ISO 5167-2003), make process datasheets customizable

IntegrationProject execution and collaboration through ICC enhancementsAttending the needs of pharmaceuticals, power (especially nuclear), mining and metals industries

15

SPI Major initiatives under considerationAddressing common I&E tasksSupporting wireless technologyUsing SmartPlant Engineering Manager (SPEM)Extending KKS support – update shipped codes and make them editableNavigation between schematic applicationsFurther enhancing DCS integration Integration: Smarter and more flexible integration of SP PID data without additionally burdening P&ID design group, macro expansion and aligning instrument types across schematic applications.

16

Wiring:-Panel,

Cables, Connections,

I/O

I&E CableManagement

system

SLD

Enhanced reports / Loops

Schematics

SPF/SBISP3D

Auto routing

P2P

Control System vendors

Common E&I wiring Module; SPEL launches SPI wiring Module for electrical wiring tasks

Use SPEL Cable management for E&I cables

Applications maintain their autonomy and appearance/flavor

E&I Wiring/Cable Management

SPI DB

SPEL DB

Cables

Publish/retrieve

Supporting wireless technologyThe technology is here:

WirelessHART approved September 2007 as extension of HARTISA100.11a approved on April 29,2009

Projects are coming and interest is shown by EPC’s and ownersSPI need to support design toolsPhased approach likely

Identification of wireless capability (Instrument Index)Specifying wireless device for procurement (Specifications)Providing construction documents (Hook-ups, wiring and loops (?))Managing wireless configuration documentation – run time systems or plant design systems?

18

SPI Major initiatives under consideration - continuedImprove tag class change management Browser WizardDevelop Safety Instrument System (SIS) supportContinued Fluke automated calibrators enhancementsIntegration with the SP Construction

19

External validation and calculations

20

21

External functions – what is it

21

We want to open the application to allow SPI customers to add additional validation and functionality on top of what SPI provide OOTB, similar to the validation in SPPID.

Use Rule Engine mechanism where rules are used to define what type of functionality is required and on what item type and properly to trigger it

Customer will write code to implement this external function

21

22

External functions – Validation

22

To best understand where can this new feature be used and how to implement it, let take two examples• Validation: Validate that the Item tag

of the loop is unique not just in the current unit between all the loop tags, but in the entire plan and also within the Cables and Panels’ item tags

22

23


23

Add a new rule

23

24


24

24

Assign it to a loop

25


25

Select from drop down

Set by the system by default

Set by the system by default

Set the name of the project and class

25

Set the details of the external function

26


26

Write the relevant C# or VB.NET

This is the validation project

and class

26

27


27

This is the validation class

27

28


28

• The Validation external function will return True or False

• When the user enter or modify loop name that violate the code that specified in the external code, a message will pop with the text that described in the external function

28

29

External functions – Calculation

29

Similar and in addition to the Validation, the calculation allow not just validate value, but also change properties of the item in SPIFor example return value calculated by the external application (sizing results, validation, SIL rating, etc)

29

30


30

Set the details of the external function. Select Custom Calculation from the drop down

Custom calculation selection

This is the property that will be updated.

Can be multiple properties

30

31


31

• The Calculation external function will return value to all the properties that set in the rule

• User story: Because our company’s document management is centrally managed, we need to obtain drawing number for all engineering documents from external application such as SPF. The External function will call the other application and with the other application UI, or without it, will get the relevant drawing number back to the SPI system

31

When the user try to enter a loop for example, the external function call the other application that launches its own UI

Then the value is returned to SPI and stored in the database


32

33

External functions – General

33

• The external function allow only selects from the DB, do not allow modifying data other then through the properties that define in the Rule

• The External function allow initiating other applications even with their UI

33

The error text is been provided to the rule engine by the external function

Two external properties that are been used to return the error code and error

text back to SPI rule engine

External functions – Customizing error codes

34

Additional Telecom Enhanced Reports

35

• Closed Circuit TV Diagram• Radio System Diagram• Public Address Radial Topography• Public Address Ring Topography• Telecom Cable & Building Diagram

Intergraph Process, Power & Marine

The Future of Engineering –Today

smartplant instrumentation product roadmap

Documents