Template for Logical Process Blueprint Document

Owned by Tarek Rashed
Last updated: Jan 17, 2023
1 min read

Overview

The objective for creating Logical Process Blueprint is to review the To-Be User Journeys for a service name and break them down into high-level non-technical logical processes. This helps identify gaps and overlaps across building blocks, standardize terminology across teams, Identify standardized workflows and help clarify the scope.

 

Please find linked here an example of a real-world example of a ‘To-Be’ User Journey for Extended Producer Responsibility Service in Rwanda.

Service Summary

 

ID

Service_ID

 

Name

Service name

 

Implementation Country

 

Sector

 

Version

 

Status

(Draft/In review/Finalised)

 

 

Provide a clear description (no longer than 750 words) of

  1. Objectives for creating this Logical Process Blueprint.

  2. The service, in the context of the country of implementation (This should include a high-level description of what the service should accomplish, limitations, assumptions, and more)

Steps within the service name

Populate the following table for each of the steps within the Service

 

Step ID

Service_ID-Unique_Step_Number

 

Name of Step

Name of the step as mentioned in the ‘To-Be’ User Journey (if applicable)

 

Trigger

(the event that triggers the use case)

 

Assumptions

 

Preconditions

(list of conditions that MUST be met for the use case to be successful)

 

Actors & touchpoints

(List all persons, companies or organizations, computer programs or systems - hardware, software, or both)

 

Data inputs

 

Building Blocks

 

Normal Course (what happens if the step is triggered and the preconditions have been met.  You can include any relevant BBs, BB Endpoints and Scenarios)

 

Relevant Workflows

(Name the workflows and their use in the step.)

 

Annex

List of relevant resources and relevant notes. This list should include (but not limited to) the following:

 

Resource

Link

Notes

Results from Context on existing Digital Service Design Standards and Delivery Protocol (Request for Information, RFI-1)

 

 

results from Service Catalogue (Request for Information, RFI-2)

 

 

‘To-Be’ User Journey

 

 

Results from Current digital capability in the country (Request for Information, RFI-4)