Scribd
Upload
127 views3 pages

Aconex Document Controller Guide

Uploaded by

Emil Jacob
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
127 views3 pages

Aconex Document Controller Guide

Uploaded by

Emil Jacob
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Oracle Aconex – Document Controller Tutorial

This tutorial is designed for Document Controllers working on construction and engineering projects
using Oracle Aconex. It focuses on practical, day-to-day system usage aligned with common project
controls workflows.

1. Introduction to Oracle Aconex


Oracle Aconex is a cloud-based common data environment (CDE) widely used for managing project
correspondence, documents, workflows, and audit trails. As a Document Controller, your primary
responsibility is to ensure accurate, timely, and compliant document control across the project
lifecycle.
Key Document Controller Responsibilities:

• Manage document uploads, revisions, and metadata.

• Maintain proper document numbering and naming conventions.

• Control document workflows and transmittals.

• Ensure compliance with project procedures and audit requirements.

2. Navigating the Aconex Interface


Upon login, users access the Project Home. Key modules relevant to Document Controllers include:

• Documents: Upload, search, and manage project documents.

• Mail: Formal project correspondence and transmittals.

• Workflows: Review and approval processes for submittals and drawings.

• Reports: Audit trails and document status reports.

3. Document Upload and Metadata


Documents in Aconex must be uploaded with accurate metadata. Metadata enables tracking, filtering,
and reporting across the project.
Typical Required Metadata Fields:

• Document Number

• Revision

• Document Type (Drawing, Method Statement, Specification, etc.)

• Discipline

• Status (For Review, Approved, Approved as Noted, etc.)


Always verify that the revision is correct and that superseded documents are clearly marked as
non-current.

4. Document Register and Revisions


Aconex maintains a full revision history for each document. When uploading a new revision, ensure it
is linked to the existing document number to preserve traceability.
• Never overwrite previous revisions.

• Use consistent revision codes (e.g., A, B, C or 0, 1, 2).

• Confirm the correct 'Supersedes' relationship during upload.

5. Workflows (Reviews and Approvals)


Workflows are used for formal review and approval processes such as drawings, material submittals,
and method statements.

• Select the correct workflow template.

• Verify reviewers and approvers are correct.

• Set realistic due dates based on contract requirements.

• Monitor overdue actions and send reminders when required.

6. Mail and Transmittals


The Mail module is used for formal correspondence. Document Controllers often issue transmittals
for document submissions to consultants, clients, or authorities.

• Use approved mail templates where applicable.

• Attach the correct document revisions only.

• Ensure distribution lists comply with the project communication matrix.

7. Reports and Audit Trail


Aconex automatically records a complete audit trail. Document Controllers should be able to generate
reports for document status, workflow history, and correspondence logs.

• Document Register Report

• Workflow Status and Cycle Time Reports

• Mail Register and Transmittal Logs

8. Best Practices for Document Controllers


• Follow the Project Document Control Procedure at all times.

• Perform daily checks for overdue workflows and rejected documents.

• Maintain clear coordination with engineers and project managers.

• Avoid manual tracking outside Aconex unless contractually required.


Disclaimer
This tutorial is a general guide and does not replace official Oracle Aconex training materials or
project-specific procedures. Always refer to your project’s approved Document Control Plan and
Oracle’s official documentation.

Common questions

Powered by AI

In Oracle Aconex, metadata is essential as it enables tracking, filtering, and reporting across the project through specified fields like Document Number, Revision, Document Type, Discipline, and Status. Accurate metadata ensures that documents are correctly categorized and retrievable, facilitating effective project controls .

Maintaining a full revision history is crucial for preserving traceability, which ensures that all document changes are recorded and can be referenced. Revisions should never overwrite previous versions and must be linked to the existing document number. Consistent revision codes and correct 'Supersedes' relationships should be maintained to prevent errors .

Reports and audit trails enhance project management by providing complete visibility into document status, workflow history, and correspondence logs. This visibility allows project teams to track progress, identify bottlenecks, and ensure compliance with project standards, ultimately improving decision-making and project outcomes .

Best practices include adhering to the Project Document Control Procedure, performing daily checks for overdue workflows, maintaining clear coordination with engineers and project managers, and avoiding manual tracking outside of Aconex unless necessary. These practices ensure organized and efficient document control, minimize errors, and promote accountability .

A Document Controller should perform daily checks for rejected documents and communicate with relevant stakeholders to resolve discrepancies. They should facilitate corrections by ensuring accurate revision submissions and adherence to project requirements. Continuous communication with engineers and project managers is vital to prevent recurring issues .

A Document Controller is primarily responsible for managing document uploads, revisions, and metadata. They maintain accurate document numbering, control document workflows and transmittals, and ensure compliance with project procedures and audit requirements .

The 'Mail' module in Oracle Aconex is used for formal project correspondence and issuing transmittals. Best practices include using approved mail templates, attaching the correct document revisions, and ensuring that distribution lists are in compliance with the communication matrix .

When setting up workflows in Oracle Aconex, it’s important to select the correct workflow template, verify the appropriate reviewers and approvers are assigned, and set due dates that align with contract requirements. Monitoring overdue actions and sending reminders are essential to ensure the workflow progresses smoothly .

Avoiding manual tracking unless necessary helps maintain data consistency and integrity in Oracle Aconex. It minimizes errors and discrepancies that can arise from duplicate records or incomplete updates. Keeping all tracking within the system aids in ensuring comprehensive audit trails and accurate project documentation .

The Document Register in Oracle Aconex is a crucial tool for maintaining traceability as it records the status, revision history, and metadata of each document. By using a consistent document numbering system and linking revisions, the register ensures that all project information is accurate and easy to access, thus facilitating effective project tracking and accountability .

You might also like