Many companies feel they need to have a solid process before adopting technology, but you seem to be doing both in parallel. Can you talk about this approach?

We have a vision of how we want to leverage AWP principles to enhance our execution model. We have a strategy in place on how we expect to get there, and it was decided to move forward with the overarching process definition in conjunction with, and parallel to, the investigation and feasibility of the various inputs, interfaces, and data involved in the system set up and roll out.

By working in parallel, the team has not only refined the specific data input requirements but also validated and visualized how the data appears and functions within the system, along with the resulting associations and outputs. This complimented the development of the processes by facilitating and enabling the required validations, which are then incorporated into the process as specific requirements.

How has implementing both the process and technology at the same time benefited the Organization?

While having a sound, mature process in place may facilitate a more expedited software deployment, working both in parallel has proven hugely beneficial by enabling a more thorough and accurate assessment of not only what is required, but also the validation, visualization, and analysis of the impact of the various data sets and information flowing into and out of the process. At the end of the day, by defining a preliminary process, validating with data and information, then revising the process as necessary and/or updating the system configurations, this approach enables greater specificity to be embedded into both the process and the system set up.

It is also worth noting that the O3 solution does not require that you use AWP as a foundational business process. In fact, we are piloting some O3 functionality on projects that do not use any AWP or workface planning. By selecting a technology that can be used at any level of execution maturity, we have been able to progress and see value before getting our AWP process and data completely worked out. More traditional thinking might suggest that data and processes need to be in a mature state prior to engaging or using a system or tool, however, O3’s flexibility and collaborative approach has enabled us to move forward along our continuous improvement journey together.

What successes have you seen so far in your journey with O3?

While time did need to be invested early in deployment to learn how the system worked, this was a fundamental step that then enabled us to determine the most effective system configuration and set up to specifically support our execution model. By making modifications to the various system settings and adjusting fields and attributes to suit the available data as we moved through the investigation phase, the system processing capabilities facilitated the exercise as we tested and sought to produce the desired outputs.

O3 has also demonstrated a willingness to support our specific way of working, which is slightly different from the more traditional construction industries where AWP was initially developed. O3 utilizes an agile development approach that enables features and enhancements to be rolled out with a new release every couple of weeks. This has allowed us to quickly deploy a solution that follows AWP best practices while meeting the unique needs of our organization and industry.

Looking ahead, how do you see O3 continuing to impact your processes and projects?

As we move forward with our AWP execution strategy deployment and the O3 system functionality and facilitation within the Organization, the opportunities for streamlined data flow, more efficient processes, enhanced collaboration, removal of redundancy and duplicated efforts/data, and improved execution performance is not only expected, but inherently inevitable.

Do you think this partnership has potential beyond what was initially envisioned?

O3 has many features and functions, so much so that upon starting the journey it was actually quite daunting, to say the least. As well as the more traditional WFP and AWP processes within O3 that are pretty well known by most in the industry, there are many parallel, independent, and also interrelated functions that are available to be leveraged to enhance any company’s execution approach. The fact that these features can be operated in the same environment only builds the case for companies that might be looking to consolidate legacy processes and/or systems on projects that may or may not be utilizing an AWP strategy.

A key takeaway: no matter where a company stands on the AWP maturity scale, O3’s solution is adaptable—from those with no AWP experience, to those with advanced experience. The Organization is proving that partnering with O3 can drive value at any stage of the process.

While O3 is purpose-built for AWP, our software is just as effective for any project wishing to become more agile and improve the way they plan and execute. The benefits remain the same: greater visibility, improved accountability, and delivering projects on time and on budget.

Want to learn more? Request a demo and we’ll show you how O3 can fit into your existing processes and reap the same benefits.