Technical Solution Blueprint R4 Strategic Sourcing V0 8 Final Updated V2.4

Business Blueprint
Strategic Sourcing
Business Blueprint
Strategic Sourcing
Product Owner: Roger Waring& Nigel Coatsworth
Author: Amit Patil
Issue Date: 09-Jul-2015
Status: Draft
Version V0.5
Business Blueprint
Strategic Sourcing V0.6
Document Reviewers
Name Role Date
Enzen
Vaideshwar Sekar
Vikesh Sachdeva
KPMG
Required Approvers
Name Role Date
Matthew Hogg
Pam Brown
Caroline Pallister
Version History
Version Date Name Comment
0.1 22.05.2015 Initial draft
0.2 29.05.2015 Draft – updates to ‘Introduction’ section and to ‘Process

flows’
R4_Strategic Sourcing_PDD_V0.9 Page

Business Blueprint
Table of Contents
1. Introduction:...................................................................................................................................................................
1.1 High Level Business Process Overview................................................................................................................................
2Functional Solution.........................................................................................................................................................
2.1 Organisation Structure Considerations..............................................................................................................................
2.2Master Data Considerations (including all relevant data relationships).................................................................................
2.3 System Configuration Considerations...............................................................................................................................
2.4 Level 5 Processes............................................................................................................................................................
3 Technical/Development Related Items (RICEFW)..............................................................................................................
3.1 Reporting (operational and analytical)..............................................................................................................................
3.2 Interfaces......................................................................................................................................................................
3.3 Data Conversion / Historical Data.....................................................................................................................................
3.4 Enhancements...............................................................................................................................................................
3.5 Forms............................................................................................................................................................................
3.6Workflow.......................................................................................................................................................................
4 Authorisation.................................................................................................................................................................
5. Organisational Change Related Items (to be filled by business)..........................................................................................
5.1 End User Training Considerations.....................................................................................................................................
5.2Change Impact Summary.................................................................................................................................................
6 Assumptions..................................................................................................................................................................
A Decision References/ Cross References...........................................................................................................................

Business Blueprint
Strategic Sourcing
1. Introduction:
As a part of the “ Business Transformation Programme (BTP)“, it is envisaged that the Strategic Sourcing processes and
systems will be upgraded to best in class to ensure current business challenges are addressed and To-Be process will
enable business to meet the challenges of RIIO regulatory period. The design phase of the programme started with
visioning exercise where the key stakeholders were involved in identifying current problem areas of as-Is processes.
The purpose of this document is to introduce the future state Strategic Sourcing Solution which has been designed as a
part of BTP Transformation Programme. Though Strategic Sourcing does not have direct business outcomes, it is a key
enabler to achieve business outcomes, see the diagram below.
This document describes the level 5 system process maps. The level 4 processes, which have been reviewed and
assessed with key stakeholders, have been broken down further in to level 5 system tasks.
Business Blueprint
UK Power Networks Enterprise Process Model

Business Blueprint
1.1 High Level Business Process Overview
Level 1
Process: Strategic Sourcing
Description:
The process of identifying requirements, evaluating the market and suppliers, negotiating and implementing
the sourcing strategy in order to support the objectives of the category. The Strategic Sourcing process is
applicable to all purchases. It is applied to different degrees based on the value and the risk of the purchases.
There are six key bands of procurement of purchases of goods, works or services:
Is it What is Route to market Lead

High the
Risk* value?
?
No £2,000 1. Corporate Card Directorate

or less
£50,000 2. Low value Purchase Order Directorate

or less (one-off spend of value below
£50,000)
£50,000 3. Three bids (evidenced) Directorate

-
£250,000
£250,000 4. Tender Procurement

or more
£345,000 5. Tender compliant with Procurement

or more Utilities Contract Regulations
2006
Yes Any 6. Tender (compliant with Procurement

value Utilities Contracts Regulations
2006 if value above
threshold)
The primary objectives of strategic sourcing are:

 Identifying cost saving opportunities
 Streamlining the sourcing process
 Improving supplier collaboration
 Reducing supply/supplier risk
The Strategic Sourcing process involves the following sub-process:

 Identifying Opportunities
 Market Place Assessment
 Category Approach
 Contracting Approach
 Pre-Qualification and RFP
 Negotiation
 Contract Award and Handover

Business Blueprint
Level 2
UKPN’s second level process comprises the following components.
L2: Strategic Sourcing
Annual Business Strategy and

Pre-Qualification, Contract Award and
L2 Planning / Category Prequalification
RFP and Negotiation Handover
Planning Planning
Process Step Description

Annual Business
Describes the activities involved in creating annual procurement plans for each
Planning and Category
category in the business.
Planning
Strategy and Pre- Explains the methodology for creating a contracting strategy and steps to undertake
Qualification Planning (Including approvals) before the sourcing event.
Covers the steps involved in the Pre-Qualification of supplier, conducting the RFP
Pre-Qualification, RFP
and negotiation processes including the required governance and approval.
and Negotiation
Contract Award and Process for awarding the contract and handing over the contract to the business
Handover and suppliers for execution.
Level 3

Business Blueprint

Key Steps of process
 Focuses on analysis from an internal UKPN perspective, which may include, but
not limited to, a requirements document, lessons learned, high level spend
1.Identify
Opportunity analysis, ideas submitted from Procurement or elsewhere,
 Identified constraints
 Develop a high level approach for each category and draft annual work plan.
Assessing the external market, studying dynamics and balance of power, identifying
opportunities that can be tapped into and developing the list of potential suppliers for
further relationship building.
2.Market Place
Assessment Important for a new category where an existing supplier base is not identified.
Equally applicable for mature categories as it identifies niche areas for further development
and helps develop alternative sourcing opportunities, thereby increase leverage
opportunities.
Category approach is refined and finalised based on steps 1 and 2 above and on detailed
qualitative and quantitative analyses.
The approach takes into account UKPN’s business objectives of the category.
Objectives could include securing the lowest price, adherence to timelines, securing an
3.Category Approach improved service, ensuring uninterrupted supply, transferring risks to suppliers, etc. Based
on this, the size and split of the future supply is determined.
Developing a category approach aims to identify potential sourcing options through an

opportunity assessment using the supply market and supplier analysis. The procurement
Annual Work Plan reflects the agreed approach.
Key steps of the process
 Sourcing team is created.
 Review of various impact assessments.

4.Contracting
Approach  Produce a detailed statement of requirements.
 Upon approval this will lead to the preparation of a CGM Gate A Sourcing Strategy
paper which includes the prequalification and selection criteria and scoring matrix.

Business Blueprint

Focuses on pre-qualifying suppliers in Achilles UVDB and development of RFP.
The supplier submits an AQ response for assessment and deselection purposes.
The pre-qualified list of suppliers is then prepared for CGM Gate B approval, which together
with the RFP evaluation documentation, including an evaluation scoring matrix, is,
5.Pre-qualification
submitted for CGM gate B approval.
and RFP
Revisions are made as necessary and then the RFP documentation is issued to suppliers.
Any queries/clarifications to/from suppliers are answered and the suppliers submit their
RFP responses. Subsequently the RFP responses are reviewed and a shortlist of suppliers is
then agreed. This process is delivered in compliance with EU Regulation timelines
Focuses on the negotiation strategy and the potential mobilisation plan to be agreed with
shortlisted suppliers, negotiations are completed, the responses are scored once again
6.Negotiations using the defined award criteria and scoring matrix,
A CGM Gate C paper will be produced for approval; if approved, this then leads to Contract
Award and Handover process.
Process involves notifying the successful and unsuccessful bidders of the outcome of the
tender, following a standstill period where there is no legal challenge.
Two copies of the contract are issued to the successful supplier for their signature by their
7.Contract Award authorised representatives. The mobilisation plan is reviewed, training is provided where
and Handover
applicable.
The exit plan for existing contract is followed if applicable. The contract commence on the
contracted commencement date.

Business Blueprint
Strategic Sourcing
2Functional Solution
2.1 Organisation Structure Considerations
Company Code: The smallest organisational unit for which a complete self-contained set of accounts can be drawn up for purposes of external reporting. It includes the
recording of all relevant transactions and generating all supporting documents required for financial statements.
There are many legacy Company codes existing in the system. Company codes currently in use in production system are:
1000 UK PN (Operations) Ltd

1010 UK PN Holdings Ltd
1020 UK PN Services Holdings
1500 UK PN (Transport) Ltd
1600 UK PN (IDNO) Ltd
1610 UK PN (IDNO Finance) Ltd
1620 UKPN Insurance Ltd
1700 EPN plc.
1800 LPN plc.
1900 SEPN plc.
5412 UK PNS (Commercial) Ltd
5520 PADCo Ltd
5555 UK PNS Powerlink Ltd
6100 UK PNS (Contracting) Ltd
6250 UK PN (South East Svces)
6910 UK PNS (Enterprises) Ltd
6920 UK PNS (PowerlinkHldgs)
6950 UK PNS (Asset Mgmt) Ltd
7010 UK PNS (South East) Invs
7100 UK PNS (Development) Ltd
7910 UK PNS (South East) Props
Company codes relevant for Procurement are as below:

Business Blueprint
1000–UK PN (Operations) Ltd

1500 – UK PN (Transport) Ltd
1700 – EPN plc.
1800 – LPN plc.
1900 – SPN plc.
5412 – UK PNS (Commercial) Ltd
5555 – UK PNS Powerlink Ltd
6100 – UK PNS (Contracting) Ltd
Company codes: 5412, 5555 and 6100 are used for the UK Power Networks Services Business.
Purchasing Organisation: Organisational unit subdividing an enterprise according to the requirements of Purchasing. A purchasing organisation procures materials and
services, negotiates conditions of purchase with vendors, and bears responsibility for such transactions.
Existing Purchasing Organisation:PO01-Procurement Org
There is a single Purchasing Organisation in the system.
Purchasing Group: The purchasing group can be defined as a person or group of people dealing with a certain product or group of products that are purchased through the
purchasing organisation. In larger organisations there are often groups of purchasing professionals in the purchasing department who work with certain suppliers or types of
suppliers.
Currently there are more than 500 Purchasing groups existing in the system. The current Purchasing group design is based on ‘P.O. Printing’ need rather than responsible
buyer.
Purchasing group for SAP SRM will drive the Buyer responsibility based on the Product Category and the organisational unit/department. The As-Is and the Proposed
structure is explained as below:
Current Procurement Enterprise Structure:

