Introduction
This is a manual on how to set up the export/communication from QCX to ABB TiS system based on examples from upgrading old QCX V7 to QCX V8.
It is based on 2 sites in Indonesia: LafargeHolcim Cibinong Naragong and LafargeHolcim Cilacap.
The Holcim – Narogong (Indonesia) project was an upgradation of QCX V7 to QCX V8.
The V7 system transferred sample analysis results to the customer’s ABB TIS system.
The TIS system was configured to receive xml files from V7 system by ABB. It had sampling locations (sample points), material types, data items, equipment names and even the file name format preconfigured, with respect to the V7 system.
The challenge was, the new names of the V8 system was not accepted in the TIS and it gave an error for the xml file. The name of the xml file generated should be same as the file name format in V7, only the XRF results are to be exported and they must be kept in the same shared folder which is in V7 system.
1. XSLT Conversion File
For every sample export an xml file is generated. An xslt file transforms the xml file into the required format accepted by TIS (which is also an xml file). The below conversions were made with the xslt file.
1.1. Equipment name conversion
The names of XRF equipment in V7 were ‘XRF1’ and ‘XRF2’, but in the V8 system they were ‘WinXRF01’ and ‘WinXRF02’. They had to be converted in the xslt conversion file.
1.2 Sample point & Material type name conversion
The names of sample points and Material types in V8 system must match with those in V7.
This was also done in xslt conversion file.
1.3. Data item renaming
The names of the data items used in V8 system must be the same as in V7 system. So, the names were changed in the V8 system to match with V7 and then be accepted by TIS.
2. Selecting the export Procedure
This is very important to do expecially on the Raw Mill sampels as they go to BLX. If not set QCX will generate an export for all instances of BLX accountint and 20+ files are exported! it is only the files generated from the XRF that should go to the TiS system.
Now we must specify which procedures to include in the export, this has to be done in Generic Editor
(System->Configuration->Configuration).
Under
Qcx->Core.Config->OutputTray find the data exports that was configured in the QCX
Import/Export Editor, and select ExportSelection under each of these, there will be more options to control what is exported
Now select ExportProcedure, and add specific procedures that must be exported –add the
XRF procedures here (add all procedures related to XRF)
The Designation needs to be unique, but we normally name them like
(ExportName.SamplePoint.MaterialType.Procedure).
Then to select the Procedure, use the tag browser and find:
Qcx->RecipeMan->MasterProcedure
Under this, find the XRF procedures:
With this configuration, we should only get the results from XRF in the Output tray and the XML files.
3. Changing File Name
The generated xml file had the names in the format ‘QcxExport_
_.xml’. But TIS accepted file only in the format ‘LAB_RES__.xml’.3.1. Using PowerShell Script To do this PowerShell script was used. The script needs to be adjusted with the actual folder names you use on site – the first two lines defines the source and destination folder For this to work you should make another folder next to Xslt and Xml folders, e.g.: XmlLabRes, but that can be any name. The new script will copy and rename the files from Xml to this new folder
This folder contains the data export files from QCX V8. - The Xslt subfolder contains the raw xml data export files - The Xml subfolder contains xml files which are copied from Xslt folder and transformed through Xslt transformation. The Xslt transformation is done by the QCX system immediately after the data export - The XmlLabRes subfolder contains xml files which are copied from the Xml folder and renamed from QcxExport to LAB_RES. The copy and renaming is done with a PowerShell script which is executed on a Windows Scheduled task.3.2. Running PowerShell script on a schedule Move the PowerShell script file to a location on the server, such as the FlsData folder. Be aware there is a limit to the length of the path when used in Task scheduler - if this is exceeded the script will not run.Open the Task scheduler from Control Panel->All Items->Administrative Tools
Create a new scheduled task, with name and description • Ensure "Run whether user is logged on or not" is selected
Configure the trigger to run repeatedly
In Actions, add an Action to "Start a program":
