Cluster Naming Policy
1. Master Franchisee (Taluk-level Entity)
Legal Naming Format
OX [Location] Cluster Private Limited
Examples
- OX Palani Cluster Private Limited
- OX Dharapuram Cluster Private Limited
- OX Udumalai Cluster Private Limited
- OX Oddanchatram Cluster Private Limited
Rationale
- OX = Represents the organization brand.
- [Location] = Specifies the territorial jurisdiction (Taluk).
- Cluster = Represents the entire taluk-level ecosystem (Park + Nodes + Booking Centers + Outposts + Sub-franchisees).
- Private Limited = Ensures compliance, scalability, and investor readiness.
2. Sub-Franchisee (Service-level Operators)
Legal Naming Flexibility
Subs may be registered as:
- LLP
- Private Limited
Legal Naming Format
OX [Location] [Service] [Entity Type]
Examples
- OX Palani Spares LLP
- OX Palani Inputs Private Limited
- OX Palani Workshop LLP
3. Node Partner (Infrastructure Operators)
Nodes may be registered as:
- LLP
- Private Limited
Legal Naming Format
Since multiple Nodes will exist within one Cluster, each Node Partner must carry both the Cluster name and the Locality name for distinction.
OX [Cluster-Location] [Locality] Node [Entity Type]
Examples
- OX Palani Mayiladumparai Node Pvt Ltd
- OX Palani Keeranur Node LLP
- OX Dharapuram Kallimandayam Node Pvt Ltd
Operational Reference (Platform Use)
In addition to the legal name, Nodes may also be tagged with Node codes for internal platform reference and scalability:
- Palani Node-1 (Mayiladumparai)
- Palani Node-2 (Keeranur)
Rationale
- Node = Aligns with OX 4-Layer Network terminology (Layer 2 facilities).
- [Cluster-Location] = Ensures legal connection with the Master Cluster.
- [Locality] = Differentiates multiple Nodes in the same Cluster.
- Entity Type = LLP or Pvt Ltd depending on investment structure.
Usage in Communication
- Operational/Marketing: “Mayiladumparai OX Node operational with 3 sub-franchisees.”
- Legal/Contracts: “Node Agreement signed with OX Palani Mayiladumparai Node Pvt Ltd.”
- Platform Dashboard: “Palani Node-1 (Mayiladumparai).”
4. Distinction Between Concepts & Entities
| Concept | Usage | Example |
|---|---|---|
| OX Cluster | Operational/territorial concept | Palani OX Cluster |
| OX Park | Layer 1 physical hub facility | Palani OX Park |
| OX Node | Layer 2 local spoke | Mayiladumparai OX Node |
| OX Booking Center | Layer 3 customer interface | Ayakudi OX Booking Center |
| OX Outpost | Layer 4 temporary parking/deployment | Alamarathukalam OX Outpost |
| Legal Entity (Master) | Registered company operating the Cluster | OX Palani Cluster Pvt Ltd |
| Legal Entity (Subs) | Service-specific local operator | OX Palani Spares LLP |
| Legal Entity (Node) | Infrastructure-focused Node operator | OX Palani Mayiladumparai Node Pvt Ltd |
5. Filing Guidelines for CS/CA
- Always reserve the exact pattern for name of the Masters, Subs, and Node Partners.
- Master Franchisee: Must be registered as a Private Limited Company.
- Sub-Franchisee: Can be registered as a LLP or Private Limited Company.
- Node Partner: Must include Cluster Location + Locality + Node in the name; can be LLP or Pvt Ltd.
- Maintain a Master Naming Sheet to avoid duplication as OX expands across taluks.
✅ Policy Summary
- Masters: OX [Location] Cluster Pvt Ltd (uniform across India).
- Subs: Flexible but must carry service descriptor (Inputs, Spares, Workshop, etc.).
- Nodes: OX [Cluster-Location] [Locality] Node Pvt Ltd / LLP (to allow multiple Nodes per Cluster).
- Cluster vs Park: Cluster = umbrella ecosystem; Park = physical hub.
- Ensures clarity, uniqueness, and scalability across territories.