BBP For ESI Asset Supply Chain - V1.2

ESI ASSETS AND SUPPLY CHAIN PROJECT
BUSINESS BLUEPRINT
Doc-ID
ESI Assets SC_BBP_V0.21
Version
0.21
Type
FinalDraft Version
Status
Not Released
Issue Date
5 Mar 2015
Version History
Version
0.1
0.2
Date
Author
05/03/2015
07/05/2015
ESI Asset SCM Project

Business Blue Print
Remark
TCS
TCS
First Version of BBP Document

Final version of BBP document
Version: 0.1
Page 1 of 107
REVIEWERS
Version
Date
Name
Position
J Charlton
Solution Architect
Manus Walsh
Steve Thomas
Steve Richards
Project Manager (IS)
David Curran
Wendy Ongayo
Simon King
Veeresham
Katkoori
Andy Buckley
Paul Abbot
Lee Marchant
Robert Banks
Contracts Supplier
manager
Operational
Excellence manager
Project SMEs
Business Analyst
BGSM Senior
business change
managers
Senior Test Manager
James Edwards
Test ManagerService
Designer
Service Design
Huijin Liu
Application Security
Anders Barker
Data protection
manager
Solution Architect:
Integration Hub
Urban Bettag

Business Blue Print
Remarks
Version: 0.1
Page 2 of 107
Jagjit Singh
Dave Hipwell
Paul Green
Solution Architect:
Customer Journeys
Solution Architect:
ESI
Solution Architect:
mobile app
SIGNOFF
Version
Date
Name
Position
Glynn Williams
Project Sponsor
Chris Snowden
Lead Solution
Architect
Business change
programme
manager: Enduring
Effectiveness
DHL: CDC manager
Dan Healey
Andy White
Martin Kennedy
Emma Wells
Robert Cox
Avi Sengupta
Phil Davies
Nicola Roteglia
Lakshmanan
Melarcode
Ramachandran
Aneal Kerai
John Craig

Business Blue Print
Remarks
Smart commercial
manager
Smart inventory
manager
Head of STO
Development
Manager
Information Security
Business Solutions
Architect
Capacity &
Performance
Manager
Security and Risk
Manager
Director of Field
Operations
Version: 0.1
Page 3 of 107
Russ Coates
Asset Management
manager
Contents
1. INTRODUCTION........................................................................................... 97
1.1.
1.2.
1.3.
1.4.
PURPOSE..................................................................................................................... 97
PROJECT GOALS............................................................................................................ 97
BUSINESS OBJECTIVE..................................................................................................... 97
OUTCOMES................................................................................................................ 108
2. IMPACTED BUSINESS PROCESS...................................................................119

2.1. INBOUND PROCESS...................................................................................................... 119
2.1.1. Warehouse Replenishment...............................................................................119
2.1.1.1. Forecasting and MRP.................................................................................................. 119
2.1.1.2. Ordering Process level 4........................................................................................ 2018
2.1.2.
2.1.3.
ASN and Inbound delivery..............................................................................2521

Goods Receipt at CDC....................................................................................3330

Business Blue Print
Version: 0.1
Page 4 of 107
3. OUTBOUND PROCESS...............................................................................4840
3.1.
3.2.
3.3.
3.4.
3.5.
3.6.
3.7.
BUSINESS PROCESS DESCRIPTION (AS-IS)......................................................................4840

BUSINESS REQUIREMENT/EXPECTATION..........................................................................5345
BUSINESS PROCESS DESCRIPTION (TO BE SOLUTION)......................................................5546
PROCESS FLOW (TO-BE)............................................................................................ 6554
EXCEPTION HANDLING................................................................................................ 6654
SYSTEM CONFIGURATION............................................................................................. 6855
DEVELOPMENT CONSIDERATION....................................................................................7155
4. METER RETURN AND TRIAGE.....................................................................7457

4.1. ASSET RETURNS FROM WALL TO CDC...........................................................................7557
4.1.1. Removal of Asset from the Property...............................................................7557
4.1.2. Asset drop off at Royal mail site.....................................................................8665
4.1.3. Return asset receipt at CDC...........................................................................9069
4.2. RETURN TO VENDOR PROCESS AS IS...........................................................................9575
4.2.1. Business Process As Is.................................................................................9675
4.2.1.1. Return Asset for Triage............................................................................................. 9675
4.2.1.2. Return Asset to MAP................................................................................................. 9677
4.2.1.3. Return Asset to Manufacturer................................................................................... 9677
4.2.2.
Business Requirement/Expectation................................................................9777
4.2.3.
Business Process Description -TO BE..............................................................9878
4.2.2.1. Return Asset for Triage............................................................................................. 9777

4.2.2.2. Return Asset to MAP................................................................................................. 9777
4.2.2.3. Return Asset to Manufacturer................................................................................... 9777
4.2.3.1.
4.2.3.2.
4.2.3.3.
4.2.3.4.
4.2.3.5.
4.2.3.6.
Return Asset for Triage............................................................................................. 9878

Return Asset to MAP................................................................................................. 9878
Return Asset to Manufacturer................................................................................... 9878
Process Flow........................................................................................................... 10080
System Configuration Considerations..................................................................... 10080
Development Considerations.................................................................................. 10383
5. BUSINESS PROCESS EXCEPTION MANAGEMENT........................................10584

5.1.
5.2.
5.3.
5.4.
BUSINESS PROCESS................................................................................................. 10685

BUSINES PROCESS AREA........................................................................................... 10785
CLARIFICATION CASE TYPE........................................................................................10785
SYSTEM CONFIGURATION CONSIDERATIONS...................................................................10785
66. APPENDIX..............................................................................................10988
7. Non Functional Requirement.................................................................................................................................89

Business Blue Print
Version: 0.1
Page 5 of 107

Business Blue Print
Version: 0.1
Page 6 of 107
List of Figures
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
FIGURE
1: INBOUND ARIS PROCESS DIAGRAM AS IS.................................................................1111

2: FORECASTING AND MRP ARIS PROCESS DIAGRAM AS IS............................................1212
3: SMETS2 COMMS HUB PROCESS TO BE..................................................................1313
4: FORECASTING AND MRP ARIS PROCESS DIAGRAM TO BE...........................................1414
5: PERIOD INDICATOR IN MATERIAL MASTER.....................................................................1717
6: PROCUREMENT TYPE IN MATERIAL MASTER...................................................................1717
7: MRP RUN............................................................................................................. 1818
8: ASN ARIS PROCESS DIAGRAM AS IS......................................................................2525
9: SMETS2 ASSET ASN PROCESS TO BE....................................................................2626
10: SMETS2 COMMS HUB ASSET ASN PROCESS TO BE................................................2828
11: ASN PROCESS DIAGRAM TO BE...........................................................................3232
12: INBOUND GOODS RECEIPT PROCESS DIAGRAM AS IS...............................................3332
13: SMETS2 ASSET RECEIPT PROCESS TO BE.............................................................3534
14: SMETS2 COMMS HUB ASSET RECEIPT PROCESS TO BE...........................................3736
15: SAP BGR TO DCC UPDATING PROCESS....................................................................3937
16: INBOUND GOODS RECEIPT ARIS PROCESS DIAGRAM TO-BE......................................4341
17: NEW MATERIAL GROUP.......................................................................................... 4441
18: VAN REPLENISHMENT ARIS PROCESS DIAGRAM AS IS...............................................5146
19: CDC TO COLLECTION POINT ARIS PROCESS DIAGRAM AS IS.....................................5146
20: COLLECTION POINT TO VAN ARIS PROCESS DIAGRAM AS IS......................................5147
21: VAN TO WALL ARIS PROCESS DIAGRAM AS IS........................................................5247
22: COLLECTION ARIS PROCESS DIAGRAM AS IS...........................................................5247
23: VAN TO VAN ARIS PROCESS DIAGRAM AS IS..........................................................5248
24: PHYSICAL INVENTORY ARIS PROCESS DIAGRAM AS IS...............................................5348
25: ASSET INSTALLATION ARIS PROCESS DIAGRAM AS IS................................................5349
26: ARCHITECTURE FOR ASSET PREINSTALL ACTIVITIES TO BE..........................................5751
27: PROCESS FLOWCHART FOR CALLING BS006...............................................................6053
28: PROCESS FLOWCHART FOR CALLING BS058...............................................................6355
33: CDC TO WALL- PRE INSTALL PROCESS TO BE.........................................................6656
29: BAPI FOR SERVICE ORDER CREATION........................................................................6958
30: SERVICE ORDER HEADER TABLE CHANGE..................................................................7059
31: CALL BS006 VIA SYNCHRONOUS PI INTERFACE...........................................................7059
32: CALL BS058 VIA SYNCHRONOUS PI INTERFACE...........................................................7059
34: METER RETURNS PROCESS AS IS..........................................................................7562
35: REMOVAL OF ASSET FROM PROPERTY ARIS PROCESS DIAGRAM AS IS..........................7662
36: REMOVAL OF ASSET FROM THE PROPERTY TO BE.....................................................7864
37: HHT APPLICATION OVERVIEW..................................................................................8166
38: NEW REASON CODE...............................................................................................8167
39: EQUIPMENT MASTER UPDATE...................................................................................8267
40: ASSET DROP OFF AT ROYAL MAIL SITE ARIS PROCESS DIAGRAM AS IS........................8771
41: ASSET DROP OFF TO BE.....................................................................................8872
42: RETURN ASSET RECEIPT AT CDC ARIS PROCESS DIAGRAM AS IS...............................9074
43: RETURN ASSET RECEIPT AT CDC TO BE................................................................9175
44: DISPLAY STORAGE BIN IN EWM SYSTEM....................................................................9477
45: RETURN ASSET FROM TRIAGE ARIS PROCESS DIAGRAM AS IS....................................9679
46: SELECTION OF MOVEMENT TYPE.............................................................................10183
47: MOVEMENT TYPE WITH REASON CODE RELATION.......................................................10183
48: DEFINE REASON CODE......................................................................................... 10284
49: DEFINE REASON FOR ORDERING............................................................................10385

Business Blue Print
Version: 0.1
Page 7 of 107
FIGURE 50: BPEM PROCESS CYCLE........................................................................................10687
Glossary
The following abbreviations, acronyms and definitions are used in this document and throughout
the project documents.
Term
Definition
Context
ASAP
An SAP methodology for delivering change, adopted

by third party suppliers
Technical
ASN
Advanced Shipping Notification sent by each

vendor indicating the contents of a shipment inbound
to the warehouse, typically in advance of the
scheduled delivery date
Business
Business
Blueprint
An ASAP methodology deliverable, which covers the

business requirements and process design. An
expected deliverable from third party supplier
Technical
MM Module
SAP Material Management module
Technical
PM Module
SAP Plant Maintenance module
Technical
EWM
Module
SAP Extended Warehouse Management module
Technical
Outside
SAP
Requirements which will be addressed outside SAP

system either by process changing or by using 3rd
party application
Technica;l
Standard
SAP
Requirements which will be addressed by using SAP

standard functionality
Technical
Required
Developme
nt
Requirements which can be addressed by using SAP

configuration and development
Technical

Business Blue Print
Version: 0.1
Page 8 of 107
1. Introduction
1.1.
Purpose
1. To document our understanding of the current BGSM Supply Chain (AS IS)
business processes and the technical solution in place that support these
processes
2. To document the business and technical requirements of the project
3. To document the TO BE business processes and the proposed technical solution
in compliance with regulatory obligations for British Gas Smart Metering (BGSM)
Processes
1.2.
Project Goals
British Gas must have the ability to install credit and prepayment SMETS2 meters in customers
homes before Industry Live Operation (date to be confirmed by DECC). British Gas must have
the ability to install credit and prepayment SMETS2 meters in customers homes after
DCC Live Date (date to be confirmed by DECC, but currently 1st April 2016) and from BG
Live Date (date to be confirmed by Centrica, but currently 1 st July 2016).The meters will
be installed with a Smart Metering Equipment Technical Specification v2.0 (SMETS2) IHD
and a SMETS2 Comms Hub. Telefonica Comms Hubs will be used in the midlands and
south but in the north Arquiva Comms Hubs will be used.
This project will capture the required enhancement in SAP so that all of these new assets
must be accepted into the British Gas Smart Metering (BGSM) supply chain, enhancement
in job booking process and be installed along with exchanges all metering jobs where
required by Smart Energy Experts (SEEs) in customers homes. This project will also
ensure to use the Data and Communications Company (DCC) for communications and
data transfer, communicating with SMETS2 meters and communications service provider
(CSP) supplied communications hubs.
1.3.
Business Objective
Comply with regulatory obligations including the Smart Energy Code

Business Blue Print
Version: 0.1
Page 9 of 107
Meet DECC objectives for Go-Live (also known as Initial Live Operations) British Gas
Live before ESI go live by April,2016 1st July 2016.
Maintain the delivery of smart services within agreed service levels
Transition to more efficient and cost-effective smart industry infrastructure
Realise the value of the enduring solution as quickly as possible
To minimise the impact of introducing SMETS2 assets into established SMETS1
operations
Be ready for Industry E2E Testing by Dec,2015 March 2016.
1.4.
Outcomes
BGSM will be able to provide regular forecasts for SMETS2 compliant smart
metering equipment to new and existing asset suppliers
BG to be able to track SMETS2 compliant smart metering equipment throughout
their lifecycle
Deliver a system solution which will enable BG to install and commission
standard SMETS2 compliant equipment (list of SMETS2 equipment are
referenced in the BRS - Appendix A) on an existing electricity or gas connection
for domestic customers, as well as repair faults at customers homes and remove
if/when it is necessary
All changes made to add this extra functionality also needs to ensure that it
supports the advance domestic assets currently in operation. The enhancements
need to support the parallel operation of both meter systems.

Business Blue Print
Version: 0.1
Page 10 of 107
2. Impacted Business Process

Inbound Process
2.1.
Inbound Process can be classified into four sub-processes:
Warehouse Replenishment
ASN and Inbound delivery
Quality Inspection
Goods receipt at CDC
Figure 1: Inbound ARIS Process Diagram AS IS

2.1.1.
Warehouse Replenishment
Warehouse replenishment can be classified into two sub-processes:

1. Forecasting and MRP
2. Ordering Process
2.1.1.1.
Forecasting and MRP
Business Process Description As Is

SAP Forecasting is a process by which the system predicts the future requirement of the
business and the MRP run system generates the order proposal based on the
requirement. As per As Is process, system predicts next 6 weeks forecasting data based
on last 8 weeks consumption data and generates the requirement. Based on this
requirement system will run the MRP and generate the order proposal as a purchase
requisition (PR) document. Forecasting and MRP is running on every Monday by
scheduled batch job.
Forecasting is running based on the last 8 week consumption data of the asset issued
from CDC to VAN and MRP is running based on the parameters like CDC available
inventory, Supplier lead time, Safety Stock, open PO etc. Following formula is used for MRP
calculation:
Business Blue Print
Version: 0.1
Page 11 of 107
Required Quantity = Available stock + Firmed receive quantity Safety stock

Purchase Requisition (PR) is a precise document to notify the item to the purchasing
department that needs to order in the future. PR is generated automatically in the system after
running MRP at warehouse level. The procurement team will be notifying through an email for
review the PR.
1r.0
.1
erw
foe
rm
Fo
ec1a
s0
t1
foP
r6
eks
8weekshistoricaldataavailable
1fo
.0r1e.1
0s2tD
eterm
nreeif
ca
ltsia
accre
ursau
te
Forecastresultsareinaccurate 1.01.1021M
atnru
aly
upd
ca
ba
atseefo
dfarocento
erssxte
rensaullts
1.0c1r.1
0te
3RunM
RPto
era
equpisuirtciohnase
Forecastresultsareaccurate
Forecastresults
1.01e.1
0m
4e
Dette
rm
inedif
foarm
pun
rcdh
asn
erre
eqquuisirie
tion
Purchaserequisitionreadyforconverting
PurchaseRequisitionConverted
Purchaserequisitionrequiresam
endm
ent
41
Aum
p1u.r0c1h.1
as0e
req
iseitn
iodn
Purchaserequisitions
NotificationtoPurchaseteam
Figure 2: Forecasting and MRP ARIS Process Diagram AS IS

Business Requirements/Expectations
Forecasting and MRP process of SMETS2 meter assets will be same as SMETS1 assets.
The following changes will be considered for SMETS2 Comms Hub asset:
The 24 months forecasting will happen outside the SAP system depending upon the last
24 months consumption value. It is based on the operational roll-out plan for SMETS 2
and overall roll-out volumes
The Order Management system will be updated based on the data receive from the
forecasting.
The PO document will be created manually in the SAP system for the next 24 months
requirement.

Business Blue Print
Version: 0.1
Page 12 of 107
Figure 3: SMETS2 Comms Hub Process TO BE

Business Process Description TO BE
The Forecasting and MRP process included here are for the following two types of assets:
1. SMETS2 Meter
Forecasting and MRP process of SMETS2 meter will be same as SMETS1 asset.
2. SMETS2 Comms Hub
For SMETS2 Comms Hub, forecasting will be done outside the SAP system by the asset
strategy team BGSM Ops Development based on latest Finance volumes. This forecasting
will run based on the consumption data from the last 24 months and predicts the next 24
month requirement on the operational roll-out plan for SMETS 2 and overall roll-out
volumes. Purchase order will be created manually in the system based on the
forecasting result 4 5 months before actual delivery considering after 20 months
there would not be any change in forecast value.

