12
Beyond RLM at Equinor Status and plans for Equinor to replace current RLM (Remote Logistics Management) functionality when moving to S/4HANA. SBN – Energy Day, 9th March 2021 Geir Aakre, Principal Analyst IT Architecture, Equinor

Beyond RLM at Equinor - Amazon S3

  • Upload
    others

  • View
    5

  • Download
    0

Embed Size (px)

Citation preview

Page 1: Beyond RLM at Equinor - Amazon S3

Beyond RLM at EquinorStatus and plans for Equinor to replace currentRLM (Remote Logistics Management) functionality when moving to S/4HANA.

SBN – Energy Day, 9th March 2021Geir Aakre, Principal Analyst IT Architecture, Equinor

Page 2: Beyond RLM at Equinor - Amazon S3

Open 20 March 2019

RLM – Key facts

Fully supported in SAP ECC until

31.12.2025

Fully supported in SAP S/4HANA

Compatibility Packs until

31.12.2025

Goal

2 |

RLM on SAP IS-OIL ECC 6.0 on HANA

SAP S/4 HANAReplace and improve “RLM functionality” as a first step on our move to S/4HANA journey

Page 3: Beyond RLM at Equinor - Amazon S3

Open 20 March 2019

Why

• 20 years old SAP SCM solution

• Don’t utilize modern technology in warehouse operations

• Old GUI

• Need to be on SAP S/4 within 2025

• RLM, WM, EH&S, etc. not maintained by SAP after 2025

• Transition to S/4 is a huge project -> BRLM is first step

• A modern trustworthy IT tool supporting our complex, modernised and automated work processes

3 |

Page 4: Beyond RLM at Equinor - Amazon S3

Open 20 March 20194 |

2020 2020

Page 5: Beyond RLM at Equinor - Amazon S3

Open 20 March 2019

Equinor has complex

work processes.

Requires complex(yet standardized)

IT systemsto support this

BRLM components

• SAP ERP (Enterprise Resource Planning)

• EWM (Extended Warehouse Management)

• TM (Transportation Management)

• TCD (Transportation Cross Docking)

• ARM (Advanced Return Management) ???

• EM/GTT (Event Management/Global Track & Trace) ???

• Integration to WELS

5 |

Page 6: Beyond RLM at Equinor - Amazon S3

Open 20 March 2019

Material numbers

• EWM processes requires material numbers for all materials

• For former text requisitions, a non-valuated material number is created automatically.Ongoing discussion if this material number should be deleted after fulfilment of the process, or if should keep it for future use

• For catalogue requisitions (without material number), a non-valuated material number is created automaticallyProposal:

• The catalogue item will be updated with a reference to the material number

• The next time the catalogue item is used, the same non-valuated material number is used.

6 |

Page 7: Beyond RLM at Equinor - Amazon S3

Open 20 March 2019

Supply processes

7 |

SP1 - Stock/Stock

SP2 – Non stock/Stock

SP3 – Stock/Non stock

SP4 – Non stock/Non stock E x a m p l e

SP1, refilling of

platform stock from

supply base stock

Page 8: Beyond RLM at Equinor - Amazon S3

Open 20 March 2019

Many new objects in BRLM (EWM, TM, TCD…)

Some examples:

• ASN – Advance Shipping Notification

• Inbound delivery

• FO - Freight Order

• FU – Freight Unit

• TU – Transportation Unit

• TR – Transportation Request

• PMR – Production Material Request

• Etc.

8 |

Page 9: Beyond RLM at Equinor - Amazon S3

WELS enhancements

9

1 3

22

5

1

4

3

4 a)5

6

4 b)

1. Decommission Vessel Transportation Management Information System (VTMIS) in SAP ERP, and establish the corresponding functionality for voyage planning and execution in WELS

2. Decommission VTMIS/SAP dependent applications and establish corresponding functionality based on voyage planning and execution in WELS, i.e. replace ‘Vessel log’ and ‘VTMIS on Web’ with corresponding, functionality based on enhanced ‘WELS Reporting client’

3. Move cost capturing and allocation logic from SAP to WELS, i.e. move the basis for cost allocation from SAP to WELS, but carry out cost distribution and financial postings in SAP ERP

4. Enhance cargo package functionality in WELSa) to handle transportation needs related to Equinor owned material b) and to handle 3rd party transportation needs with an SAP work order reference

5. Required interfaces to exchange voyage and cargo information, during planning and execution, between SAP and WELS

6. WELS app improvements/enhancements for efficient cargo operations, i.e. loading and unloading at supply base and installation

7. Determine potential additional requirements from hybrid scenarios like ‘subsea’ and OCTG

8. Determine requirements related to land transport of 3rd party materials originating from WELS, e.g. ASN messages

Page 10: Beyond RLM at Equinor - Amazon S3

Equinor Beyond RLM High-level Plan (only O&G)2020 2021 2022des jan feb mar apr mai jun jul aug sep okt nov des jan feb mar apr mai jun jul

Sprint 7Functional Test (incl. Summer and Xmas Holiday)Delivery of FeaturesIntegration Test

28.02.2022Acceptance of FeaturesUser Acceptance TestPerformance Test

Realize Phase

End-user TrainingCutover

12.06.2022

11.01.2021Prepare Phase

Go-live Support

Sprint 1

Sprint 4

Project PreparationExplore Phase

Sprint 2

Activity

Sprint 6

09.01.2022

Deploy Phase Pilot

Sprint 5

Project Kick-off

Summer Holiday (Equinor)

Specification/Backlog Refinement(incl. Summer Holiday)

Sprint 3

Go-live

Page 11: Beyond RLM at Equinor - Amazon S3

Timeline

12

Functional specification Voyage execution

ProcurementInterface studies WellIT

Development Interface and voyage scope

Page 12: Beyond RLM at Equinor - Amazon S3

© Equinor ASA

This presentation, including the contents and arrangement of the contents of each individual page or the collection of the pages, is owned by Equinor. Copyright to all material including, but not limited to, written material, photographs, drawings, images, tables and data remains the property of Equinor. All rights reserved. Any other use, reproduction, translation, adaption, arrangement, alteration, distribution or storage of this presentation, in whole or in part, without the prior written permission of Equinor is prohibited. The information contained in this presentation may not be accurate, up to date or applicable to the circumstances of any particular case, despite our efforts. Equinor cannot accept any liability for any inaccuracies or omissions.

Geir Aakre, Principal Analyst IT Architecture, Equinor

Beyond RLM at Equinor