fare.logiQ enables the management of sales and booking data with devices from different manufacturers. At the heart of fare.logiQ is a central multi-client-capable database that manages both sales-related data supply from vending devices and all data disposal accounting information from vending devices.
Standardised interfaces simplify data exchange with devices from a wide range of manufacturers. Technical and professional data checks ensure that the data stock is correct and complete, thereby providing security. Driver accounting, manual re-entry and the option of importing data from third-party systems make fare.logiQ a powerful sub-ledger with revenue management.
Featuring extensive exports, statistics and preparation for transport service accounting, the functionalities are supplemented to form a complete system that can handle even the most complex public transport requirements. Furthermore, fare.logiQ can be used regardless of manufacturer. In an extended form, fare.logiQ can be deployed as a central component of the highQ mobility platform. In this context, the mechanisms applied in the public transport environment have also proved to be useful for multimodal processes within the networking of regional mobility service providers.
fare.logiQ is an MS Windows-based desktop application that can also be used as a central installation for remote or metaframe access.
through the direct connection to all your sales channels
takes place via driver accounts
can be made in the back office
the highQ sales system TicketApp and fare.logiQ complement each other perfectly
the device layers are checked for completeness
(optionally with safebag management)
shifts can be booked collectively
can be settled by accounting
fare.logiQ offers a wide range of configuration options. The multi-level user administration follows a detailed role concept, which allows you to clearly define individual application areas. Client control can thus be based on a central database. All master data relevant for the accounting of public transport operations is defined in meaningful dependencies on several differentiation levels. Organisations are assigned to the clients, to which in turn are assigned the sales units (drivers or operators of the sales devices). In addition, lines are assigned to franchises and these in turn are assigned to franchisees.
The integrated dual control principle can be activated to ensure that modifications only become effective after they have been confirmed by another user. Import and export options are available in HUSST format for both device and personnel master data. This enables you to maintain the data centrally before distributing it. Among other things, this is also where you can configure revenue accounts, key posting figures and line concessions to enable automatic assignment during processing.
The HUSSTkon conversion module is used for the automated import of data in the format of the vendor-independent HUSST standard interface. Sales data is imported from the connected distribution systems of different manufacturers. HUSSTkon is a stand-alone programme that is also available as a Windows service and does not require manual operation. The XML-format data is cyclically read in from a specified directory, checked and archived. In general, this requires that the XML format used in the data is correct.
When importing sales data, a plausibility check is carried out against the device, personnel and tariff master data stored in the central database. Depending on their characteristics, incorrect data is either flagged as such in the database or not imported at all and stored in file form in a special error directory. At the same time, extensive process and error logs provide information about the type of errors and what measures need to be taken to correct them.
Correctly incorporated data is already pre-sorted by HUSSTkon for accounting and statistics purposes on the basis of a corresponding configuration in the master data. Key posting figures linked to revenue accounts and line concessions, for example, can be directly assigned to sales. This makes it much easier to perform statistical evaluations later on.
The HUSST format allows you to maintain tariff data, device or personnel master data in addition to sales data. Both export and import options are available for this purpose. As a result, fare.logiQ can be flexibly deployed – as the dominant system for data supply or integrated into existing environments.
As a further import option, Safebag data from money counting service providers or booking data from payment terminals can also be incorporated via file interfaces.
To guarantee the completeness and correctness of the data stock, fare.logiQ provides mechanisms and data views that allow comprehensive control of the technical condition of the sales devices. Connection control is used to monitor the completeness of the imported sales data. Here, individual devices as well as definable device groups can be automatically checked for existing gaps with regard to the consecutive numbering of the sales shifts for each device group and device. The shift gap report generated in this way provides detailed information. It can be generated in either PDF or MS Excel format.
In the event that missing sales shifts can no longer be delivered, e.g. if a device is defective, you have the option of pre-booking. The corresponding shift data can be manually entered – this option can be explicitly activated for specific users by means of the multi-level user administration. It is also possible to control the activity of individual devices. This allows you to determine whether there are devices that have been inactive for long periods of time.
All sales processes from staff-operated sales as well as from ticket vending machines are combined in sales shifts that are checked and accounted for via fare.logiQ. Operator accounts are maintained to check the cash receipts of drivers, train conductors or ticket inspectors.
The cash collected can be assigned to the operator account, either manually or automatically by importing Safebag data from a cash service company. In the case of manual allocation, a distinction can be made between whether the payment was deposited by the operator into a bank account or delivered in cash directly to the clearing centre.
A shift corresponds to a debit position that needs to be balanced by the corresponding amount on the operator account as a credit position. To enable a flexible differentiation of the shifts to be recorded, shifts can be collectively booked. Depending on the configuration, this can be done either manually or fully automatically. The decisive factor is that the operator account has sufficient funds. This removes the need to carry out strict shift-based accounting. Shift bookings are consolidated in daily statements, which are assigned to the respective fare.logiQ user. Open item lists provide a quick overview of shifts that are yet to be booked.
There is a special procedure for invoicing contractors. In this case, the system does not use individual operators. Instead, the organisation assigned to the operators is used as the differentiator for the collective posting. This produces a corresponding receivable from the external company.
Subsequent additions and deductions can be performed via fare.logiQ, such as targeted cancellations of individual sales, subsequent voucher submissions or the retrospective booking of block sales. These are then not only reflected in the operator accounts, but also in the statistical data and the monthly association reports. The operator account statements are fixed during accounting month-end closing and can afterwards be sent to the operators. These statements provide detailed information on all cash transactions affecting the operator, including any manual corrections made by the clearing centre.
Revenues are not limited to income from ticket sales. Substitute student transportation, product sales, financial subsidies or revenues from association invoicing are only a few examples that require an additional booking option. fare.logiQ enables this in several modules that have been adapted to different requirements.
Transportation revenue can be recorded by line and allocated on the basis of predefined booking combinations. In the process, you can use the master data to assign revenue accounts to the selectable key posting figures. A receipt is issued at the end of the posting procedure. In addition, both debtors and creditors are maintained in the master data, for which revenue postings can be created on account.
External revenues, such as those from cooperation agreements with tourism providers, are posted to vendor numbers that are likewise stored in the master data. Similarly, other posting types have their own specifically defined revenue accounts, which are transferred as balanced data records during export to general ledger accounting. Entered items such as amounts from change or cash deficits are also receipted. This ensures that all transactions can be transparently traced.
All accounting transactions are consolidated in daily closings, which are assigned to the respective user of fare.logiQ. The daily closing is not related to a calendar day and can be finally closed at any time. After that, no further changes can be made to the respective accounting items.
The final daily closing is assigned to the current monthly closing. The month-end closing is assigned to the calendar month. As long as there are no open daily closing dates, a final month-end closing can be performed that consolidates all assigned daily closing dates. In the process, different printouts provide information on monthly totals, for example relating to distribution channels, payment types, products, or revenues per organisation.
With regard to both daily and monthly closing, corresponding exports can be generated for downstream general ledger accounting. SAP R3K interfaces are already available in fare.logiQ for this purpose.
All sales and booking data in fare.logiQ are stored in a central database with a relational structure.
An easy-to-use interface is provided to create and save statistical analyses based on SQL queries. For this purpose, there is a default set of standard evaluations. Evaluation variants can also be created or adapted by the user. As an option, a business intelligence tool is offered to create a graphical representation with interactive editing.
The user interface displayed via the statistics evaluations can be used to select preset evaluation variants. After selecting a date range and, if required, setting the desired filters (this is possible for each field of the query), a corresponding evaluation can be created at the push of a button.
Default settings include sales per month, organisation and product; sales by day of the week; usage according to sales location, start location and destination.
Via settings on the user interface, the result of a statistical query can be generated either as an MS Excel file or as a semicolon-separated CSV file.
Query variants can be freely defined by users with special authorisation. A set of possible fields is provided, which can initially be configured as desired using a selection box. Once this has been done, the attributes “Display”, “Group”, “Totalize” or “Filter only” can be displayed for each field via a further selection box. Finally, each field can be assigned a filter value. After completing the input, the resulting query variant can be given a name and saved. The system then generates a template in MS Excel format. This can be edited and permanently used as a template for this query variant.
As a result, even users without database knowledge can generate statistical overviews of their business activities, such as sales revenue per line, information on passenger counts or ticket use.
fare.logiQ also enables the creation of a reporting month that is independent of the accounting month and is controlled by the user. This enables a clear differentiation of the monthly allocation of sales data. Subsequently, reports can be generated for associations on the basis of the tariffs sold. The sales data is formatted according to individual requirements and, if necessary, additional information can be added and formatted. In the process, simple CSV files can be generated or report templates for the association can be filled directly, for example in MS Excel format.
The creation of reports can be marked as final on a monthly basis, thus guaranteeing unambiguous traceability, even independently of any data that may subsequently be incorporated. These reports are assigned to the following month as follow-up reports.
For mapping analyses with flexible reporting, fare.logiQ offers an optional browser-based, multidimensional business intelligence system (BI tool). This allows the user to create individually configurable reports at any time and to display them in graphical as well as tabular form.
This BI system corresponds to a platform with freely configurable evaluation and reporting functions, whereby a wide range of evaluation variants are possible.
The system allows the creation of any kind of evaluation for which the corresponding raw data can be imported from the database (automated daily import job). As an output form, the user can choose between exporting to PDF or printing a hard copy, as well as viewing the data digitally on a PC or smartphone/tablet.
Thanks to interactive control of individual query elements, viewing the digital statistics with the business intelligence system offers a particularly flexible and transparent view of the data. The view can be quickly and easily extended or restricted by clicking on the graphic.
fare.logiQ is equipped with an interface to transport service accounting (TSA). For this purpose, revenues from the sales devices already assigned to the corresponding lines during data conversion are used together with the additional revenue postings from association/partner company billing or subsidies, which are assigned to the corresponding line during data entry. Revenues from non-relational sales that cannot be assigned to a line are initially assigned to a fictitious line.
To prepare the data for the TSA, the line-related revenues are compared with the line kilometres travelled. A VDV-compliant interface is available for recording the line kilometres, meaning that the data can be imported directly from a planning system. For individual assignment and especially for the resolution of the amounts initially assigned to the fictitious lines, the values can be edited manually in the master data administration, allowing distribution keys and corresponding weightings to be specified.
In an export run, this creates the data required for the cost-benefit calculation in the TSA. The system supports the Deutsche Bahn “TSA Bus” interface
Perfectly organised VDV-KA level 3. Using standardised interfaces, CiCoLo from highQ offers comprehensive check-in / check-out management. With (((eTicket Deutschland and the associated standardisation of data interfaces, the Association of German Transport Companies (German abbreviation “VDV”) offers a specification that fully supports CiCoLo. If you are planning to expand your transport services with a standardised procedure that automatically calculates fares based on actual use, CiCoLo will integrate seamlessly into your transportation company.
Similarly, CiCoLo can also be used as a background component in the field of smartphone app-based check-in / check-out systems.
Operating fully automatically, CiCoLo reads the VDV-KA control transactions (so-called TXEBER data records) of electronic tickets at reading terminals in vehicles or at stops, as well as entry/exit transactions from the app backend of a CiBo system. It then determines check-in and check-out actions on the basis of this data.
Based on configurable criteria, journeys or entire chains of journeys are determined from the actions, which lead to a priced sales data record in connection with the selected tariff. All actions can be monitored via graphical user interfaces and, in exceptional cases, manually edited.
To ensure customer-friendly handling of misuse events that are often unavoidable during the check-in / check-out procedure, such as forgetting to complete the check-out action, CiCoLo features automatic journey completion. This tool uses a memory function in conjunction with configurable criteria to control escalation levels – an intelligent, self-learning solution that will appeal to your passengers.
To transfer the sales data records to a background system for further processing, CiCoLo supports the vendor-independent HUSST standard interface. The tariff stored in CiCoLo can also be imported in full or as a differentiated delivery via the vendor-independent HUSST standard interface.
Thanks to the analogous processes, CiCoLo can also be used for sales systems with check-in / check-out or Be-in / Be-out procedures. CiCoLo was developed in cooperation with Kreisverkehr Schwäbisch Hall, which operates the first check-in / check-out sales system in accordance with VDV-KA standards.
Do you have questions about fare.logiQ? Kai Horn and his team will be happy to answer your questions.