IBM Idea - Normalize non-breaking spaces in ALN fields and search processing
Short description
Maximo Manage can store non-breaking spaces (U+00A0) in standard ALN fields and treats them differently from ordinary spaces (U+0020) during searches. The characters appear identical to users, so relevant records can be omitted from filters and searches. Sund & Bælt kindly request a supported, configurable capability that treats both characters as equivalent during search processing and normalizes U+00A0 during input, save, and supported integration processing.
Business need and impact
Sund & Bælt relies on Maximo data to plan, execute, and document maintenance of major transport infrastructure. Normal copy-and-paste from Excel, email, Word, or websites can introduce U+00A0 without the user being able to see it.
· Searches and filters can omit relevant records even when the visible text matches.
· Apparently identical values can behave differently in queries, integrations, exports, and duplicate controls.
· Troubleshooting and cleansing require technical analysis because the character difference is invisible in the Maximo user interface.
Evidence and scope
Analysis within Sund & Bælt’s Maximo Manage identified the issue across master and transactional data:
· 21 affected attributes across 10 object types, with approximately 27,500 affected records in that analysis scope.
· Separately, approximately 19,397 Work Orders and 11,794 Purchase Orders were identified with U+00A0 in Description.
· Affected areas include Assets, Locations, Preventive Maintenance, Job Plans, Routes, Item Master, Failure Codes, Classifications, People, and Crafts.
The figures come from different analysis scopes and must not be added together as one total.
Requested capability
Provide one supported and configurable Maximo Manage capability with consistent behavior across search, user input, save processing, and supported integration channels:
1. Search equivalence
Treat U+00A0 and U+0020 as equivalent in standard searches, filters, lookups, and query mechanisms. This is the primary requirement because it also makes existing affected records discoverable.
2. Input and integration normalization
Convert U+00A0 to U+0020 before storage when values are entered, pasted, imported, or created or updated through supported integration channels.
3. Existing data remediation
Provide a supported, auditable method to identify, preview, and normalize existing values.
4. Configuration and documentation
Provide supported configuration and document scope, compatibility, rollback, and cases where a non-breaking space must intentionally be preserved.
Acceptance criteria
· When normalization is enabled, saving an ALN value containing U+00A0 stores U+0020 instead.
· A search containing U+0020 returns matching records whose stored value contains U+00A0 in the corresponding position, and vice versa.
· The capability works consistently in commonly used Manage applications, including among other Work Orders, Assets, Locations, Preventive Maintenance, Job Plans, and Routes.
· The documented rule applies to supported imports and integrations, including Maximo Integration Framework and REST API processing of ALN values.
· IBM provides an auditable approach for scanning and normalizing existing data without silently changing whitespace documented as semantically meaningful.
Why a product-level solution is needed
Local automation scripts or attribute-specific validations can reduce new occurrences in selected fields, but they do not make existing affected records consistently searchable and require ongoing maintenance across objects, applications, and interfaces. An export setting that changes whitespace in downloaded data does not address storage or search processing inside Maximo Manage.
IBM Support position
In IBM Support case TS022935622, IBM confirmed that U+00A0 can be introduced through normal copy-and-paste and is treated differently from ordinary spaces during searches. IBM described the behavior as a design flaw rather than a defect because no product rule currently prevents or converts the character, and recommended submitting an enhancement request. IBM also referred to related idea MASM-I-900, which was not under consideration at the time of the support response.
Benefits
· Predictable searches and filters for end users.
· Reduced risk of missing relevant maintenance information.
· Improved consistency across master and transactional data.
· Lower troubleshooting, cleansing, and customization effort for Maximo customers.
