as a part of DBE Core Ecosystem Orchestration

as a part of DBE Core Ecosystem Orchestration
THTH TIE project plan Introduction of the Technical Information Management (TIE) project for investment projects and O&M as a part of DBE Core Ecosystem Orchestration THTH Spring Seminar Arto Marttinen, THTH ry

Agenda Process industry target in a larger DBE* Core ecosystem framework Joint TIE project (Technical Information Exchange) plan proposal Conclusions *DBE stands for Digital Business Ecosystem

DBE Core Ecosystem development network
Maritime industry THTH driven TIE is one project in larger business framework Process industry Common denominator: open standards, opens solution, blockchain technology

Technical information exchange currently
Internal business API Internal business API Suppliers, service providers End- customers EPC/EPCM Other business partners (analytics services, installation work, …) Banks and financiers Currently companies are exchanging information manually Internal business API Internal business API Suppliers, service providers End- customers EPC/EPCM Digitally ? Other business partners (analytics services, installation work, …) Banks and financiers Currently companies are considering own individual (point-to-point) solutions ISO/IEC content standardization

Shared data models form the foundation
Other business partners (analytics services, installation work, …) Banks and financiers Internal business API Internal business API Commercial ISO (UBL2.2) SHARED DATA MODELS Suppliers, service providers End- customers Network connectivity missing Commonly agreed intercompany workflows missing Technical ISO-15926, IEC-61987, … CFIHOS, USPI, SSG, PSK,… EPC/EPCM

Collaborative business processes link parties together
Other business partners (analytics services, installation work, …) Banks and financiers Internal business API Internal business API L O C V E I A R T B U S N P SHARED DATA MODELS Suppliers, service providers End- customers Workflows Business area specific use-cases Network connectivity missing transfer-file-based manual workflows possible EPC/EPCM

Interoperability using standardized interfaces
Other business partners (analytics services, installation work, …) Banks and financiers Internal business API Internal business API L O C V E I A R T B U S N P SHARED DATA MODELS Suppliers, service providers End- customers E R F N A P I C E R F N A P I C Ecosystem interoperability guaranteed EPC/EPCM

New data sharing in digital ecosystems
Other business partners (analytics services, installation work, …) Banks and financiers Internal business API Internal business API Metso (FC) Sulzer Pumps Endress+Hauser Siemens Andritz Neste Engineering Pöyry Process industry pilots DBE Core, Tieto, … Bixaco, Pajarinc, … SHARED DATA MODELS L O C V E I A R T B U S N P F Technical Information Other B2B Other Tech Info Business Information Open Digital Ecosystem Stora-Enso Metsä Group Fortum UPM Suppliers, service providers End- customers Ecosystem interoperability guaranteed EPC/EPCM

ORCHID information maturity model
ORCHID - ORCHestrated Industrial Data Lower all ecosystem obstacles Business motivation (to exchange information) Information sovereignty (ownership) Open networks, open standards, open solutions From point-to-point model to ecosystem model Simpler technological solutions (blockchain) Open Ecosystem development Common agreement (orchestration) Network infrastructure development Intercompany integration development Company’s internal development International industrial standards  ISO standards CEN CWA 2010 standard – ORCHID project

TIE development target
Create commonly agreed concept and tools to manage technical information data models based on international and industry standards (classes, content, schemas, APIs) and targeting to open solutions together with companies (pilots and PoCs) and standardization bodies (PSK, SSG, USPI/CFIHOS, DEXPI, MIMOSA, ISO/IEC,…) with Scandinavian perspective for pulp and paper industry that will be continuously maintained after the project starting from existing 4 exemplar data models (automatic valves, centrifugal pumps, electric motors, flow meters) Create ecosystem rules and principles for projects and O&M in process industry governance model for the network development and operations agree and specify common business processes and corresponding use-cases – TIE to focus process industry plant lifecycle business specifications (in projects and O&M) – step-by-step via PoCs and pilots network rulebook definition & development Support common network infrastructure component development for PoCs and pilots together with other business areas and IT infrastructure companies including tools development for data modelling, schema and API interoperability testing Support common network integration components & testing development

