A New Model for SCADA and Measurement Host Systems

carenextΛογισμικό & κατασκευή λογ/κού

18 Νοε 2013 (πριν από 3 χρόνια και 4 μήνες)

56 εμφανίσεις

®

A New Model for
SCADA and
Measurement Hosts

Steve May

CPU LLC

Metairie, LA

www.cpullc.com

ENTELEC Conference 2013

®

SCADA
is an
acronym that stands
for
S
upervisory
C
ontrol
a
nd
D
ata
A
cquisition.

SCADA

®

A
SCADA system host is the
computer system that is used to
gather
data
, view it, and control
certain functions in the system
.

This system can also be used to
Visualize data, perform
Reporting, Well Testing and
other functions.

SCADA System Host:

®

A Measurement system
host is
the
computer system/software
that is used to
gather
measurement (audit) data,
Visualize the data, perform
Reporting and other functions.

Measurement System Host:

®


SCADA


Real
-
time Data/Alarming


Measurement


Historical


SCADA


Control


Measurement


Audit


SCADA


PLC’s, RTU’s, sensors,
etc.


Measurement


EFMs, Totalizers,
etc.

SCADA/Measurement Differences:

®

SCADA System Foundation (Vendor)

SCADA Foundations and
Layers

Data Collection, Protocol Layer

Alarms, History, Scripting Layer

Visualization, Mimics, Trending Layer

Reporting, Well Testing, Allocations Layer

Business Processes and Work
-
Flow Layer

®


Railroads


Utilities

SCADA History

Panels of lights, buttons,
switchs
,
knobs and dials

®

Jubilee Train Line

®

SCADA Hosts
-

1970’s


SCADA System Foundation (Vendor)

Data Collection, Protocol Layer

Alarms, History, Scripting Layer

Visualization, Mimics, Trending Layer

Reporting, Well Testing, Allocations Layer

Business Processes and Work
-
Flow Layer

®

SCADA Hosts
-

1970’s


®

Integration Challenges Then:


Getting the required data


Program Everything


Historians


Daily Production Reports

All you could do!

®

SCADA Hosts
-

1980’s


SCADA System Foundation (Vendor)

Data Collection, Protocol Layer

Alarms, History, Scripting Layer

Visualization, Mimics, Trending Layer

Reporting, Well Testing, Allocations Layer

Business Processes and Work
-
Flow Layer

®

1990’s
-

Yesterday


SCADA System Foundation (Vendor)

Data Collection, Protocol Layer

Alarms, History, Scripting Layer

Visualization, Mimics, Trending Layer

Reporting, Well Testing, Allocations Layer

Business Processes and Work
-
Flow Layer

®

Integration Challenges Then (90’s):


Getting the required data


Program Most things


Integrate Historians


Custom Production Reports


Custom Well Testing

All you could do!

®

Integration Challenges Still Today:


Getting the required data


Custom Production Reports


Custom Allocations


Custom Rollup Reporting


Custom Well Management


Custom Well Testing


®

Integration Challenge Example 1:


Customer had excel
spreadsheet to manually
do Daily

Production
Reports


Wanted to be integrated
into the existing SCADA
System.

Custom Daily Production Reporting 2011
-
2012:

®

Integration Challenge Example 1:

®

Integration Challenge Example 1:

®

Integration Challenge Example 1:

®

Integration Challenge Example 1:

®

Integration Challenge Example 1:


8 man
-
months


(2500 lines of code)


2 other consultants spent 5 man
-
months trying to get the job
completed.


Thus, 13 man
-
months * $150/hour
=
$312,000

That does not include company time!

®

Integration Challenge Example 2:


Offshore Customer needed
Well Testing solution.


Wanted to be integrated
into the existing SCADA
System.

Well Testing 2009
-
2010:

®

Integration Challenge Example 2:


Gather the data from the
SCADA system,


Custom reporting,


Custom
Screens,


Custom PLC
Program.

®

Integration Challenge Example 2:


Gather the data from the
SCADA system


Custom reporting.


Custom Screens


Custom PLC Program

®

Integration Challenge Example 2:


Gather the data from the
SCADA system


Custom reporting.


Custom Screens


Custom PLC Program

®

Integration Challenge Example 2:


3 people


15 month duration


45 man
-
months


Thus, 45 man
-
months * $150/hour
=
$1,080,000

Again, that does not include
company time!

®

Review:


Program data gathering


Program Logic for Daily Production
Report


Program Logic for Well Testing


Program Logic for Allocations


Program Logic for Rollup of
information

®

Today!!!!!!!
-

NEW MODEL


SCADA System Foundation (Vendor)

Data Collection, Protocol Layer

Alarms, History, Scripting Layer

Visualization, Mimics, Trending Layer

Reporting, Well Testing, Allocations Layer

Business Processes and Work
-
Flow Layer

®

New Model


Program Nothing


Configure Everything:

How?!?

®


Intelligent SCADA?


Smart SCADA?


NO!

TM

Relational SCADA
TM
!

®


Object Oriented


Create/Configure Objects


Device


Well


Test Separator


Separator


Tank


Facility


Company


Tag


Each have a relation to another object!


Relational SCADA
TM
:

®


Name


Todays Oil Production


Todays Gas Production


Todays Water Production


Yesterdays…


List of Facilities


Company Object:


Name


Todays Oil Production


Todays Gas Production


Todays Water Production


Yesterdays…


List of Wells


List of Test Separators


Facility Object:

®


Drop Company Object on Report


Assign the list of Facilities to a grid Object in Report


Assign columns of grid to fields in object

Have Rollup of all current Production!

Object Reporting:

Since all Wells are related to Facilities and all
Facilities related to the Company, the rollup of
well oil, gas, and water are automatic. Thus,
the Report is a simple drag
-
and
-
drop of
information on a report and literally only takes
minutes to configure!


®


Drop Company Object on Report


Assign the list of Facilities to a grid Object in Report


Assign columns of grid to fields in object

Have Rollup of all current Production!

Object Reporting:


Name


Todays Oil Production


Todays Gas Production


Todays Water Production


Yesterdays…


List of Wells


List of Test Separators

®

8 man
-
months
vs

1 day
of analysis and
configuration

OR

$312,000
vs

$1,200!


Savings of Object Reporting:

®


Create Well Test Scenario


Create Instance of Well Test


Put in test

Relational SCADA
TM

Well Testing:

All Configuration based on the
relations in the system!

®

(Well A) + (Well B) = Test Separator

Relational SCADA
TM

Well Testing
Scenario:

Drag Well Object instances
from the tree to the Well Test
configuration screen to replace
items in the scenario!

®

Well1 + Well2 =
MainTS

Relational SCADA
TM

Well Test:

Put it in test!

®

45 man
-
months
vs

5
days of analysis and
configuration

OR

$1,080,000
vs

$6,000!

Savings of Relational SCADA Well Testing:

®

Custom
Programming


vs


Configuration!!!

Difference???:

®

New Paradigm means:


Faster results


Better results


Easier to maintain


More Cost Effective


Quicker ROI

Results?:

®

Relational SCADA
TM


TM

Questions??

Steve May

504
-
432
-
7026