Package Descriptions

There are many different packages that are available, with new ones being added often, to help customize your OneOffice application. Below is a description of each package along with applicable screenshots to give you a glimpse into the package before you install it.

1. oneoffice/acs-integration: Allows the ability to download ACS csv Export

2. oneoffice/ad-for-bid-award: Adds the field “award date” to the Ad for Bid table

3. oneoffice/bid-qustions: Adds a module for contractors to communicate and ask questions with the agency while in the bidding phase.

4. oneoffice/bidders-list: This adds a template that shows the contract and project numbers/names along with a list of bidder name, their bond amounts, if they acknowledged any addenda, and their total bid amount.

5. oneoffice/bidvault-link: this displays a link on the public dashboard of the bidding phase, above the plans table, for plan holders to bid online via bidVAULT.

6. oneoffice/colorado-item-list: this will import the CDOT Item Code Book

7. oneoffice/construction-status: this adds the sections Suspension of Work, Intermediate Projects, and Construction Dates. (There is a user role for this that you need to assign for users to have access to these sections)

8. oneoffice/consultant: this gives external users like Consultants access to contracts on a per contract basis. (There is a user role for this that you need to assign for users to have access)

9. oneoffice/contract-attachments: this adds an Attachments section to each contract. You can use this like a file folder to store contract related documents that are not created within OneOffice. (There is a user role for this that you need to assign for users to have access)

10. oneoffice/contractor-payment: this installs the following Payment Templates - Contractor Payment with and without Final Acceptance, Contractor Payment with Project Values with and without Final Acceptance, Contractor Payment with Funding Breakdown.

11. oneoffice/contractor-payment-by-project: this creates the ability to add payments on a per project basis rather than on a contract basis. It is not recommended to switch back and forth between the two options on a single contract. (There is a user role for this that you need to assign for users to have access)

12. oneoffice/dropbox: this adds the Dropbox file integration.

13. oneoffice/encumbrance: this adds an Encumbrance section to the contract menu. (There is a user role for this that you need to assign for users to have access)

14. oneoffice/engineers-estimate: this adds an Excel Template for the Engineer’s Estimate by contract or by project.

15. oneoffice/engineers-estimate-extra-report: this adds an extra report for the Engineer’s Estimate (under the Reports section) to group items by project and category.

16. oneoffice/funding-category-group-number: this adds a group number field to the Funding Category table.

17. oneoffice/funding-source-type: this adds the field Type to the Funding Source table.

18. oneoffice/labor-mgmt: this adds a Labor Management section to the contract menu. (There is a user role for this that you need to assign for users to have access)

19. oneoffice/legacy: this gives users access to ‘Legacy’ features like Agreements, Permits, Scheduling, Completion Checklist, and Final Item Documentation in the contract menu. In the project menu, the user will see different sections like Details, Data, Planning, Construction Data, Completion Data, Custom Data, Attachments, Inspection Questions, and Final Inspection. (There is a user role for this that you need to assign for users to have access)

20. oneoffice/legacy-archive: this archives contracts in groups, rather than having to archive individually. You set the date and any contract created prior to that date will be archived. You can ‘unarchive’ a contract at any time.

21. oneoffice/missouri-item-list: this will import the Missouri Bid Item List with additional columns for Accuracy, NIGP, and NAICS.

22. oneoffice/mn-ad-for-bid: this is a Word Template for an Ad for Bid for MN agencies.

23. oneoffice/mn-certificate-of-final-acceptace: this is a Word Template for the MnDOT Certificate of Final Acceptance.

24. oneoffice/mn-change-in-status: this adds information for Change in Contract Construction Status like the Ad for Bid award date, construction status field, geographical location field, and project numbers.

25. oneoffice/mn-change-order: this is a Word Template for the MnDOT Change Order document.

26. oneoffice/mn-daily-construction-diary: this is a Word Template for the Daily Construction Diary document.

27. oneoffice/mn-disctrict-document-access: this grants access for State/District users to view contract related documents. (There is a user role for this that you need to assign for users to have access)

28. oneoffice/mn-force-account-agreement: this is a Word Template for the MnDOT Force Account Agreement document.

29. oneoffice/mn-funding-source-type: this adds different Funding Source Types to the drop down menu for Funding Sources that are pertinent to Minnesota.

30. oneoffice/mn-item-record-account: this is a Word Template for the MnDOT IRA document for items.

31. oneoffice/mn-state-aid-payment-request: this adds a section to the Project menu to enter and submit Minnesota State Aid Payment Requests. You can map contract funding sources to lines on the document automatically - you will want to also install the mn-funding-source-type package. This also installs the MN State Aid Payment Request Excel Templates. (There is a user role for this that you need to assign for users to have access)

32. oneoffice/mn-weekly-diary: this is a Word Template for the MnDOT Weekly Diary document.

33. oneoffice/mndot-historical-prices: this allows you to import MnDOT historical prices from previous years to use for your own estimating.

34. oneoffice/mndot-spec-book: this imports the MnDOT Spec Book Item List for optional years.

35. oneoffice/office-mgmt: this adds Office fields to the Ad for Bid and Plan Holder list if there are multiple offices for one organization. Example - RTVision Office A, RTVision Office B, etc.

36. oneoffice/oh-inspection: this installs the Ohio Inspection Package that includes custom sections related to ODOT tracking.

37. oneoffice/ohio-item-list: this imports the ODOT Item Master

38. oneoffice/on-hand-describe: this adds a comments field to the transaction table for Material on Hand.

39. oneoffice/organization-account: this adds a field to the organization table for the account number

40. oneoffice/project-construction-location: this adds a field to the project table for the Construction Location.

41. oneoffice/project-engineer: this adds a field to the project table for the Project Engineer.

42. oneoffice/project-funding: this adds a section the Project Menu to track funding on a Project level.

43. oneoffice/project-geographical-location: this adds a field to the project table for the Geographical Location.

44. oneoffice/project-item-extended: this adds an Extended Description column to the Item table.

45. oneoffice/project-numbers: this adds the fields Local, State, and Federal Numbers to the project table.

46. oneoffice/project-work-type: this adds a field to the project table for Work Type.

47. oneoffice/punch-list: this adds the section Contractor Task List which includes a punch list and submittals area. (There is a user role for this that you need to assign for users to have access)

48. oneoffice/schedule-of-prices: this is a Word Template for the MnDOT Schedule of Prices, by contract and by project, documents.

49. oneoffice/sonoma-contract-extension: this is a package for Sonoma County, California that adds extended calculations to the contract in calendar and working days per week and per payment. This also tracks various working days in the daily journal.

50. oneoffice/texas-item-list: this imports the TxDOT Bid Codes.

51. oneoffice/transaction-describe: this adds some additional fields to the Transaction table; comments, segment description, and documentation.

52. oneoffice/transaction-verify: this adds a field to transactions and marks it verified after payments are applied.

53. safety/safety: this adds the Public Safety Concern Reporting feature the Safety & Issue Reporting Tool.