During an implementation or services project, often interim data needs followed up on. This is data collected or obtained between the time of the data being sent to ITpipes and the data going back to the client and/or the new system being used. There are two potential scenarios outlined below.
Interim data created while upgrading from ITpipes Desktop to ITpipes Mobile or Web
We understand inspections will still be happening during the migration and upgrade process. Based on that, we have two options for migrating the interim inspections.
- ITpipes can help you export a dataset and media from ITpipes, using the cut off dates you provide, so the new data can be sent to ITpipes using the form and/or method previously used to send the initial data set for migration.
- ITpipes can set up Sync in the cctv units to continuously sync new data into ITpipes Web, this may require a video conversion process depending on the Desktop setup. This will simply keep syncing inspections during the upgrade process.
Interim data created from 3rd Party App while upgrading to ITpipes
We understand inspections will still be happening during the migration and upgrade process using the 3rd party field software..
Based on that, when the move from the 3rd party application to ITpipes is made, ITpipes requests that you export a dataset and media from the 3rd party application, using the cut off dates based on previous data sent. If a compliance standard such as PACP was used to collect the data, a PACP export is required to migrate this data and media. The new data can then be sent to ITpipes using the form and/or method previously used to send the initial data set for migration.
Please keep in mind if all legacy data is resent, this will take ITpipes time to sort through and longer for you to upload, using the cutoff date to only move “new/interim” data, will save many hours of effort moving data.