Workflow migration
A well defined workflow help on management process. And there are many tools in market that helps defining these workflows, but monitoring FPSO platforms has a lot of complexities that challenges this tools, bumping into limitations. I’m going to address briefly those limitations and how we migrated these platforms.
How it worked
The adopted tool, affectionately called Oldflow, we defined:
- A form with fields monitored
- Flow for each equipment
- Triggers
- Permissions for model owners, that will investigate or react these alarms
Problems with Oldflow
- Our product owners created those flows, and received notifications because of that
- There was cost per account, increasing expense unnecessarily
- Access and report generation were too slow
- Changing form fields generated inconsistencies, denormalized and discontinued data silently
- There was no graphic visualization, just text
- Search did not combined fields
So we decided to migrate everything.
Migration
There were several steps to guarantee that everything went well:
- Mapping all fields and flows
- Cleaning and normalizing data
- Intense validations with Product Owners
- Switch systems that consumes the oldflow to the new platform
Mapping fields and flows
To guarantee all necessary data required were provided, without any incorrectly alarm closing
Cleaning and normalizing data
Uniform data, in a format that the new platform requires
Validations
Check for inconsistencies
Consume the new Platform
Integrate systems to read the correct platform to enhance the monitoring and improve our models
Prepared for the future
The new workflow resolved many oldflow limitations, with integrated graphs, improved and more accurate search, authentication, internationalized data (Hello/Olá/Ohayou future clients!) and more.
Come with us shape the future.
Take a look at our Linkedin and website:
