1. 1 Introduction to MBProject

2. 2 Part I: MBProject and how it is used. Part II: What MBProject might do in the future. Also, as-built data collection and import into P3.

3. 3 Introduction Microsoft Access database application Developed for use on VDOT inspection projects Links with VDOT’s Construction Workbook (CWB) program Provides comprehensive project management tools

4. 4 Introduction Consists of two files –Program file –Data file Allows for upgrades to the program Can be customized for non-VDOT use

5. 5 The Main Menu Operates as an application The user does not have to understand the details of MS Access or how a database works to use MBProject Provides categories of user actions Specific menus of subtasks provided

6. 6

7. 7

8. 8 Setting Up a Project A new project must be created Basic information is entered into MBProject –Job name –VDOT Contract ID Number –Description –Contract $ Value & Completion Date –Path to location of MBProject data file

9. 9

10. 10 Choose a Job

11. 11 Maintenance Tables CompaniesEquipmentInspectorsLaborWeather*Contacts * Contain pre-set entries but can be customized Contractors CPM Codes Actions* Document Types* Specifications

12. 12

13. 13

14. 14 Updating CWB MBProject transfers transaction information to CWB only when directed by the user Data should be verified before running the update procedure Once the update has been performed, the data is locked and cannot be changed

15. 15 Creating a Diary Page First step in building the database A date must be created or selected from the list Once a date has been established, the weather and Contractor work hours may be entered

16. 16

17. 17

18. 18

19. 19 Creating a Diary Page Each page is created for a specific PCN (VDOT “Project Control Number”) Once a page is created, it must be saved and the user return to the Main Menu before adding a page for the same date under a different PCN From the Main Menu, choose the Edit action to enter the Diary Form and begin entering daily information

20. 20

21. 21 The Activities Tab Information regarding specific work activities –Contractor –Pay Items –Issues –CPM Codes –Narrative text

22. 22

23. 23 The Labor & Equipment Tab Record information regarding counts of manpower and equipment Manpower recorded by Labor classification Equipment includes a note field (i.e. to note if equipment was idle) Manpower and equipment can be recorded separately for each contractor

24. 24

25. 25 The Inspectors & Visitors Tab Record inspectors on project and hours worked Record visitors that were on the project, and for how long

26. 26

27. 27 The Notes Tab Record general notes for the day Notes can be associated with Issues and CPM Codes

28. 28

29. 29 Printing a Diary Page Can be printed from any Diary Tab Can print single or multi-page Can also be printed from the Reports menu

30. 30

31. 31 Project Logs C-79 Log Document Log Issue Log Material Status Log Work Order Log Follow-up Log

32. 32

33. 33

34. 34 Document Log Record documents sent and received Record any actions required Identify file location Link to Issues

35. 35

36. 36

37. 37 Issue Log Identify issues that occur on the project Note if and when the issues are resolved Note cost if issue results in a change or associated work order Used to link diary entries, CPM Codes, documents, work orders, etc. to Issues

38. 38

39. 39 Materials Status Log Record materials submittals Track submittals dates and turnarounds Track actions required Link to responsible contractor and specification section

40. 40

41. 41

42. 42 Work Order Log Record Work Orders Track associated cost and time Track cumulative cost and time for all Work Orders Link Work Orders to Issues

43. 43

44. 44

45. 45 Follow-up Log Record items from meetings, etc. requiring action Track actions and responsibility

46. 46

47. 47 Reports Allows the user to print a variety of information –Diary Pages –Pay Item Summaries –Quantity Summaries –Issue Activity –CPM Activity

48. 48

49. 49

50. 50

51. 51

52. 52 Summary MBProject has given MBP a way to do more than just create diaries for VDOT It allows us to manage much of the information that we want to handle on a project So what is coming in the future? –More flexibility –Customization for Non-VDOT use –Ideas from the Team (More on these next time!)