Construction ERP Software Resources
Articles, Discussions, and Reports to expand your knowledge on Construction ERP Software
Resource pages are designed to give you a cross-section of information we have on specific categories. You'll find articles from our experts, discussions from users like you, and reports from industry data.
Construction ERP Software Articles
The Construction Project Lifecycle Drives Innovation in Construction Technology
Construction ERP Software Discussions
Which Construction ERP platforms actually keep field and office users logged in for 6 months after go-live, rather than reverting to spreadsheets once the implementation team leaves? Reviewer patterns in the Construction ERP category point to a few specific reasons that do or don't occur. What we're hoping to find:
- Mobile access good enough that site supervisors actually use it, not just office staff
- A workflow that fits how construction teams already operate, rather than forcing a generic ERP process
- Support that continues meaningfully after go-live, not just during onboarding
- Reviewer evidence of sustained use, not just initial satisfaction
- CMiC Platform: Reviewers cite continued use tied to its mobile field tools, which several say keep site teams engaged after the initial rollout excitement fades.
- AccuBuild: The highest-rated platform in this category, reviewers cite straightforward day-to-day use as the reason adoption sticks for smaller and mid-size firms.
- Sage Construction Management (formerly Corecon): Reviewers describe solid initial adoption, with a few noting engagement drops once a firm outgrows its core feature set.
Has anyone actually measured login frequency or field-tool usage a year after go-live, rather than relying on how the rollout felt at the time?
Why we need this tool? There is no centralized deployment process in IFS to deploy releases to all servers. The following task must be performed manually to install a tiny release. • Login & Copy release on each server from release location. • Install releases manually to all servers e.g. (onshore, offshore(n)). • Electronically sign the deployment manifest files for the host you use. • Verify that the user can start the client as an end user. Solution: • GUI designed to support centralized deployment. • Batch script designed to check connectivity of all sites opted to deploy. • Batch script designed to copy and install releases on all sites opted to install. Benefits: • Minimized manual efforts required for copying and installing release. • Support all environment e.g. (Development, Preproduction, Production). • Support installation from multiple sources e.g. (VDI, Locally, Individual RDP) • Deployment can be done on one or multiple sites at once from single place. • Installer will receive verification link to verify installation.

