Set up, secure, run and develop your complete company IT under a binding operating constitution.
From a message to a technically set-up, protected website, with a clear structure and ongoing care.
Bespoke platforms, portals and interfaces: specified, programmed, tested and integrated.
Digital assistants take in the work; rule-bound processes deliver checks, approvals and documented results.
Operational infrastructure from the network, on its own or as part of a complete IT landscape.
The binding framework of order: manifesto, charter and operating constitutions.
The operational order for IT landscapes: 14 domains, mandatory artefacts, evidence.
The Sulek Intelligent Process Execution System: rules become managed processes.
Companies, specialists and infrastructure in several countries, coordinated by contract.
The IT operating constitution.
A universal target model for describing, planning, securing and operating a complete IT landscape – and the normative basis for service catalogue, offers and contracts with a clear division of responsibility.
Prescription, not description.
Universal
across sites and clients; client and jurisdiction parameters via scope and profiles.
Auditable and evidential
Evidence is part of the landscape, not an afterthought.
Clear division
between client and service provider, defined per domain.
Locked by default
Access only through authorised, encrypted paths and controlled release.
Stable changes
Updates and patches risk-based, tested and controlled.
Order of precedence
Contract before scope, deviations and responsibilities – then the constitution.
14 domains in five areas.
A site ends where the platform begins that carries the workloads. Above it lie structure and continuity, the uniform working environment, the external interfaces and the commercial basis.
Sites
site-boundDomain 1 · Physical basis
Rooms, rack and zone structure, fire protection, access, cable routes.
Domain 2 · Power and climate
Power paths, uninterruptible supply, emergency power, cooling, sensors.
Domain 3 · Hardware
Servers, storage, separate out-of-band management, life cycle.
Domain 4 · Platform and virtualisation
Clusters, high availability, templates; backup target separate and tamper-protected.
Structure and continuity
cross-site, onceDomain 5 · Replication and fallback
Workloads move to another site in case of failure.
Domain 6 · Backup topology and recovery objectives
Redundant backup, retention, mandatory restore and failover tests.
Domain 7 · Namespaces and base rules
Names, time base, certificates, identity anchor – the same everywhere.
Uniform IT working environment
onceDomain 8 · Systems and roles
Standardised operating systems, hardening, patch rules.
Domain 9 · Applications and services
Applications, databases, communication – recoverable.
Domain 10 · End devices
Policies, software distribution, workplace operation.
Domain 11 · Identities and access
Permissions, strong authentication, recertification.
Domain 12 · Security, operation and control
Controls, evidence, service organisation; leads all control rules.
External interfaces
industry-neutralDomain 13 · Interfaces and data flows
Partners, client portals, remote support, cloud, payment and authority channels – with handover point and evidence.
Commercial basis
per landscapeDomain 14 · Operational and resource management
Contracts, licences, suppliers and costs related to IT.
Mandatory artefacts and global control rules
Scope
Coverage, parameters, exposures, cloud, allocation of services.
Applicability
Per domain applicable or not, with reasons.
Responsibilities
Client, provider and third parties per domain and building block.
Deviations
Each deviation with risk analysis, compensation, approval, liability class.
Evidence and checks
All evidence, logs and retention periods.
Jurisdiction and requirements
Seat, data protection, roles, deletion duties, third-country transfer.
Steered by risk: HR1 to HR3.
critical / liability-relevant
Existential, statutory duties; an omission can lead to personal liability of management.
evidence mandatory · restore and failover tests mandatory · deviations only with risk analysis, compensation and approval · periodic review of access
essential / duty of care
Strong influence on operational safety and state of the art.
evidence largely mandatory · tests where dependence is high · deviations on protection topics documented
standard / operational
Important for efficiency and quality; errors cause disruption without direct legal consequences.
minimum documentation · tests as needed · deviations handled operationally
What is checked – and what applies.
D1 Restore tests
according to protection needs; mandatory and logged for HR1.
D2 Failover tests
replication and switchover, results kept as evidence.
D3 External visibility
periodically: which endpoints are visible from outside?
D4 Access releases
periodically checked and evidenced.
Cooperation
Agreed rules are observed; unauthorised interventions count as deviations.
Jurisdiction profiles
DACH and international; with several jurisdictions the stricter duties apply.
Connected to recognised standards.
The IT operating constitution is aligned with ISO/IEC 22237 and EN 50600 (data-centre infrastructure), the tier principles of the Uptime Institute, ISO/IEC 27001/27002 (information security), ISO/IEC 20000 (service management) and ISO 22301 (continuity). These standards are reference frameworks; the binding requirements follow from the constitution and the contracts. Certifications are separate projects.
How we apply it in your IT landscape →Let us talk about your company.
Write to us in English, German or Spanish. You will receive the answer directly from Atlantic Bridge Exchange.
sulek@techcenter.infoBy post: Atlantic Bridge Exchange Ltd, Unity House, Suite 888, Westwood Park, Wigan WN3 4HE, England
Atlantic Bridge Exchange Ltd
Registered in England and Wales, company number 16995192.
Registered office: Unity House, Suite 888, Westwood Park, Wigan WN3 4HE, England