Dispatch path
Kolkata is handled through TYTEC dispatch with vetted local partner alignment once site, access, and evidence requirements are clear.
Regional node console
Kolkata node ready
Use the command router for a short operational readout, then continue into the local node profile below.
NODE: KOLKATA REGION: ASIA FACILITY MAP: MARKET CONTEXT PENDING COVERAGE: PARTNER LED DISPATCH: VETTED PARTNER LANGUAGES: ENGLISH / BENGALI READY: LOCAL CAPABILITY PROFILE ONLINE
tytec.ai/cities> load-node kolkata --tier 3 --coverage partner-led
Regional context
Lighter India page when the request is scoped and evidence requirements are explicit. This node is dispatch-supported; include facility name or address, access method, and required evidence to confirm execution.
Command router
Kolkata command surface
Type a command or use the chips below to load node status, geo, service, facility, and dispatch views for Kolkata.
Operational city page
TYTEC in Kolkata
Kolkata is a TYTEC.ai city node for structured datacenter field execution in India, operating in partner led mode with vetted partner coordination and support in English and Bengali. Send facility, access, timing, and evidence requirements up front so TYTEC can confirm the dispatch path before work starts. TYTEC.ai is the operational layer; use TYTEC.se/contact for formal intake and reference the Kolkata node in your request.
TYTEC.ai and TYTEC.se
This TYTEC.ai page is the canonical operational source for Kolkata. TYTEC.se remains TYTEC AB's company, trust, and formal inquiry site.
Coverage model
How this node is operated
Coverage type, team status, and language support are shown in the node console and hero. This section defines what the operating model means in practice.
This node is partner-led: TYTEC coordinates the request, confirms site and access details, and aligns vetted local delivery against explicit evidence requirements.
Services
Services this node supports
Use the same structured request model across all TYTEC nodes. Coverage type affects routing, not the clarity of the deliverable.
- Remote hands verification (photos, labels, console notes)
- Simple patching or reseat tasks (where authorized)
- Rack work (swap, move, label, staging)
- Basic troubleshooting (hands + eyes, guided by your runbook)
- Decommissioning assistance (pulls, packing, labeling)
- Access mediation support (escort coordination, handoff alignment)
Required inputs
What to send before dispatch
Clear inputs produce reliable outputs. This is the fastest way to reduce back-and-forth and confirm the dispatch path.
- Facility or site name (and street address if ambiguous)
- Room / hall / cage / rack identifier
- Task definition and success criteria
- Approved window (local time) and urgency classification
- Access status (badge, pre-approval, escort, loading constraints)
- MOP / runbook link or attached steps (if applicable)
- Evidence requirements (photos, serials, labels, console outputs)
- Escalation contacts (primary + backup) and comms channel
Example request
Copy-paste request template
Use this format when opening a formal request. It makes the TYTEC operating model explicit and reduces handoff friction.
Subject: Kolkata | Remote hands | <site> | <rack> | <date/time local> City node: Kolkata Site / facility: <facility name> (<address>) Location: <room/hall/cage/rack> Task: <one sentence> Steps / MOP: <link or attached> Access: <badge/escort/loading/security> Evidence needed: <photos/serials/labels/console outputs> Escalation: <name + phone + email> Close-out format: <single summary + evidence bundle>
Evidence standards
What close-out should include
Evidence is part of the deliverable. Requests should define the expected close-out standard before work starts.
- Photos: wide shot for context, then close-ups for labels and ports
- Serial and asset capture: record exact serials for touched hardware
- Before/after: show state change for every action that matters
- Console observations: include timestamps, LEDs, error screens, and anomalies
- Handoff: one-paragraph summary plus evidence pack (zip or shared folder)
After-hours
After-hours dispatch rule set
After-hours requests are viable when access, timing, and evidence expectations are already clear.
After-hours work should clearly state local access status, escalation contact, and evidence format because overnight dispatch often crosses time-zone boundaries.
Datacenter context
Datacenters in and around Kolkata
This node is dispatch-supported; include facility name or address, access method, and evidence requirements to confirm execution.
Facility reference layer
Dispatch-supported routing
- No named facility references are published yet for this node
- Requests should include site identity, access path, and evidence requirements
Operator note
What improves this node next
- Add campus or facility references once the site identity can be verified
- Prefer exact facility naming over generic metro-level wording
Dispatch-supported node
Kolkata can be routed with a defined site and access path
This node is dispatch-supported; include facility name or address, access method, and evidence requirements to confirm execution.
Formal intake
How to send the request
Send the formal request via TYTEC.se/contact, reference the Kolkata node, and include the structured request template above.
Related cities
Related nodes
Use related nodes when a runbook spans multiple metros or when the nearest viable execution path sits outside a single city.