41
SiteManager Implementation Challenges “Getting Connected” Joseph J. Bouchey SiteManager Administrator Office Of Construction Conn. Dept. of Transportation PH: (860) 594-2676 FX: (860) 594-2678

SiteManager Implementation Challenges “Getting Connected”

Embed Size (px)

DESCRIPTION

SiteManager Implementation Challenges “Getting Connected”. Joseph J. Bouchey SiteManager Administrator Office Of Construction Conn. Dept. of Transportation PH: (860) 594-2676 FX: (860) 594-2678. Challenges. Speed- Login (blue bar of death) Adding new items Retrieving Samples - PowerPoint PPT Presentation

Citation preview

Page 1: SiteManager Implementation Challenges  “Getting Connected”

SiteManager Implementation Challenges

“Getting Connected”Joseph J. Bouchey

SiteManager AdministratorOffice Of Construction

Conn. Dept. of TransportationPH: (860) 594-2676FX: (860) 594-2678

Page 2: SiteManager Implementation Challenges  “Getting Connected”

2

Challenges Speed-

– Login (blue bar of death)– Adding new items– Retrieving Samples

Keeping synchronized with the database - – Error messages upon saving

Migrating to new releases– Supporting and documenting version changes & training

Getting reports to end users quickly

Page 3: SiteManager Implementation Challenges  “Getting Connected”

3

Terminal Server (TS) Advantage Speed - Screenshots are passed not database. Blue bar

login time is down to just a few seconds. 56K is OK. Support - Only one install on TS, end user problems are

limited to printing & login access. No more on-site visits Upgrades - SM was backed-up and upgraded and rolled

out from SM 3.3 to 3.4a-1 in 2.5hrs Training & Testing - Each client has access to

testing/training & production environments. (can be different versions of SM)

Downtime - Since TS implementation (7/6/04) we have had a total of 2 hours downtime. (Server reboot needed)

Page 4: SiteManager Implementation Challenges  “Getting Connected”

4

Application ServerDPS

SiteManager Connection Diagram

Terminal ServerSM Client 3.4a-1MS Server 2003

DataBaseOracle 8.1.7

NT

Thin Clients - Screenshot

Page 5: SiteManager Implementation Challenges  “Getting Connected”

5

Terminal Server Facts

$40,000 to implement includes Server & 300 Licenses

Couldn’t have done it without FLDOT– James Phillips - port assignment

Same principal as Citrix With VPN next best thing to being web

enabled

Page 6: SiteManager Implementation Challenges  “Getting Connected”

6

Page 7: SiteManager Implementation Challenges  “Getting Connected”

7

Connecting to SiteManager

Enter Windows Id and Password

Pick the serverProduction/test/training

Page 8: SiteManager Implementation Challenges  “Getting Connected”

8

How to set personal connection options

You will be prompted to save as the default, click ok.

Re-type your windows password.

Page 9: SiteManager Implementation Challenges  “Getting Connected”

9

SiteManager Login

Page 10: SiteManager Implementation Challenges  “Getting Connected”

10

The Need for Customized Reports SiteManager internal reports fall short in

many areas Don’t have Powerbuilder knowledge on staff Don’t have RTF knowledge on staff Need ability to quickly query Manager’s want reports without the hassles of

logging into anything!

Page 11: SiteManager Implementation Challenges  “Getting Connected”

11

On every user’s desktop by default are 4 icon’s. 1) Shared folder with updated Construction information (read-only)2) Personnel end user space to store files – when on the road3) Production SiteManager4) SiteManager Reporting – Customized CTDOT specific reports5) End user created reporting is availableNote: MS Access is the DOT Standard front-end to SM Data.

Access front-end tied through an ODBC to ORACLEconnection

1)

2)

3)

4)

5)

Shows TS Server ID

Page 12: SiteManager Implementation Challenges  “Getting Connected”

12

How To Run SiteManager Reporting

Select SiteManager Reporting

Page 13: SiteManager Implementation Challenges  “Getting Connected”

13Each button is tied to either a specific report or additional reporting.

Page 14: SiteManager Implementation Challenges  “Getting Connected”

