sisco vision interfaces models protocols

1

Systems Integration Specialists Company, Inc.

The Standards Based Integration Company

© Copyright 2006 SISCO, Inc.

Standards Based Power System Integration:

From Simple Protocols to IntelliGrid

Model Driven Integration and SISCO’s Vision for the Adoption of International Standards for Energy Utilities

© Copyright 2006 SISCO, Inc.2

Objective

To provide an overview of the rational for developing and the benefits of using a comprehensive set of standards for model driven integration in the electric utility environment.

2


Definitions:

InteroperabilityInteroperability

The ability of computer systems to exchange information with other systems.


Definitions:

IntegrationIntegrationThe ability of computer based applications to interact with other

systems in order to perform a useful function for the user.

3


Interoperability and Integration

Easy to Achieve:

Nearly anything is possible with enough money and development effort


A Better Way

Interoperability and Integration without having to program it all yourself:

Where applications and devices are inherently capable of interoperating with other systems and performing integrated application functions in a cooperative and distributed manner.

This is only possible if there are standards to enable it.

This work is progressing.

4


Standards are Good!

“Standards are great. Everyone should have one.”

– Bob Metcalfe, Co-inventor of Ethernet

The Right Standards are Needed


A Cautionary Note

“Plug and Play” of applications is a path, not an end point.

By the time we get to were we are going today, someone will have moved the goal.

If you don’t set out on the path, you will never make any progress.

The first on the path will work the hardest and will also reap the most reward.

5


“Obstacles are those frightful things that appear when you take your eyes off your objective.”

- Henry Ford


The Interoperability Dilemma

HUNDREDS OF PROTOCOLS!Meter RTU Recloser Breaker Transformer

Diff.Relay

O.C.Relay SOEMeter RTU Recloser Breaker Transformer

Diff.Relay


Diff.Relay


Diff.Relay


Diff.Relay


Diff.Relay


Diff.Relay

O.C.Relay SOE

HUNDREDS OF SUBSTATIONS!

DMS CIS EMS/SCADA OMS

Too Expensive

6


RTU

Meter RTU Recloser Breaker Transformer Diff.Relay

O.C.Relay SOE

RTU


O.C.Relay SOE

RTU


O.C.Relay SOE

RTU


O.C.Relay SOE

RTU


O.C.Relay SOE

RTU


O.C.Relay SOE

RTU


O.C.Relay SOE

The Interoperability Dilemma



O.C.Relay SOE

RTU

RTURTURTURTURTURTURTURTU

RTURTURTURTURTURTURTURTU

Too Expensive


The Integration Dilemma

RTU


O.C.Relay SOE

RTU


O.C.Relay SOE

RTU


O.C.Relay SOE

RTU


O.C.Relay SOE

RTU


O.C.Relay SOE

RTU


O.C.Relay SOE

RTU


O.C.Relay SOEMeter RTU Recloser Breaker Transformer Diff.

RelayO.C.Relay SOE

RTU


GIS WOM MaintVSAToo Complex

7


Standards are Needed

Standards enable independent developers to reduce the uniqueness of their solutions at the interface points

Traditionally, this meant the protocols to the devices

But, this did not address the integration dilemma for applications (not devices) that did not use “protocols” as the interface

A new level of standardization is needed


Traditional Protocol Standards

Specified how you arrange bytes on the wire in order to transfer bytes of data between a device and an application

Good News: It worked! Device communications costs were lowered.

Bad News: No standard for data representation or how devices should look and behave to network applications.

Some Interoperability but not Integration

8


Typical Legacy Protocol Data Model

Device

I need the Phase A voltage for the 345KV primary feeder

It is in Register 4023!

That’s intuitive?

NO POWER SYSTEM CONTEXT FOR DATA ACCESS


Behavior Modeling

Assume R400220 holds breaker status.Does 1 mean open or closed?Can I write this object to operate the breaker?Where is the select?Is it selected?

Even if every device used R400220 to hold breaker status this still isn’t enough to provide integration.

9


A New Approach Needed

For protocols to provide integration at the system level they need to:

Specify the bytes/format of the data on the wire

Specify the meaning of data

Specify the behavior of the data


IEC61850 – Abstract Models + Protocols

Mapping to MMS Protocol - IEC61850-8-1

Abstract Service Model - IEC61850-7-2

Device Object Models - IEC61850-7-3, 7-4

Device Model Data Objects Data Types Naming Conventions

Communication Stack Profiles

ISO/OSI protocol stack TCP / IP protocol stack

