C-TMS Key Concepts
Aptean
C-TMS Key Concepts
Calidus TMS - 12.45
20th March 2013 - 5.0
Reference: CTMS-KEY
Schedule
A schedule within C-TMS relates to a physical grouping of orders and trips that can be used to refer to a schedule of work. All orders, order lines, trips, trip stops, and haulage activities must belong to a parent schedule, which acts as a container for those key items of data which defines the work that C-TMS is managing.
As such a schedule is a driving entity within the C-TMS system and is used to restrict the view of data presented within forms, reports, exports, interfaces and many other elements of the C-TMS system.
However, the creation of a schedule itself is not something that a user has to necessarily be concerned about, since schedules are automatically created when creating orders in C-TMS.
Schedules generated by the C-TMS application will either have a name of YYMMDD e.g. 020101 (if the date was 1st Jan 2002); this is the default, or WKDAY e.g. 01MON.
In the case of YYMMDD a "Key DateTime" is taken from the order (usually the early delivery date). The schedule has a nominal start time, stored in a system parameter and if the time component of the Key DateTime is after this time, then the date component of the Key DateTime is used as the schedule name, otherwise the previous day is used.
In the case of WKDAY, this format uses the week number and a three-letter abbreviation for the day of the week as the schedule name. For example, in the case of 01MON the WK 01 would represent a schedule for the first week of the financial year and the DAY MON would represent a Monday within that first week of the financial year. The WK part of the schedule name is in fact the number of weeks elapsed since a fixed date specified by a system parameter. (The week containing this date is deemed to be week 1.) The Schedule Start time is used as above.
In the case of YYMMDD, which is the most commonly used format for schedules within C-TMS, (WKDAY does not indicate year so has implications after a system configured in this manner has been operational for more than a year) a schedule can be for any number of days although 1 day and 7 days (a week) are the most commonly used values.
When a user or an interface creates an order in C-TMS, the Schedule module will look to see if a schedule already exists for the Key DateTime that is defined and if it does the order will be placed into that schedule, otherwise a new schedule will be created for that order and any other orders which have the same Key DateTime will also be placed into that schedule too.
Schedules have a status of either 'active' or 'closed'. If a schedule is active then operations can be undertaken on the trips and orders that reside in that schedule, assuming for the operation that the user wants to perform, the trip or order being worked upon is in an appropriate status.
The schedule form is the entry point to the C-TMS application, in that it is the first form that a user would be presented with after they have logged in using their username and password. It lists all of the schedules within the database, their start date and their status and whether the schedule is locked or not. It also provides statistics about orders and trips within the schedule (if the show status checkbox is selected) and allows the user to create a new schedule close a schedule and delete a schedule (assuming that they have the correct access privileges).
The locked by property of a schedule is used if a user is performing an operation that affects the whole of the schedule and the schedule must not be viewed or updated by another user. When this type of activity occurs the locked property would display the username of the user that is running the process that is locking the schedule such as a synchronisation of trips from a planning tool back to C-TMS, once the process that has locked the schedule has completed the locked property would be unset.
Since the schedule form is the entry point to the C-TMS application it is also the exit point in that when a user wants to end their session in C-TMS they should use the Exit button to gracefully exit the C-TMS application.
In general, schedules are created automatically in C-TMS as a result of standard system functionally. Initially, no schedules will exist until transactional data (Order, Booking, Trip etc) is created which requires a schedule for a particular date. The action of creating this data will generate the schedule for you.
There are instances which may require a new schedule, where the C-TMS functionality does not automatically create this record - e.g. Manual booking creation, Fixed Schedules. There exists the ability to create this record manually:
This is actually generated from the main access screen ORI_STATS - no menu selection is required; however, if other screens are open, you may need to:
- Select Window
- <User name> on <database name>
- e.g. SMITHJ on MASTST
The main C-TMS Stats form will be displayed.
The System Parameter SCH_MANUAL_CREATE_SCHED will need to be set to 'Y' in order for the "NEW" button to be displayed.
Create Schedule
Click on the "New" button and the New Schedule window is displayed.
The Access Control Group Function SCH_Manual_Create_SCHED will need to be authorised for use by the C-TMS Group to which user name is applied.
This will default the "Schedule Date" to today's date. Enter the date you wish to create in the format DD/MM/YYYY.
Click the "Create" button to generate a schedule for the date entered.
This will display a refreshed version of the main C-TMS Stats form, highlighting the created schedule.
If a schedule already exists for the chosen date, a pop-up window is displayed showing an appropriate error message.
Delete Schedule
Highlight the Schedule record which you wish to delete from the main C-TMS Stats form.
Click the "Delete" button, this will remove the schedule.
A refresh of the main C-TMS Stats form shows the schedule as removed. Note: this is not yet saved.
Click the "Apply" button to save the deletion.
You can only remove a schedule for which no transactional data occurs, e.g. Orders or Trips. If attempted, a pop-up window is displayed with appropriate error message.
System Functional Areas
| C-TMS FUNCTIONALITY | Description |
|---|---|
| Forms | Standard Oracle 11g Forms |
| Oracle Reports | Standard Oracle 11g Reports |
| Imports | Oracle Forms functionality using WebUtil which allows CSV format data upload from local or network PC |
| Exports | Oracle Forms functionality which will produce a data extract in CSV format and display in a separate web browser window |
| EDI | Automated inbound and outbound file transfer and upload. Both CSV and XML format. |
| Navteq | External web based service to provide Time and Distance information via the Web |
| Oracle Forms Functionality to produce email manually or automatically from various C-TMS functions | |
| Tokairo | External application to provide visibility of non-electronic Proof of Delivery documentation. Automated CSV Extract provides information to TokOpen Web server which feeds an inbound EDI message (via ESI) as documents are scanned. |
| Documents are visible via Oracle Forms functionality and displayed in a separate web browser window | |
| EFX | External application to provide planning, tendering and acceptance information of jobs sent to carriers. EDI interface communicates messages from C-TMS to EFX and from EFX to C-TMS |
| Optimiser | External application to provide planning of orders onto loads/trips, e.g. Paragon, DPS. Oracle Forms functionality to produce Export of orders from C-TMS and Import into C-TMS of planned loads/trips |
| Microlise | External application to provide an outbound trip manifest and receive real-time arrival times and debrief information based on GPS and user activity captured by in-cab units. |
| Isotrak | External Interface to provide real time debrief information of actual collection and delivery times and other load/trip information |
| VB interface hosted on an XP server passes inbound and outbound messages via MSMQ to Isotrak HUB server | |
| Smartphone | External Interface to provide an outbound trip manifest and receive real-time arrival times and debrief information triggered by a driver Smartphone application, mobile network and GPS. |
| EPOD | External OBS application to provide real time arrival, departure and debrief information. Also includes mapping, tracking and route information. |
| MIS | Data flow that can be set up to push large data extracts from configured C-TMS tables to third party data warehousing applications. |
| TTM/LOTS | Live order tracking application linking Warehousing and Transport application data to give an end-to-end view of an order. The web based front end also allows data updating between systems via EDI. |
| Portal | Web based portal allowing real-time data visibility for transport order enquires, also with order updating for suppliers and tracking of delivery items. |
| WCS | External OBS application which controls scanning actions on arrival of goods at depot/cross dock. This supports the remote hand held terminals which can be used to track and record delivery units, supporting order fulfilment for onward planning and internal goods movements. |
}
| Application Functionality | Functional Screen Listings |
|---|---|
| Order Management | Bookings |
| Purchase Orders | |
| Orders | |
| Order Lanes | |
| Order Templates | |
| Order Debrief | |
| Order Tracking | |
| Shipments | |
| Order Entry Targets | |
| Slot Usage | |
| Trip Management | Trip Find |
| Trip Manipulation | |
| Trip Planning | |
| Trip Summary | |
| Trip Overview | |
| Trip Debrief | |
| Fixed Routes | |
| Carrier Trip Management | |
| Carrier Trip Planning | |
| Execution | |
| Loading Management | |
| Trip Message Holds |
| Application Functionality | Maintenance Screen Listings |
|---|---|
| Maintenance | Customer / Cost Centres |
| Resources | |
| Locations | |
| Network | |
| Countries | |
| Contracts | |
| Products | |
| Order Offsets | |
| Business Data | |
| Lane Based Order Entry Admin | |
| Message Maintenance (email) | |
| Accounts | |
| Warehouse | |
| WCS Maintenance | |
| Task Lists | |
| Fixed Routes | |
| Imports | |
| Delivery Targets | |
| SAP Data Maintenance | |
| Static Data Maintenance | |
| Asset Management | |
| Schedule Rules | |
| Carrier Rules | |
| Milk Round Maintenance |
| Application Functionality | Administrative Screen Listings |
|---|---|
| Accounts | Invoicing |
| Payments | |
| Saving | |
| Debrief Invoice | |
| Carrier Invoice Consolidation | |
| File Interface | Imports |
| Exports | |
| Extracts Suite | |
| Interfaces | Interface Errors |
| Paragon Interface | |
| Isotrak Interface | |
| LogiX Interface | |
| EDI Maintenance | |
| Web Services Audit Enquiry | |
| Reporting | Oracle Reports |
| Administration | Audit Log |
| Access Control | |
| Message Monitoring (Email) | |
| Archived Messages | |
| Fixed Schedules | |
| Lock Monitor | |
| System Parameters | |
| Configuration | |
| Task List Inbox |
