• Design, build, test, maintain, and optimize Workday reports, particularly Advanced, Matrix, and Composite reports, together with calculated fields, Worksheets, dashboards, discovery boards, and other applicable reporting capabilities.
• Apply strong knowledge of the Workday data model, including business objects, related business objects, report data sources, indexed data sources, filters, single- and multi-instance relationships, calculated-field dependencies, and relationships between HCM and Financial Management data.
• Administer report prompts, formatting, sharing, scheduling, delivery, performance, and approved security behavior; tailor delivered reports where appropriate.
• Maintain the report catalogue and carry out approved ownership, consolidation, rationalization, disablement, and retirement activities under section 3.6.

3.3 Workday Integrations

• Design, build, test, deploy, and support EIB, Core Connector, Cloud Connect, Document Transformation, RaaS, and REST/SOAP web-service solutions.
• Develop and troubleshoot XML, XSLT, JSON, transformation logic, integration maps and attributes, launch parameters, transport configuration, PGP settings, and file conventions.
• Monitor scheduled integrations daily; resolve failures and discrepancies; implement reconciliation, data-quality, root-cause, corrective, and preventive controls; and maintain operational documentation.
• Specify integration security, credential, key, certificate, and transport requirements and implement integrations within configuration approved and provided by the Workday Security team.
• Deliver curated Workday data to PAHO’s corporate data and analytics platform through approved extracts, RaaS endpoints, connectors, or web services, ensuring that outputs are reconciled, appropriately secured, efficient, and documented.
• Migrate reports, integrations, and configuration between tenants using approved promotion procedures.

3.4 Security Operating Model

• Identify and specify the security needed for assigned reports, data sources, calculated fields, Worksheets, dashboards, and integrations, including least privilege, segregation of duties, ISU/ISSG, domain-access, credential, certificate, key, and transport requirements.
• Configure integrations to use items approved and issued by the Workday Security team, which retains issuance, custody, and rotation of integration credentials, certificates, and encryption keys. The consultant does not generate, retain, or exchange secret material unless specifically delegated in writing.
• Do not create, modify, or assign security groups, domain policies, or business-process security policies unless a specific task is explicitly delegated and approved by the Workday Security team.
• Validate approved security behavior and report access failures, over-permissioning, unintended exposure, expiry risks, or changed data-access requirements promptly.
• Process PAHO information, including personal, payroll, medical, financial, confidential, or tenant-derived data, only through PAHO-approved platforms. Such information shall not be entered into public or unapproved AI services, and any AI-assisted output used in PAHO work remains subject to consultant review, validation, confidentiality, and human accountability.
• Maintain audit evidence for report and integration changes, and engage the ITS Information Security unit on security incidents, information classification, credential and certificate handling, and integrations transmitting PAHO data outside the tenant.

3.5 Operations, Releases, and Improvement

• Provide first-line support for the reporting and integration layer; coordinate Workday Support and AMS cases; and retain responsibility for specification, review, testing, acceptance, and documentation of escalated outcomes.
• Escalate work to the AMS partner where it exceeds available capacity against agreed priorities, requires capability outside the contracted scope, requires access the consultant does not hold, or is on the critical path for payroll or a financial deadline where reliance on one resource presents unacceptable risk. Escalation outside these criteria requires Supervisor approval.
• Assess Workday release impacts, execute assigned risk-based Sandbox Preview regression testing within PMIS cycle timeframes, address identified defects, monitor API and feature deprecations, and support tenant refresh validation.
• Establish a prioritized baseline of reports and integrations recording inventory, purpose, owner, data sources, calculated-field dependencies, approved security, schedules, downstream consumers, procedures, current run success, recurring failure patterns, and report-performance issues.
• Identify risks, technical debt, performance issues, duplication, and automation opportunities with estimated effort, benefit, risk, and dependency, and implement only work approved and prioritized by the Supervisor. Unprioritized findings remain recorded for future consideration and do not become open-ended obligations.
• Identify and propose practical automation and AI-assisted improvements to reporting, documentation, testing, reconciliation, and operational support for evaluation and prioritization by the Supervisor.

3.6 Report Catalogue Rationalization

• Business-critical objects are designated under an existing PAHO classification or, where none applies, during the baseline and approved by the Supervisor. Payroll, financial close, statutory or external reporting, regulatory submission, downstream-system dependency, and external-party impact inform the designation.
• Analyse the complete catalogue at inventory level and provide detailed dependency review and proposed disposition for the Supervisor-approved rationalization scope, prioritizing business-critical, never-used, orphaned, duplicated, and superseded reports. Categories comprise: never run since creation and created more than twelve months previously; owner or last user departed more than twelve months previously with no subsequent use; historically used but not run within the previous twelve months; and duplicated or superseded reports.
• Before proposing retirement, check dashboard and worklet placement, sharing, scheduled delivery, sub-report use, use as another report’s data source, and RaaS or integration consumption. An unresolved dependency prevents retirement.
• Propose a disposition of retain, reassign, consolidate, disable or retire, or defer for further review. Never-used reports and unused reports whose owner departed may be proposed for retirement without owner confirmation where no dependency exists. Historically used, duplicated, or superseded reports require responsible-business-area confirmation, because annual, statutory, and audit cycles may not appear in recent usage.
• Execute retirements by disposition list approved by the Supervisor. Identified affected owners receive thirty days’ notice; approved reports are disabled rather than immediately deleted; and deletion may occur after a further sixty-day quiet period without objection, including after the consultancy where PAHO assumes the scheduled action.
• Record reinstatements with the reason. Reinstatement is a permitted outcome before reports are deleted; the control target is zero reports disabled or retired without approved disposition, completed dependency check, and required notice.

3.