An IT services firm with a rapidly growing SaaS portfolio faced a classic EA problem: Workday, Salesforce, Greenhouse, and Kantata were introduced largely in isolation, without overarching architecture governance or binding guardrails. Portamus established a TOGAF-based enterprise architecture spanning all four domains — business architecture, information system architecture, technology architecture, and integration architecture — and introduced architecture principles, review processes, and a structured evaluation procedure that now places all technology decisions on a solid architectural foundation.

IT Services Firm Establishes Full-Spectrum Enterprise Architecture Function
TOGAF-based enterprise architecture across all four architecture domains — with architecture principles, review processes, and decision support for a growing SaaS portfolio.
The Engagement at a Glance
Where the Organization Stood
A growing IT services firm operated a heterogeneous SaaS portfolio including Workday, Salesforce, Greenhouse, and Kantata without architecture governance — technology decisions were made without architectural guardrails.
No Architecture Governance
Without established EA governance, technology decisions were made in silos without cross-cutting assessment — creating increasing risk of redundancies and integration failures.
Heterogeneous SaaS Portfolio Without Integration Architecture
Workday, Salesforce, Greenhouse, and Kantata were operated largely in isolation — a coherent integration architecture was missing.
No Architecture Principles
No binding architecture principles existed to guide solution designs and technology evaluations across the organisation.
What We Did
TOGAF-Based Enterprise Architecture
Portamus designed the enterprise architecture using TOGAF across all four domains: business architecture, information system architecture (application and data), technology architecture, and integration architecture.
Architecture Principles and Governance
Binding architecture principles were established, compliance monitoring introduced, and a review process for submitted solution designs and architecture proposals was implemented.
Technology Evaluation and Market Trend Assessment
Portamus continuously assesses opportunities and risks from technology developments and market trends, providing architecture models and decision papers for leadership.
What Changed
Architecture Domains Covered
The EA fully covers all four TOGAF domains: business, information system, technology, and integration architecture.
Framework Implemented
TOGAF serves as the methodological foundation for all architecture decisions and review processes.
Architecture Principles
Binding architecture principles now govern all solution designs and prevent technology missteps.
SaaS Integrations Designed
Workday, Salesforce, Greenhouse, and Kantata have been embedded in the integration architecture with defined interfaces.
What Made This Engagement Work
EA Requires All Four Domains
An EA that focuses only on technology architecture and neglects business architecture does not create genuine business-IT alignment — all four domains must be developed coherently.
Architecture Principles as Guardrails
Binding architecture principles are the most effective instrument for steering decentralised technology decisions — they scale better than case-by-case reviews.
Technology Evaluation Is an EA Responsibility
Continuously assessing market trends and emerging technologies is a core enterprise architect responsibility — reactive technology adoption without architectural assessment carries too much risk.
More Client Outcomes
European Aviation Authority Designs ECCAIRS-Integrated Occurrence Reporting System
Optimisable digital system for managing internal aviation occurrences, required integration with European ECCAIRS standard
Process design for IORS, ECCAIRS integration architecture, SAP integration evaluation, staff training
IORS live (easa.europa.eu/iors), ECCAIRS integrated, EU-wide incident data exchange enabled
Fashion Retailer Builds ITIL-Compliant ITSM with Automated CMDB
No unified ITSM, missing CMDB, manual release processes without unified automation for host and Java workloads
ITIL CMDB with automated asset discovery, Nagios monitoring, ChangeMan z/OS release management, Serena PPM
Automated CMDB live, release management brought into production, SLAs and OLAs defined
National Healthcare System Consolidates ITSM Architecture Across 22 Hospitals
Fragmented ITSM across 6 hospital clusters, no unified monitoring for health-critical SLAs
End-to-end ITSM architecture across 8 process areas, SLA monitoring design, 4-system integration blueprint
Unified ITSM blueprint for $54M programme, SLA-capable monitoring, integration architecture delivered