A manufacturing integration should be reviewed as a data path, not as a marketing promise. AutoOps AI connects to SAP ECC or S/4HANA through OData, keeps credentials on the server, and separates scheduled reads from optional write-back. The checklist below explains what the current implementation does and what an IT team should verify for its own landscape.
1. Confirm the read scope
The current pull covers work orders, BOM components, routing operations, quality notifications, and production confirmations. Verify the exact OData services, service user permissions, plant filters, and expected record volume in a non-production or restricted environment before broadening access.
2. Review authentication and secret storage
AutoOps supports HTTP Basic and OAuth 2.0 client credentials. Credentials are encrypted at rest with AES-256-GCM using a server-side encryption key, decrypted only when a sync or write-back request needs them, and are not returned through the application API. IT should still apply its own credential rotation, service-account, and network policies.
3. Test runtime behavior
- Confirm the configured SAP base URL, certificate chain, and proxy path from the deployed server.
- Exercise timeouts and an unavailable endpoint; requests have a hard timeout and scheduled work is isolated per integration.
- Check sync timestamps and row counts after the first pull instead of assuming a successful login means complete data.
- Review application logs and audit entries without placing credentials or sensitive payloads in operational logs.
4. Treat write-back as a separate decision
Quality-notification write-back is unavailable until an SAP integration is configured. Once it is, any signed-in member of the organization can file one and it is sent on submission — there is no approval queue and no per-organization switch to disable it. Requests carry idempotency keys, retry backoff, a dead-letter state, and audit records. Idempotency and the audit trail reduce operational risk; they do not replace SAP authorization design, change control, or reconciliation testing. Constrain what the integration user is permitted to do in SAP itself.
5. Define acceptance evidence
- Permission evidenceDocument the service user's allowed entities and operations.
- Data evidenceCompare a bounded sample of cached records with the SAP source.
- Failure evidenceDemonstrate timeout, retry, and dead-letter behavior using safe test cases.
- Recovery evidenceConfirm credential rotation and a manual re-sync procedure.