Healthcare · CMMS Migration

CMMS migrations fail because source data is dirty.

Struktive normalises your biomedical register, maps every field to your target CMMS schema — Nuvolo, ServiceNow HAM Pro, or IBM Maximo — and produces a clean, import-ready file with TJC audit pack attached. In minutes, not weeks.

Nuvolo Connected WorkplaceServiceNow HAM ProIBM Maximo AMSAccruent Connectiv

First 50 records free · No credit card · PHIPA & HIPAA aware

The problem

Why CMMS migrations go over budget

The consulting engagement is not the bottleneck. The source data is.

Dirty source data

Vendor names have 40+ variants per OEM. Model numbers are Excel-corrupted. Locations are free-text with no hierarchy. The CMMS import wizard rejects 30–60% of rows on the first attempt.

Manual field mapping

Each CMMS has a different schema. Mapping 200+ source columns to Nuvolo, ServiceNow, or Maximo fields takes 2–4 weeks of consultant time — and breaks when the source changes.

Consultant dependency

CMMS implementation partners charge $150–$300/hour for data preparation work that is fundamentally a normalisation problem, not a consulting problem.

No quality baseline

Without a data quality score, there is no way to know which records are safe to import and which will corrupt the CMMS. Post-go-live cleanup is 3–5× more expensive than pre-migration cleanup.

Time comparison

8–12 weeks of prep work. Done in under an hour.

Manual data preparation vs. Struktive — same output, different timeline.

Migration phase	Manual / consultant	Struktive
Source data audit	2–3 weeks	< 5 minutes
Vendor name resolution	1–2 weeks	Automatic
Field mapping to CMMS schema	2–4 weeks	Pre-built
Location hierarchy parsing	1–2 weeks	Automatic
Quality scoring & validation	1 week	Included
TJC audit pack preparation	3–5 days	Included
Total pre-migration prep	8–12 weeks	< 1 hour

Field mapping

Nuvolo Connected Workplace

Struktive output columns pre-mapped to Nuvolo Connected Workplace field names. Drop the export directly into the Nuvolo import wizard.

Struktive output column	Nuvolo field	Notes
canonicalVendor	manufacturer	Resolved OEM name — no alias cleanup needed
normalisedModel	model_number	Excel-corruption recovered; leading zeros restored
serialNumber	serial_number	Direct pass-through after format validation
htmCategory	asset_class	GMDN device category → Nuvolo asset class enum
criticalityRating	criticality	Life Support = Critical; maps to Nuvolo 1–5 scale
campus	location.campus	Top-level hospital hierarchy node
building	location.building	Building / tower parsed from location string
floor	location.floor	Floor level extracted from free-text
ward	location.room	Ward / unit mapped to Nuvolo room field
fdaUDI	fda_udi	FDA UDI cross-referenced and validated
nuvoloAssetType	asset_type	Pre-mapped to Nuvolo asset type taxonomy
maintenanceClass	maintenance_class	PM schedule class derived from criticality + category
networkConnected	network_connected	Boolean flag — CISA advisory check applied
qualityScore	data_quality_score	0–100 completeness score for import validation

Field mapping

ServiceNow HAM Pro

Struktive output aligned to ServiceNow Hardware Asset Management Pro tables — alm_asset, cmdb_ci, cmdb_model, cmn_location.

Struktive column	ServiceNow field	Table	Notes
canonicalVendor	manufacturer	alm_asset	Resolved to ServiceNow manufacturer record
normalisedModel	model_number	cmdb_model	Maps to CMDB model record; creates if absent
serialNumber	serial_number	alm_asset	Direct import; duplicate detection enabled
htmCategory	asset_tag	alm_asset	Category prefix used in asset tag generation
criticalityRating	operational_status	cmdb_ci	Critical → Operational; maps to CI operational status
campus	location.u_campus	cmn_location	Custom campus field on location table
building	location.building	cmn_building	Standard building record
floor	location.floor	cmn_location	Floor field on location record
ward	location.name	cmn_location	Ward name as location display name
fdaUDI	u_fda_udi	cmdb_ci	Custom UDI field — standard HAM Pro extension
maintenanceClass	maintenance_schedule	alm_asset	PM schedule reference
networkConnected	u_network_connected	cmdb_ci	Boolean; triggers CISA advisory workflow if true
qualityScore	u_data_quality	alm_asset	Import quality gate — records below 60 flagged

Field mapping

IBM Maximo Application Suite

Struktive output aligned to Maximo ASSET object structure for MAXUPLOAD import. Classification hierarchy and location records pre-resolved.

