20230823 - Unity Rollout Status Report
Current progress of Unity testing, development, and deployment.
RISKS
Migration time
Establish upgrade procedures and version controls for live clients on a single code version.
Need agreement by all internal teams so that client communication is aligned.
Needs to be clearly communicate to clients so they understand the future process.
Need to confirm any risk associated with testing on one type of environment and going live on another.
Need standard timeline of deploying latest branch, there is a calendar that a few have seen internally and gme/terra have seen
For Unity-Upstream2
We will need to have db loaded for each one to test regulatory in all the different states(8 total, possibly can exclude 2)
Bank formats
Land/Contract Management needs heavy regression (170/290 features were WPX)
For Unity-Midstream1
Bank formats
Fixed assets
Resource constraints internally
Chris Peterson(M33) assisting in who and how to target on initial call. Continued discussion scheduled 7/10
Services to begin assisting Midstream regression testing to meet Aug1 deadline
Micah, Blake, Ryan putting together Midstream specific test cases
GAPS
Release Notes (Jeff Gunter/Michael Ferrante actively working on)
Need process put in place to combine deltas as new clients onboard to Unity
Active projects versioning and communication
action item: Sally to delegate communication out about releases and release notes coming
Internal project box alignment
Still need Raisa project and UAT setup for project team to start
Vipul to schedule call (frank, csms, sally) to discuss quick box break down to determine which can be shut down
Rewrite SOC documentation for delivering patches, releases etc
Pre Unity to Unity db schema changes
Clients with replica db’s need this level of detail for reporting/dashboards etc.
This must be the source and destination for the respective client.
Internal Feedback/Questions
We are forming teams of 2-3 to reach out to next 20 clients.
Timeline needed for midstream unity 2 merge.
Mustang is a new client that will need Summit’s contract management code. No timeline is set still on mid1. can’t just do summit due to targa and some others lined up for future rollout
There could be delay in rollout and unity items being worked while services burndown is happening
Consistent OI issues
WH Balancing documentation needed for Flywheel from 10.5.0
How are we looking to resolve the space issue?
What are we doing internally to resolve the issues we continue to experience on new roll outs?
We have not had 1 clean Unity upgrade for any client.
Current Status
LIVE CLIENTS
TERRA (Live 5/22) Yellow
GME (Live 5/22) Yellow
IKAV (Live 6/12) Red
Flywheel (Live 7/17) Green
Highpeak (Live 7/31) Yellow
King (8/1) Green
Riverbend (8/7) Yellow
Vital (UAT-GO LIVE TARGET 8/18) Yellow
28 open tickets(12 code change, 13 support review, 3 awaiting feedback)
client requested 6 old tickets be moved to Vital Unity organization that increased ticket count
All critical for go-live tickets were completed and returned to Vital for testing
Internal regression testing(QA)
Upstream(Jaybee DB)
Functional high risk: total = 133 (Untested - 127, Pass - 5, Fail-1)
Midstream
Eagleclaw (will not be our first midstream client on unity)
total = 509(Untested - 60, Pass - 414, Fail-35)
Transportation
CHS
73 test cases Untested.
Live clients' logged ticket count in backlog: 76
Dev queue: 18
Support queue: 44
Waiting on DevOps: 2
Waiting for Feedback (from client):11
Assigned to reporting team: 1
Focus for Next Week
Future Process Improvements
Build RACI matrix for future efforts for transparency of responsibilities across teams.
Add automation for the “easy” wins like UI testing to eliminate almost 30% of the testing effort.
Continue to build out test cases for regression testing across the application.
Add expected results to compare against for testers with limited functional knowledge.
Have defined performance testing with PROD comparable environments to provide better expectations to clients when taking code.
Add code test coverage to eliminate lost functionality with future merges or code changes.
During current round of testing multiple issues have re-emerged after originally fixed.
Comprehensive and up-to-date check list of all tasks related to upgrades.
Important Links | Regression testing dashboard - https://wenergysoftware.atlassian.net/jira/dashboards/10080 Release 10.2.0 Dashboard - https://wenergysoftware.atlassian.net/jira/dashboards/10077 |
Clients in upgrade pipeline | Jaybee, TRG, Dugan |

