SiteManager Implementation Challenges “Getting Connected”

1. 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

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

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)

4. SiteManager Connection Diagram Application Server DPS Terminal ServerSM Client 3.4a-1 MS Server 2003 DataBaseOracle 8.1.7NT Thin Clients - Screenshot

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

7. Connecting to SiteManager Pick the server Production/test/training Enter Windows Id and Password

8. How to set personal connection options Re-type your windows password. You will be prompted to save as the default, click ok.

9. SiteManager Login

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!

11. Shows TS Server ID 1) 2) 3) 4) 5) Access front-end tied through an ODBC to ORACLEconnection 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 road 3) Production SiteManager 4) SiteManager Reporting – Customized CTDOT specific reports 5) End user created reporting is available Note: MS Access is the DOT Standard front-end to SM Data.

12. How To Run SiteManager Reporting Select SiteManager Reporting

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

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

16. The report also shows the overall Contract Value

17. This area is contract specific and requires some user selections

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

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

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.

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

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

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

27. 1) Select a Contract 2) Select a Report 3) Select a Day

28. PM & Inspectors wanted a daily snap shot of what work items were done on any given day including zero quantities. Inspector Remark information Sub or Prime Work Location Summary of Qty

30. Identifies if placed quantities exist Grouped by date

32. This report is used rather then the SM “Item Work Report. Remarks are used to identify location of the computations Typically Volume, Book and Page

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

35. This 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.

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

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

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