Production Technology Workbench: Developing and Scaling a Corporate Digital Product Using Agile Methods

Joel Chacon, Peter Dabrowski
{"title":"Production Technology Workbench: Developing and Scaling a Corporate Digital Product Using Agile Methods","authors":"Joel Chacon, Peter Dabrowski","doi":"10.2118/207922-ms","DOIUrl":null,"url":null,"abstract":"\n \n \n The production technology working environment of an oil brownfield is usually an inconsistent collection of tools and spreadsheets. In this paper, we will explore Wintershall Dea's digitalisation journey from a patchwork of tools and spreadsheets to a unified corporate Production Technology Workbench (PTW) solution starting from the replacement of an existing and ageing tool on an asset on the Norwegian continental shelf and ending by incorporating the requirements of other assets from Wintershall Dea's diverse and geographically dispersed portfolio.\n \n \n \n The project started by selecting the low-code application platform suitable to be used as the basis for the journey. After a proof-of-concept stage, an Agile project was launched owned by the asset and with a geographically dispersed Development Team conformed by Wintershall Dea's Product Owners, IT/OT experts, UX consultants and Eigen's scrum master and Development Team. After the delivery of the MVP, a second Product Owner was incorporated from a second asset. The Agile project continued to deliver on enhanced functionality and requirements that would most benefit both assets.\n \n \n \n The original production system calculations and workflows are vital for the asset. However, such patchworks are not easy to work with and complex to maintain or change. This had a negative effect on the efficiency as work is time-consuming and cumbersome. Well anomalies were often detected by actively looking for them daily in various plots, reports and platforms, and therefore the detection and response time to production events was delayed. A Production Technology dashboard with built-in / automated data processing for standard tasks provides engineers with the required transparency of data to identify issues and pain-points in a timely manner. This helps engineers to proactively intervene to mitigate unplanned losses and downtime, reducing the amount of deferred production. Investment in a corporate-wide unified (standard UX) platform, will help engineers when starting new assignments to spot issues easier and quicker independently of the asset they are assigned to. But beyond a standardization, each engineer needs to be able to create individual workflows (for effects such as scaling, slugging, sand etc.) for their needs by means of the self-service capabilities of the technology. Also, the quick access to frequently used and relevant data could be accessed through one platform, making everyday life of the production engineer more efficient and smoother. Over the timeframe of 15+ Sprints the Product Owners refined and re-defined the exact functionality they would like to see delivered.\n \n \n \n The PTW concept seeks to minimise the time that engineers require to learn the tool and use it to inspect, analyse, and make decisions to optimise the production of the field. This is one of Wintershall Dea's first projects executed following Agile, using a geographically dispersed team, during the restrictions imposed by the pandemic. The multi-Product-Owner project approach is a novel way to govern the evolution of the tool to suit multiple stakeholders. In comparison to a E&P typical waterfall project management approach, the application of Scrum really showed added value in reducing risk early on, increasing visibility and transparency and adapting to the customer's needs (production engineers) throughout the process.\n","PeriodicalId":10959,"journal":{"name":"Day 3 Wed, November 17, 2021","volume":null,"pages":null},"PeriodicalIF":0.0000,"publicationDate":"2021-12-09","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Day 3 Wed, November 17, 2021","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.2118/207922-ms","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 0

Abstract

The production technology working environment of an oil brownfield is usually an inconsistent collection of tools and spreadsheets. In this paper, we will explore Wintershall Dea's digitalisation journey from a patchwork of tools and spreadsheets to a unified corporate Production Technology Workbench (PTW) solution starting from the replacement of an existing and ageing tool on an asset on the Norwegian continental shelf and ending by incorporating the requirements of other assets from Wintershall Dea's diverse and geographically dispersed portfolio. The project started by selecting the low-code application platform suitable to be used as the basis for the journey. After a proof-of-concept stage, an Agile project was launched owned by the asset and with a geographically dispersed Development Team conformed by Wintershall Dea's Product Owners, IT/OT experts, UX consultants and Eigen's scrum master and Development Team. After the delivery of the MVP, a second Product Owner was incorporated from a second asset. The Agile project continued to deliver on enhanced functionality and requirements that would most benefit both assets. The original production system calculations and workflows are vital for the asset. However, such patchworks are not easy to work with and complex to maintain or change. This had a negative effect on the efficiency as work is time-consuming and cumbersome. Well anomalies were often detected by actively looking for them daily in various plots, reports and platforms, and therefore the detection and response time to production events was delayed. A Production Technology dashboard with built-in / automated data processing for standard tasks provides engineers with the required transparency of data to identify issues and pain-points in a timely manner. This helps engineers to proactively intervene to mitigate unplanned losses and downtime, reducing the amount of deferred production. Investment in a corporate-wide unified (standard UX) platform, will help engineers when starting new assignments to spot issues easier and quicker independently of the asset they are assigned to. But beyond a standardization, each engineer needs to be able to create individual workflows (for effects such as scaling, slugging, sand etc.) for their needs by means of the self-service capabilities of the technology. Also, the quick access to frequently used and relevant data could be accessed through one platform, making everyday life of the production engineer more efficient and smoother. Over the timeframe of 15+ Sprints the Product Owners refined and re-defined the exact functionality they would like to see delivered. The PTW concept seeks to minimise the time that engineers require to learn the tool and use it to inspect, analyse, and make decisions to optimise the production of the field. This is one of Wintershall Dea's first projects executed following Agile, using a geographically dispersed team, during the restrictions imposed by the pandemic. The multi-Product-Owner project approach is a novel way to govern the evolution of the tool to suit multiple stakeholders. In comparison to a E&P typical waterfall project management approach, the application of Scrum really showed added value in reducing risk early on, increasing visibility and transparency and adapting to the customer's needs (production engineers) throughout the process.
生产技术工作台:使用敏捷方法开发和扩展企业数字产品
棕地的生产技术工作环境通常是一个不一致的工具和电子表格集合。在本文中,我们将探讨Wintershall Dea的数字化之旅,从工具和电子表格的拼凑到统一的企业生产技术工作台(PTW)解决方案,从替换挪威大陆架资产上现有和老化的工具开始,最后结合Wintershall Dea多样化和地理分散的投资组合中的其他资产的要求。项目从选择适合作为旅程基础的低代码应用平台开始。在概念验证阶段之后,敏捷项目由资产和由Wintershall Dea的产品负责人、IT/OT专家、UX顾问和Eigen的scrum主管和开发团队组成的地理分散的开发团队共同启动。在交付MVP之后,从第二个资产中合并了第二个产品负责人。敏捷项目继续交付增强的功能和需求,这对两个资产都是最有利的。原始的生产系统计算和工作流程对资产至关重要。然而,这样的拼凑并不容易处理,维护或更改也很复杂。这对效率产生了负面影响,因为工作既耗时又繁琐。在不同的区块、报告和平台中,通常通过每天积极寻找异常来发现异常,因此延迟了对生产事件的检测和响应时间。生产技术仪表板内置/自动数据处理标准任务,为工程师提供所需的数据透明度,以及时识别问题和痛点。这有助于工程师主动干预,减少计划外损失和停机时间,减少延迟生产的数量。在公司范围内的统一(标准UX)平台上的投资,将帮助工程师在开始新任务时更容易、更快地发现问题,而不依赖于他们所分配的资产。但是,除了标准化之外,每个工程师都需要能够通过该技术的自助功能为他们的需求创建单独的工作流(例如缩放、段塞、砂等效果)。同时,通过一个平台可以快速访问常用数据和相关数据,使生产工程师的日常生活更加高效和顺畅。在超过15个sprint的时间框架内,产品负责人精炼并重新定义了他们想要交付的确切功能。PTW的概念旨在最大限度地减少工程师学习工具的时间,并使用它来检查、分析和做出决策,以优化油田的生产。这是Wintershall Dea在疫情限制期间采用敏捷方法执行的首批项目之一,使用了一个地理分散的团队。多产品所有者项目方法是一种管理工具演进以适应多个涉众的新方法。与E&P典型的瀑布式项目管理方法相比,Scrum的应用在早期降低风险、增加可见性和透明度以及在整个过程中适应客户(生产工程师)的需求方面确实显示出了附加价值。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
求助全文
约1分钟内获得全文 求助全文
来源期刊
自引率
0.00%
发文量
0
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
确定
请完成安全验证×
copy
已复制链接
快去分享给好友吧!
我知道了
右上角分享
点击右上角分享
0
联系我们:info@booksci.cn Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。 Copyright © 2023 布克学术 All rights reserved.
京ICP备2023020795号-1
ghs 京公网安备 11010802042870号
Book学术文献互助
Book学术文献互助群
群 号:481959085
Book学术官方微信