Business Blue Print
Version: 0.1
Page 13 of 107
Determ
ineAssettype
M
anualForecasting
SM
ETS2COM
M
SHUB
M
eterAssets
1f.0
1.1
0s2tD
eterltm
ineif
ore
ca
accruersau
tesare
1r.0
.1
oe
rm
Fo
ec1a
s0
t1
foP
re
6rfw
eks
8weekshistoricaldataavailable
Forecastresultsareinaccurate 1.01.1021M
upd
axsate
tnru
ea
sluylts
ba
atseefo
dfare
ocntcoe
rsrnal
Forecastresults
1.0c1r.1
0t3
RunM
RPto
era
ee
qupisuirtciohnase
1.01e.1
04e
Dette
m
inedif
rerqq
foarm
pun
rcdhm
asn
ere
uuisirie
tion
Forecastresultsareaccurate
PurchaseRequisitionConverted
Purchaserequisitionrequiresam
endm
ent
41
A
p1u.0
rc1h.1
as0e
req
um
iseitn
iodn
Purchaserequisitions
NotificationtoPurchaseteam
Figure 4: Forecasting and MRP ARIS Process Diagram TO BE
Solution approach for requirement ID PCD Req 1, 2 and 3

BRS
Requirement
ID
PCD Req 1
Standard/Require
Development
Description
FR1.1 -The Latest Estimate produced by the Ops Strategy

Team must cover a 24 month period for comms hubs
Outside
SAP
FR1.2 - The Asset StrategyBusiness team(TBC) team must

maintain records of the volumes forecasted for SMETS2 assets.
Outside
SAP
FR1.3 - The business requires the ability to uniquely identify

each SMETS2 asset type and model.
Standard SAP
PCD Req 2
FR2 - The ability to provide forecasts for SMETS2 smart

metering assets to existing suppliers.
Standard SAP
PCD Req 3
FR3.1 - The Asset Strategy Team requires access to the Order

Management System (OMS).
Require
DevelopmentOutsi
de
SAP
FR3.2 - The DCC relationship manager requires a user profile

to enable access to the OMS to view comms hub forecast
volumes

Business Blue Print
Version: 0.1
Require
Outside
SAPDevelopment
Page 14 of 107
FR1.1 and FR1.2: The asset strategybusiness team(TBC) team will capture the 24 months
future requirements which will be considered outside the SAP system. The asset
strategybusiness team(TBC) team will upload the future requirements into the OMS portal on a
monthly basis. The DCC relationship manager can able to viewsee the requirements through
OMS portal.
FR1.3: Refer in section master data to be section.
FR2: This information is available in the standard SAP system through MP38 but British Gas
already developed a new report in the Qlick View system which is more user friendly.
FR3.1 and FR3.2: Centrica IS or DCC team will provide the require access to asset
management team.
Solution approach for requirement ID PCD Req 5
BRS
Requiremen
t ID
PCD Req 5
Description
FR5.1 - CDC replenishment must use the following
parameters to calculate replenishment volumes for SMETS2
assets:
CDC shipments (last 8 weeks usage)
Return asset volumes
Minimum and Efficient order quantities (safety stock)
Supplier lead times
Available inventory in the warehouse
Inventory targets in the warehouse
Open purchase orders
Standard/Requir
e Development
Standard
SAP
Outside
SAP
Standard
SAP
Standard
SAP
minimum and efficient order quantities for all SMETS2

assets in BG systems.
Standard
SAP
FR5.9 - BG systems must include SMETS2 assets in the

weekly replenishment calculation (CDC replenishment).
Standard
SAP
FR5.10 - Purchase requisitions generated as a result of a
Standard
SAP
FR5.2 - Amendments to orders in the OMS, including any
amendments to the delivery date of a SMETS2 asset order,

must be updated in BG systems (SAP) by the Inventory
Manager to facilitate replenishment calculation of SMETS2
assets
FR5.5 - The inventory manager requires the ability to view on
BG systems the lead time for each SMETS2 asset supplier

(CSP)
FR5.6 - The inventory manager requires the ability to set the

Business Blue Print
Version: 0.1
Page 15 of 107
replenishment calculation must include SMETS2 assets.

FR5.11 - The inventory manager must be automatically
notified when a purchase requisition for a SMETS2 asset is
generated by BG systems.
FR5.12 - The inventory manager requires the ability to adjust
a purchase requisition
Standard SAP
Standard SAP
FR5.13 - The inventory management team requires the

ability to convert the purchase requisition to a Purchase
order in BG systems.
FR5.1: The SMETS2 meter will be forecasted through SAP system. Return assets will not be
considered because returned stock always lies in blocked stock and SAP does not consider the
blocked stock for MRP run.
FR5.2: Any changes in the OMS system will also be updated in the SAP system. As an example
the change in order or change in delivery date in OMS system will be updated into the SAP
system. This will help the SAP system to calculate the next CDC replenishment date for
SMETS2 asset. Comms Hub.
FR5.5: The lead time will be maintained in the material master MRP data or in the Vendor
master Purchasing data in the SAP system. This data can be viewed by the inventory manager
whenever required in the future.
FR5.6: These will be maintained in Material MRP master data in SAP. This will work as a safety
stock in the SAP system. This safety stock can be viewed by inventory manager from the
system.
FR5.9: The SMETS2 asset will be included in the weekly replenishment depending upon the
MRP data setup in the material master. The selection parameter of the Period indicator in the
MRP master data will include that particular material code in the weekly replenishment. The
following screenshot depicts the process.

Business Blue Print
Version: 0.1
Page 16 of 107
Figure 5: Period Indicator in Material Master

FR5.10: By configuring the MRP data in SMETS2 material master we can include that material
in the MRP run. After the MRP run the future requirement will be captured as a purchase
requisition.
Figure 6: Procurement Type in Material Master

Business Blue Print
Version: 0.1
Page 17 of 107
Figure 7: MRP Run

FR5.11, FR 5.12 and FR 5.13: Purchase requisition creation after MRP run, an email notification
will be sent to the purchasing team inventory team based on SAP standard BADI enhancement.
There will not be any SAP approval process for purchase requisition. Based on the email,
purchasing team can review the requisition document and make changes as required. SAP
change log should provide all the details of purchase requisition changes. SAP standard BADI
will be used to trigger the email to notify the Purchasing team for PR creation. On completion of
the PR review, purchase order can be created manually or automatically using SAP batch job.

Business Blue Print
Version: 0.1
Page 18 of 107
Solution approach for requirement ID PCD Req 7 and 12

BRS
Requiremen
t ID
PCD Req 7
Standard/Requir
e Development
Description
FR7.1 - BG systems must capture historical order data for
comms hubs for a configurable period. This is necessary for
calculating replenishment forecasts for comms hub orders
Outside
SAP
FR7.2 - In line with the existing SCAM process, BG systems

must use the historical data to run the 5 month short term
forecast for SMETS2 comms hubs
Outside
SAP
FR7.3 - The inventory manager requires the ability to adjust

Purchase requisitions in BG systems for SMETS2 comms
hubs
Standard
SAP
Outside
SAP
FR7.4 - The inventory manager requires the ability to submit

monthly orders via the OMS.
Standard SAP
FR7.5 - Order volumes for SMETS2 assets must be
accessible in BG systems in line with existing SCAM
process (via PO).
PCD Req 12
FR12.3 - The Inventory manager requires the ability to

generate short term forecasts for hot shoes
Standard SAP
FR 7.1 and 7.2: Comms Hub material is new to the SAP system so no consumption data is
available for this material. This forecasting process is also proposed to happen outside the SAP
system .In future the consumption value will be stored in SAP so business can extract the
consumption value from SAP for reference.Currently the forecasting and ordering process will
be outside SAP process but in future Centrica business can bring this process in to SAP with
extracted consumption data and require master data set up for MRP.
FR 7.3: The Purchase Requisition order document will be created in the SAP system based on
the forecast value calculated outside the SAP system. The PR document can be amended in
the SAP system if needed by T Code ME52N. PO document will be approved by inventory
manager.
Business Blue Print
Version: 0.1
Page 19 of 107
FR7.4: OMS is a third party system so Centrica IS team will provide the required access to the
inventory manager to place the order.
Assumption
The MRP and forecasting will be done outside the SAP system. The asset strategybusiness
team(TBC) team will capture the future requirements for the next 24 months. The asset
strategybusiness team(TBC) team or supply chain team will upload the future requirements into
the OMS portal on a monthly basis. The DCC relationship manager can view the requirements.
It is assumed that the SMETS2 COMMS HUB forecasting will be outside SAP system but in
SAP also the long term forecasting can be done and there are 2 options to address the
requirement. The following two approaches have been discussed and decided against:
1. Contract used for MRP (within SAP)
2. Scheduling agreement used for MRP (within SAP)
The analysis presented and pros and cons discussed are captured in the attached document.
Process Flow
Refer ASN TO-BE process flow
2.1.1.2. Ordering Process level 4
Inventory team CDC users manually convert the PR to PO and send to the vendor and initiate
the ordering process. PO is created in SAP BGR system and replicated to SAP CORP system
through an Idoc PORDCR. An email notification will be triggered to the PO release manager for
PO approval. An output will trigger followed by PO approval, and an email will be sent to the
vendor with a PDF attachment.

Business Blue Print
Version: 0.1
Page 20 of 107
If any modification is required in PO, a new release strategy will be triggered again and an email
will be sent to the PO release manager for the required approval. After the approval, the PO will
be sent back to the vendor with the change details. These changes happen in BGR SAP system
only. If any changes happen in PO, a PORDCH Idoc will trigger and update the SAP CORP
system. Supplier receives the PO and confirms through an email.
Ordering process of SMETS2 meter will be same as SMETS1 meter. For Comms Hub asset
following changes will be considered:
The inventory team will create the PO directly based on forecasting value calculated
outside the system.
After PO approval the document will be downloaded manually from the SAP system.
Inventory team will login to the Order Management System (OMS) and upload the PO
document.
Any amendment in PO document will also be updated in the OMS.
Business Process Description - TO BE

The Ordering process included here are two types of assets:
1. SMETS2 Meter
Ordering process of SMETS2 meter will be same as SMETS1 asset.
2. SMETS2 Comms Hub
PO will be created manually in the system. This PO information will flow into the SAP Corp
system through an Idoc. Order Management system (OMS) will updated manually with the
forecasting value and PO information. OMS is third party software handled by the DCC who use
to track all the order details.
CSR process
SMETS2 meter procurement will have some operation changes which have been introduced in
the ordering process. After generating the PO, asset strategy team will send the certificate
signing request (CSR) the PO will go to inventory team for approval. On release of PO by
inventory manager the PO details will go to the manufacturer based on AS-IS solution.to the
manufacturer and the mManufacturer will send back the CSR with unique identifier (GUID) for
each and every asset to BG operation team. The CSR information will be uploaded manually
Business Blue Print
Version: 0.1
Page 21 of 107
into the SMKI portal after visual check by operation teamvalidation. The following is the step-bystep process:
CSR integrity The manufacturer will generate CSRs (based upon BGs requirements
for certain fields) and provide to BG. Requirement is integrity to be assured through
digital signatures such that BG can verify what was sent is what was received.
Validation BG will need to create a process to validate the integrity of the CSRs but
also content of the CSRs (for example, have correct individual GUID, correct key usage
value and so on) prior to submission to SMKI for signing.
Sharing of CSR/certificates between BG and manufacturer We will need to send the

signed org certificate and device certificates back to the manufactureran SFTP link or
other secure file transfer is the preferred option rather than email for security and
traceability purposes.
The following attachment is the CSR process flow diagram which will be triggered by inventory
management team after PO creation for SMETS2 assets.

Business Blue Print
Version: 0.1
Page 22 of 107
BRS
Requiremen
t id ID
PCD Req 7
Standard/Requir
e Development
Description
FR7.5 - Order volumes for SMETS2 assets must be
accessible in BG systems in line with existing SCAM
process (via PO).
Standard SAP
FR7.5: SMETS2 asset forecasting and MRP happens in the SAP system. The PR document
generated from the SAP system will be converted to PO. The material code is different for
SMETS2 and SMETS1 assets. So by material code we can segregate the order volume by
running Transaction code ME2l/ME2M.
Assumption
Complete CSR process will be out of the SAP system. Validation and FTP process needs to be
decided by business.

Business Blue Print
Version: 0.1
Page 23 of 107
Exception Management
Exception
Solution Approach
Correction Process
Order Management
system is down or logon
issue
Raise an incident in incident

management system
DCC support groupIS

operations team IS operations
team will resolve the incident
CSR not submitted in

the SMK1 portal

management system
DCC support groupIS

operations team will resolve
the incident
Authorisation issue in
OMS portal

management system
DCC support groupIS

operations team will resolve
the incident
COMMS HUB PO did

not download from SAP
on PO release
Incident to SAP IS team
Manually enter the PO

information to OMS
FTP failure during CSR

transfer from
manufacturer

management system
FTP technical team will resolve

the incident
Security key validation

with GUID
SAP authorization issue

to access MRP and
forecasting transactions
In case of mismatch stop

uploading to SMKI portal ,
store the assets in different
place and inform manufacturer.
Manual validation
Raise an incident to security team
Security team will address the

incident
Table 1 : Exceptions
Process Flow
Refer ASN TO-BE process flow
2.1.2.
ASN and Inbound delivery

Business Blue Print
Version: 0.1
Page 24 of 107
An Advance Shipping Notice (ASN) is a notification of pending deliveries, sent in an electronic

format used to list the contents of a shipment of goods. The manufacturer sends the ASN file
after receiving the PO through the SFTP server. A SAP batch job is triggered to process the file
and create an inbound delivery by standard Idoc type DESADV. If ASN is validated successfully,
an inbound delivery (IDN) will be generated and an email notification will be sent to the goods in
team and vendor. If the ASN validation fails, then the system will send an email notification to
the vendor about the ASN rejection details.
IDN is replicated in SAP EWM by RFC call method with all the relevant information which is
captured from ASN.
1.0
.2h
0a
2s1eA
m
e
pu1rc
ord
en
rd
1.0
1.20r1eq
Convert
purc
phuarcse
haseuoisrditeiornto
1.0
.2h0a2sA
ro
pu1rc
epop
rd
evre
Purchaseorderrequiresam
ending
2
teut
Purchaseorderapproved pu1
rc.0
h1
aa.2
sile0a2
o
rdcC
ehrre
oau
in
m
tta
m
etp
nt
02o3rdS
enm
dail
u1r.0
ch1a.2
se
ap
tta
toae
vren
pucrchhm
ae
sn
ette
m
ad
no
dr,
1c.0k1
02
R
ecPeuirvceha
nd
a
n.2
ow
le4
drd
g
ee
o
r ase
1.0d
1e
.2li0
v2
e5
ryC
do
an
tefirm
1.01.2
pF
loT
aP
dASN
fi0
le26
byU
S
ASNfilevalid
1.01.203V
fia
lelidateASN
0a3ti3onSe
ndhE
m
il
c1o.0
nfi1r.2
m
lin
kato
A
S
Nrfielw
eitto
m
anufa
ca
tu
m
nagrearndw/h
1in
.0
b1
o.2
un0d32
deC
lire
vearte
y
Em
ailnotificatiw
o/h
nrm
ecaenia
vg
ee
drbym
anufand
ASNfilenotvalid
3d
1C
o
tasctin
v1
e.0
nd1o.2
rvi0
a
G
oin
o
an
enm
a
ld
with
lite
nkam
to
o
w
a
filedto
relsoo
ld
veASN
Inbounddeliverydocum
ent
Purchaseorderm
ailattachm
ent
Figure 8: ASN ARIS Process Diagram AS IS

ASN and inbound delivery creation process are included over two types of assets:
1. SMETS2 meter
The ASN delivery process of SMETS2 meter will be same as the SMETS1 meter. Below
some system and operation changes which will be considered for SMETS2 meter.
Introduction of unique GUID for SMETS2 assets which will be added in existing ASN
file. GUID will be stored in equipment master level in SAP system
The Asset StrategyBusiness team(TBC) Team must be able to receive Certificate
Signing Requests (CSRs) from SMETS2 manufacturers
The Asset Strategy team requires access to the SMKI portal to submit the CSR from
supplier

Business Blue Print
Version: 0.1
Page 25 of 107
Figure 9: SMETS2 Asset ASN Process TO BE

Business Blue Print
Version: 0.1
Page 26 of 107
2. SMETS2 Comms Hub

Following changes will be considered for SMETS2 Comms Hub:
New ASN file format coming from CSPs
The inventory team will download the ASN file from the OMS system
Uploaded the ASN file manually to the FTP folder
Auto ASN validation in SAP using NW framework Existing SAP ASN interface will
be extended to support the new set of validations.
On ASN validation failure auto email to inventory team
Inventory team(in CDC) will create service issue in portalSSI portal with rejection
reason
On ASN validation success auto delivery creation and email to inventory team.

Business Blue Print
Version: 0.1
Page 27 of 107
Figure 10: SMETS2 Comms Hub Asset ASN Process TO BE
Business Process Description To Be

The ASN and inbound delivery process included here are two types of assets:
1. SMETS2 Meter
ASN process for SMETS2 meter is same as SMETS1 asset. Existing SMETS1 ASN file will
be updated with a new field with GUID.
GUID is mandatory field and will be validated against SMETS2 material codes
Extend ASN SAP table ZTEWM_ASN_HT
2.
SMETS2 Comms Hub

