The number of technology and solution platforms that have been introduced to electrical contractors over the past few years have been staggering. The challenge comes when those systems need to transfer data between themselves. We often end up with good software operating in separate silos, leaving employees to hop between them manually. As contractors continue to build more connected field-to-office workflows, application programming interfaces (APIs) offer a relatively simple way to bridge those gaps and get more value from your existing technology that already in place.

What is an API?

An API is a defined way for one software application to exchange information with another.

You don’t have to be a software developer to understand the basic concept. Think about a project management platform containing project numbers, names, addresses and superintendent information. That same information may also be needed in an estimating database, prefab dashboard or internal reporting tool.

Without integration, somebody may enter that information several times, which leaves room for typos and errors. An API allows one system to request the information directly from another. This simple concept can open the door to some very interesting custom workflows.

Connecting the technology stack

Construction companies already generate large amounts of data. The key here is accurate data. The quote “garbage in, garbage out” sums up this concept perfectly. Field information can flow into dashboards, where project teams use it to identify trends and address problems before they become schedule issues. APIs can extend that idea across the technology stack.

For example, a contractor could pull project information from its project management software into an internal dashboard. An estimating system could send project awarded information into the same dashboard. A prefab application could receive this information into its own custom dashboard for project status and future project updates.

The integration doesn’t always need to be complicated. Many modern cloud applications already provide APIs. Simply search the phrase “List all API access from Autodesk Forma” and your top result takes you to a complete list of APIs available. In practical terms, the hardest part is often deciding what information needs to be integrated, where it needs to go and which system should be considered the single source of truth.

Start with a repetitive tasks. If someone downloads a spreadsheet every Friday, cleans it up and then uploads the same information somewhere else, there may be an opportunity for an API connection.

One technical person can change the conversation

This is where having one technically capable person on staff can make a surprisingly large difference. That person doesn’t necessarily need the title of software developer. It could be a coder, data analyst, BIM/VDC specialist or construction technologist who understands basic programming, databases and how APIs work. Give that person access to the right systems and suddenly the conversation changes from “Does our software do this?” to "Can we build this ourselves?” The key here is that this process gives you the ability to create tools that fit your process, as opposed to buying a tool that was created trying to fit everybody’s processes.

This follows a pattern we’ve already seen with other construction technologies. Cloud platforms improved the cyclical exchange of information between the field and office, while BIM/VDC helped connect coordination, prefab and installation workflows. APIs provide another layer of connectivity between those systems.

Start with the workflow, not the code

Contractors don’t need to become software companies to take advantage of APIs. They just need to understand their own processes first. Find a repetitive task where employees are manually moving the same information between systems. Map where the information originates, determine where it needs to go and identify whether the applications offer API access. Then give someone with the appropriate technical skills the opportunity to test a small integration.

The first successful connection may save only a few minutes. The bigger value is discovering that your technology stack doesn’t have to be limited to the workflow software vendors provide out of the box.

With the right person internally, APIs can turn a collection of individual applications into something much more powerful: a technology environment customized around how your company actually works.