Initiate InfoReport. GetNameList Write VariableList Journals

Associate Reporting Self-Description Control Data Set Logs

10


IEC61850 Overview

IEC61850 is an object oriented substation automation standard that defines:

Standardized names

Standardized meaning of data

Standardized abstract services

Standardized device behavior models

Standardized protocols for:ControlSCADAProtectionTransducers

Self-describing devices

Common configuration language


Benefits of Abstraction and Layering

Abstract models are independent of the protocol and can be used outside of protocol applications

Enables definition beyond just the bytes on the wire to incorporate naming and behavior

Each layer is optimized independently

Enables protocols to be separated from application functions to enable use of existing standards

11


IEC 61850 Data Model

Physical Device(network address)

Logical Device(e.g. Relay1)

MMXU1 MMXU2

MXMX

APhV

Logical Nodes

Functional Constraints

Object Name =MMXU2$MX$A =

Feeder #2 Current Measurements

Network

Measurement Unit

Measurements

Current

Phase to Ground Voltage


IEC 61850 Conventions in Legacy SCADA

SCADA

I need the Phase A voltage for the 345KV primary feeder

MMXU1$MX$PhV$PhsA$cVal$mag$f

That IS intuitive!

POWER SYSTEM CONTEXT IS INHERENTLY VISIBLE

12


Legacy Object Mapping

Legacy data objects and I/O must be manually mapped to power system for each different device, application, and vendor.

Power System Functions

Phase A Voltage

Phase B Voltage

Phase C Voltage

Local/Remote Status

Breaker Position

Blocked Open

Activate Phase A

Activate Phase B

Activate Phase C

Legacy Data Model

Measurements

Controls

Protection

R400040

R400041

R400042

R400043

R400044

R400045

R400046

R400047

R400048

R400049

R40004A

R40004B


IEC 61850 Object Mapping

NO MAPPING NEEDED: IEC61850 objects already portray the power system context.

IEC61850 Device

LD

MMXU1

XCBR1

PIOC1

MX.A.PhsA.cVal.mag.f

MX.A.PhsB.cVal.mag.f

MX.A.PhsC.cVal.mag.f

ST.Loc.stVal

ST.Pos.stVal

ST.BlkOpn.stVal

ST.Op.phsA

ST.Op.phsB

ST.Op.phsC

13


Standardized

Interfacing Protocols to Applications

Application1

Driver 1

Application2

Driver 2

Application3

Driver 3

Application4

Driver 4

Application5

Driver 5Not

Standardized

Standardized Protocol

Interface


Impact of Lack of Interface Standards

Each application developer has to develop drivers for all popular protocols.

Application developers spent considerable resources on drivers instead of applications.

Result:Everybody has to solve the same protocol problems (less interoperability)Have to make application decisions based on protocol functionality (less choice) Less application functionalityHigher application costs

14


Using Protocols: Interface Standards Lower Costs

Application1

Driver

Application2

Driver

Application3

Application4

Application5

Driver


Interface Standards

Enables interoperability for applications and devices with minimal development

Allows more resources to be applied to applications

Enables 3rd party market for drivers and applicationsEnables niche players to exist

All parties have a self-interest in seeing that this works

ResultsMore ChoiceLess WorkLower Costs

WIDESPREAD SUCCESS IN PROCESS AND AUTOMATION INDUSTRIES

15


DDE

Dynamic Data Exchange (DDE) introduced in Windows 3.1

Enabled DDE servers for protocols to be used for any application supporting DDE interface

Created a market for third party communications drivers.


DDE Limits

Designed for linking data between spreadsheets:Resource intensive

Low throughput

No pre-defined structure

Interface was standard, but the configuration and usage was different between drivers and applications.

16


OPC – OLE for Process Control

Based on MS Object Linking and Embedding (OLE) and Component Object Model (COM) technology.

Rigorously defined resource efficient API that provides plug’n play of applications and drivers.

Result: Widespread usage and thousands of off-the-shelf interoperable products available.


OPC Today

Hundreds/Thousands of protocols and applications.Data AccessHistorical Data AccessAlarms and EventsData ExchangeXML MessagingComplex DataCommands

17


OPC Shortcomings

Windows specific. What about Unix used in many EMS/SCADA?

Data was still a collection of items without context The meaning of the data is left to the design of the OPC server

Every OPC server represents the data differently

Applications were still dependent on the data representations of each individual OPC server

A standard representation of data and the relationships between data and the power system are needed