Business Blue Print
Version: 0.1
Page 28 of 107
ASN process for SMETS2 Comms Hub will differ from SMETS2 assets. CSP will publish the
ASN into the OMS system. The inventory team will download the ASN file from the OMS
system and upload into the SFTP server. One scheduled batch job will run and validate the
ASN file. The ASN success message will flow to inventory team and inbound delivery will
create into the SAP BGR and replicate into EWM system. The ASN failure notification will
flow to inventory team. The team will raise a Service issue in the portalSSI portal with
rejection reason.
ASN Validation at framework level
In SAP NW FTP framework following validations will be done before IDOC creation at BGR
SAP:
Check mandatory fields

Check all the number fields to make sure they are in the right format
Check format of other fields
Check header file row
ASN validation at BGR SAP

On successful validation an IDOC will be created in BGR SAP. The following validations will be
done during ASN processing:
Master data validation

PO validation against the ASN
Validate duplicate serial Numbers or GUIDs
Quantity check between PO and ASN
Pallet ID format check
Manufacturer validation
Quantity per pallet and volumetric validation
In case of validation failure inbound delivery will not be created and an email will be sent to the
inventory team with error log and details.
The following table specifies the ASN file format for COMMS HUB where the anticipated format
will be validated against each field.
Field
order
Field
Anticipated format
CHF ID
EUI-64
CH WAN variant

Business Blue Print
Version: 0.1
Page 29 of 107
Field
order
Field
Anticipated format
GPF ID
EUI-64
Zigbee MAC
EUI-64
SM WAN ID
DCC order ref
Party order ref
Party consignment ref
Delivery location
String
10
Delivery date & time
Date/time
11
Firmware version
12
Hardware version
13
Device config ID
14
Manufacturer, country and date of manufacture
15
Batch number
16
Reconditioned status
17
Pallet ID
18
Qty of cartons on pallet
19
Carton ID
20
Qty of CH in carton
PO number
(Y/N)
Num
Num
Table 2: New CSP ASN file format

Business Blue Print
Version: 0.1
Page 30 of 107
BRS
Requiremen
t ID
Standard/Requir
e Development
Description
PCD Req 11
FR11.1 - On successful validation of a SMETS 2 ASN file,

the business requires the ability to send a Device Pre
Notification Business Service (BS001) to the IH
PCD Req 17
FR17.1 - The solution must be able to capture the additional Require

set of data introduced in the ASN by the CSPs. Development
FR17.2 - The new asset data relating to SMETS2 comms
hubs (as defined in the ASN) must be available to view from
BG systems
Require
Development
Require
Development
FR11.1: Refer goods receipt section for DCC inventory update.

FR17.1: In the proposed solution it is assumed that the OMS system will capture all the
information regarding ASN data but if it is not considered then ZTEWM_ASN_HT current table
in SAP system will be used for storing the ASN data by adding some extra fields in the table
otherwise a new Z table will have to be developed to store the ASN data. Business needs to
clarify this matter. Existing ASN table will be extended to store the ASN information and in
case of technical complexity new Z table will be created.
FR17.2: The new asset information will be captured in the Equipment master. From Equipment
master the new asset data will be visible. The extra data in the new ASN file like unique GUID
will be captured in the Equipment master characteristics field.
New Requirement INB01:Currently for SMETS1 meter after completion of ASN process the ASN
information is extracted and sent to HES Trilliant using a SAP program.For SMETS2 assets the
ASN information is not required to send to HES Trilliant.So the existing SAP program will be
changed to validate the SMETS2 assets to stop processing.
Assumption
Here in the To-Be process it is assumed that the OMS system will capture all the information
regarding ASN data but if it is not considered then ZTEWM_ASN_HT current table in SAP
system will be used for storing the ASN data by adding some extra fields in the table otherwise
a new Z table will have to be developed to store the ASN data. Business needs to clarify this
matter.
Business Blue Print
Version: 0.1
Page 31 of 107
Exception
ASN file download from
OMS failed
Solution Approach
Raise an incident to incident
management system
Correction Process
DCC Integration Hub support team

should resolve the incident
The system will raise an Raise service request with rejection
email with errors to CDC reason
team
Reprocess the IDOC and if it does not
resolve then raise an incident to IS team
Email to CDC team
COMMS HUB ASN file

validation failure
ASN IDOC failure
Process Flow
Determ
ineAssettype
1.01.20c3re
4aM
an
nualPO
tio
SM
ETS2COM
M
SHUB
Gateway
M
eterAssets
1.01d.2
3n5loP
Ofile
o0
w
ad
1.0
.2h
0a
2s1eA
m
e
pu1rc
ord
en
rd
Purchaseorderrequiresam
ending
1.0
1.20r1eq
Convert
purc
phuarcse
haseuoisrditeiornto
Gateway
1.0
.2h0a2sA
ro
pu1rc
epop
rd
evre
Purc
odrder
aphparsoeve
Lou
gpilnoa
todO
PM
OS
fila
end
Lo
ow
gin
nlo
to
M
S
d
adO
A
S
Nafinld
e
Save
N
leldin
shA
aS
re
dfifo
erFTP
SM
ETS2COM
M
SHUB
2
teut
pui1
rc.0
h1
aa.2
sile0a2
o
rdcC
ehrre
oau
n
m
tta
m
etp
nt
Gateway M
eterAssets
.0h1a.2
02o3
dail
u1rc
se
rdS
ee
ren
m
ap
tta
to
n
pucrchhm
ae
sn
ette
avm
ad
no
dr,
1
02
R
ecPeuirvceha
nd
ac.0k1
n.2
ow
le4
drd
g
ee
o
r ase
1.0d
1e
.2li0
v2
e5
ryC
do
an
tefirm
1.01.2
pF
loT
aP
dASN
fi0
le26
byU
S
1.01.203V
fia
lelidateASN
ASNfilevalid
1in
.0
b1
o.2
un0d32
deC
lire
vearte
y
0a3ti3onSe
ndhE
m
il
c1o.0
nfi1r.2
m
lin
kato
A
S
Nrfielw
eitto
m
anufa
ca
tu
m
nagrearndw/h
ASNvalidationfailed
Em
ailnotificatiw
o/h
nrm
ecaenia
vg
ee
drbym
anufand
.0d1o.2
1
Co
tasctin M
eterAssets
v1
en
rvi0
aa3
ne
dm
G
oin
o
a
ld
with
lite
nkam
to
ow
filedto
rn
elsooald
veASN
GatewaySM
ETS2COM
M
SHUB
R
aiitshere
S
ercvtiicon
ere
qsuo
en
st
w
je
rea
Purchaseorderm
ailattachm
ent
1.0
3i1
C
on
ctith
glio
s1.2
in0
anle
m
ata
ilw
no
kdto
ovw
ald
filedto
re
soo
veASN
Inbounddeliverydocum
ent
Figure 11: ASN Process Diagram TO BE
2.1.3.
Goods Receipt at CDC

Business Blue Print
Version: 0.1
Page 32 of 107
1i.0
0d
23de
C
nb1o.3
un
lia
vn
ecryel
Qualityinspectionfailedpartialy 1.01.3022Return
rejecte
vedng
do
oo
rdsto
1i.0
3n
0d
25de
U
nb1o.u
lipvd
ea
ryte
Qualitycio
nm
sppelecttieo
lynfailed
Inbounddeliverycreated
1.01.3g0o1od
R
seceive
1q.0
1l.it3y0i2nsC
ua
poencdtiu
ocnt
Isth
sainsato
teirm
tep!or
1p.3
21go
Return
c1o.0
m
lve0
te
e
ndorodsto
1.01.3024CancelASN
1.01
3u
0i3
C
e.q
p2
m
enre
tate
ASNcanceled
1d
.3o
0n
3vP
tm
aw
b1a.0
se
oulu
etriayc
Equ
ip
tp
cd
re
te
S
tom
ce
knU
aa
te
dd&
Qualityinspectionpassed
1.01.3s0to
31ckUpdate
Goodsm
ovem
entdocum
ent
Figure 12: Inbound Goods receipt Process Diagram AS IS

Once the asset physically arrives at CDC, the inventory team will have a manual quality
inspection check. Quality inspection process is a manual process done outside of the SAP
system. After a successful QI process, the put away task will be created based on capacity
planning in the warehouse. Shelf Life Expiry Date (SLED) is assigned to the asset based on
receive date. Once the task is confirmed, it will update the inventory in EWM and also update
the SAP BGR and CORP system.
On successful goods receipt at SAP EWM, one dynamic RFC call will be executed to update the
BGR SAP inventory and then update the SAP CORP system by an Idoc. So that inventory is insync in all the systems.
Goods receipt process is included over two types of assets:
1.
SMETS2 meter assets

Goods receipt process for SMETS2 meter is the same as the SMETS1 meter. Some
operation changes will be defined in brief as follows:
The goods physically arrive at the CDC location with pallet barcode tagging
The SMETS2 assets will be identified by BGSM asset tag and also the unique
identifier GUID
QI will happen outside the SAP system
Equipment record creation with GUID as characteristic value
The DCC will be updated on GR confirmation via BS001

Business Blue Print
Version: 0.1
Page 33 of 107
For batch managed assets as flying leads and hot shoe batch number will be
stored and tracked in system
Figure 13: SMETS2 Asset Receipt Process TO BE
2. SMETS2 Comms Hub

Business Blue Print
Version: 0.1
Page 34 of 107
Following changes have been considered for SMETS2 Comms Hub:

SMETS2 Comms Hub has two GUID, one is Supplier GUID and another one is
CHF GUID. Both the GUIDs will be 16-digit code.
16-digit CHF GUID will be considered as asset ID serial number in SAP
The QI process is outside the SAP system
Quality sampling failed within 5 days of arrival reject delivery and raise delivery
issue at order management system
Quality sampling failed after 5 days of arrival received asset and follow vendor
return process
The Equipment master will be created with new characteristics to store Supplier
GUID.

Business Blue Print
Version: 0.1
Page 35 of 107
Figure 14: SMETS2 Comms Hub Asset Receipt Process TO BE

Business Process Description - TO BE
The goods receipt process included here are two types of assets:
1. SMETS2 meter assets
2. SMETS2 Comms Hub assets
The SMETS2 asset receipt process is almost the same as the SMETS1 meter asset process
but some operation and SAP changes are described here. The SMETS2 meter assets
physically arrive into the CDC with pallet bar code attached. Here two tags are attached one is
BGSM asset tag and another one is 16-digit unique GUID. The assets will go for Quality
Business Blue Print
Version: 0.1
Page 36 of 107
sampling. This is outside the SAP system. On QI failure delivery will be rejected and on success
pallet id will be scanned for unloading. The assets are unloaded into the CDC. The put away
task created with put away strategy based on the capacity planning in the warehouse. The
assets are packed into the destination bin and in SAP system the task will be confirmed by
scanning the pallet id. The CDC inventory updated into the EWM system and replicated to SAP
BGR also to SAP CORP. The Equipment is created in SAP BGR system. SLED date is updated
into the equipment master.
The DCC inventory is also updated with the receipt of the goods in the CDC via business
service BS001. The interface will be triggered and the goods related information will be updated
from SAP to Integration Hub (IH) which is connected to DCC.
PI Solution to call BS001
An Outbound proxy contained the GR information from SAP system will trigger the interface and
the interface will update the DCC. In order to achieve the requirement PI will use proxy adapter
as inbound process update and SOAP adapter(assuming web service is the interface) as
outbound process update.File based interface will be used to call the BS001 to update the DCC
inventory.This will be file based transfer where the file will with asset information will be sent to
integration hub using NW batch framework.SAP will extract the file and store it in application
server.SAP NW Batch will pick up the file and transform it into XML file and then send to
integration hub(IH).

Business Blue Print
Version: 0.1
Page 37 of 107
Figure 15: SAP BGR to DCC Updating Process

Exceptions returned from BS001
On submitting the inventory file to DCC IH, DCC can send the response back to SAP with the
below exceptions. The below exceptions will be picked by SAP NW batch and store in
application server in a file format. SAP will pick up those exceptions file and record it in SP
exception tool.
Invalid
request for
new added
device
The Device ID for a new Device

already existed in Inventory and
its Status wasnt
Decommissioned or Withdrawn
E1202
03
Invalid
request
The Device Type / Manufacturer /

Model / Firmware Version data
specified by the DCC User does not
match the DCCs list of equipment
that has been approved for use
E1202
04
Not all the applicable optional data

items are included in the Request
E1202
06
Inconsisten
request
Invalid
service user
role for
device type
E1202
07
Invalid
device type
This Device Type cant be Prenotified
E1202
01
The DCC Service User Role is not

authorised to Pre-notify this Device
Type
SMETS2 COMMS HUB

The SMETS2 Comms Hub process differs from the SMETS2 meter asset receipt process. The
assets physically arrive into the CDC with pallet bar code attached. Here two tags are attached
to each asset -one is 16-digit CHF GUID and another one is 16-digit GPF GUID . The 16-digit
CHF GUID will be considered as serial number in SAP system. The assets are packed in pallets
are received in CDC. The assets will go to the quality sampling. This is outside the SAP system.
On QI failure two possibilities can happen. Firstly if QI fails within 5 days, delivery will be
rejected and raise a service request in OMS. Secondly if QI fails after 5 days of arrival then
goods will be received and returned through vendor return process as described in the return
process. On success the goods will be unloaded into the CDC by scanning the pallet label. The
put away task created with put away strategy based on the capacity planning in the warehouse.
Business Blue Print
Version: 0.1
Page 38 of 107
The assets are packed into the destination bin and in SAP system the task will be confirmed by
scanning the pallet id in pallet label. The CDC inventory updated into the EWM system and
replicated to SAP BGR also to SAP CORP. The Equipment is created in SAP BGR system.
SLED date is updated into the equipment master.

BSR
Requiremen
t ID
PCD Req 10
Standard/Require
Development
Description
FR10.9 - On successful completion of inspection, BG
systems must create a put away task for stock from the
CSP
FR10.10 - BG systems must
information for SMETS2 asset.
maintain
Standard
SAPOutside
volumetric Outside
SAPStandard SAP
PCD Req 13
FR13.1 - BG systems must maintain asset records for all

SMETS2 asset equipment types.
Outside
SAPRequire
Development
PCD Req 14
FR14.1 - For all serialised SMETS2 assets, an asset

identifier must be displayed on the asset.
Outside
SAPRequire
Development
FR14.2 - The asset identification should be visible without

the need to open the packaging.
FR14.3 - SMETS2 comms hubs must display the following
information:
Part number and description of Communications Hub
Variant
Hardware version number
Device Configuration Identifier
Manufacturer, country and date of manufacture
CE Mark
CHF ID (GUID: EUI-64 unique number )
GPF ID (GUID: EUI-64 unique number )
FlexNet ID
Business Blue Print
SAP
Version: 0.1
Outside
SAPRequire
Development
Require
DevelopmentOutsid
e
SAP
Page 39 of 107
BSR
Requiremen
t ID
Standard/Require
Development
Description
ZigBee MAC
PCD Req 16
FR16.1 - BG systems must have the ability to store the

GUID for:
SMETS2 meters (gas and electricity)
Comms hubs
Gas proxy GUID (against the comms hub)
Require
Development
FR16.2 - BG systems must have the ability to track

SMETS2 comms hubs using the GUID and NOT a BGSM
tag
FR10.9: The SMETS2 meter assets physically arrive at the CDC. The stock will be directed
towards manual Quality inspection which is performed outside the SAP system. After successful
QI inspection the stock is unloaded by scanning the delivery and pallet id. By scanning the pallet
the system will propose the destination bin. The asset will be packed into that bin; put away task
will be created and confirmed into the SAP system. The asset is stored in the CDC and the
stock is updated in the EWM warehouse. The stock is also replicated in the BGR system. The
Equipment master will be created and the Shelf Life Expiration Date (SLED) will be activated.
System will calculate the SLED date based on the goods receipt date plus 90 days during put
away. For asset, SLED life duration (90 days) will be maintained in material master SLED field.
Based on the SLED maintained against each asset (equipment characteristics) in SAP, the
system will propose the oldest asset for consumption. A message will display if SEE selects
other than Oldest Meters in the HHTOldest Meter already exists and you have not selected
the Oldest One. For SMETS2 COMMS HUB SLED date will be the GR date and is not required
to have the validation in field application.
FR10.10: The introduction of volumetric information means weight and dimension will need to
be maintained in SAP system for SMETS2 asset. The Volumetric information will be maintained
in master data of SMETS2 meter. Volumetric will be used to calculate the number of totes
required for each order and also to provide forward visibility on the total number of totes
required.

Business Blue Print
Version: 0.1
Page 40 of 107
FR13.1: The goods receipt in CDC will update the EWM inventory. Both SAP BGR and SAP
CORP systems will update in parallel with the inventory update in the EWM system. The
Equipment master is also updated regarding the inventory.
FR14.1 and FR14.2: The SMETS2 meter assets will be identified with BGSM asset tag and
SMETS2 COMMS HUBs will be attached identified with a 16-digit GUID. and also a BGSM
asset tag. The 16-digit GUID is a unique identifier with respect to all SMETS2 assets. The
assets will be identified easily by seeing that 16-digit GUID which performs outside the SAP
system.
FR16.1 and FR16.2: The SMETS2 meter assets are tagged with BGSM asset tag and also one
16-digit unique identifier GUID. The 16-digit GUID will be stored in the characteristics value of
the Equipment master for EMSTS2SMETS2 meter assets. The SMETS2 Comms Hub also
comprises of two IDsone is the 16-digit CHF GUID and the other is the GPF GUID. CHF
GUID will be considered as asset tag as serial number in SAP and the other GUID will be stored
in equipment master as characteristics value.
Assumption
In the To-Be world, two 16-digit GUIDs will be considered as serial number in the SAP system.
This will be updated into the Equipment master characteristics field.
Exception
Solution Approach
Inventory update failure
During goods movement at BGR SAP all

