Page Comparison

USE CASE STEP

USE CASE: Unconditional Social Cash Transfer

STEP: Outreach Communication

PRECONDITIONS

(list of conditions that MUST be met in order to be able to successfully execute this process)

The USCT program has been set up, and its objectives and eligibility criteria have been defined.
The Ministry of Social Welfare or another leading agency/organization is responsible for organizing the information campaign.
Communication Digital campaign communication channels (e.g., mobile messaging, emails, village-to-village campaigns) have been established and are available under Messaging BB.
All necessary building blocks and workflows have been set up.

DATA INPUTS

Note: Details on Data Inputs will most likely depend on Building Blocks that are not yet available. For now high level inputs are listed.

Program details (objectives, benefits, constraints, partners, etc.)

Target beneficiary group(s)

Communication channels (mobile messaging, radio/television, etc.)

Content for educational and promotional purposes

Locations of households and individuals for outreach targets

Scheduler Event

Name
Description
Category
Host Entity ID
From
To
Deadline
Subscriber Limit
Terms
Status
Venue

Scheduler Resource

Name
Category
Phone
Email
Alert URL
Alert Preference

Scheduler Entity

category
name
phone
email
website

Scheduler Message

Entity Identifier
Category
Message content

Workflow Process

Name
Type
Version
Description
Process Body
- code
- value

Beneficiary

First Name
Second Name
DOB
National ID Number
Place of residence
Contact info:
- Email
- Phone Number
- Address
Eligibility criteria [Data required for making decisions on enrollment, e.g. with using Proxy Means Test, can vary between countries]
- number of children
- marital status
- type of settlement [town, village, etc.]
- employment status

ACTORS

Human

Leading Organization (Ministry of Social Welfare or other entity)
District / local social welfare officers
Target beneficiary group(s)

System

Messaging BB
Scheduling BB
Consent BB
Identity BB
Registration BB
Mobility management BB (not yet developed) (outside of BB use case document)
Shared Data Repositories BB (not yet developed)
Terminology BB (not yet developed)
Collaboration Management BB (not yet developed) (outside of BB use case document)
Content Management BB (not yet developed) (outside of BB use case document)
eLearning BB (not yet developed) (outside of BB use case document)

NORMAL COURSE

Step 1: Prepare outreach campaign content

Step 1.1 Social Welfare worker is authenticated.

Step 1.2 Social Welfare worker creates campaign content

Code Block

Feature: Prepare Content
Scenario: Leading organization staff creates awareness content using Content Management BB
  Given Social Welfare workers is authenticated and have access to Content Management BB
  And all requirements regarding campain content are established (also stored in shared data repositories?)
  When staff create or update content for outreach and communication
     And created content is complant with content requirements 
  Then the content is stored in the Shared Data Repositories BB
    And the content is available for editing in Content Management BB

Example Content Management BB endpoints (api spec not yet created):

/content/create
- Save content assuming that content management is also used as storage.
  In other case Shared Data Repositories would be use to store content)
/content/update
- Save content assuming that content management is also used as storage.
  In other case Shared Data Repositories would be use to store content)
/content/get/{content}
- Access to specific set of requirements

Example Shared Data Repositories BB (api spec not yet created):

/repositories/data/create
/repositories/data/update

Step 2: Setup outreach schedule for potential beneficiaries

Step 2.1: Create scheduler flow

NORMAL COURSE

Step 1: Setup outreach schedule for potential beneficiaries

Note: For now we assume that content of the scheduled massage is hard-coded. At the moment definition of Content Management BB is not determined, and therefore we’re sending message directly to the scheduler BB. This will be changed in next iterations (example use of using Content Management BB was presented added in previous version of this document under Prepare outreach campaign content step).

Step 1.1: Create scheduler

Code Block

Feature: Create scheduler event 
Scenario: Setup outreach event in the scheduler 
  Given timeline of outreach program was determined
    And Outreach channels were determined
    And Social Welfare worker can schedule events  
    And Social Welfare worker has prepared content of the outreach
  When Social Worker create new scheduler bb event 
    And Social Worker attaches event message
  Then new scheduler event is created
    And new scheduler message is created

Relevant Scheduler BB endpoints:

/event/new
- Add new event
/message/new
- Create content message event

Note: This assumes that only one event and message will be created. Should we assume that different outreach channels will require different events and messages?

Step 2 Beneficiary targeting Identify target group of potential beneficiaries

Step 2.1 Prepare targeting workflow

Code Block

Feature: Create schedulernew workflow event 
Scenario: Setup outreach event in the scheduler 
  Given timeline of outreach program was determined Create workflow that adds beneficiary Scheduler BB resources using Digital Registry BB data
  Given Social Worker can create workflows 
    And Outreach channels were determined Workflow is connected to the Digital Registry BB
    And SocialWorkflow Welfareis workerconnected canto schedulethe eventsScheduler BB
   When Social Worker createAnd newFunction/model schedulerto bbevaluate eventpotential beneficiaries is ready
  AndWhen Social Worker creates new attachesworkflow event
message   Then newThen schedulerNew eventworkflow is created 
    And new scheduler message is created Potential beneficiaries who meet the targeting criteria can be identified

Relevant Digital Registries BB endpoints:

/data/{registryname}/{versionnumber}
- Access the list of individuals for scoring.

Relevant Scheduler BB endpoints:

/event/new
- Add new event
/message/new
- Create content message event

Note: This assumes that only one event and message will be created. Should we assume that different outreach channels will require different events and messages?

