Your IFS applications run on resources dedicated to you alone — an isolated environment that is never shared with another customer or application, dimensioned to deliver the performance of physical hardware and sized to the server, network and security requirements IFS Global publishes. Hardware, network, operating system, Oracle, IFS application servers, backup, monitoring and disaster recovery are all managed by our team. You need neither your own datacentre nor an in-house infrastructure team.
An ERP that carries your operation needs the database, the application server and the network to be dimensioned together. On shared infrastructure the resource you paid for is contended for by someone else’s workload; when month-end closing slows down, no one can tell you whether the cause is your code, your database or a neighbour on the same host.
We start from IFS’s own requirement document — the server roles, resource sizes, network and security requirements published by IFS Global are the specification, and the resources are dedicated to you alone — isolated, not contended for. The same team that runs your Oracle database and IFS application servers also operates the infrastructure underneath them.
No hardware to purchase, no datacentre contract to sign.
No in-house infrastructure team to build and keep.
No sizing guesswork: the requirement comes from IFS, the measurement from us.
Production, development and test environments are provided as separate server sets — because a version upgrade you cannot test is a risk you carry into production. Each environment gets its own Oracle database and application server; management servers are added for the IFS Cloud version, and e-application, portal and document management servers are provided when your licence covers them.
The boundary is drawn in writing before the service starts, so no layer is left to “whoever notices first”. You use the application and own your data; every layer beneath it — down to the datacentre network — is operated, patched, backed up and monitored by us.
| Layer | Owner |
|---|---|
| Data and usage | You |
| IFS application | DBO |
| Monitoring | DBO |
| Backup | DBO |
| Installation and version work | DBO |
| Runtime and middleware | DBO |
| Oracle database | DBO |
| Operating system and patching | DBO |
| Virtualisation | DBO |
| Servers and storage | DBO |
| Datacentre network, firewall, DDoS | DBO |
Server roles sized to the resource, network and security requirements published by IFS Global — on resources reserved for you and isolated from any other customer or application, performing like physical hardware.
The network and security layer the environment needs, including DDoS protection, is set up and operated as part of the service.
Internet bandwidth at the access speed IFS requires, so that client performance is not limited by the connection.
Database and application server backups follow the strategies IFS and Oracle recommend; retention is 14 days and a copy is kept in a second, geographically separate datacentre.
A disaster recovery environment in a different city and datacentre, holding continuous copies of the live system.
Critical patches and security updates for IFS application and database servers are in scope, as long as IFS approves their compatibility with the IFS release.
Emergency system support followed by a technical team with genuine IFS and Oracle expertise, around the clock, inside agreed response times.
The monitoring and reporting system is set up and managed by us; regular system health reports land with you rather than being asked for.
Where measurement shows it is needed, database performance work is carried out as part of the service — not quoted as a separate project.
Continuity is not a promise, it is a topology: backups follow the strategy IFS and Oracle recommend, a copy leaves the primary site, and the disaster recovery environment sits in a different city and datacentre in active-passive mode. Restore tests are part of the operating routine, not something discovered on the day of the incident.
| Site | Holds | Purpose |
|---|---|---|
| Primary datacentre | Production, Dev, Test | live operation |
| Second city / datacentre | Continuous copy of production | disaster recovery |
| Separate datacentre | Backup copy · 14 days | restore and audit |
Tell us your IFS version, user count and the environments you need; we will come back with the server roles, resources and continuity topology that fit.