CARL Source offers several standard classes that perform database processing: these standard jobs are executed by automated processes.

 

DATA PROCESSING

Calculated checkpoints: Updating the values of calculated checkpoints - CSJOBCALCCTRLPOINT

This job automatically calculates the values of "calculated" Checkpoints.
It takes into account the minimum time interval that must elapse between two automatic calculations (specified for each calculated Checkpoint) before initiating the calculation and updating the value.

Updating users from an external directory - CSJOBDIRECTORYUPDATE

This job synchronizes CARL Source users with an external directory (e.g., LDAP).
The directory data replaces the user data in CARL Source.
The adaptation class for connecting to an external directory is specified in the System Configuration.

 

Indicators: historical calculations or email alerts for out-of-range values - CSJOBINDICATORMAIL

Depending on the selected value, this job:

• Automatically sends an email when the value of a Indicator is outside the minimum and maximum values defined for this Indicator.
  The message sent is based on the message template as indicated on the Indicator, and the recipient can be dynamically specified there.

or

• It automatically calculates and saves the values of indicators marked as "historical."

 

The parameters are as follows:

• Value type:
  • PERIODIC (alerts): This job sends an email alert if the value of one or more Indicators falls outside the specified range.
  • HISTORIC (calculations): This job calculates and saves the values of one or more "historical" Indicators.

• Indicator code: You can specify the indicator to be included in the automatic submission (or logging) when there is only one indicator.
  Otherwise, all indicators (ALL) will be scanned and evaluated; this job will therefore be run for all indicators for which thresholds have been specified (or for all “historical” indicators).

 

Standard job for initiating preventive plans - CSJOBPREVENTIVE

This job automatically triggers preventive plans and creates the corresponding work orders.
It is equivalent to triggering preventive plans using the feature Simulation and Launching of work order plans, by selecting only the Work order plan with a launch type of "Automatic".

 

Enhancing troubleshooting support - CSJOBUPDATEMAINTHELP

This job updates the troubleshooting trees of models and Asset Depending on the Symptoms, causes and Remedies provided information on closed work orders.

The parameters are as follows:

• Work orders closed since: It determines which work orders to address based on how many days they have been pending.
• Reset: Specify the update method: overwrite or append.
  • REINITALL: All troubleshooting trees are cleared before processing.
  • REINIT: Only the troubleshooting trees that have been updated are reset beforehand.
  • APPEND: Troubleshooting trees are simply updated; existing data is not deleted.

• Scope of application: The process will apply to Asset (MATERIAL), to models (PATTERN) or both (BOTH). It is based on the Model and the Asset provided information on completed work orders.

 

Location Initialization Task Asset in CARL Touch - TOUCHJOBINITLOCBOX

This job updates the location of each Asset Already in use across the equipment fleet prior to the installation of CARL Touch.

 

Task to update dates following a new definition of time zones - UPDTS4MODTZ

When a change is made to the time zone definitions, this job retrieves and updates all of the beans For these fields, "date" and "date-time" options are available.
Example : If a country decides to cancel the summer/winter time change for the following year, this change must then be applied in bulk to the relevant dates.

 

Task to initialize the equipment search in CARL Flash - EQPTSEARCHINITJOB

This job updates the column codeAndDescSearch for Asset and the structure points present in the equipment fleet prior to the installation of CARL Flash.
This column is used by CARL Flash when searching for Asset and locations.

 

Task: ANONYMIZATION of CARL Flash Users - GDPRANONYMIZERJOB

This job anonymizes all CARL Flash users who are required by law to be anonymized. The maximum retention period for inactive user data is set by default to 3 years (36 months). This setting is adjustable.

This job updates the status of CARL Flash users by setting it to Canceled and deletes their personal data. It then anonymizes these users in work requests and login history.

 

Automated Email Sending Job - SENDMAILMSGTMPLJOB

This job automatically triggers email messages. It processes only models of the "Automatic Processing" type.

The scenario is as follows:

• Message model: Code for the "Transition" message model associated with the job.

 

Project to AUTOMATE the issuance of rental contract invoices - FMJOBPAYMENT

This job automatically generates payment lines for lease contracts (rent, standard charges, and maintenance charges).
Completion lines can only be generated once the Contract has the status "Validated."

 

