Projects change; Aconex changes with them.
No matter how big or small the project is that you are involved in, it will go through different stages.
For example, let’s take a look at a typical construction project. It goes from Conception to Design, to Construction before reaching Completion and being handed over to its new owner.
The project team evolves from one stage to the next, and so do the processes required to deliver the outcomes.
Aconex has been designed to adapt, just like the project team does. However there are a few important things to keep in mind.
Don’t over-engineer your Aconex setup during the early stages. You might “think” that you know what is needed in the future, but all too often this changes as the project progresses.
Make sure you consult the key stakeholders when setting up a new process. Anything from how Design Reviews are run to management of RFI registers requires input from the people who own the process.
Don’t assume people “just know” what to do. Make sure that whenever you have new members joining the team, you have an information pack available which tells them everything they need to know about getting started with Aconex, and lets them know about any specific processes already set up on your project.
It is mission-critical to have someone in charge of the settings on your Aconex project. Not only as a gatekeeper against unwanted changes to settings, but also as a reference point and champion. And yes, that person may change over the course of the project. That is why it’s important to document changes to the settings, and why they were made, so that this can be referred to when needed.