Guides
Compare ICT Support Proposals by Scope and Site Access
Compare ICT maintenance proposals using a shared coverage matrix, clear response definitions, site-access conditions, exclusions and questions for suppliers.
DETIAN ICT · Tanzania & East Africa
Discuss your ICT project with DETIAN.
DETIAN ICT supports audiovisual, security, network and smart-building projects in Tanzania and East Africa, with design, equipment supply, installation and maintenance services.
Share your site location, required systems and available drawings or equipment list. Start a discussion about the work scope and the information still needed.
Put every offer against the same service requirement
Compare ICT support proposals by asking each supplier to complete the same coverage and responsibility matrix. Identify the sites and equipment, the work included, when support is available, what each response commitment means, and what the customer must provide. Resolve missing scope before comparing the total price.
For a facilities or procurement team responsible for an office, factory or project compound in Tanzania or elsewhere in East Africa, the useful output is a record of confirmed coverage and open questions. A heading such as “annual maintenance” does not tell you whether an offer includes remote investigation, travel, replacement parts or planned inspections.
This guide helps you prepare and compare a support enquiry. The worksheet is an original planning aid, not a DETIAN service package or a promise that a particular location, device or response target can be covered.
Fix the site and equipment boundary first
Create a dated scope list with one identifier for each site and system. Record the country, town, building or area, equipment category, known model, approximate quantity and operational owner. Give each supplier the same revision. Keep sensitive asset details in a controlled attachment if they are needed later.
Separate equipment under review from equipment already confirmed in scope. List existing warranties, subscriptions and manufacturer support references where known, then ask who will check their status. A supplier offering to coordinate a warranty claim is not necessarily offering replacement stock or repair labour within the same fee.
Mark the interfaces between providers. For example, a network team may investigate a connection while an internet provider controls the external circuit and an application supplier controls the affected service. Ask who opens each external case, who updates the site contact and which activities are excluded. Do not assume one proposal covers every connected system.
Use these rows in a comparison matrix
Use these columns: requirement ID; site or system; customer requirement; supplier response; included, excluded or conditional; evidence reference; customer dependency; and clarification owner. Add a separate supplier-response column for each offer. “Not stated” remains an open question; it is not an included item.
R1 — Covered assets and activities. Ask for the precise equipment boundary and whether the proposal includes fault investigation, configuration assistance, planned inspection, documentation updates or other named work. Keep enhancements and new installation separate from maintenance.
R2 — Support availability and case ownership. Record the contact channel, service days, working hours, time zone, holiday basis and escalation contact. Ask who can open a case and how an issue keeps the same reference when another provider becomes involved.
R3 — Remote work and site attendance. Ask what can be considered remotely, who authorises access, what triggers a proposed visit, and whether attendance, travel and accommodation are included or separately quoted. Keep the actual site location beside this row.
R4 — Parts and third-party charges. Ask who supplies replacement items, who checks eligibility, whether delivery and return handling are included, and who authorises an extra charge. Record confirmed stock or delivery information only when the supplier provides an applicable basis.
R5 — Planned visits and service records. Specify the systems and tasks proposed for each visit, any operating restrictions, the report to be returned and who reviews unfinished work. A visit count alone does not identify the work performed.
R6 — Customer responsibilities and exclusions. Record the local contact, permitted access, available documentation, agreed maintenance windows and dependencies on other teams. Require each exception to identify its practical effect and the next decision needed.
R7 — Commercial comparison basis. Compare the same period, sites, asset list, included visits and stated charging basis. Show conditional travel, parts, licences and other separately quoted work alongside the base fee. An unknown cost stays unknown until clarified; it should not disappear from the comparison.
Define response, attendance and restoration separately
Ask each supplier to name the event behind a proposed time target. Does it mean acknowledging the message, having a qualified person start investigating, arranging attendance, delivering a part, or restoring the agreed business function? Record when timing starts, which hours count, what customer input is required and how a delay is documented.
Microsoft’s Azure support page provides a useful example of precise wording: its initial response refers to a support engineer contacting the customer and beginning work. The page relates responsiveness to the support plan and business impact, and explains customer participation requirements. These are Azure-specific terms, not DETIAN commitments or benchmarks for onsite ICT work.
For your comparison, use a separate line for each offered milestone and leave absent commitments marked “not stated”. Ask how priorities are assigned from the effect on operations and who can change that priority. Avoid treating a response target as a guaranteed restoration time.
Have the operational owner identify the important business task and any approved temporary procedure. This helps suppliers discuss the required service arrangement without inventing a universal deadline or assuming every incident has the same urgency.
Check whether the site can support the proposed workflow
Prepare an access note for each location: permitted visiting hours; the person who arranges entry; induction or escort requirements; equipment areas that can be accessed; available local assistance; and who approves work that could interrupt operations. Keep personal details and access credentials outside the comparison sheet.
Ask the supplier to review these conditions against the offered workflow. If attendance requires an escort who is available only during certain hours, record that dependency next to the attendance arrangement. If remote assistance is proposed, have the authorised system owner agree its scope and method before access is granted.
Keep investigation, approval and execution as separate steps. A maintenance proposal should not silently authorise changes to accounts, safety systems or a live production network. Record who approves each type of work, how the planned effect is communicated and what evidence is expected afterwards.
For multiple sites, repeat the location-dependent rows. Confirmation for an office in one town does not establish the arrangements for a distant compound. Ask which conditions require a survey or further information before an offer can be confirmed.
Work through a hypothetical comparison before choosing
The following is an invented example, not a DETIAN quotation, customer case or market-price comparison. A team wants support for one office network and one meeting room at the same site. Offer A describes remote assistance and quotes site visits separately. Offer B lists two planned visits and remote assistance, but does not state whether replacement parts or additional fault visits are included.
In R3, record A’s site attendance as separately quoted; record B’s additional fault attendance as not stated. In R4, ask both suppliers to confirm parts, delivery and labour responsibilities. In R5, ask B which tasks the two planned visits cover and ask A whether an equivalent planned inspection can be quoted.
If both offers say “rapid response”, put that wording in R2 or the milestone record and request an actual definition from each supplier. Neither offer has supplied a comparable timing commitment merely by using the phrase. Also ask both to respond to the same site-access note and asset-list revision.
The next step is a clarification round, not an automatic winner. Request revised responses for the unresolved rows, keep the base and conditional charges visible, and have the operational owner check whether either offer meets the required workflow. Retain exceptions in the decision record even when a supplier is selected.
Keep the comparison useful after selection
Before service starts, record the accepted scope revision, covered locations and assets, support contacts, reporting channel, customer responsibilities and unresolved exclusions. Ask what service reports, visit records and updated documentation will be provided and who keeps them.
Use actual service records to review whether the agreed tasks were performed and which dependencies caused delays. Record the observed event and its time separately from the contractual target. Do not treat a closed ticket or a reachable device as proof that every affected business task has been restored.
When an incident occurs, use a concise fault report linked to the agreed scope. The separate fault-report guide below explains how to record symptoms and evidence without sending passwords; this comparison sheet establishes what support was agreed in the first place.
Send DETIAN the scope and the questions to resolve
For a support discussion, share the project country and town, site type, systems and equipment to be considered, operating hours, existing support arrangements, access conditions and desired work. Include the comparison rows that remain unclear and identify the person who can confirm the site details.
DETIAN’s public service page describes maintenance and technical support arrangements agreed around the location, equipment and operating requirements. Use the official contact page or [email protected] to discuss your scope. Site attendance, availability, responsibilities and response arrangements need confirmation for the specific enquiry.
