Change Log Process for BOOL Personalization

This article explains the Change Log Request process for BOOL projects. 

Preliminary Review

When a customer makes personalization requests they should first be entered into the personalization sheet for preliminary review. This is intended to be a "scratch pad" for design, procurement, construction and/or sales to make an initial decision regarding the feasibility of making the change. 

Once a request has been "confirmed to proceed" the AE or Designer can submit the "Change Log Request" in Blueprint.

Submission

When submitting the request from the Change Log tab in Blueprint as much detail should be entered into the request as possible. For this process select the Change Source of "Bool Customer Request/Personalization".

When submitting multiple requests for a single customer they should be added to a group. You can either create a new group or add requests to an existing group. 

Note: When creating a Group use the naming convention, "Customer Last Name - Project Address"

Note: Assets are now auto-generated based on the Change Source. Additional assets can be added but auto-generated assets cannot be deleted

Review

Initial Review To Do's will be created and assigned to relevant team members once the request is submitted. These To Do's ensure that team members review the request, determine if it is feasible and add relevant information such as pricing and product information.

Note: Marking the Initial Review To Do's Complete keeps the Change Log Request process moving forward

Once pricing information has been entered AEs should communicate with the Client to get an initial confirmation that they would like to move forward. If the Client would like to move forward the AE should check "Client Confirmation" box. If the Client decided not to move forward then the Change Log Request should be rejected.

Approvals

If the "Client Confirmation" box is not checked then the request cannot move forward to approvals. Once that box is checked and the Initial Review To Do's are marked as complete then the Change Log Request will be sent for approval.

For BOOL requests approvals will be sent to the "Director of ConOps", "Sales Lead", "Design Lead" and the "General manager" assigned on the Team Members page. 

Note: Approvers will be the relevant team leads for the "Assets" impacted by this Change Request

Implementation

Once the Change Log Request is approved "To Do's" will be created and assigned for the Change Log Request to be implemented. The "Implementation To Do's" will be based on the assets that need to be updated.

Once all Implementation To Do's are marked as complete then the Change Log Request will be assigned a status of Complete!