Business Blueprint
With the Centralised Purchasing Organisation there is an opportunity to negotiate centralised contracts which will be relevant for all business units/Directorates within
UKPN. But there will be some cases where we need to restrict usage of Outline Agreements for a specific Business unit/Directorate. In the current structure there is no
simple way to limit Procurement terms and conditions and specifics pricing to Directorates/Business units.
In the current structure, Purchasing groups are not aligned to category buyers but are aligned to business users which are not standard best practice. There is high number
of purchasing groups which needs a review and in the new application only relevant Purchasing groups need to be created/used.
Proposed Purchasing Organisation Structure:

Business Blueprint
In the proposed Purchasing Organisation structure, the Centralised Procurement organisation is retained, along with addition of three new Purchasing Orgs:
-Purchasing Org: Network Operations

-Purchasing Org: Corporate Procurement
-Purchasing Org: Capital Programmes
The Purchasing Org-Centralised Procurement will function same as it is working in current scenario.

Business Blueprint
The three new Purchasing orgs will have Purchasing groups assigned to each based on business requirement. Purchasing Groups contain Procurement Buyer. One Buyer
may be associated for multiple Purchasing groups.

Business Blueprint
The Proposed Purchasing Organisation structure continues with a Centralised Purchasing Organisation. So all the benefits associated with Centralised Purchasing
organisation remains intact. Additional Purchasing organisations enable effective enforcement of Procurement Policies and governance. This will enable the Procurement
with the ability to restrict usage of Outline Agreements by Directorate/Business Unit (this will address one of the current pain points).
The new structure will enable appropriate involvement of responsible Category buyers in the transactional procurement process. There will be a change to current
Procurement process which will require user training to manage the change.
The details of the proposed Purchasing organisation structure for the SAP SRM system are as below:

Business Blueprint
Purchasing Group Buyer Product Category Purchasing Org Org Unit/Department
Helen Wain Capex Capex –/ works Capex Procurement
Nigel Coatsworth Capex Capex –/Materials Capex Procurement
Tony Harwood Capex Capex –/Materials Capex Procurement
Matt Hogg Capex Capex –/Materials Capex Procurement
Caroline Pallister Corporate Corporate Corporate Procurement
Preethi George Corporate Corporate Corporate Procurement
Isaac Korenteng Corporate Corporate Corporate Procurement
Mercia Bartlett Opex Opex Opex Procurement
Michael Purcell Opex Opex Opex Procurement
Earl Lynch Opex Opex Opex Procurement
Olusola Onasanya Opex Opex Opex Procurement
Velina Lazenrova Opex Opex Opex Procurement
Organisational Structure Setup Strategic Sourcing:
2.2Master Data Considerations (including all relevant data relationships)
Master Data Description

Vendor Master is managed in Omnicom system and replicated to SAP system. A supplier can enter the system through a Vendor
Request or UVDB search in Achilles. In these examples the supplier’s details will be populated. Where a supplier does not exist
within Omnicom and they need to be added so that they can be used within the system i.e. contract bid list.
As part of Release1 Omnicom system is not being reviewed for replacement. During Release4-Strategic Sourcing Omnicom is to be
Vendor Master reviewed.
Any Vendor master cleansing in Omnicom or SAP system will be BAU activity with the support of BTP team.
Material Master (stock material) is owned by UKPN-Logistics team. Currently Procurement does not maintain Material Master. For
Material Master Release1-Corporate Procurement Material Master may be created for Internal Catalogue purposes.

Business Blueprint
. Service Master is owned by Procurement. Release1-Corporate Procurement may require rationalisation of Service Master to be
Service Master uploaded in the internal Catalogue. New Service Master may be required to be created for use of Corporate Procurement.
Material Group rationalisation is required. Taxonomy creation is in scope for Corporate Procurement-Release1. Material Group is
referred as Product Category in SAP SRM. Product Category is relevant for various linkages in terms of defining Purchasing Group
Material Group responsibility, links to Account assignment category, General Ledger account and enables spend reporting.
Material Group:
Material Group is a key that is used to group together several materials or services with the same attributes. Each Material or Service is assigned to a particular Material
Group. Material Groups are used for reporting purposes and can be used to restrict the scope of analysis and search Material Master records via search helps.
The Material Group (base Material Group) is the level in the Material Group hierarchy, which must be assigned directly to a material when it is created. It is defined across
the corporate group and sub-divides the complete material assortment from a business management viewpoint. Those Material Groups which themselves comprise
Material Groups are called Material Group hierarchy levels. A hierarchy level can have one or more other hierarchy levels (Material Groups) assigned to it.
For example: ‘Consultancy’ can be a Material Group hierarchy level and there can be other Material Groups assigned to it, such as Legal Consultancy, IT Consultancy,
Marketing Consultancy etc.
By structuring/linking Material Groups and Material Group hierarchy levels in a meaningful way, the Material Group hierarchy is created. SAP based ERP system uses set of
Material Groups that users must select in the Purchasing module in order to enable accounting mechanisms. Material Group is called Product Category in SAP SRM system.
Significance of Material Group:
-Material Group forms a Product/Service hierarchy
-Material Group (Product Category) is responsibility of Purchasing Group
-Links to Account Assignment Category
-Links to G/L Account

Business Blueprint
-Enables Spend Reporting
Background of UKPN Material Groups:
• Number of Material Groups available for user to select currently - 324

• Need identified for rationalisation of existing Material Groups to remove legacy Material Groups
• Need to build Material Group taxonomy / hierarchy
– to ease Material Group selection by requestor for free text orders
– to ensure accuracy of selected Material Groups as it determines supplier identification of:
• Responsible Purchasing Group / category buyer
• General Ledger accounts
• Requirement to maintain link between UKPN Material Groups (rationalised) and Codes in external classification standards (e.g. UNSPSC / CPV)
• This is to provide standardise interface to external procurement related applications e.g. External Catalogues, Achilles (or similar application),
Omnicom and any future applications
Recommended Classification Standard: UNSPSC Classification with mapping table to Achilles
UNSPSC: United Nations Standard Products and Services Code
What is UNSPSC?
• United Nations Standard Products and Services Code

• A classification standards that is jointly developed by the United Nations Development Programme (UNDP) and Dun & Bradstreet Corporation
• Currently managed by GS1 US (an international non-profit organisation)
• Open Source Standards
• It’s hierarchical classification with 4 levels Recommendation on usage of Classification Standards:
• Use UNSPSC Classification Standards to align UKPN Material Groups

• Build a mapping table between UKPN Material Groups and external Procurement specific systems (Achilles and future Punch-Out Catalogues)
– Example of mapping table:

Business Blueprint
2.3 System Configuration Considerations
Transaction code SAP Project Runtime Object (SPRO)

Business Blueprint
2.4 Level 5 Processes

2.4.1 Identify Opportunities Process

Business Blueprint
Identify Opportunities Process Description
Solution Type (E-

Proce Process Step Related Business Enhancement, S- SAP Transaction
Solution RICEFW Actor
ss ID (L5) Requirement Standard, M- code/ Menu path
Manual)
2.1.1 Select a Ability to enable category a) To enable the Category strategy module Yes R4-CS-C-01 Category
template manager to identify the through Project module provided by SAP manager
list of opportunities. E- Category manager Sourcing.
b) The Category manager will select the
Category type template from the selection
screen
c) The category type template will have
the collaborators added.
d) This information will be captured during
Draft phase of the Category
e) The Category manager will fill up the
header data.
2.1.2 Update header The category specialist will a) The Category manager being the owner Yes R4-CS-E-01 Category
data document the of the document will fill up the header manager
requirement details with Name of the Category
definition and will give the relevant
validity period and the expected Savings
potential and the estimated value.
For all this the Category manager will have
the input fields where he can enter the
required values
2.1.3 Add Adding the relevant a) The Category manager being the owner Yes NA Category
Collaborators stakeholders who will of the document will be able to add the manager
provide the Business plan collaborators to the Category document
and portfolio plan

Business Blueprint
Solution Type (E-

Manual)
2.1.4 Receive The relevant stakeholders a) The Category manager being the owner Yes R4-CS-E-02 Collaborator
Notifications will be able to add the of the document will be able to add the
business plan, portfolio collaborators to the Category document
plan. and will send the notification to the
collaborators.
2.1.5 Update Enable planning for the a) The Category manager will list down the Yes R4-CS-C-02 Category
schedule tasks activities like opportunities task and dependences and will schedule a manager
identification and timeline for uploading each and every task
marketplace assessment and the relevant owner where the mail
activities will be triggered to those respective
stakeholders.
The Category manager will change the
phase to the Gathering information phase
2.1.6 Change NA Data gathering phase will initiate / trigger NA NA Category
document the notifications to respective manager
phase to ‘Data collaborators who have been assigned
gathering’ tasks to submit various data such as
business plan, high level
requirements ,lessons learnt etc.
2.1.7 Receive Data gathering phase will initiate / trigger NA R4-CS-E-03 Commercial
notification the notifications to respective Manager
collaborators.
2.1.8 Provide lessons The category specialist will The category manager will update the Yes NA Commercial
learnt compile all the learning’s category strategy document with the Manager
Formal Lessons learned lessons learnt. To update this a section
from current/ historic will be provided in the Category
contracts Contractor Management module with big text and
attachment facility

