THE SYSTEMS PARAMETERS
WHAT ARE THE SYSTEM PARAMETERS USED FOR
The Optima LRMS® solution includes many system-level parameters that can be configured during the implementation phase or at any time by your system administrator.
This page provides access to a series of system-level parameters.
The Table below provides description and values that can be used:
Name | Description | Value Num | Value Characters |
| Allow partial scheduling of requests | If a request is partially scheduled because the system is blocked at a given step (due to constraints set in master data): No = when an error is encountered, no scheduling of any tasks Yes = Scheduling of the tasks up to the error | Y/N | |
Allow scheduling beyond completion date | When a request is being scheduled, the Completion Date stated on the scheduling page is verified. If the expected completion of the tasks exceeds the Completion Date: No = No scheduling of any tasks Yes = Scheduling of all tasks regardless of the completion | Y/N | |
Always show the task comments | This parameter specifies whether the comment field is visible and editable in the Create / Edit Tasks Forms - Analytical and Non-Analytical | Y/N | |
Buffer for monthly Recurring tasks | Number of days in advance that monthly recurring tasks are scheduled in the instrument or employee agenda The default value is 180 days. Monthly recurring tasks are scheduled 6 months in advance. | Days | |
Buffer for yearly Recurring tasks | Number of days in advance that yearly recurring tasks are scheduled in the instrument or employee agenda The default value is 180 days. Yearly recurring tasks are scheduled 6 months in advance. | Days | |
Calculate buffer considering holidays at site level | A buffer is the number of days allowed for initiating the scheduling of a request based on its start date or any relevant date set in the request form. The default value is Y (yes), which means that holidays defined at site level are considered in the calculation. | Y/N | |
Calculate buffer considering weekend days | A buffer is the number of days allowed for initiating the scheduling of a request based on its start date (or any relevant date set in the request form). The default value is Y (yes), meaning weekend days are not considered in the calculation | Y/N | |
COMPLETED REQUESTS CAN BE DELETED | When a Request is flagged with status Completed on the scheduling page, The default value is N (no) to prevent the request from being deleted. | Y/N | |
COMPLETED REQUESTS CAN BE UPDATED | When a Request is flagged with status Completed on the scheduling page, The default value is N (no) to prevent the request from being edited | Y/N | |
COMPLETED TASKS CAN BE DELETED | When a Task is flagged with status Completed on the scheduling page, the default value is N (no) to prevent the task from being deleted If Yes the tasks can be flagged as deleted, yet the task is not deleted from the DB | Y/N | |
COMPLETED TASKS CAN BE UPDATED | When a Task is flagged as Completed on the scheduling page, the default value is N (no) to prevent the task from being edited. | Y/N | |
Date format external requests | This parameter specifies the expected date format, controlling and accepting data when uploaded from the Request form (whether via Excel file or through LIMS Integration). | YYYY-MM-DD | |
Date format for MASTER DATA upload | This parameter specifies the expected date format, controlling and accepting data when uploading Master Data Excel files. | YYYY-MM-DD | |
Default Date Format with time | This parameter specifies the format to be displayed in the front end of the application. | MM/DD/YYYY HH24:MI | |
Default Date Format without time | This parameter specifies the format to be displayed in the front end of the application. | MM/DD/YYYY | |
Display batch | When a request process requires grouping lines from the request form and batching samples or lot numbers, this parameter specifies whether the Batch Information is provided in the dedicated column in the Tasks List views. | Y/N | |
Display project | This parameter specifies whether the Project Information is provided in a dedicated column in the Tasks List views. | Y/N | |
Display sample | This parameter specifies whether the Sample Information is provided in a dedicated column in the Tasks List views. | Y/N | |
FTE calculation including weekends | This parameter is linked to the customer configuration feature and assignment of a number of FTE to your customer´s project. This parameter specifies wether the calculation of FTE is including weekends | Y/N | |
HOLIDAYS EXCLUDED IN ALLOCATION CHART | This Parameters specified wether official holidays are omiteed in the display of the Allocation charts | Y/N | |
MAXIMUM SCHEDULING RANGE (DAYS) | This parameter specifies the number of days within which Optima should schedule the tasks of the requests. The longer the range the longer the time of the scheduling process - This is mostly related to enough resources available within a given time range for the amount of request to be executed - | Days | |
Maximum value for yellow (Employees occupancy) | Refers to the maximum % of yellow range in employee occupancy report - above it is red | 90 | |
Maximum value for yellow (Instruments occupancy) | Refers to the maximum % of yellow range in instrument occupancy report - above it is red | 90 | |
MINIMUM INTERVAL (MIN) | This Parameter defines the rounding in minutes for the start date of the tasks | Minutes | |
Minimum value for yellow (Employees occupancy) | Refers to the minimum % of yellow range in employee occupancy report - below it is green | 10 | |
Minimum value for yellow (Instruments occupancy) | Refers to the minimum % of yellow range in instrument occupancy report - below it is green | 10 | |
Reject partial scheduling of requests | If an error is encountered during the scheduling process. This parameter defines whether the request Status is updated to ERROR and no tasks are scheduled | Y/N | |
Rounding task end (min) | This Parameter defines the rounding in minutes for the end date of the tasks. useful when step duration are multiplied by number of samples. | Minutes | |
SCHEDULE IN THE PAST | If a request is coming in with the Start Date in the past from the moment of scheduling No = Tasks are placed from the date of the engine run Yes = Tasks are placed in the past from the Start Date | Y/N | |
Task performance - level of delay 1 | Refers to the delays vs completion tasks in the Lab performance report - Days | 1 | |
Task performance - level of delay 2 | Refers to the delays vs completion tasks in the Lab performance report - Days | 3 | |
Task performance - level of delay 3 | Refers to the delays vs completion tasks in the Lab performance report - Days | 5 | |
Total number of days for scheduling daily recurring tasks | Number of days in advance that daily recurring tasks are scheduled in the instrument or employee agenda The default value is 90 days. Monthly recurring tasks are scheduled 3 months in advance. | 90 | |
Total number of days for scheduling weekly recurring tasks | Number of days in advance that weekly recurring tasks are scheduled in the instrument or employee agenda The default value is 90 days. weekly recurring tasks are scheduled 3 months in advance. | 90 | |
Working hours FTE per day | This parameter is linked to the customer configuration feature and assignment of a number of FTE to your customer´s project. This parameter specifies the number of hours per day per FTE | 8 |
Related Articles
Reports Settings
How to work our your Reports Settings This page allows to work on the settings of the reports, for them to obtain meaningful pieces of information when reports are generated Instruments Reporting Groups In this area, Instrument Reporting Groups can ...Setting the Projects Parameters
HOW TO SET THE PROJECTS PARAMETERS Project This area of the settings allows to list all your projects and assigned them a Project Type. You need to define first all your Project Type in Settings/Project Parameters/Project Types By clicking the Create ...Setting the Tasks Parameters
HOW TO SET THE TASKS PARAMETERS The following sections take through the different steps for the configuration of the Tasks Parameters. Task Status This section displays the different possible Task Statuses. The Edit icon can be used to change the ...THE CUSTOM PARAMETERS
WHAT ARE THE CUSTOM PARAMETERS USED FOR The custom parameters are used to adapt your Optima LRMS® solution to your requirements. Custom parameters can be set at different levels of the system to specify actions for an object (item in the master ...Setting the Sites Parameters
HOW TO SET THE SITE PARAMETERS Locations This area of the settings allows to set a location code for each and every site and/ or departments for which the user would like to have specific series of parameters assigned (eg. users, instruments, ...