the exceptions to the DCC inventory
update will be captured during equipment
master updating and an email notification Business needs to decide
will be sent to asset management team in
case of any failure with error logs captured
in SAP exception tool
SAP fails to call the PI

interface
The system
message.
DCC update failure
The system will raise an exception

message. Detailed DCC exceptions is
mentioned in the exception list file
attached in the appendix.

Business Blue Print
will
Correction Process
raise
an
exception
Version: 0.1
PI monitor and SAP exception

tool EMMA will be used by
technical team.
Business needs to decideIS

operations team
Page 41 of 107
Process Flow
Qualityco
inm
sp
cttieo
pe
le
lynfailed
M
eterAssets
1.01.3g0o1od
R
seceive
1.m
01a.n
302Conduct
insupaelcqtiuoanlity
G
ateway
1p.3
21go
Return
c1o.0
m
lve0
ete
ndorodsto
1in
.0b1o.u
3n
0d
23de
C
lia
vn
ecryel
Gateway
rejectveedng
orodsto
do
1.01.3024CancelASN
1.01e.q
3u
0i3
C
p2
m
enre
tate
ASNcanceled
1.D
01
.C
30i3
C
n3
veU
np
todrayte
M
eterAssets
1i.0
0d
25de
U
nb1o.3
un
lip
vd
ea
ryte
1d
.3o
0n3vP
aw
b1a.s0e
oulutm
etrayic
Equ
ip
m
tp
cd
re
te
S
to
ce
knU
aa
te
dd&
SM
ETS2COM
M
SHUB
G
ateway
Qualityinspectionfailedwithin5daysofarrival
Qualityinspectionfailedafter5daysofarrival
VendorReturnProcess
ReturnCom
pleted
Goodsm
ovem
entdocum
ent
QualityInspectionpassed
Qualitycionm
sp
tio
pe
lecte
lynfailed
M
eterAssets
1.01.3g0o1od
R
seceive
1.0
1a.3
02Conduct
m
innsupaelcqtiuoanlity
Gateway
1p.3
21go
Return
c1o.0
m
lve0
te
e
ndorodsto
1in
.0b1o.3
0d
23de
C
un
lia
vn
ecryel
Gateway
rejecte
vedng
do
oo
rdsto
1.01.3024CancelASN
ASNcanceled
RaisetoD
C
C
xcoelption
S
A
Peto
1.01
0i3
2C
e.3
qu
pm
enre
tate
M
eterAssets
1i.0
25dU
nb1o.3
u0
nd
elip
vd
ea
ryte
Gateway
Qualityinspectionfailedwithin5daysofarrival
Qualityinspectionfailedafter5daysofarrival
1.0
.3
0i3
D1
C
C
n3
veU
np
todra
yte
Exceptionraised
1d
.3o
0n
3vP
tm
aw
b1a.0
se
oulu
etrayic
Equ
ip
tp
cd
re
te
S
tom
ckenU
aa
te
dd&
SM
ETS2COM
M
SHUB
SM
ETS2COM
M
SHUB
1.01.3s0to
31
ckUpdate
Raisedeliveryissue
1.01.3s0to
31ckUpdate
SM
ETS2COM
M
SHUB
Raisedeliveryissue
VendorReturnProcess
ReturnCom
pleted
Goodsm
ovem
entdocum
ent
QualityInspectionpassed
Figure 16: Inbound Goods receipt ARIS Process Diagram TO-BE

System Configuration Considerations
New material group configured
SPRO>Logistic General>Material Master>Settings for key field>Define material group

Business Blue Print
Version: 0.1
Page 42 of 107
Figure 17: New Material Group
Development Considerations
RICEFW Type
RICEFW Name
Description
Work
Stream
Enhancement
ASN file
Validation
Validation of ASN files.
MM module
Enhancement
GUID update
on Equipment
Master
Unique GUID validation in

Equipment Master
MM/PM
module
Enhancement
RF gun change
RF Gun screen change
EWM module
Interface
New Interface
DevelopmentProxy
development
New Interface Development-Proxy

development
PM module
Smart form
Creation of PO
template
Create PO on PO release
MM module
Table 5 : Development Objects
Master Data TO-BE

Business Blue Print
Version: 0.1
Page 43 of 107
The new TO BE solution will have an impact in the master data in SAP. This section is going to
cover all the master data changes in SAP. The following are the master data sections that will be
updated as part of this solution:
1
Material Group: New material group for SMETS2 assets
2. Material Master: 9 new material codes will be created in the SAP system. 4 new material
code for non BG SMETS2 COMMS HUB. Below is the list
Asset
Telefnica
cellular CH
Telefnica
cellular aerial
Telefnica
cellular & mesh
CH
Arqiva variant
420 CH
Arqiva variant
450 CH
Hot shoe
Flying lead
IHD
L+G ESME
L+G GSME
Description
GPRS comms hub
for central and
south CSP
Hi gain aerial for
GPRS comms hub
GPRS & mesh
comms hub for
central and south
CSP
LW comms hub for
northern CSP
LW comms hub for
Fylingdales area
(see appendix 9.1)
Cable clamp to
provide power to
the CH for gas
only installs
Cable to site the
CH away from the
ESME
New in home
display
SMETS2 elec
meter
SMETS2 gas
meter
Type
Comms Hub
Consumable so
no material
master
Comms Hub
Comms Hub
Comms Hub
IHD
Meter
Meter
3. Vendor Master: 4 new vendor codes will be introduced to the system2 for CSP vendor
and 2 for flying leads and hot shoes.
4. Batch Master: Batch master created automatically by the system based on the vendor
provided batch number.
Business Blue Print
Version: 0.1
Page 44 of 107
5. Product Group: New product group for multi SMETS2 asset providers
6. Product master : New product masters in SAP EWM system for new materials
Auxiliary SMETS2 Meter Assets Flying Leads and Hot shoe

Two new material codes will be introduced to identify flying leads and hot shoes in system.
These will be serialised assets and will be consumed during SMETS2 meter installation. These
2 materials will be batch managed which means each asset will be assigned against a batch
number. In the system this assets can be easily tracked using the batch NUMBER. SAP
standard batch tool (tcode BMBC) can be used to track these assets.
It was decided that the batch management is not required for these two material codes.
List of Assumptions: Inbound Logistics
OMS process will be manual which is means there is no integration between SAP and
OMS systems and user has to login to OMS manually to do any activity in OMS
SMETS2 COMMS HUB forecasting will be outside SAP and purchase order will be
created directly in SAP
CSR process will be outside SAP system and need to be completed before PO creation
by business
There will be a separate FTP set up for CSR process and the FTP team will support any
issues related to FTP failure
New 16 digit GUID for SMETS2 meter assets will be stored in equipment master level
SOAP(simple object access protocol) adapter will be used to integrate ESI considering
integration between SAP ESI will be web services framework based.
There wont be any packaging hierarchy defined in SAP system which means pallet level
packaging will be done by SAP
Manual quality sampling process needs to be changed to support SMETS2 assets
All kind of SMETS2 assets inventory will be updated in SAP CORP
List of Dependencies : Inbound Logistics
Purchase order template supported by OMS should be provided by DCC
ASN validations for SMETS2 COMMS HUB other than basic validations will be provided
by DCC
Validation with CSR key and GUID needs to be defined
Business Blue Print
Version: 0.1
Page 45 of 107
Interface definition for BS001 has to provided by DCC-ESI

Asset volumetric information should be provided by business
Pallet number definition should be provided by CSPs or new vendor
MI Reporting : Inbound Logistics
The below are the reporting requirements in inbound logistics area which will be delivered either
in SAP or in QlickView based on the report type.For QlickView reports Hadoop data extraction is
in this project scope which will be delivered to QV team for frontend development.
Ref
MI1
MI2
MI5
Requirement
The Inventory Manager requires a
monthly report showing the order
volumes for each SMETS2 asset:
By asset:
For comms hub, the report
should show order volumes by
variants
Note 1: The order volumes of
SMETS2 assets ordered are
required by the Inventory
Manager as this feeds into future
MRP calculations
The business requires a monthly
report showing all SMETS2 asset
returns:
Monthly return volume by asset
Batch number
For all comms hub returns, the
monthly comms hub report must
include the Job Status Report (JSR)
reference number
Note 1: The return volumes are
also required by the Inventory
Manager as this feeds into future
MRP calculations
The warehouse manager and
asset strategy team must be able
to view an ASN accuracy report
for SMETS2 assets on BG systems.
The ASN accuracy report will give
details related to validations
success and failures:
Validation errors in ASN files
received
Quantity variances between ASN
quantities and deliveries

Business Blue Print
Area
Asset
Ordering
Asset
Ordering
Warehouse
and Van
Stock
Manageme
nt
Priority
Must
Must
Must
Version: 0.1
Owner
MI or
Operational?
Emma Wells
Operational
Updat
inform
picked
stand
Operational /
MI
1. Thi
Suppl
and d
provis
JSR in
hadoo
2. The
report
to me
report
at a g
Operational
There
report
will be
incorp
assets
Russell
Coates/
Gerard
Masterson
Andy White/
Martin
Kennedy
Page 46 of 107
MI7
MI8
MI9
BG Systems should generate an

Inventory Stock Report for the CSP
(North)
BG systems must generate a

monthly report - by the 5th
working day of the following
month on all comms hubs
delivered and accepted in the
month
monthly report - by the 5th
working day of the following
month on all comms hub
rejected within 5 days of delivery
in the month
Warehouse
and Van
Stock
Manageme
nt
Must
Warehouse
and Van
Stock
Manageme
nt
Must
Warehouse
and Van
Stock
Manageme
nt
Must
Operational
If the
look a
stock
from t
then t
in SAP
the re
lookin
This w
the 2
"north
their i
Operational
This c
an SA
Operational
This c
an SA
Andy White
Sam Shah
Sam Shah
3. Outbound Process
3.1.
Business Process Description (As-Is)
The outbound logistics in Centrica consists of two processes which are subdivided into the
following sub-processes:
1. Warehouse Outbound
2. Asset Installation
3. Van to Van transfer process
4. Physical Inventory process at Van
1. Warehouse Outbound
Warehouse Outbound has the following subprocesses:
I. Van Replenishment Process: Reorder point planning of the assets for Vans

Business Blue Print
Version: 0.1
Page 47 of 107
II. Outbound delivery process: The outbound delivery processes is captured at three
different levels
Internal Warehouse Process to issue the assets from CDC
Asset receipt at collection point.
Asset transfer from collection point to van.
For Van replenishment process in the AS-IS world it is standard SAP consumption-based
planning process, for example, Reorder point planning. In this process Vans are treated as
storage locations in SAP. All the assets assigned to the van are maintained in SAP. Storage
Location is considered as MRP Area.
The continuous monitoring of available Van stock within reorder point planning is carried out in
Inventory Management.
Every time an asset is withdrawn from the Van, the system checks whether this withdrawal has
caused stock levels to fall below the reorder level. If this is the case, the system makes an entry
in the planning file for the next planning run.
Internal Warehouse Process to issue the assets from CDC

In the as-is world Royal mail TOTE is considered as a new handling unit or packaging material
type in SAP. Internal warehouse process covers the demand replenishment of the bins, picking
process supported by RF functionality. Wave management process consolidates the outbound
deliveries and packaging specification functionality handle the volumetric of TOTE.
Asset receipt at collection point
Assets are being despatched from CDC as a stock transfer to collection point. In SAP system
collection point is stored in van customer master as a partner profile.
Asset transfer from collection point to van

Once the asset arrives at the collection point, based on the collection order and notification in
hand held terminal (HHT), SEE will arrive at the collection point to collect the asset. SEE
currently has to scan the TOTE or the individual asset to receive the asset into their van.
2.
Asset Installation

Business Blue Print
Version: 0.1
Page 48 of 107
I. Van to Wall
II. ISU Industrial Flow
III. Invoicing and Billing
3. Van to Van Transfer
Asset transfer from Van to Van is carried out as a standard SAP two step transfer posting
procedure. HHT should have the interface with SAP for handling stock issue and receipt along
with the notification function for receiver.
4. Physical Inventory process at Van
Physical inventory check process is scheduled as a batch job in BGR SAP; HHT should have
the function to carry out physical inventory process. The result of the count has to be entered in
HHT, if there is any difference in physical stock and HHT stock same has to be posted in HHT.
The found or lost asset will be moved to a different storage location, business decision is
pending for posting the found/lost asset. Upon posting the difference in HHT application, the
difference in stock should be updated in BGR SAP through interface.
Startevent
2.0o1
.1oW
ad
re
ho
use
-V
reuptb
lenuisnh
m
eannt
2o.0
1.2uW
areD
houto
se
u
ctb
olo
ecn
tid
o-C
npoC
int
.3W
arelheocutisoen
o2u.0
tb1
poouin
nd
t-C
too
Van
2tb
.0o1u.4
are
eal
ou
ndW
-V
anho
tousw
W
are
house
o2u.0
tb1o.5
upn
dc-C
ro
esoslection
2tb
.0o
1u
.6
W
araenho
use
ou
n
trd
a-nV
sfe
rtovan
2
1.7
W
aP
rehhyo
use
o.0
utb
o
inuvnedn-to
rysical
Process Flow
Warehouse Outbound-Van replenishment

Obsoleteassetidentified 2.01.1041Suggest
supercessionofasset
Replenishm
entrequired
2.01.101lP
evla
en
l reorder
.0h1.1
02foS
hR
edP
ulru
en
ba2tc
job
rcM
2.01.1a0s3se
Pts
rioritise
Lq
isutisoiftio
pn
urccrheaaste
ed
re
urcckhtrasae
nre
to
sP
to
nsre
pq
ou
rtisoirtidoe
d
2a
.01h
.105
S
he
dautile
ra
ucto
m
c
cob
nvtc
ere
rsqifo
o
un
isiotifop
nutrc
ohase
2p
.0e1rc
.1e0d4inC
su
ghaescsket
Correctassetidentified
2.0c1o.1
06tAp
uto
ly
rcm
haatsiccea
reqtrn
uavisneistrip
oo
nrutto
orsdto
ek
0d
7d
C
o2u.0
tb1o.1
un
erle
ivaete
ry
Outbounddeliverycreated
Batchjobscheduled
VanPurchaserequisition
StocktransportorderforColectionpoint Outbounddeliverydocum
ent
Figure 18: Van Replenishment ARIS Process Diagram AS IS
Warehouse Outbound-CDC to collection point

Business Blue Print
Version: 0.1
Page 49 of 107
Endevent
Outbo
dte
dd
elivery
curn
ea
2u.0
.2
1
re
ate
O
tb1o
u0
nu
deC
d
re
q
se
tlivery
2.0d1e.2
02
Pb
ica
ksF
ace
dm
ed
replem
na
iw
snha
veentPre
2.01.203CreateW
ave
2.01.204
re
orC
de
ratepick
2.01.2
0l5eyScloacnatiToon
testo
tro
2.01.206Scanasset
2.01.207T
Po
late
ceassetin
2.01.208ScantheTote
2p
.0
Decte
rm
ic1k.2r0
o9
ute
om
piln
ee
teif
Pickroutecom
plete
Pickroutenotcom
plete
2.01w
.2e
1i0
no
lote
asdand
ghUT
2.0
1t1oC
rm
w1
e.2
igh
fo
Tn
ofite
2a.0
1.2
1p
2lyPo
rin
ntT
la
el
nd
ap
ob
te
2.01.2
13giM
sta
ngovaereT
aoteto
2.0s1h.2
ip1p4inR
geppaalcektto
2q.0
1l.2
ep
rfo
m
ua
ity15
saP
m
linrg
2.01.216Issuegoods
2.01s.2
7piC
reate
i1pe
g
docuhm
nn
ta
tion
.0
.2
18Pp
ea
rtc
forhm
p2
h
ysss1ice
a
A
tlfrdoism
C
DCof
AssetdispatchedfromCDC
Goodsm
ovem
entdocum
ent
2.01.20T
91
Scanthe
ote
No.ofTotesbasedonvolum
etricorder
Totelabel
Figure 19: CDC to Collection Point ARIS Process Diagram AS IS
Warehouse Outbound-Collection point to van
3Determ
ineif
Validasset 2
s.0
ho1rt.3p0ic6
cko/rroevcetrpickor
Correctasset
2.0
64isC
oantcfirhm
as1s.3
et0m
m
063v1erSphio
rtpick
ShortpickorOverpic2
k.01.3
notifio
cratiO
ongencekrated
R
a2s.0
s1
et.3a0t1C
oe
leccetiivoe
n
AssetdispatchedfromCDC point
.3
S
eenndtto
ac2
k.0
nB
o1w
lR
e0d2S
gA
m
G
P
1s.3a
0t3C
Receive
g2o.0
od
poinotlection
2.01c.3
4cS
E
gio
o0
le
tio
nEpo
ne
tsto
2.0
as1s.3
e0
ts5aS
nE
dE
Tsocteasns
2.01.30a6ssD
ette
ineif
isrm
duplicavtea,lelio
dckedor
2o.0
06n2otiG
enerate
Lockedassetdeterm
inedw
rk1fl.3
ow
ISficationto
.3
641T
Assetm
atchp2o.0
sti1np
go0ifro
cra
oalnn
escfe
tiorn
ntm
toV
2.0
3D
terrrm
if1
s.3
to0
c6
k4tra
nsefe
eidne
Assetm
ism
atchw
2o
.0
1fl.3
06n
42Gentieora
te
rk
o
LS
Tw
foroatinfiacla
ysisnto
Notificationgenerated
2.0
0c6o4l3e2
Update
Stocktransferred sto
ck1.3
ina
ndVcatinonpoint
UpdatedstockinVan
E-m
ailtoISgenerated
Stocknottransferred 2.01.306431Generate
workflownotification
Duplicateassetdeterm
ine
2d
.01.3
0a
6i1
Ge
nH
eLrateem
lto
D
Notificationtransferred
E-m
ailtoDHLgenerated
NotificationtoISteam NotificationtoISteam
NotificationtoLST
NotificationtoLST
NotificationtoLST
Figure 20: Collection Point to Van ARIS Process Diagram AS IS
Warehouse Outbound-Van to wall
a2g.0
a1
in.4
st0s1eP
rvicickeaosrsde
etr
UpdatedstockinVan
.4
om
posH
eHT
old2e.0
st2a
s0
s2
etP
frro
2.01s.4
0n3aP
ktand
ca
sisce
2a.0
1i.4
Isrsvu
od
ga
ns0t4se
iceegoord
ers
2.01.405
U
sto
cpkdatevan
2.0
er
in1
d.4
us0tr6iaT
lrflig
og
w
Industrialflowtriggered
Goodsm
ovem
entdocum
ent
Figure 21: Van to Wall ARIS Process Diagram AS IS
Warehouse Outbound-Collection process