Business Blueprint
Solution Type (E-

Manual)
performance reports and

the Master agreements
with performance metrics
due based on which the
Opportunities identified by
Procurement / rest of
Business
2.1.9 Receive inputs Category manager will To capture the business requirement NA NA Category
gather the business information as an attachment in the Manager
requirement like Category Management module and
 Scope of Service adding the big text
 Business Process
 Interdependencie
s with other
Directorates
 Cost factor
 Service level
expected
Time scale
2.1.10 Receive NA Data gathering phase will initiate trigger NA NA Collaborator
notifications the notifications to respective
collaborators.
2.1.11 Submit NA Application to enable collaboration NA NA Collaborator

necessary data between Procurement and business
Collaborators to mutually share the
information.

Business Blueprint
Solution Type (E-

Manual)
2.1.12 Perform NA Category manager will perform required NA NA Category

required analysis based on the received inputs. manager
analysis
2.1.13 Provide inputs NA Category Specialist will perform required NA NA Category

analysis and will provide inputs to the manager
Category manager.
2.1.14 Validate inputs NA Category manager will receive the input NA NA Category
from the category specialist and will manager
validate the input.
2.1.15 Phase moved to Category Manager will The Category Manager will capture the Yes NA Category
analysis receive a notification to data in the Analysis tab. Manager
Compile and analyse the There will be a section to capture the
information gathered. historic spend analysis data and also the
Analysed spend data and contract audit requirement data.
identified improvement There will be a Big text and Attachment
opportunities based on that will be created in the space Analysis
the business needs tab
Category Manager will
prepare the baseline of
spend and the generation
of expected future annual
spend for the
External suppliers,
Suppliers for 80% of spend
under contract
Items, buyers, Key internal
customers. The Category

Business Blueprint
Solution Type (E-

Manual)
manager will analyse

Category wide spend
2.1.16 Perform Category Manager will receive a NA NA Category

Analysis notification to Compile and analyse the Manager
information gathered.
Analysed spend data and identified
improvement opportunities based on the
business needs
2.1.17 Draft a list of The Category Manager will Once when all the tasks are completed by Yes R4-CS-E-04 Category
desired identify the opportunities the various stakeholders and the Manager
outcomes and will analyse to identify compilation is done then a notification will
the potential go to the Category specialist to identify
opportunities for the the opportunities.
increased value in each There will be a placeholder to document
spend area / category the opportunities
Notification to the
Category Specialist to
Capture the Opportunities
Captured opportunities
based on several criteria
2.1.18 Change NA Once the list of desired outcomes are NA NA Category
document drafted, the document phase is changed Manager
phase to to the Category Strategy
category
strategy
2.1.19 Review and The Category Manager will The Category Manager will now the move Yes R4-CS-W-01 Head of
approve of the capture the opportunity the phase to the approval phase. Once Procurement
Category and produce a high level when the phase will be moved to the R4-CS-E-05

Business Blueprint
Solution Type (E-

Manual)
Strategy category approach and approval phase the document will be

document send to head of locked and then the mail will be triggered
procurement for approval. to the collaborators who will further
The head of procurement follow the link and will go to the Category
will review and sign off the document for approval. The approver will
proposed category review the document and add his
approach which will be comments and will approve the
agreed and signed by the document.
business to come to the If there are any missing documents the
approach/ strategy for approver can reject the document and put
each category his comments and the phase will be
changed to the previous requirement
gathering phase. If the document is
approved then the phase will go the
Market research phase
2.1.20 Approved NA The Category Manager will capture the NA NA Head of
opportunity and produce a high level Procurement
Category Strategy and send for approval
to the head of procurement. If it is not
approved , it is send back to the Category
manager to make the changes suggested
by the Head of Procurement
2.1.21 Approved NA Following the approval from the head of NA NA EMT

procurement, the document will be
forwarded to the EMT for approval. If it is
not approved , it is send back to the
Category manager to make the changes
suggested by EMT

Business Blueprint
Solution Type (E-

Manual)
2.1.22 Category NA Following to the approval from the head NA NA Category

Strategy Active of procurement and EMT, there will be an Manager
active category strategy.
2. 2 Sub Category Approach Process

Business Blueprint
Sub Category Approach Process Description

Business Blueprint
Solution Type (E-

Proces Process Step Enhancement, S- SAP Transaction
Related Business Requirement Solution RICEFW Actor
s ID (L5) Standard, M- code/ Menu path
Manual)
Active Active category strategy in place NA Category

2.2.1 category Manager
Strategy
Select the The category specialist will a) The category specialist will check Yes NA Category
category check service and materials the complete documentation that is Specialist
strategy and requirements for the category, available in the Category Management
create follow to supplement the high level module to make the decision.
on sub business requirements which are b) The category specialist will move
category already identified. the phase from market place
strategy The category understands the assessment to closed so that the team
2.2.2 impact of the detailed can move to the next business process
requirements on wider business
and supply chain route and will
also collect the spend data and
also the cost element drivers
which drive the decision making
process
Select the The category specialist will a)To enable the Project module NA R4-SCS-C-01 Category
template to a create the category service or provided by SAP E-Sourcing. Specialist
create sub material that fits in to risk or b) The category specialist will select
category value model the Project type template from the
strategy selection screen based on the category
that is finalized
2.2.3
c) The project template will have the
collaborators added
d) This information will be captured
during Draft phase of the Project
e) The category specialist will fill up
the header data

Business Blueprint
Solution Type (E-

Manual)
Update the The category specialist will fill a) In the project under the header tab Yes R4-SCS-E-01 Category
sub category the header data to compile the the Category specialist will fill in the Specialist
strategy data of the relevant sub category details for
header data Status
Description
Name*
Priority of the Project
2.2.4
Phase
Type
Company
Product Category
Currency*
Project Classification
*Mandatory Fields
Update The category specialist will a) In the project under the header data NA NA Category
detailed Collate granular spend data from tab the category specialist will list Specialist
spend data management information and down the
current supplier reports Estimated value
2.2.5 Budgeted value
Savings target
There will be fields that will be
provided to category specialist to
capture this data
Add Adding the relevant stakeholders a) The category specialist being the NA NA Category
collaborators who will provide the Business owner of the document will be able to Specialist
plan and portfolio plan add the collaborators and the
2.2.6
Managers to the Project Management
document

Business Blueprint
Solution Type (E-

Manual)
Receive The relevant stakeholders will a) On saving the document by the Yes R4-SCS-E-02 Category
Notifications receive the notification to add Category specialist a mail notification manager
the relevant plans will go to the Collaborators and the
Category Manager to add the relevant
2.2.7 plans.
With the link that will be provided to
the Managers they can click on the link
and access the project document
directly.
Receive The relevant stakeholders will a) On saving the document by the Yes R4-SCS-E-02 Collaborator(SM
Notifications receive the notification to add Category specialist a mail notification T)
the relevant plans will go to the Collaborators and the
Category Manager to add the relevant
plans.
2.2.8
With the link that will be provided to
the Managers they can click on the link
and access the project document
directly.
2.2.9 Attach the The category specialist will be a) The category specialist will be able NA NA Category
spend able to build a TCO model for the to upload the spend analysis data Specialist
Analysis required product / service. A there will a section provided for the
report, the detailed category spend profile data to be captured with the big text
TCO model will be based on the detailed and attachment
and capture spend data. For e.g. what is
the results being procured, in what volumes
/ proportions. Whole life
contract value to be forecasted
including estimates of any
inflation or indexation.

Business Blueprint
Solution Type (E-

Manual)
The total cost drivers for the

total cost of ownership of the
material / services (i.e.
maintenance, internal costs,
delivery, transport)
Draft the The category specialist will draft a) The category specialist will put the Yes NA Category
category the category approach draft category approach document. Specialist
Approach document. The category baseline The phase will be changed to Category
will be defined as current spend Approach initialization in project
and therefore the addressable document which will be reviewed by
2.2.10
spend for forthcoming events. the Category Managers
Update the The category specialist will a) The category specialist will upload NA NA Category
final Category Utilize all information and the work plan and Annual work plan Specialist
Plan and analysis undertaken to date, document. There will be an
Annual Work revise the draft Category attachment functionality provided to
Plan Management Plan and Work capture the plans
2.2.11
Plan to produce the final
Category Management Plan and
Final Annual Work plan prior to
agreeing with Business.
Update the The category specialist will a) The category specialist will NA NA Category
2.2.12 risk register undertake a category risk categorize the list under the Risk Tab. Specialist
for the assessment, identifying and b) Under the risk management tab

Business Blueprint
Solution Type (E-

Manual)
category quantifying potential, separate sections will be created to

operational, social, political, capture the relevant risks. There will
environmental, financial and be dependencies that will be
legal risks. associated to it.
c) A dropdown table will be provided
to collect the required risks and add
further description to it so that the
relevant risk can be captured in the
project document
Phase NA The phase of the document is changed NA NA Category
changed to to the sub category approval. Specialist
2.2.13 sub category
strategy
approval
2.2.14 Approve? The Category Manager will The category specialist will now move Yes R4-SCS-W-01 Category
review and agree the category the phase to the Approval phase. The R4-SCS-E-03 Manager
baseline (for future benefits document will be locked and then the
measurement and sign off), the mail will be triggered to the
Category Management Plan, and collaborators who will further follow
the Annual Work Plan. Sourcing the link and will go to the Project
event resource requirements document for approval. The category
should be agreed at this stage. manager will review the document and
add his comments and will approve
the document.
If there are any missing documents the
approver can reject the document and
put his comments and the phase will
be changed to the Draft phase
requirement gathering phase. The
category managers will be able to

Business Blueprint
Solution Type (E-

Manual)
review the document and if they reject

the document the phase will be
changed and the category specialist
will be able to make changes to the
Category Management Plan and
Annual Work Plan, incorporating any
comments from the Business. After
performing changes the contract
specialist then again trigger an
approval workflow for further review
If they approve the document the

