🏗️ ITINT ERP R2 Integration Architecture

Leveraging Existing Patterns & Infrastructure for 28 New Integrations

Foundation: 90+ Existing Golang Integrations

ITINT has built 30+ golang worker repositories serving 90+ active integrations.
This mature infrastructure provides proven patterns to leverage for ERP R2 work.

195+

Total Active Integrations

90+ Golang | 101 Boomi | 2 CF Workers

30+

Golang Worker Repos

Multi-tenant architecture pattern

99.999%

Boomi Success Rate

160k executions/24h proven reliability

ERP R2 New Integrations

16 TBD | 8 Go+OIC | 4 OIC

🗺️ Overarching Architecture: Existing + New

External Systems

Workday
4+ integrations

Anaplan
7+ integrations

NetSuite
10+ integrations

Crane/Omni
6 NEW integrations

NLYTE
4 NEW integrations

MITAC/ODMs
5 NEW integrations

Jira/Navan
Existing + NEW

⬇

Integration Infrastructure Layer

Existing Workers
anaplan-worker
workforce-mgmt-worker
asset-mgmt-worker
payment-worker
+ 26 more repos

New ERP R2 Workers
warehouse-worker
dcim-worker
manufacturing-worker
oracle-erp-worker

Boomi Platform
101 packages
160k executions/day
99.999% success

⬇

Target Systems

Salesforce
Oomnitza
Zylo

Oracle ERP Cloud
Inventory | Procurement
PPM | FA | ALM
GTM | ARCS | FLA | GL

Anaplan
HighRadius
Stripe

Key Insight:

ERP R2 integrations follow the same architectural patterns as existing ITINT infrastructure: External Systems → Golang/Boomi Workers → Target Systems. The main difference is Oracle ERP Cloud as the new primary target, requiring Oracle-specific patterns.

✅ Existing Golang Workers (30+ Repositories)

Multi-Tenant Worker Pattern (Proven at Scale)

ITINT uses a multi-tenant architecture where one golang worker repository handles multiple related integrations. This pattern reduces code duplication, centralizes error handling, and enables shared connection pooling.

anaplan-worker

📦 7+ integrations

🔗 NS→Anaplan, RevPro→Anaplan, WD→Anaplan

Pattern: Financial data consolidation

workforce-management-worker

📦 4+ integrations

🔗 Workday → Coupa/Navan/NS/SF

Pattern: HR data distribution

asset-management-worker

📦 Bidirectional sync

🔗 Coupa ↔ Oomnitza

Pattern: Two-way asset tracking

payment-worker

📦 Payment processing

🔗 Stripe↔HighRadius, Kyriba→HighRadius

Pattern: Payment reconciliation

salesforce-worker

📦 Internal SF flows

🔗 SF→SF (compliance, upgrades)

Pattern: Internal data sync

netsuite-worker

📦 NS integrations

🔗 NS→SF/Oomnitza

Pattern: ERP data distribution

coupa-worker

📦 Procurement

🔗 SimpleLegal ↔ Coupa

Pattern: Legal procurement sync

app-usage-worker

📦 CF Access logs

🔗 CF Access → Zylo

Pattern: SaaS usage tracking

+ 22 more worker repositories covering various domains

🔄 Pattern Matching: ERP R2 Requirements vs. Existing Patterns

✅ Existing: Anaplan Worker Pattern

Repository: anaplan-worker

Integrations: 7+ sources → Anaplan

Pattern: Multiple sources converging to financial planning system

🆕 ERP R2 Need: Oracle ARCS Convergence

New Integrations:

• EPM-INT-015 (NetSuite→ARCS)

• EPM-INT-017 (Workday→ARCS)

• EPM-INT-019 (RevPro→ARCS)

Pattern: Multiple sources converging to reconciliation system

💡 Reusability: HIGH

Create oracle-arcs-worker using anaplan-worker pattern. Same convergence pattern, different target API.

✅ Existing: Workforce Management Pattern

Repository: workforce-management-worker

Integrations: Workday → 4+ targets

Pattern: One HR source broadcasting to multiple systems

🆕 ERP R2 Need: Workday to Oracle Procurement

New Integrations:

• STP-INT-030 (Workday→Oracle Procurement)

Pattern: HR system → ERP procurement (PO requests)

💡 Reusability: HIGH

Leverage workforce-management-worker authentication and Workday API patterns. Add Oracle Procurement connector.

✅ Existing: Asset Management Bidirectional

Repository: asset-management-worker

Integrations: Coupa ↔ Oomnitza

