Teleproject
All services

Services · Network monitoring and supervision (NOC)

Remote supervision of network equipment, radio systems, in-tunnel installations, and IoT sensors with the Track-TP platform.

We connect network equipment, radio systems, in-tunnel coverage installations, and LoRaWAN sensors to our Track-TP platform. We agree with the customer the thresholds beyond which an alarm is raised, deliver the notifications to the technicians by email, WhatsApp, and Telegram, and keep the history of every measurement.

SNMP · Syslog · REST · LoRaWAN
collection protocols
H24
continuous monitoring
ISA/IEC 62443-3-3 SL2
cybersecurity
ISO 9001:2015
quality
The service

A mission-critical system does not fail all at once: it gives way one piece at a time, and the defect stays invisible until the day someone needs to communicate. A site running on its backup batteries, a repeater that reboots every night, a mobile operator cell that stops transmitting in one bore, a radiating cable broken along a stretch of tunnel: none of this is visible from the control room, because the control room shows the calls, not the state of the equipment that makes them possible.

Monitoring is there to catch it before it becomes an outage. We connect the equipment to our Track-TP platform, which polls it over SNMP v1, v2c, and v3, collects Syslog messages and traps, reads the systems that expose a REST interface, and receives the readings of LoRaWAN sensors at 868 MHz. With the customer we decide which quantities to follow, the value beyond which an alarm is raised, and who has to receive it: the notifications go out by email, WhatsApp, and Telegram, and where a supervision system is already in place the same alarms are forwarded as SNMP traps.

Track-TP is developed to the ISA/IEC 62443-3-3 Security Level 2 standard, supports compliance with the NIS2 directive, and runs in the cloud or on a Linux server inside the customer’s network. Supervision does not replace the maintenance contract, it works alongside it: it identifies the anomaly, then the contract brings a technician on site within 24 h of the request.

The service

How the service is organized.

How supervision of a system works, from continuous data collection to the periodic reports, and where the platform is installed.

  • Continuous supervision

    Track-TP polls the connected equipment and logs its status, measurements, and alarms without interruption. Every reading is stored in the history, so you can trace exactly when a parameter started to degrade.

  • Alarm management

    We configure the thresholds and the rules that raise an alarm, define who receives it and on which channel, then run a test send to confirm that the notifications reach the technicians named by the customer.

  • Reports and analysis of the history

    From the measurement history we produce the periodic reports on the condition of the installations: alarms logged, the units that raised the most of them, and parameters that are degrading. The data exports to CSV and Excel.

  • Platform in the cloud or on the customer’s servers

    Track-TP runs in the cloud or on a Linux server installed inside the customer’s network. The choice depends on the security policies of the organization and on the connectivity available at the sites.

Supervision

What we keep under control.

The equipment, the installations, and the quantities the platform checks without interruption, and the rules by which we raise and deliver the alarms.

  • Network equipment and servers

    • Reachability of every unit and response time of the network that connects it
    • Polling of routers, switches, firewalls, and site equipment over SNMP v1, v2c, and v3
    • Processor load, memory usage, and disk space on servers and virtual machines
    • Port status, interface traffic, and PoE power
    • Collection of the Syslog messages and of the SNMP traps sent by the equipment
  • Radio systems and repeaters

    • Operating status of base stations, repeaters, and radio gateways
    • Alarms sent by the equipment: module failure, over-temperature, loss of synchronization
    • Status of the links between the radio sites and toward the control room
    • Availability of the dispatch consoles, of the radio gateways, and of the voice recorder
    • Reading of the parameters of equipment that exposes a REST interface instead of SNMP
  • In-tunnel installations

    • Cellular coverage inside the bore, measured by TP-CELLX on the 2G, 3G, and 4G networks of every operator and by TP-CELLX Pro on 5G DSS and 5G NR
    • Carriers present in band, detected by TP-RFX from 15 MHz to 2.7 GHz: TETRA, DMR, PMR, FM, DAB, and P25
    • Radiating cable continuity, checked by TP-CCV2, which detects short circuits and open lines
    • Alarms of the line amplifiers and of the equipment installed in the tunnel niches
    • Status of the FM and DAB+ rebroadcast systems and alarms reporting their failure
  • Environmental and LoRaWAN IoT sensors

    • Temperature, humidity, CO₂, and radon in equipment rooms, technical shelters, and tunnels
    • Structural sensors on bridges and viaducts: vibration, tilt, load, and strain
    • Road operating sensors: vehicle counting, asphalt temperature, light level, fuel level, and weather stations
    • Status of the LoRaWAN gateways and level at which they receive the sensor transmissions at 868 MHz
    • Remaining battery charge of the sensors installed in the field
  • Power and backup supply

    • Presence of the mains supply and switchover of the site to the backup batteries
    • Status of the UPS units and of the power supplies feeding the racks
    • Voltage and current draw on the DC lines of the radio equipment
    • Operation of the air conditioning and temperature reached in the equipment room
    • Door-open alarms on cabinets and equipment rooms, where the installation provides them
  • Thresholds and alarm rules

    • Choice, for each type of unit, of the quantities to follow and of the value beyond which an alarm is raised
    • Separation of the anomalies that need an immediate callout from those that can wait for the scheduled visit
    • Tuning of the thresholds to avoid repeated notifications when a single fault affects several units
    • Advance notice of planned downtime, so that agreed work is not mistaken for a fault
    • Update of the thresholds when the equipment or the operating conditions of the installation change
  • Notification channels

    • Notifications sent by email, WhatsApp, and Telegram to the technicians named by the customer
    • Alarms forwarded as SNMP traps to the supervision system already in use at the customer
    • Separate distribution lists per installation and per site
    • Alarms consulted from a phone, through the Track-TP interface, which runs in a browser
    • Test send on every channel before the service starts and whenever the recipients change
  • Dashboards, maps, and history

    • Dashboards built per installation and per equipment group, on the parameters the customer wants to see first
    • Geographic map of the supervised sites, with the status of each location
    • Charts of how the measurements move over time, to compare today’s value with that of the previous months
    • History of every measurement and every alarm, exportable to CSV and Excel
    • Separate accounts for the customer’s staff, with the roles assigned to each operator