document will go for next phase
automatically.
Approve the NA Collaborator will approve the sub NA NA Collaborators(S

category category strategy once approved by MT)
2.2.15 approach & the Category Manager
plan
Final agreed Category specialist can move to After approval final project document Yes NA Category
sub category the Contract approach phase. will be created with Executed phase. Specialist
strategy
2.2.16

Business Blueprint
2.3 Contracting Approach Process

Business Blueprint
In the Header tab of Contract Approach, the Sub Category Strategy Project document will be linked in the document link section.

Business Blueprint
The Sub Category Strategy Project document will be linked in the document link section of Contract Approach Project type.
Contracting Approach Process Description
Process Process Step (L5) Related Business Solution RICEFW Solution Type Actor SAP Transaction
ID Requirement (E- code
Enhancement,
S-Standard, M-
Manual)
2.3.1 Category Plan & Initiate the contracting approach with the NA NA Category
Annual work plan inputs from Category plan and annual Specialist
project work plan.
2.3.2 Create Contract The category specialist will a) The category specialist will Yes R4-CA-E-01 Category
Approach project Detail Sourcing create Contract Approach Specialist
by selecting the requirements, including document by selecting the
Template as current and, if necessary, Project Template ‘Contracting
Contracting to be business process flow Approach’. The Sub Category
Approach from detailing Strategy Project document will
Annual work plan interdependencies with be linked in the document link
other teams or section of Contract Approach
Project type.
Directorates
b) The Category specialist will fill in
the header details of Category
Approach;
Status
Description
Name*
Phase
Type
Company
Product Category
Currency*
*Mandatory Fields

Business Blueprint
Enhancement,
S-Standard, M-
Manual)
2.3.3 Add collaborators Adding the relevant a) The category specialist being the owner NA NA Category
to form sourcing stakeholders who will of the document will be able to add the Specialist
team( if required) provide the Business plan collaborators and the Managers to the
and portfolio plan Contract Approach document. There will
be different groups that will be created
that will include the people from the
specified business groups.
2.3.4 Attach the draft The business team will The category specialist will attach this NA NA Category
of requirement provide a formal Statement document under a section created in the Specialist
document to the of Requirements document Contract Approach document where
Contract (template), detailing the there wills Attachment facility available
Approach required scope for the with description to be filled in. These
document sourcing event in terms of details will be updated when the
products / services, document is in Draft phase.
resources, outcomes,
current and, if necessary,
to be business process flow
detailing
interdependencies with
other teams or
Directorates
2.3.5 Move the phase The business team will The category specialist will move the NA NA Category
of the document provide a formal Statement phase to the Requirement Review phase Specialist
to “Requirement of Requirements document of the document
Review” phase (template), detailing the
required scope for the
sourcing event in terms of

Business Blueprint
Enhancement,
S-Standard, M-
Manual)
products / services,
resources, outcomes,
current and, if necessary,
to be business process flow
detailing
other teams or
Directorates
2.3.6 Receive The Sourcing Team will After the phase is changed to Yes R4-CA-E-02 Collaborators
notification to review and where Requirement Review the workflow will be ( Sourcing Team)
review the necessary challenge the triggered to notify the users but there will
requirements requirements provided by be no decision but internally the status
the Business Users in order will be set as Reviewed and the workflow
to agree final requirements will then unlock the document so that it
for the sourcing event can be manually changed to the next
phase
2.3.7 Collaborate with The sourcing team will There will be a discussion board that will Yes R4-CA-E-03 Collaborators
Category review the document be set up for the requirement topic ( Sourcing Team)
specialist using internally and check discussion. It will allow the category
discussion board the Agreed statement specialist to select the list of collaborators
of requirements and that it would like to collaborate for taking
specifications the discussion further.
A mail notification will be sent to business
collaborators and the sourcing team. The
collaborators will now be able to
participate in the discussion and will able
to review the document.
2.3.8 Review/Edit & The business team will Sourcing team members will (specifically NA NA Collaborators
upload the review the formal the business users) update the Contract ( Sourcing Team)

Business Blueprint
Enhancement,
S-Standard, M-
Manual)
technical Statement of Approach document with the finalised
specification Requirements document technical specification document.
document. (template) This document will include all necessary
, detailing the required technical details which are needed – (a)
scope for the sourcing for business to execute the work in
event in terms of question (b) for supplier to be able to
products / services, respond to the tender event
resources, outcomes, A place holder will be provided in the
current and, if necessary, Contract Approach document to attach
to be business process flow these documents.
detailing
other teams or
Directorates
2.3.9 Perform The business user will Regulatory impact analysis will be NA NA Collaborators
regulatory impact perform the TUPE, performed by relevant members of the ( Sourcing Team)
analysis & attach regulatory change, sourcing team. This will be an offline
necessary customer impact. The activity, however, Contract Approach
analysis. sourcing team category document will have a section where the
specialists marks process sourcing team member will attach the
step as complete and summary of regulatory impact analysis.
progresses to the next step
2.3.10 Update CGM Application to enable A custom tab named – Gate A- will be Yes NA Category
Gate A PAPER process orchestration available on the Contract Approach Specialist
Tab + Move the through automated document (type Contracting Approach).
Contract workflows After completion of the various analysis
Approach Phase undertaken by the Sourcing team, the
to Sponsor category specialist will update the
Approval summary of the analysis in ‘Gate A’ tab.

Business Blueprint
Enhancement,
S-Standard, M-
Manual)
Once completed, category specialist will
change phase of the Contract Approach
document to ‘Sponsor Approval’.
Application will validate if the ‘Gate A’ tab
page information is updated when
changing the phase.
2.3.11 Receive approval Sponsor will review the CGM Gate A Sponsors
request and paper and review GATE tab. (AM/NO/CPP)
review info in
CGM and GATE A
tab
2.3.12 Approved? Application to enable Change in phase of the Contract Approach Yes R4-CA-W-01 Sponsors
process orchestration document will trigger an approval (AM/NO/CPP)
through automated workflow. The workflow will send relevant
workflows notifications to the relevant sponsors
defined as collaborators in the Contract
Approach document.
Upon rejection, the category specialist will
be notified and Contract Approach
document will be sent back to the
Category Specialist to rework as stated by
sponsors in their rejection notes.
2.3.13 Output CGM Gate Application to accelerate, Upon approval from all sponsors, category Yes R4-CA-F-01 Category
A PAPER & possibly automate creation specialist will trigger output of Gate A Specialist
Present it in CGM of GATE A paper and paper, which can later printed and
approval process presented in the CGM
2.3.14 Approved by Application to record After attaching the output of the CGM Yes R4-CA-W-02 Category

Business Blueprint
Enhancement,
S-Standard, M-
Manual)
CGM? approval decision in CGM Gate A paper, Category Specialist will Specialist
move the ‘Contract Approach’ phase to
‘CGM Approval’.
This will trigger a workflow. Category
specialist will be the approver (on behalf
of CGM) in the case.
Category specialist will need to present
the Gate A paper in CGM and seek for the
sign-off.
2.3.15 Attach signed Application to ensure the If the Gate A paper is approved in CGM, NA Category
CGM Gate A Gate A paper to be signed Category specialist will need to scan and Specialist
Paper & move off before commencing the attach the signed paper to the Contract
‘Prequalification’ Approach document.
the phase to
Once attached, category specialist will
“PREQUALIFICATI
approve the Contract Approach on behalf
ON IN- of CGM. If approved, Contract Approach
PROGRESS” phase will be automatically changed to
‘Prequalification in Progress
2.4 Pre-Qualification Process

Business Blueprint

Business Blueprint
Process ID Process Step Related Business Solution RICEFW Solution Actor SAP Transaction
(L5) Requirement Type (E- code/ Menu path
Enhancemen
t, S-
Standard,
M-Manual)
2.4.1 Create a new Ability to start NA NA Category NA
RFx of prequalification process Specialist
The Category Specialist will change the phase of the Project
document following sign-off of
document to “Prequalification” after the document is used for
type Gate A (Contracting
signing off Gate A paper (contracting approach) and create a
‘Prequalificati Approach)
new RFx (new round) of type ‘Prequalification’. The
on’ from the
collaborators will be added to the new Rfx document.
Project
document
2.4.2 Phase change Prequalification of the Following the phase change of the RFI document to NA R4_PQ_I_01 Category NA
to ‘Open for suppliers should be ‘Prequalification Open for Review’, Category Specialist will log Specialist
Review’ and enabled by the system. on to Achilles to start the prequalification process.
login to The prequalification
Achilles for should include ability to
the identify suppliers, invite
prequalificati suppliers, issue
on questionnaire to the
suppliers, ability to
receive and compare
their responses and
ability evaluate and
shortlist suppliers. It is
also required to transfer
the shortlisted suppliers
for sourcing application
for further sourcing

Business Blueprint
Enhancemen
t, S-
Standard,
M-Manual)
activities.
2.4.3 Select the Ability to identify In Achilles database, suppliers are linked with the Categories. NA NA Achilles NA
Product suppliers for Hence shortlisting process is started with searching of
categories prequalification process supplier with appropriate category. As per current processes,
within prequalification process will be executed in Achilles
Achilles and
start
prequalificati
on process
2.4.4 Review Ability to evaluate NA NA Achilles NA
shortlisted suppliers as per the Achilles will provide (as currently used) an ability for the
suppliers prequalification criteria Category Specialist to compare and evaluate the supplier
set during Gate A paper responses for the prequalification process.
process
2.4.5 Prepare and Ability to send additional If suppliers responses to initial set of questions are NA NA Achilles NA
Publish questionnaire to the insufficient for the Category Specialist to shortlist the
Additional suppliers to support ‘qualified’ suppliers, Additional Questions will be formulated
questions to supplier evaluation and posed to the participating suppliers for them to respond
the suppliers process to. This will be enabled by Achilles application ( as currently
(if necessary) being used by UK Power Networks)
2.4.6 Suppliers Ability to send additional NA NA Achilles NA
receive questionnaire to the Supplier will receive the Additional Questions published by
Additional suppliers to support the Category Specialist through Achilles application. Suppliers
Questionnaire supplier evaluation will have access to Achilles portal and will be able access
from UK process these questions anytime once published by the Category
Power Specialist
Networks
2.4.7 Suppliers Ability to collaborate NA NA Achilles NA
raise queries with suppliers In case of any queries, suppliers will be able to use Achilles
application send their queries back to Category Specialists

