Download presentation
Presentation is loading. Please wait.
Published byTyrone Marshall Modified over 9 years ago
1
Consultants and SiteManager
2
History
3
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
4
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?
5
Y2K Scare So here comes the Y2K scare. Mainframe breakdown? Used it as a concern
6
History FieldManager CAS And the field offices started receiving laptops
7
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
8
Consultants in SiteManager??? We issued the programs to the consultant offices. –SiteManager –VPN Client Software –Oracle
9
Woohoo!!! The consultants were in SiteManager
10
What??? We couldn’t distinguish Oklahoma contracts from consultant contracts
11
What Now???? We needed to know which jobs in each division were given to the consultants We wanted the least impact on the user
12
Brainstorming
13
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!
14
Roadblock
15
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.
16
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
17
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
18
Residency Codes
19
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
20
Contracts Screen
21
Consultant Tracking This helps us make decisions on each consultant Keeps contract money from being tied up from consultant jobs
22
In Closing
23
Was it worth it?
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.