Planning an ICT Project in East Africa

1. Describe the business and daily use

Describe the activities the site needs to support: office work, remote meetings, production coordination, visitor entry or facilities management. Identify the people using each space, approximate numbers and working patterns. A room list or annotated site plan is a useful starting point.

Separate essential opening requirements from later improvements. For an existing site, explain the current problem and its effect on operations. Describe the outcome you need instead of specifying only a product, such as enabling remote participants to hear a meeting clearly.

• List key spaces, users and operating hours.
• Identify what must be ready before the site opens.

2. Investigate network, power and physical conditions

Confirm what is already available at the actual location. Internet service, internal cabling, equipment space and power arrangements should be investigated for that site. Record the source and date of information; do not assume conditions at another property apply to this one.

Share available drawings and photos, noting areas that remain inaccessible or unverified. Discuss whether a site survey is needed before final design. Existing equipment, cable routes, environmental conditions and backup power needs can affect both the proposed system and installation work.

• Mark existing network, power and equipment locations.
• Keep a list of conditions that still need checking.

3. Coordinate the four system areas

Review AV and collaboration, security and access, networks and data rooms, and smart building controls together. They may share cabling routes, equipment space, power or network connections. Planning these dependencies early helps expose missing work and incompatible assumptions between suppliers.

For each required connection, identify the systems involved, the intended function and who should confirm compatibility. Integration should be discussed explicitly; equipment on the same network does not automatically provide a coordinated user experience. Also record who will administer users, settings and access permissions.

• Name shared infrastructure and system interfaces.
• Assign an owner to each compatibility question.

4. Compare scope and acceptance, as well as equipment

Use the same project brief when requesting proposals. Compare equipment quantities and specifications alongside design, delivery, installation, configuration, testing and training. Ask suppliers to state exclusions and work expected from others, such as preparing equipment space or providing access to the site.

Agree acceptance criteria before ordering. Define the functions to demonstrate, the locations to test and who will sign off the results. Record how outstanding items and changes will be handled. A clear scope makes differences between offers easier to discuss without relying on the total price alone.

• Request an itemised scope with assumptions and exclusions.
• Agree test records and the acceptance decision process.

5. Plan handover and maintenance information

Discuss what the operating team should receive at handover: equipment lists, agreed drawings, configuration records, test results and user instructions. Agree how administrator access and configuration backups will be transferred securely. Name the people who need training and the tasks they should be able to perform.

Maintenance arrangements should reflect the location and equipment. Clarify warranty responsibilities, fault reporting, spare parts and any planned inspections. Discuss site access, travel and remote assistance where relevant, and record the agreed scope and response arrangements instead of assuming a particular service level.

• Name the person responsible for keeping project records.
• Agree support responsibilities before final handover.

6. Prepare a brief for a project in another location

For Chinese enterprises developing or operating sites in East Africa, a shared brief can help headquarters, procurement and local teams work from the same information. Include the country, town, site type, local contact and any access arrangements that may affect a survey or installation.

Send DETIAN ICT the information below, together with any available plans. State which points are confirmed and which need discussion. If the project covers several sites, list their requirements separately and identify any standards you want to share across them.

• Identify one contact for decisions and one for site coordination.
• State preferred communication language and project milestones.

A six-part project brief

Use these headings in an email or document. Unknown items can be marked “to be confirmed”.