Grids filters management
- Nicolas Barreau (Unlicensed)
- Laurent Girard (Unlicensed)
This page describes how to handle grids filters in Axiodis especially for the data and constraints module.
Standard filters management in grids
- Option
to manage grid filters (list of existing filters, save current filter or as a new filter, …) - Options to manage filters (create, delete, duplicate)
- Option to publish and share filters for other users :
- Private: the filter profile is visible and accessible only for the user having created the filter
- Public: the filter profile can be visible and accessible for all users for which the filter have been published
- Synthesis of current filters applied on the grid
Specific filters for Transport Operations (TO) grids
In all the cockpits (Planning, Execution management, and Economic management), specifics filters are proposed for Transportation Operation grids :
| N° | Option | Description | Values | Examples |
|---|---|---|---|---|
| 1 | Logistics status | Define a filter based on the list of logistics status to consider transport operations to load in the transport operations grids | All logistics status available in the system | To plan, In planning, planned, ToDo, ..., Ended |
| 2 | Definition horizon | Define a filter based on the time horizon to consider transport operations to load in the transport operations grids | Fixed time horizon : Load transport operations with dates compatibles to the fixed period defined Sliding time horizon (days) : Load transport operations with dates compatibles to the variable period defined based on the current date +/- x days Sliding time horizon (weeks) : Load transport operations with dates compatibles to the variable period defined based on the current date +/- x weeks Sliding time horizon (months) : Load transport operations with dates compatibles to the variable period defined based on the current date +/- x months Sliding time horizon (years) : Load transport operations with dates compatibles to the variable period defined based on the current date +/- x years Routes time horizon : Load transport operations with dates compatibles to the period defined based on the horizon defined and fixed on routes grids | Fixed time horizon : 15/01/2018 - 31/01/2018 Sliding time horizon (days) : 14/01/2018 - 16/01/2018 if current date = 15/01/2018 and -1/+1 days Sliding time horizon (weeks) : 08/01/2018 - 22/01/2018 if current date = 15/01/2018 and -1/+1 weeks Sliding time horizon (months) : 15/12/2017 - 15/02/2018 if current date = 15/01/2018 and -1/+1 months Sliding time horizon (years) : 15/01/2017 - 15/01/2019 if current date = 15/01/2018 and -1/+1 years Routes time horizon : 15/01/2018 - 31/01/2018 if period defined on routes is 15/01/2018 - 31/01/2018 |
| 3 | On route | Define a filter based on the fact that a transport operation is assigned or not to a route | Yes : Only transport operations assigned on a route are loaded in the transport operations grids No : Only unassigned transport operations on a route are loaded in the transport operations grids All : All transport operations are loaded in the transport operations grids independently on the fact that the operation is assigned or not to a route | TO1 assigned to a route and TO2 unassigned to a route Yes : Only TO1 will be displayed No : Only TO2 will be displayed All : TO1 and TO2 will be displayed |
| 4 | Neighboring operations | Define a filter based on the neighboring notion defined on transport operations (logistics areas) | Yes : Only transport operations compatible with the logistics areas defined as neighboring logistics areas for the current user are loaded in the transport operations grids (Those operations are displayed but can't be edited by the user). No : Only transport operations not compatible with the logistics areas defined as neighboring logistics areas for the current user are loaded in the transport operations grids (Those operations are displayed and can be edited by the user). All : All transport operations are loaded in the transport operations grids independently on the neighboring logistics areas definition for the current user (All operations are displayed but some can be edited by the user and others not) | Logistics areas LA1 is defined as management for a user U1 and logistics areas LA2 is defined as neighboring for a user U1 TO1 assigned to LA1 and TO2 assigned to LA2 Yes : Only TO2 will be displayed No : Only TO1 will be displayed All : TO1 and TO2 will be displayed |
Specific filters for Routes grids
In all the cockpits (Planning, Execution management, and Economic management), specifics filters are proposed for routes grids :
| N° | Option | Description | Values | Examples |
|---|---|---|---|---|
| 1 | Logistics status | Define a filter based on the list of logistics status to consider on routes to load in the routes grids | All logistics status available in the system | To plan, In planning, planned, ToDo, ..., Ended |
| 2 | Definition horizon | Define a filter based on the time horizon to consider on routes to load in the routes grids | Fixed time horizon : Load routes with dates compatibles to the fixed period defined Sliding time horizon (days) : Load routes with dates compatibles to the variable period defined based on the current date +/- x days Sliding time horizon (weeks) : Load routes with dates compatibles to the variable period defined based on the current date +/- x weeks Sliding time horizon (months) : Load routes with dates compatibles to the variable period defined based on the current date +/- x months Sliding time horizon (years) : Load routes with dates compatibles to the variable period defined based on the current date +/- x years | Fixed time horizon : 15/01/2018 - 31/01/2018 Sliding time horizon (days) : 14/01/2018 - 16/01/2018 if current date = 15/01/2018 and -1/+1 days Sliding time horizon (weeks) : 08/01/2018 - 22/01/2018 if current date = 15/01/2018 and -1/+1 weeks Sliding time horizon (months) : 15/12/2017 - 15/02/2018 if current date = 15/01/2018 and -1/+1 months Sliding time horizon (years) : 15/01/2017 - 15/01/2019 if current date = 15/01/2018 and -1/+1 years |
| 3 | Filter reference | Define the route date criteria to consider to apply the filter on definition horizon | Route date : Filter on definition horizon is based on the route date definition (attribute "Route date") Route progress : Filter on definition horizon is based on the route realization definition (attributes "Beginning" and "End") | |
| 4 | Neighboring operations | Define a filter based on the neighboring notion defined on routes (logistics areas) | Yes : Only routes compatible with the logistics areas defined as neighboring logistics areas for the current user are loaded in the routes grids (Those routes are displayed but can't be edited by the user). No : Only routes not compatible with the logistics areas defined as neighboring logistics areas for the current user are loaded in the routes grids (Those routes are displayed and can be edited by the user). All : All routes are loaded in the routes grids independently on the neighboring logistics areas definition for the current user (All routes are displayed but some can be edited by the user and others not) | Logistics areas LA1 is defined as management for a user U1 and logistics areas LA2 is defined as neighboring for a user U1 Route R1 assigned to LA1 and route R2 assigned to LA2 Yes : Only R2 will be displayed No : Only R1 will be displayed All : R1 and R2 will be displayed |
Specific filters for Resources grids (Trucks, Trailers, drivers)
| N° | Option | Description | Values | Examples |
|---|---|---|---|---|
| 1 | Definition horizon | Define a filter based on the time horizon to consider on resources (trucks, trailers, drivers) to load in the routes grids | None : Load all resources without any restrictions defined on time horizon Fixed time horizon : Load resources with dates compatibles to the fixed period defined Sliding time horizon (days) : Load resources with dates compatibles to the variable period defined based on the current date +/- x days Sliding time horizon (weeks) : Load resources with dates compatibles to the variable period defined based on the current date +/- x weeks Sliding time horizon (months) : Load resources with dates compatibles to the variable period defined based on the current date +/- x months Sliding time horizon (years) : Load resources with dates compatibles to the variable period defined based on the current date +/- x years Routes time horizon : Load resources with dates compatibles to the period defined based on the horizon defined and fixed on routes grids | None : N.A Fixed time horizon : 15/01/2018 - 31/01/2018 Sliding time horizon (days) : 14/01/2018 - 16/01/2018 if current date = 15/01/2018 and -1/+1 days Sliding time horizon (weeks) : 08/01/2018 - 22/01/2018 if current date = 15/01/2018 and -1/+1 weeks Sliding time horizon (months) : 15/12/2017 - 15/02/2018 if current date = 15/01/2018 and -1/+1 months Sliding time horizon (years) : 15/01/2017 - 15/01/2019 if current date = 15/01/2018 and -1/+1 years Routes time horizon : 15/01/2018 - 31/01/2018 if period defined on routes is 15/01/2018 - 31/01/2018 |
| 2 | Resources planning | Define a filter based on the resource perimeter (Routes optimization, Resources planning, Resources sizing) defined on resources | Yes : Load resources with the following attributes :
No : Load resources with the following attributes :
|