eastman chemical company introduces seiga

Seamless EngineeringInformationGlobal Access

Approved for External Use

Eastman: Who we are

A global specialty chemical company headquartered in Kingsport, Tennessee

Chairman and Chief Executive Officer, Mark Costa

Founded in 1920 in Kingsport, Tennessee by George Eastman

Spun-off from Eastman Kodak in 1994 and became a publicly traded

company

NYSE Symbol: EMN

Approximately 15,000 employees and 50 manufacturing sites around the

globe

Serving customers in approximately 100 countries


Eastman: Who we are

A company dedicated to environmental stewardship, social responsibility &

economic growth

A Responsible Care® company for more than 25 years

2016 ENERGY STAR® Partner of the Year Sustained Excellence

2016 Ethisphere’s World’s Most Ethical® Companies

2016 Glassdoor Employees’ Choice Best Places to Work (# 11)

2015 revenue of $9.6 billion


Our manufacturing locations

5


Eastman is committed to enabling a

safe and secure workplace for our

team members, customers, and

clients.

Our ultimate goal is zero injuries and

process safety incidents worldwide

Safety is personal and everyone is

accountable to work as safely as

possible.

Eastman has a Safety Vision: Because

we CARE, we CHOOSE to ACT so

everyone is SAFE.

ALL IN FOR SAFETY

Each person is ALL IN FOR SAFETY.

Every shift, every day, here and away from work, in all activities


End-market and geographic diversity contribute to growth

2015 sales revenue by end market and geography

Electronics

Energy, Fuels & Water

Other

Food, Feed & Agriculture

Personal Care/Health & Wellness

Industrial Chemicals & Processing

Durable Goods

Tobacco

Consumables

Building & Construction

Transportation

3%

3%

6%

6%

7%

8%

8%

12%

14%

14%

19%

45%

24%

25%

6%


Introduction to Project SEIGA

Purpose

Streamline development and use of engineering data

Commercially available software tools

Innovation

From document-centric engineering deliverables

To data-centric system

Documents still created, but are reports/views of the database; NOT hand-edited files

Payoff

Reduce manual data entry and re-entry


Document-centric Process

Datasheets

Vendors

Datasheets

Conceptual

EngineeringDatasheets

Reliability

Operations

Maintenance

Vendors

Datasheets

Detailed

EngineeringConstruction Check-Out /

Start-Up

Datasheets


https://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&uact=8&ved=0CAcQjRxqFQoTCPnfm4z42sYCFUeKDQodLx4FRw&url=https://en.wikipedia.org/wiki/Arthur_Fry&ei=4CqlVfnvOceUNq-8lLgE&bvm=bv.97653015,d.cWw&psig=AFQjCNFzKEkp0m6WC_UJEEBzA6KNNgRKng&ust=1436974160954459

https://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&uact=8&ved=0CAcQjRxqFQoTCNvOl_iI28YCFcjPgAodGLICtQ&url=https://www.flickr.com/photos/usacehq/6326585126/&ei=ijylVdvhFMifgwSY5IqoCw&bvm=bv.97653015,d.eXY&psig=AFQjCNGu5wHlT4xpZ5eFOnofVwuuQbvCLQ&ust=1436978662091244

Data-centric Process

Asset Engineering Information

Technology Interoperability


Data-centric Engineering

SpSpecs &

Standards

PiP&IDs (smart)

3dPDS

InInstrumentation

ElElectrical

Schematics

MoMotors

PuPumps

MeMechanical Equipment

RdRelief

Devices

Valve:FV-BY-7654


SEIGA Initial Focus Area

Factors influencing that decision include:

Large potential initial benefit• More than an order of magnitude difference between P&ID’s and Instruments

Large quantity of documents that require interchange with vendors

Provides the underlying data structure for other engineering deliverables such as smart P&ID’s

Performance Instrumentation Engineering $ can be measured on large projects

Converting P&ID static cells to smart elements is large up-front effort• Typically drafted by technicians; adding smart info will require a second person (engineer) to

provide technical info (2 sets of hands)


Document-centric Process

Datasheets

Pegasys

Load Sheet

PegasysSAP

Engineering

Construction

Operations

Maintenance

Vendors

• Instrumentation specifications

prepared, usually as individual Excel

files

• Datasheet files sent to the selected

vendors for detailed completion

• When returned, the datasheets have to

be manually evaluated for changes

from original specification• On large projects, this can be very

labor intensive, resulting in data being

manually “handled” multiple times

• Information must then be manually

copied into a master list for Meridium

load

1

2

3

4

1

2

3

4


Data-centric Process

• Commercial-off-the-shelf software

• streamline the development and use of engineering data

• Reduce manual data entry and “handling” during detailed engineering

• Reduce hours/datasheet on capital projects

• Bi-directional data exchange with SAP (Meridium)

• Extensible to Eastman sites worldwide

• Extensible to primary contractors

1

2

3

4

1

3

2

5

4 5


“Can’t we use Excel for instrumentation database?”

Advantages:

• Fairly easy to understand

• Everyone has it on their computer

Disadvantages:

• Only one person can have an Excel file open for write access at a time

• Not easily linkable to other systems

• Does not support versioning of datasheet info

• Use of macros is a malware vector

Even greater concern when files are exchanged with non-Eastman vendors

Common Question . . .


Instrumentation

Engineering

Valve:FV-BY-7654

DatasheetsEquipment

Engineering

3D Model

Loop Diagrams

P&ID

VISIONVision


Short Term

Measurable reduction in engineering hours for instrumentation• Evaluated performance on previous capital projects over several years

• Instrumentation Engineering $ vs. Instrument Material $

• Goal is a measurable % reduction in Instrumentation Engineering $

Bidirectional interface with SAP• Example: New instrument or equipment - Request and receive EquipID from SAP

Mid Term

Mechanical Equipment Datasheets

Brownfield data capture

Generate DCS loop elementaries

Long Term

Expand to other sites

Add other engineering disciplines

Value Capture: What is success?


SEIGA Software DistributionRDC app for AVEVA Instrumentation

Desktop users do not need application directly

installed

Application runs on a terminal server

Contractors access via F5

Application(s) show up in users’ “start menu”

automatically

Pushed by Group Policy Object based on security

group membership

Environment variables for license also set via GPO

Bootcamp curricula developed

Initial training sessions ~ 2 hours


Mobility: RDC app adapted to iPad


Versioning implemented for Templates (Excel file and mapping)

Manual process…this would be a GREAT feature if built-in …

SEIGA Datasheet Template Management


Revision log embedded in each Excel template file

Outside of the print region



Zip file for each template to hold previous versions

“Rollback” files



Report generated with mapping for all templates

Stored with “Rollback” files

Rolling back to previous version difficult (mapping must be done manually),

but is do-able



Vision: pass valve dimension info from AVEVA Instrumentation to E3D

Parametric valve in E3D

Excerpt from valve datasheet (second worksheet tab):



SEIGA Loop Drawings

Wiring rules applicable at tag level

Example: 2 wire transmitter to analog input (field IO)


SEIGA Loop Drawings

Wiring rules applicable at tag level

Example: 2 wire valve positioner to analog output (field IO)


SEIGA Loop Drawings

Field IO Device Types created in Wiring Manager

Example: Analog Input

“Terminals” on the right are placeholder labels for datalinks on seed file


SEIGA Loop Drawings

Instruments AND Field IO grouped into loop

Field IO created similarly to instruments

Initially given same sequence number as loop to aid in

association/grouping; to be changed later


SEIGA Loop Drawings

Field IO grouped into

IO controller

Site – DCS – Bldg

Group – Bldg

hierarchy


SEIGA Loop Drawings

“Loop Wiring Check”


SEIGA Loop Drawings

“Loop Wiring Check” attached to seed file, exported to AutoCAD


SAP Interface

Work progressing with AVEVA and Eastman IT use AVEVA Xchange as

interface to/from SAP

AVEVA Xchange installed on DEV server

ODATA protocol (Web services) used

Successful POST from AVEVA Xchange to SAP using SAP preferred method (token and cookies)

AVEVA created an add-in module for AVEVA Engineering to interface with Xchange

Beta version installed on DEV server (will be part of standard product)


SAP Interface

Instrumentation Engineer

AVEVAEngineering

Creates InitialInstrumentation List in Aveva Using Tag No as Key

IFP Status

Sets Status of Instruments to IFP

• Asset Descriiption• Auth Group• Maint Plant Code• Job No. • PID• Sets User Status• SAP Tag No. • SAP Class• Aveva Last Edit User

Periodic task calling PML to pull tags from AInst to AEng with tag status of either IFP, IFC, or IFR

SAP Software

Trigger Orch

IFP status triggers orchestration to send Equipment ID request to SAP using Xchange: OData protocol to SAP

Creates New EQ Records in SAP and Sends EQ Number back to AVEVA Xchange

Write Back EQ number to Exchange

Updates Aveva with EQ Number assigned in SAP

Master Data Coordintor

Create Report

Generate Orphan EQ Report at Night

MDC installs Into Project FL or Correct Location using Information Provided by Aveva

Has finished filling out nessessary Informaiton is ready for Construction

IFC/IFR Status

Sets Status of Instruments to IFC or IFR

• Pressures• Temps• Materal Specs• Size• Other Attributes• Updates User Status

Sends Attriburte Data and Updates EQ Status

CAll SAP

Updates EQ Record and Sets Status of EQ to "Pre-Installed"

AVEVAXChange

Intiates Call to SAP to Create Assets in SAP

IFC or IFR status triggers orchestration to send asset update to SAP using Xchange: OData protocol to SAP

CAll SAP

Trigger Orch

Intiates Call to SAPUpdate Assets in SAP

Compare/Update (manual) to pull SAP data from AEng

(Manual)


SAP Interface: Orchestration

..


SAP Interface: REST/ODATA Query


Reference Slide Links


Loop Diagrams

iPad

Datasheet Template

Evaluation Debrief

Loop Diagram


3D Model


P&ID


Datasheet import


Instrumentation Engineering


Datasheet


Eastman managed iPad


Revision log embedded in each Excel template file

Outside of the print region



Evaluation Debrief

Instrumentation:

Data exchange with 3D: dimensional data exchange not an out-of-box capability.

Data exchange with AVEVA Engineering: Line data via Excel only (no direct link)

Poor alignment of DSHData.Fieldxx attributes across different datasheet types• Becomes an issue for mapping attributes for transfer to SAP and Meridium

• For example: Tag1.DSHData.Field09

On DSS2020 (differential pressure) it is LP Process Connection

On DSS2021 (orifice plate) it is Density

See screenshots on next page…


Evaluation Debrief

Tag1.DSHData.Field09

• On DSS2020 (differential pressure) it is LP Process Connection

• On DSS2021 (orifice plate) it is Density


Evaluation Debrief

Access Control/Security

• AVEVA Engineering and 3D does NOT use NT security groups

More difficult to manage large user groups, i.e. View-only

When a user changes job functions, they can be more easily removed from an NT security

group than as an individual from multiple software admin packages


? Click here to contact the team

today!

avevaworld.com

@aveva

/aveva

http://www.aveva.com/en/Contact/

http://avevaworld.aveva.com/

https://twitter.com/AVEVAGroup

https://www.linkedin.com/company/aveva