No-account synthetic demo

Database Administration

Create no-account schemas and synthetic/demo records for any database object. Map records appear on the dashboard Design-mode planning assets layer.
Open Map Design Layer
Administration boundary
The backend uses a no-account demo engineer for edits. Keep all records synthetic/demo unless imported and verified later.
Object types
0
Design records
0
Map-visible records
0
Work-linked records
0
Design database guide
A quick playbook for using GridAssetLink as an editable design database and work-order system.
1
Start with a design objectInstall the core schemas or choose a template, then create a synthetic record with the minimum fields needed for planning.Use templates
2
Edit the living recordUse the record browser to search, select, update properties, redraw geometry, duplicate similar assets, or archive stale assumptions.Open editor
3
Use status as workflowKeep rough ideas as proposed, move reviewed designs to planned, use in_review for field/engineering review, and reserve as_built for verified closeout.Review statuses
4
Issue field workCreate work orders from selected records when a design needs site verification, installation, splicing, commissioning, or closeout evidence.Issue work order
5
Materialize carefullyMaterialize only supported synthetic records into module tables after review. Materialization does not make an assumption real or verified.Use backend mapping
6
Protect the data boundaryDo not enter CEII, operational telecom, SCADA, relay/protection settings, credentials, or private fiber-route details.Synthetic only
Open no-code guideOpen map design modeView work ordersImport / Export
Required parameters for full database integrationDefine these fields before saving a custom object type or materializing design records into backend modules.
Identity and sourceGive every object a stable identity before it is linked to map layers, modules, traces, or work orders.
object_typerecord_keydisplay_labelsourcevisibilitysynthetic_or_verified_status
Lifecycle and reviewTell the database where the record is in the design lifecycle so proposed work does not look like active infrastructure.
statusvalidation_statusapproval_statusreview_notesmaterialization_modeas_built_evidence
Geometry and map behaviorDefine whether the object appears on the dashboard map and how users should interact with it.
geometry_typegeometry_or_locationmap_styledashboard_layerservice_territoryplacement_notes
Relationship keysCapture the IDs that let the object interact with the rest of the planning database.
parent_ida_end_idz_end_idcable_idstrand_numberssplice_idspatch_panel_iddevice_idcircuit_idwork_order_id
Engineering parametersAdd type-specific fields that make the object useful for planning, validation, and field execution.
asset_typeowner_or_groupcapacityfiber_countport_or_strand_rangeservice_typecriticalityloss_or_latency_target
Work, evidence, and continuityDefine what proves the record is ready, installed, tested, or safe to materialize into module data.
required_evidenceacceptance_criteriacloseout_statuscontinuity_trace_idoutage_impact_flagrollback_plan
How objects interact with the rest of the databaseUse these paths to connect records to map layers, backend modules, fiber continuity, devices, services, circuits, and work orders.
Map dashboard interactionClickable map objects need geometry, display labels, lifecycle status, and a dashboard layer assignment.Open Dashboard Design Mode -> Draw or select the object -> Edit generated fields -> Open linked module or issue work
Backend module interactionModule rows need stable record keys and backend entity mapping so reviewed design records can be materialized safely.Create object type -> Fill required fields -> Set materialization mode -> Materialize after review
Fiber and splice interactionContinuity depends on explicit cable, strand, splice, patch-panel, and endpoint IDs.Create cable or span -> Generate or enter strand rows -> Add splice rows -> Trace continuity
Device, service, and circuit interactionServices should connect device ports, LIU/patch-panel ports, strands, splice IDs, and A/Z endpoint records.Create endpoint devices -> Capture ports -> Reserve strands -> Assign service -> Open fiber trace
Work-order interactionLiving design records become actionable when scope, affected assets, evidence, and closeout states are linked.Select source record -> Issue work order -> Add tasks and evidence -> Review closeout -> Update lifecycle status
Assign a service from one substation LIU to anotherUse this sequence when inserting endpoint devices, reserving strands, building the splice path, and assigning a circuit or service across synthetic planning fiber.
1. Build both substation endpointsCreate or select the A-end and Z-end substations, then add each substation LIU or patch panel as a design object with rack, panel, port count, and location fields.
2. Insert devices at each endAdd the endpoint devices, such as SEL ICON, relay, RTU, router, or switch records. Capture device name, type, manufacturer, substation, rack, device ports, and the LIU port each device lands on.
3. Create the fiber cable and strandsAdd the cable route between the substations, then add strand records for the cable. Track fiber count, tube/color, strand number, strand status, A-end LIU, Z-end LIU, and whether each strand is available, reserved, assigned, or retired.
4. Add splice closures and splice rowsPlace terminal or inline splice closures at each LIU transition, route junction, or structure. Enter splice rows from cable/strand to cable/strand so continuity can be traced from one LIU to the other.
5. Assign the serviceCreate a service or circuit record, select the devices and ports at both ends, choose the fiber strand pair or strand set, attach splice IDs, then save the fiber assignment as proposed or planned.
6. Validate, issue work, then close outReview continuity, estimated loss, reserved strand conflicts, patch panel terminations, and required field evidence. Issue a work order, then move to as-built only after closeout review.
Capture these required elements
  • A-end and Z-end substation records
  • A-end and Z-end LIU or patch panel records
  • Endpoint devices and device ports
  • Fiber cable, route, segment, and strand records
  • Splice closures, splice points, and splice matrix rows
  • Circuit/service record with service type and criticality
  • Fiber assignment with cable IDs, strand numbers, splice IDs, and status
  • Continuity trace, loss estimate, work order, evidence, and closeout status