Setup

How supervision is set up.

The service cycle, from the equipment inventory to the day-to-day handling of the alarms.

  1. Step 01

    Equipment inventory

    Site by site we compile the list of the equipment to be supervised: network addresses, available protocols, read-only credentials, and the quantities that each unit makes available.

  2. Step 02

    Connection and configuration

    We connect the equipment to Track-TP, set up collection over SNMP, Syslog, and the REST API, connect the LoRaWAN gateways and register the sensors on the platform, then verify that every value arrives correctly.

  3. Step 03

    Thresholds, rules, and notifications

    With the customer we define the alarm thresholds, the distribution lists, and the recipients for each installation, then we test the send on every channel: email, WhatsApp, Telegram, and SNMP traps.

  4. Step 04

    Operation

    The notifications reach the technicians named as soon as a value moves outside the configured limits. We review the data collected, check the anomalies that cleared on their own, and report to the customer those that need work in the field.

  5. Step 05

    Reports and fine-tuning

    We deliver the periodic reports on the condition of the installations, correct the thresholds that raise alarms of no significance, and add to supervision the equipment installed in the meantime.

Deliverables

What you receive.

The access, the documents, and the reports the customer keeps for the whole duration of the service.

  • Access to Track-TP

    Separate accounts for the customer’s staff, with dashboards, the map of the sites, and the measurement history, all available in a browser and from a phone.

  • List of supervised equipment

    The inventory of what is connected to the platform: unit, site, collection protocol, and the quantities followed for each one.

  • Alarm plan

    The configured thresholds and the distribution lists, agreed with the customer and updated at every change.

  • Real-time notifications

    The alarms arrive by email, WhatsApp, and Telegram, and are forwarded as SNMP traps to the customer’s supervision system where one is in place.

  • Periodic reports

    The condition of the installations over the period: alarms logged, the units that raised the most of them, and parameters that are degrading.

  • Measurement history

    Every value collected stays on file and exports to CSV and Excel, so you have the data to reconstruct a fault and to document how it was handled.

Related products

Products used.

The products developed in-house by Teleproject that we use in this service.

FAQ

Frequently asked questions.

The questions we hear most often about this service.

Do I have to expose the equipment to the internet to connect it to the platform?

No. Track-TP also runs on a Linux server installed inside the customer’s network: in that case the data never leaves the infrastructure and no unit is reached from outside. If instead the platform is in the cloud, we agree with the customer’s IT department how the equipment is to be reached. In both cases the data is collected with read-only credentials, because supervision reads the parameters and does not change the configurations. The choice between the two arrangements depends on the security policies of the organization and on the connectivity available at the sites.

Can equipment from different manufacturers be connected?

Yes. What matters is not the brand of the unit but the protocol it uses to make its data available: Track-TP polls the equipment over SNMP v1, v2c, and v3, collects Syslog messages and traps, reads the systems that expose a REST interface, and receives the readings of LoRaWAN sensors at 868 MHz. During the inventory we check, unit by unit, which quantities are actually available, because two models from the same manufacturer can expose a different number of them. Equipment that exposes none of these protocols stays outside supervision, and we tell the customer at the end of the inventory, before the service starts.

What happens if a site loses its data link?

Track-TP flags the equipment at that site as unreachable and raises an alarm. On its own, however, the platform cannot tell a failure of the unit apart from the loss of the link that reaches it: that is why we also monitor the network equipment and the links between the sites, so that the pattern of alarms shows where the problem really is. The measurements collected before the interruption stay in the history and can be compared with those taken after the link is restored.

Does anything need to be installed on the equipment to be monitored?

We install nothing on the customer’s equipment: Track-TP collects the data that every unit already makes available through its own protocols, so no additional software is needed on routers, servers, repeaters, or consoles. We install a unit of our own only where no existing equipment provides the measurement required: TP-CELLX for cellular coverage in tunnels, TP-RFX for the carriers present in band, TP-CCV2 for radiating cable continuity, and LoRaWAN sensors for environmental and structural quantities. These measurements also reach Track-TP and appear in the same dashboards as the network equipment.

Contact us

Request a quote for network monitoring and supervision (noc).

One of our Project Managers analyzes your specific project requirements and prepares a dedicated technical and commercial proposal.