Skip to content
Established in 2008Cairo, Egypt
Flags of Arab countries
الاتحاد العربي لتنمية الموارد البشريةArab Union for Human Resources DevelopmentVisitor Register
Programme profile

Controlling data ingestion during source delays or duplicate events and testing record completeness

Programme code: U27-S26-T01-P002

An applied programme in Artificial Intelligence and Data, connecting specialist learning with a reviewable work pack.

Information to help you choose

Dates
2027-01-10 — 2027-01-14
Venue
Cairo — Arab Union for Human Resources Development headquarters
Programme fee
USD 600
Duration
One week · 5 training days
Delivery language
Arabic — English delivery is available by agreement
Delivery mode
In person
Training hours
25 training hours

Submitting a request does not confirm a place or booking. The administration will review availability, dates and arrangements.

The programme fee includes

  • Training
  • Training materials
  • Certificate
  • Session breaks
  • Lunch
  • Airport arrival and departure transfers

The advertised fee is the total amount payable by the participant. No additional fees are charged.

Request an invoice or official quotation — Include the programme name or number in your request.

Certificate of completion of the programme, workshop or training course

The participant receives a certificate of completion of the programme, workshop or training course issued by Arab Union for Human Resources Development. The certificate is awarded on the basis of attendance.

A programme in Artificial Intelligence and Data / Data Pipeline Engineering and Advanced Analytics in the UHRDA 2027 Plan.

Programme brochure

Controlling data ingestion during source delays or duplicate events and testing record completeness

Introduction

The programme “Controlling data ingestion during source delays or duplicate events and testing record completeness” addresses a professional task within Artificial Intelligence and Data, connecting the subject with case data, user requirements and the expected deliverable. Participants define the question and scope of responsibility, then select the evidence needed to assess the situation, compare options and prepare a reviewable practical deliverable.

Learning progresses from data requirements and sources to data pipeline design, connecting analysis with selection, verification and follow-up. Participants develop an application pack for “Controlling data ingestion during source delays or duplicate events and testing record completeness” containing the case definition, inputs, alternatives and review findings, with the assumptions, constraints and responsibilities that determine whether the recommendation is suitable.

The approach combines concepts, review of training documents and data, decision exercises and presentation of findings. Examples are adapted to participant experience, with a clear distinction between classroom learning and workplace execution under the relevant professional authorisations and approved institutional procedures.

Objectives

  1. Define the scope of “Controlling data ingestion during source delays or duplicate events and testing record completeness”, its expected result, its users and its acceptance criteria.
  2. Organise data for data requirements and sources and assess its sources, completeness and limits of use.
  3. Apply data pipeline design and connect it with the programme task and its professional constraints.
  4. Analyse alternatives through data quality and reproducibility, explaining the selected option, its risks and its requirements.
  5. Define verification evidence for analysis and result presentation, review points and matters requiring escalation.
  6. Prepare a follow-up plan for pipeline operation and monitoring with responsibilities, indicators and reassessment triggers.

Programme topics

Learning area 1: Data requirements and sources

  1. Define data requirements and sources and its scope, explaining how it relates to the professional task and the required case result.
  2. Review analytical question, identifying sources, units and reference periods and recording gaps and conflicts before using the information.
  3. Analyse data boundaries using case documents and data, distinguishing direct measurements from estimates and assumptions and discussing their effects on the decision.
  4. Compare options for data requirements and sources against requirements, resources and dependencies, documenting why an option is appropriate and the limitations affecting its use.
  5. Prepare a checklist linking evidence for analytical question and data boundaries, identifying the reviewer, acceptance criterion and action needed when a condition is not met.
  6. Apply this learning area to the “Controlling data ingestion during source delays or duplicate events and testing record completeness” exercise and update the work pack with documented inputs, analysis and observations to carry forward to the next learning area.

Learning area 2: Data pipeline design

  1. Define data pipeline design and its scope, explaining how it relates to the professional task and the required case result.
  2. Review transformation stages, identifying sources, units and reference periods and recording gaps and conflicts before using the information.
  3. Analyse pipeline dependencies using case documents and data, distinguishing direct measurements from estimates and assumptions and discussing their effects on the decision.
  4. Compare options for data pipeline design against requirements, resources and dependencies, documenting why an option is appropriate and the limitations affecting its use.
  5. Prepare a checklist linking evidence for transformation stages and pipeline dependencies, identifying the reviewer, acceptance criterion and action needed when a condition is not met.
  6. Apply this learning area to the “Controlling data ingestion during source delays or duplicate events and testing record completeness” exercise and update the work pack with documented inputs, analysis and observations to carry forward to the next learning area.