Common Information Model (CIM) is an object-oriented information model of the power system

Central GeneratingStation

Step-Up Transformer

DistributionSubstation

ReceivingStation



Commercial

Industrial Commercial

Gas Turbine

RecipEngine

Cogeneration

RecipEngine

Fuel cell

Micro-turbine

Flywheel

Residential

Photovoltaics

Batteries

UML – Unified Modeling Language

18


Benefits of Models

Models give context and meaning to data improving integration and interoperability.

The information contained in the model enables automation of setup and maintenance tasks.

Model aware applications can be made independent of the data.


Read TSUB23PHA4023Read TSUB23PHB4023Read TSUB23PHC4023Read TSUB24PHA6187

Read TSUB76PHB5865Read TSUB76PHC5865Read TSUB76PHA5977Read TSUB76PHB5977Read TSUB76PHC5977

.

.

.

.

.

Read All Transformer Voltages

Other algorithms possible. But,

regardless of algorithm, programs must contain hard coded references

to either names or tables to access.

Data Dependent Application

19


CIM as a topic tree

Everything needed to access data is contained in

the modelNorth Area

Airport Substation Main

Substation

Breakers Loads Breakers TransformersTransformers

TC57 Physical Model

Company X


Data Independent ApplicationRead All Transformer Voltages

Find Next Substation

Find NextTransformer

Find NextVoltage

Read

Every name defined in the model

20


Legacy Data Model – Data is Referenced by TagSCADA

I need the primary current of the 345KV transformer in the airport substation


How do users find this today?

With lots of paper documentation and manual maintenance effort subject to manual error detection

and correction.

21


CIM View Of SCADA Data

ClientHierarchy changes with network model changes

SCADA

Device or other system related views

supported

Access by Description

Bus

XFMR XFMR XFMR XFMR

Bus

Substation


CIM – IEC61970 & IEC61968

Originally developed by EPRI’s Control Center API (CCAPI) Workshop.

Now progressing as IEC standards in Technical Committee 57, Working Groups 13 and 14.

IEC61970Power System Modeling & SCADA

IEC61968Asset Mgmt, Billing, GIS, Work Mgmt, etc.

22


CIM and IEC61850

CIM has power system, asset, business process, work management models.

IEC61850 has device models

How do they fit?


IEC 61850 Substation Automation and CIMThe power system models of CIM and device models of IEC61850 intersect at the fundamental driver for most operational energy applications in the control center: MEASUREMENTS

IEC61970/68CIM

IEC61850

Power

System

Models

Device

Models

Measurements

23


The Next Step: Interfaces and Models – GID

With CIM, programs still need an interface/service method for accessing both the data and the model information about the data (meta-data)

As with protocols, without standardized interfaces you can’t achieve interoperability using off-the-shelf products

Interface standards are needed for a robust third party market

EPRI CCAPI project submitted the Generic Interface Definition (GID) to the IEC WG13 for standardization in IEC61970.


IEC 61970 and IEC 61968: Standards for Integration

Provide a common agreement on What data is exchangedThe Common Information Model (CIM)

Provide a common agreement on Services to exchange the dataThe Generic Interface Definition (GID)

The benefits of using CIM and GID:Access to the vendors, applications, sensors, and the general plant environment that can be connected via off-the-shelf adapters.Adapters can be fed with data from hundreds of devices and applications with little or no investment or development. Object model abstractions organize the data and give structure to the service actions that are invoked from business applications to provide the consistent integration method needed to build off-the-shelf adapters. Adaptor approach follows industry standards.

24


GID provides standardized interface services

GID interfaces reference all data in the context of a common data exchange model, the CIM.

GID Services:Generic Data Access (GDA): For model management and distribution of updates.High-Speed Data Access (HSDA): For access to real-time measurement data.Time Series Data Access (TSDA): For access to historical measurement data.Generic Events and Subscriptions (GES): For pub/sub of generic XML messages.

GID is based on existing open standards for both energy and industrial:Object Management Group (OMG): Data Access for Industrial Systems, Data Access Facility.OLE for Process Control (OPC): Data Access, Historical Data Access, Alarms & Events.


GID is based on existing widely used standards