Task: AUTOMATE the renewal of lease contracts - FMJOBRENEWAL

This job automatically generates lease renewals, with the exception of those for which the renewal setting is set to "None."

The scenario is as follows:

• Type of renewal : Run the job only for this type of renewal.
  By default, the TACIT and CONTROLLED values are applied.

 

Entity Indexing Job in elasticsearch® - CSJOBINDEXER

This job initiates the indexing of entities in elasticsearch® to make them available for full-text search.

It must be called when CARL Source is run for the first time or when the elasticsearch® content is reset.

The FORCE_REINDEX parameter triggers the reindexing of all entities: it must be used when you need to resolve a discrepancy between the database content and that of elasticsearch®.

 

Mapping task - APPLYMAPPINGSTDJOB

This job allows you to run mapping processes related to data from a CARL BIM model. The process involves retrieving information from the model in JSON format and linking it to CARL Source data (standard attributes, additional attributes, Characteristics, etc.).

The parameters are as follows:

• Stop at the first error: If this parameter is specified, the job execution stops as soon as an error is encountered.
  Otherwise, all import lines are processed even if errors are reported.
• Standard code: Mapping standard applied to data processing. The standard corresponds to the rules defining the relationship between the model data and the equipment present in CARL Source.
• Project : If this parameter is specified, the job will run only on data from the specified BIM project.

 

Job anonymization - GDPRANONYMIZATIONJOB

This job allows you to run anonymization processes on objects subject to the GDPR. The process involves deleting or updating personal data.

The scenario is as follows:

• Item to be anonymized: If this parameter is specified, the job will run only on this object (feature).
  Otherwise, all items identified as “GDPR” are taken into account.

Further details on data anonymization are also available at this page.

 

Job to synchronize entities from an ArcGIS® WebHook - ARCGISWEBHOOKJOB

This job allows you to trigger (manually or on a scheduled basis) a synchronization of entities from an ArcGIS® WebHook.

The parameters are as follows:

• Entities modified after (including): A date used to define a range of entities that will be affected by the process (inclusion).
  If this date and the next one are left [blank], all entities are (re)synchronized.
• Entities modified previously (excluded): A date used to define a range of entities that will be affected by the process (exclusion).
  If this date and the previous one are left [blank], all entities are (re)synchronized.
• Force resynchronization? : If checked, the synchronized data is deleted (synchronization status in CARL Source and data on the entity in the FeatureService ArcGIS®) in order to start from scratch for these entities. These entities are then resynchronized.
• List of entity types to synchronize: List of entity types, separated by commas—e.g., "mr, WO".
  If this list is left [empty], all entity types specified in the WebHook will be synchronized.
• Number of entities to be processed together (batch processing): The number of entities that will constitute a batch during processing.
• WebHook: The ArcGIS® WebHook ID on which to initiate synchronization.

 

Characteristic Integrity Verification Job - CHARACTINTGCHECKJOB

This job allows you to detect (or even remove) characteristics with incorrect values.

The scenario is as follows:

• Read-only mode : If this setting is enabled, the automatic processing will not delete any characteristics but will log the corrupted characteristics in the application log. If this setting is not enabled, characteristics with incorrect values will be permanently deleted.

 

Task to verify the integrity of maintenance process operations - WOPROCDTYPECHECKJOB

This job detects (and even corrects) corrupted process operations—that is, those with an incorrect discriminant value.

The following process operations are being tested: scheduled work orders, approved work orders, and WO templates.

The scenario is as follows:

• Read-only mode : If this setting is enabled, the automatic processing will not correct any process operations but will log the corrupted process operations in the application log. If this setting is not enabled, the corrupted process operations will be corrected.

 

Calculation of linear aging of reading points - CSJOBCALCULAGING

This job calculates the average increase in the meter reading over a period of 'n' days, based on previous readings.

When the process is run, the following updates will be made in the “Average Age” section for each relevant reading point:

• Period (in days): corresponds to the period defined in the job settings.

• Value: calculated by multiplying the average of the daily changes by the number of days in the period.

The parameters are as follows:

• Analysis period (in days) : the aging period.

• Reading point code or "ALL" for all: the code for a reading point or the term "ALL" for all reading points.

