Reference · built on requestOperator by FibricProperty & tenants

Common Area Triage

Camera events, sensor uplinks, and porter reports from shared spaces sorted into one work order each, with trade and priority proposed.

Request accessPricing ↗

About

A lobby leak gets reported more than once: a water sensor uplinks, a camera sees the puddle spread, and the porter writes it up. Common Area Triage reads all of them and proposes one work order. It reads zone counts, dwell, and entry and exit transitions from Camera Vision, motion and tampering events with a JPEG snapshot from AXIS VAPIX, door, leak, temperature, and humidity uplinks from your LoRaWAN network, DEVICE_DATA events from Milesight, and waterPresent and contact events from Disruptive Technologies. Porter reports arrive as work requests in MaintainX, UpKeep, or Limble CMMS.

For each event it proposes the trade, the priority, and the space, attaches the snapshot, and merges duplicates into the open order. Each order waits for you. It never sends a technician.

This is a reference listing. It documents what Fibric would read from Common Area Triage and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Zone counts, dwell time, and zone entry and exit transitions from Camera Vision on lobbies, corridors, and loading areas
  • Motion and tampering events such as tns1:VideoAnalytics/tnsaxis:MotionDetection from AXIS VAPIX, with a JPEG snapshot from /axis-cgi/jpg/image.cgi
  • Door, leak, temperature, humidity, and tank-level uplinks from your LoRaWAN network, with battery level and last-seen freshness per device
  • Milesight DEVICE_DATA events of type PROPERTY or EVENT, and Disruptive Technologies waterPresent, contact, motion, and touch events
  • Porter and resident reports as work requests: MaintainX NEW_WORK_REQUEST, UpKeep REQUEST_CREATED, or Limble work request submissions
  • Open work orders on the same space in the CMMS, so a report of a fault already in hand joins it

Proposed actions

  • Target capability: propose a work order with trade, priority, and location through MaintainX POST /workorders, Limble POST /v2/tasks with a locationID, or Facilio POST /workorder
  • Target capability: propose attaching the snapshot or sensor reading to the order, as a Facilio task photo, a MaintainX comment, or a Fiix file upload
  • Target capability: propose approving a porter's work request in UpKeep or Limble CMMS with the trade and priority filled in
  • Target capability: propose merging a duplicate report into the open order as a comment, instead of a second order
  • Target capability: propose raising priority when signals agree, such as a leak uplink and a wet-floor report on one space within your window

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Turn a leak uplink into a plumbing order

    A LoRaWAN leak sensor in the garage stairwell uplinks wet. The operator pulls the AXIS snapshot from the nearest camera and proposes a MaintainX plumbing work order at high priority.

    With LoRaWAN Network, AXIS VAPIX, MaintainX

  • Merge the porter's report into the open order

    An UpKeep request describes a fault a Milesight door sensor already raised. The operator proposes approving the request and a comment on the existing order, not a second one.

    With UpKeep, Milesight Development Platform

  • Send cleaning where people actually dwelled

    Camera Vision reports long dwell and high counts in a lobby corner. The operator proposes a Facilio cleaning work order for that space with the counts attached.

    With Camera Vision (RTSP), Facilio

  • Raise priority when sensors agree

    A Disruptive Technologies waterPresent event and a Limble work request name the same laundry room. The operator proposes one Limble task at the priority your table gives a confirmed leak.

    With Disruptive Technologies, Limble CMMS

Requirements

  • A source of camera events: Camera Vision on RTSP feeds, or AXIS VAPIX events and snapshots from the cameras themselves
  • A sensor source: a LoRaWAN network server, Milesight Development Platform, or Disruptive Technologies
  • A CMMS to receive the work orders: MaintainX, UpKeep, Limble CMMS, or Facilio
  • Your triage table: which sensor and event types map to which trade and priority, per space
Authentication
It reads cameras, sensors, and requests through the video, sensor, and maintenance connectors you attach, each with the scopes you grant; it keeps no credentials itself.

Limits

  • Camera analytics give counts, motion, and a frame. They do not diagnose. The trade comes from your table and the snapshot goes to a person.
  • LoRaWAN devices report on their own interval. A leak that starts between uplinks is seen at the next one.
  • A porter's text is read as written. A vague report is proposed with the priority your table gives an unknown.
  • It views no live video and dispatches nobody. Every work order waits for approval.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Common Area Triage ↗

Questions and answers

What am I approving for each report?
One work order: its trade, priority, location, and the attached snapshot or reading. The proposal shows every source that pointed at the space, the open orders it checked, and the table row it applied. Approve, change the trade, or dismiss.
What is kept for each order?
A receipt: the event ids and uplinks cited, the snapshot attached, the work request approved or merged, the work order id created, the priority set and why, who approved, and how to reopen a merged report.
Does it ever create a work order on its own?
It does not. Every order, approval, merge, and priority raise waits for a person. If no table row matches an event, it proposes nothing and lists the event for review.
Ask about Common Area Triage

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy