Insights /Managed IT and Infrastructure

What should managed IT services include, and how should a manufacturing or SME define scope and pricing?

Managed IT should not be priced only by PC count. Inventory networks, servers, Active Directory, VMware, backup, permissions and remote access first, then define remote/on-site frequency, change windows, SLAs, documentation and project boundaries.

What should managed IT services include, and how should a manufacturing or SME define scope and pricing?
Key assessment

Establish a factual baseline with “asset and system scope” and “remote versus on-site support boundaries”, then move to “SLA”. Use scope, ownership, change control and acceptance as the evidence chain and avoid changing production before the fault boundary is clear.

Risk boundaries and prerequisites

Start by checking asset and system scope, remote versus on-site support boundaries and SLA independently. A healthy result for one of these checks does not establish the state of the entire service path.

Evidence and safe checks

CheckWhy it mattersRecommended action
01 · asset and system scopeChecking asset and system scope helps establish whether scope, ownership and acceptance evidence are clear; compare it with a known-good baseline and the incident timeline.Record the actual state of asset and system scope. Cross-check assets, responsibilities, change windows and recorded handover items before making changes.
02 · remote versus on-site support boundariesChecking remote versus on-site support boundaries helps establish whether scope, ownership and acceptance evidence are clear; compare it with a known-good baseline and the incident timeline.Record the actual state of remote versus on-site support boundaries. Cross-check assets, responsibilities, change windows and recorded handover items before making changes.
03 · SLAChecking SLA helps establish whether scope, ownership and acceptance evidence are clear; compare it with a known-good baseline and the incident timeline.Record the actual state of SLA. Cross-check assets, responsibilities, change windows and recorded handover items before making changes.
04 · change and maintenance windowChecking change and maintenance window helps establish whether scope, ownership and acceptance evidence are clear; compare it with a known-good baseline and the incident timeline.Record the actual state of change and maintenance window. Cross-check assets, responsibilities, change windows and recorded handover items before making changes.
05 · backup, account and documentation responsibilitiesChecking backup, account and documentation responsibilities helps establish whether scope, ownership and acceptance evidence are clear; compare it with a known-good baseline and the incident timeline.Record the actual state of backup, account and documentation responsibilities. Cross-check assets, responsibilities, change windows and recorded handover items before making changes.
06 · boundary between monthly reporting and separately billed projectsChecking boundary between monthly reporting and separately billed projects helps establish whether scope, ownership and acceptance evidence are clear; compare it with a known-good baseline and the incident timeline.Record the actual state of boundary between monthly reporting and separately billed projects. Cross-check assets, responsibilities, change windows and recorded handover items before making changes.

Investigation and change sequence

  1. Capture a baseline for asset and system scope and remote versus on-site support boundaries and compare it with a known-good system.
  2. Correlate evidence from SLA and change and maintenance window to distinguish the direct fault from dependent symptoms.
  3. Only if evidence points to backup, account and documentation responsibilities, plan a controlled change with backups, a change window and rollback triggers.
  4. Finally check boundary between monthly reporting and separately billed projects and the real business workflow. Have the client validate agreed business outcomes, configuration records, outstanding issues and ownership.

Validation and rollback evidence

  • Have the client validate agreed business outcomes, configuration records, outstanding issues and ownership.
  • Recheck backup, account and documentation responsibilities and boundary between monthly reporting and separately billed projects against the expected business outcome.
  • Retain initial configuration, event evidence, validation results and rollback triggers for production changes.

Common actions that increase risk

  • Assuming asset and system scope is sufficient while overlooking remote versus on-site support boundaries and dependent checks.
  • Changing several settings before preserving the original evidence for SLA.
  • Installation alone does not constitute acceptance or a maintainable handover.

Common questions and acceptance criteria

What should be checked first?

Begin with asset and system scope and remote versus on-site support boundaries. Capture reproducible errors and protect recoverable data before changing production.

What proves the issue is resolved?

Have the client validate agreed business outcomes, configuration records, outstanding issues and ownership.

What evidence should be retained?

Retain original logs, configuration snapshots, the approved change scope, business verification and rollback conditions.

InsightsNextHow should a factory network be redesigned? Segmenting office, production and server networks with VLANs and firewalls

Need an assessment for your actual environment?

Share the current topology, device models, system versions, symptoms, impact, maintenance windows and available configuration/backup information. We can first assess risk, scope and rollback needs, then define remote, on-site or project work.

Implementation reference

Related service and delivery evidence

For a production issue, confirm impact, recoverability and a verifiable rollback point before changing the environment.