Software Selection/Integration Issues for Large Contractors

By Sheldon Needle

When discussing software requirements issues for contractors, it is important to consider the size and scope of operations.

A small – medium sized contractor ($2M – 50M) may get along fine with a basic job cost program, and the essential financial accounting modules of accounts payable, accounts receivable, estimating, general ledger, purchase orders, inventory, basic service management, simple document management and payroll. But a larger contractor $50M+ often will need either more depth in their accounting applications (e.g. multicompany, complex consolidations) and/or require other applications such as Human Resources, Fixed Assets, Equipment Management, collaborative project management, document scanning and vaulting, etc.

A really large contractor ($250M+) may require any or all of the following:

• interfacing to corporation financial reporting systems
• portfolio management of several entities
• integrating with specific industry applications like Primavera P6 for scheduling and cost tracking
• integration with industry specific estimating programs (like Hard Dollar for heavy contractors)
• supply chain management for inventory control and ordering
• quality assurance tracking for materials
• engineering control for bills of material
• greater security features by entity user and application
• strong integration with Outlook for tracing emails and creating alerts
• document imaging and workflow features
• earned value computations
• contract management
• user definable workflows
• realtime key performance indicator dashboards for management

With more applications come more complications as to how each vendor handles all the requirements and what, if any, third party vendors must be brought in to provide everything necessary.

With applications like project management, it is typical that the project management vendor will need to spend time studying the precise requirements (and even help advise on industry best practices) and to then provide a time and cost estimate to modify their software to meet the specific company processes. A typical scenario for creating a custom interface for a project management system to a construction accounting system can involve several months of work and $25-50k or more of expense.

Data can be a two way street

Work Breakdown Structures (WBS) are a way of describing and tagging specific costs assigned to jobs. Depending on which application captures those cost transactions, data may need to be moved between two different systems. For example, if Primavera is used to capture transaction costs it may use an entirely different set ofcost codes than the codes used by the construction application program (Timberline, Viewpoint, Dexter Chaney,Maxwell, Computer Guidance, etc.) . It then becomes necessary to set up a mapping translation between the systems so that data reporting is consistent between the two systems. This is critical for things like earned value computations which companies with government contracts must comply with (as well as others where the contract requires it).

Working with WBS codes and earned value according to job cost schedule budgets requires a higher degree of competence than just performing simple job to complete reports in a typical job cost accounting system.

Summary

Given the scope of applications, more sophisticated accounting requirements and potential multiple points of integration, evaluating construction software for larger contractors can be exponentially more complex than evaluating the needs of smaller ones.

To do the job right often requires expertise in accounting, financial management, project management, supply chain/inventory control, engineering, HR, and risk management. To execute the evaluation and selection of construction software for this category requires a well led committee of experts in each area who have the absolute confidence of management and are fully committed to the project.