IMPORTS / EXPORTS

Data Import Job - EXCHINJOB

This job initiates the execution of one or more Interfaces import from a given external system.
The parameters are as follows:

• External system: Code of the external system on which the interfaces run.
• Interface : Code of theInterface to be executed. If not specified, all active interfaces of the external system will be launched sequentially in the order indicated on the external system.
• Connection point: Connection point used. By default, the one from the external system.
• Authentication chain: User password.
  simple:<Plaintext password> or crypt:<Password as encoded in the database>.
  For example: simple:demo or crypt:fe01ce2a7fbac8fafaed7c982a04e229.

 

Data export job - EXCHOUTJOB

This job initiates the execution of one or more Interfaces export to a specific external system.
The parameters are as follows:

• External system: Code of the external system on which the interfaces run.
• Interface : Code of theInterface to be executed. If not specified, all active interfaces of the external system will be launched sequentially in the order indicated on the external system.
• Predefined filter: If the interface is specified, a filter to apply to the exported data can be selected from among the custom filters.

 

Data import job from a GIS or a BIM model - GISIMPORTJOB or BIMIMPORTJOB

These jobs allow you to import data into CARL Source from a GIS (GISIMPORTJOB) or a BIM model (BIMIMPORTJOB): the tree structure (Points - Asset - Site - Buildings - Premises) as well as all geometries (positions on a plan).

The parameters are as follows:

• Time frame: Execute the job within a specified time frame.
• Stop at the first error: If this parameter is specified, the job execution stops as soon as an error is encountered.
  Otherwise, all import lines are processed even if errors are reported.

 

Job to import external diagnostic reports provided by inspection service providers - PROVIDCTRLIMPORTJOB

This job imports external diagnostic reports provided by inspection service providers.

The parameters are as follows:

• Authentication chain: The User password associated with running the job.
  simple:<Plaintext password> or crypt:<Password as encoded in the database>.
  For example: simple:demo or crypt:fe01ce2a7fbac8fafaed7c982a04e229.
• Supplier : Supplier code (inspection service provider that performed the diagnosis to be imported).
• Organization : The organization code specified in the service provider’s control import configuration. If this field is left blank, the job will apply to all of the service provider’s organizations.

CLEANING

Job to purge obsolete connections - CONNPURGEJOB

This position has two main responsibilities:

• Update the disconnection date for historical records whose date is earlier than a time limit set by the "Maximum number of days for open sessions".

• Delete from theLogin history, the lines preceding the time range specified by the "Number of days of service to be retained".

 

Audit table purge job - CSJOBPURGEAUDIT

This job deletes the audit tables "Items that are older than the number of days specified in the parameter"Number of days of service to be retained".

The parameters are as follows:

• List of tables to be cleaned (separated by commas): The list of tables to which the cleanup should be applied. Items in the list must be separated by a comma (',').
• Number of days of service to retain: The number of days of seniority to be retained.

 

Job to clear the execution history of automated processes - CSJOBPURGEHISTOCRON

This job deletes the result lines from the automated processing "dating back more days than the number spent in the '" parameter"Number of days of service to be retained".

 

Job to purge historical indicator data - CSJOBPURGEINDICVALUE

This job deletes entries from the indicator history table that are older than the number of days specified in the parameter "Number of days of service to be retained".

 

Job to clear the execution history of exchange interfaces - CSJOBPURGEINTEXEC

This job removes the result and error lines from the executions ofInterfaces "dating back more days than the number spent in the '" parameter"Number of days of service to be retained".

 

Purge job for Asset (with footprint) moved or deleted - CSJOBPURGEMOVEDEQPT

This job allows you to delete data related to Asset that have footprints and have been moved or deleted in CARL Source.

 

Temporary Data Purge Job - CSJOBPURGETEMPDATA

This job deletes temporary data generated by the application that is more than 4 hours old.

 

Job to purge messages imported from external systems - EXCHPURGEJOB

This job deletes pending work orders imported more than x days.
This time frame, expressed in days, is configured by Control-S connectors [General] in the "Retention of temporary data".

 

Job to purge "Export" documents - CSJOBPURGEEXPORTDOC

