top of page

Sensor Arrays Change Order: Map Measurements by Identity, Not Position

Nov 9
3 min read

A telemetry payload can remain valid JSON while two measurements swap positions. If an importer assumes that the first item always means the same sensor, plausible values can be assigned to the wrong asset without a syntax error.


Original conceptual illustration: Sensor Arrays Change Order: Map Measurements by Identity, Not Position

Original conceptual illustration; not a live software screen, specific product or customer installation.


Key takeaways


  • JSON validity does not establish sensor identity.

  • Test reordered and duplicate records.

  • Version the mapping and expected channel set.


1. Define the identity contract


JSON arrays are ordered sequences, but that syntax does not define what a particular position means in your application. A stable positional contract requires an explicit agreement with the producer. Otherwise map using a documented source identifier and channel definition.


Keep measurement identity, unit and quality information together. A temperature value is not an adequate identity: two sensors can report the same number. Likewise, array length proves only the number of elements received, not that every expected channel is present exactly once.


2. Avoid silent reassignment


For keyed records, validate the required identity field before updating a destination. Decide how unknown, missing and duplicate identities are handled. An importer that simply accepts the last duplicate can hide a source defect; the correct project policy should be explicit and observable.


The ProSight Software platform overview can support a discussion of asset mapping and reporting scope. This is an integration acceptance guide, not a claim that any particular payload schema, import endpoint or automatic identity resolver is available in every deployment.


3. Reorder a synthetic test payload


Hypothetical example: three invented test sensors A, B and C report distinguishable values. Import a record ordered A/B/C, then a record ordered C/A/B without changing each sensor’s identity or value. Under an identity-based contract, each destination should still receive its own measurement.


Repeat with one expected identity missing, one unknown identity and one duplicate. Inspect destination changes and the diagnostic record, not merely the import success count. These software tests should use isolated test assets so fabricated measurements cannot be mistaken for production observations.


Original explanatory workflow: Define channel identity. Validate incoming record. Resolve destination by contract. Handle missing and duplicates. Verify destination and unit

Original explanatory infographic. Values and test cases are hypothetical; equipment selection and implementation require project-specific verification.


Diagnostic comparison


Observation

Next check

Values appear in wrong assets

Inspect identity-to-destination mapping.

Item count remains unchanged

Check the expected identity set, not just length.

New source version adds a channel

Retest the documented mapping contract.


4. Make schema changes reviewable


A producer upgrade that adds or removes channels can expose a positional assumption years after commissioning. Preserve a representative payload, mapping revision and expected identity set in the handover pack. Require a controlled retest when the source schema or channel inventory changes.


If a deliberately positional protocol must be used, document its version, fixed slot definitions and mismatch response. Reject incompatible layouts instead of guessing. Also verify timestamps, units and validity separately: correct identity does not make every value fresh or suitable for the intended engineering decision.


  1. Define the source identity and destination map.

  2. Import distinguishable synthetic records.

  3. Reorder without changing identities.

  4. Test missing, unknown and duplicate channels.


Recommended equipment / related solutions


Start with the ProSight Software platform overview to discuss the supported software scope and the reporting evidence your team needs.


Where the requirement needs engineered integration or a tailored reporting workflow, review ProSight Custom project scope. Confirm deliverables and the exact supported deployment before selecting an implementation.



Frequently asked question


Is a fixed array position always wrong?


No. It can be valid under an explicit stable schema. The risk is assuming that contract exists without documenting and testing it.


Technical references



Need help with your application?


Send the equipment models, current documentation and a sanitised test example. Discuss this integration and equipment requirement with ProSense; confirm the actual functions, interfaces and acceptance scope before purchase or deployment.









Comments


prosight-software-logo (1).png
bottom of page