How to set up sample sharing through child areas

Modified on 2024/05/28 08:50 by MKR Categorized as How to, QCX Core V8
Note that this is only available for QCX 8.7 and onwards.

'''1. Setting up sample sharing'''


The set up consists of two parts. First, setting up the child area(s) to be shared samples with, and second, tag mapping the relevant tags to each child area. It is important to note that the recipes on the parent and child area does not need to be identical. The user chooses which parts to share, but there must be a recipe on both the parent and child area for the samples to be shared. Also note that a sample received from a parent area will not appear under Active Samples, but will be in the Sample Viewer.


'''1.1 Child area set up'''


In the FLSmidth Discovery tool, there is a tab called Child areas. This tab shows all existing child areas that are connected. In the picture above, it can be seen that one such area has already been established. To add a new area, press Add area.


[image:{UP(How-to-set-up-sample-sharing-through-child-areas)}Child Areas.PNG|medium|left]











The below screen should now appear. Area designation is the name that the user gives the child area, and is shown in the above picture in bold letters. '''Host designation MUST be the name of the child area server, if the IP adress is used it is not possible to browse the child area tags'''. In the above picture VMTest-2 is the server name. After entering the Host designation and pressing Apply, it should appear below Area designation in blue lettering. Press OK to continue. The window should now close, and the Apply button on the above picture should now be pressed to finalize the new area.


[image:{UP(How-to-set-up-sample-sharing-through-child-areas)}AddChildArea.PNG|medium|left]
















'''1.2 Tag mapping samples'''


After the child area(s) have been made, it is possible to start setting up which samples and procedure data to be shared. This is done in System, Configuration, Core, Ref, TagMapping, as seen below. MyTagId is the local tag, and MappingTagId is the corresponding tag on the child area. It is possible to simultaneously tag map a single local tag to tags in multiple child areas by making the mapping for each child area.  
'''Remember to include ALL DATAITEMS! Also Derived items'''


[image:{UP(How-to-set-up-sample-sharing-through-child-areas)}TagMappingScreen.PNG|medium|left]














For sharing a sample, it is necessary to tag map the following tags:
* Data items  (All data items! Also derived items)
* Sample points
* Material Types
* Master Procedures
* Equipment (optional)
* Equipment functions(optional)


What each of these does is explained in the sections below.


When tag mapping, the below window will pop up to allow the user to search through all areas (local and child). It can here be noted that the LocalArea will always be the local area of the parent server, while the child areas will have their server names, as seen when they were set up in 1.1.


[image:{UP(How-to-set-up-sample-sharing-through-child-areas)}TapMappingExample.PNG|medium|left]
















'''1.2.1 Data items'''


Data items are the oxides, residues, etc., which have been set up for the procedures. When transferring procedure results, any data items, which haven’t been tag mapped will be left blank, so it is important to tag map every data item that needs to appear on the child area, including derived data items like the Lime Saturation Factor.


The Data Items can all be found under the area, Qcx.DataItem. path.


'''1.2.2 Sample points'''


Sample points are the points, where samples have been taken. A single sample point with multiple possible material types need only be mapped once.


The Sample Points can be found under the area, Qcx.SamplePoint. path.




'''1.2.3 Material Types'''


Material types are the raw material of the sample. If multiple sample points use the same material type, the material type need only be mapped once.


The Material Types can be found under the area, Qcx.MaterialType. path.




'''1.2.4 Master Procedures'''


Master procedures are the procedures from the recipes. An XRF procedure on a parent area can be tag mapped to an offline procedure on a child area as long as both are set up with the data items to be shared. The user doesn’t need to map all procedures in a parent recipe if only the results of a single procedure is needed on the child area.


The Master Procedures can be found under the area, Qcx.RecipeMan.MasterProcedure path.




'''1.2.5 Equipment'''


The equipment tag mapping is optional, but recommended if the equipment tag is used to differentiate between different data items in for example the reporting. Using this tag mapping swaps the equipment used for the parent area procedure with the equipment that was used for the child area procedure. For instance, if the parent area has an XRF installed, but the child area uses the Offline equipment instead.


The Equipment can be found under the area, Qcx.Equipment path.




'''1.2.6 Equipment function'''


Like the Equipment, this is optional, and swaps out the parent area function name for a specific equipment to the child are function name for that equipment.


The Equipment Functions can be found within the area, Qcx.Equipment path by selecting the equipment and opening the below folders until the folder ending in Function is reached.


1.Setting up sample sharingThe set up consists of two parts. First, setting up the child area(s) to be shared samples with, and second, tag mapping the relevant tags to each child area. It is important to note that the recipes on the parent and child area does not need to be identical. The user chooses which parts to share, but there must be a recipe on both the parent and child area for the samples to be shared. Also note that a sample received from a parent area will not appear under Active Samples, but will be in the Sample Viewer.
Meta Keywords: Child, Child Area, Export, Import, Sample, Sample sharing
Meta Description:
Change Comment:
FLSmidth QCX wiki

How to set up sample sharing through child areas
