Route GSA tickets

Route GSA tickets
The main components of the system are:
- Mobile document generation system
- Billing system
- Data storage system (Google Docs, DropBox, Alfresco)
The architecture of the IS looks as follows:

Description of the tools used:
Repository:
- Alfresco – An ECM system capable of version control and copy tracking. It doesn’t allow collaborative work on a document but supports creating multiple document versions for subsequent creation of a final version. Alfresco can also be used as a knowledge accumulation system (similar to Wiki systems).
- Google Docs/Google Drive – Lacks version control but supports collaborative work on documents and the ability to add comments to specific parts of the text.
- Dropbox – Document exchange without the option for leaving comments or establishing connections between users within the system.
Mobile document generation environment:
- Mobile application – Combines functions of a wiki, web interface, Rizzoma’s functionality, and serves to store tickets, mobile receipts, and mobile documents, allowing their offline viewing.
- Web interface – A web service used for document creation and coordination among participants, enabling the viewing of statuses of existing documents, adding personal notes to documents, etc. For instance, it could involve contract signing where the main document reflects its status (approved, not approved, signed, under review, in revision, etc.). Alternatively, it could involve a previously ordered ticket with its respective status.
- Wiki system (Xwiki, etc.) – Intended for preparing, storing, and organizing documents.
- Collaborative document work systems (Rizzoma) – Using this system allows for collaborative document preparation. Later, it’s possible to import into a document storage system or a wiki system. Description of the existing “RUTA” information system.
This document presents the overall task statement for the comprehensive information task of automating all processes related to the centralized ticket sales system for all directions.
The concept of the “RUTA” information system is based on the comprehensive integration of solutions for the following typical tasks:
- Real-time sales and refunds with authenticity control;
- Financial control;
- Accounting;
- Contract and related document management;
- Distributed databases;
- Information security system and access control;
- Economic and financial analysis and forecasting;
- Specialized informational subtasks;
The system management principles are based on establishing transparent and efficient automated accounting, encompassing the accounting of all types of operational activities. This minimizes operational costs, simplifies financial control, and eliminates losses in the analytical component of information flows.
The software package includes the input, storage, and maintenance system for the following information:
- Route information with route identification capabilities;
- Schedules with the number of intermediate stops identifiable by departure time or distance;
- Passenger and luggage tariffs, discounts, their application based on season, days of the week, and different rates on various routes;
- Various types of fees and discounts, rules of application;
- Bus types, loading norms, including the sale of “standing places”;
- Norms for selling seats from departure stations and intermediate stations for different trips, considering seat reservations for “current” sales;
- Information about cashiers, dispatchers, etc., working with the system and their functional rights;
- Information about transport companies, buses, and drivers.
The system performs:
- Opening routes for current and advance ticket sales for a specified period; sales status control;
- Seat sales and ticket printing with reservations accounting for future cancellations and no-shows;
- Additional ticket sales before bus departure;
- Generating and printing accompanying documentation for the route (passenger and luggage manifest) printed just before bus departure and handed to drivers; managing sales in case of route cancellations, schedule changes, bus type alterations, or changes in the number of seats on the bus.
- Recording the history of all operations performed by system operators;
- Generating statistical summary reports for sales analysis, route occupancy, etc.;
- Generating a summary of revenue distribution among transport companies;
- Analysis of station activities.
The system provides the following advantages:
- Direct and advance ticket sales for all routes at any station’s ticket counter;
- Dispatch support throughout the entire transportation sales cycle, from opening routes for sales to handing over seating manifests to drivers;
- Online availability of data for accounting on cash transactions and calculations with transport companies servicing passenger transportation from bus stations.
- A history of all operations in the system, specifying the date, time, and operator performing the operation.
- Access to all necessary information about current activities at any time, enabling effective and timely decision-making at all stages of operation.
- Ticket sales data can be stored on primary and backup servers, with no need for staff intervention to switch to the backup server.
The “RUTA” system is implemented as a hardware and software complex using modern software and technical solutions. The system involves integrating all hardware components—server equipment, workstations, automated cashier workstations with fiscal registration equipment—into a unified local computing network.
In the practical implementation of the project, a scenario for the globalization of the information system was developed for the future:
- Comprehensive automation of the Central Bus Station in Chișinău (accounting and sales system)
- Gradual automation of all bus stations in the Republic of Moldova (accounting and sales system)
- Automation of the Ministry (aggregate analytical information on sales, routes, etc.)
- Integration of bus stations (including sales for any direction from any departure and transit points)
- Integration of the “RUTA” system with all interested organizations—transport companies, travel agencies.
- Alignment of the IS (Information System) in accordance with security standards.
Functionally, the system belongs to the class of tasks of distributed databases. The most efficient solution for such tasks, practically implemented at the moment, is the SQL variant of the client-server technology. Within this technology framework, the system is divided into two major components: the server-side and the client-side.
The server-side represents nothing but a central data repository serviced by specialized software—a server.
To ensure guaranteed efficiency in implementing the central data repository, the most widely used system for managing large distributed databases—Oracle Database Management System (ORACLE DBMS)—was chosen.
The client-side comprises a set of functionally diverse and domain-specific applications. Although the functionality of each individual application must fully reflect the specifics of its tasks, the practical implementation of all client applications must be done in a unified technological style. This is necessary to reduce development and testing costs, as well as to standardize the implementation and support process. Considering these aspects, the software implementation of the client parts selected a professional application development visual system, Builder C++. This integrated environment is based on the globally recognized high-level programming language for professional application development, C++.
Most accurately, the overall structure of the information system can be represented as a hierarchical structure.
Level A. Upper level. Generalizes the entire system
- A.S Central Server.
- A.S.1 Central Database.
- A.S.1.1 Ticket Sales Database
- A.S.1.2 Vehicle Fleet and Issued License Database
- A.S.2 Transaction Support for Remote Clients.
- A.S.3 Subject and Technical Support Module for Distributed Data Systems
- A.S.4 Universal Core for Storing Accounting Data for all system subjects
- A.K Upper-level Direct Client Applications
- A.K.1 High-Level Data Summarization Reporting
- A.K.2 Data Monitoring, Audit, and System Parameterization
- A.K.3 Analysis and Forecasting Module
Level B. Lower level. Generalizes the information system
- B.S Bus Station Server
- B.S.1 Sales Subsystem Database.
- B.S.2 Accounting Database.
- B.S.3 Synchronizer of distributed data with level A.
- B.S.4 Synchronizer of distributed data with level B – other Bus Stations.
- B.K Bus Station Client Application Level
- B.K.1 Administrator Workstation
- B.K.2 Dispatcher Workstation
- B.K.3 Universal Cashier Workstation (ticket sales for any routes and destinations, reservation, booking, refunds, sales for other bus station routes, integration with cash registers with fiscal memory)
- B.K.5 Information Service Workstation (autonomous functioning possible, support for an Internet website)
- B.K.6 Senior Cashier Workstation
- B.K.7 Platform Controller Workstation
- B.K.8 Remote Sales Cashier Workstation (via modem, Internet)
- B.K.9 Accountant Workstation
- B.K.10 Production Manager Workstation (control and analysis of sales, routes, contracts, vehicle fleets, etc.)
- B.K.11 Director’s Workstation
The functioning of the system is considered from the lower level. Sales registers, dispatchers perform operational activities in real time, populating the database with atomic primary documents. Simultaneously, the accounting database is formed. If necessary, the data synchronization module is activated, allowing operations on remote databases of other bus stations. Technically, this is expressed in establishing modem connections over a regular telephone line. At the end of the operational day, the data synchronization module with Level A is activated. This leads to updating data in the central database. At any time, all types of reports can be obtained without limitations on the period.
Data protection and access control are carried out using ORACLE tools at all levels and on each workstation. For remote clients, access control is also additionally implemented at the operating system level.
All client applications operate under OS Windows 95, 98, NT4, 2000, XP, 2003.
A user manual is provided for each workstation. For administrators, a technical description of the system and database structure is additionally provided.
Capabilities of the main workstations.
Sales Register for Current and Advance Sales and Refunds
- Current ticket sales
- Advance ticket sales
- Obtaining information about route stops and ticket prices
- Refund initiated by the passenger
- Refund due to the bus station’s fault
- Acceptance/return of funds from other cashiers and collectors
- Summary report on sold and returned tickets
- Report on sold discounted tickets
- Report on returned tickets
Dispatcher
- Current operational activities:
- Arrival
- Departure
- Delay
- Additional actions:
- Extra trip
- Delays at stops
- Extended information about routes, buses, courses
- Reports:
- Daily Report
- Boarding List
- Sales Situation
- Commitments and Delays
- Operator’s Actions Record
- Enterprise Situation
- Wages of cashiers, operators, controllers, and dispatchers
- IT Delays Record
Administrator
- Schedule
- Users
- Privileges
- Cash Registers
- Currency Exchange Rates
- Ticket Tariffs
- Directories (Fleet, Analytics,…)
- Reports
- Tariff-related (points and routes)
- Sales Status
- Cashier Reports
Senior Cashier
- Processing Statements
- Cash Statement Accounting
- Cash Register Operations Tracking
- Additional Cash Operations
- Reports
Chief Accountant
- Accounting Document Register
- Balance Sheet
- Analytical Accounting by Sections
- Turnover Statements for Accounts: 516, 591, 241, 228
- Additional Cash Operations
Information Service
- Schedule Information
- Sales Status Information
All workstations provide FULL SUPPORT for operation ONLY via KEYBOARD and ENSURE 100% DATA INTEGRITY and PRESERVE the PREVIOUS OPERATION (OR ANY COMPLETED TRANSACTION) IN CASE OF ANY CLIENT-SIDE FAILURES
List of Processes

Processes related to ticket sales:
- Schedule
- Ticket reservation
- List of available tickets and their prices and other attributes
- Reservation
- Receipt of an invoice for payment or other guarantees for the reservation
- Confirmation of guaranteed reservation based on payment or freezing of funds or based on a digital signature Mobile-ID
- MobileID document signing process
- Reservation confirmation
- Selection of payment scheme and request for an invoice
- Generating a payment order
- Receiving confirmation or rejection of the payment order execution
- Ticket generation, sending via email, and printing
- Presentation of payment and reservation confirmation in the booking system to obtain the ticket
- Providing the ticket upon boarding
- Inclusion of the ticket in the boarding list
- Cancellation of the reservation