Factories
List office IT and servers separately from production controls. Agree maintenance windows and coordinate any production-system changes with the authorised equipment vendor.

Compare responsibilities, coverage and evidence before comparing the monthly fee.
An internal IT team owns day-to-day context. An outsourced provider takes responsibility for an agreed service scope. A co-managed arrangement divides responsibilities between them. The right choice depends on your existing skills, critical systems, locations and support hours—not company size alone.
| Model | Useful when | Clarify before choosing |
|---|---|---|
| In-house team | You need close daily involvement and have resources to recruit and manage the required skills. | Holiday cover, specialist skills, tools, documentation and escalation. |
| Outsourced support | You want an external team to own a defined set of support and maintenance tasks. | Included systems, response targets, on-site arrangements, reporting and access ownership. |
| Co-managed support | Your internal staff need help with selected systems, workload or specialist projects. | A responsibility matrix: who accepts requests, approves changes and closes incidents. |
Illustrative planning scenario, not a customer result or a price offer. User count alone cannot define the work. For a two-site company, prepare the following information so suppliers quote against the same scope:
Ask for recurring support, onboarding, project work, equipment, licences and travel to be shown separately. This makes proposals easier to compare without assuming an unverified market price.
| Topic | Ask for a clear answer |
|---|---|
| Scope | Which devices, applications, sites and tasks are included or excluded? |
| Response and resolution | When does the response clock start, what are the priorities, and how is progress escalated? A response target is not a guaranteed repair time. |
| Changes | Who approves a restart, access change, patch or configuration change, and what is the rollback procedure? |
| Reporting | How are recurring incidents, completed maintenance, open risks and pending approvals reported? |
| Account ownership | Does the company retain control of domains, tenants, licences and administrator access? |
| Exit and handover | How are documentation, access, open tickets and supplier contacts handed over at the end? |
IT outsourcing is priced against a defined environment and support scope. User and device counts, sites, servers, operating hours, on-site visits and specialist responsibilities all affect the quotation. IT Genesis prepares a tailored proposal after reviewing these requirements.
| Cost category | What to confirm |
|---|---|
| Recurring support | Included users, devices, sites, service hours and tasks; how additions or scope changes are priced. |
| Onboarding | Initial review, documentation, access setup and any remediation needed before normal service begins. |
| Visits and travel | Included visit frequency and duration, locations, travel charges and additional emergency visits. |
| Tools and third parties | Microsoft 365, security, backup and monitoring licences; which subscriptions the customer owns and pays for. |
| Projects and equipment | Migrations, installations, replacement parts and hardware purchases, itemised separately where excluded from support. |
Compare the total for the same contract period: recurring fees, one-time work, agreed extras and applicable taxes. Ask for the currency, quotation validity, renewal terms and any usage limits. This guide gives a comparison method, not a published price list or an average market rate.
A service-level agreement (SLA) should define the priority, service window, target, escalation owner and measurement method. A first response, restoration of service and a permanent fix are different milestones. A workaround can restore work while the underlying problem remains open.
| Priority | Illustrative business impact | Agree in the SLA |
|---|---|---|
| Critical | An agreed business-critical service is unavailable and affected users have no workable alternative. | Coverage hours, first response, update frequency, escalation and a restoration objective. |
| High | A major department or workflow is disrupted, with only limited alternatives. | Affected users, available workaround, response target and coordination with other vendors. |
| Normal | A limited user issue with a usable workaround and no critical operational interruption. | Response target, appointment arrangements and the next progress update. |
| Service request | A planned installation, user setup or approved configuration change. | Approvals, prerequisites and a scheduled completion date. |
These are planning examples, not IT Genesis response-time commitments. The signed scope sets the actual targets. Record when each clock starts, any permitted pauses, how after-hours incidents are handled and who can change a priority. Include evidence for time waiting on customer approval or a third-party supplier.
Agree the calculation and data source for every KPI. Use the report to identify recurring problems and decisions that need an owner.
For factories, document peak production hours and authorised maintenance windows. For shipping offices, identify shared email, booking and document workflows. Monitoring trends can support capacity planning and preventive action; they cannot guarantee that every failure will be predicted or prevented.
List office IT and servers separately from production controls. Agree maintenance windows and coordinate any production-system changes with the authorised equipment vendor.
Identify shared email, quotation workflows, documents, sites and operating hours. Read the marine IT support scope.
Distinguish guest connectivity, office IT and specialist hotel systems. Define who owns each supplier relationship and when work can be scheduled. Explore hospitality technology.
List connectivity, local contacts and critical systems for each branch. Define which tasks can be completed remotely and when a site visit is required.
Ask a prospective provider for an example report without customer data, a proposed onboarding checklist, an escalation route and references they are authorised to share. A product demonstration can show how a tool works; it does not prove a customer outcome or a service-level commitment.
IT Genesis publishes product information for Endpoint Manager, ITNX and Mail Insight. Review the relevant product scope and request a demo where useful; product licences and features are not automatically part of every support agreement.
Read the cloud backup and disaster recovery comparison guide
Only compare prices after checking equivalent scope. Missing visits, licences, onboarding or project work can change the total cost.
Only if expressly agreed. Record service hours, out-of-hours arrangements and priorities in the agreement.
Service enquiries are welcomed from businesses across Egypt. Remote support, visits, travel costs and response arrangements are agreed for the location and scope. Review coverage details.
Send a short description of your systems, locations and desired outcome. We will review the brief and discuss the scope and next step.
Contact IT Genesis