Learning area 3: Data quality and reproducibility

  1. Define data quality and reproducibility and its scope, explaining how it relates to the professional task and the required case result.
  2. Review quality rules, identifying sources, units and reference periods and recording gaps and conflicts before using the information.
  3. Analyse transformation log using case documents and data, distinguishing direct measurements from estimates and assumptions and discussing their effects on the decision.
  4. Compare options for data quality and reproducibility against requirements, resources and dependencies, documenting why an option is appropriate and the limitations affecting its use.
  5. Prepare a checklist linking evidence for quality rules and transformation log, identifying the reviewer, acceptance criterion and action needed when a condition is not met.
  6. Apply this learning area to the “Controlling data ingestion during source delays or duplicate events and testing record completeness” exercise and update the work pack with documented inputs, analysis and observations to carry forward to the next learning area.

Learning area 4: Analysis and result presentation

  1. Define analysis and result presentation and its scope, explaining how it relates to the professional task and the required case result.
  2. Review method selection, identifying sources, units and reference periods and recording gaps and conflicts before using the information.
  3. Analyse result interpretation using case documents and data, distinguishing direct measurements from estimates and assumptions and discussing their effects on the decision.
  4. Compare options for analysis and result presentation against requirements, resources and dependencies, documenting why an option is appropriate and the limitations affecting its use.
  5. Prepare a checklist linking evidence for method selection and result interpretation, identifying the reviewer, acceptance criterion and action needed when a condition is not met.
  6. Apply this learning area to the “Controlling data ingestion during source delays or duplicate events and testing record completeness” exercise and update the work pack with documented inputs, analysis and observations to carry forward to the next learning area.

Learning area 5: Pipeline operation and monitoring

  1. Define pipeline operation and monitoring and its scope, explaining how it relates to the professional task and the required case result.
  2. Review reliability indicators, identifying sources, units and reference periods and recording gaps and conflicts before using the information.
  3. Analyse exception handling using case documents and data, distinguishing direct measurements from estimates and assumptions and discussing their effects on the decision.
  4. Compare options for pipeline operation and monitoring against requirements, resources and dependencies, documenting why an option is appropriate and the limitations affecting its use.
  5. Prepare a checklist linking evidence for reliability indicators and exception handling, identifying the reviewer, acceptance criterion and action needed when a condition is not met.
  6. Apply this learning area to the “Controlling data ingestion during source delays or duplicate events and testing record completeness” exercise and update the work pack with documented inputs, analysis and observations to carry forward to the next learning area.

Outputs

  1. An integrated application pack for “Controlling data ingestion during source delays or duplicate events and testing record completeness” showing the path from the professional question to the finding and recommendation.
  2. An input, assumption and gap register with information sources and verification owners.
  3. A documented analysis of case alternatives linking data pipeline design with execution and resource requirements.
  4. A professional checklist defining acceptance criteria, review points and closure evidence.
  5. An action plan identifying priority, owner, due date, follow-up indicator and dependencies.
  6. A final presentation of findings, limitations, open questions and requirements for institutional application.

Who should attend

  1. Specialists, supervisors and work coordinators in Artificial Intelligence and Data whose responsibilities relate to the programme subject.
  2. Team leaders, work coordinators and reviewers who assess deliverables and coordinate disciplines.
  3. Practitioners preparing for broader responsibilities in the discipline who have basic familiarity with the work context.

Participation requirements and delivery methodology

  1. Basic subject knowledge or professional experience sufficient to understand the terminology and case documents.
  2. Use non-confidential training data; participant examples may be discussed after removing identifiers and information not authorised for sharing.
  3. Interactive explanations, individual and group exercises, case analysis, peer review and presentation of applied work.
  4. Assess progress through input quality, analytical reasoning, deliverable clarity and responses to review comments.
  5. Programme duration: five training days and twenty-five training hours.
  6. Delivery in Cairo at UHRDA headquarters in Arabic; English delivery is available by agreement.

Conclusion

The programme “Controlling data ingestion during source delays or duplicate events and testing record completeness” concludes with a practical pack connecting specialist knowledge with evidence, alternatives and responsibilities. Progress is demonstrated by the participant’s ability to explain choices, document their limits and produce work that users and reviewers can understand and follow up.

Applying this approach in the organisation supports better questions, stronger information and clearer team coordination. Workplace application is planned around the asset or service, available data and review requirements, with impact monitoring and updates when conditions change.

Request participationProgramme participation requestArab Union for Human Resources Development
Programme

Controlling data ingestion during source delays or duplicate events and testing record completeness

Dates: 2027-01-10 — 2027-01-14

Submitting a request does not confirm a place or booking. The administration will review availability, dates and arrangements.

7–15 digits. Include the country code for international contact.

Your request is saved in the visitor database and a copy is directed to [email protected].

The Union administration reviews your request and contacts you to confirm availability, dates and arrangements. Submitting a request is not final confirmation of participation.

We use the name, job title, employer, country, contact information and participation details you provide to process this request and contact you. Records are retained permanently under Union policy. You may contact the administration to request access, correction or review of a deletion request. Details and contact preferences

How do we use your information?

Your request is submitted when a save confirmation and reference number appear. The result shows the email notification status; saving the request or acceptance by the mail server does not prove inbox delivery. A request does not confirm participation, a price or a booking before the administration replies. The Union team will contact you to follow up.

← Back to the 2027 plan