Acme Manufacturing

Servers

47

Applications

8

Databases

5

Environments

3

Network zones

2

Replatform

7

Rehost

4

Retain

2

Refactor

1

Retire

1

Waves

4

Engineering tasks

93

Terraform candidates

31

Ansible candidates

44

Evidence coverage: inventory 94%, dependencies 78%, utilization 51%.

Showing 12 of 47 discovered servers from the example inventory.

• ERP (Infor LN)→Active Directoryidentity

  Kerberos auth observed on erp-app-01

• Manufacturing Execution→ERP (Infor LN)data

  Nightly order export, 02:15 plant local

• Warehouse Management→ERP (Infor LN)runtime

  SOAP inventory API, 4,200 calls/day

• Warehouse Management→Manufacturing Executionruntime

  Pick-complete events over AMQP

• Quality Management→File serversruntime

  UNC path \\fs-01\qms

• Quality Management→Active Directoryidentity

  LDAP bind from qms-app-01

• CRM→ERP (Infor LN)data

  Customer master sync, inferred from cron + JDBC

• EDI Gateway→ERP (Infor LN)data

  Inbound 850/855 files landed on erp-app-01

• Data Warehouse→ERP (Infor LN)data

  Oracle Data Pump + nightly ETL

• Data Warehouse→CRMdata

  PostgreSQL logical replica slot

• Legacy reporting→ERP (Infor LN)data

  Read replica connection string

• Intranet / SharePoint→File serversruntime

  Content library on DFS share

• Manufacturing Execution→Active Directoryidentity

  Service account MES_PROD

• Bastion / jump hosts→Active Directoryidentity

  Admin group membership required

Estimated monthly AWS run rate $15,750. Assumptions and uncertainty are first-class fields — low-confidence lines are not presented as facts.

1. Wave 1

   Foundation

   Identity, access, and observability that every later wave depends on.

   • Active Directory
   • Bastion / jump hosts
   • Nagios monitoring

2. Wave 2

   Shared services

   Move shared platforms and retire unused print before line-of-business apps.

   • File servers
   • Backup system
   • EDI Gateway
   • Print services

3. Wave 3

   Plant operations

   Warehouse, quality, and MES after latency and identity are proven.

   • Warehouse Management
   • Quality Management
   • Manufacturing Execution

4. Wave 4

   Core systems

   ERP, CRM, and warehouse refactor once dependencies are already in AWS.

   • ERP (Infor LN)
   • CRM
   • Data Warehouse

Sample of 15 representative tasks from 93 generated items. Terraform and Ansible candidates are tagged so execution can start from the same dataset.

• T-001

  Create landing-zone accounts, VPCs, and plant connectivity

  Wave 1 · terraform

• T-002

  Deploy IAM Identity Center and break-glass roles

  Wave 1 · terraform

• T-003

  Stand up domain controllers and validate replication

  Wave 1 · ansible

• T-004

  Replace jump hosts with Systems Manager Session Manager

  Wave 1 · terraform

• T-005

  Export Nagios checks and recreate in CloudWatch / Grafana

  Wave 1 · ansible

• T-018

  Provision FSx and DFS namespace cutover runbook

  Wave 2 · terraform

• T-019

  Enable AWS Backup and vendor S3 connector

  Wave 2 · terraform

• T-024

  Build Transfer Family + Lambda EDI ingest

  Wave 2 · terraform

• T-025

  Decommission print queues after SaaS acceptance

  Wave 2 · engineering

• T-041

  Provision RDS PostgreSQL for WMS and validate extensions

  Wave 3 · terraform

• T-042

  Ansible-cutover WMS app config, secrets, and health checks

  Wave 3 · ansible

• T-055

  Rehost MES VMs and measure plant RTT

  Wave 3 · engineering

• T-071

  RDS for Oracle sizing decision with license review

  Wave 4 · engineering

• T-072

  Terraform ERP target VPC, RDS, and security groups

  Wave 4 · terraform

• T-088

  Pilot Redshift Serverless with 90-day history

  Wave 4 · engineering