As-Built Ripple
The “Spatial Engineer 11” video tutorial focuses on the process of converting proposed Ripple projects into as-built status. The presenter begins by highlighting a proposed Ripple, identifiable by its unique color coding, which serves as a visual alert to engineers that work is in progress. This color remains until the project is marked as built.
Two methods for marking a Ripple as built are discussed:
- Applying the as-built status to the entire work order.
- Performing a partial post, which updates only a portion of the Ripple if, for instance, work has not been completed on other branches.
A key difference in marking Ripples as built, compared to new facilities, is highlighted: at the end of the as-built process, the system prompts the user to confirm if the changes should be permanently recorded in the database. A “No” response will revert the changes, while a “Yes” confirms and completes the as-built process.
The presenter demonstrates selecting the as-built option for a Ripple work order and entering the current date to initiate the process. Following this, the system processes the Ripple, updating the cable colors back to normal upon completion, and removing the splice badge indicators.
To illustrate the completion of the as-built process, the presenter deletes temporary color layers and re-queries the system to show that the plant components have returned to their standard color scheme, indicating that they are now officially as-built.
This tutorial provides a clear guide for Spatial Engineer 11 users on how to update the status of Ripple projects, emphasizing the importance of the final confirmation step to ensure accurate database records. The process is crucial for keeping project data up-to-date and ensuring all modifications are correctly reflected in the system.
Keywords: Spatial Engineer 11, as-built Ripple, proposed Ripple, work order, database recording, color coding, partial post, splice badge, query, tutorial.