Business Blue Print
Version: 0.1
Page 50 of 107
Replenirsehqm
ue
irn
etdforVan
01orC
reate
co2l.0
en
c1tio.5
o
tin
ficatidoenrand
2.0
1l.5
co
ec0ti2oS
ncohre
ddeu
rle
3fo
R
aa
dtion
col2
e.0
cti1o.5
n0in
re
m
2.0
1l.5
Colect
m
ate
ria
frp0
oo4
m
intcolection
2.01.505
U
sto
cpkdatevan
.506n1dR
aoitisfeyto
Vanstocknotupdatedexc2e.0
pS
ti1o
L
Tnaa
ndSnE
E
2.0
6cD
ine
va1n.5s0to
keute
prm
date
dif
07rC
lose
Co2l.0
en
c1o
ti.5
tiofnico
atidoenrand
2.01.5
ex0c6e2ptiR
oensolve
Colectionorderclosed
Vanstockupdated
Figure 22: Collection ARIS Process Diagram AS IS
Warehouse Outbound-Van to van transfer

Acceptedasset
Validasset
2.01.60a2ssD
ette
ineif
isrm
duplicavtea,le
lio
dckedor
2.01
hte
kvaa
snsets
fo.6
r0d1oC
na
incg
Vanto
trdansfer
revqaunire
Ld
oe
cte
kerm
da
insesdet
2ti.0
.6ti0
4G
enerate
no
fic1a
o2
n
vafo
nrrecipient
2.01.6023Issueasset
2.01.60
2a
2ilG
erateem
toen
IS
ined
2re
.0c1ip
.6e0n2t5va
D
rm
in
edif
nete
re
ve
orrie
jected
a
scseeits
2.p
0o
1s.6
2w
T
sp
fer
ti0
n2
g5T
ora
sn
te
Rejectedasset
Stockacceptedinreceivingvan
2r.0
.6
02
51Rettu
rn
ed
j1eo
cnte
ad
tinagssve
anto
Assetreturned
E-m
ailtoISgenerated
2.01.6
0a
2i1
GD
enH
eL
rateem
lto
E-m
ailtoDHLgenerated
NotificationtoISteam NotificationtoISteam
Figure 23: Van to Van ARIS Process Diagram AS IS
Warehouse Outbound-Physical inventory

W
arehouse2.01.7032Physicaly
count(W
arehouse)
Physicalstockcheckrequired
1i.7
reate
p2h.0
ysd
cca0u
l1im
nC
vee
o
nnttory
relo
eczkesbto
ook
i2
n.0
ve1n.7
to0rp
y2o
/F
sB
tin
g ck
Nodifference2.01.7041Post
docum
ent
2p.0
34Enter
h1
y.7
sairc0
(W
eahlocuosuen)t
2
e
p.0
hy1s.7
ic0a3
lcD
oe
ute
ntrm
tyipne
Docum
entposted
2.0e
1r.7
04D
eite
rm
inceeif
e
beth
twe
ea
nisnpdahb
ydo
sfo
ife
ckarlecno
unt
Van 2.01.7031Physicaly
count
2p.0
3l3cE
nn
tetr
h1
y.7
sic0a
ou
Difference
2
0e4n2tP
ost
d.0
od
c1iuf.7
m
fe
rencw
eith
Docum
entwithdifferenceposted
Physicalinventorydocum
ent
ovem
entdocum
ent
Goodsm
ovem
entdocum
eG
ntoodsm
Figure 24: Physical Inventory ARIS Process Diagram AS IS

Business Blue Print
Version: 0.1
Page 51 of 107
Serviceordercreated
Asset installation
2.0s2e
.1
crd
heedrule
rv0i1
ceSo
2.0
2.1
Srm
endservice
ord
er0i2nH
fo
HTationto
2.0s1e.1
eceu
rv0
ic3eE
oxrd
rte
2
4oP
foern
m
g.0
oo1d.1
s0m
ve
erm
t
2.02c.1
5
teo
rm
ineif
rr0m
eceD
tneg
m
ovoe
to
pod
ssted
Goodsm
ovem
entposted
Goodsmovem
entnotposted
2.0
1o
R
olevn
et
G
oo1d0s5
veesm
ism
sue
Newasset
2.02.10o
6fC
ctkstatus
ashsee
2.02.107oC
rdloesreservice
ServiceorderclosedsuccessfulyinBGR
Refurbishedasset
.0a
2ti.1
061S
end
info2
rm
foo
rnbito
linIgSUflow
Figure 25: Asset Installation ARIS Process Diagram AS IS
3.2.
Business Requirement/Expectation
With the introduction of DCC the impact on the warehouse outbound process is minimal. So the
system change in this area is minimal
Van Replenishment
Vans working in the border zone should have COMMS hub from both the CSPs. This
means the van MRP set up should consider both type of COMMS HUB so that system
can generate demand for them
In case of permanent location change from one CSP location to another CSP location.
Van has to do a van to van transfer for the COMMS HUB. MRP has to set up for the
COMMS hub material assigned to new location. Existing LSMW program can be used ro
maintain it
CDC internal picking process
For batch managed material like flying leads and hot shoes batch number takes
precedence over serial number which will impact the warehouse operation efficiency.
One EWM enhancement will be introduced to deactivate the batch selection during
picking task creation. This will help the warehouse operation AS-IS without any impact.
For SMETS2 COMMS HUB pickers will scan the 16 digit GUID(serial number in system)
to pick and in case of wrong GUID scan the system will throw an error message.
CDC to van van pick up process

Business Blue Print
Version: 0.1
Page 52 of 107
There will be system change in van pick up process. For batch managed materials like
hot shoes and flying leads batch number is mandatory for any goods movement. So in
existing pick up and drop off FS1 interfaces batch numbers need to be added to
complete the goods movement.
Assumptions
With the change of mobile field application the existing SAP interfaces (FS1) integrated to this
field application in this process area will also be changed which will be taken care in a separate
project.
Job Booking Process
The entire energy industry is moving from the smart foundation phase, where each energy
supplier has its own meters, communications mechanism, and head-end, into the enduring
phase where all energy suppliers will use the data and communications company (DCC) for
communications and data transfer, communicating with SMETS2 (Smart Metering Equipment
Technical Specification v2.0) assetsmeters and communications service provider (CSP)
supplied communications hubs.
The CGI Integration Hub (IH) is a new gateway to the DCC for communication with SMETS2
meters. The IH provides aggregated access to DCC Service Requests through Business
Services.
The following are the key objectives of the outbound process change as part of this project:
I.
Change in the asset preinstall activities: The To-Be process will take care of inclusion
of required information in the service order. The information will come from the business
services being hosted by Integration Hub and thereby be populated in the service order.
This provides the maximum information to SEE when the SEE goes to the premises of
the customers.
II.
Introduction of the new middleware interface: The business services are being
hosted by integration hub which is the main gateway for communication with DCC. In
order to get access to these services and therefore to achieve the objective, we propose
the introduction of the new interfaces which will call these services to populate the data
in the service order.

Business Blue Print
Version: 0.1
Page 53 of 107
III.
Introduction of new job type codes: The proposed changes demand for an
introduction of new job type codes for gas only installation for different meter types,
scenarios (credit-credit, pp-credit, gas pressure, capacity etc.).The new job type is smart
in nature and of type installation.One of the important attributes for creation of new job
type code is job reason code. There is no job reason code available for the Smets 2
smart installation job.To keep the project requirement in mind and to facilitate the
Smets2 installation , SAP recommends creation of a new job type code with the below
specifications
Job Type Code
Operation
performed
GSISM2
Installation
to
be
Job Reason
Job
Reason
Description
138
Smets2 Installation
The new job type code will be assigned to smart requirement profile in MRS Te
aintionedein the above table able we need a new job type code ts2 installation , SAP
recommends creation of a new job type co
3.3.
Business Process Description (TO BE Solution)
In CDC-Wall installation process a new JSR process will be introduced for SMETS2 COMMS
HUB which needs to be stored in the system. Refer Return and Triage section for the JSR
process.
The To-Be process requires some changes in the asset pre-installation activities. The following
figure depicts the To-Be architecture.

Business Blue Print
Version: 0.1
Page 54 of 107
CDC to Wall Pre Install Process

Business Blue Print
Version: 0.1
Page 55 of 107
Business Service: Coverage check and Inventory details in SAP Service Order
BG System ABAP Program
SAP Middleware Layer
DCC Layer-Integration Hub
First ABAP Program
Web Service- Hosted By

Middleware Server
Web Services-006 & 058
1)Pick up the service

orders
2)Call Web Service
Business
Service
Proxy
Start
SOAP
Z-Table
population
Second
ABAP program
Update
Service
Order
End
Figure 26: Architecture for Asset Preinstall Activities TO BE

There are some new functions that need to be adopted by the organisation, as well changes to
existing activities. The new functions that need to be adopted are:

Business Blue Print
i.
Change in the service order as part of asset pre-install activities.
ii.
Introduction of the new middleware interface:
iii.
Introduction of new job type codes:
iv.
Exception management:
Version: 0.1
Page 56 of 107
PCD Requirement ID
ESI Ascafo BRS
PCD Req 30
FR30.1.1
FR30.1.2
PCD Req 31
Requirement Description
Standard/GapR
equire
Development
The solution must identify

what assets and consumables
have been used during the
course of completing a service
order. Prior to a gas and / or
electricity meter being install
or exchanged the solution
should prompt the SEE to
undertake a WAN signal
check (survey) whilst at the
premises
GapRe
quire
Develo
pment
FR31
The ability to install gas only

or gas first smart metering
systems
GapRe
quire
Develo
pment
PCD Req 35
FR35
It must be clear to SEEs which

assets to install without
requirement
GapRe
quire
Develo
pment
PCD Req 43
FR43
CSP WAN coverage must be

taken into account
GapRe
quire
Develo
pment
Solution approach for inclusion of BS006 information in service orderthe requirement ID

PCD Req 30
Asset Installation will require changes to PM/CS to ensure that gas only jobs can be created
and sent to the HHT. There is a requirement to inform the SEE which comms hub variant and
accessories are expected to be installed during a SMETS 2 job.
In order to achieve the functionality in the TO-BE world, there are few changes required across
the landscape
A) There will be an addition of a few new job type codes for gas only installation in SAP table.
Business Blue Print
Version: 0.1
Page 57 of 107
AB) The business services are being hosted by integration hub which is the main gateway for
communication with DCC. The call to the DCC for inventory check will be done by batch on a
time triggered event in SAPThe mode of creating service orders are as follows
AWB/CCUI
New Installs
Warrants
Online
Policy jobs/CST
During service order creation from different mediums, Ccall to business service 006 will take
place via SAP Middleware PI in a synchronous way. The entire process of calling the business
service is illustrated in the following figure.
Service Order
creation
Select new Job Type,post

code along with other
Call Bapi for

Order creation
prerequisite
Hit BS 006 In
Integration Hub
Server proxy
SAP PI
Response from
business service

Business Blue Print
New field value

populated in order
Version: 0.1
Create and Release

service order
Page 58 of 107
Batch Program
SAP Holding
Table Population
Web service
call
Batch Program
Updating class
and HHT table
Figure 27: Process Flowchart for calling BS006
Figure 28: Process Flowchart for calling BS006

1) During service order creation, the post code, new job type along with the other details will be
provided and the standard SAP program will be called. Inside the code, there are few implicit
enhancement pointsThe first batch program will pick up the service orders created on system
Business Blue Print
Version: 0.1
Page 59 of 107
date.The program then takes any one of the following input parameters of each service order
and send it to the ABAP proxy..
2) There will be a synchronous interface in PI having input and output parameters. The interface
will take the input values and pass it to the business service 006 in integration hub. The
response coming from the service will be sent back to order creation code. In order to achieve
this, we propose the use of Server proxy in PI.
3) The input parameter for calling the service is post code which will be passed to the
middleware.
Post code and premise identifier
MPxN
24) In response, a list of zero or more devices will be returned; zero indicating that no other
[DCC enrolled] devices have ever been installed at the premise.The program then stores the
response in a custom table in SAP.
3)The next batch program will take the values from the custom table and store in the functional
location or connection object master data as characteristics for instance than in the
Service Order.This will also update the HHT table.
4) The program will be scheduled as a background batch job and run after the completion of
first program.
The new order will be created then with the value populated in it. The response will be updated
to the order table also.
5) Based on whether IHD exists or not, suitable operation will be added to the order.
Exceptions:6) There could be cases of not having any response from the business service.This
means there can be technical and business exceptions
The potential reason could be followings
The Middleware server is down
The Integration Hub is down
The Business Service is down
Business Blue Print
Version: 0.1
Page 60 of 107
Network bandwidth insufficiency

The service call does not recognise the address
The exceptions will be classified as business and technical.Due to exception, the service order
will not be populated with the inventory information. The service order will have all the
characteristic value related to 006 as blank.
Due to any of the reasons mentioned above, the service order will not be populated with the
inventory information. In this case, the business has confirmed that the process will not stop
creation of service order. The order will be having an additional flag Default Value Populated.
Additionally the exceptions linked with the middleware or source or target system will be caught
in the middleware trace management tools.
There may be a case of Business wanting to know the number of service orders created without
the inventory information. In that case, there will be separate report needed to be developed in
SAP.
The impact will be changes across various modules in SAP in order to achieve this functionality.
Solution approach for the requirement ID PCD Req 310
In the TOBE world, more than one new job type codes will have to be created for Smets2 gas
only install jobs because of different meter types, scenarios etc. (credit-credit, pp-credit, gas
pressure, capacity etc.).The new job type is smart in nature and of type installation.One of the
important attributes for creation of new job type code is job reason code. There is no job reason
code available for the Smets 2 smart installation job. We will create the new job type code in the
following way in SAP.
JTC itself
Material(service product) we are using the Service Product on the order header for
the appointment offering to see the requirement profile for the first operation.
Standard text key
Task list
Any change need to be done in various job booking channels as a result of back end change in
SAP is out of scope of this document and therefore should be taken care in customer journey.
Solution approach for new requirement ODN01
In the TO-BE world for SMETS2 assets there is no need of sending the asset pre notification to
HES Trilliant after service order creation.Validate the service product code and stop sending the
information for SMETS2 assets in the existing SAP program.

Business Blue Print
Version: 0.1
Page 61 of 107
Solution approach for the requirement ID PCD Req 35 and 43

In the TOBE world, the next addition to the service order will be the ability to have coverage
check information.call business service 058 during appointment booking. This service provides
the information about the possibility of existence of wan coverage on the day of appointment
booking.
In order to doing so, we propose to invoke the service 058 from the service orderr. The entire
process of calling the business service is illustrated in the following figure.
Open Service
Order
Inside FM, invoke the

Server proxy
Response from
business service
Batch Program
Call the ISU service

class
SAP PI
New field value

populated in order
Call the function module

for appointment booking
Hit BS 058 In
Integration Hub
Change and Save

service order
SAP Holding
Table Population
Web service
call
Batch Program
Updating class
and HHT table
Figure 29: Process Flowchart for Calling BS058