OPC Foundation (http://www.opcfoundation.org) developed application programming interfaces to enable plug and play of applications and drivers called OLE for Process Control (OPC).

OPC Foundation: 362 member companies (end users and OEMs)Supported by 1500+ companies and 7500+ products

OPC is dominant in the industrial automation and process controlindustries providing connectivity to hundreds of key applications.

GID is a platform independent version of OPC supporting model driven services capable of being used on any computing platform.

25


GID and OPC

GID is platform independent AND model-driven:OPC uses vendor determined namespace for data

GID uses a namespace derived from the CIM for all data

AEAlarms & Events

GESGeneric Eventing and Subscriptions

UA QueryUnified Architecture

GDAGeneric Data Access

HDAHistorical Data Access

TSDATime Series Data Access

DAData Access

HSDAHigh Speed Data Access

OPCGID Service


IEC TC57 Standards

The IEC Technical Committee 57 standards are specifying a model driven architecture for electric utility integration

Protocols - Messages

Models

Interfaces and Services

A common approach across industries

26


ISA S.95 – IEC62264

An ISA standard for the interface between automation and production control.

Addresses both discrete and continuous process industries.

Specifies models and terminology for production orders, scheduling, planning, etc.


CIM vs. S.95

ConductingEquipment(from Core)

Equipment(from Core)

PowerSystemResource(from Core)

RegulationSchedule

TapChanger

0.. 1

0.. n

+RegulationSchedule0.. 1

+ TapChan gers

0.. n

W indingTest

HeatExchanger

Tran sformerW inding

0..n

1

+TapChangers

0..n

+TransformerW inding

1

1

0..n

+From_TransformerW inding1

+ From_W indingTest s0..n1

0..n

+To_W indingTest1

+To_TransformeW indings0..n

PowerTransformer

0..1

1

+HeatExchanger 0..1

+PowerTransformer 1

1..n

1

+ Cont ains _TransformerW indin gs

1..n

+MemberOf_PowerTransformer

1

MaintenanceRequest

MaintenanceRequest

MaintenanceWork Order

MaintenanceWork Order

MaintenanceResponse

MaintenanceResponse

May be generated for0..n

1..1

1..1

1..1

EquipmentClass Property

EquipmentClass Property

EquipmentProperty

EquipmentProperty

EquipmentCapability TestSpecification

EquipmentCapability TestSpecification

EquipmentClass

EquipmentClass

Hasvalues for

0..n

0..n

0..n

0..n

0..n

EquipmentEquipment

EquipmentCapability Test

Result

EquipmentCapability Test

Result

0..n

0..n1..n

Hasproperties

of

Is testedby a

Maps to

Defined by

Records theexecution of

0..n

0..n May result in

0..1

May be up of Is against

Is madeagainst

0..n

0..n

Def ines aprocedure forobtaining a

CIM

S.95

27


Impact of Being Model Neutral

Increased data independence.

Enables user specific customizations without affecting coding

Enables application of adapters across industries increasing 3rd party interest in supporting product based adapters.

LOWERS THE COST OF USING TECHNOLOGY


Impact of Self Description

Applications obtain the description of the data from the source of the data.

Eliminates a great deal of configuration and errors.

Improves understanding of data

Increases independence of applications from the sources of data


28


Impact of Model Awareness

Applications and users can see the meaning of data and its relationship to other data.

Allows configuration in the context of the power system.

Avoids arcane proprietary tag naming conventions.

Allows model changes to be propagated automatically



Impact of Application Independence

Application can be independent of the data required by finding what is needed in the model automatically.

No need to preconfigure each instance of data to be operated on.

Enables reusability of applications without configuration.


29


Impact of Leveraging Existing Technology

The layered approach enables utility specific functions to be added to existing generic technology that is in widespread use.

Minimizes the utility specific technology (lower volume) required.





What About Web Services?

30


What are Web Services?

A structured integration architecture using eXtensible Markup Language (XML) messaging over a network architecture using the world-wide web (WWW)

Web Services:Can reuse existing network infrastructure used by the WWW (Internet, Intranet)

Allows a client to discover the services and data supported by a server.

Defined by the World Wide Web Consortium: http://www.w3c.org

Uses a standard framework for integration development using widely deployed tools (Java (etc.), .Net, etc.)


Web Services is Based on the WWW

URL HTML HTTP

UDDI WSDL SOAP

Web Services

World Wide Web

World Wide Web (WWW)

Uniform Resource Identifiers (URI) or locator (URL)

Hyper-Text Markup Language (HTML) and the eXtensible Markup Language (XML)

Hyper-Text Transport Protocol (HTTP)

Web Services

Universal Description, Discovery, and Integration (UDDI)

Web Services Description Language (WSDL) using XML

Simple Object Access Protocol (SOAP)

31


Web Services Architecture


Service-Oriented Architecture (SOA)

A service-oriented architecture (SOA) is an application framework that takes applications and breaks them down into individual business functions and processes, called services.

Services are the building blocks of an SOA. A service can be a business function, such as find the location of an asset, or determine a voltage level at a certain time, or a system capability such as authenticate user. SOAs enable “packaging” business functions from new and existing applications in a simple and standardized way.An SOA increases flexibility by treating elements of business processes and the underlying IT infrastructure as secure, standardized components (services) that can be reused and combined to address changing business priorities.

Can’t maximize the value of an SOA without open standards.

32


Generic Web Service Integration

SCADA

Asset/WorkManagement

EMS/DMS/GIS

DataWarehouse

CMS

Portal N*(N-1) Different client/server service

combinations requiring coding

Typically no agreement on common messages, models, services, etc.


Flexible connectivity infrastructure for integrating applications and services to power SOA

CONVERTING transport protocols between requestor and service

ROUTING messages between services

TRANSFORMING message format between requestor and service

HANDLING business events from disparate sources

What is an Enterprise Service Bus (ESB)?

33


Components Connect To An ESB Using Web Services

SCADA

Asset/WorkManagement

EMS/DMS/GIS

Data Warehouse

CMSPortal

Enterprise Service Bus

Web Services Web Services Web Services

Web Services Web Services Web Services

Application wrappers


SOA using ad-hoc web services with an ESB

Significant benefits due to use of standards:SOAP – HTTP for transport

WSDL to describe the services and messages supported

Ad-hoc because each application specifies its own servicesEach service provider independently defines their own services (WSDL)

Each client needing to access a service must discover and adapt to each unique web service provider.

Application integration still requires significant programming effort unique to:The specific application functions involvedThe developer/brand of the applications

Result: integration is customized and unique to each and every system

34


What are Web Services?A structured integration architecture using XML messaging over a similar network architecture as the world-wide web (WWW)

Web Services:Can reuse existing network infrastructure used by the WWW (Internet, Intranet)

Allows a client to discover the services and data supported by a server.

Defined by the World Wide Web Consortium: http://www.w3c.org

Uses a standard framework for integration development using widely deployed tools (Java (etc.), .Net, etc.)

Web Services Do Not Interpret and understand tags, values, or descriptions semantically (no standardized model)Automatically connect services unless identical models are usedDefine standardized services – only a standardize method of discovering, invoking, and managing services


Remember This? Same Problem….But BIGGER

Standardized

Application1

Driver 1

Application2

Driver 2

Application3

Driver 3

Application4

Driver 4

Application5

Driver 5Not

Standardized

Standardized Protocol

Interface

35


CIM and GID - Enable More Interoperability in a Web Services Environment

Provide a common agreement on WHAT data is exchangedThe Common Information Model (CIM)

Standardized Data and Message Types

Provide a common agreement on HOW to exchange the dataThe Generic Interface Definition (GID)

Standardized Services to Exchange Data and Messages


GID provides standardized interfaces and services

GID Interfaces:

Generic Data Access (GDA): For model management and distribution of updates.

High-Speed Data Access (HSDA): For access to real-time measurement data.

Time Series Data Access (TSDA): For access to historical measurement data.

Generic Events and Subscriptions (GES): For pub/sub of generic XML messages including IEC61968 (WG14) Messages

Interfaces are translated into services via WSDL for each GID interface in the IEC61970-40X specifications

Results in GID as standardized web services

36




Applying these concepts to utilities:


Control Center Databases

Documents, E-mail, Generic

Files Gateways to Customer

Sites

Control Center Systems and ApplicationsSubstation

Data Concentrators and Masters

IntraNet and Internet Access

Energy Market and

eCommerce Applications

Multitude of Legacy

Applications and Systems

IT Networking and Computer

Systems

Legacy Approach: Ad Hoc Proprietary Links: Expensive

RTUs, IEDs, and Other

Field Devices

37


“Verbs” include: request, send, query, authenticate, publish, subscribe …

Common Services/Protocols

Information Object Models

“Nouns” includes: power system data, application data, network management

data, security data …

Control Center Databases

Documents, E-mail, Generic Files

RTUs, IEDs, and Other Field

Devices

Gateways to Customer Sites

Control Center Systems and Applications

Substation Data Concentrators and

Masters

IntraNet and Internet Access

Energy Market and eCommerce

Applications

Multitude of Legacy Applications and

Systems

IT Networking and Computer Systems

Model Driven Integration Addresses: Cost, Efficiency, and Complexity

IntelliGrid Architecture http://www.intelligrid.info


Abstract Model of the IntelliGrid ArchitectureIndustry Requirements → Engineering Principles → Framework for Implementation

Use Cases

38


Abstract Model of the IntelliGrid ArchitectureIndustry Requirements → Engineering Principles → Framework for Implementation

Use CasesIEC

TC57Standards


Strategic Vision

Abstract ModelingObject and Information ModelsAbstract Service and Interface ModelsSelf Description and DiscoveryTechnology Independent Design

Security ManagementPrinciple driver for applying architecture principles across the industry

Network and System ManagementCritical for management of the “dual” nature of utility networks

Data ManagementAvoid “Garbage In” to eliminate “Garbage Out”

Integration and InteroperabilityAn appropriate set of standards to meet the business requirements

39


Utility Enterprise


IntelliGrid Environments

40


How to Use IntelliGrid




Projects

41


PowerPool

Sample Project 1

SISCO Utility Integration Bus (UIB) and IBM WebSphere MQ

ODMSGDA

GDA

Power System Models

PSS/O

PSS/E

GDA

GDA

HSDA

HSDA

TSDA

TSDA

EMS

UIB-ICCPGateway (Red.)

CIMXML

UIB-ICCPGateway(Redundant)

HSDA

HSDA

ICCP-TASE.2

ICCP-TASE.2 Adapter

ExistingHome-Grown

Historian

GID

HSDA

HSDA

To BeDone

byUser

GDA

GDA

GDA

GDA


CIM/GIDData

Warehouse

Maximo

GDA TSDA

AnalysisApplications

EquipmentModels

UIB

GDA

PowerModels

TOTS

MMW

GDA

GDA

GDA

Event Logand Others

GDA

.

.

.TSDA

ODBCODBC

Legacy Databases wrapped using

Database Server Adapter

EPRI Project with SISCO

42


UIB PI Adapter

ModuleDatabase

CIM

ArchiveGDA TSDA HSDA

GDA TSDA HSDA

ICC

P

UIB

PowerModels PI

EMSPTI’s ODMS

GDA Server

GDA

Power SystemModels

PSS/E

PSS/OTSDA

TSDA

GDA

GDA

HSDA

HSDA

EPRI Project with Siemens


EquipmentModels

CIM-GIDData

Warehouse

EMS

GDA

AnalysisApplications

ICC

P

ODMSGDA Server

GDA

Power SystemModels

UIB

GDA

PowerModels

MMW

GD

A

ODBC

ODBC

PSS/O

PSS/E

GDA

GDA

EPRIPTLoad/DTCR

Maximo

TOTS

Others

.

.

.

GDA TSDAGES GES

Equip & power

Results

GDA TSDAGES

GDA

GDA

GDA

Desktop

GES

Results

ModuleDatabase

CIM

PowerModels

HSDA

HSDA

TSDA

UIB PI Adapter

GDA TSDA HSDA

GDA TSDA HSDA

TSDA

TSDA

TSDA

Archive

PI

EPRI Project Overall Architecture

43




How Do You Make This Work In Your Enterprise?

Business Justification


The Justification Dilemma

COSTSBENEFITS

44



Engineer’s View of Justification

COSTS

BENEFITS



Accountant’s View of Justification

COSTS

BENEFITS

45


The Tragedy of Automation

There are no benefitswithout some cost


About Benefits & JustificationIdentify all the benefits (obvious).

ALSO Identify ALL the costs:EquipmentInstallationEngineeringCommissioningUtilization CostsImpact on External SystemsCosts to Change/Migrate in FutureIntangibles (new capability)

Requires a complete view of cost.

Requires a longer time frame.

46


The benefit of using technology is not in the

purchase.

The benefit is in using technology to improve operations AFTER the

purchase.


Model-Driven Cost Justification

Cos

t

TimePurchase

Payback

BENEFITTraditional

Approaches

ModelDriven

Approaches

47


Value of IntelliGrid

Use Cases are extremely valuable in understanding cost issues over time.

IntelliGrid has a number of use cases that can be used to compare approaches to make justifications even accountants can understand.


“Obstacles are those frightful things that appear when you take your eyes off your objective.”

- Henry Ford

48




Thank You

Ralph MackiewiczSISCO, Inc.6605 19½ Mile RoadSterling Heights, MI 48314-1408 USATel: +1-586-254-0020 x103Fax: +1-586-254-0053Email: [email protected]