Welcome to Techneaux Welcome to Techneaux

• Casual Conversation • Katie says, “Make it great!” • About Techneaux • What is SCADA • What about Enterprise Services • Excuse the Technical Gobbledygook Start Up Oil and Gas Company X Lessons Learned Kick-off September 2018

• Timeline • Go Live March 1st, 2019 • Scope • Migrate multiple CygNet Sites to a new Ignition SCADA System with a polling engine yet to be determined and make it look/work like the CygNet system. • Team Members • Shannon • Chris • Philip • Cathy • Budget • TBD

That’s not a lot of words… About that scope… Ignition Plus…

Autosol Kepware CPU ACM Software Cost - + + Integration Cost + - + Tools and Utilities + - + Real Time Polling + ++ + Minute History Collection + + + Measurement Collection + + + Flow-Cal Support ++ + - Flow-Cal to Meter GQ + - - Support + + OPC Client Interface - + + System and Comm Statistics + Oil and Gas Focus + + ++ Known Ignition + + Implementations API + + Maturity in the Market + + Customizable - - + Timeline - Plan Timeline - Actual Project Plan 3/1/2019 9/10/2018 3/19/2019 GO LIVE! Kick Off Project complete

9/10 - 10/3 10/3 - 11/1 11/1 - 1/20 1/20 - 2/27 3/5 - 3/19 Discovery Design Implimentation Testing Support

10/1/2018 11/1/2018 12/1/2018 1/1/2019 2/1/2019 3/1/2019 9/10/2018 3/19/2019

2/27 - 3/5 Go Live

Project Timeline Title 9/10/2018 11/4/2018 6/30/2019 Kick Off Applications Chosen Project complete 12/1 - 5/2 Implimentation

9/10 - 10/17 10/17 - 12/1 2/2 - 3/1 3/1 - 3/16 5/2 - 6/30 Discovery Design Testing Go Live Support / Transfer

10/1/2018 11/1/2018 12/1/2018 1/1/2019 2/1/2019 3/1/2019 4/1/2019 5/1/2019 6/1/2019 9/10/2018 6/30/2019

10/17/2018 11/30/2018 1/18/2019 3/1/2019 4/2/2019 On Site Discovery Servers Available Crash GO LIVE! Measurement

Timeline - Comparison How did we get this done?

• Design? • Applications? • Team? • Customer? • Scale? • BUDGET?!?!? Budget? LOL

Crash • Spending more money to get something done more quickly is called crashing Team Member Count

Crash Scope Change Project Changes

• Timeline • Go LiveLive MarchMarch 1 1stst, ,2019 2019 with Operational Data April 1st with Measurement • Scope • Migrate multiplemultiple CygNet CygNet Sites Sites to to an a Azure new Ignitionvirtualized SCADA environment System with hosting a polling an engineIgnition yetSCADA to beSystem determined with Kepware and make Polling/Measurement it look/work like collection the CygNet featuring system. Bont Gas Quality Writeback from FlowCal CFX and Transaction Queue collection • Teamand Members Develop Production Manager 3 and 4 . Include allowances for Cirrus Link • ShannonPolling via MQTT for ROC minute history. • Team• Chris Members • PhilipShannon, Chris, Philip, Cathy, AJ, Alainia, Brandon, Byron, David C, Dustin, • CathyElizabeth, Forrest, Jakob, Katie, Matt, Rilee, and Ross. Honorable Mention Cody • Budget • Established Budget/Spend per Day. We came in about 10% under budget total, • withinTBD 5% at Go Live So About those Lessons Learned

• Key areas: • Requirements Gathering • Design • Implementation • Testing • Go Live • Customer Requirements Gathering

Item Success Area of Improvement Phase Requirements Gathering Risks

SizeFeatures of and system Risk Identification and needs of highly Size of system and needs of highly technical Company X team exposed skill technical Company X team exposedgaps in Ignition/Customer X Data Consolidation Going from a known good (CygNet) Progress Tracking with hard targets

skillGoals gapsand Objectives in Ignition/Company X Scope was not well defined and caused success of project hard to define Constraints

Data Gathering Data Provided by Company A Design

Item Success Area of Improvement Phase Should have scheduled recurring meetings Design Environment Design Should have scheduled recurring meetings with Ignition and Kepware with Ignition and Kepware throughoutthroughout development process. Customer unaware of impact to system from changes to Fac development process. Significant exclusions of data without full discussion with team Polling Methodology

