SAP RLM Overview

Solution Overview and History

SAP Remote LogisticsManagement (RLM)

SAP AG 2006

Operators of remote oil and gas production facilities need an efficientmeans of supplying and re-supplying those locations. But if your companyis like most, remote platform re-supply is not an integrated part of youroverall business support systems.

You need an integrated software solution to ensure your platforms remainfully operational with the supply of parts and materials on a ‘right-on-time’basis.

SAP Remote Logistics Management (RLM) meets that requirement. Itprovides a solution that seamlessly integrates your remote logistics withall your other logistics processes.

What is SAP RLM ?

SAP AG 2006

Shell, Phillips and Statoil had each developed in-house remote logisticssolutions

These were proving labour-intensive and costly to maintain

They wanted a solution which was integrated with SAP functionality

The solution should provide automation of the requisitioning process andhigh levels of tracking capability

The RLM development partner group was formed and SAP worked withthem in scoping the requirements for the RLM solution

Since its release in 2001 RLM has seen a high level of acceptance in themarket with a dozen operators now active.

These users have formed an active focus group RLMFoG with theapproval of the Global Industry Advisory Council

Ensures a broad representation of the industry in the roll-in process andhelps new implementors in networking

SAP RLM – How did it start?

SAP AG 2006

• Remote location - not easily reached

• May be no regular transportation channel

• Requires special shipping arrangements

• Warehouse is located apart from the operations

• Onshore supply bases

• Small storage capacity at operations site

• May need to hold materials at intermediate location until ready foruse

• High transportation costs for deliveries to remote facility

• Need to consolidate shipments

• One voyage to multiple remote facilities

Unique Aspects of Remote Operations

Business Problem

SAP AG 2006

• Empowerment of requisitioners

• Efficient procedures for serving remote locations from supply bases

• Reduced overheads for requisitioning through remote supply chain

• Vendor support

• Replace existing custom or other third-party solutions

• Must not be single customer-specific

• Maximum integration with SAP core

Customer Requirements

Business Issues and Needs

SAP AG 2006

Originally called the solution ‘Offshore Logistics Management’

The term ‘Offshore’ – was misleading – solution supports remoteoperations whether offshore or onshore

Renaming allows us to more easily position the solution in other industrysectors eg Mining

What’s in a name?

and

SAP AG 2006

RLM Introduction: Component Overview

Externalvendor

Base plantRemote

plantShipping / supply

Returns

Goods receipt,holding,packing

Material tracking

SAP AG 2006

RLM Introduction: Scope of RLM

SAP AG 2006

Requisitioning (recommendation: use PM / PS orders)Supply chain system utilities (automations)

Goods receipt (GR) at base

Shipping / packingVoyagesShipmentsContainersDeliveries

Rentals material mobilization

Return documentsRentals material demobilizationReturn for temporary holdingReturns work list (change or display)

Material tracking (monitoring tool for all users)

RLM Work Processes

SAP AG 2006

RLM Areas

ProcurementRLM-S Supply Chain

RLM-G Goods Receipt

DispatchRLM-P Shipping and Container Management

RLM-H Material Holding

RLM-M Material Tracking

ReturnsRLM-R Returns Management

SAP AG 2006

PurchaseRequest

Procurement: Supply Chain Processing

MaterialIssue

MaterialRequest

PurchaseOrder

TransportRequest

TransportOrder

MaterialReservation

Supply ChainProcessing

SAP AG 2006

Supply Process

RLM-S: Supply Process Examples

Material Request

StockedOffshore

StockedOnshore

GasketO-RingSpacerValve

01020304

ManualRequisition

PM Order

PS NetworkOrder

SAP AG 2006

RLM-S Supply Process: Stock/Stock

ST/ST Material: stock at remote plant and base plant

Remote plant

PM Order

Network

Reservation Tr. Req. Conversion Tr. OrderMRP

StockAvailable

No StockAvailable

An RLM conversion programconverts transport req. totransport order.RLM maintains a link betweentr.req. and purch.req.

Deliveryref. to Tr. Order

Base plant

MRP

Purch. Req.

No StockAvailable

Purch.Order Goods Rec.

StockAvailable

SAP AG 2006

RLM-S Supply Process: Non-Stock/Stock

NS/ST Material: Stock at base plant only

Remote plant

PM Order

