Enaimco Support handles bulk uploads for you. You gather the data, send it to us, and we load it into your environment - you do not need to run the import yourself.
There are two ways to get data to us, and which one you choose affects how quickly it appears.
Two ways to send us your data
1. Filled-in templates - the quickest route
Download the template for the record type you want loaded, fill it in, and send it to Enaimco Support. The columns already match our importer, so we can load it much as it arrives.
2. Your existing documents - no reformatting needed
If filling in templates is not practical, send us what you already have: an asset register, an anomaly spreadsheet, an export from your current integrity software, a document register. We will take it as it is.
These take longer to appear in your environment. Our Solutions team has to translate your format into the import format first, and how long that takes depends on how the data is structured. If you are not sure whether something is usable, send it and ask - it usually is.
You can mix the two methods of sending us data. There is nothing wrong with sending your assets as a filled template and your anomaly register exactly as it comes out of your current system.
Rules that apply to every template
Following these means we can load your data on the first pass instead of coming back to you with questions.
One row per record. Do not merge cells, split a record across two rows, or rename the header row.
Dates as YYYY-MM-DD. 2024-06-18, not 18/06/2024. Regional date formats are the most common reason a whole file fails.
Yes / No columns. Yes, Y, TRUE or 1, and No, N, FALSE or 0 all work. Blank means not set.
Numbers as digits only. Write 310, not "310 Nm" and not 1,250. Leave out units and thousands separators.
Dropdown columns. Pick from the list of acceptable values. If none of the options match how you record something, leave it blank and tell us rather than forcing a value - we will agree a mapping with you.
A blank beats a guess. An empty optional column is easy to fill in later. A wrong value looks like real data and tends to stay.
Keep names and IDs consistent. The same asset, person or file should be written identically everywhere.
Download the templates
Fill in only the ones that apply to the modules you are using. Anything that does not apply can be left out entirely.
Record type | What it covers | Columns | Template |
User | Everyone who needs access to Enaimco, and the names that anomalies, notes and actions get attributed to. | 4, of which 2 required | |
Asset | The hierarchy itself - every structure and component, how they nest, and their status, key dates and life figures. | 23, of which 4 required | |
Asset Identification | Alternate identifiers for each asset: SAP IDs, legacy IDs, client tags, plus optional deep links back to your systems. | 4, of which 3 required | |
Document | The register of your document files - title, type, originating supplier and review state. | 5, of which 1 required | |
Document Revision | Revision history for each document: revision label and date. | 3, of which 3 required | |
Document Document Number | Client, vendor or DMS document numbers for each document. | 3, of which 3 required | |
External Document | Documents that stay in your DMS, recorded as a link rather than a copy. | 5, of which 1 required | |
Asset File | Which documents belong to which assets - the link that makes drawings findable straight from the 3D model. | 2, of which 2 required | |
Asset Note | Free-text notes and history recorded against an asset. | 9, of which 3 required | |
Anomaly | The anomaly register: what was found, where, how critical it is, when it was found and by whom. | 18, of which 8 required | |
Anomaly Revision | Re-inspection history for each anomaly, which is what lets Enaimco trend it over time. | 9, of which 6 required | |
Anomaly Action | Remediation actions raised against an anomaly, with owner, due date, priority and status. | 7, of which 4 required | |
Anomaly Note | Free-text notes recorded against an anomaly. | 9, of which 3 required | |
Anomaly File | Which media and documents relate to which anomaly, and to which revision of it. | 3, of which 2 required | |
Valve Operation Log | Valve manipulation history: position, turns, torques and indicator condition for each operation. | 15, of which 1 required | |
Photo | Details for each still image: title, capture date and campaign. | 5, of which 1 required | |
Video | Details for each video: title, description, dive, work order, campaign and clip length. | 9, of which 1 required | |
Asset External Document | Links a DMS-hosted document to the asset it describes, without copying the file. | 2, of which 2 required | |
External Document Document Number | Client, vendor or DMS document numbers for documents that stay in your DMS. | 3, of which 3 required | |
Anomaly External Document | Links a DMS-hosted document to an anomaly, and optionally to one of its revisions. | 3, of which 2 required | |
Valve Attributes | Valve engineering data: ROV interface and torques, pressure and temperature ratings, weights and flow path. | 29, all optional |
Each template explains itself. Row 2 describes every column in plain language. Hovering a column name shows its data type, whether it is required, and the accepted values for dropdown columns. Row 3 is a shaded example row showing the expected format - we remove it, so either overwrite it or start on row 4.
A note on IDs and codes
Enaimco generates its own numeric ID for every asset, so leave the enaimcoId column blank when you first send us your hierarchy. Put your own tag in the name column - that is what your team will search on.
Once your assets are loaded we send you an export listing each one alongside the ID we assigned it. The asset_ref and parent columns in the other templates use that ID. If you would rather keep working in your own tags, put those in instead and tell us - we will translate them.
Anomaly codes work the same way. Enaimco generates them too, so leave the code column blank. They are incrementing alphanumeric codes whose prefix comes from the anomaly type in your code list, so LK37 and LK38 are leaks 37 and 38, and FS12 is freespan 12. We return them in the same export, and the anomaly_ref column in the Anomaly Revision, Action, Note and File templates uses that code - or send your own register reference and tell us, and we will map it.
An asset and its parent cannot be created in the same file. If you are building a new branch of the hierarchy, send the parent assets first and their children in a second file - or just tell us and we will sequence it. Rows whose parent does not yet exist are rejected rather than guessed at.
Things we set up rather than import
Some things are configuration rather than records, so there is no template to fill in:
Risk matrices - threat categories, Consequence and Likelihood of Failure ratings, and the criteria behind each level
Anomaly code lists, code descriptions and severity levels
Inspection task libraries - which inspection applies to which asset type, and how often
Asset identification types, such as SAP ID or Client Tag
Live video connection settings for ROV feeds
Send us the document behind each one - your anomaly guidelines, risk register, RBI study, IMR strategy or DVR manual - and we will configure it with you.
Files, drawings and models
The Document, Photo and Video templates carry information about files. The files themselves come across separately, and the file name is what links the two - so please do not rename anything after sending us the accompanying list.
Photos and videos. See How do I upload inspection video and media files?, and Uploading files with Azure Storage Explorer for very large sets.
Drawings, GIS and CAD. Field layout drawings, AutoCAD files, GIS datasources, general assembly drawings, P&IDs and O&M manuals have no template. Send them to Enaimco Support and we will build your 2D map and 3D model from them.
What happens after you send it
We load your data and check it. Any row we cannot load comes back to you with a plain-language reason - just the rows that need a decision, never the whole file again. Rows that did load stay loaded, so partial data starts being useful straight away and you do not need to wait until everything is complete.
If a register is going to take a while to pull together, tell us. We would rather load your assets now and your valve history next month than hold everything back.
Related articles
Still not sure whether your data can be used? Send it to Enaimco Support and ask - we will tell you what we can do with it.