Understanding CloudSuite Architecture#
Infor CloudSuite represents a fundamental shift from traditional ERP architecture. Understanding this architecture is essential for evaluating whether CloudSuite fits your organisation's technical requirements and constraints.
What makes CloudSuite different: - True multi-tenant SaaS (not hosted single-tenant) - Industry-specific code bases (not configured generic ERP) - Amazon Web Services (AWS) infrastructure - Continuous delivery model with automatic updates
This guide explains the technical architecture, deployment implications, and platform capabilities that every evaluation team should understand.
---
Multi-Tenant Architecture: What It Means#
The Multi-Tenant Model#
CloudSuite is built on true multi-tenant architecture. All customers share: - A single codebase - Shared infrastructure - Common database schema (with customer data logically separated) - Simultaneous updates
What this enables: - Lower infrastructure costs passed to customers - Faster innovation (Infor updates once, everyone benefits) - No upgrade projects - Consistent functionality across customer base
What this prevents: - Code-level customisation - Deferring updates - Customer-specific database modifications - Long-term stability on older versions
The Configuration vs Customisation Distinction#
In CloudSuite, you can configure but not customise:
Configuration (allowed): - Setting options within the application - Creating reports and dashboards - Defining workflows within supported parameters - Adding fields through extension framework - Creating user-defined tables
Customisation (not allowed): - Modifying source code - Changing database schema - Creating custom database objects - Altering core business logic - Bypassing standard processes
The implication: Your organisation must adapt to CloudSuite's industry-standard processes. If your "unique" processes are genuinely differentiators, CloudSuite may not be suitable.
Update Cadence and Control#
CloudSuite receives updates on a regular cadence (typically quarterly):
What gets updated: - New features and functionality - Bug fixes and performance improvements - Regulatory changes (tax updates, compliance) - Security patches
Your control: - You cannot defer updates - You cannot skip versions - You receive advance notice of changes - Sandbox environments let you test before production updates
Risk mitigation: - Subscribe to Infor's release notes - Test critical processes in sandbox after each update - Maintain regression test scripts - Plan for update weekends
---
Infor OS: The Technology Platform#
Infor OS (Operating Service) is the platform layer that provides common services across all CloudSuite products.
Core Platform Components#
Infor Coleman AI: - Embedded artificial intelligence capabilities - Machine learning for predictive analytics - Natural language processing for queries - Intelligent automation for routine tasks - AI-assisted decision support
Practical applications: - Demand forecasting - Anomaly detection in transactions - Intelligent document processing - Predictive maintenance (for EAM) - Chatbot interfaces for common queries
Infor Birst Analytics: - Native business intelligence platform - Self-service reporting and dashboards - Data visualisation - Enterprise reporting consolidation - Mobile analytics
Key capabilities: - Embedded in CloudSuite (no separate BI licence needed) - Real-time data access - Scheduled report distribution - Ad-hoc query capability - Integration with external data sources
Infor Ming.le: - Collaboration and social business platform - Contextual information sharing - Workflow and approval management - Document management - Activity streams
Use cases: - Approving transactions from mobile devices - Collaborating on customer issues - Sharing documents with context - Tracking process status
Infor ION (Integration Object Network): - Middleware for application integration - API management - Business event monitoring - Data synchronisation
Integration capabilities: - Pre-built connectors to common applications - API access for custom integrations - EDI support for B2B integration - Real-time and batch integration options
API and Integration Architecture#
CloudSuite provides comprehensive API access:
REST APIs: - Modern RESTful API architecture - Comprehensive coverage of business objects - OAuth 2.0 authentication - JSON data format
API documentation: - Available through Infor's developer portal - Swagger/OpenAPI specifications - Sandbox environments for testing
Common integration scenarios: - Payroll systems (critical for ANZ) - Banking and payment gateways - E-commerce platforms - CRM systems (if not using Infor's CRM) - Third-party logistics providers - Industry-specific applications
Integration considerations: - API rate limits may apply - Complex integrations require middleware (ION or third-party) - Real-time vs batch trade-offs - Error handling and monitoring
---
AWS Infrastructure#
CloudSuite runs exclusively on Amazon Web Services.
Infrastructure Characteristics#
Global availability: - Multiple AWS regions worldwide - Australian regions available (Sydney, Melbourne) - Discuss region selection during contracting
Data centre considerations: - Physical security handled by AWS - Redundancy and disaster recovery built-in - Geographic redundancy options - Backup and recovery managed by Infor
Performance: - Latency depends on distance to AWS region - Australian customers typically use Sydney region - New Zealand customers may experience slightly higher latency - Content delivery networks for static content
Data Residency and Sovereignty#
For Australian organisations: - Australian AWS regions available - Discuss data residency requirements with Infor sales - Contractual commitments for data location - Consider regulatory requirements (privacy, financial services)
For New Zealand organisations: - No NZ-based AWS region currently - Australian region is typical choice - Discuss data residency if required for compliance - Privacy Act 2020 considerations
Questions to ask: - "Which AWS region will host our data?" - "Can you contractually commit to data residency?" - "How is data backed up and where are backups stored?" - "What happens to our data if we terminate the contract?"
---
Security and Compliance#
Security Architecture#
Infor's security model: - Role-based access control (RBAC) - Segregation of duties configuration - Audit logging - Encryption at rest and in transit - Regular security assessments
AWS security: - SOC 2 Type II certified - ISO 27001 certified - PCI DSS compliant (for applicable services) - Regular penetration testing
Customer responsibilities: - User access management - Role configuration - Password policies - Security monitoring and response - Data classification and handling
Compliance Certifications#
Infor CloudSuite certifications: - SOC 2 Type II - ISO 27001 - HIPAA (for healthcare editions) - FDA 21 CFR Part 11 (for life sciences) - Additional industry-specific certifications
ANZ-specific compliance: - GST/BAS calculations - Privacy Act compliance (customer responsibility for configuration) - Financial reporting standards - Industry-specific regulations (food safety, healthcare)
---
Deployment and Implementation#
Implementation Approach#
CloudSuite implementations follow a structured methodology:
Phase 1: Discovery and Planning (4-8 weeks) - Requirements validation - Gap analysis - Project planning - Team formation
Phase 2: Design (6-12 weeks) - Solution design - Integration architecture - Data migration planning - Training planning
Phase 3: Build and Configure (8-16 weeks) - System configuration - Integration development - Data migration execution - Testing
Phase 4: Deploy (4-8 weeks) - User training - Cutover planning and execution - Go-live support - Hypercare
Environment Strategy#
Typical environment landscape: - Production: Live system - Test: For user acceptance testing - Development/Sandbox: For configuration testing
Environment considerations: - Additional environments may incur cost - Sandbox refresh from production - Development testing for integrations
Data Migration#
Migration approach: - Master data migration (customers, suppliers, products) - Open transaction migration - Historical data archival strategy - Data cleansing before migration
Industry-specific data: - Formulas and recipes (Food & Beverage) - Style matrices (Fashion) - Patient records (Healthcare—special handling required)
---
Operational Considerations#
Support Model#
Infor support: - Tier 1: Partner first line - Tier 2: Infor product support - Severity-based response times - Online support portal
Partner support: - Implementation partner typically provides ongoing support - Local time zone coverage (if partner has ANZ presence) - Configuration assistance - Training
Support considerations: - Define support SLAs in contract - Clarify escalation paths - Understand support hour allocations - Plan for after-hours support needs
Monitoring and Performance#
Infor provides: - System health monitoring - Performance metrics - Availability reporting
Customer responsibilities: - Monitoring business processes - User adoption tracking - Integration monitoring - Performance issue reporting
Disaster Recovery and Business Continuity#
Infor's DR capabilities: - AWS multi-availability-zone deployment - Regular backups - Recovery point and time objectives (check current SLAs)
Customer planning: - Business continuity planning - Communication plans for outages - Alternative process documentation - Regular DR testing participation
---
Total Cost of Ownership#
Direct Costs#
Subscription: - Per-user-per-month pricing - Minimum user commitments - Module-based pricing - Annual increases (typically 3-5%)
Implementation: - Partner implementation fees - Infor consulting (if used) - Internal resource costs - Training costs
Infrastructure: - No separate infrastructure costs (included in subscription) - Integration middleware (if needed) - Third-party application licences
Indirect Costs#
Internal resources: - Project team allocation - Ongoing administration - Training development and delivery - Change management
Integration costs: - Payroll integration development and maintenance - Banking integration - Third-party application integration - EDI setup and maintenance
Ongoing costs: - Partner support retainer - Additional training - Process improvement initiatives - Expansion to additional modules
---
Monday Morning Action Plan#
Technical evaluation checklist:
- Document Integration Requirements: List every system that must connect to CloudSuite. Each integration is cost and complexity.
- Assess Customisation Needs: Identify processes that differ from industry standard. Each is a risk factor for CloudSuite fit.
- Review API Documentation: Request access to Infor's API documentation. Verify coverage of your integration needs.
- Plan for Payroll: For ANZ organisations, payroll integration is typically required. Identify your payroll provider and verify integration options.
- Discuss Data Residency: If data location matters for compliance, negotiate contractual commitments.
- Evaluate Network Performance: Test CloudSuite performance from your locations. Latency matters for user experience.
- Understand Update Impact: Review recent CloudSuite release notes. Understand how updates might affect your organisation.
---
Conclusion: CloudSuite Requires Adaptation#
Infor CloudSuite's architecture provides significant benefits—lower infrastructure costs, continuous innovation, and industry-specific functionality. But it requires organisational adaptation.
CloudSuite works when: - Your industry is a target vertical - You can adapt processes to industry standards - You accept multi-tenant constraints - You have realistic expectations about customisation
CloudSuite struggles when: - You need extensive customisation - Your processes are genuinely unique - You require on-premise deployment - You need to control update timing
The technical architecture is sound. The question is whether your organisation can work within its constraints.