DIGIT Docs
Microplanning 0.2
  • DIGIT Knowledge Base
  • Local Governance
Microplanning 0.2
  • Introducing Microplanning
    • Release Notes
      • v0.2 Release Notes
        • Release Checklist
        • Technical Release Summary
        • Master Data Management Service (MDMS) and Configuration updates
        • Service Builds
        • UI/UX Audit
  • PRODUCT SPECIFICATION
    • User Manual
    • Product Requirement Document
      • SOPs
        • Guidelines
  • TECHNOLOGY
    • Architecture
      • High Level Design
      • Low Level Design
        • Plan Management
        • Census Management
        • Microplanning UI
          • System Admin Flow
          • Population Data Approval
          • Facility Catchment Mapping
          • Microplan Estimation Approval
      • Services
        • HCM Microplan Web
          • User Interface Design
          • Set Up Microplan
            • Microplan Details
            • Boundary Selection
            • Data Management
            • Data for Assumptions and Formulae
            • Microplan Assumptions
            • Formula Configuration
            • User Tagging
            • Summary Screen
          • User Management
            • Bulk User Create
            • Download Users Credentials
          • Supervisor Flows
            • User Interface Design
            • My Microplan
            • Select Activity
            • Validate And Approve Population Data
              • Village Details
            • Assign Facility To Villages
              • Village Assignment And Unassignment to Facility
            • Validate And Approve Microplan Estimation
          • Open Microplans: System Admin
            • Draft Flow
    • Specification
      • Plan Service
      • Resource Generator Service
      • Census Service
  • SETUP
    • Installation
    • Configuration
      • Advanced Configurations
    • QA Test Cases
    • Performance Testing
Powered by GitBook

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

On this page
  • System Administrator Flow
  • Steps
  • Web Sequence Diagrams

Was this helpful?

Export as PDF
  1. TECHNOLOGY
  2. Architecture
  3. Low Level Design
  4. Microplanning UI

System Admin Flow

Create/Update Microplan

System Administrator Flow

The System Administrator is responsible for setting up the entire microplanning platform, which includes defining campaign boundaries, configuring facilities, and assigning roles. This user operates at the national or country level and ensures all configurations align with campaign objectives.

Steps

  1. Capture Campaign Details:

    • Actor: System Administrator/Program Manager

    • Objective: Configure campaign information.

    • Process:

      • Select Disease: Choose the disease for the campaign (e.g., malaria).

      • Campaign Type: Select from options like Bednets or SMC (Seasonal Malaria Chemoprevention).

      • Resource Distribution Strategy: Choose between Fixed post, House-to-House, or a combination of both.

      • Next/Back: Proceed to the next screen or return to the previous step.

    • Validation:

      • All fields are mandatory before proceeding.

  2. Naming the Microplan:

    • Actor: System Administrator/Program Manager

    • Objective: Assign a unique name to the microplan.

    • Process:

      • Auto-Suggested Name: The system provides a default name based on the format: Country-Disease-CampaignType-MonthLast2DigitsOfYear.

      • User Input: Option to modify the name while following a strict naming convention.

    • Validation:

      • The name must be unique and follow specific guidelines (e.g., minimum 3 characters, no special characters except _() ).

  3. Select Campaign Boundaries:

    • Actor: System Administrator/Program Manager

    • Objective: Choose the geographic administrative boundaries (country, province, district, village, etc.).

    • Process:

      • Multi-Select Dropdowns: Select from a multi-select list of administrative divisions.

      • Validation: All fields are mandatory.

  4. Upload Population Data:

    • Actor: System Administrator/Program Manager

    • Objective: Upload population data required for resource estimation.

    • Process:

      • Download Template: Download a pre-configured Excel template.

      • Input Data: Enter total and target population, village coordinates, etc.

      • Upload: After filling in the template, upload it back to the system.

    • Validation:

      • Ensure data integrity (e.g., total population must be greater than zero, population data must be whole numbers).

  5. Upload Facility Data:

    • Actor: System Administrator/Program Manager

    • Objective: Set up facilities to be used during the campaign.

    • Process:

      • Download Facility Template: Fill out the downloaded template with facility details (e.g., facility type, capacity, geographic coordinates).

      • Upload and Validate: Once filled, upload the template.

    • Validation:

      • Mandatory fields such as facility name, type, and capacity must be filled in.

  6. Manage Microplan Assumptions:

    • Actor: System Administrator/Program Manager

    • Objective: Configure assumptions for calculating required resources.

    • Process:

      • Set parameters like population density and distribution strategy.

    • Validation:

      • Input values must be numerical.

  7. Access Control and Role Configuration:

    • Actor: System Administrator

    • Objective: Define and assign roles and permissions (e.g., Data Collectors, Microplan Approvers).

    • Process:

      • Configure roles and assign them to specific users.

      • Define user boundaries and access hierarchies.

Web Sequence Diagrams

PreviousMicroplanning UINextPopulation Data Approval

Was this helpful?

System Admin Flow
Employee Tagging Flow