14

The example above is tied to a DOT summary report.This report compares all Districts and the amount of assigned Work.

Page 15: SiteManager Implementation Challenges  “Getting Connected”

15

Page 16: SiteManager Implementation Challenges  “Getting Connected”

16The report also shows the overall Contract Value

Page 17: SiteManager Implementation Challenges  “Getting Connected”

17This area is contract specific and requires some user selections

Page 18: SiteManager Implementation Challenges  “Getting Connected”

18

All Reports are Contract Specific• Identifies all Items that exceed 125% of original contract Value• Displays current line item level detail sorted by Item Code, Project, then Category• Stockpile Report by Invoice Number• Daily snapshot of DWR work items performed on a given day and grouped by inspector. User is prompted to select day (YYYYMMDD)• Current list of all Prime/Subcontractor equipment sorted by vendor name then equipment ID• Listing of unauthorized DWRs sorted by date, then user

• Similar to the “Item Work Report”, but alsoincludes remark and subcontractor details• Used on older SM contracts when MP&T Items required additional general remarks details

Page 19: SiteManager Implementation Challenges  “Getting Connected”

19The user can type the contract ID or use the drop down arrowfor the selection options

Page 20: SiteManager Implementation Challenges  “Getting Connected”

20

Page 21: SiteManager Implementation Challenges  “Getting Connected”

21

This Report shows what contract items are currently 125% overthe original contract amount and may be required to negotiate an adjusted contract price with the contractor.

Page 22: SiteManager Implementation Challenges  “Getting Connected”

22

The calculation is based on the sum of the item installed vs. bid quantities.

Page 23: SiteManager Implementation Challenges  “Getting Connected”

23

Page 24: SiteManager Implementation Challenges  “Getting Connected”

24This report is a variation of the “Item Quantity Report”.It is more compact (less pages) and gives Category Details

Page 25: SiteManager Implementation Challenges  “Getting Connected”

25

Page 26: SiteManager Implementation Challenges  “Getting Connected”

26

Line Items grouped by Invoice Number with installation qty, payment and status

Page 27: SiteManager Implementation Challenges  “Getting Connected”

27

1) Select a Contract

2) Select a Report

3) Select a Day

Page 28: SiteManager Implementation Challenges  “Getting Connected”

28

PM & Inspectors wanted a daily snap shot of what work items were done on any given day including zero quantities.

InspectorRemark informationSub or PrimeWork LocationSummary of Qty

Page 29: SiteManager Implementation Challenges  “Getting Connected”

29

Page 30: SiteManager Implementation Challenges  “Getting Connected”

30

Identifies if placed quantities exist

Grouped by date

Page 31: SiteManager Implementation Challenges  “Getting Connected”

31

Page 32: SiteManager Implementation Challenges  “Getting Connected”

32

This report is used rather then the SM “Item Work Report.

Remarks are used to identify location of the computationsTypically Volume, Book and Page

Page 33: SiteManager Implementation Challenges  “Getting Connected”

33This area is contract & Subcontract specific and requires some user selections

Page 34: SiteManager Implementation Challenges  “Getting Connected”

34

Page 35: SiteManager Implementation Challenges  “Getting Connected”

35This report finds when the sub was approved, started work and last worked. It also specifies if a DBEand contact information. This list is sorted alpha numeric.

Page 36: SiteManager Implementation Challenges  “Getting Connected”

36

Page 37: SiteManager Implementation Challenges  “Getting Connected”

37

Report Identifies current Payroll submittals sorted by vendor, then by date

Page 38: SiteManager Implementation Challenges  “Getting Connected”

38

Page 39: SiteManager Implementation Challenges  “Getting Connected”

39

Report Identifies amount of Subcontract work completedcompared against the actual subcontracted amount.

Page 40: SiteManager Implementation Challenges  “Getting Connected”

40

Page 41: SiteManager Implementation Challenges  “Getting Connected”

41

This report is compared against the payroll received report to determine if payrolls are missing. If onsite is marked NO, then no work was performed and only a payment was made. T_DWR_CONTR