SoCalGas has been working to build a digital asset solution using AVEVA tools hosted on the cloud. This presentation discusses the strategies, challenges, and lessons learned from implementing this solution for capital projects. Key strategies included establishing clear data requirements, using cloud infrastructure for scalability, and leveraging AVEVA templates and components. Challenges included adapting workflows to the new system and ensuring contractor understanding of requirements. Lessons learned centered around continuous communication, early planning, flexibility in data entry, and properly estimating resource needs.

1. © 2017 AVEVA Solutions Limited and its subsidiaries. All rights reserved.
Presentation Summary
SoCalGas has been working to build a Digital Asset solution using
AVEVA. This presentation discusses the strategies, challenges, and
lessons learned from using AVEVA Integrated Engineering Design
tools on the cloud to execute capital projects.

2. 2
Managing a shift to Owner Controlled Data Centric Project
Execution
THE PATH TO OWNERS OWNING
THEIR DIGITAL ASSET

3. Agenda
» Introduction
» Motivation and AVEVA Experience
» Strategies
» Challenges
» Lessons learned
» Questions?
3

4. Introduction
» For 150 years, SoCalGas has served
Central and Southern California as
responsible and engaged environmental
leader, employer and neighbor
» As the nation's largest natural gas
distribution utility, we deliver clean, safe
and reliable energy to 21.6 million
consumers through 5.9 million meters in
more than 500 communities.
» Our service territory encompasses
approximately 20,000 square miles in
diverse terrain throughout Central and
Southern California, from Visalia to the
Mexican border.
» SoCalGas is a regulated subsidiary
of Sempra Energy
4

5. Motivation and AVEVA Experience
» Engineering Information Management
» Control of data / Spec driven Engineering &
Design
» AVEVA projects
▪ Back modeling of existing facility
▪ Regulator Station
▪ Filter replacement
» On going major project utilizing cloud
infrastructure and AVEVA Integrated Engineering
Design
5

6. Strategies – Engineering Data
Requirement
6
» Data centric requirement – building digital asset
▪ Develop data requirement in addition to traditional
engineering deliverables
» Setting expectations
▪ Clearly document data requirement and design tool
execution plan
▪ Host workshops to communicate and demonstrate data
requirement
» Specification driving engineering design
▪ Pre-approved specifications
▪ Ownership of design templates and components

7. Strategies – Infrastructure & Workflows
» Cloud hosted solution
▪ Startup time
▪ Scalability
▪ System performance & stability
▪ Agile deployment on system changes & software update
▪ Streamline onboarding process
» Design tool architecture & workflows
▪ Leverage available templates where possible
▪ Import NON AVEVA data from FEED
▪ Define AVEVA deliverables based on function availability and project schedule
▪ Leverage experienced AVEVA admins to do data clean up and systematic
updates & imports
7

8. Current Project AVEVA configuration
8
Engineering Information Management/Digital Hub
AVEVA IED Tools
Paragon
Spec
Library
E3D
AVEVA
Engineering
AVEVA
P&ID
AVEVA
Instrumentation
AVEVA
Electrical
AVEVA NetISM
Engage
Schematics Model
Manager
Integration Services

9. Cloud Web Services
AVEVA In the CLOUD
9
EP Team
Members
Paragon
Spec
Library
SCG Internal Network
AVEVA
IED
Tools
File
Servers
Database
Storage
License
Servers
AVEVA
Net/
Engage
SCG Projects/
Engineering
Team
Access via
AWS
Workspaces
SCG
Management
Projects/
Engineering
Team
EP Team
Members
Others?
Operations/
Construction
Access via
Web
Browser

10. Challenges
» Unknowns are scary – new ways of thinking for contractors and
project managers
» Project schedule
» Contractors limited knowledge of AVEVA tools
» Local resources with AVEVA knowledge
» Defining data requirement
» Organization changes and resource allocation
» Adapting to new workflows and change of mindset to build digital
asset
10

11. Lessons learned
» Continuous communication and make sure Contractors have the
same understanding for data requirement
» Early start with data requirement and design tool execution plan to
be on the same page of project management team
» Be flexible of data entry and information creation
» Properly estimate AVEVA resource to support projects
» AVEVA environment and project startup time
» Early infrastructure requirement check
11

12. » Use in-progress data for early construction/commissioning team
engagement, planning and scoping
» Expand data model for next projects/evolve workflows
» Improve internal project reporting – KPI’s and progress
monitoring – data analytics
» Data requirements define scope for contract development
» Higher alignment on project outcomes – harmonize teams
objectives
Opportunities on the Horizon
12