Network

Tr. Req. Conversion Tr. Order

An RLM conversion programconverts transport req. totransport order.RLM maintains a link betweentr. req. and purch. req.The creation of tr. req.

(instead of purch. req.)is controlled by RLM.

Base plant

MRP

Purch. Req.

No StockAvailable

Purch.Order Goods Rec.

StockAvailable

Deliveryref. to Tr. Order

SAP AG 2006

Procurement: Goods Receipt Processing

PurchaseRequest

MaterialIssue

MaterialRequest

PurchaseOrder

TransportRequest

TransportOrder

OutboundShipmentOutbound

DeliveryGoodsReceipt

Goods ReceiptProcessing

MaterialReservation


SAP AG 2006

RLM-G: Automatic Deliveries

Goods Receipt GoodsReceipt Note

(GRN)

DeliveryNote

DocumentFlow

Cross-Docking ReportPacking Program

SAP AG 2006

Dispatch: Shipping and Container Management

PurchaseRequest

MaterialReservation

MaterialIssue

MaterialRequest

PurchaseOrder


TransportRequest

TransportOrder




MaterialReceipt

Container

Shipping &Container

Management

SAP AG 2006

RLM-P: Flexible Container Master

DisplayContainer

Flexible Container Master

ReadSelectDisplayValue RequestLockUnlock

Generic FunctionsRLM containers

Container Types

PM Equipment

Internet (customer functions)

One-off containers

Other ...

HandlingUnits

Containertracking

Packing

SAP AG 2006

RLM-P: Packing and Loading

Holding Area

Loading Area

Delivery

Container

Container

Shipment

Container

SAP AG 2006

Dispatch: Material Holding

PurchaseRequest

MaterialReservation

MaterialIssue

MaterialRequest

PurchaseOrder


TransportRequest

TransportOrder




MaterialReceipt

Container

Shipping &Container

ManagementMaterialHolding

SAP AG 2006

RLM-H: Hold Delivery

PM Order

Delivery

Delivery Block

Shipping Block

Operation Hold

PM Order

Component Hold

Item Hold

X

X

SAP AG 2006

Dispatch: Material Tracking

PurchaseRequest

MaterialReservation

MaterialIssue

MaterialRequest

PurchaseOrder


TransportRequest

TransportOrder




MaterialReceipt

Container

Shipping &Container


MaterialTracking

SAP AG 2006

RLM-M: Tracking Report Layout

Documentflow profile

Trackingstatus

Trackingprofile

Trackinggroup

SAP AG 2006

Returns: Returns Management

PurchaseRequest

MaterialReservation

MaterialIssue

MaterialRequest

PurchaseOrder


TransportRequest

TransportOrder




MaterialReceipt

Container

Shipping &Container


MaterialTracking

ReturnsHandling

SAP AG 2006

RLM-R: Returns – Business Process

Order

PM Order NetworkOrder

PurchaseRequisition

TransportRequisition

TransportOrder

PurchaseOrder

PO GoodsReceipt

OutboundDelivery

InitialDelivery

RepeatDelivery

MaterialReservation MRP

DirectProcurement

DeliveryDue List

RLM X-Docking

GoodsIssue forDelivery

GoodsReceipt for

Delivery

Createreturn w/ref

to order

MaterialReturn

Createrepeat

deliveryReturn

Delivery

Shipmentreceipt

offshore

Shipmentreceipt

onshore

GoodsIssue forDelivery

GoodsReceipt for

Delivery

SUPPLY

DISPATCH

RETURNS

RequisitionConversion

Repeat delivery cycle

SAP AG 2006

Voyage Management and Information System (VMIS)

Functional enhacement of RLM

Overview of all voyages in the RLM supplyprocess to remote locations

Support of Planning and Scheduling of voyages

Execution of RLM functions via VMISin a simplified way

Shipment withERP 6.0 (ERP 2005) Enhancement Pack 3

VMIS Introduction: – Scope of VMIS

VMIS

RLM

Note: The information in this Roadmap is proprietary of SAP. This document contains only intended strategies, developments, and/or functionalities of the SAP product and is not intended tobe binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at anytime without notice.

SAP AG 2006

Voyage and Shipments in RLM

BaseLocation

LocationA

LocationB

LocationC

RLM groups shipments to multiplelocations into a voyage.