Open ecosystem development tasks
Common orchestration and development Companies’ own platform and integration development Process industry main focus Shared focus with other business areas Common integration components Common ecosystem specifications Integration components C1 A B Platform implementation Network infrastructure components Ecosystem’s rules, principles, governance model, processes, “network rulebook” Common network infrastructure components Common GitHub OASIS, UBL business document standardization body Test and pilots UBLschemas Equipment class schemas Business processes in investment projects and O&M General documentation Backend systems integration Technical data modeling tool Equipment class specific attribute dictionaries from standardization bodies (RDL) C2 D Interopera-bility testing tools Equipment class specific schemas from standardization bodies Orchestration tasks Industry group specific additional attributes and/or schemas Common ecosystem documentation Common development tasks Common ecosystem specifications Companies development tasks

TIE – for process industry development
Network rules and principles development Governance model for the network development and operations Agree and specify common business processes and corresponding use-cases – TIE to focus process industry plant lifecycle business specifications (in projects and O&M) – step-by-step via PoCs and pilots Network rulebook definition & development Common network infrastructure component development Developing infrastructure components, common refence APIs, network support & metrics Common network integration components & testing development Developing integration components and data model, schema and API interoperability testing concepts Technical data models and their governance concept development Exemplar technical data models and schemas for selected equipment classes based on existing international and industry standards Technical data modeling concepts and a tool to maintain/modify them together with standardization bodies and special industry groups With industry pilots (possible complementing future MIMOSA OGI pilots with P&P viewpoint)

Example workflow in a project
Manual workflow Digital workflows can be implemented transaction by transaction (according to company’s corresponding internal process integration maturity level). API (send) API (receive) Acknowledgment Payment

API ”handshake” Engineering systems Engineering systems
API (”send”) API (”receive”) Commonly approved network infrastructure implementation Blockchain Back-end systems integration Network integration Open network Engineering systems Maintenance management systems PDM systems ERP systems CRM systems Engineering systems Maintenance management systems ERP systems CRM systems Tech Internal parsing & validation UBL DBECore C C UBL DBECore Git Hub Open concept for development and sharing data models, schemas, reference APIs and other ecosystem documentation Com

TIE orchestration and development tasks
A. Network rulebook definition & development (Deliverable: Network Rulebook) AO1 – PoC orchestration & guidance AO2 – Defining business processes, ecosystem roles & principles based on PoC findings AO3 – Defining integration of common technical data models in ecosystem processes AO4 – Defining network operations and maintenance activities and responsibilities AD1 – Business use case specific network PoCs (multiple) B. Common network infrastructure development (Deliverable: Common network codebase, running network) BO1 – Agreeing and defining technical components based on the network rulebook BO2 – Agreeing and defining the network supporting components & metrics (monitoring, etc.) BD1 – Defining and developing common technical network components BD2 – Onboarding and running the network nodes / components C. Network integration & testing (Deliverable: Integration documentation as part of rulebook, common integration codebase, running test network) CO1 – Agreeing and defining common integration components CO2 – Agreeing and defining tools & practices for testing integration and onboarding (e.g. test network) CO3 – Agreeing and defining the rules & documentation of test network usage & onboarding CD1 – Developing common integration components CD2 – Defining and developing test network toolstack CD3 – Setting up and running the test network components D. Common technical data models (Deliverable: Data model governance concept) DO1 – Concept for agreeing common technical data models’ content DO2 – Agreeing and defining common data modeling concept for creating and maintaining technical data models DO3 – Agreeing information sharing principles and information sovereignty (SEED collaboration?) DD1 – Defining and developing a technical data modeling tool for the ecosystem needs DD2 – Defining and developing interoperability tools for technical data model schemas Use-case specific WGs Based on PoCs/pilots Network infrastructure WG Starting definitions for end-to-end information exchange International tech standard WG DEXPI, MIMOSA, USPI, CFIHOS, SEIIA, PCA, … Equipment class specific content WGs Instrumentation & automation WG Pumps WG Electric motors WG Other equipment WGs Schema WGs Common schema specification WG Defining tech data modeling concept & project WG