Business Blueprint
Enhancemen
t, S-
Standard,
M-Manual)
2.4.8 Category Ability for suppliers to Suppliers will be able to update their responses / answers to NA NA Achilles NA
Specialist collaborate with the queries and submit it back to the Category Specialist.
Respond to category specialists Transfer of this information will enabled through Achilles
queries application
2.4.9 Supplier send Ability of suppliers to be Supplier will login to sourcing portal to submit answers to the NA NA Achilles NA
responses able to send the questionnaire. Supplier will also update the draft contract
responses electronically document and send it back to
2.4.10 Category Ability for a Category NA NA Achilles NA
Specialist Specialist to respond to
Achilles application will deliver queries or responses from the
receive the supplier queries as
suppliers to the respective Category Specialist.
Responses well as receive their
answers electronically
2.4.11 Evaluate Ability to evaluate the Achilles application will provide an ability to compare the NA NA Achilles NA
Responses responses received from responses to prequalification questionnaire. It will be able to
multiple suppliers analyse the responses considering the weightage of the
questions, type of questions (qualitative /quantitative) etc.
2.4.12 Short List Ability for Category Yes R4_PQ_I_01 Category NA
An interface will be built between Achilles and SAP
Suppliers and Specialist to be able to Specialist
application which will enable transfer of the suppliers from
transfer to shortlist the supplier
Achilles to SAP. The transfer will be initiated by the Category
Sourcing for following the evaluation
Specialist. Once completed, the supplier tab of the RFI
further and transfer list of
document will have a list of shortlisted suppliers updated
processing suppliers to SAP
2.4.13 Change Phase Ability to output Gate B Once the supplier transfer is completed from Achilles, Yes R4_PQ_E_01 Category NA
of Project to paper Category Specialist will change the Project document to ‘Gate Specialist
‘prepare Gate B Preparation’. To do the field level validation
B paper’
2.4.14 Prepare Gate Ability to output Gate B In Project document, a tab will be available for updating Gate Yes R4_PQ_F_01 Category NA
B paper B paper content. This will be populated by the Category Specialist
Specialist. This content will be a summary of the analysis
performed to shortlist the prequalified suppliers. The details

Business Blueprint
Enhancemen
t, S-
Standard,
M-Manual)
of this analysis will be available as attachment to the same RFI
document.
2.4.15 Analyse and Preparation for the RFP NA NA Sourcing NA
Consolidate (event) should be Sourcing team members will revisit the draft contract Team
Requirements enabled by the system document and fine tune the same
2.4.16 Prepare for Preparation for the RFP NA NA Sourcing NA

During RFP process, supplier responses will be categorised in
RFx process (event) should be Team
2 parts –
by adding enabled by the system
1) Response to draft Contract document
questionnaire
2) Response to Questions asked by the UK Power Networks
from the
For the responses to the questions, the questions to be added
available
to the RFP document. During Gate B preparation phase,
library and
sourcing team will add the questions to the RFP Document.
Phase Change
Once this activity is completed, sourcing team will change the
to Open for
phase of RFx document to ‘Open for Response’
Response
2.4.18 Create the Preparation of the MA Create a Master agreement document and add the legal NA NA Category NA
Terms and and attaching the terms and conditions document as a Contract document. Put specialist
Conditions baseline Legal and terms the contract document in Internal review phase and also have
document condition document a dummy supplier updated in the Master agreement
2.4.19 Approved for SMT and Sponsors Phase change in previous step will trigger an approval Yes R4-PQ-W-01 All NA
Gate B needs to approve the workflow in Project document. SMT team members Directorates
preparation for Gate B (identified by roles in the list of collaborators) will receive - SMT
paper request to review and accept preparation for the RFx which
includes –
1) Draft Contract to be issued to the bidders
2) Questionnaire & respective weightings
2.4.20 Approval by Gate B preparation Respective approvers from the RFx’s collaborators tab will Yes R4-PQ-W-01 Sponsors NA
Sponsor needs to approved by receive the request to approve Gate B paper.
the Sponsors before Sponsors can display the summary of Gate B paper in the RFx

Business Blueprint
Enhancemen
t, S-
Standard,
M-Manual)
seeking approval from document by accessing the ‘Gate B’ tab of the RFx or by
CGM downloading the gate B paper.
If the Gate B paper is rejected by any of the sponsors, the
phase of the document will be reset to ‘Draft’ and notification
will be sent to Category Specialist.
Upon approval notification will be sent to ‘Category Specialist’
2.4.21 Approval by CGM need to approve On receipt of the approval notification, Category Specialist NA NA CGM NA
CGM the Gate B paper will present the Gate B paper in the CGM and seek formal
approval by the members.
If approved, the signed copy of the Gate B paper, will be
attached to the RFx document and the phase of the
document will be set as ‘Approved by CGM’.
If rejected by CGM, the phase of the RFx document is
changed back to draft. After making necessary changes to the
document, the Category Specialist will put the document back
into each phase and re-request all approvals providing the
detailed reason for this request.
2.4.22 Phase NA Gate B paper will be presented by the Category Specialist in NA NA Category NA
changed to the CGM. Physically signed Gate B paper (if approved) will be Specialist
‘Gate B’ attached to the RFx as an evidence. With this, Category
approved Specialist will change the phase to ‘Gate B approved’
2.4.23 Attach Gate B Ability to output and Category Specialist will be able to generate the Gate B form Yes R4_PQ_F_01 Category NA
paper attach Gate B paper to using the custom functionality developed in the RFx Specialist
the RFx document document. The generated word document (Gate B Paper) will
be reviewed by the Category Specialist and post review the
document will be attached to the RFx event.

Business Blueprint
2.5 Request for Proposal (RFP) Process
Request for Proposal Process Description

Business Blueprint
Process ID Process Step Related Business Solution RICEFW Solution Type Actor SAP Transaction
(L5) Requirement (E- code/ Menu path
Enhancement,
S-Standard, M-
Manual)
2.5.1 Create new Ability to run After prequalification, the Category Specialist will Yes R4_RF_E_01 Category NA
RFx tendering event in create a new round of RFx with reference to Specialist
document alignment with prequalification RFx document.
type of RFP the regulatory Both RFxs will be linked to each other and also to
type requirements the overarching Project documents
The field level validation to be done after the Gate B
approved.
2.5.2 Prepare RFx Ability for a A library of Frequently asked questions will be Yes R4_RF_C_01 Category NA
questionnair Category created and made available for the user to select R4_RF_C_02 Specialist
e Specialist to the set of questions from this library. R4_RF_E_02
customise the RFP These questions could be qualitative and
event by drafting quantitative and must be about Capability and
the questions and Capacity and not ability – EU Regulation
assigning relevant requirement
importance Category specialist can create custom questions at
(weightage) to the the point of drafting the RFx document.
questions The questions will be in the form of multiple choice,
number or text fields.
The evaluation parameters are set for the
questionnaire.
Scoring can be set.
The schedule can be set for the RFP responses
There will be one question where Category specialist
will add a check box to ensure whether the supplier
has gone through the Legal terms and condition
document
2.5.3 Issue RFP Ability to invite Category specialist will publish the RFP when it’s Yes R4_RF_E_03 Category NA
suppliers for ready. Specialist
bidding by issuing System will send email notification to the Contact
the RFP person maintained in the supplier master (bidder) in
electronically. the sourcing.

Business Blueprint
Enhancement,
S-Standard, M-
Manual)
2.5.4 Receive RFP NA Suppliers will receive RFP NA NA Suppliers NA
2.5.5 Provide NA Suppliers can communicate with Category Specialist NA NA Suppliers NA
Clarification if they have some queries or if they need
Required clarification
2.5.6 Respond to NA Category specialist to respond to the suppliers NA NA Category NA

queries queries. Specialist
Default response to all suppliers but can be selective
if necessary (Commercially sensitive)
2.5.7 Submit RFP NA Supplier to submit the RFP responses if they don’t NA NA Suppliers NA
responses have any queries.
All bids will be ’locked’ for review by Category
Specialist until the closing date.
Suppliers may make changes to submissions up until
closing date and time of RFP
2.5.8 Receive RFx Ability to Supplier will receive the email notification. The NA NA Category NA
Responses electronically notification itself will have a URL to RFx document Specialist
receive responses for the supplier to access. It will also contain the
from the bidders login credentials for the supplier user to login to the
back to category Sourcing portal.
specialists / Once logged in, supplier can see the RFP issued by
sourcing team the Category Specialist and then respond to the
same through the same portal.
Supplier will review schedule, deadlines and
milestone, sections and attachments (Legal Term
document)
2.5.9 Phase RFP process Once all responses are received, Category Specialist NA NA Category NA
change to should have clear can manually change the ‘phase’ of the RFP Specialist
‘Closed distinction document as ‘Closed Responses’ commencing the
Responses’ between various start of comparison of received bids.
phases within The phase will also automatically change to ‘Closed