A shipment to a remote location willnormally have a return shipment (e.g.return of materials and containers tosupply base )

Also transfer shipments between remotelocations are possible

Enhancement of existing RLM Voyage object in VMIS

SAP AG 2006

Supply Base

Supply Vessel

VMIS Scenario

Plattform A

Plattform D

Plattform B

Plattform C

Example: Supply-Vessels going to Upstream OffshorePlatforms

SAP AG 2006

VMIS: Main Functionality

1. Master Data Concept for Vehicles (e.g. supply vessels)

2. Master Data Concept for Locations (e.g. offshore platforms)

3. Voyage creation with “drag and drop” and creation of shipments(automatic or manual)

4. Execution of RLM functions from VMIS

5. Voyage Selection and Overview

VMIS supports planning, estimation and execution of voyages

SAP AG 2006

1: General Concept for Vehicles

Vehicle

Functionality of Vehicle Master from Transportation and Distribution (TD) nowused in RLM. TD Master Data concept can be used to model vehicles used inthe supply process to remote locations (e.g. supply-vessels)

SAP AG 2006

Vehicle: VMIS Attributes

To support planning in VMIS additional attributeswere added to the vehicle.

Average Speed + UoM for Speed Travel time calculations

E-mail address / Fax / phone number

Fields for „arrival buffer“ + „departure buffer“ Travel time calculationsMS Maria

Additional Vehicle attributes

SAP AG 2006

Vehicle: VMIS Rescue Material

Enhancement of the existing TD Vehicle Masterfor VMIS with the required information on therescue equipment on the vehicle

MS Maria

New Rescue Equipment sub-screen

Rescue Material types defined in Customizing

SAP AG 2006

2: Business Location concept for VMIS

Based on the general business location concept, RLM/VMIS location types areintroduced (e.g. Base Location, Remote Location company operated, RemoteLocation partner operated). Location type is controlling screen layout withmandatory/optional fields.

Business Location: Base-1Type: Base Location

Business Location: Platform-AType: Remote Location

Business Location: Platform-BType: Remote Location

Business Location: Platform-CType: Remote Location

SAP AG 2006

Business Locations Concept for VMIS

Business location master data concept used in VMIS

Business Location Master Data

Address Location address

Status Location status

RLM General Location Shipment data

Roles Partner role assignments

Object links Links to MM, CO, FI, PM,….

SAP AG 2006

VMIS Location concept: Address and RLM screen

Address Screen

Geo coordinates from BusinessLocation and speed from vehiclewill allow distance and traveltime calculations

RLM general screen

RLM general screen holdingdefaulting information forautomatic creation of shipments

RLM general screen

There are two options for route determination:Via via shipment route or connection points

SAP AG 2006

VMIS Location concept: Location Status

Location Status

Concept for location statusinformation

Check conflict of voyage withopening hours or events likemaintenance

Entry of multiple overlapping critical date/time windows is possible.Creation of overlapping entries with red, yellow or green traffic lights

SAP AG 2006

3: Create/Change Voyage with “Drag and Drop”

The creation of a voyage going to multiple locations is currently a complex procedurewithin RLM with a lot of manual work steps and the risk of errors.With VMIS this task can be done with “drag and drop” in an intuitive way.

SAP AG 2006

4: Execute RLM Functions from VMIS

RLM will appear much more dynamic with VMIS and improve RLM usability inan enormous way

From the list of all shipments in a voyage it is possible to directly access via buttons the mostimportant RLM functions

SAP AG 2006

5: Voyage Selection and Overview

Flexible voyage selection

Voyage Selection

Automatic defaulting of user specific selection variants possible, as different group ofusers (e.g. Base, Marine Control Center, Platform) will work with VMIS

SAP AG 2006

Voyage Selection and Overview

Voyage Overview Screen

Icons are giving information about theactual position of a vehicle in a voyage

Overview about Voyages and their destinations

SAP AG 2006

Copyright 2006 SAP AG. All Rights Reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may bechanged without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner,WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks orregistered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respectivecompanies. Data contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express priorwritten permission of SAP AG.

This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments,and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that thisdocument is subject to change and may be changed by SAP at any time without notice.

SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other itemscontained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties ofmerchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials.This limitation shall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained inthese materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

Documents

SAP RLM Overview