build.works vs. Oracle Aconex

Large, Multi-Party Capital Projects
Scenario: Major construction or infrastructure projects involving owners, designers, multiple contractors, subcontractors, and regulators. Why Aconex Fits: Provides a neutral, single source of truth across many independent organizations. Strong permissioning and data ownership model builds trust between parties. Scales well to very high document volumes and long project durations. Example Use: Design development and construction documentation for a multi-year infrastructure project with hundreds of external users.

Incentivized

• The existence of insurance and permit tracking.
• Budgetary control measures and expense monitor.
• Job costing and logistical management.
• Skills and competencies improvement.

Incentivized

• Sharing of projects comments and document can be more efficient.
• Estimation capabilities can be improved.
• The initial configuration can easily confuse the beginners.

Incentivized

Requires a better interface that allows you to find all tools in order to utilise all functions.

Incentivized

Aconex's document control workflow allows for multiple versions of the same revision, enabling markups to be seen and document history as appropriate. This is on par with SOLIDWORKS EPDM, and is by far better than InEight's TeamBinder, as the originator and uploader of the document are able to change the version without the need for an administrator.

Incentivized

• Reductions in print costs alone (subcontractor bid process) paid completely for the use of the product. Further benefits to all project participants included process streamlining and 100% access to all project documentation (Drawings, Specifications, Contracts, Notices of Change, Change Orders etc.) from any online source including mobile devices. Benefits probably accounted for 150% of product cost.
• Intangible benefits included reduced exposure to claims as a result of good (and agreed process tracking).

Incentivized