This job deletes the documents generated by the application when processing asynchronous export are performed.
Items will be purged according to a "Number of days of service to be retained".

 

Job involving the entry of corrective inventory transactions - CSJOBPURGESTOCK

This job allows you to delete inventory transactions that contain functional inconsistencies.
It can be run either on an entire Warehouse, on a specific Item, or on all inventory movements (if no parameters are specified).

The parameters are as follows:

• Item code : Run the job only on this item.
• Warehouse Code : Run the job only at this warehouse.

 

Job to purge expired access tokens - TOKENPURGEJOB

This job deletes all authentication tokens whose validity period has expired.

 

Cleaning up the index of actions and messages - TOUCHJOBATNSTGECLNUP

The action index is cleaned, followed by the message index, whenever the main index exceeds one of the two system configuration parameters. IndicesMaxDocCount or IndicesMaxSizeInGB.

If the index becomes “too large,” performance may be affected, in which case it is rebuilt.

A new primary index is created; the old primary index becomes the secondary index; and the old secondary index is deleted.
If the indexes were set to read-only when the disk is nearly full, the job resets the indexes to read-write mode so that the old secondary index can be deleted, thereby freeing up disk space.

If there are still unsent messages in indexes that have been deleted:

• If the message is intended for a CARL Touch client, a reset command is sent to them.
• If the message is intended for a specific category, that category is disabled.

 

Task to purge obsolete connections from CARL Touch devices - TOUCHJOBCONNECTPURGE

This job removes entries from the CARL Touch device connection history for connections made before the date calculated based on the parameter "Number of days of seniority to retain".

 

Job to automatically reset mobile devices after n pending actions - TOUCHJOBCATUPTODATE

This role is responsible for ensuring that the CARL Touch category structure remains consistent with both the technical configuration and the needs of all mobile users.

The technical configuration specifies the maximum number of categories allowed, as well as the minimum number of Users required to form a category.
Based on these parameters, the job reassesses which categories are relevant by comparing them with all mobile users at the time of execution.

 

CATEGORY RECONSTRUCTION TASK - TOUCHCOMPUTECAT

This job is responsible for periodically rebuilding all CARL Touch categories. When this automated process is triggered, all categories will be recalculated, regardless of their current status Ready or Invalid.

By default, this automatic processing is scheduled every 10 days.

 

Job to purge DOCUMENTS UPLOADED FROM CARL Flash - DOCUMENTPURGEJOB

This job deletes documents uploaded from CARL Flash that are not ultimately linked to a work request and whose creation date exceeds the time horizon defined in the settings.

 

GIS Migration

Job #1: REQUIRED FOR THE MIGRATION OF GEOLOCATED DATA - COORDSYSMIGRATIONJOB

This job is The first step To enable the migration of geolocation data from various tables into a single table.

This role allows you to:

• Retrieve the list of SRIDs to be migrated to the CSSY_RESOURCE resource table
• Create a valueList with these SRIDs
• For each SRID, create a corresponding item entry in the CSGI_COORDSYSTEM table (if one does not already exist).
• Finally, for each SRID, check whether geometric data exists. If not, immediately mark the SRID as “Migrated.”

 

Job #2: REQUIRED FOR THE MIGRATION OF GEOLOCATED DATA - GISDATAMIGRATIONJOB 

This job is Step 2 To enable the migration of geolocation data from various tables into a single table.

This role allows you to:

• Checks: Are we able to initiate the task for the relevant SRID?
• Data retrieval for the relevant SRID
• Persist the retrieved data in a single table
• Regenerate the geometric index
• Mark the SRID as migrated

The scenario is as follows:

• SRID of the project to be migrated : The SRID must correspond to a value found in the Coordinate System feature (e.g., SRID = 2154)

 

Job #3: REQUIRED FOR THE MIGRATION OF GEOLOCATED DATA - SWITCHGEOMSTORAGEJOB 

This job is The third and final step To enable the migration of geolocation data from various tables into a single table.

This role allows you to:

• Checks: Are we indeed in a “post-migration” state? Storage mode ≠ SINGLE and Check: no more data managed by GeometryMapper (and not excluded) is marked as “unmigrated”
• Switching the storage mode to “SINGLE” (functionally final status).