Consultants and SiteManager

History

History

• In 1988 the first TUG Conference was held in Oklahoma

• At that time, Oklahoma made a commitment to participate in the CMS, now known as SiteManager

• Oklahoma used a mainframe progressive estimate system for years, even with the first consultant contracts

• Oklahoma field offices had a single user to input all the pay quantities for all contracts

History

• SiteManager enthusiasts saw the need to get the department prepared for the change ahead– Management – If it’s not broke, don’t fix it!– More personnel involved and educated– Better hardware

• What could buy us some time?

Y2K Scare

• So here comes the Y2K scare.

• Mainframe breakdown?

• Used it as a concern

History

• FieldManager• CAS• And the field offices started receiving laptops

One Giant Leap

• After lots of planning, devotion, cussing, and swearing, SiteManager Construction was implemented in Oklahoma in 2004!

• Consultant contracts were still loaded into CAS until we could get them started in SiteManager

Consultants in SiteManager???

• We issued the programs to the consultant offices.– SiteManager– VPN Client Software– Oracle

Woohoo!!!

• The consultants were in SiteManager

What???

• We couldn’t distinguish Oklahoma contracts from consultant contracts

What Now????

• We needed to know which jobs in each division were given to the consultants

• We wanted the least impact on the user

Brainstorming

Consultant Codes

• We wanted to give the consultants a code that would easily distinguish them from the Oklahoma offices

• We wanted to add each consultant to each division

• We had it all figured out!

Roadblock

Roadblock

• What will this do to the other Trns·port modules?

• Historical data

• We determined this type of change would affect LAS, PES, the jobs we had left in CAS and FieldManager, and DSS as well as the closed contracts in SM.

Resolution

• We realized at this point we needed InfoTech’s help

• The quote from InfoTech was substantial but we needed the change

• We started meeting with InfoTech

Done

• December 1, 2007

• With InfoTech’s help, we ran the scripts they provided which updated the code in all affected areas

• The consultants were added using the same code format

Residency CodesResidency Old Code New Code

DIV RES DIV RES

MUSKOGEE 1 1 01 100SALLISAW 1 2 01 200DIV. 1 BRIDGE 1 7 01 700ANTLERS 2 1 02 100HEAVENER 2 2 02 200

Consultants

EST ? ? DIV # 001Tetra Tech ? ? DIV # 002Cobb Eng ? ? DIV # 003

What’s New

• We updated all the affected reports and reporting tools

• We even added a field in some SiteManager screens to make it easier on the user

Contracts Screen

Consultant Tracking

• This helps us make decisions on each consultant

• Keeps contract money from being tied up from consultant jobs

In Closing

Was it worth it?