Skip to main content
Skip table of contents

20230927 - Unity Rollout Status Report

Current progress of Unity testing, development, and deployment.

RISKS

  1. Establish upgrade procedures and version controls for live clients on a single code version.

    1. Need agreement by all internal teams so that client communication is aligned.

    2. Needs to be clearly communicate to clients so they understand the future process.

    3. Need to confirm any risk associated with testing on one type of environment and going live on another.

    4. Need standard timeline of deploying latest branch, there is a calendar that a few have seen internally and gme/terra have seen

  2. For Unity-Upstream2

    1. We will need to have db loaded for each one to test regulatory in all the different states(8 total, possibly can exclude 2)

    2. Bank formats

    3. Land/Contract Management needs heavy regression (170/290 features were WPX)

  3. For Unity-Midstream1&2

    1. Bank formats

    2. Fixed assets

GAPS

  1. Release Notes (Jeff Gunter/Michael Ferrante actively working on)

    1. Product team working to make release notes in app. Potentially 10.8.0, either dev to build or widget(preferred by Vipul). hoping by friday there is a demo for product

  2. Active projects versioning and communication

    1. Release schedule has been validated and approved. Micah sent follow up to Product for some FAQs and will have Todd put together a one-pager for communication.

  3. Rewrite SOC documentation for delivering patches, releases etc

    1. Discussions have been made but documentation not completed. Deadline by EOM. Micah to send follow up to Erik, Hari and sally

  4. Pre Unity to Unity DB schema changes (client by client request)

    1. Clients with replica DB’s need this level of detail for reporting/dashboards etc.

    2. Unsure if Cognos would be affected

Internal Feedback/Questions

  1. What is the game plan for unique features testing by QA in this continuous rollout?

    1. need land test cases for dugan and QA to test them

    2. Vipul to start analyzing column E of unity combined spreadsheet with the product team and QA

  2. How are we looking to resolve the space issue?

    1. Can we upgrade a few support and QA boxes?

  3. Superior added to pipeline below. We have no internal knowledge of volume balancing to even create test cases for QA. Nathan did a lot of the unique coding in data prep logic related to volume balancing. potential suggestion: upgrade regular environment, figure out volume balancing piece after and maybe get it in one instance

  4. JIB improvements and DO improvements, but Revenue was slower than normal. release rev payments

Current Status

  1. LIVE CLIENTS

    1. TERRA (Live 5/22) Yellow

    2. GME (Live 5/22) Yellow

    3. IKAV (Live 6/12) Red

    4. Flywheel (Live 7/17) Green

    5. Highpeak (Live 7/31) Yellow

    6. King (Live 8/1) Green

    7. Riverbend (Live 8/7) Yellow

    8. Vital (Live 8/28) Yellow

  2. In UAT

    1. Mustang (services project Aug2023) - Mid/Trans 1

      1. 1 open ticket

    2. Legacy/Revenir(services project) - Upstream 1

      1. pushed to beginning of year

    3. AEC

      1. Received UAT box for gap analysis project with Magnum Forge

    4. Jaybee

      1. Received UAT box for testing

  3. Regression Testing

    1. Mid/Trans

      1. Total Executed Failed Pass
        101 38 4 33

  4. Live clients' logged ticket count in backlog: 126 (trending steady)

    1. Dev queue: 44

    2. Support queue: 47

    3. Waiting on DevOps: 5

    4. Waiting for Feedback (from client):27

    5. Assigned to reporting team: 3

Focus for Next Week

  1. Mid/Trans Unity1 regression testing - @a user coordinating additional resources from Services

  2. Determine how many clients we can take on internally for continuous and successful roll out of Unity

    1. Need follow up meetings surrounding FR2.0 and land - material item. should be feature flag.

  3. Examine root cause for open tickets @a user and team

Future Process Improvements

  1. Build RACI matrix for future efforts for transparency of responsibilities across teams.

  2. Add automation for the “easy” wins like UI testing to eliminate almost 30% of the testing effort.

  3. Continue to build out test cases for regression testing across the application.

    1. Add expected results to compare against for testers with limited functional knowledge.

  4. Have defined performance testing with PROD comparable environments to provide better expectations to clients when taking code.

  5. Add code test coverage to eliminate lost functionality with future merges or code changes.

    1. During current round of testing multiple issues have re-emerged after originally fixed.

  6. 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

Upstream: Jaybee(september), Dugan, Kosmos

Mid/Trans: TRG, Superior January 2024 , CHS(ready as soon as chorus integration is complete) , EOG Q2 2024,Western Q2 2024 Targa mentioned Q32024 need messaging for reluctant clients

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.