The use of SIMS .Net to export data via standard facilities such as ATF, CTF, User defined reports and standard reports is a fully supported and safe way to exchange data with SIMS.

Whilst file formats may change there is no risk to data because SIMS import routines are fully tested by ESS. Customers would expect these to ‘just work’ assuming that for import, the formats provided are correct.

SIMS security settings are fully honoured.

NB: Once data is outside of SIMS, the responsibility to secure the data lies with the producer. 

The use of SIMS Command Reporter to automate the import and extract of data.

The use of these interfaces require that a copy of SIMS .Net workstation is installed on the machine

Part of SIMS and fully supported. 

Easily automated without knowledge of SIMS.  At its simplest, a batch file can be used to run a report and put it in to an agreed folder.  Advanced usage such as filters would benefit from training programmatic automation would be made simpler with training.

SIMS security settings are fully honoured.

NB: Once data is outside of SIMS, the responsibility to secure the data lies with the producer. 

The use of SIMS Third party business objects to read / write SIMS data. 

The use of these interfaces require that a copy of SIMS .Net workstation is installed on the machine

Supported by the Partner Development Support team.  These business objects are designed for easier interfacing but it is still possible to do damage to SIMS data.  These cover a subset of SIMS.

SIMS security settings are fully honoured, although the concept of ‘My’ is not enforced.

The use of SIMS business objects to read / write SIMS data. 

The use of these interfaces require that a copy of SIMS .Net workstation is installed on the machine.

Supported by the Partner Development Support team.  These business objects are the ones used by the SIMS application and may or may not be easily used within the partner’s application.

NB: it is still possible to do damage to SIMS data.

SIMS security settings are fully honoured, although the concept of ‘My’ is not enforced.

Direct SQL access via ADO or other mechanisms are not supported and cannot be accredited as interfaces to SIMS .Net.

We do not publish schema or make an attempt to maintain the signatures of stored procedures across calls.

SIMS security is bypassed completely.