Business Blueprint
Enhancement,
S-Standard, M-
Manual)
tendering process Responses’ if the RFP is closed (validity period
ended) for responses
2..5.10 Receive Ability to Automatic or manual phase change of the RFP to NA NA Supplier NA
notification communicate ‘Bid Evaluation’ will lock the RFP document for any
about the with all further responses. i.e. supplier will not be able to
closure participants as submit any responses through the sourcing portal.
‘Response’ and when System will issue a relevant error if the supplier tries
phase of required. to submit the response.
the event
2.5.11 Evaluate Ability to compare Category specialist / Sourcing team can only display NA NA Category NA
responses responses and compare the responses when the RFP Specialist
and shortlist submitted by the document is in ‘Bid Evaluation’ phase.
suppliers bidders based on Various standard reports will enable the user to
pre-set , score and analyse the responses based.
confidential Category specialists will shortlist the suppliers for
criteria the negotiations.
2.5.13 Accept and Ability to Category specialist will accept the bids of the NA NA Category NA
Reject electronically shortlisted bidders and reject the remaining specialist
Response accepts and reject suppliers.
the bids At this point, a notification will be sent to all the
submitted by the bidders about their respective decision.
bidders.
2.5.14 Attach the The Legal terms In the MA under the contract document tab upload NA NA Category
legal and condition the Legal terms and condition document that is specialist
document document to be received from the supplier.
to the upload in the MA
contract
document

Business Blueprint
2.6 Negotiation Process

Business Blueprint

Business Blueprint
Negotiation Process Description
Process ID Process Step Related Solution RICEFW Solution Type (E- Actor SAP Transaction
(L5) Business Enhancement, S- code/ Menu path
Requirement Standard, M-
Manual)
2.6.1 Change phase Ability to record After completing the RFP process, Category Specialist NA R4_NG_E_01 Category NA
to “Initiate details of will change the phase of the Project document to Specialist
negotiations” negotiation ‘Initiate Negotiations’ to mark the commencement of
in Project process the negotiations.
document
2.6.2 Create new NA Category Specialist will then create a new round of NA NA Category NA
RFx of type RFx with reference exiting (RFP) type document. Specialist
‘Negotiations’ This will copy all relevant details of the RFP document
such as collaborators, accepted bidders etc.
2.6.3 Issue RFx to NA Category Specialist will validate information in the NA NA Category NA
the shortlisted new RFx document and re-issue the document to the Specialist
bidders shortlisted bidders in the RFP stage.
2.6.4 Receive RFx NA Reissue of the RFx document will send the Yes R4_NG_E_02 Supplier NA
information notifications to the bidders.
Bidders can log in to the Sourcing application (and to a
specific event) using the URL in the mail.
2.6.5 Submit NA Bidders will be able to respond to the new round of NA NA Category NA
response to RFx (negotiations); however this response is generally Specialist
the RFx submitted post discussions / negotiations through a
meeting
2.6.6 Conduct NA Shortlisted bidders in previous round (RFP) will be NA NA Category NA
meetings invited for a discussions. During these discussions, Specialist
/discussions both the parties will negotiate the terms and
conditions and other relevant aspects of the contract.
2.6.7 Refine NA Post negotiations, if required, bidder will update the NA NA Supplier NA
responses and response (through the portal access) and submit it
resubmit back to UK Power Networks.
2.6.8 Compare the Compare the Post negotiations the supplier will send a Legal NA NA Category NA
Baseline legal baseline document that they have accepted and agreed. The Specialist

Business Blueprint
Manual)
document documents same document will be uploaded by the supplier to
with the the Contract document tab and will change the phase
document as supplier negotiation. With this the Category
received from specialist will be able to compare the document and
the Supplier will be able to achieve the red-lining and will be able
to compare the document from the base document to
the newly submitted document by the Supplier.
2.6.9 Accept and NA Upon receipt of the response from the bidders, NA NA Category NA
Reject Category Specialist (along with sourcing team) will Specialist
responses review and evaluate the responses. The responses can
following the only be opened once the bid submission time for the
discussions event is over.
If required, Category Specialist can also extend the bid
response time for the bidders. The information about
event timings can be maintained on RFx header tab
page. While saving the decision about response
acceptance / rejection, the application will check the
value of the tender and the ‘Risk Category’ of the
event.
2.6.10 Is RFx value NA If the value of the tender is >250K or is tender for NA NA Category NA
£250 k or high ‘High Risk’ activity, prepare the gate C paper and Specialist
value? attach. If the value of the event is higher than
£250,000 or the risk category is ‘High’, application will
make it mandatory for the user (Category Specialist/
sourcing team member) to enter the information on
the Gate C tab of the event.
For low risk and < 250K value event, Procurement will
create an event and provide a reference number to
business (traditionally known as net number).
Business will run the 3 bid process and identify the

Business Blueprint
Manual)
shortlisted bidders and submit evidences to Category
Specialist. Category specialist will update the
evidences in the respective event and provide
approval and if necessary create an outline
agreement.
2.6.11 Prepare and NA Prepare the ‘Gate C’ paper. Output will be manually Yes R4_NG_F_01 Category NA
attach Gate C triggered by the user however will be generated Specialist
paper in automatically by the application.
Project
document
2.6.12 Change phase NA Post closure of event for receiving responses, phase of NA NA Category NA
to ‘Award;’ the RFx will automatically change to ‘Bid Evaluation’. Specialist
A decision to award the contract is taken following
comparison of these responses which are the
downstream processes that will be a part of contract
management.
To begin the proceeding for contract award, Category
Specialist will manually change the phase of the
Award. If the RFx event has ‘Gate C’ paper attached,
system will trigger an approval workflow to CGM.
2.6.13 Approved NA Category specialist will present the Gate C paper in Yes R4_NG_W_01 Collaborators of NA
CGM and seek approval in the Project Management type CGM and
module, if approved, the category specialist will HOP
attached the signed & scanned copy of the CGM and
HOP paper to the RFx event.
After attaching the signed copy of the Gate C paper,
Category specialist in the RFx document

Business Blueprint
2.7Contract Award and Handover Process

Business Blueprint
Contract Award & Handover Process Description
Process ID Process Step (L5) Related Business Solution RICEFW Solution Type (E- Actor
Requirement Enhancement, S-Standard,
M-Manual)
2.7.1 Accept / Reject bids, NA Once gate C is approved, Category specialist will accept Yes R4-CH-E-01 Category Specialist
trigger award / or reject the bids. This will trigger email notifications to R4-CH-E-02
rejection letters the contact person of the suppliers.
2.7.2 Move Project phase NA Once acceptance and rejections of the bids is completed, Yes R4-CH-W-01 Category Specialist
to ‘Contract Award the user will move the phase of the Project to ‘Contract R4-CH-E-03
Award’ from ‘Contract Award Preparation’. This will
trigger a workflow which effectively is auto-approval but
it will wait until 15 days from the phase change to affect
the approval. Once approved, system will send
notifications to all collaborators
2.7.3 Receive notification NA Upon acceptance or rejection of the bid by the category NA NA Category Specialist
and submit the query specialist, respective suppliers will receive notification. If
if required. required, they can raise queries.
2.7.4 Response to supplier Supplier queries Upon receiving query from supplier, a notification will be NA NA Category Specialist
queries needs to be sent out to the owner of the RFx document (generally
responded to by the Category Specialist). Upon receiving the notification, the
Sourcing team Category Specialist will co-ordinate with Sourcing team
members and respond to the query through the Sourcing
application.
2.7.5 Create Master NA Category Specialist will create a follow-on document – Yes NA Category Specialist
Agreement Master Agreement (MA) – with reference to the RFx
document.
User will select the appropriate document type when
creating the MA.
The response information, will be copied from RFx to

MA automatically and the collaborators will added
manually in the MA.
2.7.6 Upload Contract NA After populating the mandatory, information of the MA, Yes NA Category Specialist

Business Blueprint
M-Manual)
document Category Specialist will link the Contract document to
the MA.
This contract document will be accessible to the supplier
through portal.
Upon saving the MA a notification will be sent to the

relevant supplier contact.
2.7.7 Receive and sign the Ability to sign the Upon receipt of the notification, supplier contact will NA NA Supplier
contract and send it contract by the login to the portal following URL in the notification.
back to UK Power supplier and submit it The user will then download, sign, and upload the signed
Network back to UK Power contract back to the MA available through the portal.
Networks
2.7.8 Receive signed Ability to store the Category specialist will be receiving a system notification NA NA Category Specialist
contract, counter contract document on receipt of the signed contract from the supplier.
sign and update and relevant
contract repository metadata securely Category specialist will then counter sign the document
and upload with the same with the status ‘final’ contract
document.
Contract document when linked to MA will become a

part of contract repository. The repository will enable
search, filter of contract documents.
2.7.9 Implement Application to enable Category Specialist will compile the contract document Yes R4-CH-C-01 Category Specialist
mobilisation plan schedule and and update the MA schedule tab to reflect the agreed
monitoring of the plans.
various plans agreed These schedules can be downloaded from the repository
during the tendering available in sourcing.
process. E.g.

Business Blueprint
M-Manual)
mobilisation,
communication plan
2.7.10 Receive handover Ability to collaborate Once attached the documents will be automatically be NA NA Commercial Manager
documentation and information with the available to collaborators including the Commercial
Plan from category supplier electronically Managers.
specialist
2.7.11 Educate the business Collaborate, educate, Business users will generally be part of the sourcing NA NA Category Specialist
users with contract drive awareness to team. They will have to the Master Agreement
details and transfer the wider business document in SAP Sourcing as collaborators.
the knowledge user group once the Category Specialist and other relevant sourcing team
contract is in place members will transfer knowledge to these business
and available to be users.
used to execute
work.
2.7.12 Confirmation of exit Enable exit planning, Master agreement schedule will include necessary NA NA Commercial Manager
plan for the existing if relevant details about the exits plan of the contract.
contract Relevant responsible users will be notified when a
specific task from the schedule is due.
For exit plan, detailed activities will be maintained in the
MA schedule tab.
2.7.13 Schedule supplier Ability facilitate The MA schedule will be updated with recurring NA NA Category Specialist
review meeting supplier meetings at meetings as tasks. These tasks will be assigned to both
regular period to UKPN and Supplier users.
monitor the contract An advance notification will be generated by the
performance application to inform the relevant parties about their
planned meetings.
2.7.14 Publish Master Ability to kick off the After updating MA with necessary documentation and Yes R4-CH-E-04 Category Specialist
Agreement to ERP contract and the schedule of activities, Category Specialist will change R4-CH-W-01
and Change Project execute the work the phase of the MA as ‘Send Contract to ERP’
Phase to ‘Contract with reference to
Execution’ negotiated contract This phase change will validate if the ‘integration’
relevant information is updated by the user for the MA.

