top of page

Micro Sign or Greek Mu? Keep Unit Labels Separate from Measurement Identity

Nov 8
3 min read

Two unit labels can look identical while containing different characters. Diagnose the actual character sequence before renaming fields, and keep engineering-unit conversion separate from text normalisation.


Original conceptual illustration: Micro Sign or Greek Mu? Keep Unit Labels Separate from Measurement Identity

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


Key takeaways


  • Inspect code points, not appearance alone.

  • Separate source identity, display text and unit.

  • Validate numeric scale independently.


1. Inspect the character identity


The micro sign µ and Greek small letter mu μ are different Unicode characters. Unicode normalisation distinguishes canonical forms from compatibility forms; a compatibility transformation may collapse distinctions that a canonical transformation retains.


Start a ProSight Software platform overview discussion with a sanitised example of the original label and the intended measurement. This guide describes an interface design issue; it does not claim a particular normalisation or unit-conversion feature in an existing deployment.


2. Preserve the original engineering meaning


Record the source field identifier, displayed label and declared engineering unit separately. A label that contains a micro prefix is not enough to establish the full quantity. Conductivity, current and length require different units and cannot be reconciled by changing a character.


Ask which identifiers the source and destination actually match. A stable machine identifier with separately controlled display text is generally easier to audit than an identifier derived from whatever a spreadsheet happens to display. Preserve the original value in the diagnostic evidence.


3. Test an apparently identical pair


In a hypothetical handover, one column is labelled µS/cm using U+00B5 and another uses μS/cm with U+03BC. A character-by-character comparison can distinguish them despite the similar display. An engineer should establish whether they refer to the same intended unit before applying any mapping.


Test the intended policy on a copied dataset. Retain the source label, resulting canonical identifier and mapping decision. The acceptance result should demonstrate which labels are accepted, rejected or explicitly aliased; it should not merely show that the font looks consistent.


Original explanatory diagram: Preserve source label. Inspect Unicode code points. Resolve intended engineering unit. Apply approved explicit mapping. Validate channel identity and scale

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


Diagnostic comparison


Observation

Check next

Labels look identical but do not match

Compare the stored character sequences.

Normalised labels collide

Keep distinct channel identities and review aliases.

Labels match but values differ by a factor

Check engineering scale separately.


4. Do not normalise indiscriminately


Unicode describes compatibility normalisation as potentially removing meaningful distinctions. Do not apply it to an entire industrial dataset merely to fix one heading. Identifiers, free text and measurement labels may have different preservation requirements.


Specify the permitted aliases for the actual unit field and check them for collisions. A transformed label must not cause two different source channels to overwrite each other. Preserve the raw original and include a deliberate exception path for unknown labels.


  1. Inspect code points, not appearance alone.

  2. Separate source identity, display text and unit.

  3. Agree explicit aliases for the unit field.

  4. Check mappings for channel collisions.

  5. Validate numeric scale independently.


5. Validate the numeric consequence separately


Character normalisation is a text operation. It does not multiply a reading by a prefix factor, change calibration or establish the correct physical quantity. After agreeing the label mapping, independently verify scale, unit, range and representative engineering values.


For ProSight Custom project scope, provide the source schema, sample labels and required mapping audit. Confirm any proposed transformation and reporting behaviour for the actual deployment. Treat changes to control-related values as an application design matter requiring competent validation, not a cosmetic import cleanup.


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


Will Unicode normalisation convert micro-units into base units?


No. Text normalisation does not perform engineering conversion. Validate quantity, prefix and numeric scale as a separate explicit operation.


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