Struktive column	Maximo field	Notes
canonicalVendor	MANUFACTURER	COMPANIES table lookup; creates new record if absent
normalisedModel	MODELNUM	ASSET.MODELNUM — 30-char limit enforced
serialNumber	SERIALNUM	ASSET.SERIALNUM — duplicate check on import
htmCategory	CLASSSTRUCTUREID	Maps to Maximo classification hierarchy
criticalityRating	PRIORITY	Critical = 1, Important = 2, Standard = 3
campus	SITEID	Top-level Maximo site
building	LOCATION (parent)	Parent location record
ward	LOCATION	Leaf location record
maintenanceClass	PMNUM	PM record reference
qualityScore	DESCRIPTION (suffix)	Appended as [QS:nn] for import audit

What you get on every run

Six deliverables. No consulting required.

Nuvolo Connected Workplace import file

14-column CSV pre-mapped to Nuvolo field names. Drop directly into the Nuvolo import wizard — zero reformatting.

ServiceNow HAM Pro import set

alm_asset and cmdb_ci columns aligned to HAM Pro schema. Includes model record creation for new device types.

IBM Maximo MAXUPLOAD format

ASSET object structure with CLASSSTRUCTUREID, SITEID, and LOCATION hierarchy pre-resolved.

TJC EC.02.04.01 audit pack

Seven-tab workbook with SHA-256 tamper-evident hash. Required for Joint Commission survey readiness.

Data quality report

Per-record quality score (0–100) with field-level flags. Import gate: records below 60 flagged for review before loading.

Issues log

Every normalisation decision logged with raw value, resolved value, confidence, and recommended action.

For implementation partners

Built for Nuvolo SIs and ServiceNow partners

If you are a Nuvolo implementation partner or ServiceNow HAM Pro integrator, Struktive removes the data preparation bottleneck from your delivery timeline — and gives your client a defensible data quality baseline before go-live.

Reduce delivery risk

Clean source data means fewer import failures, fewer change requests, and fewer post-go-live support tickets. Your team focuses on configuration, not spreadsheet cleanup.

Accelerate go-live

8–12 weeks of manual data preparation compressed to under an hour. Your project timeline is no longer blocked by the client's data quality.

Defensible quality baseline

Per-record quality scores and a full issues log give you a documented data quality baseline before import — protecting your team if data problems surface post-go-live.

RTLS integration

Clean asset records are a prerequisite for RTLS deployment.

Every RTLS tag — CenTrak, Zebra MotionWorks, Stanley Healthcare, Sonitor — is mapped to an asset record. If the record is dirty (wrong OEM name, wrong device class, wrong location hierarchy), the RTLS data is also dirty. Struktive is the data preparation step that happens before your RTLS vendor arrives on site.

Tag-to-asset matching

RTLS tags are assigned to asset records by serial number and model. Dirty serial numbers and corrupted model numbers cause tag assignment failures — devices go untracked from day one.

Zone and location hierarchy

RTLS zones are built on top of your location hierarchy. If your register has 40 variants of 'ICU', the RTLS vendor has to clean them manually before they can configure zones.

Alert rules and criticality

Life support alert thresholds in CenTrak and Zebra MotionWorks are driven by asset criticality. Struktive flags every Life Support device before the RTLS system is configured.

CenTrak RTLS — Asset Record Mapping

Struktive output columns pre-mapped to CenTrak asset record fields

Struktive column	CenTrak field	Notes
canonicalVendor	Manufacturer	Resolved OEM name — maps to CenTrak asset record
normalisedModel	Model	Normalised model number for tag-to-asset matching
serialNumber	Serial Number	Primary identifier for RTLS tag assignment
htmCategory	Asset Type	HTM category → CenTrak asset type enum
criticalityRating	Priority	Life Support = High Priority for real-time tracking
campus	Facility	Top-level CenTrak facility node
building	Building	Building-level location hierarchy
floor	Floor	Floor-level for zone-based RTLS
ward	Department	Ward / unit as CenTrak department
fdaUDI	UDI	FDA UDI cross-reference for tag validation

Zebra MotionWorks Healthcare — Asset Record Mapping

Struktive output columns pre-mapped to Zebra MotionWorks Healthcare asset fields

Struktive column	Zebra MotionWorks field	Notes
canonicalVendor	manufacturer_name	Resolved OEM — Zebra MotionWorks asset record
normalisedModel	model	Normalised model for MotionWorks asset catalogue
serialNumber	serial_number	Tag-to-asset binding key in MotionWorks
htmCategory	asset_category	GMDN device category → MotionWorks category
criticalityRating	priority_level	Critical assets get real-time alert thresholds
campus	site	MotionWorks site (top-level)
building	building	Building node in MotionWorks hierarchy
floor	floor	Floor-level zone assignment
ward	zone	Ward / unit as MotionWorks zone
networkConnected	network_enabled	Boolean — triggers MotionWorks network alert rules

Ready to unblock your CMMS migration?

Upload your biomedical register and get a Nuvolo, ServiceNow, or Maximo-ready import file in under five minutes. No setup, no consulting, no commitment.

First 50 records free · PHIPA & HIPAA aware · TJC EC.02.04.01 compliant