Business Blueprint
M-Manual)
Once validated by the system, user will publish the
contract from Sourcing; this will transfer the contract
from Sourcing to SRM application.

Business Blueprint
3 Technical/Development Related Items (RICEFW)
3.1 Reporting (operational and analytical)
<< Include references to Reports specified in the Reporting Catalogue>>
SAP Sourcing Standard Reporting:
Report Title Purpose Transaction Code

RFx Cycle Time Summary by Product Category Measures the average cycle time to award acceptance
RFx Cycle Time Summary by External Category Measures the average cycle time to award acceptance
RFx with Insufficient Bidders
Identifies all current and prior RFx events with fewer than 5 qualified suppliers.
Quarterly Summary of Value Utilizes a bar graph format to summarize the total Estimated Value of each
business document type, across business units and companies.
RFx Summary Extract Provides access to the summary information for a set of RFxs in a given time period
for printing or exporting.
RFx Summary Status Summarizes, for each business unit and category, the number of RFXs in each
Phase (Created, Open, Closed, Awarded, New Round).
RFx Proposal Award Reasons Summary Provides visibility into the reason why RFx proposals were awarded, for proposals
awarded in a specified time period. A pie chart displays the breakdown of award
reasons, and a list of each award with the associated reason is provided. In
addition it also provides the option to search for proposals awarded during a
specified time period. Search results can be narrowed further by product category.
Top Category Awards by Period
Graphically displays the total awarded to each market category
Top Supplier Awards by Period
Graphically displays the total value of awards by supplier per quarter
RFx Award Summary by Supplier Status
Graphically displays the total value of awards for each supplier type
Grand Total The total value of the awards combined.

Business Blueprint
Auction Summary Extract
Provides access to the summary information and auction type attributes for a set
of auction events in a given time period for printing or exporting
Auctions and RFxs Completed by Month
Shows the number and total value of auctions and RFxs completed by month for a
selected time period and product category
Total Auctions and RFxs Completed Report Total number of auctions that closed in this month. Choose the number to view a
list of the auctions.
RFxs Completed by Month Name of RFx. Choose the title to view the RFx document.
Auctions Completed by Month Name of RFx. Choose the title to view the RFx document.
Auctions with Insufficient Bidders
Identifies all current and prior auction events with fewer than 5 qualified suppliers.
Project Summary Extract Provides access to the summary information for a set of projects in a given time
period for printing or exporting.
Master Agreements with Overdue Audits Summary Summary of master agreements with audits overdue.
Master Agreements with Performance Metrics Due
Summary of master agreements with performance metrics due.
Master Agreements with Low Performance: Summary of master agreements with performance metric targets that were not
Summary met.
Upcoming and Expired Master Agreements and
Agreements
This report is a list of master agreements and agreements that will expire soon, or
which has expired within a configurable number of days.
Search All Automatic Renewal Master Agreements List of master agreements that are flagged as Auto Renewal on the Master
Agreements Header page.
Agreement Item Pricing by Organization and Plant
Lists all materials that were previously under contract but have expired, and
groups the output by organization and then by plant
Agreement Item Pricing by Supplier and Plant
Provides detailed information for all agreements that contain the material
Item Spend Versus Award
Lists all materials under contract and compares the expected spend per item from

Business Blueprint
the contract terms to the actual spend and calculates a percent of agreement
consumed. The list is grouped by buying organizational unit and plant.
Material Analysis Provides the capability to search for a particular material across all RFxs and view
the associated details, such as delivery terms and price. All information for the
material can then be seen in a consolidated view. In addition it provides the option
to search for materials by description and plant name or by name, number, or
description. The asterisk wildcard may be used to indicate "all" records.
Unawarded Items with Volumes provides visibility into the total number of items that are not yet awarded.
Associated volumes are included for each contract to show the size of outstanding
items. Also provides the option to search for items under contract between 2 dates
not under agreement on a particular date. Unawarded items meeting the search
criteria are then displayed.
Agreement Savings Impact for Owner Summary of master agreement and agreement savings associated with a given
agreement owner.
Master Agreements in My Cost Centres List of master agreements associated with the cost centres defined in your user
account setup.
Agreements in My Cost Centres List of agreements associated with the cost centres defined in your user account
setups
Cost Centre Master Agreements: Cancelled or
Closed
List of master agreements that are associated with the cost centres defined in your
user account setup and which have been cancelled or closed.
Cost Centre Agreements: Cancelled or Closed
List of agreements that are associated with the cost centres defined in your user
account setup and which have been cancelled or closed
Master Agreement Advanced Search
List of all master agreements with one or more key attributes (or with sub
agreement attributes) containing a user-entered text string
Agreements Payment Terms Analysis This report provides a list of master agreements and sub agreements for the
payment terms you enter.

Business Blueprint
Contract Performance Dashboard
The Contract Performance Dashboard allows you to quickly search agreements and

expiring agreements according to various criteria, and immediately drill down into
their details.
Expiring Agreements
This report provides a list of expiring agreements for which you are the owner
between a start date and end date that you enter.
Item Standard Cost Savings Projections Lists all materials under contract and determines the amount of savings expected
by comparing the material's standard cost to the contracted material price. The list
is grouped and totalled by buying organizational unit then plant.
Item Standard Cost Savings Projections by Supplier Lists all materials under contract and determines the amount of savings expected
by comparing the material's standard cost to the contracted material price. The list
is grouped and totalled by supplier and then by plant
*Following is the list of reports extracted during process detailing. However the list may be extended based upon the inputs from business on additional reports.
3.2 Interfaces
Identify all interfaces required to provide inputs to or outputs from this part of the process. Provide a functional description of the interfaces including the source and type
of data.
RICEF-ID Description Report Type (ABAP, Data Elements Relevant KPI

(LINK TO FS End of BI, BOBJ)
Sep)
R4_PQ_I_01 Interface with Achilles Not Applicable Not Applicable Not Applicable
3.3 Data Conversion / Historical Data

RICEF-ID Conversion Object Source Conversion Conversion Method # of Objects to be
Activities (e.g. (manual / converted Responsible
cleansing) automated)
R4-CS-C-01 Upload of Category CSV Manual
Strategy Templates in SAP

Business Blueprint
RICEF-ID Conversion Object Source Conversion Conversion Method # of Objects to be
Activities (e.g. (manual / converted Responsible
cleansing) automated)
Sourcing system.
R4-CS-C-02 Import Category Strategy CSV Manual

Schedule tasks.
R4-SCS-C-01 Upload of Sub Category CSV Manual
Strategy Templates in SAP
Sourcing system.
R4_PQ_C_01 Import Questionnaire CSV Manual

libraries for Prequalification
R4_NG_C_01 Import Questionnaire CSV Manual
library in SAP Sourcing for
Negotiation document
R4_RF_C_01 Import Questionnaire CSV Manual
library in SAP Sourcing
R4_RF_C_02 Importing the schedule CSV Manual
Library and clause library
R4-CH-C-01 Importing the MA schedule CSV Manual
Library and clause library
3.3.1 Data Cleansing Requirements

Section Contents: Cleansing requirements to be captured to enable clean data migration from legacy(source) systems to target system. These requirements will help in
eliminating data inaccuracies, inconsistencies, redundancies etc. The below requirements will feed into the Data Cleansing Register (DCR).
These will be elaborated by data conversion team during design phase
Data Source name Who will perform Data Cleansing Requirements Which Data load Type of Data:
(where cleansing to be performed) the Data Cleansing Requirements provided by object it’s linked to a. Master Data
(UKPN Business if (name of UKPN b. Transactional Data
it’s a UKPN data Business Data c. Historical Data
source) Champion) d. Data related to Regulatory
Reporting requirements

Business Blueprint
e. Anything else
3.3.2 Data Load Requirements

3.3.2.1 Data load requirements: Legacy systems to Target system
Section Contents: This section should contain the data load requirements to from legacy systems(existing data) to support the To Be processes in the target system. This
section should feed into Data Migration Register.
Data Type of Data: Which TO Data Source name Data Extraction Target SAP area (if applicable) Respective
Load a. Master Data BE (e.g. Criteria from the System (e.g. BackOffice: Business Data
Object b. Transactional Data Process P6/Netmap/Enmac) source system (e.g. SAP Finance/Logistics/Procurement/HR; Champion
name c. Historical Data it’ll ECC6/ PPM) CRM, PPM, PS, PM etc)
d. Data related to support
Regulatory
Reporting
requirements
e. Anything else
3.3.2.2 Data load requirements: New Data requirements

Section Contents: This section should contain the new data items that need to be loaded in the target system which doesn’t exist in the current systems. This section
should feed into Data Migration Register. New data should be collected in the Data Collection Workbook(DCW) template by the Data Migration team.
Data Type of Data: Which TO Data Source name Target SAP area (if applicable)
Load a. Master Data BE Process (DCW only) System (e.g. BackOffice: Finance/Logistics/Procurement/HR;
Object b. Transactional Data it’ll (e.g. SAP CRM, PPM, PS, PM etc)
name c. Historical Data support ECC6/ PPM)
d. Data related to
Regulatory Reporting
requirements
e. Anything else