Example synthetic circuit assignments
87L-MA-WBS-AUB-101C37.94 / 87L protection service
Devices
WBS-SEL411L-01 port C37-1 to AUB-SEL411L-01 port C37-1
Fiber
WBS-LIU-01 ports 1-2 to AUB-LIU-01 ports 1-2 on SYN-OPGW-WBS-AUB-48F strands 1-2
Splicing
Terminal splice at WBS LIU, inline splice at WBS-AUB-JCT-01, terminal splice at AUB LIU
Assignment
Create a Protection fiber assignment, reserve strands 1-2, link splice rows, validate latency/loss, then issue a C37.94 turnup work order.
SCADA-MA-WOR-FRA-204SCADA Ethernet VLAN service
Devices
WOR-SW-01 Gi0/12 to FRA-RTU-01 Eth1
Fiber
WOR-LIU-02 ports 9-10 to FRA-LIU-01 ports 17-18 on SYN-ADSS-WOR-FRA-96F strands 37-38
Splicing
WOR terminal splice, pole-mounted splice case SC-WOR-014, FRA terminal splice
Assignment
Create an Ethernet service, set VLAN and QoS fields, assign strands 37-38, attach splice IDs, and generate a SCADA field verification work order.
DS1-MIG-MA-MIL-WBS-033Leased DS1 migration to private fiber
Devices
MIL-NID-01 DS1-1 to WBS-ICON-01 DS1-3
Fiber
MIL-LIU-01 ports 5-6 to WBS-LIU-03 ports 21-22 on SYN-OPGW-MIL-WBS-72F strands 11-12
Splicing
MIL terminal splice, midspan closure SC-MIL-WBS-022, WBS terminal splice
Assignment
Create a Leased migration service, reserve strands 11-12 as planned, track cutover window, and issue a migration work order with rollback evidence.
How to change the database
Use this admin workflow for any synthetic planning object you want available in the app and on the map.
1. Create or install schemasInstall the core TelecomNE schemas or define a custom object type with fields, validation hints, and map style.
2. Add recordsUse guide buttons, templates, forms, and map drawing tools. Point, line, and polygon records appear on the dashboard Design Mode layer.
3. Review on dashboardOpen `/dashboard?drawer=design`, enable Design Mode, draw/edit geometry, and search the editable planning asset layer.
4. Issue and close workIssue work orders from living design records, track field tasks, then update records to planned, active, or as-built after verification.

All admin-created data remains synthetic/demo unless a later import workflow explicitly marks it verified. Do not enter CEII, SCADA, relay/protection, operational telecom, credentials, or private fiber-route data.

Recommended design/edit improvements
Templates and guide actions reduce manual entry and make common design objects consistent before they become work orders or module records.
Living database work queue
Any schema-backed planning object can issue tracked work. The record stores the latest work-order link in its properties.

No living database records are available yet. Create a database object first.

Record browser and editor
Search, filter, edit, duplicate, archive, and review design records from one place.
0 matching records

No records match the current filters.

Select a record to edit it.

Create object type
Form fieldsThese fields become the no-code editor for every record of this object type.
Object name
Category
Status
Notes
Map styleChoose how this object appears on the dashboard map.
Advanced schema backup

Optional fallback for exported schemas. Use the visual field builder for normal database updates.

Create database object

Select or create an object type with form fields before adding records.

Map locationEnter the synthetic point location or edit it on the dashboard map.
Advanced raw snapshot

Read-only preview of what the form will save. Everyday updates should use the fields above.

0 rows
Display LabelAsset Type Display NameRecord KeyStatusLiving Database StatusLatest Work Order NumberGeometry TypeMap VisibleVisibilityDashboard View
Page 1 of 1