Quickstart

This walks you from a fresh account to your first Jax-driven design, then to a branched, saved plan — in well under fifteen minutes. No code required.

Core concepts

You will touch every major part of Nexma in one pass: create a Project, bind an Ontology and a Skill, load some data, design with Jax, review on the Globe, and branch to save an alternative. If any term is new, the Introductory concepts page defines all of them in one screen.

1. Create an account and organization

Sign up, then create or join an organization. Your org is the boundary for members, roles, projects, and shared Skill libraries. Everything you build belongs to the org, not to a personal account, so colleagues can pick it up later.

See Authentication and access.

2. Create a project

From Projects → New, give the project a name and bind its world model:

1. Pick an Ontology — the typed world model for your domain (FTTH, water, electric, and more).
2. Add one or more Skills that target that ontology, such as FTTH Network Design.
3. Or simply describe what you're building in natural language — Jax will propose a matching ontology and skill, and set the project up for you.

Each project gets its own Globe view and its own Jax session.

3. Load some data

Open the Globe and scope your work. Search or zoom to your area of interest, then draw a polygon — it is saved into the project as an entity you can reuse, edit, or hand to Jax. To bring in real-world data, connect a feed through Nexma SyncEngine (addresses, parcels, existing assets, terrain). Spatial feeds render on the Globe automatically.

See Nexma SyncEngine and live data.

4. Ask Jax to design something

Open the Jax panel and describe an outcome. Use a request shaped by your domain:

• FTTH: "Generate a feeder and distribution network for every household in this polygon, respecting splitter ratios."
• Water: "Lay out a pressurized network from the existing main, respecting elevation and a 40 m pressure budget."
• Electric: "Add a 15 kV feeder loop with branch fuses every 200 meters."
• Logistics: "Plan delivery routes for these 80 stops from the depot, minimizing total drive time."

Jax plans the work, calls Nexma MathEngine for the optimization, and streams the result onto the Globe. The map updates live as it works.

5. Inspect, refine, ask why

Click any feature on the Globe to read its full record. Right-click to pin it into the Jax conversation as context. Then push on the design:

• "Why did you pick this splitter location?"
• "What changes if cabinet capacity drops to 144 ports?"
• "Cost-optimize the trench layout but keep the same coverage."

You see every step. Nothing is hidden, and every edit is a real, reversible change to the project.

6. Branch, review, and save

When you want to explore an alternative without disturbing the approved plan, branch the DataStore. Work on the branch, compare it against main — entities added, links rewired, constraints checked — the way a reviewer reads a pull request. Merge it back when the plan is approved. Main is the operational truth; branches are where you experiment safely.

See Spatial Branches.

Where to go next

• Get oriented in The workspace.
• See the full path from problem to production in Delivering a use case.
• Find your role-specific reading in Next steps by role.
• Hand work to crews via the mobile app.