Business Blue Print
Version: 0.1
Page 62 of 107
1. 1.The business services are being hosted by integration hub which is the main
gateway for communication with DCC. The call to the DCC for WAN Coverage and
CH Variant will be done by batch on a time triggered event in SAP During service
order appointment booking, the web service is called. The ISU service class will
eventually end up calling into the function module.
2. TInside this function module, the synchronous server proxy of PI will be called with its
input and output parameters. The interface will take the input values and pass it to the
business service 058 in integration hub.
3. The input parameters for calling the service are any one of the followings is post code
which will be passed to the middleware.
Post code and premise identifier
MPxN
4. The following is expected in response to service 058:
Request ID
Post code of address
First line of address
Availability (yes/no)
Availability date
CH variant required
Auxiliary equipment required
Connectivity
The program stores the response in a custom table in SAP.
5. The next batch program will take the values from the custom table and store in the
functional location or connection object master data as characteristics for instance than
in the Service Order.This will also update the HHT table.
6. The program will be scheduled as a background batch job and run after the completion
of first program.
Business Blue Print
Version: 0.1
Page 63 of 107
Exceptions: There could be cases of not having any response from the business service.This
means there can be potential exceptions
The potential reason could be followings
The Middleware server is down
The Integration Hub is down
The Business Service is down
Network bandwidth insufficiency
The service call does not recognise the address
No WAN data available
The exceptions will be classified as business and technical. Due to exception, the service order
will not be populated with the coverage. information. The service order will have all the
characteristic value related to 058 as blank..
Additionally the exceptions linked with the middleware or source or target system will be caught
in the middleware trace management tools.
The service order will accommodate these response values. The response will be
updated to the order table also. The following have been confirmed from Business:
In case of no coverage in near future, the agent will not proceed to book
appointment for the customer.
If there is a coverage in near future (say after 15 days from the date of checking),
the appointment can only be booked on the earliest date from which coverage is
available. So the question of cancellation of the order does not arise.
3.4.
Process Flow (To-Be)
Warehouse Outbound: CDC to Wall-Pre Install TO-BE

Business Blue Print
Version: 0.1
Page 64 of 107
DCCcalfailed
Startevent
2d
.0e3
.2
ntecrre
oa
rd
er
ilsie
sta
erv
cto
eorde
rte
peendiju
om
b
b2o.3
o0
ki.1
ngom
2.03.4raiseException
2.03.7Raiseexception
DCCcalfailed
2
1itU
teusltevrv
ce
e
or.0
d3
e.1
rw
hpddeafa
aliu
2.a0p3p.6
C
aleD
rig
ng
oin
tm
ntC
bC
oodkuin
2.03.3CalDCC
DCCcalpassed
DCCcalpassed
2.o0r3
teC
S
eirnvfo
ice
d.5
erU
wp
itd
haD
C
2.0o3rd
.8Upd
ate
eruvltice
ith
dtesd
fa
appeorinw
tm
en
ate
.0e3r.9
d
rvie
cn
et
o2rd
wU
ithp
aa
ptpeosinetm
da
te
Gateway Coveragecheckpassed
Coveragecheckfailed
Appointm
entBooked
.1e0nR
aise
app2
o.0
in3
tm
issutebooking Appointm
entnotbooked
Figure 30: CDC to Wall- Pre Install Process TO BE
3.5.
Exception Handling
Exception
Solution Approach
Correction Process
Van replenishment error
Existing MRP error log program will be

used so no change.
SAP related interface exceptions will be

All interface exceptions
Correction process is already
captured in SAP EMMA CASE
in pick up, drop off and
defined for existing. For new
exception tool. For the exception list
GMVT install area
needs to be decided.
details refer Appendix section.
Business Service 006 Exceptions will be captured in new sap
ErrorCall
failure- custom holding table and will be passed
Response from DCC
to HHT table also. Standard technical
exceptions related to middleware will be
caught
inside
middleware
trace
management tool. Exceptions will also
be caught in SAP program and
eventually be published as Exception
tool.
New custom table and HHT table

will have the exception details.
Exceptions will also be caught in
SAP program and eventually be
published as Exception tool.
The error will not stop creating

service order. However standard
technical exceptions related to
middleware will be caught inside
The error will not stop creating service middleware trace management
order. However standard technical tool. Exceptions will also be
exceptions related to middleware will be caught in SAP program and
caught
inside
middleware
trace eventually be published as EMMA
management tool. Exceptions will also caseException tool
eventually be published as EMMA

Business Blue Print
Version: 0.1
Page 65 of 107
Exception
Solution Approach
Correction Process
caseException tool
Exceptions will be captured in new sap
custom holding table and will be passed
to HHT table also. Standard technical
exceptions related to middleware will be
caught
inside
middleware
trace
management tool. Exceptions will also
Business Service 058
eventually be published as Exception
Error
Call
failure
tool.
Response from DCC
New custom table and HHT table

will have the exception details.
Exceptions will also be caught in
SAP program and eventually be
published as Exception tool.
Standard technical exceptions

related to middleware will be
caught inside middleware trace
Standard technical exceptions related to
management tool. Exceptions will
also be caught in SAP program
middleware trace management tool.
and eventually be published as
Exceptions will also be caught in SAP
EMMA caseException tool
program and eventually be published as
Standard technical exceptions
related to middleware will be
caught inside middleware trace
management tool. Exceptions will
be
published
as
EMMA
caseException tool
Middleware server down
Standard technical exceptions related to

middleware trace management tool.
Exceptions will be published as EMMA
caseException tool
Integration Hub down
Exceptions will be published as EMMA Exceptions will be published as

caseException tool
Detail DCC exceptions is mentioned in the exception list file attached in the appendix.
3.6.
System Configuration
The impact will be changes across various modules in SAP in order to achieve this functionality.
1) There will be a few new job type codes for Smets 2 gas only installation in SAP.
Business Blue Print
Version: 0.1
Page 66 of 107
2)
There will be new task list for new job type code.
3) There will be two batch programmes for calling business service 006.
4) There will a custom holding table in SAP to store the response.

Business Blue Print
Version: 0.1
Page 67 of 107
5) There will be new characteristics in the function location and connection object master
data.
program for service order creation.
changes in the SAP
Figure 31: Bapi for Service Order Creation

From the program, we call the proxy and pass the data needed to the web service. Also
there will be changes in the header table of order.

Business Blue Print
Version: 0.1
Page 68 of 107
Figure 32: Service Order Header Table Change

6) The process of using PI interface to call the business service is depicted in the following
figure.
Figure 33: Call BS006/BS058 via Synchronous PI Interface

7) There will be changes in the web service for calling the service hosted by Integration Hub.
8) From the ISU class and appointment booking function module, we call the proxy and pass
the data needed to the web service.
9) The process of using PI interface to call the business service is depicted in the following
figure.
Figure 34: Call BS058 via Synchronous PI Interface
10) There will be changes in the service order consequently. BS006

Business Blue Print
Version: 0.1
Page 69 of 107
3.7.
Development Consideration
RICEFW Type
RICEFW Name
Description
Work stream
EWM task creation enhancement

to not to consider batch during
task creation.
Enhancement
EWM task
Interface
Stock info to
DCC
Outbound interface to send stock

information to DCC
MM module
Enhancement
Service order
update
Update custom field while creating

service order from job booking
channels
PM module
Calling business service 058 from

the service order at the time of
appointment booking in MRS.
PM module
Calling business service 006 to

include inventory information in
service order
PM module
Report Containing Default Service

Order Creation Information
PM module
Report containing service order

information without coverage
check
PM module
Enhancement
Enhance
Report
Report
Call BS058 at
appointment
booking.
Call BS006 to
accommodate
inventory
information in
service order
Service order
without
inventory
information
Service order
without
Coverage
information
EWM module
Enhancement
New Job Type

Creation
New Job Type Creation
PM module
Interface
New Interface
DevelopmentProxy
development
New Interface Development-Proxy

development
PM module
List of Assumptions Outbound Logistics

Changes in the van to collection point will remain AS-IS
Business Blue Print
Version: 0.1
Page 70 of 107
Changes in the van functional location will be taken care in Boundary Change project
This project will provide the DCC related interface changes to the FS1 interface
replacement project team.
No process change in CDC internal, picking processes
BS058 is in scope of this project
Proxy adapter will be used from SAP side
SOAP adapter will be used in order to consume web service from integration hub.
No new SEE qualification and can be managed with existing qualifications.
New job type codes for gas only installation will be used.
List of Dependencies Outbound Logistics

Business service interface development is highly dependent on the IH interface definition
details.
MI Reporting : Outbound Logistics
The below are the reporting requirements in outbound logistics area which will be delivered either in SAP
or in QlickView based on the report type.For QlickView reports Hadoop data extraction is in this project
scope which will be delivered to QV team for frontend development.
Ref
MI11
Requirement
All existing reports to be updated
to incorporate SMETS2 assets.
Note: These reports include:
Lost in Transit Reporting
Return stock reporting
Report for all assets which are
installed
Report for assets which are not
installed
Report for assets which are
installed and will be invoiced to
MAP
Report on meter exchange jobs
Transactional Jobs report (e.g.
Removal, Fault etc) which will be
billed to BGR SAP

Business Blue Print
Area
Van Stock
Manageme
nt
Priority
Must
Version: 0.1
Owner
Emma Wells/
Jenny Dutton
MI or
Operational?
MI
Page 71 of 107
Data w
to Had
team
Report for Asset removal
MI12

monthly report to be viewed by
the Metering Settlements
manager showing a count of all
Comms Hub installed in the
month. The report must be ready
by the 5th working day of the
following month. The following
additional information must be
available:
Comms hub guid
Gas Proxy Guid
MPxN
Install Date
Meter Attached
CSP
Job Ref
CH Model:
The report must be downloadable
as an excel spreadsheet and must
be aligned with the MB51
Movements for Installs

Business Blue Print
Asset
Tracking
and
Financing
Must
Sam Shah
Operational
Version: 0.1
Page 72 of 107
This c
as a r
perfor
this m
placed
solutio
report
inform
MI13
MI14
MI16

monthly report to be viewed by
the Metering Settlements
manager for all Comms Hub
removed in the month. The report
must be ready by the 5th working
day of the following month and
must have the following fields:
Comms hub GUID
Date removed
JSR Ref No
MPxN
Removal reason
Asset Condition
Model
CSP
Service order ref
The report must be downloadable
as an excel spreadsheet
Note: This is for comms hubs
where a JSR has been submitted
to the DCC
The DCC relationship manager
and STOC must be able to view a
quarterly record of all user roles
with access to the SSI: The report
must have the following fields:
BG Role
SSI Role
Level of Access provided
Note: this report is required as a
control on who is accessing the
DCC systems on our behalf
The quarterly report must be
compiled into an annual report
and made available every 1st
January to the Legal and Regs
team.
The following information must
also be available to query:
MPxN for premises where a
smart meter was installed
Date of install
Meter type (SMETS 1 or SMETS 2
meter)
Date IHD installed

