...
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
📜 Process 📜 Process Overview
The Oriel-TIS integration entails manual data handling across diverse local offices, with discrepancies in practices leading to inefficiencies. Attempts at process streamlining and automation varies by region, and the manual mapping to TIS is a significant challenge.
...
The integration is characterized by the extraction and processing of reports, with noted pain points including access constraints, manual record creation, and TIS template user-unfriendliness. Data mapping and accuracy are hampered by inconsistencies in terminologies and data structure changes.
😤 Pain Points
Manual processes: Manual data entry and upload to TIS are prone to errors and inefficient
Complicated data mapping: Discrepancies in data language, terminology, and field structure between Oriel and TIS complicate direct mapping. Data integrity comes into question
Absence of direct data mapping: Lack of direct data mapping between Oriel and TIS, particularly for post and programme details causes high manual workload, leading to delayed or near-deadline processing
Data mapping disruptions: Changes in Oriel's field structure over time create data mapping iconsistencies
Access to data: Limited superuser privileges in Oriel creates bottlenecks
Template Unfriendliness: TIS templates are not user-friendly, hindering the record creation process
Data quality: Data integrity is threatened by manual processing and misaligned terminologies
📈 Options For Improvement
Do nothing: maintain status quo. Not very nice!
Enhanced ETL: Improving ETL processes to efficiently handle and store Oriel data in a query-able format for easy querying. Create subset of relevant data for TIS, enriched with timestamps for change tracking.
Data mapping: Developing automated mapping tools to reduce manual data handling.
Data integration: Developing a more robust data integration process to ensure that programme and curriculum details are accurately mapped from Oriel to TIS.
Integrated Process/System Development: Using Oriel procurement to create a more integrated system for data flow between Oriel and TIS.
Tableau integration: Exploring the use of Tableau for data management and quality tracking. Using Tableau to automate data splitting for different audiences and to create reports to map Oriel data to TIS bulk upload format, identify and track upload issues, and data quality
Alignment: Aligning Lists of Values (LoV) to minimize manual data matching efforts, by ensuring Oriel and TIS use the same lists of values for fields.
Standardization: Standardizing program names and numbers across systems for better alignment.
Automation: Implementing full or semi-automated data ingestion from Oriel to TIS. This can streamline the process and reduce manual errors.
...