A company’s operational systems form the backbone of day-to-day processes—from enterprise resource planning (ERP) to manufacturing execution systems (MES) and beyond. These systems, and the architecture connecting them, directly affect efficiency, data integrity, and decision-making speed.
1. Objective
1. Identify Key Systems and Architecture
- Understand the software and hardware platforms that enable core operations such as production planning, procurement, inventory management, and sales order processing.
- Evaluate the overall system design—whether highly integrated or fragmented—and how this influences data flow and decision-making.
2. Assess System Performance and Reliability
- Determine if current systems can handle existing transaction volumes without lags, errors, or frequent downtime.
- Spot any legacy platforms or custom solutions that hinder upgrades, limit flexibility, or pose cybersecurity risks.
3. Uncover Opportunities and Risks
- Highlight areas where improved integration, automation, or modernization could streamline operations and reduce costs.
- Identify critical weaknesses—such as single points of failure, limited vendor support, or poor scalability—that may impede growth or create vulnerabilities.
2. Data Request
1. System Inventory and Architecture Diagrams
- Comprehensive list of software applications and hardware platforms underpinning operations (ERP, MES, CRM, WMS, etc.).
- Diagrams or documentation showing how these systems connect, including data flows and integration points (APIs, middleware).
2. System Performance Metrics
- Records of system uptimes/downtimes, response times for critical functions, and transaction volumes over the past 12–24 months.
- Helpdesk or IT support logs capturing recurring issues and their resolution times.
3. Vendor and Licensing Agreements
- Contracts or service level agreements (SLAs) with software vendors, cloud providers, and IT service partners.
- Information on license models, maintenance costs, and renewal timelines for critical systems.
4. Change Management and Upgrades
- Documentation on the company’s processes for applying software patches, system upgrades, or infrastructure overhauls.
- Past project plans or post-mortems for major IT initiatives, highlighting successes and pain points.
5. Roadmaps and IT Budgets
- Future plans or roadmaps detailing planned system replacements, migrations to cloud solutions, or new module implementations.
- Historical IT expenditure data, including capital vs. operational spending on core systems.
3. Questions to Ask
1. System Scope and Integration
- Which operational processes (finance, procurement, manufacturing, logistics) are covered by the primary ERP or similar systems?
- Are there significant “shadow IT” tools or spreadsheets filling gaps where the main systems fall short?
2. Architecture Strategy
- Does the organization prefer a single integrated platform, or a “best-of-breed” approach with multiple specialized applications?
- How does data flow across systems—real-time, batch uploads, manual exports?
3. Performance and Reliability
- Are there known bottlenecks or peak load times that strain system resources?
- How frequently do critical systems experience outages, and what are the contingency or disaster recovery plans?
4. Scalability and Customization
- Can current systems handle projected growth or the addition of new product lines without major rework?
- What level of customization has been applied, and does it hinder upgrades or vendor support?
5. Security and Compliance
- Are these core systems subject to any industry-specific regulatory requirements (e.g., FDA, SOX, GDPR)?
- Does the company have robust identity/access management, encryption, and incident response processes in place?
4. Analyses to Perform
1. System Mapping and Gap Analysis
- Compare the architecture diagram to actual workflows, identifying manual workarounds or disconnected tools.
- Highlight duplication (e.g., multiple tools performing the same function) or missing functionality that forces staff to improvise.
2. Performance and Reliability Review
- Analyze uptime statistics and helpdesk tickets for recurring system failures or latency issues.
- Examine how quickly critical problems are escalated and resolved—especially during peak operational periods.
3. User Feedback and Adoption
- Interview or survey end-users (production managers, sales staff, etc.) to gauge satisfaction with system capabilities and ease of use.
- Look for signs of “system avoidance,” where users prefer unofficial tools due to system complexity or poor design.
4. Customization and Upgrade Path
- Assess how extensively the main ERP/MES/other platforms are customized—custom code can complicate vendor upgrades or reduce vendor support viability.
- Determine if upcoming vendor releases or new modules align with the organization’s future needs.
5. Cybersecurity and Disaster Recovery
- Evaluate whether backups, failover systems, or cloud-based solutions protect against data loss and extended outages.
- Check for vulnerabilities from outdated software versions or lax access control measures.
5. What Best Practice Looks Like
1. Unified, Streamlined Architecture
- A well-integrated set of core systems providing end-to-end visibility of operations (from order entry to production scheduling to fulfillment).
- Real-time data sharing, eliminating redundant data entry or synchronization delays.
2. High Availability and Resilience
- Robust infrastructure (often cloud-hosted or hybrid) with built-in redundancy and failover capabilities.
- Proactive monitoring tools that alert IT staff to potential performance issues before they escalate.
3. Modular, Scalable Solutions
- Systems designed to handle volume spikes or expansion into new regions or product lines without extensive reconfiguration.
- Minimal reliance on deep custom code—configuration over customization—so upgrades are smoother and vendor support remains intact.
4. Secure and Compliant Environments
- Strong cybersecurity posture, including regular vulnerability assessments, encryption of sensitive data, and strict user access protocols.
- Clear audits and documentation for compliance with relevant regulations or industry standards.
5. Continuous Improvement and User-Centric Approach
- A formal governance process where users provide feedback, and IT prioritizes enhancements based on business impact.
- Ongoing training and change management to ensure employees leverage system capabilities effectively.
6. Example Findings That Would Be Cause for Concern
1. Heavily Fragmented or Outdated Systems
- Multiple legacy systems patched together, with limited interoperability and risk of frequent breakdowns.
- High dependence on manual processes or spreadsheets for critical operations (e.g., cost accounting, inventory tracking).
2. Unstable or Slow Performance
- Regular complaints of system slowdowns during peak hours, causing order processing or production scheduling bottlenecks.
- Minimal or no real-time monitoring, leading to prolonged downtime before problems are identified and addressed.
3. Excessive Customization or Vendor Lock-In
- ERP or MES platforms with extensive custom code, complicating every upgrade or vendor patch.
- Dependency on specialized software with no clear vendor roadmap for modernization or support, raising long-term viability concerns.
4. Security Vulnerabilities or Poor Governance
- Gaps in patch management or outdated software versions exposing the company to cyber threats.
- Weak disaster recovery or backup policies, risking significant data loss in the event of a system failure or breach.
5. Lack of Alignment with Business Growth
- No clear IT strategy to support upcoming initiatives (e.g., new product lines, acquisitions, global expansion).
- Key processes (like advanced forecasting, quality tracking, or customer analytics) missing from existing systems, hampering competitiveness.
Request the Operational Due Diligence Playbook:
Table of Contents:
Chapter 1: Introduction
Chapter 2: How Operational Due Diligence Fits into the Full Due Diligence Process
Chapter 3: Strategy & Governance Analysis
Chapter 4: Organizational Structure & Leadership Assessment
Chapter 5: Talent & Workforce Management
Chapter 6: Supply Chain & Procurement
Chapter 7: Production & Operations Management
Chapter 8: Technology & IT Systems
Chapter 9: Financial Operations & Performance Measurement
Chapter 10: Risk Management & Regulatory Compliance
Chapter 11: Quality Assurance & Continuous Improvement
Chapter 12: ESG & Sustainability Considerations
Chapter 13: Post-Merger Integration & Operational Synergies