Versions Compared

Old Version 1

changes.mady.by.user Damian Borowiecki (Deactivated)

Saved on

compared with

New Version 2

changes.mady.by.user Damian Borowiecki (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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 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

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

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  
  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.2

:

Identify target group of potential beneficiaries

Code Block
Feature: Schedule notifications for target group 
Scenario: Potential beneficiaries are listed for outreach
  Given scheduler event was created 
  When Social Welfare worker has identified program criteria  
    And Social Welfare worker is authenticated in Digital Registries 
  When Social Worker queries potential beneficiaries for being target group
    And potential beneficiaries are meet the criteria
    And potential beneficiaries signed consent agreement to be notified
  Then potential beneficiaries are added as resources in scheduler BB
    And potential beneficiaries are appointed to 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

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 target group

…

    • 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

To be specified:

Current steps don’t cover handling Outreach Campaign monitoring or Assessing the effectiveness of the outreach campaign. Should we include it as indispensable
part of use case step or include outreach monitoring and assessment in separate step (8. Ongoing M&E)?

On Figma chart Outreach Communication step is composed of 3 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 scope of this use case step of put focus on the client communication workflow?

ALTERNATIVE COURSE 

TBA

DATA OUTPUT 

POST-CONDITIONS (SUCCESS CRITERIA)

  1. The target audience is aware of the USCT program and its objectives, benefits, constraints, timeline, etc.

  2. Potential beneficiaries are encouraged to enroll in the USCT program and they know how to do this.

  3. Relevant content has been created and managed for use in the information campaign.

EXCEPTIONS 

  1. Target audience doesn’t accept messages used to spread awareness

  2. 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 BBMobility 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)