Guides
Office Network RFQ: Map Connection Requests to the Right Places
Prepare an office network enquiry with matching floor-plan markers and connection-request rows, separating proposed locations, existing outlets and unresolved site questions.
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.
Match each connection request to an identifiable place
Before requesting a quotation for an office network, give each requested connection a stable identifier and place the same identifier on the relevant floor plan. Record what needs to connect there, whether the location is agreed or still proposed, and what is known about the existing installation. A room total alone does not tell a designer where the requirement belongs.
For a new office or an upgrade in Tanzania or elsewhere in East Africa, this helps the owner, procurement team and site contact discuss the same locations. DETIAN’s network FAQ asks for the number and location of users and devices, building layouts and existing cabling information. The worksheet below makes that part of an enquiry more specific.
This is an original manual requirements record, not a network design, an installation drawing or a promise that an existing outlet can be reused. Cable routes, outlet quantities, wireless design and equipment selection still need review for the actual site.
Identify the drawing before adding location markers
Write the site, building, floor, drawing title, revision and issue date at the top of the schedule. State whether the drawing represents the current layout, a proposed fit-out or an older record that has not been checked. A PDF received yesterday may still show last year’s furniture arrangement.
Use the room identifiers already agreed for the project. If the team needs temporary names, label them as working references and keep a small room-name crosswalk. “Office 1” on the ground floor and “Office 1” upstairs must not become one location simply because their names match.
Place each request marker at the intended work area and add a short description, such as “reception desk, visitor-facing side.” Mark a proposed location as proposed. A mark on an unscaled sketch is a way to discuss position; it is not a verified distance, mounting height or cable length.
Keep the request, the device and the existing outlet separate
A request identifier describes a requirement under discussion. An equipment identifier describes a particular device, where known. An outlet label describes a physical point recorded at the site. Keep these fields separate so the drawing does not imply that a requested connection already exists or that one visible outlet will satisfy it.
For each request, state the activity and the device or device group involved. Write whether a wired connection is requested, wireless service is requested, or the connection method still needs advice. Do not turn a count of seats into a fixed count of outlets or access points without the relevant design decision.
If an existing outlet is relevant, record the visible label and the source of that observation. Its presence does not establish its destination, condition or suitability. Mark an old drawing reference as unverified until the responsible person checks it; do not ask office staff to open equipment, disconnect cables or test live systems to complete this enquiry.
Where a device may need network-delivered power, keep the device requirement as an open technical question unless supported information is available. The separate PoE schedule deals with per-port and shared power requirements after the relevant devices and design assumptions have been identified.
Create a location schedule the supplier can answer
Use one row for each separately identifiable request. Suggested columns are: request ID; drawing and revision; building, floor and room; position description; intended task; device reference if known; requested connection method; opening or later phase; related existing outlet label; evidence and observation date; confirmation status; and question owner.
When a row covers a repeated group, name the individual positions or explain exactly which marked area the group covers. Split the row if the locations, devices or phases need different answers. “Ten points somewhere in the office” cannot show which areas were included in the quotation.
Keep requirement status separate from site-evidence status. The owner may confirm that a printer is needed at a position while the existing cabling there remains unverified. Conversely, a labelled outlet may be visible in an area whose future use is not yet agreed. A single green “confirmed” cell would hide that distinction.
For each unresolved item, write a question that someone can answer: “Which layout revision shows the approved reception desk?” or “Who can confirm whether outlet label O-17 belongs to this position?” Assign a contact or role without assuming that the supplier has accepted the investigation as part of its scope.
Work through a fictional two-room example
The following identifiers and circumstances are invented for this exercise; they are not a DETIAN project, measured installation or recommended network layout. Drawing L-02, revision B, shows a reception area and a shared workroom. The owner requests a connection at the reception workstation and one for a shared printer in the workroom.
Row R-01 refers to the reception workstation and its marker on L-02 B. The request is confirmed by the owner, but the final desk position is still proposed. An older drawing shows outlet O-17 nearby; the schedule records that source and leaves its current position and suitability unverified. It does not mark the request as already served.
Row R-02 refers to the shared printer, equipment reference PR-01, at the marked workroom position. A separate department list also mentions PR-01 under reception because that team uses it. The coordinator asks whether both entries describe the same shared device and records the answer before treating them as separate connection requests.
If the owner confirms that PR-01 is one shared printer, keep one location request and identify both user groups. If a second printer is actually required, add its distinct device reference and location request. Similar names alone do not justify merging entries, and two department mentions alone do not establish two devices.
If the desk later moves, keep R-01 as the same requirement where appropriate, revise its location reference and identify which drawing and supplier response need review. Do not leave a revision-B quote appearing to cover a revision-C position without checking the affected scope.
Attach site context without inventing an installation route
Include the project address, site contact, intended operating date and known restrictions on access or interruption. Identify equipment-room locations and existing drawings where available, with their source and verification status. Share only plans and photographs authorised for the enquiry; exclude credentials and unnecessary sensitive detail.
Photos can help identify a marked area when their references match the schedule. A close-up of an outlet is easier to interpret alongside an authorised wider view that locates it in the room. Do not use a photo to infer an unseen cable route, a tested connection or a safe working method.
Keep confirmed opening requirements separate from possible later expansion. The supplier can then explain how each phase affects its proposal. An expansion note is a request to discuss provision, not an instruction to add a universal spare percentage or assume capacity is already available.
Ask the project team whether a site survey is needed to resolve the remaining questions. The enquiry can identify inaccessible areas and required permissions without prescribing electrical work, ceiling access or changes to an operating network.
Compare replies against the same location revision
Send the marked plan and schedule together, each with its revision. Ask the supplier to reference the request IDs, explain the proposed treatment of existing outlets and list assumptions, exclusions and information still required. The reply should make clear which locations and phases it covers before its equipment totals are compared.
Check the relationship in both directions: every schedule row should lead to the intended place on the named drawing, and every request marker on that drawing should lead to a row. Resolve missing, repeated or ambiguous IDs explicitly. This checks the enquiry record, not network performance or installation acceptance.
If the supplier proposes a different location or connection approach, retain the original request and record the proposed change, reason and person responsible for the decision. Update the shared revision only after the relevant parties confirm it. A marked-up proposal is not automatically the approved or installed arrangement.
Keep any later design, test and handover records identifiable by their own purpose and status. The location schedule helps define the enquiry; the project’s agreed acceptance and handover process remains separate.
Send DETIAN a specific network enquiry
For an initial discussion, prepare the country and town, facility type, current or proposed layout, location schedule, existing information and unresolved questions. Name who can confirm user requirements and who can arrange site access. State whether the request concerns a new installation, an extension or an existing office.
DETIAN’s public pages describe network and data-room solutions alongside design, equipment supply, installation and support. Use the official contact page or [email protected] to discuss the actual site and required scope; the Tanzania contact number is +255 723 666 959. Confirm survey arrangements, deliverables and responsibilities for this enquiry rather than assuming a fixed service package.
