IQDoc
ITIQPro Docs Maintenance Connection Everywhere (MCe) · EAM/CMMS manuals
Directory, Sharepoint and other data storage
File loading suggestions and issues

Storage types

Especially for things like DataHub, saving reports

We have a 'safe' access for files, so you can't write or read files except in explicitly permitted places

TypeReliabilityComments
Direct local directory👍Very highThis provides us with the tools to know when the file can be locked preventing changes.
SFTP👍Very highThis provides us with the tools to know when the file can be locked preventing changes.
eMail👋HighOnce it arrives, it is very reliable.
Sharepoint👍Very HighLogin issues, but once you are connected, if we get a file it is 'completed' (no changes pending)
Virtual File System👋HighThis provides us with the tools to know when the file can be locked preventing changes.
FTPS⚠️MediumWhile it has an S like SFTP, FTPS is very different and it doesn't provide the same level of features that SFTP does. It is possible to read a file, unaware that the sender wasn't finished writing to it. We recommend against using FTPS.
FTP🛑LowErrors can occur on transmission, no way for us to be 'sure' the file is complete - it gets bigger while things are being written to it, if no changes for a period of time, typically 10 seconds, it is treated as complete. We therefore strongly recommend against using plain FTP.

Some common ones we define on our SaaSs:

SFTT:\ gives access to files that you sent to your SFTP directory on our server. It is yours and only yours. When used in one database it gives access only to the SFTP directory for that database, when used in another - then you get that other.

Imageserver:\This is default configuration on every system, not just our SaaSs

Discussion:

You can name ones C:\ for on prem, but that shouldn't point at the real c: drive rather a restricted directory on it. If you do point it at the c: drive, the user will be restricted to only the places the IIS user can see so it's not completely dangerous, but in general on-prem you will want to tightly lock where your users of the application can write. Like the SFTP:\ which points at a directory that 'happens' to be where files can be uploaded by SFTP on our servers, it points at a conceptual location.

You can put in confusing ones, like you could define C:\ to point at E:\files\CMMS\, but that will likely cause confusion, so generally it is not advised to have the value confusing like that - but it's your choice onsite.

You can have TWO pointers at the same location. This is both for convenience - you might think about it in two ways - and to allow for changes in storage locations without having to change scripts or values set using the old location.

This is one case where using C:\Files\ (that might point at C:\CMMS\System\Files\ for example, might be maintained even though it is moved to E:\EAM\User\Files\ in the future and maybe the link to it you will use will be E:\Files\, by having C:\Files\ pointing at E:\EAM\User\Files\ as well as E:\Files\ you will avoid breaking the existing use cases while allowing future ones to use the new E:\Files\.

Maybe using a real drive like C:\ isn't the best idea:

Now, this also means - you might not want to even use C:\Anything\ rather have the pointer be CMMS:\ and initially point to C:\CMMS\System\Files\ and later C:\CMMS\System\ and still later point a a Sharepoint or your own SFTP/FTP or FTPS server

Security:

This is not available for setup within the CMMS. This is setup by IT, your IT in on-prem, our IT on our SaaSs. The rights they offer (read, read/write, read/write/directory) restrict you to what you have been offered.

This prevents use of things like "C:\DirYouDontWantPeopleIn"

Once a you get to the physical location, wherever it is, the security is up to you on on-prem. If you allow wide open security on your, so for example Virtual File System directory, then the files that can go or be read there can, from outside the CMMS have that access, but MCe will restrict the access using this tooling to the access IT has decided for each location. Just be aware that we are not the OS, so we can restrict what our app has access to - but we have no control over what you give other apps and users access to.

For the SFTP on our SaaSs, you hold the userid and password. If you let it leak - let us know immediately so we can change it for you. If this happens regularly, there will be Professional Services incurred, but with SMA that is not '0 hour SMA' we permit one change in password per year as part of the SMA, not Professional Services. Note that after we give you your password, we delete record of it and it is not stored in a bi-directional way, so we have no way of looking it up for you.