Step 2.2 Identify target group of potential beneficiaries

list_details
- Get information regarding about what event beneficiaries will be appointed to

Relevant Workflow BB endpoints:

/processes (post)
- Create new workflow

Step 2.2 Execute targeting workflow

Code Block

Feature: Schedule notifications for target group

Scenario: PotentialList potential beneficiaries arefor outreach
 listed forGiven outreachthat   Givena scheduler event washas been created
      When Social Worker queries potential beneficiaries for being target groupAnd that a targeting workflow process exists
  When the Social Worker triggers the workflow process
    And the potential beneficiaries are meet the criteria
    And the potential beneficiaries have signed a consent agreement to be notified
   Then Then the potential beneficiaries should arebe added as resources in the scheduler BB
    And potentialthey should beneficiariesbe areassociated appointedwith tothe previously created event

Relevant Scheduler BB endpoints:

/resource/new
- Save beneficiary in scheduler BB
/appointment/new
- Bind potential beneficiary to the event

Relevant Digital Registries BB endpoints:

/data/{registryname}/{versionnumber}
- Query digital registry for target group

Relevant Consent BB endpoints:

/service/agreement/{agreementId}/
- Confirm that potential beneficiary has signed the agreement and can be notified about the program

Relevant Workflow BB endpoints:

/processes/{processId}/start
- Trigger appointment process

Step 2.3 Notify target group

Code Block

Feature: Send bulk notifications  
Scenario: Scheduled event is triggered and messages are sent to target group
  Given Target Group was registered in the scheduler BB
    And Scheduler can trigger bulk message in messaging BB
    And Scheduler Alert had been scheduled
  When Alert is triggered
  Then Target group receives notifications through messaging BB
    And Scheduler sets marks action as successfull

Relevant Scheduler BB endpoints:

/alert_schedule/new
- Used to setup trigger for notifying target group

Relevant Messaging BB endpoints:

/send/email/batch
- Notify target group. At the moment that’s only available batch endpoint, should be extended when other notification methods are added.

Info

Current steps don't cover handling Outreach Campaign monitoring or assessing the effectiveness of the outreach campaign. Should we include these as indispensable parts of the use case step, or include outreach monitoring and assessment in a separate step (8. Ongoing M&E)?

On the Figma chart, the Outreach Communication step is composed of three workflows:

Client Communication (covered)
Client Education (not covered, no BBs specified at the moment)
Content management (partially included in the existing step, no BB)

Should we include Client Education and Content Management in the scope of this use case step or focus on the Client Communication workflow?

ALTERNATIVE COURSE

TBA

DATA OUTPUT

POST-CONDITIONS (SUCCESS CRITERIA)

The target audience is aware of the USCT program and its objectives, benefits, constraints, timeline, etc.
Potential beneficiaries are encouraged to enroll in the USCT program and they know how to do this.
Relevant content has been created and managed for use in the information campaign.

EXCEPTIONS

Target audience doesn’t accept messages used to spread awareness
Consent policy to use data to inform about social program has not been created

RELATED BBs

Messaging BB
Scheduling BB
Consent BB
Identity BB
Registration BBContent Management BB (not yet developed) (outside of BB use case document)BB

SEQUENCE DIAGRAM

Expand

title	Mermaid UML Diagram

sequenceDiagram

participant SW as Social Welfare Worker

participant SBB as Scheduler BB

participant WBB as Workflow BB

participant DRBB as Digital Registries BB

participant CBB as Consent BB

participant MBB as Messaging BB

activate SW

SW->>SBB: Create scheduler event (/event/new)

activate SBB

SW->>SBB: Attach event message (/message/new)

SBB-->>SW: Confirm scheduler event and message created

deactivate SBB

SW->>WBB: Create workflow (/processes (post))

activate WBB

WBB-->>DRBB: Validate Digital Registry BB connection

WBB-->>SBB: Validate Scheduler BB connection

WBB->>SW: Confirm new workflow created

SW->>WBB: Trigger workflow process (/processes/{processId}/start)

deactivate SW

WBB->>DRBB: Access list of individuals for targeting (/data/{registryname}/{versionnumber})

loop For each potential beneficiary

WBB->>CBB: Check consent agreement (/service/agreement/{agreementId}/)

alt Has signed agreement

WBB->>SBB: Add beneficiary as resource (/resource/new)

WBB->>SBB: Associate beneficiary with event (/appointment/new)

end

WBB-->>SW: Inform about finished process

deactivate WBB

SW-->>SBB: Schedule alert for notifications (/alert_schedule/new)

activate SBB

SBB->>MBB: Trigger bulk message (/send/email/batch)

activate MBB

loop For each potential beneficiary

MBB->>Beneficiary: Send notifications

end

MBB->>SBB: Confirm notifications sent

deactivate MBB

SBB-->>SW: Confirm outreach communication executed

deactivate SBB

Image Added

Versions Compared

Old Version 3

New Version Current

Key

Step 1: Prepare outreach campaign content

Step 1.1 Social Welfare worker is authenticated.

Step 1.2 Social Welfare worker creates campaign content

Step 2: Setup outreach schedule for potential beneficiaries

Step 1: Setup outreach schedule for potential beneficiaries

Step 1.1: Create scheduler

Relevant Scheduler BB endpoints:

Step 2 Beneficiary targeting Identify target group of potential beneficiaries

Step 2.1 Prepare targeting workflow

Step 2.2 Execute targeting workflow

Relevant Scheduler BB endpoints:

Step 2.3 Notify target group