Valero and Track™ 6.2 Enterprise Rollout

2012 Track User Conference

October 17th, 2012

© Valero 2010 Page 2

Agenda

• Valero Today• Pembroke Wales 6.2 Implementation• Track Landscape at Valero• New Functionality in 6.2 (from 5.2)• Implementation Approach• Shared Data in 6.2 Enterprise• Centralized Functions• Q & A

© Valero 2010 Page 3

Valero Today

© Valero 2010 Page 4

Pembroke Wales – Track 6.2

• Implemented Spring 2012• Go-Live April 30th with 11 vendors – headcount

about 800• On-boarded 19 additional vendors since• Used currency functionality for GBP (£)• Updated reports for currency and date format• Followed standard Valero business process of

Valero Timekeepers performing Allocations on behalf of Contractors

© Valero 2010 Page 5

Pembroke Wales – Track 6.2

• Unique Union Calculation Rules, including use of Rates 4, 5, & 6

• Use of Scheduled Reports• Use of Active Directory• Introduced Allocation Import Process (new to

Valero with Track 6.2 – see next slide)• Pembroke now in a Turnaround with a

headcount over 2,500

© Valero 2010 Page 6

Pembroke Wales – Track 6.2

• Allocation Import Process – Custom report for Excel to pre-populate Allocation Import template with default values including Timesheet Date, Location, Company Code, Order Type, Resource ID, Resource Name, Total Hours, Breakout of ST/OT/DT Calculated Hours, Extra Charges, and fields to indicate need for override

Track Landscape Current Model Proposed Model

Track 5.2 PL01

Track 5.2 PL02

Track 5.2 PL03

Track 5.2 PL07

Track 5.2 PL08

Track 5.2 PL10 Track 5.2

PL11 Track 5.2 PL16

Track 5.2 PL21

Track 5.2 PL22

Track 5.2 PL26

SAP

TRACK 6.2 North America

SAPV-SourceBW/BOBJ

Track PL08

DB

Track 5.2 PL09

DB

DB

DB

DB

DB

DBDB

DB

DB

DB

DB

Data Base

Web Server

WS

WS

WS

WS

WS

WS

WS

WS

WS

WSWS

WS

SAPV-SourceBW/BOBJ

DB

WS

Track 6.2 Europe (PL25)

TRACK 6.2 Europe

Data Base

Web ServerTrack 5.2 Ethanol

DB

WS

© Valero 2010 Page 8

Key New Functionality in 6.2

• Single sign-on• Import/Export Capability (allocations, contracts, rates, etc.)• Multiple Allocation Capability• Capability to Schedule Reports• Comments required on Voided Timesheets• Analytic (graphical) Reports• Blocking of allocations for resources with expired rate or no skill

assignment• Ability to CalcNet selected resources instead of entire company• Additional Purchase Order data in Track• Shift Differential by Skill

© Valero 2010 Page 9

Implementation Approach

• Migration to 6.2 Enterprise Instance will be phased by site• Track activity from 6.2 cutover forward will reside in the

new central instance• Track activity prior to 6.2 cutover will be available in a

separate database• Concurrent Track activity from multiple sites will be tested

to evaluate performance• Track business processes may change to take advantage of

new capabilities in 6.2• Rate Management interim vs. long-term approach

© Valero 2010 Page 10

Shared Track Data

• Master Data– Skills, Equipment Types– Holidays, Override Reasons, Pay Types

• Reports– Base reports delivered with Track– Valero developed reports (VLO-)

• Security Profiles– New users, security profile updates, access to companies,

access to reports• Pay Formulas• Schedules

© Valero 2010 Page 11

Centralized Functions

• Track master data maintenance– Skills, Equipment Groups/Types, Material Groups/Items– Holidays, Override Reasons, Pay Types– ERP Vendor Code (for communicating with V-Source)

• Track security– New users, security profile updates, access to

companies, access to reports• Pay Formula maintenance• Rate management (partial)

© Valero 2010 Page 12

Questions