TIE next steps – phase 1 1st orchestration step tasks 3rd phase starts
Basic orchestration definitions and project specification Disseminating open concept idea, searching new partners prepare Orchestration step 1 National start Orchestration step 2 Expanding international collaboration Orchestration step 3 Expanding international collaboration 6/2019 11/2019 6/2020 6/2021 1st orchestration step tasks Agreeing business cases for PoCs and define their use-cases Agreeing common data modeling concept basics for orchestration step 2 Agreeing the development targets and project plan for the data modeling tool development project Enhance international standardization collaboration (USPI, CFIHOS, MIMOSA, DEXPI, SEIIA,…( Find more companies to join Outlining common network infrastructure and integration development targets. Agreeing common ecosystem rules and principles together with other business areas Development step 1 Tools and components Development step 2 Tools and components 3rd phase starts 2nd phase starts according to the approved plans Tech data modelling tool development starts Ecosystem infrastructure components development starts 1st phase Business Finland approves application, ECOSYSTEM WILL START!

TIE next steps – phase 2 2nd orchestration step tasks
New companies to join the orchestration Ecosystem rules and principles prepare Orchestration step 1 National start Orchestration step 2 Expanding international collaboration Orchestration step 3 Expanding international collaboration 2nd orchestration step tasks Agreeing the next common business cases for PoCs and define corresponding use-cases together with business partners (end customer-EPC-suppliers networks) Attaining wider approval for the concept among standardization bodies and companies Agreeing additional equipment classes and their commonly needed data content Agreeing the concept to integrate the technical data schemas with the corresponding business documents in different phases of the workflows defined by use-cases. Outlining together with other business areas the common network infrastructure and integration development targets – agreeing network rulebook and metrics 6/2019 11/2019 6/2020 6/2021 Development step 1 Tools and components Development step 2 Tools and components 1st development step tasks Defining and developing the data modeling tools for technical data models according to the ecosystem needs. Defining and developing common integration components together with other business areas. Common network infrastructure development together with other business areas. (common codebase for infrastructure components, network rulebook, member pilots, …) Defining the next development steps 3rd phase starts 2nd phase starts according to the approved plans Tech data modelling tool development starts Ecosystem infrastructure components development starts 1st phase Business Finland approves application, ECOSYSTEM WILL START!

TIE next steps – phase 3 3rd orchestration step tasks
New companies to join the orchestration Ecosystem governance model prepare Orchestration step 1 National start Orchestration step 2 Expanding international collaboration Orchestration step 3 Expanding international collaboration 3rd orchestration step tasks Agreeing and defining tools & practices for testing integration and onboarding Agreeing and defining the rules & documentation of test network usage & onboarding Defining network operations and maintenance activities and responsibilities Agreeing and defining technical components based on the network rulebook Agreeing and defining the network supporting components & metrics (monitoring, etc.) 6/2019 11/2019 6/2020 6/2021 Development step 1 Tools and components Development step 2 Tools and components 2nd development step tasks Finishing the data modeling tools for external standardization usage. Finishing common integration components together with other business areas. Finishing common network infrastructure development together with other business areas. (common codebase for infrastructure components, network rulebook, member pilots, …) Finishing network integration and testing development together with other business areas. (common codebase for integration components, interoperability testing tools, member pilots, …) 3rd phase starts 2nd phase starts according to the approved plans Tech data modelling tool development starts Ecosystem infrastructure components development starts 1st phase Business Finland approves application, ECOSYSTEM WILL START!

Conclusions Start orchestration now!
Limited process industry focus as a part of wider business framework New way to support standardization for technical information exchange Part of international standardization development Shared development target with standardization bodies  CFIHOS collaboration, MIMOSA OGI pilots  joint discussion and other global standardization bodies Finnish partner PSK, Swedish partner SEIIA  target one common Scandinavian solution Companies’ PoCs and pilots determine the development roadmap THTH to establish TIE division to support continuity today!

THANKS

Sharing of distributed information

Collaboration areas: focused industry roadmap exists

TIE step 1 – ecosystem to be opened
Step 1 is only orchestration development Resources: PoC experts from companies Equipment class experts from companies and PSK teams THTH/Marttinen Pajarinc/Pajari Orchestration costs: 50k€ Funding: companies 50% and BF 50% Members’ PoCs AO2 – Defining business processes, ecosystem roles & principles based on PoC findings AO3 – Defining integration of common technical data models in ecosystem processes Agree and define use-cases for PoCs Update and document agreed UBL2.3 specs DO1 – Concept for agreeing common technical data models’ content DO2 – Agreeing and defining common meta modeling concept for creating and maintaining technical data models Agree additional 7 equipment classes, complete existing 4 Agree and define metamodeling concept, initiate international collaboration with standardization bodies AO1 – PoC orchestration & guidance AO4 – Defining network operations and maintenance activities and responsibilities Agree PoCs and common principles for them Agree basic network O&M activities and responsibilities* 5/2019 11/2019 * To be done together with other businesses Detailed project plans for the next phase orchestration and development tasks to be agreed

TIE step 2 – ecosystem development
Step 2 is composed of orchestration and common development work Resources: PoC experts from companies Equipment class experts from companies and PSK teams Selected subcontractors OrchestrationsTHTH (Pajarinc/Pajari, Marttinen) Orchestration costs: 50k€ ; Development costs: 100k€ Funding: BF 50% for orchestration, 30% for development Members piloting network functionalities AD1 – Business use-case specific network PoCs (multiple) A AO2 – Defining business processes, ecosystem roles & principles based on PoC findings AO4 – Defining network operations and maintenance activities and responsibilities Business processes Common network infrastructure development together with other business areas. (common codebase for infrastructure components, network rulebook, member pilots, …) B Network infrastructure components Shared development together with other businesses Network integration and testing development together with other business areas. (common codebase for integration components, interoperability testing tools, memeber pilots) C Network integration components DO1 – Concept for agreeing common technical data models’ content Agree additional 10+ equipment classes, agree concept Meta-modeling tool development DD1 – Defining and developing a meta modeling tool for the ecosystem needs D 9/2019 3/2020 Detailed project plans for the next phase orchestration and development tasks to be agreed

TIE step 3 – closing orchestration
Members piloting network functionalities and starting to ramp-up production network Step 3 is composed of orchestration and common development work. Orchestrations will be ended 3/2021 but the development projects will continue A Business processes, ecosystem rules Orchestration costs estimates: 50k€ ; Development costs estimates: 100k€ Funding: BF 50% for orchestration, 30% for development B Network infrastructure components C Network integration components D Finish meta-modeling tool development and finish the concept 2/2020 3/2021 Ecosystem foundations established, development projects continues

Business messages in projects and O&M
1. RequestForQuotation 2. Quotation1 3. Order1 4. OrderResponse1 5. OrderChange1 6. RequestTechnicalData2 7. DespatchTechnicalData2 8. ReceiptTechnicalData2 9. DespatchAdvice3 10. ReceiptAdvice3 11. CatalogueRequest3 12. Catalogue3 [1] Ecosystem (DBE Core) subset from original UBL 2.2 [2] Ecosystem (DBE Core) addition to UBL 2.2 [3] Not on the scope at this moment See UBL 2.2

OPEX – Workflow elements in agreement based business
Metsä Group Stora-Enso UPM Fortum Neste Wärtsilä Yara … Buyer Seller Seller Metso, Siemens, Sulzer, Endress+Hauser CatalogueRequest Catalog delivery Catalogue Order Technical information can attached to any business document Order/Call-off workflow OrderResponse DespatchAdvice Order fulfillment MESSAGES Commercial Ref. to technical Technical ReceiptAdvice RequestTechnicalData Data delivery DespatchTechnicalData ReceiptTechnicalData

CAPEX – Workflow elements in projects
EPC/EPCM Andritz, Pöyry, Sweco Supplier Metso, Siemens, Sulzer, Endress+Hauser Project Metsä Group Stora-Enso UPM Fortum Neste Wärtsilä Yara … Preliminary Request Based on engineering items CatalogueRequest Catalogue Automatic/manual 80%/20% Quotation workflow Detailed Request Based on PCE request / functional location RequestForQuotation Automatic/manual 80%/20% Quotation ProcurementProposal Technical information can attached to any business document Order workflow Order Order OrderResponse OrderResponse OrderChange OrderChange MESSAGES Commercial Ref. to technical Technical Change management OrderResponse OrderResponse DespacthAdvice ReceiptAdvice Order fulfillment RequestTechnicalData Data delivery DespatchTechnicalData ReceiptTechnicalData

Siirtymämalli Riskin jakaminen prepare
Projektin aloitus viivästyy 2 – 3 kk Riskin jakaminen prepare Orchestration step 1 Companies 25k€, Business Finland 25k€ Orchestration step 2 Companies ~25k€, Business Finland ~25k€ Orchestration step 3 Companies ~50k€, Business Finland ~50k€ 3/2019 9/2019 3/2020 3/2021 Development step 1 Companies ~70k€, Business Finland ~30k€ Development step 2 Companies ~70k€, Business Finland ~30k€

Project information mgt (CWA 16180-2)
Plant owner EPC Equipment vendor Manufacturer A C D B C requirements (OLOP) B information D information (DLOP) A specifications Number of participants 1 ~ Order of magnitude pages in documents ~1.000+ ~ ~ Lähde: CEN CWA , The CEN ORCHID Roadmap, Standardising Information across the Plant Engineering Supply Chain – Part 2: Implementation Guide, CEN September 2010

Done so far Equipment class Proposal from Reference
Additional reference Notes Automation valves Metso +PSK IEC-61987 ISO CFIHOS In-line flow meters and pressure meters Endress+Hauser IEC 61987 Centrifugal pumps Sulzer None * Asynchronous motors Siemens Siemens IEC 61360 * Corresponding attribute codes and descriptions to be specified separately (to be proposed new PSK task group)

Connecting ISO-19845 with technical standards
Each CommodityClass will have tailored asset specific schema for technical data according to corresponding ISO or IEC standard (in this case IEC-61987) Commodity Classification Document Code Asset Description 1000 10000 Automatic Valve 1001 Releef Valve 2000 Electric Drive 2001 Low Voltage AC motor 2002 Syncronous Motor 2003 Generator 3000 Process pump 3001 Centrifugal Pump 3002 Piston pump UBL concept to link Item to LineItems. Validation of asset data will be done based on CommodityClass information

Process industry information ownership
DRAFT ROLES Information group Information source by roles Information usage Buyer Engineering &design Equipment supplier Service Financing Procure-ment Engineering&design S Sales and delivery Contract data - Bilateral (or multilateral) business agreement P E W F z Procurement Functional/device location data - E.g. engineering and design M v x Engineering Administrative device data (ALOP) -E.g. contact information, purchase order ID Administrative engineering data -E.g. contact information, issuing details Maintenance Requirements for functional location (OLOP) - Engineering design/sizing Service work Device specifications (DLOP) -E.g. technical specs of device , maintenance instructions O Original equipment manufacturer Commercial device/service data - E.g. price, invoice, delivery data, incidence costs (CLOP) L Material logistics Commercial engineering data - E.g. price, invoice, delivery data, incidence costs Product/device lifecycle data (LLOP) - E.g. product fading, replacement Product catalog information - Agreement based catalogs Order financing information - Order financing for supplier or customer Material logistics -E.g. shipping list USAGE Functional/device location maintenance data -E.g. maintenance plan, maintenance history owner of the subject Device maintenance data (MLOP) - Individual device and component history authorized by the owner of the subject Functional safety data - Safety requirements and documents shared information by the nature Condition and performance monitoring data - Device health data for O&M Information sharing rules to be defined Creator owns information

Industry 4.0 RAMI 4.0 IEC-62541 OPC-UA and AutomationML in RAMI 4.0 (Reference Architecture Model Industrie 4.0) Return IEC (FDI) IEC (FDT) IEC (EDDL) Source: Automaatioväylä 6/2016

CAPEX – faster projects and less costs
Lesser business partner specific adjustments One internal solution for all business partners and one external solutions for all Digital Partners External Portal solutions for all non-digital “Transfer-file” business partners (with possible partner specific mappings) Shorter project lead times Additional costs savings and business benefits – even with non-digital transfer-file-based suppliers Better information integrity Better information quality benefits end-customers over the plant lifecycle Means lesser hassle for all parties during the project phase and in O&M Internal cost savings Lesser manual project expert work – simpler workflows, lesser hassle, lesser errors In Quotation and Order phase In Change management Smaller transactional costs – less supporting manual work to handle Opportunity for new ways to utilize external expertise Suppliers could maintain installed-base information (and connectivity to deeper equipment information) Engineering partners could maintain end-customers engineering information (cloud services) Analyst partners could easier do performance and condition monitoring services Ecosystem benefits Piloting partners creates the basic ecosystem rules

Metso ready for pilots OPEX challenges – Valve service pilot
Established practices already available Digital concept for valve exchange procedures and valve inventory management OPEX challenges – Valve condition monitoring service pilot Connection to field condition monitoring tools (e.g. FieldCare) and production performance tools (e.g. PlantTriage or LoopBrowser) Connectivity to maintenance work planning and valve service workflow CAPEX challenges – Capital investment project pilot Together with engineering companies (e.g. EPC/Andritz, EPCM/Pöyry, Sweco) Metso ready to test capital/MRO project workflows and related data exchange Metso Project Portal for Äänekoski already available (all data and documents uploaded) as a starting point Plant lifecycle business benefits Project benefits

Metso Project Portal pilot
All data and documents for 2600 delivered valves Tools to manage valve requirement data from engineering partners related to functional locations Currently simple workflows for managing valve data handover

Metso Condition Monitoring Services
Metso Service creates recommendations for actions Needs maintenance Needs inspection Maintenance work planning creates corresponding work orders for Metso

Sulzer pumps ready for pilots
OPEX challenges – Pump service pilot Established practices already available Digital concept for pump exchange procedures and pump inventory management (InvO) OPEX challenges – Pump condition monitoring service pilot Connectivity to maintenance work planning and pump service workflow PumpsOnline supporting asset information management CAPEX challenges – Capital investment project pilot Together with main product line suppliers and engineering companies (e.g. EPC/Andritz, EPCM/Pöyry, Sweco) Sulzer ready to test capital/MRO project workflows and related data exchange Plant lifecycle business benefits Project benefits

Endress+Hauser ready for pilots
OPEX challenges – Day-to-day operations Replacement equipment call-offs and other day-to-day functions Established e-procurement concept available Strong global experience supports fast pilot implementations OPEX challenges – service and asset management support Connectivity to field management tools (FDM, SMT70, …) Asset information management connectivity to maintenance management and engineering tools CAPEX challenges – Capital investment project Together with engineering companies (eg. EPC/Andritz, EPCM/Sweco, Pöyry) Ready to test capital/MRO project workflows and related data exchange Existing plant engineering connectivity to Endress+Hauser PEA Plant lifecycle business benefits Project benefits

E+H engineering and asset information support

Siemens ready for pilots
OPEX challenges – Day-to-day catalog procurement Established e-procurement concept available Strong global experience supports fast pilot implementations CAPEX challenges – Capital investment project pilot Together with engineering companies (e.g./EPC/Andritz, EPCM/Sweco, Pöyry) Ready to test capital/MRO project workflows and related data exchange Existing plant engineering connectivity to engineering systems (Comos) Plant lifecycle business benefits Project benefits

Automation of Technical Information Exchange
Proprietary & Confidential 7/29/2019 Automation of Technical Information Exchange Fixing and completing installed-base information!1 ERP, CMMS, ENG.&DESIGN SYSTEMS ERP, PDM, CRM Device data and documents Procurement data ENG. & DESIGN SYSTEMS Functional locations’ data INDUSTRY PLANT SUPPLIERS ENGINEERING DESIGN O & M data Easier workflow management!2 Shorter delivery lead times!3 Target - correct information for O & M 1Improved dependability, reduced human, environmental and plant asset risks, +1%-unit business benefits (EBIT)** 2Transactional costs reduced, +0,5%-unit business benefits (EBIT)** 3Shortened project lead times, data and documents available instantly for O&M! **ARC 2010 Collaxion Investor Presentation

Internal and external processes
Small 10% Large 90% 90% Source: IBM 10% Investment Commonly funded orchestration and development Company funded development Continuity required! Common funding! External common bodies to take care Standardization bodies Industry area specific networks (THTH, USPI, … Ecosystem board Company funded maintenance Standards preferred to be based on ISO/IEC Maintenance Commonly agreed business issues Data models & semantics Workflows, intercompany business processes Ecosystem rules and principles External Common technology agnostic specifications Technology enables the solution - Network infrastructure (infrastructure components) Capability to exchange information (integration components) Internal Company’s own solutions External processes – intercompany connections – external process integration Internal process integration

Alternatives for improving efficiency
Information exchange to be agreed separately with every business partner. Automatic workflows (point-to-point APIs). Information exchange agreed on ecosystem level. Automatic workflows (commonly agreed APIs). Current situation Manual workflows. Ecosystem Point-to-point Manual Automatic Every company has its own APIs No interoperability Companies have ecosystem approved APIs Yes – interoperability in digital operations Companies don’t have digital workflows Yes – interoperability in manual operations Digitalization is proceeding digitalization

Technical Information Exchange development
Process industry focus is in Technical information exchange (TIE) project Is an integral part of the DBE Core ecosystem concept Project and O&M gives special process industry requirements for the ecosystem Fast track from tech information standards to open solutions needed Together with global technical standardization bodies for process industry (USPI-NL, CFIHOS, PSK, SSG, PCA, …) In collaboration with commercial business standardization bodies (OASIS, UBL 2.3 ISO/IEC-19845) Continuous solutions to maintain data models and open ecosystem components  Meta-modelling concept Network infrastructure and integration model to be agreed and developed Ecosystem rules and principles to be commonly agreed  Governance model Integration and infrastructure components to be developed Appropriate testing facilities to support companies’ backend systems integration Technical Information Exchange (TIE) project THTH driven – process industry companies participating Business Finland ecosystem status approval means 50% public funding for Orchestration work

Transportation and logistics
Development tasks 1 5 3 2 Orchestration Common development Companies’ internal THTH specific 4 6 DBE Core Framework Transportation and logistics Maritime

Open ecosystem development “organization”
THTH Process industry (projects and O&M in forest, chemical and energy industry) Maritime industry CAAS Nordic Transport and logistics Finance and insurance OWG – Operative Work Groups Manage business requirements Manage orchestration and common development Nominate representatives for Board TIE THTH project TIE is one project in larger business framework OWG OWG OWG OWG DBE Core Ecosystem Orchestration Board Association to be founded TWGs Technical Working Groups together with commonly selected development partners Companies’ PoC projects and own development A. Network rulebook definition & development Development work B. Common network infrastructure development C. Network integration & testing D. Common technical data models Members participate in activities DBE Core Ecosystem Orchestration Board Manage orchestration funding Coordinate common development targets Ecosystem member companies

Open ecosystem development schedule
Orchestration and common development on all other business areas 5/2019 11/2019 6/2021 6/2020 THTH TIE Orchestration sub-project phases Phase 1 with PoC-based network development Phase 2 with small scale network piloting Phase 3 With partial production ramp-up Phases may overlap in practice A. Network rulebook definition & development D. Common technical data models B. Common network infrastructure development C. Network integration & testing Deliverable: Rulebook Deliverable: Infra codebase & running network Deliverable: Integration codebase, test network Deliverable: Data model governance concept PoC Pilot common network functionalities Production network (ramp-up mode) Member activities Process industry Orchestration & Ecosystem common development Members’ activities (PoC’s, etc) feed input to ecosystem activities for finalizing the deliverables Color codes: process industry, companies, orchestration, common development

Business Finland expectations
THTH to collect process industry summary Each company should give its own rationales for the estimates

as a part of DBE Core Ecosystem Orchestration

Similar presentations

Presentation on theme: "as a part of DBE Core Ecosystem Orchestration"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

as a part of DBE Core Ecosystem Orchestration

Similar presentations

Presentation on theme: "as a part of DBE Core Ecosystem Orchestration"— Presentation transcript:

Similar presentations

About project

Feedback