Pattern: Two-way asset synchronization

🆕 ERP R2 Need: NLYTE Bidirectional Sync

New Integrations:

• GTM-INT-034 (NLYTE→Oracle GTM)

• GTM-INT-035 (Oracle GTM→NLYTE)

• INFRA-INT-003 (NLYTE→Oracle FA)

• INFRA-INT-004 (Oracle Inventory→NLYTE)

Pattern: Two-way DCIM data synchronization

💡 Reusability: MEDIUM

Create dcim-worker using bidirectional sync pattern from asset-management-worker. Adapt conflict resolution logic for DCIM use case.

✅ Existing: Netsuite Worker ERP Pattern

Repository: netsuite-worker

Integrations: NetSuite → SF/Oomnitza

Pattern: ERP as data source, distributing to downstream systems

🆕 ERP R2 Need: Oracle PPM Broadcast

New Integrations:

• PTC-INT-003 (Oracle PPM→Anaplan)

• PTC-INT-004 (Oracle PPM→Multiple Systems)

Pattern: ERP as data source, broadcasting project data

💡 Reusability: HIGH

Create oracle-ppm-worker based on netsuite-worker pattern. Same ERP distribution pattern, different source API.

✅ Existing: Payment Worker Reconciliation

Repository: payment-worker

Integrations: Stripe↔HighRadius, Kyriba→HighRadius

Pattern: Financial transaction matching and reconciliation

🆕 ERP R2 Need: Oracle FA/FLA Pattern

New Integrations:

• RTR-INT-021 (IronClad→Oracle FLA)

• RTR-INT-025 (Oracle FA→Oomnitza)

Pattern: Asset/lease financial tracking

💡 Reusability: MEDIUM

Leverage payment-worker error handling and retry logic for Oracle FA integrations. Financial data requires same reliability.

✅ Existing: NONE - Gap Identified

Repository: N/A

Integrations: No existing warehouse/logistics integrations

Pattern: High-frequency warehouse operations

🆕 ERP R2 Need: Crane/Omni Warehouse Suite

New Integrations:

• STP-INT-032, INFRA-INT-009/010/011/013/015 (6 Crane/Omni integrations)

Pattern: Bidirectional warehouse management (PO, shipments, receipts, inventory)

💡 Reusability: LOW

⚠️ NEW PATTERN NEEDED: Create warehouse-worker from scratch. No existing warehouse/logistics pattern. Consider real-time requirements (webhooks vs polling).

✅ Existing: NONE - Gap Identified

Repository: N/A

Integrations: No existing manufacturing/EDI integrations

Pattern: Manufacturing supply chain data

🆕 ERP R2 Need: ODM/MITAC Manufacturing

New Integrations:

• INFRA-INT-005 (ODMs→Oracle)

• INFRA-INT-017 (MITAC→Oracle)

• INFRA-INT-001 (MITAC→Oracle FA)

Pattern: Manufacturer → Oracle Inventory/FA (finished goods, work orders)

💡 Reusability: LOW

⚠️ NEW PATTERN NEEDED: Create manufacturing-worker. May require EDI format support depending on vendor APIs.

🔧 Reusable Infrastructure Components

✅

Error Handling

Boomi: 38k+ exception handlers/day
Golang: Multi-tenant shared error handling
Kibana monitoring + Sentinel alerts

✅

Authentication

CF Access tokens (app-usage-worker)
OAuth patterns (workforce-mgmt-worker)
API key management (R2, external APIs)

✅

Data Staging

R2 storage patterns (app-usage-worker)
Staging buckets for large data
Failure recovery mechanisms

✅

Monitoring

Boomi: Real-time health via MCP API
Execution metrics (count, errors, latency)
Kibana dashboards + alerts

⚠️ Gaps: New Patterns Needed for ERP R2

🚨 Priority 1: Oracle ERP Cloud Patterns

Gap: No existing Oracle-specific golang workers
Impact: 28 integrations need Oracle API patterns
Action: Create oracle-erp-worker skeleton with:
- Oracle SOAP/REST API golang library
- Authentication (OAuth, JWT)
- Error handling for Oracle-specific errors
- Retry logic for Oracle rate limits

🚨 Priority 2: Warehouse Operations Pattern

Gap: No high-frequency warehouse/logistics integrations
Impact: 6 Crane/Omni integrations (21% of ERP R2)
Action: Create warehouse-worker with:
- Real-time webhook support (if available)
- High-frequency polling (if no webhooks)
- Inventory data validation
- Idempotency for warehouse operations