Business Blueprint
3.3.2.3 Data load requirements: Grey IT data migration requirements
Section Contents: This section should capture all the unstructured data in use by business (held in data sources like Excel, MS Access DB etc.) that is needed to run the To
Be processes in the new systems. This section should feed into Data Migration Register based on source to target attribute level mapping.
Grey IT Grey IT Current Which TO Target Data Load Object Target SAP area (if applicable)
File Id File Owner of BE Process name System (e.g. BackOffice: Finance/Logistics/Procurement/HR;
name the Grey IT it’ll support (for which this migration (e.g. SAP CRM, PPM, PS, PM etc)
File to be considered) ECC6/ PPM)
3.4 Enhancements
Enhancements
RICEF-ID Description Data Object Functional Gap Alternative SAP Reason

Standard
R4-CS-E-01 Field level validations in Category Yes No
Category Strategy Business Strategy -
document. Projects
R4-CS-E-02 Modifying the content of e-mail Yes No
notification, sent to the
Collaborators of the Category
Strategy document. Category
Strategy -
Projects
R4-CS-E-03 Modifying the content of e-mail Category Yes No
notification, sent to the Strategy -
Collaborators of the Category Projects
Strategy Document.
R4-CS-E-04 Enhancement to send Category Yes No

notification to Category Strategy -
Specialist once all the Projects

Business Blueprint
Enhancements

Standard
stakeholders complete their
tasks.
R4-CS-E-05 Enhancement to send email Category Yes

Notification and modifying the Strategy -
email content. Email to the EMT Projects
on completion of the 1st level
approval by HOP.
R4-SCS-E-01 Field level validations in Sub Sub Category Yes
Category Strategy Business Strategy -
document. Projects
R4-SCS-E-02 Modifying the content of e-mail Sub Category Yes
notification, sent to the Strategy -
Collaborators (Category Projects
Manager and SMT) of the Sub
Category Strategy document.
R4-SCS-E-03 Enhancement to send email Sub Category Yes No

Notification and modifying the Strategy -
email content. Email to the SMT Projects
on completion of the 1st level
approval by Category Manager.
R4-CA-E-01 Field level validations in Contracting Yes No
Contract Approach Business Approach -
document. Projects
R4_PQ_E_01 Field level validations in Prequalification Yes No
Prequalification Business
document
R4_RF_E_01 Field level validations in RFP-Rfx Yes No
Prequalification Business

Business Blueprint
Enhancements

Standard
document for preparing the
questions
R4_RF_E_02 Preparing questionnaire fields RFP-Rfx Yes No
R4_RF_E_03 Enhancement to send RFP-Rfx Yes No
notifications to the Business
Collaborators and the Sourcing
team
R4_NG_E_01 Field level validations in Yes No
Prequalification Business Negotiation- Rfx
document for preparing the
Gate C
R4_NG_E_02 Enhancement to send Negotiation- Rfx Yes No
notifications to the bidders
Modifying the content of e-mail Contract Award Yes No
notification, sent to the & Handover
Supplier contact person after an
R4-CH-E-01 RFx response
RFx response 'Award' phase Contract Award Yes No
validation with the Gate C & Handover
R4-CH-E-02 Approval
R4-CH-E-03 Stand still validation for follow- Contract Award Yes No
on document creation (MA) & Handover
R4-CH-E-04 Integration Validation in Master Contract Award
Agreement. To complete the & Handover
field level changes for SRM
3.5 Forms

Business Blueprint
RICEFW-ID Description Data Object Output Type (Form, EDI, etc.) Frequency Volumes Owner
A custom page named

– Gate A- will be
available on the Project
document.
After completion of the
various analysis
undertaken by the
Sourcing team, the
category specialist will
update the summary of
the analysis in ‘Gate A’
R4_CA_F_01
tab.
Once completed,
change phase will
validate if the ‘Gate A’
tab page information is
updated when
changing the phase
R4_PQ_F_01 A custom page named

– Gate B- will be
document.
various analysis
undertaken by the
Sourcing team, the
the analysis in ‘Gate B’
tab.
Once completed,

Business Blueprint
RICEFW-ID Description Data Object Output Type (Form, EDI, etc.) Frequency Volumes Owner
change phase of the

RFx document
will validate if the
‘Gate B’ tab page
information is updated
when changing the
phase
A custom page named

– Gate C- will be
document.
various analysis
undertaken by the
Sourcing team, the
the analysis in ‘Gate A’
R4_NG_F_01
tab.
Once completed,
change phase of the
RFx document to
‘Sponsor Approval’.
Application will
validate if the ‘Gate A’
tab page information is
updated when
changing the phase
3.6Workflow
Identify workflow requirements for this process. Provide detailed requirements for the workflow. e.g., purchase order approval process and authority levels etc.
RICEFW-ID Description Data Object Engaged Parties Owner
R4-CS-W-01 Two step approval by Head of Procurement and EMT -Review and Approve Category Strategy - Head of Procurement, Category

Business Blueprint
RICEFW-ID Description Data Object Engaged Parties Owner
the Category strategy document. Projects EMT Manager
R4-SCS-W-01 Two step approval by Category Manager and SMT -Review and Approve Sub Category Category Manager, Category
the Sub Category Strategy document. Strategy - Projects SMT specialist
R4-CA-W-01 Approval Workflow by the Sponsors on changing the phase to “Sponsor Approval”. Contracting Sponsor Category
Approach - specialist
Projects
R4-CA-W-02 Approval Workflow by the Category manager. Contracting Category Manager Category
Approach - specialist
Projects
R4_PQ_W_01 Workflow approval required to Approve/Reject for completion of Gate ‘B’ in Pre- Prequalification - All Directorates Sourcing
qualification process. RFx SMT Team
R4_NG_W_01 Approval workflow required for Gate ‘C’ paper in Negotiation process. Negotiation - RFx CGM Category
specialist
R4-CH-W-01 Contract award workflow Contract Handover Category
specialist
4 Authorisation
Section Contents: This section should contain all the system roles and the number of employees who will be given the access per role.
The SAP authorisation concept protects transactions, programs, and services in SAP systems from unauthorised access. On the basis of the authorisation concept, the
administrator assigns authorisations to the users that determine which actions a user can execute in the SAP System, after user has logged on to the system and been
authenticated.
Sr. No. Authorisation Job Role Data Objects / T-Code # of employees

Business Blueprint
5. Organisational Change Related Items (to be filled by business)
5.1 End User Training Considerations

Section contents: All the functionalities mapped to the organisational roles that will carry out that activity. This should help in creating the training needs analysis.
Requirement Roles Affected Estimated Numbers Requiring Training
5.2Change Impact Summary

Section contents: The section does not add any value to training team in the given format. It is recommended to modify the section that is fit for purpose as per the
needs of the engagement team
Organizational Change Impact
Process ID Change Impact Old Way New Way Positive Impacts Negative Impacts
Summary To Company To Company
To individual roles To individual roles
1) 1)

Business Blueprint
6 Assumptions

Business Blueprint
A Decision References/ Cross References

Related/Referenced Documents
Document Name Requirement Number

Technical Solution Blueprint R4 Strategic Sourcing V0 8 Final Updated V2.4

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Technical Solution Blueprint R4 Strategic Sourcing V0 8 Final Updated V2.4

Uploaded by

Copyright:

Available Formats

Business Blueprint

0.1 22.05.2015 Initial draft

0.2 29.05.2015 Draft – updates to ‘Introduction’ section and to ‘Process

R4_Strategic Sourcing_PDD_V0.9 Page

R4_Strategic Sourcing_PDD_V0.9 Page

UK Power Networks Enterprise Process Model

R4_Strategic Sourcing_PDD_V0.9 Page

1.1 High Level Business Process Overview

Is it What is Route to market Lead

No £2,000 1. Corporate Card Directorate

£50,000 2. Low value Purchase Order Directorate

£50,000 3. Three bids (evidenced) Directorate

£250,000 4. Tender Procurement

£345,000 5. Tender compliant with Procurement

Yes Any 6. Tender (compliant with Procurement

The primary objectives of strategic sourcing are:

The Strategic Sourcing process involves the following sub-process:

R4_Strategic Sourcing_PDD_V0.9 Page

UKPN’s second level process comprises the following components.

L2: Strategic Sourcing

Annual Business Strategy and

Process Step Description

R4_Strategic Sourcing_PDD_V0.9 Page

Process Step Description

Key Steps of process

Developing a category approach aims to identify potential sourcing options through an

Key steps of the process

 Sourcing team is created.

 Review of various impact assessments.

R4_Strategic Sourcing_PDD_V0.9 Page

Process Step Description

Focuses on pre-qualifying suppliers in Achilles UVDB and development of RFP.

The supplier submits an AQ response for assessment and deselection purposes.

Key Steps of process

Key Steps of process

R4_Strategic Sourcing_PDD_V0.9 Page

2.1 Organisation Structure Considerations

1000 UK PN (Operations) Ltd

Company codes relevant for Procurement are as below:

1000–UK PN (Operations) Ltd

Existing Purchasing Organisation:PO01-Procurement Org

There is a single Purchasing Organisation in the system.

Current Procurement Enterprise Structure:

R4_Strategic Sourcing_PDD_V0.9 Page

R4_Strategic Sourcing_PDD_V0.9 Page

-Purchasing Org: Network Operations

R4_Strategic Sourcing_PDD_V0.9 Page

R4_Strategic Sourcing_PDD_V0.9 Page

R4_Strategic Sourcing_PDD_V0.9 Page

Organisational Structure Setup Strategic Sourcing:

2.2Master Data Considerations (including all relevant data relationships)

Master Data Description

R4_Strategic Sourcing_PDD_V0.9 Page

Significance of Material Group:

-Material Group forms a Product/Service hierarchy

-Material Group (Product Category) is responsibility of Purchasing Group

-Links to Account Assignment Category

-Links to G/L Account

R4_Strategic Sourcing_PDD_V0.9 Page

Background of UKPN Material Groups:

• Number of Material Groups available for user to select currently - 324

Recommended Classification Standard: UNSPSC Classification with mapping table to Achilles

UNSPSC: United Nations Standard Products and Services Code