DIGIT Workbench
PlatformDomainsAcademyDesign SystemFeedback
  • 👋Introducing DIGIT Workbench
    • Release Notes
      • Service Build Updates
      • MDMS & Configuration Updates
      • Test cases
      • Schema Collection
  • Understanding Workbench
    • Workbench Concept Note
    • Approach
  • Specifications
    • Master Data Management Process Flow
    • User Stories
  • Platform
    • Architecture
      • High Level Design
      • Low Level Design
    • Source Code
  • Setup
    • Configurations
      • Services
        • MDMS V2 (Master Data Management Service)
          • Adopt New MDMS - Steps
      • Workbench UI
        • Configurations
          • MDMS Configurations
          • DevOps Configuration
          • FAQ :: On Localisation Screens
        • Manage Master Data
          • Search Master Data
          • Add Master Data
          • View Master Data
          • Update Master Data
        • Manage Localisation Data
          • Search Localisation Data
            • Add Localisation Data
          • Edit Localization Messages
          • FAQ :: Add localisation if screens are not localised.
        • Create New Master
      • MDMS V2 Migration Guide
  • Community
    • Issues
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
  • Background
  • Implementation Process Overview
  • Problems
  • Objective
  • Solution
  • Key Components / Abilities
  • Pre-requisites
  • Maturity Model

Was this helpful?

Export as PDF
  1. Understanding Workbench

Workbench Concept Note

PreviousSchema CollectionNextApproach

Last updated 7 months ago

Was this helpful?

Background

Implementing products built on the DIGIT platform requires engineering capacity to set up the system and configure master data before going live. The increasing demand for implementations of DIGIT applications triggered the need for low-cost and high-velocity solutions to manage these implementations.

Implementation Process Overview

Implementation refers to the process of deploying applications built on the DIGIT platform in a new business context or geographical location. The deployment steps include system setup, master data configuration and customisation. The implementation process ensures the application workflows are tailored fit to meet the requirements of the local or regional policies for smooth functioning.

Examples of DIGIT implementations -

Problems

The current implementation process for DIGIT applications faces two primary challenges.

  1. Skilled personnel - The implementation requires experienced engineers who are familiar with the DIGIT platform. This proves both expensive while limiting the number of implementations that can be handled at a time.

  2. Cost and time constraints - Since the number of experienced engineers is limited, it poses limitations on the number of implementations that can be handled simultaneously. The result is longer timeframes for going live and increased costs.

Objective

Enable a non-tech/low-tech user to set up one or more DIGIT applications on a fully managed cloud infra with the ability to customise the application, features and registries to their context, all through an intuitive UI without writing a single line of code.

Solution

The Workbench solution is designed to meet the rising demand for low-cost, rapid implementations of DIGIT products. It simplifies the setup process by enabling senior engineers familiar with DIGIT to manage and configure master data through a user-friendly interface easily. The Workbench addresses the requirements of high demand for implementations in regions with limited DIGIT expertise and tight go-live timelines. The goal is to streamline the process and allow quicker, code-free deployments.

The Workbench user interface enables users to set up a new account with DIGIT services. It provides system users with a dynamically generated UI to perform key implementation tasks that typically require software code to be written by engineers.

End-state flow:

Key Components / Abilities

  1. Generate forms (UI) based on schema and push data entered in the forms to corresponding API endpoints

  2. Open to access for all services

  3. UI to add/remove fields from the registries

  4. UI to update forms

  5. Spin up a DIGIT service from a web portal

Pre-requisites

  1. Standardized JSONSchema for services

  2. UI-Schema Library

  3. UI-templates for forms

  4. Codified rules for updating registry structure

  5. UI to initiate “primary-tenant”

  6. Deploy selected services

  7. UI to trigger the installer

  8. Master-tenant creation and management

  9. Delineation of tenants

Maturity Model

The table below outlines the distinctive phase of development of the Workbench solution.

Version
Phase 1
Phase 2
Phase 3

UI to manage master data and system data

UI to customize forms (limited)

UI based installation and setup

v1

Senior engineer - eGov Solution Engineering Team

Add and manage master and system data for HCM

Feasibility & Effort - TBD

v2

HCM Solutioning Team

v1 + create new tenants for HCM ; customize UI for each master data with UI schema

v3

Trained non-egov BA

Modify application* - add/remove fields to forms

Bednet campaign on the Health Campaign Management platform in Mozambique
Malaria vaccine on the Health Campaign Management platform in Liberia
FSM on Sanitation platform in Indonesia
Drawing