SAP Remote Logistics Management (RLM)
Solution Overview and History
What is SAP RLM ?
Operators of remote oil and gas production facilities need an efficient means of supplying and re-supplying those locations. But if your company is like most, remote platform re-supply is not an integrated part of your overall business support systems. You need an integrated software solution to ensure your platforms remain fully operational with the supply of parts and materials on a right-on-time basis. SAP Remote Logistics Management (RLM) meets that requirement. It provides a solution that seamlessly integrates your remote logistics with all your other logistics processes.
SAP AG 2006
SAP RLM How did it start?
Shell, Phillips and Statoil had each developed in-house remote logistics solutions 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 and high levels of tracking capability The RLM development partner group was formed and SAP worked with them in scoping the requirements for the RLM solution Since its release in 2001 RLM has seen a high level of acceptance in the market with a dozen operators now active. These users have formed an active focus group RLMFoG with the approval of the Global Industry Advisory Council Ensures a broad representation of the industry in the roll-in process and helps new implementors in networking
SAP AG 2006
Business Problem
Unique Aspects of Remote Operations
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 for use
High transportation costs for deliveries to remote facility Need to consolidate shipments One voyage to multiple remote facilities
SAP AG 2006
Business Issues and Needs
Customer Requirements
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
SAP AG 2006
Whats in a name?
Originally called the solution Offshore Logistics Management The term Offshore was misleading solution supports remote operations whether offshore or onshore Renaming allows us to more easily position the solution in other industry sectors eg Mining
and
SAP AG 2006
RLM Introduction: Component Overview
External vendor
Base plant
Shipping / supply
Remote plant
Returns
Goods receipt, holding, packing
Material tracking
SAP AG 2006
RLM Introduction: Scope of RLM
SAP AG 2006
RLM Work Processes
Requisitioning (recommendation: use PM / PS orders)
Supply chain system utilities (automations)
Goods receipt (GR) at base Shipping / packing
Voyages Shipments Containers Deliveries
Rentals material mobilization Return documents
Rentals material demobilization Return for temporary holding Returns work list (change or display)
Material tracking (monitoring tool for all users)
SAP AG 2006
RLM Areas
Procurement
RLM-S RLM-G Supply Chain Goods Receipt
Dispatch
RLM-P RLM-H RLM-M Shipping and Container Management Material Holding Material Tracking
Returns
RLM-R Returns Management
SAP AG 2006
Procurement: Supply Chain Processing
Material Request Supply Chain Processing Material Issue
Purchase Request Purchase Order
Material Reservation
Transport Request Transport Order
SAP AG 2006
RLM-S: Supply Process Examples
PM Order
Material Request
Stocked Offshore Stocked Onshore
Supply Process
Manual Requisition
Gasket O-Ring Spacer Valve
01 02 03 04
PS Network Order
SAP AG 2006
RLM-S Supply Process: Stock/Stock
ST/ST Material: stock at remote plant and base plant
An RLM conversion program converts transport req. to transport order.
Remote plant
PM Order Reservation Network
Stock Available
RLM maintains a link between [Link]. and [Link].
No Stock Available
MRP
Tr. Req.
Conversion
Tr. Order
Delivery ref. to Tr. Order
Base plant MRP
No Stock Available
Stock Available
Purch. Req.
[Link]
Goods Rec.
SAP AG 2006
RLM-S Supply Process: Non-Stock/Stock
NS/ST Material: Stock at base plant only
An RLM conversion program converts transport req. to transport order.
Remote plant
PM Order
The creation of tr. req. (instead of purch. req.) is controlled by RLM. Tr. Req.
RLM maintains a link between tr. req. and purch. req.
Conversion
Tr. Order
Network
Delivery ref. to Tr. Order
Base plant MRP
No Stock Available
Stock Available
Purch. Req.
[Link]
Goods Rec.
SAP AG 2006
Procurement: Goods Receipt Processing
Material Request Supply Chain Processing Material Issue
Purchase Request Purchase Order
Material Reservation
Goods Receipt
Outbound Delivery
Outbound Shipment
Transport Request Goods Receipt Processing Transport Order
SAP AG 2006
RLM-G: Automatic Deliveries
Goods Receipt
Goods Receipt Note (GRN) Document Flow
Delivery Note
Cross-Docking Report
Packing Program
SAP AG 2006
Dispatch: Shipping and Container Management
Material Request Supply Chain Processing Material Issue
Purchase Request Purchase Order
Shipping & Container Management
Container Material Reservation Material Receipt Outbound Shipment
Goods Receipt
Outbound Delivery
Transport Request Goods Receipt Processing Transport Order
SAP AG 2006
RLM-P: Flexible Container Master
Display Container
Flexible Container Master Generic Functions Container Types
Read Select Display Value Request Lock Unlock RLM containers PM Equipment Internet (customer functions) One-off containers Other ...
Handling Units
Packing
Container tracking
SAP AG 2006
RLM-P: Packing and Loading
Loading Area
Container
Shipment Delivery
Container
Holding Area
Container
SAP AG 2006
Dispatch: Material Holding
Material Request Supply Chain Processing Material Issue
Purchase Request Purchase Order
Shipping & Container Management
Material Holding
Container Material Reservation Material Receipt Outbound Shipment
Goods Receipt
Outbound Delivery
Transport Request Goods Receipt Processing Transport Order
SAP AG 2006
RLM-H: Hold Delivery
PM Order PM Order Operation Hold Delivery Component Hold Delivery Block Shipping Block X X
Item
Hold
SAP AG 2006
Dispatch: Material Tracking
Material Request Supply Chain Processing Material Tracking Material Reservation Material Receipt Outbound Shipment Material Issue
Purchase Request Purchase Order
Shipping & Container Management
Material Holding
Container
Goods Receipt
Outbound Delivery
Transport Request Goods Receipt Processing Transport Order
SAP AG 2006
RLM-M: Tracking Report Layout
Tracking profile Tracking group Tracking status
Document flow profile
SAP AG 2006
Returns: Returns Management
Material Request Supply Chain Processing Material Tracking Material Reservation Material Receipt Outbound Shipment Material Issue
Purchase Request Purchase Order
Shipping & Container Management
Material Holding
Container
Goods Receipt
Outbound Delivery
Transport Request Goods Receipt Processing Transport Order
Returns Handling
SAP AG 2006
RLM-R: Returns Business Process
SUPPLY
Material Reservation MRP Purchase Requisition Requisition Conversion Network Order Direct Procurement Transport Requisition Transport Order Purchase Order PO Goods Receipt
Order PM Order
DISPATCH
Goods Issue for Delivery
Outbound Delivery Initial Delivery
Delivery Due List RLM XDocking
Goods Receipt for Delivery
Shipment receipt offshore
Repeat Delivery
Create return w/ref to order
Repeat delivery cycle
Material Return
Return Delivery
Goods Issue for Delivery Shipment receipt onshore
Create repeat delivery
RETURNS
Goods Receipt for Delivery
SAP AG 2006
VMIS Introduction: Scope of VMIS
Voyage Management and Information System (VMIS)
Functional enhacement of RLM Overview of all voyages in the RLM supply process to remote locations Support of Planning and Scheduling of voyages Execution of RLM functions via VMIS in a simplified way Shipment with ERP 6.0 (ERP 2005) Enhancement Pack 3 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 to be 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 any time without notice.
SAP AG 2006
Voyage and Shipments in RLM
Location A
Location B
Location C
RLM groups shipments to multiple locations into a voyage. A shipment to a remote location will normally have a return shipment (e.g. return of materials and containers to supply base ) Also transfer shipments between remote locations are possible
Base Location
Enhancement of existing RLM Voyage object in VMIS
SAP AG 2006
VMIS Scenario
Example: Supply-Vessels going to Upstream Offshore Platforms
Plattform B
Supply Base Supply Vessel
Plattform A
Plattform C
Plattform D
SAP AG 2006
VMIS: Main Functionality
VMIS supports planning, estimation and execution of voyages 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
SAP AG 2006
1: General Concept for Vehicles
Functionality of Vehicle Master from Transportation and Distribution (TD) now used in RLM. TD Master Data concept can be used to model vehicles used in the supply process to remote locations (e.g. supply-vessels)
Vehicle
SAP AG 2006
Vehicle: VMIS Attributes
To support planning in VMIS additional attributes were added to the vehicle.
Average Speed + UoM for Speed E-mail address / Fax / phone number
Travel time calculations
MS Maria
Fields for arrival buffer + departure buffer
Travel time calculations
Additional Vehicle attributes
SAP AG 2006
Vehicle: VMIS Rescue Material
Enhancement of the existing TD Vehicle Master for VMIS with the required information on the rescue equipment on the vehicle
New Rescue Equipment sub-screen
MS Maria
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 are introduced (e.g. Base Location, Remote Location company operated, Remote Location partner operated). Location type is controlling screen layout with mandatory/optional fields.
Business Location: Platform-B Type: Remote Location Business Location: Platform-A Type: Remote Location
Business Location: Base-1 Type: Base Location
Business Location: Platform-C Type: Remote Location
SAP AG 2006
Business Locations Concept for VMIS
Business location master data concept used in VMIS
Business Location Master Data
Address Status RLM General Roles Object links Location address Location status Location Shipment data Partner role assignments Links to MM, CO, FI, PM,.
SAP AG 2006
VMIS Location concept: Address and RLM screen
Address Screen Geo coordinates from Business Location and speed from vehicle will allow distance and travel time calculations
RLM general screen
RLM general screen RLM general screen holding defaulting information for automatic creation of shipments
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 status information Check conflict of voyage with opening hours or events like maintenance
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 procedure within 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
From the list of all shipments in a voyage it is possible to directly access via buttons the most important RLM functions
RLM will appear much more dynamic with VMIS and improve RLM usability in an enormous way
SAP AG 2006
5: Voyage Selection and Overview
Voyage Selection Flexible voyage selection
Automatic defaulting of user specific selection variants possible, as different group of users (e.g. Base, Marine Control Center, Platform) will work with VMIS
SAP AG 2006
Voyage Selection and Overview
Voyage Overview Screen Overview about Voyages and their destinations
Icons are giving information about the actual position of a vehicle in a voyage
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 be changed 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, [Link], xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered 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 respective companies. 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 prior written 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 this document 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 items contained 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 of merchantability, 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 in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.
SAP AG 2006
