Project Description

Wimbledon Ticketing System
sub heading

THE BRIEF

The Client required a system to produce 250,000 tickets for the Wimbledon Tennis Finals in 25 different formats. Each ticket would be printed with individual data specifying the court, row, seat and the day of which the play was to take place. Each ticket would then be allocated a unique barcode. The tickets would need to be produced in batches and to the highest print specifications. Once printed each ticket would require scanning for quality purposes and complied into books. These books must then be accounted for, packed for despatch with the relevant tracking information and sent to the client. A reprint facility would also be required for any misprints.  

STAGE 1 – CONSULTANCY

Our first step was to understand exactly the customers requirements. The specification was very complex and the number of variables made the consultancy stage even more important. We performed detailed analysis and returned our understanding of the project in writing to ensure all the aspects of the project had been understood.

STAGE 1 – CONSULTANCY

Once we had agreed the specification and the client was happy we had a detailed knowledge of their requirements, we began the system design stage this consisted of both database an GUI (user interface). We needed to get a large volume of data in a raw format supplied by the client in a format which we could manipulate and produce the final ticket. A Microsoft SQL database engine was commissioned especially for the project, and we got to work writing the algorithms to transform the data. The algorithms we produced imported the data and transformed it all in one pass to reduce the risk of data pollution. Once the data was in our databases we produced a hard copy of the data in a formatted report, this fondly became known as the Wimbledon bible as it contained the world according to Wimbledon.

STAGE 3 – VARIABLE DATA

Next came the development of the variable data printing process, we developed a system which would allow a printer to select the the tickets required and send them straight to a digital press without any human intervention. This would take data from the database and merge it with a template with inbuilt logic to produce the correct ticket format, this also included facility for book printing and auto imposition.

STAGE 4 – VERIFICATION

Once production of a ticket type was complete the tickets where verified against the database to ensure all the ticket data was correct and the generated barcode would read. For this purpose we developed a Windows system which displayed an image of the ticket on screen for the user to verify, the corresponding record in the database was then updated with the users credentials, dates and times etc. for reporting and audit purposes. If for any reason the verification process failed an automatic reprint job would be initiated and the whole print and verification process would start again.

From what I must say was a very basic specification, the guys at Axisware took our ideas and turned them into reality. They also had many ideas of their own which where adopted as part of the application. From start to finish the professional and personable approach of the guys helped us develop a system which is still in operation now 7 years later.

 

Dorn Pryce, Wimbledon

Capability
beyond Expectation.

We strive to make your application as user friendly and as visually rich as possible. Simple software increases user buy in and therefore give better ROI

Discover More

More Projects

Offshore Personnel and Vessel Certificate Management2019-07-25T11:36:50+01:00
Syndicated Loan Management System2019-04-30T13:31:47+01:00
Health and Safety Risk Assessment & Method Statement Application and Portal2019-04-24T11:42:07+01:00
CDM 2015 Web Application and Portal2019-04-25T10:14:14+01:00
Financial Product Management Solution2019-04-30T09:43:46+01:00
Distribution and Validation Solution2019-03-19T11:58:03+00:00