Build Operate Transfer for Manufacturing IT: A Delivery Guide
Manufacturing companies run enterprise IT estates that are older, more complex, and harder to staff than most CIOs outside the sector realise. SAP implementations that have been running since the late 1990s. RPG applications on IBM iSeries machines that control warehouse and production logic no one has touched in a decade. MES systems from Siemens, GE, or Rockwell sitting between the shop floor and the ERP layer, connected by custom integrations written in Java 1.4.
The Build Operate Transfer (BOT) model fits manufacturing IT delivery for a specific reason: the staffing problem is structural, not cyclical. The engineers who built and know these systems are retiring. Western European and North American universities are not producing replacements. The talent is in Eastern Europe and India, and the BOT model is the mechanism for accessing it with permanence — not rotating contractors.
Below: which systems a manufacturing BOT center covers, what the economics look like, and what to watch for in the setup.
Why Manufacturing IT Is a BOT-Suited Problem
Manufacturing IT fits the BOT delivery model for three structural reasons.
SAP PP, SAP PM, and RPG/AS400 expertise are concentrated among engineers in their 40s and 50s. The next generation did not train on these stacks. In Germany, the Netherlands, and the UK, finding a senior ABAP developer with manufacturing module experience takes months and costs €90,000–€130,000 per year. In Romania or Poland, the same profile costs €50,000–€75,000, and the talent pool is proportionally younger.
A manufacturing company running SAP on a 15-year-old implementation does not have a project — it has a permanent operational need. SAP enhancements, production planning changes, quality module updates, and MES integration work generate a steady flow of development demand that outlasts any individual contractor engagement. BOT is built for this horizon.
When a manufacturing company uses rotating contractors to manage SAP or legacy RPG systems, tribal knowledge about production scheduling logic, batch control flows, and system interdependencies dissipates every time a person leaves. A BOT center accumulates that knowledge inside a stable, single-client team. At Transfer, the client inherits the team and its accumulated understanding of the system.
Systems Covered in a Manufacturing BOT Center
A manufacturing IT delivery center typically covers one or more of these system categories, depending on the client's estate:
| System category | Technologies | Typical use in manufacturing |
|---|---|---|
| Enterprise ERP | SAP S/4HANA, SAP ECC, Oracle EBS | Production planning, procurement, inventory, finance |
| Legacy ERP | RPG IV/RPGLE on IBM iSeries, COBOL | Warehouse management, order processing, legacy finance |
| Manufacturing Execution | Siemens Opcenter, GE Digital, Rockwell FactoryTalk | Shop floor control, work order management |
| MES/ERP integration | Java, .NET, REST/SOAP, XML | Connecting shop floor to ERP |
| Data & Analytics | Databricks, Snowflake, Power BI, Azure Synapse | OEE dashboards, production analytics, supply chain visibility |
| Quality systems | SAP QM, standalone LIMS | Inspection planning, batch traceability, CAPA |
| Warehouse | SAP EWM, SAP WM, custom RPG WMS | Goods receipt, picking, shipping, inventory control |
A typical 15-person manufacturing BOT center covers the ERP layer (SAP or RPG) as its primary function, with smaller cohorts handling integration and analytics.
SAP Delivery Centers for Manufacturing
SAP is the dominant ERP in mid-to-large manufacturing. For companies running SAP ECC or migrating to S/4HANA, the delivery center model is well-established.
Roles in a manufacturing SAP BOT center
- SAP PP (Production Planning) Consultant: MRP runs, production orders, capacity planning, integration with MES
- SAP PM (Plant Maintenance) Consultant: equipment master, maintenance orders, preventive maintenance scheduling
- SAP MM (Materials Management) Consultant: purchasing, goods receipt, inventory management, batch management
- SAP SD (Sales & Distribution) Consultant: order management, delivery, billing, pricing
- SAP QM (Quality Management) Consultant: inspection lots, quality notifications, batch classification
- SAP EWM Consultant: extended warehouse management, relevant for large distribution operations
- ABAP Developer: custom development, enhancements, BAPI/RFC integrations, report development
- SAP Basis Administrator: system administration, transport management, performance tuning
- SAP BTP Developer: extension development on Business Technology Platform, used for S/4HANA migration programs
S/4HANA migration context
Many manufacturing companies are mid-way through S/4HANA migration programs running 2–5 years. A BOT center staffed with SAP PP/MM/SD and ABAP expertise supports the migration workstream while simultaneously maintaining the ECC production system. This dual-running requirement (maintain the old while building the new) is where permanent, embedded teams outperform rotating consultants: the team that knows the current system configuration is the same team building the migration.
Legacy Systems: RPG, COBOL, and MES
RPG and IBM iSeries
RPG IV and RPGLE remain in active production at thousands of manufacturing and distribution companies across Germany, the Netherlands, the UK, and North America. Common use cases in manufacturing: production scheduling logic, warehouse management systems, EDI processing, customer order management, and custom MRP routines that were never migrated to SAP.
Finding RPG engineers in Western Europe takes 3–6 months. BOT centers in Romania, Poland, and Ukraine retain concentrations of iSeries-experienced engineers.
A BOT center for iSeries manufacturing typically covers:
- RPG IV / RPGLE development and maintenance
- CL programming
- DB2 for i database administration
- EDI (X12, EDIFACT) integration maintenance
- IBM MQ and API integration layer
MES Integration
The integration layer between MES and ERP is where manufacturing IT is most fragile. Custom Java or .NET services handling production order confirmation, goods movements, quality notifications, and equipment downtime reporting are often undocumented and understood by one or two engineers. A BOT center that includes MES integration engineers protects this knowledge layer.
Data & Analytics in Manufacturing BOT Centers
Manufacturing data analytics demand has grown significantly as OEE (Overall Equipment Effectiveness) measurement, supply chain visibility, and predictive maintenance programs move from pilot to production.
A data analytics cohort within a manufacturing BOT center covers:
| Layer | Technologies | Manufacturing use case |
|---|---|---|
| Ingestion | Kafka, Azure Event Hubs, Fivetran, custom MES connectors | Real-time shop floor data, SAP delta extraction |
| Processing | Databricks, Spark, dbt | OEE calculation, supply chain modelling |
| Consumption | Power BI, SAP Analytics Cloud, Tableau | Production dashboards, quality reporting |
| Governance | Collibra, Great Expectations | Material master data quality, batch traceability |
Cost Benchmarks
Indicative monthly per-head rates for a manufacturing BOT center in Romania, including provider management margin (12–20%):
| Role | Romania gross salary (€/month) | BOT per-head rate (est.) |
|---|---|---|
| SAP PP/PM Consultant (senior) | €4,000–€6,000 | €5,200–€7,800 |
| ABAP Developer (senior) | €4,000–€6,500 | €5,200–€8,500 |
| RPG IV Developer (senior) | €3,800–€5,500 | €5,000–€7,200 |
| SAP Basis Administrator | €4,500–€7,000 | €5,800–€9,100 |
| MES Integration Engineer | €3,500–€5,500 | €4,600–€7,200 |
| Data Engineer (Databricks) | €4,500–€7,000 | €5,800–€9,100 |
For a 15-person manufacturing SAP center in Germany, the equivalent fully loaded cost would run 70–110% higher than the Romania BOT rate.
Build Phase: What Setup Looks Like
The Build phase for a manufacturing BOT center has two characteristics that differ from generic software development center setups.
SAP PP, RPG IV, and MES integration engineers are not sourced from a large active candidate pool. The BOT provider needs to run active headhunting campaigns, approaching passively employed engineers. Budget 10–14 weeks for senior legacy roles rather than the 6–8 week standard.
Client knowledge transfer must happen early. The BOT provider cannot hire RPG engineers who understand your specific iSeries configuration without structured onboarding. The Build phase should include at minimum two on-site knowledge transfer sessions: one covering system architecture, one covering business process context. Engineers who understand why the system works the way it does are more productive and less likely to introduce regressions.
A realistic Build phase timeline for a 10-person manufacturing BOT center:
| Milestone | Timing |
|---|---|
| Legal/EOR structure confirmed | Week 2 |
| Job descriptions approved by client | Week 3 |
| First hire (senior anchor role) | Week 8–10 |
| Full team at 10 FTE | Month 4–5 |
| On-site knowledge transfer (session 1) | Month 2 |
| On-site knowledge transfer (session 2) | Month 4 |
| Governance framework live | Month 5 |
Risks Specific to Manufacturing
Manufacturing ERP and MES systems are increasingly connected to OT (operational technology) networks. The BOT center's access to production SAP systems must be governed by the client's IT security policies, with VPN, MFA, and data classification protocols agreed before the first hire starts.
If the BOT center is taking over maintenance of a live production system from an internal team or departing contractors, there must be a structured handover period. Running parallel coverage for 4–8 weeks before the incumbent team exits avoids gaps in system support.
Senior RPG and SAP PM engineers in Eastern Europe are in demand. Retention programs — performance bonuses, clear career paths within the center, training budgets — should be agreed in the operating agreement, not left to the provider's discretion.
Frequently Asked Questions
Can a BOT center support an active S/4HANA migration while maintaining the existing ECC system?
Yes. This is a common structure. The center runs two parallel workstreams: a migration team working on the S/4HANA build (ABAP, Basis, functional consultants in transformation mode) and a run team maintaining ECC production. Team size for this model typically starts at 12–15 people. The same team that maintains ECC gains the system knowledge that makes them effective on the migration — this knowledge continuity is a structural advantage over bringing in external migration consultants who need months to understand the client's configuration.
Is Romania a viable location for RPG/AS400 expertise?
Romania retains a meaningful pool of RPG IV and RPGLE engineers, primarily engineers in their 30s and 40s who trained on iSeries platforms at manufacturing and distribution companies during the 2000s and 2010s. The pool is smaller than the SAP talent market and requires active headhunting rather than posting. Poland and Ukraine also have RPG talent. For a 5–8 person RPG center, Romania is viable. For 15+ RPG engineers, a multi-country sourcing strategy is more reliable.
How does MES integration work across time zones?
Real-time MES integration issues — production order failures, goods movement errors, OEE feed problems — require responsive support. A Romania-based center (UTC+2/+3) has full working day overlap with DACH, Benelux, and UK manufacturing sites. For North American sites, a follow-the-sun model with a small on-call rotation is standard. The BOT operating agreement should specify response time SLAs for production-impacting incidents separately from standard development SLAs.
What is the minimum team size for a manufacturing BOT center?
The minimum viable team for a manufacturing SAP center is 8–10 people — enough to cover PP, MM, SD, ABAP, and Basis without single points of failure. For a legacy RPG-only center, 6–8 people can be viable if the RPG estate is the sole scope. Below 6 people, a dedicated team arrangement is more economical than the full BOT governance structure.
Who owns the institutional knowledge of the production system at transfer?
The institutional knowledge transfers with the team. Employment contracts novate to the client, meaning the engineers — and their accumulated understanding of the client's SAP configuration, RPG business logic, and MES integration architecture — become direct employees of the client. This is the primary asset in a manufacturing BOT transfer. The BOT contract should also specify delivery of operational documentation: system landscape diagrams, customisation inventories, known issue registers, and runbooks. Documentation obligations should be a milestone in the Operate phase, not deferred to Transfer.