Context
This subproject belonged to an annual information systems portfolio. It was a third-phase upgrade of an existing tourism operations and ticketing platform. The goal was not to launch a standalone website, but to improve an established business platform with years of operational data and user habits.
The scope combined software and on-site equipment. On the software side, it included service-quality evaluation, mobile operations management, and dispatch-ticketing platform upgrades. On the equipment side, it included self-service ticket pickup, information query displays, ticket printing, high-availability support, and network security maintenance. The management task was to make online transactions, on-site service, mobile operations, and back-office management work as one chain.
Key Challenges
The first challenge was upgrading an old platform without breaking established operations. The existing platform carried historical data, user habits, and business rules. New functions had to improve the experience while preserving process continuity.
The second challenge was synchronized software and hardware delivery. Ticketing and operations software alone would not create value if on-site query, pickup, and printing devices were unstable. Conversely, qualified equipment would not matter if the back-office workflow did not close.
The third challenge was multi-end consistency. Management users needed dispatch, ticketing, statistics, and maintenance functions. On-site users needed pickup, query, and printing. Mobile users needed operational handling and feedback. Public users needed transaction and service access. Data and status had to remain consistent across those ends.
The fourth challenge was future expansion. The upgrade introduced mobile development, improved business-side experiences, and reserved interfaces for later development. Management therefore had to consider interface stability, data structure, permissions, and device integration beyond the immediate release.
Management Approach
Breaking Delivery into Business Chains
I managed the project through four chains: service feedback, mobile operations, dispatch-ticketing, and on-site devices. Each chain was checked by data flow, status synchronization, user operation, and back-office traceability rather than by module completion alone.
Including Device Integration in Platform Acceptance
Self-service pickup, query displays, and printing devices were not treated as separate delivery items. Equipment arrival, power-on testing, installation, process linkage, and data consistency were managed as part of the platform acceptance evidence.
Using Layered Testing to Control Quality
Testing moved through unit, integration, and system levels. It covered user interface, performance, stress, capacity, fault tolerance, security, configuration, and installation. The three core capabilities, service evaluation, mobile management, and dispatch-ticketing upgrade, had to pass testing before moving to the next stage.
Using Trial Operation and Training to Verify Usability
For an upgraded operations platform, real risks often surface after users begin using the system. Trial operation, training, on-site guidance, and feedback records were treated as part of delivery. Training was used not only to teach functions, but also to validate process flow, data accuracy, and equipment maintainability.
Reserving Expansion Conditions
The upgrade was not the final form of the platform. Future mobile, transaction, evaluation, and on-site service features would continue to evolve. Interface, permission, data, and device-access assumptions were therefore kept extensible to reduce later rework.
Outcome
The project completed the third-phase upgrade of the business and online ticketing platform. It delivered a connected set of capabilities: service evaluation, mobile management, dispatch-ticketing support, on-site query and ticket pickup, and printing output. Software functions, equipment delivery, power-on testing, system testing, trial operation, training, and initial acceptance evidence formed a coherent delivery chain.
From a management perspective, the project placed several software capabilities and multiple on-site device categories into one delivery framework. This reduced the risk of software being available without practical on-site service, or equipment being functional without a closed workflow. Continuous verification through testing, trial operation, and training made the upgrade closer to real operational needs.
Reusable Lessons
A third-phase upgrade should begin with the legacy context. Historical data, user habits, interfaces, and workflow assumptions all shape how new functions can be introduced.
Online ticketing and on-site service projects need software and hardware to be validated as one business chain. Back-office processing, mobile functions, on-site equipment, and user operation must close together.
Testing should cover more than feature presence. Integration, performance, capacity, fault tolerance, security, configuration, and installation are where multi-end systems often fail. Training and trial operation are management tools. Realistic business simulation can expose workflow, device, interface, and data issues early enough to correct them before acceptance.