Skip to Main Content
D-Tools System Integrator Ideas Portal
6 Not supported for the current status
Created by Guest
Created on Oct 24, 2024

Comprehensive item change log/audit trail.

We have been working on some huge projects that have dozens of change orders. Some are pending, some are approved, and some are rejected. Some items are getting kicked around across multiple COs.

Huge Project Example:

- Project quoted late 2021. $5M 10-floors 100s of rooms. Solutions and packages utilized.

- Project approved Mid-2023.

- Some items may now be EOL so an internal change order is created to replace EOL items with their replacements. Let's pretend this doesn't affect the project price.

- It is discovered that during the original quoting process, some rooms were missed but we cannot ask for more money, was our mistake. Alternatively, some rooms were added on the OG project also our mistake, so again, not to affect price, these BOM items become part of a 'pool of spares' that can be utilized where items were missing previously. So a shuffling of items to different locations is warranted.

- Project changes are pouring in faster that we can get CO built and approved/rejected so changes on items are layering across several change orders. In a perfect world, this would work serially, but in the real world that just isn't the case. While we do try and keep a manually written change narrative, it is not item by item. We don't have the resources.

Here is the issue:

Due to limitations in SI, we cannot convert the items in a solution to project items that are no longer part of the solution on an approved project. So the only way to deal with that is to clone the OG solution on a new CO, delete the OG solution and convert the solution to items so they can be redistributed.

So it is now possible that a single item from the approved revision was replaced because it was EOL on one CO then cloned and moved on anther CO. or any other number of changes.

So as more and more COs are created and and some remain pending, this becomes a rather large web of changes with no real meaningfull way to understand the journey a single item may have taken without an audit trail. For an item that was replaced, the deleted item may no longer be in the same location as the added item so how do we find that later. We need a way to track it's journey.

This may be a big ask, but this has been plaguing us for a long time on HUGE projects. This is less critical for small/medium projects, but we are struggling on the VERY large projects. If I am missing something or doing this incorrectly I am all ears.

    Not supported for the current status
  • Attach files
  • +1