Your team owns
- Equipment list authority and P&ID / historical workbook source files
- Approving staged ERP sync records and engineering calculation sign-offs
- Day-two form, checklist, and approval-chain edits in the workspace
Implementation
Configure the platform around the work.
Start with one asset class, unit, or turnaround. Import the register, configure workflows in metadata, and go live in days.
Delivery path
Preparation before configuration. Validation before handoff.
Each rollout follows four structured stages led by our Professional Services team.
01
Import the asset spine
intelliVISION · CFIHOS & ISO 14224
Load your facility hierarchy, equipment tags, corrosion circuits, and historical CML readings via Excel workbook mapping or the Integration Hub, with deduplication and preview validation before commit.
- Validated facility, unit, equipment, and CML hierarchy
- Historical UT thickness and short/long corrosion rate reconciliation
- SSO (Microsoft Entra ID / SAML / OIDC) and MFA setup
02
Configure workflows in metadata
Forms · Turnaround templates · Approval gates
Map inspection wizards (API 510, 570, 653), damage mechanisms, coating ITP hold points, and turnaround project templates in JSON metadata. No custom code or developer sprint is required.
- Asset-aware inspection wizards and custom fields
- Turnaround wall-chart task stages and gate review checklists
- Unit-of-measure (Imperial / Metric) and rate-card templates
03
Validate RBAC, crew & offline sync
524 RBAC permissions · intelliCREW · intelliEDGE
Bind users and API keys to roles and hierarchy data scopes, load inspector qualifications and calibrated gauge serials, and verify 30-day offline package checkout in intelliEDGE.
- Role and hierarchy node data-scope verification
- Inspector credential and calibrated instrument gating
- Airplane-mode field capture and bi-directional conflict sync test
04
Go live & own day two
Production rollout · Admin self-service
Launch on your first unit, tank farm, or turnaround campaign. Your administrators add fields, templates, and budgetary plans directly in the workspace while intelliSPEC supports rollout and expansion.
- Live unit or turnaround cutover with field crews
- Administrator training for zero-ticket form and workflow updates
- Direct customer success and professional services support
Clear ownership
Who owns what during rollout.
intelliSPEC Professional Services owns
- Initial hierarchy, circuit, and historical CML migration mapping
- Template configuration for your inspection codes and turnaround stages
- Field-crew onboarding, offline sync validation, and go-live support
Answers
Implementation questions
Why does intelliSPEC go live in days instead of quarters?
Forms, inspection wizards, turnaround wall-chart stages, dashboards, and approval chains are defined in declarative metadata rather than custom code. Adding a field, a damage mechanism, or a hold point is a configuration change, not a software release.
Do we have to migrate every facility at once?
No. Most operators start with one asset class, one process unit, or one upcoming turnaround. Because intelliVISION scopes data by facility and hierarchy node, additional units and sites come online progressively on the same tenant.
How are historical thickness readings and corrosion rates validated during migration?
Legacy UT readings import into intelliNDT alongside the source system's prior rates. Engineers review short-term, long-term, and governing corrosion rates and tMin formulas in preview before the baseline is locked.
Can our own administrators change forms and workflows after go-live?
Yes. Tenant administrators can update form fields, conditional rules, project templates, budgetary plan rate cards, and language translations directly without opening a developer ticket.
Evaluation path