Frequently Asked Questions
Common questions about the OCRIS suite and methodology.
We operate on the assumption that there is often a poor connection between the remote loggers and the database and with this assumption in place we utilize a process that creates an export file from Mobile that is then imported using tools in our Toolbox application. The single file from OCRIS Mobile can be sent to a remote server and loaded to the database via a data manager or as a scheduled task if appropriate. We have in the development pipeline direct logger to database connectivity if the comms are up to specification.
Our Mobile product works on Windows XP to 8.1. We do not support IOS or Android at this stage.
Yes, that is the standard implementation.
Yes, as part of the configuration of the Logger it is possible to set a variety of rules that ensure only valid data can be exported. Rules include unique keys, required fields must be populated, only valid codes can be entered, only valid numeric ranges can be entered, we can do inter-table and intra-table validation. Users are given visual feedback if a value in a cell is not compliant and if the validation level has been set to Fatal then the data will not be exported. Users can however continue to do data entry if there is an error on a row as it might be a case where entry is done via columns rather than rows and we do not want to stop entry by columns.
Completely! The worksheets you have, the columns on those worksheets, the library codes on those columns are all to your requirements. We have a very strong model for drilling, geotech drilling, channel sampling etc which you are welcome to take advantage of but if you have a particular way of doing things then our system will cater for that
Calculated values are done at the time of configuration, it is not a user enabled feature.
We capture a variety of metadata in Mobile relating to the data entered including which computer, which user, what time. In addition to this row by row metadata we also capture when a file was exported, who did the export, what was the original export file name. Once the data has been successfully exported we lock that row to prevent changes happening in the field, if there is a problem identified then it is fixed at the database level which also has a complete audit of all and every change made to the data.
No! There is a deliberate design feature that precludes field people making changes to the Logger configuration. The update process however is very simple and any changes required can be done via a supplied upgrade package. The update can be generated via the OCRIS Mobile Admin tool which is available to you with the master configuration stored on a Cloud server.
Our default implementation is multi-project with a Project defined by you.
YES. Our Database management system runs on SQL Server 2008R2 and above. We do support SQL Express in these versions but recommend a full SQL Server licence is used to ensure ease of setting up maintenance plans etc.
YES. We have a very well established data model with all the base tables, relationships, triggers, stored procedures and functions to ensure always accurate data. Built into the system is the ability to configure “Domains” to store and display data in the way you want to see it. All data in these domains is then stored in our base tables.
Completely configurable to suit your needs. Natively we capture data as either interval, at depth or no depth related and from this it is possible to capture and manage data from any role. We have wizard based tools to make the configuration process very quick and simple.
The process of setting up domains is very straight forward and all you really require is an understanding of the data types you have and the relationships between those datasets.
This can be done either via direct connection to views in the database or via exports to industry standard formats. It is possible to setup recurring export templates where data is dropped out in the same format each time or on an ad-hoc basis from Data Views. It is also possible to run a cascading export from a data view that honors all filters applied to each level of the data.
Yes. We support databases around the globe and are currently rolling out systems for exploration and mining in Indonesia and Brazil. We have systems in Canada, China, various African countries, SE Asia, South America and of course Australia. We have systems for all commodities including Diamonds, Coal, Iron Ore, Gold, Copper, Uranium, Water. It doesn’t actually matter what a client is exploring for as we can tailor Domains to suit the different geological terranes and the Results Manager to look after any analytes without the requirement to make any structural changes to the underlying data model.
Absolutely, our system is based on DepthFrom, DepthTo or DepthAt and these can be in Metric or Imperial. If there is going to be data that covers both systems then we would include a flag at the header level to define what units of measure the related data is in.
We have a fully blown Results Manager to handle data from labs supplied in industry standard formats. No manual data entry is required (indeed it is not possible to manually enter Results data for very obvious reasons). Our Results Manager is a dispatch centric system so we can check that data supplied from Labs actually complies with what was requested by the client. Any deviation from the request is automatically flagged and can be rectified during the results file loading process. As more files are loaded from a Lab more mappings can be created so that future loads become much faster. With our Results Manager it is possible to validate and load multiple files in a single operation. We also have full inline, interactive QC charting to check on the integrity of the results and if a job is not up to spec it can be quarantined to ensure it is not used for resource work. It is then possible to load in later jobs that may have been redone
We have about 100 clients running OCRIS Mobile and I would be happy to supply a few reference sites to you once I get permission to do so from the users.
We have full training packages for both OCRIS Mobile and OCRIS Toolbox. Mobile is a very simple program to use and the training is done in around 4 hours. Obviously the full data management package is a bit more involved and we tailor the training to suit a person’s role within an organization. We typically complete site training over a week to cover Management and User level use of the system.
We offer phone, email, skype and Team Viewer support for remote sites. Support and upgrades can be provided via remote connection if the Internet connection has sufficient bandwidth. We do this remote support for quite a number of clients around the world.
We cater for all different user requirements, our system does not put limitations on the type of data that is captured, transferred, managed and reported.
Reports are completely configurable from Strip logs through to pie charts. It really depends on what you want to get out of the system.
While we now primarily promote our own OCRIS database management tools, we have a long history of supporting GBIS/Geobank and can help you get value from your investment in that system. Most of our tools work seamlessly with GBIS/Geobank (as well as other geological data management systems).