diff --git a/content/configuration/images/ER_DE/image1.png b/content/configuration/images/ER_DE/image1.png
new file mode 100644
index 0000000..2318ade
Binary files /dev/null and b/content/configuration/images/ER_DE/image1.png differ
diff --git a/content/configuration/images/ER_DE/image10.png b/content/configuration/images/ER_DE/image10.png
new file mode 100644
index 0000000..0ff48f3
Binary files /dev/null and b/content/configuration/images/ER_DE/image10.png differ
diff --git a/content/configuration/images/ER_DE/image11.png b/content/configuration/images/ER_DE/image11.png
new file mode 100644
index 0000000..508400d
Binary files /dev/null and b/content/configuration/images/ER_DE/image11.png differ
diff --git a/content/configuration/images/ER_DE/image12.png b/content/configuration/images/ER_DE/image12.png
new file mode 100644
index 0000000..c473012
Binary files /dev/null and b/content/configuration/images/ER_DE/image12.png differ
diff --git a/content/configuration/images/ER_DE/image13.png b/content/configuration/images/ER_DE/image13.png
new file mode 100644
index 0000000..c78cc1d
Binary files /dev/null and b/content/configuration/images/ER_DE/image13.png differ
diff --git a/content/configuration/images/ER_DE/image14.png b/content/configuration/images/ER_DE/image14.png
new file mode 100644
index 0000000..09ef47c
Binary files /dev/null and b/content/configuration/images/ER_DE/image14.png differ
diff --git a/content/configuration/images/ER_DE/image15.png b/content/configuration/images/ER_DE/image15.png
new file mode 100644
index 0000000..f5b2212
Binary files /dev/null and b/content/configuration/images/ER_DE/image15.png differ
diff --git a/content/configuration/images/ER_DE/image16.png b/content/configuration/images/ER_DE/image16.png
new file mode 100644
index 0000000..5699ed8
Binary files /dev/null and b/content/configuration/images/ER_DE/image16.png differ
diff --git a/content/configuration/images/ER_DE/image17.png b/content/configuration/images/ER_DE/image17.png
new file mode 100644
index 0000000..1fa2c65
Binary files /dev/null and b/content/configuration/images/ER_DE/image17.png differ
diff --git a/content/configuration/images/ER_DE/image18.png b/content/configuration/images/ER_DE/image18.png
new file mode 100644
index 0000000..c7e0191
Binary files /dev/null and b/content/configuration/images/ER_DE/image18.png differ
diff --git a/content/configuration/images/ER_DE/image19.png b/content/configuration/images/ER_DE/image19.png
new file mode 100644
index 0000000..89c9a71
Binary files /dev/null and b/content/configuration/images/ER_DE/image19.png differ
diff --git a/content/configuration/images/ER_DE/image2.png b/content/configuration/images/ER_DE/image2.png
new file mode 100644
index 0000000..a9152b3
Binary files /dev/null and b/content/configuration/images/ER_DE/image2.png differ
diff --git a/content/configuration/images/ER_DE/image20.png b/content/configuration/images/ER_DE/image20.png
new file mode 100644
index 0000000..b33166c
Binary files /dev/null and b/content/configuration/images/ER_DE/image20.png differ
diff --git a/content/configuration/images/ER_DE/image21.png b/content/configuration/images/ER_DE/image21.png
new file mode 100644
index 0000000..5a22531
Binary files /dev/null and b/content/configuration/images/ER_DE/image21.png differ
diff --git a/content/configuration/images/ER_DE/image22.png b/content/configuration/images/ER_DE/image22.png
new file mode 100644
index 0000000..ad1e136
Binary files /dev/null and b/content/configuration/images/ER_DE/image22.png differ
diff --git a/content/configuration/images/ER_DE/image23.png b/content/configuration/images/ER_DE/image23.png
new file mode 100644
index 0000000..7de1f7b
Binary files /dev/null and b/content/configuration/images/ER_DE/image23.png differ
diff --git a/content/configuration/images/ER_DE/image24.png b/content/configuration/images/ER_DE/image24.png
new file mode 100644
index 0000000..2e39566
Binary files /dev/null and b/content/configuration/images/ER_DE/image24.png differ
diff --git a/content/configuration/images/ER_DE/image25.png b/content/configuration/images/ER_DE/image25.png
new file mode 100644
index 0000000..845df8c
Binary files /dev/null and b/content/configuration/images/ER_DE/image25.png differ
diff --git a/content/configuration/images/ER_DE/image26.png b/content/configuration/images/ER_DE/image26.png
new file mode 100644
index 0000000..aed7318
Binary files /dev/null and b/content/configuration/images/ER_DE/image26.png differ
diff --git a/content/configuration/images/ER_DE/image27.png b/content/configuration/images/ER_DE/image27.png
new file mode 100644
index 0000000..4b0cadc
Binary files /dev/null and b/content/configuration/images/ER_DE/image27.png differ
diff --git a/content/configuration/images/ER_DE/image28.png b/content/configuration/images/ER_DE/image28.png
new file mode 100644
index 0000000..b2e348a
Binary files /dev/null and b/content/configuration/images/ER_DE/image28.png differ
diff --git a/content/configuration/images/ER_DE/image29.png b/content/configuration/images/ER_DE/image29.png
new file mode 100644
index 0000000..0e96177
Binary files /dev/null and b/content/configuration/images/ER_DE/image29.png differ
diff --git a/content/configuration/images/ER_DE/image3.png b/content/configuration/images/ER_DE/image3.png
new file mode 100644
index 0000000..907b896
Binary files /dev/null and b/content/configuration/images/ER_DE/image3.png differ
diff --git a/content/configuration/images/ER_DE/image30.png b/content/configuration/images/ER_DE/image30.png
new file mode 100644
index 0000000..035cb22
Binary files /dev/null and b/content/configuration/images/ER_DE/image30.png differ
diff --git a/content/configuration/images/ER_DE/image31.png b/content/configuration/images/ER_DE/image31.png
new file mode 100644
index 0000000..92f2736
Binary files /dev/null and b/content/configuration/images/ER_DE/image31.png differ
diff --git a/content/configuration/images/ER_DE/image32.png b/content/configuration/images/ER_DE/image32.png
new file mode 100644
index 0000000..abcc715
Binary files /dev/null and b/content/configuration/images/ER_DE/image32.png differ
diff --git a/content/configuration/images/ER_DE/image33.png b/content/configuration/images/ER_DE/image33.png
new file mode 100644
index 0000000..ea400fe
Binary files /dev/null and b/content/configuration/images/ER_DE/image33.png differ
diff --git a/content/configuration/images/ER_DE/image34.png b/content/configuration/images/ER_DE/image34.png
new file mode 100644
index 0000000..3002cc6
Binary files /dev/null and b/content/configuration/images/ER_DE/image34.png differ
diff --git a/content/configuration/images/ER_DE/image35.png b/content/configuration/images/ER_DE/image35.png
new file mode 100644
index 0000000..2d3dd38
Binary files /dev/null and b/content/configuration/images/ER_DE/image35.png differ
diff --git a/content/configuration/images/ER_DE/image36.png b/content/configuration/images/ER_DE/image36.png
new file mode 100644
index 0000000..e965077
Binary files /dev/null and b/content/configuration/images/ER_DE/image36.png differ
diff --git a/content/configuration/images/ER_DE/image37.png b/content/configuration/images/ER_DE/image37.png
new file mode 100644
index 0000000..b0c2aae
Binary files /dev/null and b/content/configuration/images/ER_DE/image37.png differ
diff --git a/content/configuration/images/ER_DE/image38.png b/content/configuration/images/ER_DE/image38.png
new file mode 100644
index 0000000..dcce742
Binary files /dev/null and b/content/configuration/images/ER_DE/image38.png differ
diff --git a/content/configuration/images/ER_DE/image39.png b/content/configuration/images/ER_DE/image39.png
new file mode 100644
index 0000000..cee2c13
Binary files /dev/null and b/content/configuration/images/ER_DE/image39.png differ
diff --git a/content/configuration/images/ER_DE/image4.png b/content/configuration/images/ER_DE/image4.png
new file mode 100644
index 0000000..8f2261f
Binary files /dev/null and b/content/configuration/images/ER_DE/image4.png differ
diff --git a/content/configuration/images/ER_DE/image40.png b/content/configuration/images/ER_DE/image40.png
new file mode 100644
index 0000000..943f203
Binary files /dev/null and b/content/configuration/images/ER_DE/image40.png differ
diff --git a/content/configuration/images/ER_DE/image41.png b/content/configuration/images/ER_DE/image41.png
new file mode 100644
index 0000000..6322431
Binary files /dev/null and b/content/configuration/images/ER_DE/image41.png differ
diff --git a/content/configuration/images/ER_DE/image42.png b/content/configuration/images/ER_DE/image42.png
new file mode 100644
index 0000000..755e4fc
Binary files /dev/null and b/content/configuration/images/ER_DE/image42.png differ
diff --git a/content/configuration/images/ER_DE/image43.png b/content/configuration/images/ER_DE/image43.png
new file mode 100644
index 0000000..e9a054c
Binary files /dev/null and b/content/configuration/images/ER_DE/image43.png differ
diff --git a/content/configuration/images/ER_DE/image44.png b/content/configuration/images/ER_DE/image44.png
new file mode 100644
index 0000000..707e311
Binary files /dev/null and b/content/configuration/images/ER_DE/image44.png differ
diff --git a/content/configuration/images/ER_DE/image45.png b/content/configuration/images/ER_DE/image45.png
new file mode 100644
index 0000000..0e923c3
Binary files /dev/null and b/content/configuration/images/ER_DE/image45.png differ
diff --git a/content/configuration/images/ER_DE/image5.png b/content/configuration/images/ER_DE/image5.png
new file mode 100644
index 0000000..9a63fc5
Binary files /dev/null and b/content/configuration/images/ER_DE/image5.png differ
diff --git a/content/configuration/images/ER_DE/image6.png b/content/configuration/images/ER_DE/image6.png
new file mode 100644
index 0000000..1d1e810
Binary files /dev/null and b/content/configuration/images/ER_DE/image6.png differ
diff --git a/content/configuration/images/ER_DE/image7.png b/content/configuration/images/ER_DE/image7.png
new file mode 100644
index 0000000..d3cab1c
Binary files /dev/null and b/content/configuration/images/ER_DE/image7.png differ
diff --git a/content/configuration/images/ER_DE/image8.png b/content/configuration/images/ER_DE/image8.png
new file mode 100644
index 0000000..0367693
Binary files /dev/null and b/content/configuration/images/ER_DE/image8.png differ
diff --git a/content/configuration/images/ER_DE/image9.png b/content/configuration/images/ER_DE/image9.png
new file mode 100644
index 0000000..e1b22ff
Binary files /dev/null and b/content/configuration/images/ER_DE/image9.png differ
diff --git a/content/configuration/transition_kit_de.md b/content/configuration/transition_kit_de.md
new file mode 100644
index 0000000..385a575
--- /dev/null
+++ b/content/configuration/transition_kit_de.md
@@ -0,0 +1,279 @@
+# Transition Kit from Old Data Entry App (Legacy App) to New Data Entry App (Aggregate data)
+
+
+
+- [Transition Kit from Old Data Entry App (Legacy App) to New Data Entry App (Aggregate data)](#transition-kit-from-old-data-entry-app-legacy-app-to-new-data-entry-app-aggregate-data)
+ - [Introduction](#introduction)
+ - [Benefits in brief](#benefits-in-brief)
+ - [Feature comparison of Old (Legacy App) vs. New App.](#feature-comparison-of-old-legacy-app-vs-new-app)
+ - [Feature comparison of Old (Legacy App) vs. New App Details with Screenshots](#feature-comparison-of-old-legacy-app-vs-new-app-details-with-screenshots)
+ - [Initial Interface Review](#initial-interface-review)
+ - [Option Menu Use/Function](#option-menu-usefunction)
+ - [Sections and Filters](#sections-and-filters)
+ - [Run Validation](#run-validation)
+ - [Data Element Details](#data-element-details)
+ - [New Features for V42](#new-features-for-v42)
+ - [Pivot options in aggregate datasets sections](#pivot-options-in-aggregate-datasets-sections)
+ - [Default](#default)
+ - [Pivot](#pivot)
+ - [Move a category to rows](#move-a-category-to-rows)
+ - [Content displayed before/after section](#content-displayed-beforeafter-section)
+ - [Moving a Dataset from the Legacy (Old App) to the New App](#moving-a-dataset-from-the-legacy-old-app-to-the-new-app)
+ - [Review Current Configuration](#review-current-configuration)
+ - [Understand Changes](#understand-changes)
+ - [Prepare for Migration](#prepare-for-migration)
+ - [Limitations of New App](#limitations-of-new-app)
+ - [Use cases](#use-cases)
+ - [Default form:](#default-form)
+ - [Section form](#section-form)
+
+
+## Introduction
+
+This transition kit is designed to support DHIS2 users and implementers in moving from the legacy aggregate Data Entry app to the New Data Entry App. It provides practical guidance, highlights key differences, and outlines updated workflows to ensure a smooth transition.
+
+The goal is to help users adapt quickly and efficiently to the new interface and functionalities introduced in the latest DHIS2 versions, while maintaining **data quality and reporting continuity**.
+
+## Benefits in brief
+
+1. **Modern and user-friendly interface:** More intuitive layout, improved navigation, and responsive design.
+2. **Detailed data element information:** Includes code, data element ID, category option combo ID, and last updated details.
+3. **Support for configurable forms**(default, section, and HTML-based).
+4. **Offline functionality** (especially via DHIS2 Android).
+5. **Enhanced validation and feedback**: Interactive side panels with categorized alerts.
+6. **Active development and support:** Unlike the deprecated legacy app, the new app is continuously improved and maintained.
+7. **Accessibility enhancements**: Better keyboard navigation and usability for a wider range of users.
+
+## Feature comparison of Old (Legacy App) vs. New App.
+
+
+| **Features** | **Old App (Legacy App)** | **New App** |
+|-------------------------|---------------------------------------|--------------------------------------------------------------|
+| **Interface** | Dataset & Period on right; OU on left | OU, Dataset, Period all selected from persistent top bar |
+| **Menus** | Top-right corner | Options button (includes Help) |
+| **Sections/Filters** | Visible after period selection | Available directly at top bar |
+| **Data element filter** | Limited to one section at a time | Global filter across sections; can narrow to one section |
+| **Run validation** | Button at top right menu; opens popup | Bottom of form; interactive side panel with categorized alerts |
+| **Data element details**| Popup window for comments/follow-up | Inline side panel; comments, audit history, legends available |
+
+## Feature comparison of Old (Legacy App) vs. New App Details with Screenshots
+
+### Initial Interface Review
+
+**New App**: Organisation unit, dataset, and period selected from a persistent top bar. Modern, user-friendly design with improved usability.
+
+**Legacy App**: OU on left panel, dataset selected separately. Outdated interface and workflows.
+
+
+
+### Option Menu Use/Function
+
+
+
+**New App**
+1. **Print form with values**: Prints the current data entry form including all entered data values. Useful for reviews, audits, or physical record-keeping.
+2. **Print empty form**: Prints a blank version of the dataset form. Useful for offline data collection or field distribution.
+3. **Help:** Opens documentation or guidance related to the Data Entry App. Supports users in understanding the interface and resolving issues.
+
+When you click on Help the window will open that is very useful for understanding data entry status at a glance.Built in shortcuts make data entry faster and more efficient.
+
+
+
+**Old App (Legacy App)** The Print form and Print blank form button is available at the extreme right top corner.
+
+
+
+### Sections and Filters
+
+Both are supported with section forms where you can select the section of the form
+
+**New App:** Sections displayed on the top bar; global filter across all sections with the option to narrow down by section.
+
+**Old App (Legacy App):** Section forms only available after selecting the period; filters worked within one section at a time.
+
+**Benefit**: Greater efficiency when working with large/complex forms.
+
+
+
+>Note
+> In the **Old App (Legacy App),** the data element filter was limited to one section at a time. This meant that if you wanted to find a data element, you had to first navigate to the specific section where it was located (filtering worked only within that active section).
+>
+> In the **New App**, the filter is global across all sections and can be applied to one section at a time. This means you can search for any data element from the top filter bar, and it will display results across the entire form, regardless of which section the element belongs to.
+>
+> Additionally, when a specific section is open, the filter can be used to narrow down elements within that section alone. This dual functionality offers flexibility and significantly improves efficiency, especially when working with large or complex forms.
+
+
+
+
+
+### Run Validation
+
+**New App:** Validation results shown in a **side panel**, grouped into categories: High, Medium, Low. Alerts are summarized for easier review.
+
+
+
+**Old App**: The **“Run Validation”** button is present (usually in the top right menu bar). And it only pops up the window with all violations messages if any.
+
+
+
+### Data Element Details
+
+**New App** Users can add comments and mark data items for follow-up directly from the data entry screen which gives a more clear view and understanding.Comments, audit history, and legends are handled via side panels
+
+
+
+**Old App (Legacy App)** When a user **double-clicked on a data cell** in the Data Entry app (Aggregate), a **popup window** opened.
+
+This popup allowed users to:
+
+* Enter or edit a value
+* Add a comment related to the specific data value
+* View or update the last updated date
+* See who last edited the value
+
+
+
+## New Features for V42
+
+### Pivot options in aggregate datasets sections
+
+These pivot tables control how data elements and category option combos are displayed within a section of a dataset.
+
+**Configuring Pivot Options for a Data Set**
+
+1. Open the data set - Navigate to the data set you have created and to which you’ve already assigned data elements.
+2. Go to 'Manage Sections' - In the data set settings, click on Manage Sections to organize how your form is structured.
+3. Select 'Pivot Options' - Inside the section management view, choose Pivot Options to define how your data will be displayed in analytics.
+4. Choose the layout based on your design
+5. Configure the pivot options (e.g. whether data elements appear as rows or columns) according to the reporting design and data structure you need.
+
+#### Default
+By default, data elements are arranged in rows, while categories (disaggregation dimensions) are displayed in columns.
+
+
+
+
+
+#### Pivot
+
+Categories as rows, data elements as columns
+ * Useful when there are **many data elements** and few categories
+ * Makes the form **more compact horizontally**
+
+ 
+
+#### Move a category to rows
+
+* It is a hybrid layout
+* One category dimension is moved to rows
+* It helps to give more control when the dataset is large.
+
+ 
+
+#### Content displayed before/after section
+
+You can add HTML-based instructions, notes, or links that appear above or below the section form — useful for guidance or data entry rules.
+
+
+
+
+## Moving a Dataset from the Legacy (Old App) to the New App
+
+### Review Current Configuration
+
+* Data elements and category combinations
+* Custom or section forms (Check if using Java script)
+* Validation rules
+* Indicators
+
+### Understand Changes
+
+* Interface - The user interface is different
+* Custom forms - using Java script are no longer supported but HTML is supported
+* Section forms - are supported but can have different style with use of pivot - style options
+* Filtering - Improved filter and search feature
+
+### Prepare for Migration
+
+* Redesign custom forms without using Java script
+* Re - adjust the section forms
+* Test all the forms in New App
+
+## Limitations of New App
+
+| **Limitations** | **Alternative/Workaround** |
+|----------------------------------|-----------------------------------------------------------|
+| No JavaScript support in custom forms | Use indicators for calculations and validations for logic checks |
+| No enhanced styling | Use HTML (only simple table layouts) |
+
+## Use cases
+
+Below are the practical examples showing how forms behave in the **Legacy Data Entry App** compared to the **New Data Entry App**.
+
+### Default form:
+
+1. Interface
+
+ **Legacy App**
+ - Organisation unit selected from left-hand panel; dataset separately
+ - Outdated layout, harder to navigate between forms
+
+ **New App**
+ - Organisation unit, dataset, and period all selected from the **persistent top bar**.
+ - Modern, cleaner layout for faster switching.
+
+
+
+1. Organization unit
+
+ **Legacy App**: All OUs displayed, even if the dataset is not assigned (inactive ones appear greyed).
+
+ **New App**: Only OUs assigned to the form are enabled
+
+
+
+1. Error Display:
+
+ **Legacy App**: AError shown in popup messages
+
+ **New App**: Errors displayed inline within the form, with clearer indicators
+
+ 
+ 
+
+2. Run validation interface
+
+ **Legacy App**: “Run Validation” button in top-right menu; results in a popup.
+
+ **New App**:Validation button at the bottom of the form; results appear in a side panel, grouped into High / Medium / Low.
+
+ 
+ 
+
+
+### Section form
+
+1. Interface
+
+ **Legacy App**: Sections appear only after period selection
+
+ **New App**:Section tabs are visible at the top bar immediately
+
+ 
+ 
+
+2. Filter section
+
+ **Legacy App**: Filter applies to one section at a time
+
+ **New App**:Global filter across all sections, plus ability to narrow to a single section.
+ 
+ 
+
+
+3. New features
+ * Row/Column Switching for categories (e.g., “Communicable immunizable” dataset section).
+ * Not available in Legacy App.
+ * Makes large forms easier to read horizontally or vertically.
+ 
+
diff --git a/content/database_design/data-quality-06-supervision-android.md b/content/database_design/data-quality-06-supervision-android.md
new file mode 100644
index 0000000..6d3a0d4
--- /dev/null
+++ b/content/database_design/data-quality-06-supervision-android.md
@@ -0,0 +1,88 @@
+# User guide to the Supervision App - Android version
+
+## Background
+
+The mobile supervision app is designed for users on the ground. It enables them to synchronize supervision schedules, and offers the following main features:
+
+* A dashboard showing the current status of indicators;
+* An overview of previous supervision action plans;
+* Access to supervision tracker forms;
+* Synchronization for sending collected data to DHIS2;
+* Offline functioning.
+
+## Technical Specification and Installation
+
+### Android requirement and App development
+
+ This application has been developed and tested using Android version 1x. The app should work on Android 13 and above, but please note that the development and bug fixing was done on version 1x. The app can be used with a phone or tablet running the Android operating system.
+
+### Installation instruction
+
+Until the app is published on the Playstore, you can install it manually by getting the link from your DHIS2 administrator.
+ 1. To install the app, you should first download it using the link [Android Supervision App](https://drive.google.com/file/d/1icloLMhiRr-474HA-sFgrYWIs1aHNoD9/view?usp=sharing)
+ 2. Once you've downloaded the app's APK file, go to the download folder on your phone or tablet and double-click on the file.
+
+ 
+
+Then, follow the instructions to finalize the installation and open the App.
+
+
+
+
+
+
+### Login page
+
+Once opened, the first thing to do is to log in to the App using your DHIS2 user account.
+
+
+
+
+### Home interface
+
+After login, we can see the available supervision form(s) (from the tracker configured in DHIS2). Examples: DQR-RSC, …
+It is important to get started with the three-step configuration synchronization by clicking on :
+
+1. the three horizontal lines;
+2. on Settings;
+3. on Configuration synchronization.
+
+
+
+
+
+After the configuration synchronization, come back to the homepage and click on the following :
+
+
+
+1. Select the tracker to be used.
+2. Click here to synchronize data: this will update the downloaded data for the dashboard and for filling in fields in the tracker. This is useful when changes have occurred between the time of planning and the time of supervision.
+3. Select the organization unit to be supervised from the list
+4. For the selected organization unit, the various planned supervisions (events) are displayed. The most recent are at the top, and the name of the program to be supervised (or program area) appears next to the date. Clicking on each event displays the charts of the indicators whose quality you wish to check. The single values displayed at the top correspond to the values of the period indicated at the top. To display the values of another period, simply click on the period and select the new period in the calendar.
+
+### Open the form
+
+After clicking on a scheduled supervision, click on the **Open form** button in the top right corner. You will then have access to the content of the form, showing the sections with their content hidden. Click on **Show fields** to expand the fields in a section so that you can fill them in, then repeat the process until you reach the end of the form.
+
+### Filling the supervision form
+
+After opening the form, click on the “Show details” link of each section of the form to access the fields to be filled in.
+
+When you have finished, click on the following icon to save your work :
+
+### Supervision dashboard: results visualization
+
+It is possible to view supervision results directly from the Android, even if the data is not synchronized. To do so, click on the chart button at the bottom center.
+
+You can display other indicators by clicking on the other tabs of the dashboard.
+
+ Note: The dashboard is automatically generated from the data entered, even if there is no Internet connection.
+
+It is possible to share the dashboard in pdf format on or offline. When online, the dashboard pdf file can be shared using all the communication apps available on the Android device: Whatsapp, Snapchat, Gmail, Slack, etc. However, when an Internet connection is not available, the file can be shared via Bluetooth. To do this, you'll need to make sure that Bluetooth mode is enabled on both devices, and that they are paired. You can also download the file to your device by clicking on: Share > Printer > pdf
+
+### Data synchronisation
+
+After you've saved the supervision data, when you are back online, you need to synchronize the data with the server.
+To do this, go back to the supervision selection page and click on the synchronize button.
+
+It is also possible to go to the “Settings” menu and click on “Synchronize data” to send the site supervision data set entered locally onto the server.
diff --git a/content/database_design/data-quality-07-supervision-web.md b/content/database_design/data-quality-07-supervision-web.md
new file mode 100644
index 0000000..e3a8047
--- /dev/null
+++ b/content/database_design/data-quality-07-supervision-web.md
@@ -0,0 +1,478 @@
+# User Guide to the Supervision App - Web Version
+
+## Introduction
+
+It's well known that data quality and data use are closely linked. To improve data use, we must also strive to improve data quality, and vice versa. Various tools, including the Routine Data Quality Assessment (RDQA) tool, have been developed and used to assess data accuracy and the functioning of the Health Information System (HIS) across its six components. However, the RDQA tool and its use have shown some limitations, namely:
+
+* The **RDQA tool is Excel-based**, and the results of supervision visits stay on people's computers without being shared. As a result, it is **difficult to get an overview of the problems encountered in the field during supervision** visits across the country;
+
+* Difficulties in monitoring the implementation of recommendations made during supervision visits;
+
+* Archiving of Excel files
+
+* **Lack of transparency in the selection of health facilities and districts to be visited.** This has led to a situation where health facilities located along good roads or in towns with decent infrastructure are the most visited.
+
+In response to this problem, a number of institutions have developed digital solutions:
+
+* Since 2019, HISPWCA has started implementing a digital tool to facilitate supervision and also the archiving of historical data from these supervisions. This digitalization is based on WHO's RDQA tool. After the development of the first version of the tool, it has been used in Mali.
+
+* Since 2021, MEASURE MALARIA/JSI has been implementing an Android app and a DHIS2 package for the supervision and archiving of mRDQA supervision data. After a test phase in Côte d'Ivoire and Sierra Leone, its use has been initiated in Mali, Guinea and Burkina Faso.
+
+PATH is currently developing a web and mobile application based on the DHIS2 data quality audit file.
+
+Aware of the duplication of efforts by partners in different countries, the Global Fund, USAID and WHO decided to support the implementation of a standardized electronic tool, ready to host other specific supervision tools.
+
+The app currently includes two supervision tools:
+
+1. **eRDQA** (Routine Data Quality Assessment) and
+2. **DQR-RSC** (Data Quality Review Routine Supervision Checklist).
+
+**The approach to using the various forms in the application remains the same, from planning to performing supervision in the field**.
+
+The screenshots used in this guide are based on the web version of **DQR-RSC**. The Android version is covered in a separate guide.
+
+
+## Supervision Workflow Overview
+
+
+
+## Step by Step Instructions to Use the Supervision App
+
+## Access to the App
+
+To access the App, proceed as follows:
+
+1. Log in to DHIS2 with your user account and password
+2. Click on the “Search box”
+3. Enter Sup or Supervisor in the Search box
+4. Click on the app icon to access the app.
+
+ 
+
+**Note** When you open the application, you will land on the **Main Page**, where all dashboards are displayed.To begin configuring or using the app, click on the **“Settings”** module located on the left-side panel
+
+## Settings
+
+### Supervision Settings
+
+When you click the **Settings** tab, four sub-tabs appear. The first one (selected by default) is **Supervision Settings**.
+
+This tab contains two main configuration areas:
+
+1. Tracker Program Selection: Allows you to select the Tracker Program used to configure the supervision form.By default, it uses **Generate Supervisions as Events**.
+2. Tracker Program Configuration List: Displays all Tracker Programs that have already been configured for supervision.
+
+ 
+
+
+* Selecting the tracker program under supervision settings
+
+ * Select the tracker
+ * Select the type on what basis - **Organisation units** (supervision of activities carried out in facilities) or **Agent** (supervision of workers in the facilities.Its Greyed out as its not active)
+ * Select the Configuration type. Select Configuration type Normal Supervisison Program (if not DQR - RSC)
+
+ 
+
+* Configuring Supervisor & Supervision Status
+To start with this we need to specify the following:
+ * Program stage
+ * Supervisor
+ * Supervision status
+ Fill in the program stage, supervisor and supervision status fields:
+
+ 
+
+* Other fields:
+
+ 
+
+This part of the configuration is useful for RDQA-type configurations, where a number of neutral data elements will be replaced by more meaningful names at the time of supervision, or to define how many times an object should be collected. This means telling the app which tracker fields correspond to what:
+
+1. **Supervision attribute autogenerated ID:** specifies which program attribute corresponds to the supervision ID.
+2. **How many indicators:** specifies the data element used to indicate the number of indicators that need to be checked on the site.
+3. **How many source documents ?:** specifies the data element used to indicate the number of source documents that need to be checked on site.That determines how many data elements need to be checked on the site.
+4. **Most recent verification period**: specifies the data element used to indicate the most recent date of the verification periods
+5. **Indicator period type**: specifies the data element used to indicate the indicator period type.
+6. **Time consistency period type**: specifies the data element used to indicate the time consistency period type.
+7. **Register name:** specifies the data element used to indicate the name of the register to be used for checking data elements.
+8. **Register keyword**: identifies the keyword to be replaced with the name of the register in the completeness section of the data elements. This keyword will generally be “registre” and/or “register” depending on whether you are using French and/or English. If you are using another language, please use the most appropriate term. If you have written this keyword in different ways in your tracker program, please fill in all possible variations, case-sensitive.
+9. **Global program area:** specifies the type of indicator linked to a specific program (area) to be monitored. The default domains are: SNIS, Malaria, HIV, TB, Vaccination, Maternal health. However, other areas can be added if required. This field is therefore used to indicate the data element that specifies the area to be supervised when the activity is scheduled.
+10. **Program keyword:** identifies the keyword to be replaced by the program name, particularly in cross-checking sections. This keyword will generally be “programme” and/or “program” depending on whether you use English and/or French. If you use another language, please use the most appropriate term. IF you have written this keyword in different ways in your tracker program, please fill in all possible variations, case-sensitive.
+11. **Number of periods in DHIS2:** specifies the number of periods for which you wish to automatically retrieve data already entered in DHIS2 for checking purposes. If you select 3 and it is April 2024, the app will automatically fill in the corresponding fields for each indicator with the values for March, February and January 2024.
+12. **Period - 1 keywords (as for Period - n keywords):** indicates to the app the keywords it will use to write the true period of the historical data to be retrieved from DHIS2. This option is useful when you want to retrieve values already entered in DHIS2 for checking or comparison purposes. For example, in the generic tracker, the name “*Indicator 1 - DHIS2 monthly value Period-1*” should be replaced by “*ANC1 - **Jan 2024 value***”. The “**Period -1**” keyword is used to replace Period -1 with Jan 2024 if it's February 2024. The indicator 1 part is also replaced by the real name of the indicator chosen at the time of planning the visit, giving “***ANC1 - value of Jan 2024***”. Click directly in the field, then click on the “***Enter***” button on the keyboard (Month 1, Quarter 1,Trimester 1). **Period -2 keywords:** Same as period -1 **Period -3 keywords:** Same as period -1
+13. **Please select the modules**: Provide the Schedule section with the list of modules to be administered for each supervised facility.
+
+
+
+
+* Configuration of the elements
+
+ The interface below allows you to manually add several additional elements to a type of supervision. These elements enhance the data quality analysis.
+
+ 1. You can configure the indicator, cross-checking, consistency over time, data element, and source document.
+ 1. Click on the corresponding buttons to add and configure each type of element. The details of each element are presented below.
+
+ 
+
+1. **Indicator configuration**
+
+ * **Indicator 1:** Defines the data element corresponding to indicator 1.
+ * **Period -1 DHIS2 value:** Defines the data element to be assigned the period -1 value of indicator 1. “Period - 2 DHIS2 value” to “Period - n DHIS2 value” do the same for periods -2 to - n.
+ * **Indicator keywords:** defines the keyword to be used to replace the generic name indicator 1 with the name of the indicator, e.g. “***Indicator 1** - DHIS2 monthly value Period -1*” -> “ **ANC1** - Jan 2024 value”.
+ * Repeat for each indicator.
+ * **Margin of error:** selects the data element that will receive the margin of error to be configured for the accuracy of the indicator.
+
+
+2. **Cross-checks configuration**
+
+ * **Program area:** indicates the type of indicator related to a program specific (area) to supervise.
+ * **Primary cross-check:** selects the data element from which cross-check 1 information will be collected.
+ * **Secondary cross-check:** selects the data element for cross-check information 2.
+ * **Cross-check keywords:** fill in this field with cross-check and corresponding cross-check. After each word is written, click on the “Enter” button on the keyboard. They will then be taken into account in the dashboard and on the Android side
+ * **Margin of error:** allows you to select the data element that will collect information on the margin of error of cross-checks.
+ * Repeat the above steps for each cross-check.
+ 
+
+3. **Consistency over time**
+ * **Program area:** specifies the type of indicator linked to a specific program (area) to be supervised.
+ * **Time consistency:** specifies the data element used to indicate the name of the indicator to be used for time consistency.
+ * **Margin of error:** specifies the data element that collects information on the margin of error for consistency over time.
+ 
+
+4. **Data elements and source documents**
+ * Data element: specifies the data element that allows you to indicate the name of the data element to be used for checking a register's data elements in terms of fill completeness.
+ * Keywords: Specifies the generic keyword that will correspond to the actual name of the data element in the app.
+ 
+
+5. **Source documents:**
+ * Source document: specifies the data element used to indicate the name of the source document to be assessed.
+ * Keywords: specifies the generic keyword that corresponds to the actual name of the document in the app. Example “source document 1”.
+
+6. **Margin of error:**
+
+ 
+
+ **About other tracker programs, the module selection list is added as follows :**
+ 
+
+ Once you have finished, click on the **Update Configuration** button.
+
+ 
+
+### Mapping/Indicator management
+
+#### Mapping of indicators
+
+In this section, the administrator can configure indicators by program, i.e. SNIS, Maternal Health, Immunization, HIV AIDS, TB, Malaria. These pre-configured programs are linked to the corresponding DHIS2 metadata content. However, the user has the option of adding other programs and indicators.
+
+To configure or match an indicator proposed in the checklist with a DHIS2 indicator, you need to:
+
+1. Select the indicator mapping sub-menu in the “**Settings**” menu.
+
+ 
+
+When you select this menu, the following will appear: click on “Create new indicator” and continue the process by first creating the program group (e.g., HIV, TB, etc.)
+
+
+
+* If there is an existing group already configured, proceed as follows:
+ 
+
+* If the group does not exist and we want to create it, proceed as follows:
+ 
+
+ The image above shows how to add an indicator by creating a new group. Follow the steps below:
+ 1. Select the “Create a new group” option.Check this option so you can set a custom group name for your indicators
+ 2. Enter the group name.In the **Group** field, enter the name of the group you want to add your indicators to. Example: ANC.
+ 3. Enter the indicator name. In the **Indicator** field, enter the name of the indicator you want to add
+ 4. Click the “Add” button. After entering the indicator name, click + Add. The indicator will appear in the table below under the corresponding column.
+ 5. Save the group and indicators.To add more indicators to the program, simply repeat the same step until you complete the desired list.Once all the indicators have been added, click on the **Save** button to validate and save the data.
+
+Here is an example of the HMIS program group in the image below:
+
+
+
+Marker 1 on the following image allows you to select the data element or indicator in dhis2.The selection of the data element or indicator on the left is immediately reflected in the field on the right. To complete the mapping, click on the radio button.
+ 
+
+Select the corresponding data element or indicator in DHIS2
+
+
+
+To do this,
+
+* Search for the desired indicator or data element and select it (marker 2).
+
+* For (marker 3), select the dataset in which the data element is located. This will tell the app how often to retrieve data from DHIS2.
+* If the data set is monthly, then the periods that the app will consider will be months.
+* If an indicator is configured, then the app will select a dataset from among the datasets containing the data elements that form the indicator.
+
+#### Modifying the program or indicators in an existing program (indicator type):
+
+
+
+If necessary, modify the indicator as proposed in your Excel copy to match what's in DHIS2. To do this, proceed as follows:
+
+1. Click on the edit icon
+2. Select the group
+3. Choose the relevant program in the dropdown menu.
+
+Once you have finished the mapping, click on “Save the mapping” at the top right.
+
+
+
+### Register management
+
+The app allows you to configure, for the various programs being monitored, the information verification registers during supervision.
+In this section, the administrator can configure **the registers** by program, namely SNIS, Maternal Health, Immunization, HIV/AIDS, TB, and Malaria. However, the user can add other registers.
+
+To create or match a register proposed in the checklist, you must:
+
+1. Select the “Register Management” submenu in the “**Settings**” menu.
+
+ When you click on this menu, here’s what appears:
+
+ 1. Click on **\+ Add** to continue the configuration process.
+ 2. Choose the program group (e.g., HIV, TB, etc.),
+ 3. Add the new register to the group, as shown in the following images.
+ 4. Save
+
+ 
+
+
+### Cross-checks management
+
+In this section, the tools needed to cross-check information or data are configured for the program being supervised, and the process is the same as for register management above.
+
+
+
+### Data elements management
+
+This section allows you to pre-assign data elements to be counted or checked for completeness and accuracy in the tools needed to cross-check information for the program being supervised, and the configuration process is the same as for register management above.
+
+
+
+### Document sources management
+The process applied to the other sections (register management, cross-checks management, data elements management) also applies to this one. This section allows you to assign document sources to verify information for the program being supervised.
+
+
+
+
+### Visualizations (Charts) and Maps
+
+A link is made between the application and some favorites related to indicators from the monitoring forms configured in DHIS2 using the tracker program.
+If there is already a configuration for charts and maps in the system, the steps for configuring charts, tables, and maps in the monitoring application are shown in the image below.
+
+
+
+Follow the steps below to add a chart, table, or map (favorite) to a supervision type:
+
+1. Click on **Visualizations and Map**
+2. **Select the Tracker program**: From the “Tracker Programs” drop-down menu, choose the relevant program.
+3. **Choose the visualization type**: Check the “**Select Charts and Tables (Favorites)**” or “**Select Maps (Favorites)**” option.
+4. **Search for the favorite**: In the search field, type a keyword (e.g., `anc`) to filter the visualizations available for that keyword.
+5. **Run the search**: Click on the “**Search**” button.
+6. **Select the desired favorite**: Check the box corresponding to the chart or table you want to add.**Verify the selection**: The name of the selected favorite will automatically appear at the bottom of the window, in the “Favorites” section.
+7. **Save the configuration**: Click on the “**Save**” button to finalize.
+
+NB: After saving, you can delete a favorite by clicking on the trash can icon as follows:
+
+
+
+## Favorites creation
+
+1. Selecting the supervision form
+
+ By clicking on the **Create favorites** field, you'll see the supervision sheets (checklists or programs) available in DHIS2. Choose the one you're interested in. This will give you access to the interface for configuring the indicators entered in a favorite.
+
+ 
+
+
+2. Configuring the favorite indicators
+
+ There are two possibilities for this indicator configuration: either you create a new favorite with its entire content, or you improve a favorite already created in the system.
+
+ 
+
+ * Creating a new favorite
+
+ A favorite is a pre-selection of indicators, source documents and any parameters required for on-site supervision or data verification visits. For example, during an RDQA visit, you need to pre-select the indicators whose data you are going to check, the source documents to be used for verification, the data elements whose completeness you are going to check in the register, and so on. To avoid having to make this selection at each visit, the application allows you to create a favorite containing the choices made for later reuse (either during the same output or for another period).
+
+
+
+ To create a new favorite, you need to:
+ * Select the checklist (or DHIS2 program) to be used.
+ * Check “Create a new configuration”.
+ * Choose the program stage (if the tracker has several stages, e.g. one stage for the district level and another for the Health Facility level, you can configure a favorite for each level).
+
+
+ Once the program stage has been selected, a table appears on the right-hand side, proposing the definition of the supervision area (program area), indicators, source documents and register data elements to be used for verification.
+
+ For a start, those familiar with the Excel version of the tool can build on it, as the electronic version is a replica of the existing Excel version.
+
+ There are 4 levels to fill in:
+
+ 1. Indicator configuration: at this level, the choice of ***global program area*** in the drop-down list applies to the other chapters. We can also choose the ***number of indicators*** to be supervised, and this choice will also affect the number of fields in the other three chapters.The **“Indicator name”** field has a drop-down menu allowing you to choose the indicators already configured in the app settings for this particular program.The **“Margin of error”** field will be filled in manually, according to what the staff of the program to be supervised has decided to be the standard
+ 
+ 2. Cross-check configuration**
+ The **Primary Source** field allows you to choose from a drop-down list already configured in the app Settings. The **Secondary Source** field also allows you to choose from a drop-down list already configured in the app Settings.
+ The **Margin of Error** field will be manually filled in according to what the staff of the program to be supervised has decided should be the standard.
+ 
+ 3. Consistency over time
+ The **Indicator Name** field has a drop-down menu allowing you to select the indicators already configured in the application settings for this particular program.
+ The **Margin of error** field will be manually filled in according to what the staff of the program to be supervised has decided to be the standard.
+ 
+
+ 4. **Data elements and source document** This section allows you to choose the number of data elements to be included in the data completeness check. This choice will have an impact on the number of fields to be filled in the **data element** and **source document** columns.
+ The **How many data elements** field allows you to choose the number of data elements to check for completeness.
+ The **How many source documents** field allows you to select the number of source documents that supervisors will check in the field.
+ The **Register name** field allows you to select from a drop-down list the register names configured in the application settings for a specific program.
+ The **Data Element** field allows you to select from a drop-down list the data elements configured in the app settings for a specific program.
+ The **Source Document** field allows you to select the source documents configured in the app settings for a specific program.
+ The **Margin of error** field will be manually filled in according to what the staff of the program to be supervised has decided to be the standard. At this stage, filling in this field is not mandatory.
+ 
+
+ * Save as favorite
+
+ * Modifying an existing favorite
+ 
+ 1. Choose your supervision
+ 2. Click on the button from “Favorites”
+ 3. Choose the favorite you need from the drop - down menu. After selecting the favorite name, its content is displayed in the table on the right. In this table, you can modify the different elements.
+ 4. When you have finished the modification, click on the Update button .
+
+## Scheduling
+
+### Supervisions scheduling interface
+
+When you click on the **Scheduling** section, a three-level interface appears:
+
+
+
+* **The Search bar,** with the supervision form to be selected, the target organization unit for supervision, the period for scheduled supervision and the **Search** button for displaying scheduled supervision queries**.**
+* **The scheduled supervisions display area**
+* **The button for creating new schedules**
+
+#### Creating a new schedule
+
+1. To create a new schedule, click on the + icon button at the bottom right of the first interface of the Schedule option.
+2. In the schedule creation interface, there are two steps
+ 
+
+ * **The configuration**
+ The configuration of the new schedule consists of:
+
+ 
+ * Selecting the entity (organization unit).
+ * Selecting the tracker program (DQR-RSC, ECD, etc.).
+ * Selecting a favorite if available. If not, exit to create a new favorite in the “**Create favorites**” section.
+ * To cancel the process, simply click on the blue button as shown below.
+ * Other programs - In this case, there is no need to select a favorite.
+
+ * **The finalization** At this stage, you have to choose between types of schedule:
+ * 
+
+ * **Direct**: for arbitrary site selection
+ * **Performance-based**: allows you to request the app to select a number of sites on the basis of their performance against some selected indicators
+ * **Random**: allows you to request the app to randomly suggest sites to visit, after specifying the number of sites to be visited
+
+#### Direct scheduling
+
+Choosing this option assumes that the supervisor knows in advance the problems in one or more of the structures he or she decides to supervise. To do this, the supervision scheduler clicks on the **Direct** button, then adds the supervision teams, and selects one or more organization units in which supervision will take place.
+
+If all supervisors have a DHIS2 user account, don’t click on the **Add** button in the **Other supervisors** section**.**
+
+1. Specify the team lead
+2. Choose the organization units to be supervised (image below).
+3. Assign dates and supervision teams to each site.
+ 
+ 
+ 
+ 
+ 
+
+
+
+ Note: It is possible to choose the following module(s) applicable to the facilities scheduled for supervision: This has already been configured in the section settings Configuration other fields- Please select the modules…
+
+1. Click on the **Schedule the supervision(s)** button to complete the process
+ 
+
+#### Performance-based scheduling
+
+Choosing this option assumes that the supervision scheduling team wants to carry out supervision based on the performance of some indicators at the sites to be supervised.
+
+
+
+
+There are two ways of selecting indicators for this type of scheduling:
+
+* From favorites
+* Direct (define your own list of indicators on the fly). This list can then be saved as a favourite
+
+**Note** There is a difference between a favorite for indicator-based scheduling and a general favorite based on indicators chosen by a program to be supervised in the field. It should also be noted that these favorites are created from the **direct** creation of the favorites.
+
+Start by choosing the **Performance-based** supervision.
+
+1. Clicking on the **Select the indicators** button allows you to choose directly the indicators in DHIS2
+ 
+
+2. Choosing the indicators
+3. By clicking on **Save**, we can save this schedule as a **favorite** and also add supervision teams as explained in the **Direct scheduling** section**.
+
+ 
+ 
+
+ 4. After selecting the supervision team, the next step is to select the **organization units** and **period**. At this level, you choose either the national, regional or district level, depending on your needs, and then you must assign an **organization unit group set** to access the period to be explored for performance analysis.
+ 5. Once you've filled in all the required fields, click on the **Display results** button to view the health facilities matching your selection criteria.
+
+#### Random scheduling
+
+By choosing this option, the supervision schedulers are not supposed to have any specific information prior to choosing the sites to supervise. Instead, they will go to a higher hierarchy level to select a random number of structures to visit.
+To do this, they must first configure the supervision teams in the same way as for the previous options.
+
+
+
+## Supervision Schedule
+
+This interface allows the users to view the different supervisions scheduled over time.
+It has two parts:
+1. A search box for scheduled supervisions by supervision form
+ * Program: this field allows you to select the supervision form from a drop-down menu.
+ * Organization unit: allows you to select the facilities that will be subject to planned supervision audits.
+ * Period: selects the period of planned supervision to be checked
+ * Scheduling: allows you to filter planned supervisions. There are three possibilities:
+ * My supervisions: corresponds to supervisions assigned to the user as supervisor.
+ * Scheduled by me: corresponds to supervisions scheduled by the logged-in user.
+ * All: corresponds to all supervisions scheduled in the system during the period the user wishes to check.
+ * Once you have selected all the queries, click on the **Apply** button to view the search result.
+
+ 
+
+2. A display area for search result - It is represented by four field subgroups. From left to right, we have:
+ * **At the top left**, **the calendar** with the date fields in which the health facilities to be supervised are displayed.
+ * **On the left, at the bottom of the calenda**r, we have a small field containing schedules by type and number. These are **scheduled** supervisions, **cancelled** supervisions, supervisions **in progress** and **completed** supervisions.
+ * **At the top right**, a field containing the **organization units** to be supervised, with the planned **period**, the **supervision status** and a rectangle icon with an upward arrow, leading to the supervision form field in the corresponding Tracker program if the supervisor wants to use the web at the supervision site.
+ * **At the bottom right**, we have a field displaying the schedule results in a pie chart showing the colorations assigned to the supervision status.
+
+ 
+
+## Dashboard
+
+This Dashboard has been customized to suit the needs of each supervision form integrated into the app.
+Its interface has two levels:
+
+1. A filter zone for scheduled supervisions by supervision form.
+
+The user can use this dashboard to analyze data from supervisions carried out in the field. To do so, he/she must select some information to display the results as tables or charts:
+
+* the supervision form in the program drop-down list,
+* the organization unit,
+* the organization unit level,
+* the period.
+
+To display the data, click on the **Apply** button after selecting all the appropriate options.
+
+2. A display area for dashboard elements
+
+
diff --git a/content/database_design/resources/images/dq_android_supervision/image1.png b/content/database_design/resources/images/dq_android_supervision/image1.png
new file mode 100644
index 0000000..87d9c3b
Binary files /dev/null and b/content/database_design/resources/images/dq_android_supervision/image1.png differ
diff --git a/content/database_design/resources/images/dq_android_supervision/image10.png b/content/database_design/resources/images/dq_android_supervision/image10.png
new file mode 100644
index 0000000..a78ecba
Binary files /dev/null and b/content/database_design/resources/images/dq_android_supervision/image10.png differ
diff --git a/content/database_design/resources/images/dq_android_supervision/image11.png b/content/database_design/resources/images/dq_android_supervision/image11.png
new file mode 100644
index 0000000..2bc11c7
Binary files /dev/null and b/content/database_design/resources/images/dq_android_supervision/image11.png differ
diff --git a/content/database_design/resources/images/dq_android_supervision/image2.png b/content/database_design/resources/images/dq_android_supervision/image2.png
new file mode 100644
index 0000000..daca8db
Binary files /dev/null and b/content/database_design/resources/images/dq_android_supervision/image2.png differ
diff --git a/content/database_design/resources/images/dq_android_supervision/image3.png b/content/database_design/resources/images/dq_android_supervision/image3.png
new file mode 100644
index 0000000..1fa5173
Binary files /dev/null and b/content/database_design/resources/images/dq_android_supervision/image3.png differ
diff --git a/content/database_design/resources/images/dq_android_supervision/image4.png b/content/database_design/resources/images/dq_android_supervision/image4.png
new file mode 100644
index 0000000..e7b5ebd
Binary files /dev/null and b/content/database_design/resources/images/dq_android_supervision/image4.png differ
diff --git a/content/database_design/resources/images/dq_android_supervision/image5.png b/content/database_design/resources/images/dq_android_supervision/image5.png
new file mode 100644
index 0000000..140cf00
Binary files /dev/null and b/content/database_design/resources/images/dq_android_supervision/image5.png differ
diff --git a/content/database_design/resources/images/dq_android_supervision/image6.png b/content/database_design/resources/images/dq_android_supervision/image6.png
new file mode 100644
index 0000000..e1bbb1d
Binary files /dev/null and b/content/database_design/resources/images/dq_android_supervision/image6.png differ
diff --git a/content/database_design/resources/images/dq_android_supervision/image7.png b/content/database_design/resources/images/dq_android_supervision/image7.png
new file mode 100644
index 0000000..2903f1c
Binary files /dev/null and b/content/database_design/resources/images/dq_android_supervision/image7.png differ
diff --git a/content/database_design/resources/images/dq_android_supervision/image8.png b/content/database_design/resources/images/dq_android_supervision/image8.png
new file mode 100644
index 0000000..229fb6c
Binary files /dev/null and b/content/database_design/resources/images/dq_android_supervision/image8.png differ
diff --git a/content/database_design/resources/images/dq_android_supervision/image9.png b/content/database_design/resources/images/dq_android_supervision/image9.png
new file mode 100644
index 0000000..2aaa729
Binary files /dev/null and b/content/database_design/resources/images/dq_android_supervision/image9.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image1.png b/content/database_design/resources/images/dq_web_supervision/image1.png
new file mode 100644
index 0000000..1ab3476
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image1.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image10.png b/content/database_design/resources/images/dq_web_supervision/image10.png
new file mode 100644
index 0000000..03343e4
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image10.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image100.png b/content/database_design/resources/images/dq_web_supervision/image100.png
new file mode 100644
index 0000000..8d44fa2
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image100.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image101.png b/content/database_design/resources/images/dq_web_supervision/image101.png
new file mode 100644
index 0000000..99b2b39
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image101.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image102.png b/content/database_design/resources/images/dq_web_supervision/image102.png
new file mode 100644
index 0000000..ef3f1aa
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image102.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image103.png b/content/database_design/resources/images/dq_web_supervision/image103.png
new file mode 100644
index 0000000..2883ee7
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image103.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image104.png b/content/database_design/resources/images/dq_web_supervision/image104.png
new file mode 100644
index 0000000..9653326
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image104.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image105.png b/content/database_design/resources/images/dq_web_supervision/image105.png
new file mode 100644
index 0000000..7937194
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image105.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image106.png b/content/database_design/resources/images/dq_web_supervision/image106.png
new file mode 100644
index 0000000..6e405b8
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image106.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image107.png b/content/database_design/resources/images/dq_web_supervision/image107.png
new file mode 100644
index 0000000..c0ec7f5
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image107.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image108.png b/content/database_design/resources/images/dq_web_supervision/image108.png
new file mode 100644
index 0000000..2470720
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image108.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image109.png b/content/database_design/resources/images/dq_web_supervision/image109.png
new file mode 100644
index 0000000..bb161ff
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image109.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image11.png b/content/database_design/resources/images/dq_web_supervision/image11.png
new file mode 100644
index 0000000..144b2c8
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image11.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image110.png b/content/database_design/resources/images/dq_web_supervision/image110.png
new file mode 100644
index 0000000..c36f99f
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image110.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image111.png b/content/database_design/resources/images/dq_web_supervision/image111.png
new file mode 100644
index 0000000..d0784c5
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image111.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image112.png b/content/database_design/resources/images/dq_web_supervision/image112.png
new file mode 100644
index 0000000..a692f24
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image112.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image113.png b/content/database_design/resources/images/dq_web_supervision/image113.png
new file mode 100644
index 0000000..103fbee
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image113.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image114.png b/content/database_design/resources/images/dq_web_supervision/image114.png
new file mode 100644
index 0000000..bd69d6e
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image114.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image115.png b/content/database_design/resources/images/dq_web_supervision/image115.png
new file mode 100644
index 0000000..bebfbcc
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image115.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image116.png b/content/database_design/resources/images/dq_web_supervision/image116.png
new file mode 100644
index 0000000..f50250e
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image116.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image12.png b/content/database_design/resources/images/dq_web_supervision/image12.png
new file mode 100644
index 0000000..0b81f91
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image12.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image13.png b/content/database_design/resources/images/dq_web_supervision/image13.png
new file mode 100644
index 0000000..0f23902
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image13.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image14.png b/content/database_design/resources/images/dq_web_supervision/image14.png
new file mode 100644
index 0000000..663c632
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image14.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image15.png b/content/database_design/resources/images/dq_web_supervision/image15.png
new file mode 100644
index 0000000..860e1d4
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image15.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image16.png b/content/database_design/resources/images/dq_web_supervision/image16.png
new file mode 100644
index 0000000..0b9ca1a
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image16.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image17.png b/content/database_design/resources/images/dq_web_supervision/image17.png
new file mode 100644
index 0000000..1244978
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image17.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image18.png b/content/database_design/resources/images/dq_web_supervision/image18.png
new file mode 100644
index 0000000..74539e7
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image18.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image19.png b/content/database_design/resources/images/dq_web_supervision/image19.png
new file mode 100644
index 0000000..19ce0f1
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image19.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image2.png b/content/database_design/resources/images/dq_web_supervision/image2.png
new file mode 100644
index 0000000..9c3ad28
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image2.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image20.png b/content/database_design/resources/images/dq_web_supervision/image20.png
new file mode 100644
index 0000000..592bac3
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image20.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image21.png b/content/database_design/resources/images/dq_web_supervision/image21.png
new file mode 100644
index 0000000..0f8f802
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image21.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image22.png b/content/database_design/resources/images/dq_web_supervision/image22.png
new file mode 100644
index 0000000..b1fdc34
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image22.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image23.png b/content/database_design/resources/images/dq_web_supervision/image23.png
new file mode 100644
index 0000000..5fcee5a
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image23.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image24.png b/content/database_design/resources/images/dq_web_supervision/image24.png
new file mode 100644
index 0000000..057d2e2
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image24.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image25.png b/content/database_design/resources/images/dq_web_supervision/image25.png
new file mode 100644
index 0000000..b12c1ce
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image25.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image26.png b/content/database_design/resources/images/dq_web_supervision/image26.png
new file mode 100644
index 0000000..92b79b5
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image26.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image27.png b/content/database_design/resources/images/dq_web_supervision/image27.png
new file mode 100644
index 0000000..741efe2
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image27.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image28.png b/content/database_design/resources/images/dq_web_supervision/image28.png
new file mode 100644
index 0000000..ff95445
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image28.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image3.png b/content/database_design/resources/images/dq_web_supervision/image3.png
new file mode 100644
index 0000000..d1cb971
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image3.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image30.png b/content/database_design/resources/images/dq_web_supervision/image30.png
new file mode 100644
index 0000000..a64476f
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image30.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image31.png b/content/database_design/resources/images/dq_web_supervision/image31.png
new file mode 100644
index 0000000..5cb3453
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image31.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image32.png b/content/database_design/resources/images/dq_web_supervision/image32.png
new file mode 100644
index 0000000..116d4dd
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image32.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image33.png b/content/database_design/resources/images/dq_web_supervision/image33.png
new file mode 100644
index 0000000..4773a61
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image33.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image34.png b/content/database_design/resources/images/dq_web_supervision/image34.png
new file mode 100644
index 0000000..1cba165
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image34.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image35.png b/content/database_design/resources/images/dq_web_supervision/image35.png
new file mode 100644
index 0000000..3e9be8f
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image35.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image36.png b/content/database_design/resources/images/dq_web_supervision/image36.png
new file mode 100644
index 0000000..dcf53f0
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image36.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image37.png b/content/database_design/resources/images/dq_web_supervision/image37.png
new file mode 100644
index 0000000..712f2be
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image37.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image38.png b/content/database_design/resources/images/dq_web_supervision/image38.png
new file mode 100644
index 0000000..be3de58
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image38.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image39.png b/content/database_design/resources/images/dq_web_supervision/image39.png
new file mode 100644
index 0000000..295c7cb
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image39.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image4.png b/content/database_design/resources/images/dq_web_supervision/image4.png
new file mode 100644
index 0000000..3bdaf19
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image4.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image40.png b/content/database_design/resources/images/dq_web_supervision/image40.png
new file mode 100644
index 0000000..2caf0a0
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image40.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image41.png b/content/database_design/resources/images/dq_web_supervision/image41.png
new file mode 100644
index 0000000..91c40f2
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image41.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image42.png b/content/database_design/resources/images/dq_web_supervision/image42.png
new file mode 100644
index 0000000..04f2f7d
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image42.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image43.png b/content/database_design/resources/images/dq_web_supervision/image43.png
new file mode 100644
index 0000000..51e54c6
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image43.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image44.png b/content/database_design/resources/images/dq_web_supervision/image44.png
new file mode 100644
index 0000000..e0999ef
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image44.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image45.png b/content/database_design/resources/images/dq_web_supervision/image45.png
new file mode 100644
index 0000000..011f246
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image45.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image46.png b/content/database_design/resources/images/dq_web_supervision/image46.png
new file mode 100644
index 0000000..e3c9ec7
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image46.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image47.png b/content/database_design/resources/images/dq_web_supervision/image47.png
new file mode 100644
index 0000000..5cf7866
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image47.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image48.png b/content/database_design/resources/images/dq_web_supervision/image48.png
new file mode 100644
index 0000000..8e573c0
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image48.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image49.png b/content/database_design/resources/images/dq_web_supervision/image49.png
new file mode 100644
index 0000000..a69c1e4
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image49.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image5.png b/content/database_design/resources/images/dq_web_supervision/image5.png
new file mode 100644
index 0000000..cd9f4f0
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image5.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image50.png b/content/database_design/resources/images/dq_web_supervision/image50.png
new file mode 100644
index 0000000..aab9c79
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image50.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image53.png b/content/database_design/resources/images/dq_web_supervision/image53.png
new file mode 100644
index 0000000..c686cea
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image53.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image6.png b/content/database_design/resources/images/dq_web_supervision/image6.png
new file mode 100644
index 0000000..79ad299
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image6.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image60.png b/content/database_design/resources/images/dq_web_supervision/image60.png
new file mode 100644
index 0000000..e0f0d4d
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image60.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image61.png b/content/database_design/resources/images/dq_web_supervision/image61.png
new file mode 100644
index 0000000..65642c0
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image61.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image63.png b/content/database_design/resources/images/dq_web_supervision/image63.png
new file mode 100644
index 0000000..5ee56e5
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image63.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image64.png b/content/database_design/resources/images/dq_web_supervision/image64.png
new file mode 100644
index 0000000..4982536
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image64.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image65.png b/content/database_design/resources/images/dq_web_supervision/image65.png
new file mode 100644
index 0000000..c10779f
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image65.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image66.png b/content/database_design/resources/images/dq_web_supervision/image66.png
new file mode 100644
index 0000000..7520b62
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image66.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image67.png b/content/database_design/resources/images/dq_web_supervision/image67.png
new file mode 100644
index 0000000..7cc5207
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image67.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image68.png b/content/database_design/resources/images/dq_web_supervision/image68.png
new file mode 100644
index 0000000..53fe254
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image68.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image69.png b/content/database_design/resources/images/dq_web_supervision/image69.png
new file mode 100644
index 0000000..f9992fe
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image69.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image7.png b/content/database_design/resources/images/dq_web_supervision/image7.png
new file mode 100644
index 0000000..39d93cb
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image7.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image70.png b/content/database_design/resources/images/dq_web_supervision/image70.png
new file mode 100644
index 0000000..645e41f
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image70.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image71.png b/content/database_design/resources/images/dq_web_supervision/image71.png
new file mode 100644
index 0000000..a801875
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image71.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image72.png b/content/database_design/resources/images/dq_web_supervision/image72.png
new file mode 100644
index 0000000..94a7cbc
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image72.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image73.png b/content/database_design/resources/images/dq_web_supervision/image73.png
new file mode 100644
index 0000000..257ed24
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image73.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image74.png b/content/database_design/resources/images/dq_web_supervision/image74.png
new file mode 100644
index 0000000..16e624a
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image74.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image78.png b/content/database_design/resources/images/dq_web_supervision/image78.png
new file mode 100644
index 0000000..79f078e
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image78.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image8.png b/content/database_design/resources/images/dq_web_supervision/image8.png
new file mode 100644
index 0000000..f5e71b4
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image8.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image84.png b/content/database_design/resources/images/dq_web_supervision/image84.png
new file mode 100644
index 0000000..7c9a43e
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image84.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image85.png b/content/database_design/resources/images/dq_web_supervision/image85.png
new file mode 100644
index 0000000..899bb2e
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image85.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image86.png b/content/database_design/resources/images/dq_web_supervision/image86.png
new file mode 100644
index 0000000..b6b2078
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image86.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image87.png b/content/database_design/resources/images/dq_web_supervision/image87.png
new file mode 100644
index 0000000..a248d28
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image87.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image88.png b/content/database_design/resources/images/dq_web_supervision/image88.png
new file mode 100644
index 0000000..5bd1b9d
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image88.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image89.png b/content/database_design/resources/images/dq_web_supervision/image89.png
new file mode 100644
index 0000000..aceb1f1
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image89.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image9.png b/content/database_design/resources/images/dq_web_supervision/image9.png
new file mode 100644
index 0000000..d5b600d
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image9.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image90.png b/content/database_design/resources/images/dq_web_supervision/image90.png
new file mode 100644
index 0000000..8c6588f
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image90.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image91.png b/content/database_design/resources/images/dq_web_supervision/image91.png
new file mode 100644
index 0000000..a7bd5aa
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image91.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image92.png b/content/database_design/resources/images/dq_web_supervision/image92.png
new file mode 100644
index 0000000..2d6fde5
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image92.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image93.png b/content/database_design/resources/images/dq_web_supervision/image93.png
new file mode 100644
index 0000000..56bb6ea
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image93.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image94.png b/content/database_design/resources/images/dq_web_supervision/image94.png
new file mode 100644
index 0000000..4104af9
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image94.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image95.png b/content/database_design/resources/images/dq_web_supervision/image95.png
new file mode 100644
index 0000000..706b2b0
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image95.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image96.png b/content/database_design/resources/images/dq_web_supervision/image96.png
new file mode 100644
index 0000000..c944c97
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image96.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image97.png b/content/database_design/resources/images/dq_web_supervision/image97.png
new file mode 100644
index 0000000..37384f5
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image97.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image98.png b/content/database_design/resources/images/dq_web_supervision/image98.png
new file mode 100644
index 0000000..307c694
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image98.png differ
diff --git a/content/database_design/resources/images/dq_web_supervision/image99.png b/content/database_design/resources/images/dq_web_supervision/image99.png
new file mode 100644
index 0000000..df6bdb6
Binary files /dev/null and b/content/database_design/resources/images/dq_web_supervision/image99.png differ
diff --git a/content/database_design/resources/images/image29.png b/content/database_design/resources/images/image29.png
new file mode 100644
index 0000000..da5d0ba
Binary files /dev/null and b/content/database_design/resources/images/image29.png differ
diff --git a/content/database_design/resources/images/image51.png b/content/database_design/resources/images/image51.png
new file mode 100644
index 0000000..d9162cc
Binary files /dev/null and b/content/database_design/resources/images/image51.png differ
diff --git a/content/database_design/resources/images/image52.png b/content/database_design/resources/images/image52.png
new file mode 100644
index 0000000..47b3714
Binary files /dev/null and b/content/database_design/resources/images/image52.png differ
diff --git a/content/database_design/resources/images/image54.png b/content/database_design/resources/images/image54.png
new file mode 100644
index 0000000..a6051fa
Binary files /dev/null and b/content/database_design/resources/images/image54.png differ
diff --git a/content/database_design/resources/images/image55.png b/content/database_design/resources/images/image55.png
new file mode 100644
index 0000000..471c62b
Binary files /dev/null and b/content/database_design/resources/images/image55.png differ
diff --git a/content/database_design/resources/images/image56.png b/content/database_design/resources/images/image56.png
new file mode 100644
index 0000000..e75264b
Binary files /dev/null and b/content/database_design/resources/images/image56.png differ
diff --git a/content/database_design/resources/images/image57.png b/content/database_design/resources/images/image57.png
new file mode 100644
index 0000000..e6519cf
Binary files /dev/null and b/content/database_design/resources/images/image57.png differ
diff --git a/content/database_design/resources/images/image58.png b/content/database_design/resources/images/image58.png
new file mode 100644
index 0000000..34dff33
Binary files /dev/null and b/content/database_design/resources/images/image58.png differ
diff --git a/content/database_design/resources/images/image59.png b/content/database_design/resources/images/image59.png
new file mode 100644
index 0000000..1903b6c
Binary files /dev/null and b/content/database_design/resources/images/image59.png differ
diff --git a/content/database_design/resources/images/image60.png b/content/database_design/resources/images/image60.png
new file mode 100644
index 0000000..fa7a8ea
Binary files /dev/null and b/content/database_design/resources/images/image60.png differ
diff --git a/content/database_design/resources/images/image61.png b/content/database_design/resources/images/image61.png
new file mode 100644
index 0000000..2fa6003
Binary files /dev/null and b/content/database_design/resources/images/image61.png differ
diff --git a/content/database_design/resources/images/image62.png b/content/database_design/resources/images/image62.png
new file mode 100644
index 0000000..b95dca0
Binary files /dev/null and b/content/database_design/resources/images/image62.png differ
diff --git a/content/database_design/resources/images/image63.png b/content/database_design/resources/images/image63.png
new file mode 100644
index 0000000..194090c
Binary files /dev/null and b/content/database_design/resources/images/image63.png differ
diff --git a/content/database_design/resources/images/image64.png b/content/database_design/resources/images/image64.png
new file mode 100644
index 0000000..8bf9067
Binary files /dev/null and b/content/database_design/resources/images/image64.png differ
diff --git a/content/database_design/resources/images/image65.png b/content/database_design/resources/images/image65.png
new file mode 100644
index 0000000..d97357f
Binary files /dev/null and b/content/database_design/resources/images/image65.png differ
diff --git a/content/database_design/resources/images/image66.png b/content/database_design/resources/images/image66.png
new file mode 100644
index 0000000..d1d6ad4
Binary files /dev/null and b/content/database_design/resources/images/image66.png differ
diff --git a/content/database_design/resources/images/image67.png b/content/database_design/resources/images/image67.png
new file mode 100644
index 0000000..0888658
Binary files /dev/null and b/content/database_design/resources/images/image67.png differ
diff --git a/content/database_design/resources/images/image68.png b/content/database_design/resources/images/image68.png
new file mode 100644
index 0000000..750ff76
Binary files /dev/null and b/content/database_design/resources/images/image68.png differ
diff --git a/content/database_design/resources/images/image69.png b/content/database_design/resources/images/image69.png
new file mode 100644
index 0000000..583e5ea
Binary files /dev/null and b/content/database_design/resources/images/image69.png differ
diff --git a/content/database_design/resources/images/image70.png b/content/database_design/resources/images/image70.png
new file mode 100644
index 0000000..85c5e46
Binary files /dev/null and b/content/database_design/resources/images/image70.png differ
diff --git a/content/database_design/resources/images/image71.png b/content/database_design/resources/images/image71.png
new file mode 100644
index 0000000..b2284dc
Binary files /dev/null and b/content/database_design/resources/images/image71.png differ
diff --git a/content/database_design/resources/images/image72.png b/content/database_design/resources/images/image72.png
new file mode 100644
index 0000000..dfd927f
Binary files /dev/null and b/content/database_design/resources/images/image72.png differ
diff --git a/content/database_design/resources/images/image73.png b/content/database_design/resources/images/image73.png
new file mode 100644
index 0000000..47da604
Binary files /dev/null and b/content/database_design/resources/images/image73.png differ
diff --git a/content/database_design/resources/images/image74.png b/content/database_design/resources/images/image74.png
new file mode 100644
index 0000000..854051e
Binary files /dev/null and b/content/database_design/resources/images/image74.png differ
diff --git a/content/database_design/resources/images/image75.png b/content/database_design/resources/images/image75.png
new file mode 100644
index 0000000..1b4eacb
Binary files /dev/null and b/content/database_design/resources/images/image75.png differ
diff --git a/content/database_design/resources/images/image76.png b/content/database_design/resources/images/image76.png
new file mode 100644
index 0000000..87f58d7
Binary files /dev/null and b/content/database_design/resources/images/image76.png differ
diff --git a/content/database_design/resources/images/image77.png b/content/database_design/resources/images/image77.png
new file mode 100644
index 0000000..9568fe4
Binary files /dev/null and b/content/database_design/resources/images/image77.png differ
diff --git a/content/database_design/resources/images/image78.jpg b/content/database_design/resources/images/image78.jpg
new file mode 100644
index 0000000..e0c2301
Binary files /dev/null and b/content/database_design/resources/images/image78.jpg differ
diff --git a/content/database_design/resources/images/image78.png b/content/database_design/resources/images/image78.png
new file mode 100644
index 0000000..838bbea
Binary files /dev/null and b/content/database_design/resources/images/image78.png differ