BUSINESS CONTEXTS

CARL Source can be tailored to various business contexts, with prepared customization elements that can be activated as required.

The business customizations can be changed for the contexts:

• Factory: Industrial maintenance management
• Facility: Technical management of real estate assets, infrastructures and networks for service sector companies
• City: Maintenance and technical management of assets for local authorities and administrations
• Transport: Management of transport sector maintenance
• Healthcare: Management of the maintenance and operation of technical and biomedical equipment

Some of these customizations require only simple user configuration, while others require additional configuration of cross-functional elements.

The software offers pre-configured elements for quick implementation of these customizations.
It is still possible to change these elements to tailor the operating environment to the desired context.

Factory

The default CARL Source application is Factory.

No customization is required to view this business context.

The quickest way to restrict access to non-required functions is to set up a Factory user profile from the default standard profile (allowing access to functions in all business contexts).

Facility

Customizing a user to view the Facility context

In order to configure the application in the Facility business context, action should be taken regarding the configuration of a user of this Facility context.
For this user, the following must be filled in at least:

• the "Facility" business vocabulary, 
• the "FACILITY" standard customization group, to apply the forms, menus and visuals of this standardized context used during the user experience
• if necessary, a specific new profile from the standard profile, having removed access to Facility out-of-context and/or not useful functionalities.

Customization of application cross-functional elements (if required)

If the entire application is dedicated solely to the Facility context, it is advisable to rename the "PRINCIPAL" equipment structure code to "LOT_TECHNIQUE" for greater consistency with the customized name (Business vocabulary) of this structure.

Context-sensitive features:

• Locations
• Tenants
• Rental contracts
• Rental receipts monitoring
• Energy points
• Energy billing follow-up

City

Customizing a City user to view the City context

In order to configure the application in the City business context, action should be taken regarding the configuration of a user of this City context.
For this user, the following must be filled in at least:

• the "City" business vocabulary, 
• the "CITY" standard customization group, to apply the forms, menus and visuals of this standardized context used during the user experience
• if necessary, a specific new profile from the standard profile, having removed access to City out-of-context and/or not useful functionalities.

For public financial management using cascading budgets, standard "CUSTOMER" forms may need to be activated.
This activation enables you to benefit from all the mechanisms associated with this context for PURCHASING processes such as Purchase request and Purchase order.

Context-sensitive features:

• Locations
• Companies
• General managements
• Control points

Transport

Customizing a user to view the Transport context

In order to configure the application in the Transport business context, action should be taken regarding the configuration of a user of this Transport context.
For this user, the following must be filled in at least:

• the "Transport" business vocabulary, 
• the "TRANSPORT" standard customization group, to apply the forms, menus and visuals of this standardized context used during the user experience
• if necessary, a specific new profile from the standard profile, having removed access to Transport out-of-context and/or not useful functionalities.

Customization of application cross-functional elements (required)

In the default Transport context, some module settings need to be activated in order to use the mechanisms associated with this context.

The EqptTypeGroup1 and EqptTypeGroup2 module settings must be configured with the "Fixed" and "Rolling" equipment type groups (customizable values if required). This allows you to change the application's behavior towards rolling and fixed assets. This setting is effective for all users of the application.

In the user profiles, rights can then be added to display specific creation menus for assets, work requests and work orders tailored to these specific values.  

When creating work orders or work requests, if a "workCategory" value is identical to one of the module settings values entered previously, and the associated asset is of an equipment type belonging to this same group, the work category field will then be initialized with this same value.

Context-sensitive features:

• Asset with a specific inventory number (Fixed / rolling)
• Specific work report / work orders
• Work order request Work request Service request specific
• Accident

Dedicated indicators and reports:

The EQ_MTBF_TR and EQ_AVG_MTBF_TR indicators adapted for Transport should be used in this business context replacingEQ_MTBF and EQ_AVG_MTBF.

The WO_DETAIL_TR report dedicated to the Transport context should be used instead of the application's WO_DETAIL standard report. You can change the functions associated with these two reports to carry out the replacement.

Healthcare

Customizing a user to view the Healthcare context

In order to configure the application in the Healthcare business context, action should be taken regarding the configuration of a user of this Healthcare context.
For this user, the following must be filled in at least:

• the "Healthcare" business vocabulary, 
• the "HEALTHCARE" standard customization group, to apply the forms, menus and visuals of this standardized context used during the user experience
• if necessary, a specific new profile from the standard profile, having removed access to Healthcare out-of-context and/or not useful functionalities.

Customization of application cross-functional elements (if required)

If the entire application is dedicated solely to the Healthcare context, it is advisable to rename the "MATERIAL" equipment structure code to "INVENTORY" for greater consistency with the customized name (Business vocabulary) of this structure.

There are 3 files relating to the CNEH nomenclature (structure points, families, purchase types) which can be loaded by CARL Source interfaces.
They can be downloaded from the CARL Berger-Levrault customer area.

Context-sensitive features:

• Bottom-up biomedical device recall
• Top-down biomedical device recall
• Pending biomedical device recalls