⚠️ Priority 3: DCIM/IoT Pattern

Gap: No IoT device integration patterns
Impact: 4 NLYTE integrations (DCIM)
Action: Create dcim-worker with:
- Device authentication mechanisms
- Telemetry data handling
- Bidirectional sync (device ↔ ERP)
- Data center lifecycle events

⚠️ Priority 4: Manufacturing/EDI Pattern

Gap: No EDI or manufacturing supply chain patterns
Impact: 3 ODM/MITAC integrations
Action: Create manufacturing-worker with:
- EDI format support (if vendors use EDI)
- Multi-vendor connector management
- Production data validation
- Work order lifecycle handling

🎯 Strategic Recommendations

Two-Phase Approach: Fast Delivery + Long-Term Optimization

Phase 1: Use Boomi for Fast MVP (Sprints 1-4)

Why Boomi First:

✅ Proven 99.999% reliability (160k executions/24h)
✅ Native Oracle connectors (no golang library needed)
✅ Fast development (visual design, no code)
✅ Immediate deployment (no new infrastructure)
✅ Unblock 16 TBD integrations (make decision: Boomi)

Target: Deploy all 28 integrations via Boomi in Sprints 1-4

Phase 2: Migrate to Golang Post-Launch (6-12 months)

Why Golang Migration:

🔧 Long-term maintainability (code-based, version control)
🔧 Cost efficiency (Boomi licensing vs. golang compute)
🔧 Custom logic (complex transformations easier in code)
🔧 Team consistency (90+ existing golang integrations)
🔧 Performance tuning (optimize high-frequency flows)

Target: Migrate high-volume integrations (warehouse, DCIM) to golang workers

Recommended Migration Priority (Post-Launch):

1. Warehouse Suite (6 integrations)

Why first: Highest frequency, 21% of portfolio
Create: warehouse-worker (Crane/Omni integrations)
Timeline: Month 6-9 post-launch

2. Oracle PPM Suite (4 integrations)

Why second: Critical project tracking
Create: oracle-ppm-worker
Timeline: Month 9-12 post-launch

3. DCIM Suite (4 integrations)

Why third: Bidirectional complexity
Create: dcim-worker (NLYTE integrations)
Timeline: Month 12-15 post-launch

4. Keep Simple Ones in Boomi

Don't migrate: OIC-only integrations (4)
Rationale: Low complexity, not worth migration effort
Examples: IronClad→FLA, JIRA→PPM

⚡ Immediate Actions (This Week)

Day 1: Make Architecture Decision

Decide middleware for 16 TBD integrations: Use Boomi
Rationale: Proven reliability, native Oracle connectors, fast delivery
Document decision in RICE inventory
Unblock all Sprint 1-4 integrations

Day 2-3: Start Phase 1 Development

Begin Boomi development for 3 quick wins:
- RTR-INT-021 (IronClad→Oracle FLA)
- PTC-INT-001 (JIRA→Oracle PPM)
- PTC-INT-002 (Navan→Oracle PPM)
Leverage existing Boomi Oracle connectors

Week 2: Plan Golang Migration (Future)

Create oracle-erp-worker skeleton repository
Research Oracle ERP Cloud golang libraries
Document authentication patterns (OAuth, JWT)
Set up CI/CD pipeline (reuse worker-build tooling)

Week 3-4: Continue Boomi Delivery

Sprint 2: STP-INT-032 (Crane/Omni POs) - Boomi
Build all 28 integrations in Boomi (Sprints 1-4)
Monitor performance metrics
Prepare migration candidates for Phase 2

📊 Summary: Leveraging 90+ Integrations for ERP R2

HIGH

Reusability: 4 patterns

Anaplan convergence
Workday broadcast
NetSuite ERP distribution
PPM project tracking

MEDIUM

Reusability: 2 patterns

Bidirectional sync (NLYTE)
Financial reconciliation (FA/FLA)

NEW

Patterns Needed: 3

Warehouse operations (Crane/Omni)
Manufacturing/EDI (ODMs)
Oracle ERP Cloud API patterns

HYBRID

Recommended Approach

Phase 1: Boomi (fast delivery)
Phase 2: Golang (optimization)
Best of both worlds

Key Takeaway: ITINT's mature golang infrastructure provides proven patterns for most ERP R2 integrations. Use Boomi for fast Sprint 1-4 delivery, then migrate high-value integrations to golang for long-term maintainability, following the multi-tenant worker pattern used across 90+ existing integrations.