Skip to content
Annatech_

Intelligent Automation

Automation that survives production, not just the demo

Unattended UiPath and Pega systems for SAP-centric operations. Queue-driven, exception-safe, audit-trailed - designed by an architect who has watched robots run at 50,000 documents a year and knows exactly where they break.

Reference scale

What production means here

documents a year through a single unattended process
50,000+
SAP transactions automated across processes (IH08, IE03, CV01N, MM02, ME21N, IW21, IW22)
7
Pega rules architected across 8 business domains
1,500+
fewer MFA cycles after re-architecting authentication
~80%

Capabilities

Where this practice earns its keep

SAP GUI automation, done properly

Equipment lookups, document management, material master, purchase orders, service notifications - automated through the GUI when no API exists, with selector strategies and session handling that hold up under queue load. Transaction codes are not trivia to us; they are the working surface.

Framework architecture

REFramework state machines with disciplined contracts: dictionary-based data flow, standard sub-workflow signatures, business versus system exception taxonomy, trace-level logging on every decision. The structure that lets a process scale from one robot to a fleet.

Pega case management

Case design, flows, decisioning and integrations on Pega 8.x - 1,500+ rules architected across eight business domains, including a dual-jurisdiction export-control module. Plus a standardized offline branch-review methodology that keeps quality consistent as the platform grows.

Constraint engineering

MFA on an unattended robot. OCR on twenty-year-old scan quality. Systems of record you may not touch outside a change window. The interesting problems live in the constraints, and re-architecting around them - without security exceptions - is a specialty, not an annoyance.

Reference architecture

What a production process actually looks like

The two-phase certificate flow, as delivered: equipment resolution, verification and filing - queue-driven and audit-trailed end to end.

PHASE 1 - EQUIPMENT RESOLUTION PHASE 2 - VERIFY AND FILE ServiceNow intake certificate + serial no. Orchestrator queue transaction-scoped retry Robot: SAP IH08 serial -> equipment REST result back Normalize PDF document class rules SAP IE03 verify serial + plant check SAP CV01N create dynamic doc type/part DMS audit trail equipment resolved - ServiceNow triggers phase 2 ~50,000 documents/yr - every decision logged
Two-phase certificate intake into SAP DMS, orchestrated with ServiceNow.
orchestrator queue — transaction lifecycle
12:41:03 TRACE GetTransactionData      queue item acquired · reference CERT-…-4812
12:41:07 TRACE IH08.Lookup             serial resolved -> equipment record
12:41:19 WARN  CV01N.Attach            SAP GUI busy — app exception, retry 1/2
12:41:36 TRACE CV01N.Attach            document created · type/part set per class
12:41:38 INFO  SetTransactionStatus    Success · full decision log persisted
12:41:41 TRACE GetTransactionData      next item…
--------
business rule miss   -> BusinessRuleException -> human review queue (no retry)
application failure  -> retry x2, then exception queue with screenshots + logs

Illustrative trace. Retry semantics, exception split and audit logging are exactly as delivered.

Method

Delivery lifecycle

  1. 01

    Scope and rules

    Sitting with the subject-matter experts: AS-IS process, business rules, every variation mapped before a line is built.

  2. 02

    Architecture

    Queue design, state machine, exception taxonomy, credential flow - the technical blueprint that survives production.

  3. 03

    Build and verify

    Framework-based implementation, static validation, unattended test runs against every documented edge case.

  4. 04

    Hypercare and handover

    Production monitoring, log scrutiny, tuning - then a documented, maintainable system your team owns.

Evidence

Case studies from this practice

Have a process that should not need people?

Describe the process and its constraints - volumes, systems, what has already been tried. You will get an architectural assessment, not a slide deck.