Business Blue Print
Asset
Tracking
and
Financing
Must
Sam Shah
Operational
Asset
Tracking
and
Financing
Must
Rochelle
Harrison/
STO
Asset
Tracking
and
Financing
Must
Legal and
Regs
This is
user w
acces
at a p
Needs
leaver
proce
into w
Operational
Version: 0.1
This c
as a r
perfor
this m
placed
solutio
report
inform
Page 73 of 107
This is
where
(proje
requir
4. Meter Return and Triage

Reverse Logistics Process can be classified into the following two sub-processes:
Assets Return from wall to Coventry Distribution Centre(CDC)

Return to vendor process at CDC
Asset returns from wall to CDC
4.1.
This process will be comprised with following sub-processes:

Removal of asset from property
Asset drop off at Royal mail site
Return asset receipt at CDC
Startevent
3
.0w
1a
.1reR
e
tu
re
n-frRo
m
w
a
ll
to
h
o
u
s
e
m
o
v
a
ofassetfromproperty
3.0
1w
.2aR
ehtu
rn
fr-A
om
w
al
to
r
e
o
u
s
e
s
s
e
t
dropoffastitR
ail
eoyalM
3to
.01w
.3
R
eo
tuursnefr-R
oe
m
w
al
a
r
e
h
tu
r
n
assw
ea
trre
eh
co
eu
ivseedat
Endevent
Figure 35: Meter Returns Process AS IS
4.1.1.
Removal of Asset from the Property
Business Process Description - As Is

Return process will be initiated through return order to removing asset from the customer
premises. There may be various reasons which can be trigger return process like replacing a
defective meter, recall request, customer disconnected the connection etc. SEE remove the
asset from the wall through return order. If the asset is a non BGMO asset, there is no previous
history available about the asset, so SEE applied a BGSM 6 number and a bar code on the
removed assets. If the asset is a BGMO asset then SEE scan the asset and put into the
returned Tote and also scan the Tote number.

Business Blue Print
Version: 0.1
Page 74 of 107
SEE scan the new assets and placed in a yellow bag if it is new asset (sent to the SEE but not
used) return totes during drop off. This asset directly moves to pick phase after received in
CDC.
At the same time During asset removal SEE also selects enter the reason code and job type in
HHT and closed the return order asset condition code in field application . After completion of
the job the asset and Tote information will be sent to SAP. On receipt of asset information and
TOTE ID in BGR SAP, a movement type (501) will be trigger to update the inventory in van level
and 325 movement is used to update the asset condition in equipment master level. For
BGSM6 asset there is no history available into the system, so a new equipment master will be
created and based on the reason code equipment status will be updated. But for the BGSM
asset, equipment master already exist so only the equipment status will be updated.
3a.0
.1t0in38
R
turryn
ss1e
in2ve
neto
Inventoryupdatedcorrectly
3.01.103to
3te
Scanvan
Assetsrem
oved
3B
.0G
1.1
ete
or01
LeD
ga
cyrm
asinse
etif
BGassetdeterm
ined
3.01
ra
as.1s0
e3t4toTT
on
tesfer
3.0r1
.1s0
ee
lect
ea
o3n5cS
od
1ts
.103eD
eterm
ineif
a3s.0
se
d
lockaerd
orupvliacla
idted,
Lockedassetdeterm
ine
3d
.01.10
3a
2ilG
erateem
toen
IS
3.01.1
inv0e3n7toU
rypdate
3.0in
1v.1
8Dep
term
ineif
e0
nc3
to
orryreu
ctlydated
3.0
1.1
D
m
BG
o0r3L9eg
aecte
yra
sisneetif
Inventorynotupdatedcorrectly
Assetsvalid
3.01.102ta
Sg
canasset
3.01.1
3o6va
C
m
re0
m
lojo
bplete
E-m
ailtoISgenerated
3.01.1
38
G
eIS
nerate
e-0m
ai1lto
3i.0
9e
2nD
fe1q.1
u0
ip3m
te
cte
reram
tein
de
Equipm
entcreated3.01.103922Create
equipm
ent
3.0
n
a1
s.1
se0t4tT
oraV
asnfer
Equipm
entnotcreated
Legacyassetdeterm
ined
ined3.01.1031Generateem
ailtoDHL
3.01.1
161lG
B0
G
abeenlerate
BGassetdeterm
ined
Legacyassetdeterm
ined
3
.1m
0e
3n
9t1nC
ae
ter
e.0
qu1ip
ure
m
b
3.01.1e0-m
39a2il1to
G
enerate
IS
E-m
ailtoDHLgenerated
Endevent
Figure 36: Removal of Asset from Property ARIS Process Diagram AS IS

Asset removal process for SMETS2 meter assets is same as SMETS1 assets. For Comms Hub
asset following changes have been considered:
1.
New material code will be introduced for legacy Comms Hub
2.
SEE will scan CHF GUID for Comms Hub removal
3.
New fault classification code will be introduced and mapped in HHT and SAP
4.
JSR code will be introduced and map them with fault classification code.
5.
New process will be introduced to submit the JSR and send to DCC from HHT part
of new metering application
6.
Unsuccessful submission of JSR raise an exception message in HHT part of new

metering application
7.
Transfer the JSR ID along with the service order into the SAP

Business Blue Print
Version: 0.1
Page 75 of 107
AssetstransferredtoVan
8.
Store JSR ID and other mandatory information in equipment master level
Removal of asset from the property To Be

During meter exchange process smart energy experts (SEE) will remove the old assets from the
property. SEE will scan the BGSM serial no. for SMETS2 meter and GUID for Comms Hub and
drop it to the return Tote by scanning the Tote ID. In the hand held terminal (HHT), new faulty
code and JSR code will be introduced for SMETS2 asset. SEE will be entering the mandatory
information like job type, reason code, JSR code and complete the job. On completion of the
job, the asset will be added in the inventory.
For non BG SMETS2 meter assets the removal process will remain AS-IS which means existing
LO track material codes will be introduced with BG6 assets tag. For non BG COMMS hub 4 new
material codes will be introduced for 4 new variants and SEE has to scan CHF GUID during
removal.
Assumptions
4 new material codes will be introduced for non BG SMETS2 COMMS HUB. In place of 4 new
material codes all the non BG COMMS HUB can also be identified with single material code.
Needs to be decided by business.
As decided by business during BBP walkthrough single material code will be used for non BG
SMETS2 COMMS HUB.

Business Blue Print
Version: 0.1
Page 76 of 107
Figure 37: Removal of Asset from the Property TO BE

JSR Report
For SMETS2 Comms Hub, SEE should enter the JSR code during asset removal. This JSR
information comes to SAP with movement type 501 (261 movement type for new install) and
updates the equipment master. It is confirmed by the business that JSR submission in DCC will
be part of field application solution. The JSR format is specified in the following table.
Ref
Data item
D0
CH status update type*
D2
Date / Time of job

Business Blue Print
Expected values
Dead on Arrival
Comms Hub Fault
British Gas source

New Service order field,
populated on the metering
application
Service order closure (in
the field)
Version: 0.1
Page 77 of 107
Ref
Data item
Expected values
British Gas source
D3
CHF GUID*
xx-xx-xx-xx-xx-xx-xx-xx
Goods movement against

the service order
D10
DCC incident ref
STO if an incident has

been raised
D11
User job ID
Service order number
D14
Model of ESME*
D20
Fault classification*
Damaged case
Damaged connector
Corrosion due to install
conditions
Illegal
interference,
missing seals
Env.
Conditions
exceeded
SMWAN Fault
SMHAN
Interface
Fault
LED Fault
Aerial Fault
New Service order field,

populated on the metering
application
JSR template for asset removal Mandatory fields are marked with an asterisk
The following are the requirements derived from the TO BE business process:

Business Blue Print
Version: 0.1
Page 78 of 107
Requirement ID
PCD Req 20
Description
FR20.1 - New codes are required in the HHT to enable SEEs to report
accurately when returning SMETS2 comms hubs back to the warehouse.
Standard/Gap
Required
Development
FR20.2 - BG systems must maintain a full list of GUIDs and fault codes for
faulty/returned comms hubs following removal and including:
GUID
JSR Number
Removal reason code
Removal date
Date returned (when comms hub was received in warehouse)
RMA Ref Number
CSP
Required
Development
Solution approach for requirement ID PCD Req20

Asset removal process will be done by SEE in HHT application. HHT application is a .Net
application where changes are required to accommodate these requirements. HHT is connected
to SAP backend through SAP Net Weaver Mobile application, so all data inflows and outflows
between HHT application and SAP will be done through this application.
Figure 38: HHT Application Overview
New reason codes configure in BG system and populated in HHT during asset removal. After
SEE remove the asset from property, SEE has to scan asset tag and enter the reason code in
HHT. CSP defined reason codes should be aligned with the SAP and HHT for SMETS2 Comms
Business Blue Print
Version: 0.1
Page 79 of 107
Hub asset. New JSR code will be configured in HHT which should be mapped with the CSP
reason code. When SEE complete the removal job it will update the equipment master in BG
system with GUID, JSR no., removal reason code, date
Figure 39: New reason Code
Figure 40: Equipment Master Update

Business Blue Print
Version: 0.1
Page 80 of 107
Solution approach for requirement ID PCD Req21
PCD Req 21
FR21.1 - In the event that a SEE removes a comms hub from a property
for any of the following reasons, the solution must be able to submit a Job
Status Report (JSR) to the DCC:
Faulty comms hubs
No SMWAN
No fault removal
Required
Development
FR21.2 - On completion of a comms hub removal or on change of comms

hub status, the solution must be able to auto populate and submit a Job
Status Report (JSR) to the DCC
Required
Development
It is assumed that the submission of JSR report to DCC is a part of field application solution.
After submission of JSR report by SEE field application will call the business service to send the
information to DCC. At the same time field application will send the JSR information along with
service order back to SAP to store it in SAP system. The current SAP to field application
interface will be redefined during detailed design phase as a part of Interface Definition
Document (IDD).So the GMVT 261 or 501 interface should change and the below
information should come back to SAP interface
<Service Order>
<Material code>
<BGSM id or CHF GUID>
<Movement type 261 or 501>
<Fault code>
<JSR number>
<CHF status type>
Business Blue Print
Version: 0.1
Page 81 of 107
<Model ESME>
Solution approach for requirement ID PCD Req30 and 36

Business Blue Print
Version: 0.1
Page 82 of 107
PCD Req 30
PCD Req 36
FR30.9- Following the Decommission of SMETS2 assets, the solution

must allow the SEE to send Business Service BS015 (Decommission
Device) to the Integration Hub.
This functionality will need to be replicated within the contingency model,
i.e. where Business Continuity has been invoked.
Required
Development
FR30.10- Following the Disconnection of SMETS2 assets, the solution

must allow the SEE to send Business Service BS016 (Disconnect Supply
Electricity / Gas) to the Integration Hub.
Required
Development
FR30.12- The solution should allow a SEE the opportunity to re-activate /

exchange a Comms Hub without the need for a re-plan / follow on visit, in
the event that following successful commission the Comms Hub develops
a fault or becomes inoperable.
This includes the present scenarios where the comms hub commissions
correctly but subsequently stops operating or suffers an accident, i.e. the
SEE drops his toolkit and smashes the comms hub
Required
Development
FR36.1- The solution must enable the completion of a Job Status Report
for the following reasons and enable the appropriate template to be sent
to the DCC: Successful Install
No SMWAN Install & Leave
No Fault Removal
Comms Hub Fault
Required
Development
FR36.2- The solution should enable the SEE to provide the relevant Job
Status Report details by providing drop down lists wherever feasible.
Note: Further identify during Solution Design
FR36.3- The solution should pre-populate fields on the Job Status Report
according to the data held on the relevant Service Order, or using data
captured during the job.
FR36.4- The solution will be expected to incorporate the existing Job
Completion Codes into the new process and complete the Job Status
Report for all SMETS2 service orders.
All SMETS2 jobs will update Core SAP and generate the necessary JSR.

Business Blue Print
Version: 0.1
Outside SAP
Outside SAP
Required
Development
Page 83 of 107
Exception
Solution Approach
All AS-IS SAP exceptions

related to return
Map JSR code with
reason code
JSR submission failure in
HHT
Correction Process
Will be mapped to SAP EMMA

CASEEXCEPTION TOOL
Correction process is
already defined
Physical mismatch
Business needs to decide
Yet to be decided in field application project
JSR not updated in DCC
Raise an incident in incident management
Equipment update failure

with JSR information
Raise an exception in SAP EMMA

CaseException tool
4.1.2.
DCC incident management

support team will resolve
Reprocess functionality or
manual update in
equipment master
Asset drop off at Royal mail site

Though SEEs are divided by different locations in a zone but there is a common location for all
the SEEs on a particular zone called Royal mail site to collect or drop off their assets. Drop off
process is initiated at van level. SEE comes to Royal mail site to drop off their assets for return
purpose.
New assets (sent to the SEE but not used) should be returned in a yellow bag and transferred
the asset from van inventory to the CDC inventory.
SEE will scan each Tote or type twice in the screen with return assets and drop off the Tote at
Royal mail site. SEE has to confirm the drop off completion job at HHT application, which will
trigger the return delivery creation in background in a day advance. CDC can see all the return
deliveries in advance in the system.
The delivery items will contain scanned assets and storage locations details. The packaging
information in the delivery will be populated in the system by Tote ID information. On successful
completion of delivery document, the same will be replicated automatically to SAP EWM.
CDC can also receive unexpected returns (Failure of assets drop off due to exceptions). All the
anonymous assets scan in a Tote and create an inbound delivery manually. Currently one
unexpected return program is used to create delivery for bulk return assets.
3.0e1x.2
0p5ti1on
Ge
rate
ce
tone
IS
3.0
1a.2
ttsen
m
il0s1
iteAa
pdartRo
oyfal
AssetstransferredtoVan colectionorder
3.01i.2
InaptiuotnTote
nf0o2rm
3.R
01o.2
3D
verTote
to
yla0
an
iellia
co
elcM
tio
osrdpearrtof
1
04bC
om
d3
e.li0
el.2
ry
ppe
ale
rtrteof
cvo
ecjtioo
naosrd
3a.0
05
Dedte
rm
ineif
ss1lo
e.2
ts
ad
re
cke
oruvpalliicdate,
Assetsld
u
p
icatedor
cG
kle
inoB
SdM
6
eH
nL
era
e3
xc.0e1p.2
tio0n61toG
D
&te
IS
6T
ra
ncsfe
p3o.s0ti1n.2
g0
cto
le
tiorn
pto
oin
Assetsarevalid

Business Blue Print
3.01.20
is5s2ueResolve
3.01.20is6s2uR
eesolve
eH
nL
era
e3
xc.0e1p.2
tio0n81
toG
D
&te
IS
Em
ailnotoficationsenttoDHL&IS
Deliverycreationfailed
T
fo
pionsttfa
inigleto
cra
olnescfe
tiornop
d
3.01d
.2e0li7
veC
ryreate
3.0d1e.2
tea
rm
eif
v0e
e8d
ryD
cere
tioiin
succlie
ed
orfa
lned
Deliverycreationsucceeded
Deliverycreated
Transferofpostingtocolectionpointsucceeded
Version: 0.1
Page 84 of 107
Figure 41: Asset Drop Off at Royal Mail Site ARIS Process Diagram AS IS
Asset removal process for SMETS2 asset is same for SMETS1 assets. For Comms Hub assets
following changes have been considered:
i.
JSR validation during delivery creation
ii.
On successful completion of JSR validation return delivery will be created
iii.
New Exception will be raised for failed validation
iv.
Update existing unexpected return process to accommodate missing JSR ID
Asset drop off at Royal mail site To Be:

In the TOBE world SEE will scan the Tote with return asset and drop off the Tote at Royal mail
site against a collection order. System will convert the asset in to block stock in van level (For
unused asset only). On completion of drop off, SEE has to confirm the drop off at HHT which will
trigger the return delivery creation in the background in a day advance. CDC can see all the
return deliveries in advance in the system.
For unused asset, initially stock lies in unrestricted stock in van level. Based on the stock type
system can understand which is unused asset. If SEE return the unused asset to CDC, system
first transfer the asset to blocked stock and then create inbound delivery with a proper reason
code. JSR validation is not required for unused asset and this asset directly go to pick face in
CDC.
During the return delivery creation system will validate the JSR ID against each assets dropped
off and in case of validation failure the assets will be excluded from delivery. These assets will
be considered as unexpected return assets. The drop off interface between SAP and field
application will be changed to accommodate this validation and the IDD will be finalised
during details design phase.
Manual JSR creation-Unexpected return
It is assumed that a new maintainable Z table is required to store the JSR information in SAP
for manual ZSR creation process. In case of unexpected return process CDC users manually
Business Blue Print
Version: 0.1
Page 85 of 107
maintain the JSR information into the Z table and submit it to DCC from SAP. Manual or mass
inbound delivery will be created for those assets with JSR ID and receive the goods in CDC.
Pending item
Yet to decide on manual or automatic JSR process. Action item with DCC team to confirm the
JSR process
The following are the requirements derived from the TOBE business process:
Figure 42: Asset Drop off TO BE

Solution approach for requirement ID PCD Req38 and 40

Business Blue Print
Version: 0.1
Page 86 of 107
PCD Req 38
FR38- SEEs should be able to see whether there is a fault with any DCC
service
Outside SAP
FR38.3- When SEE is being sent to resolve fault/defect with any part of
the metering system the SEE should have visibility of the event log, error
log etc so they can see what has occurred with the device prior to arrival.
Outsidw SAP
Outside SAP
FR38.4- When SEE is being sent to resolve a fault/defect with any part of
the metering system the SEE should have visibility of previous faults
(including outcome, time/date, etc.).
PCD Req 40a
FR40.7- The solution must allow for the SEE to complete the appropriate
Job Status Report in the event that the Site Maintenance Visit results in a
replacement Comms Hub being fitted.
The SEE will complete the Comms Hub tab of the Job Status Report.
Outside SAP
If there is any connectivity problem or any other issue in DCC service then SEE should be
notified through metering application. SEE also have the visibility to view the event log and error
log or any previous fault history for the asset in the metering apps. JSR report should be
submitted from the HHT device and that information should be replicated in SAP system via
SAP Net weaver mobile application and store in to the SAP system. It is assumed that the JSR
information will be store in equipment master only not in service order.
Exception
Existing SAP exceptions
Validation failed with JSR
during drop off
Failure during JSR
submission to DCC
4.1.3.
Solution Approach
Will be recorded in SAP EMMA exception
tool
Raise exception in SAP EMMA exception
tool
SAP exception in SAP exceptionEMMA.PI
exception in PI tool
Correction Process
Unexpected return process
Return asset receipt at CDC
Business Process Description - As Is

Once the return assets arrived physically at CDC, CDC team will scan each Tote by RF scanner
and complete the receiving process. On completion of receiving process, assets will be moved
Business Blue Print
Version: 0.1
Page 87 of 107
to warehouse Sorting area in CDC where unpacking will be processed. By scanning each asset
in RF system will update the stock in different bin location based on the asset status or reason
code. The GR information will be updated in SAP BGR system to update the stock in CDC level
and the equipment master.
3.01.3i0
vcee
rreport
n1aD
dvealin
Deliverycreationsuceeded
3.01.30to
2D
eD
liC
verasset
C
3.01.3
a0
n3
daS
scsa
en
tTote
3.0
w
ar1
e.3
ho0u4sC
eroera
dte
er
Assetsm
atch
3.01
De
a.3
ss0e5tm
ate
tcrhm
eisneif
3w
.0
m
a1
re.3
h0
o6
usC
eoonrfidre
r
3.01.3
7rP
traew
R0
etu
nua
aayto
AssetisatReturnarea
Assetsm
ism
atch
3.0
051dM
ualy
u1
p.3
d
eelia
vn
da
ote
cum
n
tery
Figure 43: Return Asset Receipt at CDC ARIS Process Diagram AS IS
Asset removal process for SMETS2 meter asset is same for SMETS1 assets. For Comms Hub
assets following changes have been considered:
i.
For faulty COMMS HUB transfer to a new bin or MANF bin for COMMS HUB to
return the assets
ii.
New logic to automate the bin determination for COMMS HUB
iii.
For new COMMS HUB send directly to pick face
Assumptions
No Triage process for COMMS HUB.
Return asset receipt at CDC To Be
Once the return asset physically arrives at CDC, CDC team will scan each Tote and scan the
asset to receive the goods. The assets will be moved to warehouse work centre named as
RETURN area. In this area, the packing and unpacking process will prepare the asset for
Return to Vendor phase. Based on the asset status system will put the assets into the
designated bin.

Business Blue Print
Version: 0.1
Page 88 of 107
Figure 44: Return Asset Receipt at CDC TO BE
The following are the requirements derived from the TO BE business process:
PCD Req 5
PCD Req 9
FR5.3 - The business requires the ability to view how many serialized
SMETS2 assets have been returned to the CDC warehouse:
By asset model
By return period (e.g. monthly). The return period must be configurable
Standard SAP
FR5.4 - The business requires the ability to view on BG systems all

SMETS2 return assets going through triage by asset model
FR9.1 - The business requires the ability to view SMETS2 asset returns
on BG core systems by asset type
Standard SAP

Business Blue Print
Version: 0.1
Standard SAP
Page 89 of 107

SAP standard Transaction code MB51 is available to display how many SMETS2 assets are
returned within a specified period of time. But to identify the asset based on serial no. one new
Z report will be require.
One Z Transaction code ZMM_SLA is already available into the system to identify how many
assets are presently lying in triage process. It can be finding by material no.
PCD Req 25
FR25.2 - During sorting process at the CDC, the asset management team
requires the ability to view the status of the returned comms hubs to
identify whether the returned comms hub:
has never been installed and is not part of a faulty batch this will be
returned to stock in the warehouse
has never been installed but is part of a faulty batch this will be
returned to the CSP
has been installed and returned due to an identified fault this will be
returned to the CSP
FR25.3 - The Asset tracking team must be able to check that the return
location for a comms hub is as specified by the CSP
Required
Development
Required
Development

During the GR process in CDC, the asset status is updated into the system and based on the
asset status the inventory team will do the shorting and place the faulty asset in a specified bin.
For SMETS2 Comms Hub, the asset will be moved to a new bin specified for CSP. To do that a
new bin should be configured in the system. Asset management team can identify the asset
status of the returned Comms Hub by SAP standard Transaction code IQ09 in ERP system
or /SCWM/MON in SAP EWM system.

Business Blue Print
Version: 0.1
Page 90 of 107
Figure 45: Display Storage Bin in EWM system
PCD Req 26
PCD Req 27
FR26.2 - BG systems must record and maintain information on comms

hub decommissioning:
Date
Reason code (Removal reason )
Hub Status
Asset Condition
Fault Damage codes
The ability to dispose of SMETS2 assets.
Standard SAP
Required
Development

Business Blue Print
Version: 0.1
Page 91 of 107
All the asset removal information will be updated into the equipment master when GR
completed in CDC. Asset tracking team can find out all the information from SAP standard
Transaction code IQ09.
Presently there is no direct process available for material dispose. If the requirement comes to
dispose the asset then inventory team transfer the asset to a designated storage location and
then business user take the decision about the material dispose and scrap the material from the
system. To dispose the SMETS2 asset, user can follow the same process or they can directly
scrap the asset from EWM system with a new process.
Changes in Unexpected Return Process

When the asset physically reached at CDC, CDC users scan the asset against an inbound
delivery to receive the goods. If the JSR code not found against the asset user manually create
the JSR code through a Z table and assign the JSR details with the asset and complete the GR
process. This information send to DCC through a SAP PI interface and update the JSR details
in DCC.
In the existing unexpected return bulk program new validations will be added to validate the JSR
id against each asset id for SMETS2 COMMS HUB.

Business Blue Print
Version: 0.1
Page 92 of 107
Return to vendor process As Is
4.2.
Return to vendor process is initiated when the assets are received in warehouse and identified
for refurbishment or replacement. This process will be comprised of the following subprocesses:
Return asset for triage
Return asset to MAP
Return asset to Manufacturer
4.2.1.
4.2.1.1.
Business Process As Is
Return Asset for Triage
All the return assets initially follow the triage process. DHL is the only vendor who currently
operates the triage process.
Return process will start with the generation of a return purchase order with the proper reason
code in the SAP BGR system. CDC team creates an outbound delivery against the PO and the
delivery will be replicated automatically in EWM system through an RFC call. The identified
assets are scanned and packed into a magnum box and issued from the triage bin against that
delivery. A manifest will be generated and update the equipment master with the asset status.
Asset physically sends to the triage vendor.
When the asset is ready to send back to CDC, vendor will send the ASN in two day advance.
CDC user will receive the asset against the ASN and based on the asset status inventory will be
updated.
Faultya
orssdeatm
rie
da
eg
teerdm
nfu
edrbished
3.02.101UnpackTote
GoodsatReturnarea
3.02.102Inspectasset
3.0a2s.1
te
m
se0t3cD
oned
itrio
nine
Legacyasset
Newasset
32
acbkox
as3s.0
e2
t.1
to0M
agR
ne
upm
3r5dTpra
arnty
sfe
a3
s.0
se2t.1
to03
brin
Assettransferredto3rdpartybin
.10
31P
Rep
as3
s.0
et2to
M
aa
gcnkum
bA
oxM
3
4T
aS
nsbfe
a.0
ss2e.1
t0
to3M
ArP
inr
2.1
03P
3ID
refa
ctce
tra3n.0
sfe
rto
CiK
3.0
6M
Re
a2
ss.1e0t3to
Atu
Prn
AssetreturnedtoM
AP
AssettransferredtoPICKface
Figure 46: Return Asset from Triage ARIS Process Diagram AS IS

Business Blue Print
Version: 0.1
Page 93 of 107
4.2.1.2.
Return Asset to MAP
Return to MAP process is same as return for triage process. Only the difference is there are no
receiving process exists from vendor and only legacy asset with BGSM tag will follow this
process.
4.2.1.3.
Return Asset to Manufacturer
Return to manufacturer process is same as return for triage process. Only the difference is in
asset status during asset receiving process from the vendor.
Faultya
osrsdeatm
rie
da
eg
teerdm
nfu
edrbished
3
06M
1A
TrN
aF
nsbfe
a.0
ss2e.2
tto
inr
Ass3
ertdtrp
aa
nrsty
ferbre
indto
3.0
2n
.2
eaote
srub
co
tr0a1ctiC
nrg
rde
3.0
2m
.20
set
fro
32
rdIspsaure
tyabsin
3.02fr.2o0m
33
R
eiavretyASN
re
dcp
.0
2
043R
eceive
ass3e
tW
fr.2
o
rd
am
reh
o
uspeartyat
3q.0
0e5ntU
da
e
u2
ip.2
m
spta
tute
s
3.02.2
ete
rm
ine
as0s6eD
tty
pe
.20
6a3nu
R
etu
rnrer
as3
s.0
et2to
m
fa
ctu
3.02A
.2S
0N
64frR
eceive
m
anu
faco
tum
rer
3r.0
2.2
Re
vte
efu
rb0is6h5ed
acsesie
3
.0s2e.2
07P
T
sfe
as
tto
icra
knfa
cer
Refurbishedfitforpurposeassetdeterm
ined
Dam
agedassetdeterm
ined
.0
2i.2
re3
fu
rb
sh0e8dP
aiscsket
Refurbishedassetreadytopick
3.0a2s.s
2e
0t6to
2T
srcarn
aspfer
Assettransferredtoscrap
Return Asset to MAP or Manufacturer ARIS Process Diagram AS IS

1.1.1.
4.2.1.4.
Asset return for triage for SMETS2 asset is same for SMETS1 assets. It is assumed that the
Comms Hub assets not follow the triage process so no changes required.
4.2.1.5.
Return Asset to MAP
Return to MAP process will be same as SMETS1 assets for non BG assets.
4.2.1.6.
Return to manufacturer process is same as return for triage process for SMETS2 meter assets.
For Comms Hub asset following changes has been considered:
i.
COOMS HUB return assets will store in a new bin or Manf bin
ii.
Request for RMA level in OMS tool for returned assets.
iii.
CSP publish the RMA level in OMS tool.
iv.
Update the RMA id in return purchase order header field

Business Blue Print
Version: 0.1
Page 94 of 107
v.
Generate return manifest from system with JSR ID and print the document
physically. No email notification.
vi.
Equipment master will update into the SAP system
vii.
CSP provide the confirmation to BG when asset reached to CSP
viii.
Receipt the refurbished assets from CSP as a part of ASN process.
4.2.2.
4.2.2.1.
Business Process Description -TO BE

This process is same as AS-IS process for SMETS2 asset only and for COMMS HUB this
process is not applicable.
4.2.2.2.
Return Asset to MAP
N/A
4.2.2.3.
In the TO BE world SMETS2 COMMS HUB sorting and asset transfer will be warehouse
activities based upon EWM RF-based solution. The complete sorting and asset transfer will be
executed by scanning each asset and Magnum Box label using RF gun. All faulty Comms Hub
assets are placed preferably in a new storage bin CSP1. This will help the system track the
return assets inside the warehouse.
Asset tracking team will login to OMS system and generate the RMA ID for each asset.
Standard return purchase order will be created in BGR SAP and user will enter the RMA ID in
purchase order header field. Return delivery will be created for the same in BGR SAP.
Replicate the outbound delivery to SAP EWM through RFC call. In EWM using follow on option
in outbound delivery, return the magnum boxes from MANF storage type. As the asset will be
issued to vendor, inventory will be updated in the BGR SAP system.
Manifest will be generated from the SAP system. One physical copy of manifest will be sent to
the vendor with the physical asset.
There is no separate receiving process required for the refurbished asset at this moment as it is
assumed that it will be same as the inbound ASN process with assets coming as refurbished.

Business Blue Print
Version: 0.1
Page 95 of 107
PCD Req 20
PCD Req 23
FR20.3 - The asset tracking team requires the ability to access the OMS
to request a Returns Materials Authorization (RMA).
FR23.1 - The fault analysis report from the CSPs must be available to
view for the Asset Management team to facilitate trend analysis on fault
recording
FR23.2 - Existing process to track diagnosis will be updated to include
SMETS2 assets undergoing triage
Required
Development
Required
Development
Standard SAP
Solution approach for requirements PCD Req20 and 23

Asset tracking team should have required access to OMS system to generate the RMA ID and
display the fault analysis report published by CSP. Centrica IS team will provide the required
authorisation to the asset tracking team.
To view the fault analysis report from CSP, Centrica IS team will provide the required
authorisation to the asset tracking team.
PCD Req 22
PCD Req 25
FR22.1 - The asset management team must be able to view on BG

systems any SMETS2 assets which are currently under triage
FR22.2 - The product recall process implemented under SC&AM will be
applied for all tracked SMETS2 assets
FR25.1 - BG systems must create a process to send a faulty SMETS2
asset (excepting comms hubs) to the manufacturer.
Standard SAP
Standard SAP
Standard SAP
Solution approach for requirements 22 and 25

Existing Z report ZMM_SLA is available in the system which provides the required information
about the asset lying in triage vendor.

Business Blue Print
Version: 0.1
Page 96 of 107
Product recall process for SMETS2 meter is same as existing process. For Comms Hub asset
to call the GUID, new development is required.
To send the faulty SMETS2 meter to manufacturer process is same as existing process.
Exception
Not able to loigin OMS system
Authorization failed in OMS
RMA level not generated in OMS
Manifest not generated
Solution
Approach
Correction
Process
Raise incident in
incident
management
DCC incident
support team will
resolve
Raise incident in
incident
management
Raise incident in
incident
management
DCC incident
support team will
resolve
DCC incident
support team will
resolve
Raise incident in
incident
management
IS support team will

resolve
4.2.2.4.
Process Flow
4.2.2.5.
New Reason Code will be defined into the system.

Use T code OMJJ>Select movement type>enter the movement type>select reason for
movement> define new reason code

Business Blue Print
Version: 0.1
Page 97 of 107
Figure 47: Selection of Movement Type
Figure 48: Movement Type with Reason Code Relation

Business Blue Print
Version: 0.1
Page 98 of 107
Maintain the reason code in Z table, using T Code SM30> table

ZTPCMS_ASSETMVT>Maintain
Figure 49: Define Reason Code
New reason code will configure for Return PO creation

SPRO>Material Management>Purchasing>PO>Define reason for ordering>Define reason code

Business Blue Print
Version: 0.1
Page 99 of 107
Figure 50: Define Reason for Ordering
4.2.2.6.
Development Considerations
RICEFW Type
RICEFW Name
Description
Enhancement
Equipment
Master update
Equipment master updating with

incoming JSR status.
Enhancement
JSR Validation
on drop off
Validation of JSR ID during drop

off.
Interface
JSR update in
DCC
JSR details need to be updated

on DCC

Business Blue Print
Version: 0.1
Work
Stream
MM/PM
module
FS1 interface
change
program
MM/EWM
module
Page 100 of 107
Enhancement
Enhancement
Report
Enhancement
Enhancement
RMA level
update
Reason code
modification
Periodic return
asset report
JSR code
update on
EWM
JSR update on
Service Order
RMA level update on Return PO
MM module
Reason code modification in

return PO
MM module
Display periodic return asset

details by asset model, asset
serial no.
MM module
Updating of JSR code in EWM

delivery
MM/EWM
module
JSR details need to be updated

on Service Order
MM/PM
module
List of Assumptions Reverse Logistics

It is aasumed that the JSR information from HHT to SAP will be taken care by FS1
change project
4 new material codes or singleOne new material code will b e introduced for non BG
COMMS HUB
New bin or Manf bin will used for retrun COMMS HUB
No Triage process for SMETS2 COMMS HUB
List of Dependencies Reverse Logistics
Complete JSR trasnfer to SAP and storing the information in SAP is highly dependent in
FS1 interface change project
DCC BS interface definition to submit the JSR is required to complete the solution.
MI Reporting : Reverse Logistics
The below are the reporting requirements in reverse logistics area which will be delivered
either in SAP or in QlickView based on the report type.For QlickView reports Hadoop data
extraction is in this project scope which will be delivered to QV team for frontend
development.
Ref
Requirement

Business Blue Print
Area
Priority
Version: 0.1
Owner
MI or
Operational?
Page 101 of 107
MI17
MI18
MI21
The Asset Management team,

Metering Settlements Manager
and the Inventory Manager must
be able to receive a monthly
report on the volume of comms
hubs returned to the DCC along
with the following details:
RMA Ref No
Date returned
Comms Hub GUID
Return Reason
Note: it is assumed that the DCC
will contact a nominated contact
in BG to inform them of when any
returned comms hubs will be
replaced.
The solution must be able to
provide a summary report of the
outcomes from the WAN Coverage
Check on a daily, weekly, monthly
basis for: Total responses received
confirming availability
Total responses received
confirming no availability but with
an estimated availability date
Total responses received
confirming no availability (no
available date)
The solution must be able to
provide a summary report of the
Fault Audit outcomes on a daily,
weekly, monthly basis for: Correct original Comms Hub
Installation / Maintenance
o Successful Original BG fault
o No Connection Original
SMWAN incident
Incorrect original Comms Hub
Installation / Maintenance
Original BG fault
Triage,
Returns
and
Warranty
Pre-Install
Field
Support
Must
Must
Must
Russell
Coates/
Gerard
Masterson
Operational
This c
in a S
there
impac
altern
Operational
SAP re
develo
SAP re
Liam Gledhill
Dave Curran
5. Business Process Exception Management

A new SAP exception tool will be introduced to capture the business exceptions.
Exception management is the method of intelligently detecting and correcting errors in data.
This process will lower the operational risk by reducing exceptions and managing errors quickly
and automatically. It will increase staff productivity and improve ability to handle increased
Business Blue Print
Version: 0.1
Page 102 of 107
Summ
report
picked
throug
field a
Summ
in SAP
volumes by offering defined scenarios and actions. The users will be able to rapidly diagnose
and resolve problems and decrease time to resolve errors.
Based on the conversion type in FS1 dashboard, different business process will be designed to
capturing all the error type in logs, creating work lists and routing them to particular group.
The first step for BPEM configuration is to activate the business process area to monitor and
capture the exception. Then identify the system message that need to monitor and create a
BPEM case category with that message ID and business process area.
Figure 51: BPEM Process Cycle
5.1.
Business Process
Defines in which business process the exception will be captured and written into the log file.
Processes that are executed before activating the business processes cannot be processed in
BPEM.

Business Blue Print
Version: 0.1
Page 103 of 107
5.2.
Busines Process Area
The standard business process area is defined in the system but custom business processes
can also be defined in scenarios where the trigger of the exceptions is custom.
5.3.
Clarification Case Type
The clarification case category will define the conditions for creating clarification cases, which
business objects and solution processes are to be assigned to these clarification cases, and
who the clerk responsible is.
5.4.
Define Business Process:

SPRO> Financial Accounting > Contract Accounts Receivable and Payable > Basic Functions >
Enhanced Message Management > Specifications for Customer-Defined Business Processes
and Messages > Define Customer Business Processes for Message Management.
Define Business Process Area Internal Number Range:

Enhanced Message Management > Specifications for Logging > Maintain Internal Number
Range Intervals for Jobs

Business Blue Print
Version: 0.1
Page 104 of 107
Define Business Process Area:

Enhanced Message Management > Specifications for Logging > Activate Business Process
Areas for Message Management.
Define Clarification Case Type:

Enhanced Message Management > Specifications for Generating Clarification Cases > Define
Clarification Case Types.

Business Blue Print
Version: 0.1
Page 105 of 107
Define Clarification Case Category:

Enhanced Message Management > Specifications for Generating Clarification Cases > Maintain
Clarification Case Categories > Create Clarification Case Category.
6. Appendix
The following attachment provides the consolidated requirement traceability matrix with
classification of no change, system change and process change.

Business Blue Print
Version: 0.1
Page 106 of 107
The following attachment provides the consolidated list of exceptions grouped into SAP and
non-SAP exceptions.
The following attachment provides the consolidated list of RICEFW objects in different process
areas.
Link for BRS document

http://ts/001/CoreSys/R_D/Document%20Repository/ESI%20ASCaFO%20SD.docx
7. Non Functional Requirement

The below non functional requirements will be considered for this project
Requirement type
Requirement Description
Data Migration
Data migration will be a part of cut over activities using standard
LSMW
Data Archiving
Any new table will be a aprt fo data archiving strategy
Security Considerations
CSR process will be a part of process change
Performance management
Perofrmance testing will be performed to asses scalability of the
systems
Recommended
There are no recommended infrastructure changes
Infrastructure

Business Blue Print
Version: 0.1
Page 107 of 107

BBP For ESI Asset Supply Chain - V1.2

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

BBP For ESI Asset Supply Chain - V1.2

Загружено:

Авторское право:

Доступные форматы

ESI ASSETS AND SUPPLY CHAIN PROJECT

ESI Assets SC_BBP_V0.21

ESI Asset SCM Project

First Version of BBP Document

Project Manager (IS)

ESI Asset SCM Project

ESI Asset SCM Project

2. IMPACTED BUSINESS PROCESS...................................................................119

ASN and Inbound delivery..............................................................................2521

ESI Asset SCM Project

BUSINESS PROCESS DESCRIPTION (AS-IS)......................................................................4840

4. METER RETURN AND TRIAGE.....................................................................7457

Business Process Description -TO BE..............................................................9878

4.2.2.1. Return Asset for Triage............................................................................................. 9777

Return Asset for Triage............................................................................................. 9878

5. BUSINESS PROCESS EXCEPTION MANAGEMENT........................................10584

BUSINESS PROCESS................................................................................................. 10685

ESI Asset SCM Project

ESI Asset SCM Project

1: INBOUND ARIS PROCESS DIAGRAM AS IS.................................................................1111

ESI Asset SCM Project

FIGURE 50: BPEM PROCESS CYCLE........................................................................................10687

An SAP methodology for delivering change, adopted

Advanced Shipping Notification sent by each

An ASAP methodology deliverable, which covers the

SAP Material Management module

SAP Plant Maintenance module

SAP Extended Warehouse Management module

Requirements which will be addressed outside SAP

Requirements which will be addressed by using SAP

Requirements which can be addressed by using SAP

ESI Asset SCM Project

ESI Asset SCM Project

ESI Asset SCM Project

2. Impacted Business Process

Inbound Process can be classified into four sub-processes:

Figure 1: Inbound ARIS Process Diagram AS IS

Warehouse replenishment can be classified into two sub-processes:

Forecasting and MRP

Business Process Description As Is

Required Quantity = Available stock + Firmed receive quantity Safety stock

Figure 2: Forecasting and MRP ARIS Process Diagram AS IS

ESI Asset SCM Project

Figure 3: SMETS2 Comms Hub Process TO BE

ESI Asset SCM Project

Figure 4: Forecasting and MRP ARIS Process Diagram TO BE

Solution approach for requirement ID PCD Req 1, 2 and 3

FR1.1 -The Latest Estimate produced by the Ops Strategy

FR1.2 - The Asset StrategyBusiness team(TBC) team must

FR1.3 - The business requires the ability to uniquely identify

FR2 - The ability to provide forecasts for SMETS2 smart

FR3.1 - The Asset Strategy Team requires access to the Order

FR3.2 - The DCC relationship manager requires a user profile

ESI Asset SCM Project

minimum and efficient order quantities for all SMETS2

FR5.9 - BG systems must include SMETS2 assets in the

FR5.10 - Purchase requisitions generated as a result of a

FR5.2 - Amendments to orders in the OMS, including any

amendments to the delivery date of a SMETS2 asset order,

BG systems the lead time for each SMETS2 asset supplier

ESI Asset SCM Project

replenishment calculation must include SMETS2 assets.