Customer3rd Party Applications unawareand Dependencies of impact to system fromReporting changes to Fac Table Data Model Design

Design Analysis Templated tag structure became Significant exclusions of data withoutunnecessarily full deep and confusing. discussionSolution Selection with team Screen Design Developed set of screens near identical to Needed more validation of screen preexisting CygNet screens. element functionality. Implementation

Item Success Area of Improvement Phase Implementation Data Model Translation Development of Cygnet to Whatever

Software Installation Software installed on Company X servers one month before go live despite a 4 month project window proposal

Device Creation Development of KACI

Tags/Points Better understanding of tag providers and their load on Ignition gateway Server / Envionment Sufficient server balancing of Ignition gateways SQL installation needs separate server Multiple Kepware server instances needed

Screens Acquired PM4 screens from (ROC people)

Calculated Data

Hierarchies

Notifications Well developed alarm pipeline tied to distro groups for easy management Measurement Needed to create a more automated process for resetting the data cache on EFM collection

Reporting Need better knowledge/experience in reporting module since reports were created by Sponsor in PowerBI

Controls/Optimization

Security Integrated Ignition authentication with Company X AD.

3rd Party Applications and Dependencies

Scheduled Tasks

Historian Need a better understanding of SQL to administer that application and it's effects on

Polling Patching Kepware servers on the fly without a clear method to revert the patch Mass demand polling was done manually despite a clear need to develop an automated process. Implementation

Item Success Area of Improvement Phase SQL installation needs separate server Implementation Server / Environment Sufficient server balancing of SQL installation needs separate Multiple Kepware serverIgnition gatewaysinstances server Multiple Kepware server needed instances needed Polling Patching Kepware servers on the fly without a clear method to Patching Kepware servers on the fly revert the patch without a clear method to revert the patch Testing- Technical

Item Success Area of Improvement Phase Testing Data Refresh

Reporting / Interfaces

Communications Testing

Poll Testing Insufficient testing due to incomplete Kepware builds for first half of poll testing window (30days). Screen Testing

Security Testing

Notification Testing Did not research the limits of messages- per-minute for SMTP. Interface Testing

Client Testing

Dual Polling / Data Validation Go Live - Technical

Item Success Area of Improvement Phase Go Live Go Live Having Ignition SMEs on site for go live and training during the final week before cutover. Cut down on development and deployment speed. Constant changes to Kepware data without adequate notification to team members Bont FlowCal - Measurement Custom Screens History Load Plunger Data - Temp Plunger utility tool to identify and create missing tags. Push Time Sync PM3 Suite Working diligently with field operators to ensure full functionality of controls & optimization.

PM4 Suite Notification Testing Notifications were not put in place until the night of go-live.

Troubleshooting Familiarity with specific Ignition Support members Failure to follow-up with Kepware support cases in resulted in more efficient troubleshooting. a timely manner throughout the early phases of the project. Lack of knowledge & understanding of software and underlying issues led to wasted efforts, especially in identifying the problem system. Customer

CompanyItem X team runningSuccess wild and freeArea of Improvement Phase Customer inRelationship the system Management while attemptingEstablished rapport towith Gas Company X team running wild Control. and free in the system while establish stability. attempting to establish stability. Project sponsor unwilling to accept concerns regarding a no- Project sponsor unwilling to accept go call concerns regarding a no-go call The Techneaux Mission Statement?

• Did we make the customer successful?

• Did we make our team members successful?

• Did we make Techneaux successful? What value did we get out of this?

• Ignition • CPU • Kepware • ACM • Bont • Production Manager (Ign) • FlowCal (CSF/TQ) • Amine Plants • FCC Licensing • KACI Utility • SQL • Azure DB • OPC-UA/DA $o how good/bad was it? Teamwork

• Shannon – Soy Caramel Macchiato • Dustin – Iced White Mocha Sugar Free with an extra Shot (aka the snowflake) • Chris – Sugar Free Mocha • Cathy- Expresso #22 with 6 shots • Rilee – Café au Lait • Forrest – Yeah… We don’t talk about him • Elizabeth – Flat White Mocha • Alainia – Med Roast • Jakob – French Vanilla Cold Brew with a bit of almond milk • Ross – Sugar Free iced mocha ½ the syrup • Chmiel – Unicorn Frappuccino extra sprinkles • Katie – Iced White Mocha