JD - Integration architect from utility domain background
Key Responsibilities 1) Integration Architecture & Design Define the target integration architecture across HES, Energy IP MDMS, SAP PO, SAP HANA, GIS and other enterprise systems (billing/CRM/DWH as applicable). Select and standardize integration patterns: API-led, event/message-based, batch, file-based, near-real-time streaming, and hybrid models. Define canonical data model and transformation strategy (meter events, interval reads, alarms, device lifecycle, network topology references). Define interface contracts: message schemas, API specifications, payload validation rules, versioning, backward compatibility. Ensure end-to-end traceability: business requirement → interface design → test cases → operational monitoring.2) Interface Governance Architect and govern integrations implemented via mappings, adapters, routing, error-handling, retries). Define integration standards for:SOAP/REST, IDoc, RFC, JMS, SFTP, ODBC/JDBC (as applicable) Establish reusable components (common mappings, error-handling frameworks, logging standards, correlation IDs).3) Data Flow Design (HES ↔ MDMS ↔ SAP ↔ GIS) Design and validate end-to-end flows for:Interval and register reads (bulk + incremental) Events/alarms (tamper, outages, power quality) Device lifecycle (install, replace, remove, firmware/config) Commands (connect/disconnect, on-demand reads, parameter updates) Master data alignment (premise/customer/meter-to-premise mapping) GIS topology and asset references (feeder/transformer connectivity, spatial attributes)4) Non-Functional Requirements (NFR) Ownership Define and ensure compliance with NFRs:Performance (throughput, latency, peak handling) Scalability (horizontal scaling, partitioning, batching strategy) Availability/DR (HA design, RPO/RTO, failover behaviors) Security (encryption, certs, OAuth/SAML as applicable, key rotation) Observability (monitoring, alerting, audit logs, integration KPIs) Define capacity sizing inputs for integration layer: message volume/day, peak reads, file sizes, concurrent interfaces.6) Delivery Support, Testing, Cutover & Hypercare Lead integration workshops with business/IT/vendors to finalize interface requirements and sequencing. Own the integration test strategy:SIT, end-to-end testing, performance testing, failover testing Test data preparation and reconciliation approach Support cutover planning, data migration and synchronization, rollback strategy. Provide L3 support guidance during hypercare for interface failures and performance issues.
Required Skills & Qualifications Must-Have (Technical)12+ years in integration architecture across enterprise platforms. Strong experience in AMI/MDMS integrations (Energy IP preferred) or similar high-volume telemetry/data platforms. Strong hands-on architecture knowledge of:interface design, mapping, adapters, monitoring/error handling)integration patterns (data replication, interfaces, data services) API design (REST/SOAP), message-based integration (JMS/Kafka-like concepts) Data formats: XML, JSON, CSV, schema governance and versioning Experience in high-volume ingestion and processing:Batch tuning, incremental loads, partitioning, compression strategies Handling late/missing reads and estimation flags Integration security knowledge:TLS/m TLS, certificates, OAuth2/token-based auth (where applicable), secure service accounts Must-Have (Architecture & Delivery) Proven ability to define integration standards, canonical models, and enforce governance. Strong knowledge of NFR engineering: performance, DR, monitoring, resiliency patterns. Experience leading cross-functional workshops and producing architecture artifacts. Education & Certifications Bachelor’s degree in Engineering/Computer Science (Master’s preferred). Preferred certifications:TOGAF (or equivalent architecture certification) SAP PO/Integration certifications Cloud/Integration certifications (if relevant)