/
Design and integration/
MaeneoEach area of the platform has its own page: the systems in it, the standards it is drawn against, the industries it serves and how we deliver it.
Plan with usTechnologiesAreas · 5 Technologies · 190 Industries · 4
At a glance
System design
Requirements to architecture, drawn against the standards. The page on system design sets out the technologies it uses, the standards they follow and how we deliver it. System design against the reference architecture, engineering packs a contractor can build from, multi-vendor integration on typed interfaces, and programme delivery across many sites with one plan, one schedule and one evidence record.
Tatizo
One accountable integrator, site to grid
The products and services of Design and integration start with system design, engineering, multi-vendor integration and programme delivery. System design against the reference architecture, engineering packs a contractor can build from, multi-vendor integration on typed interfaces, and programme delivery across many sites with one plan, one schedule and one evidence record.
Components
- Pole-mounted edge gateway node
- Overhead line sensor on a distribution span
- Automatic weather station (AWS) to WMO siting practice
- Distribution pole transformer and meter cabinet
- Private LTE mast on a solar skid
- “AI tower in a box”
- Data hall row pair with cold-aisle containment
- Operations console with a video wall
Interfaces
- Vyombo
- SDI-12 · RS-485 / Modbus RTU · 4–20 mA
- Radio
- Ethernet · LTE-M / NB-IoT · LoRaWAN
- Time and position
- GNSS 1PPS
- Security
- TPM 2.0
- Publishing
- MQTT
Where it works
- Acceptance
- Programme delivery
In the story below
- The system, part by part
- Assembly
- Installation
- Deployment
- Connections
- Operation
- Failure and recovery
- Scale and federation
- What you get
Scenes · 13
Next steps
Plan a deploymentOpen the Field Deployment StudioSee Design and integrationSee EngineeringDesign and integration · Areas
One accountable integrator, site to grid
The products and services of Design and integration start with system design, engineering, multi-vendor integration and programme delivery. System design against the reference architecture, engineering packs a contractor can build from, multi-vendor integration on typed interfaces, and programme delivery across many sites with one plan, one schedule and one evidence record.
Area · System design
System design
Requirements to architecture, drawn against the standards. The page on system design sets out the technologies it uses, the standards they follow and how we deliver it. System design against the reference architecture, engineering packs a contractor can build from, multi-vendor integration on typed interfaces, and programme delivery across many sites with one plan, one schedule and one evidence record.
See System designArea · Acceptance
Acceptance
Tested against the plan, signed off on evidence. The page on acceptance sets out the technologies it uses, the standards they follow and how we deliver it. System design against the reference architecture, engineering packs a contractor can build from, multi-vendor integration on typed interfaces, and programme delivery across many sites with one plan, one schedule and one evidence record.
See AcceptanceArea · Multi-vendor integration
Multi-vendor integration
Many suppliers, one interface contract. The page on multi-vendor integration sets out the technologies it uses, the standards they follow and how we deliver it. System design against the reference architecture, engineering packs a contractor can build from, multi-vendor integration on typed interfaces, and programme delivery across many sites with one plan, one schedule and one evidence record.
See Multi-vendor integrationArea · Programme delivery
Programme delivery
Many sites, one plan and one schedule. The page on programme delivery sets out the technologies it uses, the standards they follow and how we deliver it. System design against the reference architecture, engineering packs a contractor can build from, multi-vendor integration on typed interfaces, and programme delivery across many sites with one plan, one schedule and one evidence record.
See Programme deliveryTime and place
When and where, on every record
On a network for Design and integration, when and where are part of every record: a disciplined clock, from satellite time or a PTP grandmaster, and the station’s surveyed position. A degraded clock or position is written into the record for Design and integration, never hidden, and every user downstream sees the same flag.
Area · Engineering
Uhandisi
Design packs, bills of materials and drawings. The page on engineering sets out the technologies it uses, the standards they follow and how we deliver it. System design against the reference architecture, engineering packs a contractor can build from, multi-vendor integration on typed interfaces, and programme delivery across many sites with one plan, one schedule and one evidence record.
See EngineeringImani
Proved before it is trusted
Every node on a network for Design and integration proves what it is before it is admitted, by answering an attestation challenge from its hardware root of trust. From then on, its keys stay in secure hardware, its software is signed, and every record it makes for Design and integration can be traced to it.
Ushahidi
Standards an auditor can check
An auditor of a network for Design and integration finds metadata to WIGOS and ISO 19115, observations through OGC SensorThings and exchange through WIS 2.0. Releases, calibrations and admissions for Design and integration are kept as signed records, so every claim can be checked against the standard behind it.
Taarifa mpya
Updates in rings, with rollback
No change reaches a whole fleet for Design and integration at once: software and configuration go to one canary site first, then to a few, then to all. Each ring for Design and integration passes only on health and data completeness, and a failed check returns every node to its last good release.
How it scales
One base unit, repeated
A network for Design and integration grows from one proven unit: a base node, its instruments, then the power and radio that make it a station. A relay turns stations into a site, a fleet repeats the site in many places, and capacity for Design and integration rises with each unit added, never by replacing what works.
What you get
Open where it can be, contracted where it must be
Anyone can use and build on the protocol, the methods and the open data behind Design and integration, free of charge. Under contract, Nexus Observatory Inc. builds and runs the sites, fleets and data tiers for Design and integration, priced per site and per fleet, with service levels written as numbers.
Next step
Design and integration, planned with you
Tell us which products and services of Design and integration you need, for which sites and by when. An engineer replies with a survey proposal, a design and a scope for Design and integration, and the plan grows from one site to the network you need.
Plan a deploymentOpen the Field Deployment StudioSee Design and integration
More presentations
See it from every side.
Each opens as a full-screen presentation: deeper pages on the same subject, explainers, stories, guided tours of the places, network scenes and the observatories that came before.
All presentationsIn depth
Use case Street flood observatoryISIC section · ISIC O Public administration and defence; compulsory social securityISIC section · ISIC Q Human health and social work activitiesUse case Utility grid-edge private LTE and wildfire weatherExplainers
Explainer · Government and public safety Government and public safetyWildfire cameras on real terrain, GBON station density, street-flood alert thresholds, CAP alerting with the authority in the loop and the radio horizon of a deployable cell.Explainer · Development and humanitarian Development and humanitarian, explainedJukwaa Design and integrationMany suppliers, nobody accountableJukwaa Sensors & instrumentsA number without its storyStories
Story · Federation across agencies Many agencies, one pictureNo single agency observes everything it needs. Federation lets each keep its own systems and still share: common interfaces, common catalogues and common…Story · Resilient operations When the links failObserving systems matter most on the days infrastructure fails. Designing for that day means local autonomy, stored power, store-and-forward delivery and…Story · End to end An observation grid, end to endAn observation is not a reading. It is a reading with a place, a time, a calibration and a path that anyone can follow back. An observing grid is the…Places and networks
Guided tour · Guided 3D tour Mountain valley siteA private 5G tower, an automatic weather station, a compact radar and a seismic vault on real alpine terrain, joined to an edge data centre that admits, times and publishes every…Guided tour · Guided 3D tour Transmission corridorLattice towers carry a line across open country; conductor sensors report temperature and sag, and the substation edge brings them into the grid operator’s systems.Guided tour · Guided 3D tour Ground stationAn 11 m class antenna and its companions on a fenced pad, with edge compute that turns each pass into catalogued products before the next one.Network scene · Private 5G · Mining Private 5G in an open-pit mineA private network for haul trucks, drills and slope radar: a mast on the rim, a cell in the pit, the core at the plant, and coverage computed over the benches themselves.Network scene · NTN · Satellite Satellite direct to device in a mountain valleyWhere the valley cell cannot reach, phones on the pass road connect straight to a low-orbit satellite, which relays through its feeder link to a gateway.Heritage observatories
Heritage observatory · United States · 1961 World-Wide Standardized Seismograph NetworkIn the early 1960s the United States put identical seismographs, calibrated the same way, in more than a hundred places around the world and published the records on film for…Heritage observatory · United States · 1921 Caltech Seismological LaboratoryA laboratory in Pasadena that gave earthquakes a number. The Richter magnitude scale of 1935 depended on one instrument type in many places, a lesson as relevant to networks today…Interactive tools
Interactive tool · Configure a station Station BuilderConfigure a station part by part in 3D, check the rules as you go and request a quote for the assembly.01Maeneo
Design and integration, area by area.
Choose an area for its systems, standards, the industries it serves and how we deliver it.
01System design
Requirements to architecture, drawn against the standards. Open the area →02Uhandisi
Design packs, bills of materials and drawings. Open the area →03Multi-vendor integration
Many suppliers, one interface contract. Open the area →04Programme delivery
Many sites, one plan and one schedule. Open the area →05Acceptance
Tested against the plan, signed off on evidence. Open the area →02Open and enterprise
Open by default. Enterprise by contract.
The open layer lives on the main site, free to use and build on. Enterprise services are delivered under contract by Nexus Observatory Inc.
Open, on the main site
- Reference architecture
- Interface contracts
Enterprise, on this site
- National observing network programmes
- Systems integration
- Programme management
03Kwenye tovuti hii
Where to go next.
Design and integrationTechnologies
The layered map of what we build with. Open →Design and integrationArchitecture
Layers, functions and evidence. Open →Design and integrationIndustries
The industry sites built on this platform. Open →Design and integrationRasilimali
Explainer, stories, specification and forms. Open →Bring us the site.
We bring the survey, the design and the crew. The form names who receives your details.
Plan a deploymentWasiliana nasi