This week, Irish Rail launched the Online Payments facility for Fixed Payment Notices (which are penalties for fare evasion and other infringements).
The Dovetail-developed system allows passengers to pay a Fixed Payment Notice online. It is mobile-friendly and allows customers to pay a Fixed Payment Notice on their mobile, tablet, laptop or desktop computer.
The system is built using ASP.Net, C#, CSS and HTML5 and it is integrated with the Irish Rail Fixed Payment Notice Management system (a version of the Standard Fare Backoffice Management System which Dovetail previously developed for Dublin Bus).
Our work with Irish Rail, LUAS and Dublin Bus is all part of Dovetail's continued involvement with the transport sector.
The following article appeared in the February 2016 edition of Rail Brief, the Irish Rail staff magazine. You can view the PDF here.
John and Martin with the Irish Rail Team in Connolly Station.
A FINE NEW SYSTEM
In 2015 there were 9,606 Fixed Payment Notices issued. There was a 22% increase in the number of Fixed Payment Notices issued in 2014 compared with 2013 and this trend remains in an upward direction putting more pressure on the system in use. As a source of revenue for us, it is critical that there is an intelligent information system to ensure detailed reporting and timely payment of fines.
Main Triggers for the New System
1. Two separate systems existed, one for DART and one for Innercity
The back office was using two disparate systems; Access and Infopath as both the Intercity & Commuter (ICCN) and DART had individual systems. This meant inputters were moving between systems with differing designs. These disparate systems continued when the RPU was centralised, meaning that the Head of Revenue Protection and the Revenue Protection & Prosecutions Manager had to interrogate each system separately and add the results together. Often they had to physically count original fines for statistics purpose as the original system didn’t allow for any meaningful interrogation. Another issue with the existing system was there was no single view across one person. A person could have a fine on the DART database but the ICCN database had no visibility of it.
2. Everything was manually typed
Prior to the new system, everything was manually typed, for example, there were no drop down boxes with list of stations, Revenue Protection officers’ names, train times or routes. This
lead to the likelihood of poor quality data as typing errors/spelling errors could occur due to the high volumes to be input.
3. Inconsistent design between forms and databases
The fields on the screen and the form didn’t match. As a result, it slowed down the speed of inputting as everything on the screen had to be matched to the form field for input. This contributed to a growing backlog and as a consequence, reminder notices, at times, were late going out to customers. This type of backlog can be very demotivating for an employee – no matter how hard the team worked, there seemed no end to it!
4. Databases were not built for high volume
There were over 38,000 records on the databases which were not built for high volume and as a result crashes often happened. Up to eight people could have been inputting at any one time
and the input may not have updated correctly. The resulting consequence was that a letter could go out to someone who has already paid a fine.
Leading the Change
Roger Tobin, Head of Revenue Protection, has been leading the change project with support from Dave Cannon Manager Revenue and Prosecutions and Shauna Fitzsimmons on the systems side. The back office team have also supported the change process. The team worked with David Bettles Information Systems, Keith Faherty Online Manager, Group IT and Customer First in specifying and clarifying what the system requirements were before Dovetail could commence their work.
Communications and Training
The team had been briefed on the full extent of the system change. These briefings were supported by the Customer First, People and Communications Lead, Linda Allen and were made
by Dave Cannon and Shauna Fitzsimmons. A training test system was set up by Dovetail to ensure all the team were comfortable with the system before it launched. They all found the system to be very straightforward and could really appreciate its benefits. The Dovetail systems supplier facilitated the training for all involved. They also provided systems support for the team to ensure the team were fully supported in the ‘go live’ and beyond. Brian Quinn, Business Process Lead, documented the new processes arising from the implementation of the new system. This was to ensure there was no ambiguity in the implementation and ensured the process in place was the optimal one.
Phase 2 Online Payment Facility
Work is currently ongoing in setting up an online payment facility with a Go Live expected in February 2016. Currently there are limitations on payment options as a customer can only pay
during office hours, Monday to Friday 9am to 5pm. There will be huge benefits to the customer to pay online anytime as the back office team had received complaints from people who wanted to pay but couldn’t get through. This will also mean a reduction of phone calls to the office to allow the employees allocate their time on the key tasks of managing repeat offenders, analysing areas to target and managing files for maximum court prosecutions.
Phase 3 Customer First
Customer First is currently looking at electronic solutions to make the RPU more efficient. Currently Revenue Protection Officers write out Fixed Payment Notices (FPN’s) which would mean real time inputting. There will be real benefits in the adoption of these portable devices.
Benefits of the New Dovetail System
One of the biggest benefits for the team is the removal of the backlog. All their hard work has significantly contributed to this. Other benefits include:
1. One single view of a ‘customer’
The new system can highlight fraudulent persons or highlight repeat offenders. It is able to supply fraud lists or repeat offenders across both systems.This allows for a more intelligent type of reporting and more successful prosecutions.
2. Better targeting of fare evasion
It allows the RPU team to more intelligently target times and services where there are fare evasions above average. The system allows them to interrogate information by multiple fields
e.g. by station, by time, by ticket types, by day of the week and by any other fields stored. The new system has all the information in the one place, it reduces the dependence on physical files.
3. One single system in place and customisation of screens
There is now one single system in place for all the back office team capturing all Railway Undertaking fine data. Customisation took place for ease of use for the inputter on all screens. The new screens mirror the FPN form and will follow the fields of the form as it appears on the page.
4. Template letters created for all scenarios
Template files for all types of letter have been supplied to the new system and can be generated automatically.
5. Preloaded lists and drop down boxes
The new system will have these all lists preloaded along with the actual timetable. It will also have an address link with google maps eliminating the need for freeform typing.
6. Appeals process standardised
The time spend on appeals has reduced as the appeals process has been standardised and the appeal is done via email with the addition of the attachment on the system.
7. Flexible to change
The new system is more flexible to change. The systems allows the addition of new routes, times, officers and can allow the addition or amendment of any fields.
Sorry for the click bait title - I just wanted to share this interesting screenshot.
Below is a screen shot overview of a Dovetail tender document. I was interested to see how many images we use: 70 in this case. This is pretty typical of a Dovetail proposal. The pictures include such things as examples of previous work, suggested approaches for the project under discussion, UML diagrams and some of our corporate bonafides.
The images aid clear communication (one of our corporate values) and they also break the text up to make the document more approachable. And the proof is in the pudding - we won this particular tender :)
So if a picture really is worth a thousand words then this tender document contains 70,000 due to the images alone, and 17,523 that we wrote, giving a whopping total of 87,523!
Here at Dovetail we love Team City and Visual Studio.
We recently updated our Team City configuration to allow projects to be built using Visual Studio 2015, C# 6, and to use the latest Nuget package manager.
In doing so, we discovered a very peculiar setting deep within Team City that caused one of our projects to break on build and break once deployed.
The Build Failures
After updating, we ran our build and the compiler threw an error saying that it could not find a specific version of a Nuget package. For example, our packages.config within Visual Studio specified we use Nuget to install Newtonsoft.Json version 7. However Team City reported that the project needed Newtonsoft.Json version 8.
We made the decision to update all affected nuget packages to the latest versions, pushed our project and Team City built it successfully.
The Deploy Failure
Looking back at our Octopus Deploy package we found that the JQuery file we were referencing and pushing to our repository was not there any more. However, we did see the latest version of the JQuery min file. Our file was being removed and replaced with the latest JQuery min version.
The Update Package Setting
We soon found the setting buried deep inside the Team City "build steps" screens:
Within the NuGet Installer build step is a setting which, when turned on, updates all your packages. This sounds great in theory but when you run into build and deploy issues this will cause headaches.
The text underneath states "Uses the NuGet update command to update all packages under solution. Package versions and constraints are taken from packages.config files". Whether this is a bug in Team City or not, this text seems very vague for an "Update Packages" function.
Be careful, because when checking this check-box, Team City will not read the packages.config version numbers and instead it will download the latest version of every package.
Update: Team City have been back to us and they're going to update the explanatory text on this checkbox to make it more clear.
I've only just learned that one can order Barry's Tea directly online!!
Not the most important blog post ever, but I'm so pleased that I wanted to share it!
In one of the applications we're working on we recently had to make a move from InfluxDb v0.8.7 to v0.9.6. Because the official migration paths didn't work for us (DB upgrades would either lose data or not finish at all) we had to develop a small c#/.net app that would reliably execute the migration for us.
We successfully migrated around 4GB of data with it and are quite happy with how it went. It did take quite a bit of time but all the data is safe and usable.
The app also lets you specify backfills (rollups) to be created once all the base data is migrated.
Today we're open-sourcing this migration tool in hope it might help someone else make the move as well. :)
This week CIS Ireland launched CIS Free, a new facility allows you to view up to five projects a week every week for as long as you like.
It is perfect for business start-ups and small businesses to get an overview of construction project leads.
Tomás, Mossy, Fabrizio and Martin have been working on the feature and you can check it out here.
The new year is about to begin and it is time to sum up all the fantastic achievements we have made this year!
Have a look at our latest newsletter below, to see how many great things have happened in 2015.
The Dovetail team wishes you a wonderful Christmas and a Happy New Year!
||Dovetail’s relationship with IKEA has expanded beyond the UK and Ireland - we are delighted to announce we will be working with IKEA Denmark too, rolling out a touchscreen kiosk solution for the IKEA FAMILY customer loyalty programme.
|With the passing of the Regulation of Lobbying Act 2015, Ireland is on the road to building a more transparent society. Dovetail was proud to design and develop Ireland’s Lobbying Register, available at www.lobbying.ie.
||The much-hyped Internet of Things gathered pace in 2015. According to PwC “the promise of the IoT is already being realized and its grand vision is just around the corner”. Dovetail is delivering this promise to our clients using cutting edge technologies including Microsoft Azure IoT Hub, InfluxData and Amazon AWS IoT. Expect to hear more of IoT in 2016.
|After organising such a spectacular World Cup you might expect World Rugby to take a well-earned break. In fact they just kicked off a custom development project to smooth their dealings with their various partners. Dovetail is delighted to be working with this world class team!
||Ireland is leading the way in providing calorie and allergen information on menus. Dovetail developed the MenuCal system for the Food Safety Authority last year to help restaurateurs correctly label their dishes. It’s proven so successful that this year the system was adopted by the Food Standards Agency in Northern Ireland.
|This year we saw a surge in demand for Cloud-based solutions. Clients are keen to move existing functions and new developments to the cloud to take advantage of lower costs and increased reliability. As a Microsoft Certified Partner and Reseller we’ve done our bit to help Microsoft’s share price surge an amazing 35% in three months!
||It’s an exciting time to be in technology in Ireland. This year, two Dovetail clients were very successfully sold to large American organisations. These deals illustrate the strength and quality of the tech sector in Ireland.
Congratulations to Colm in Realex Payments and Robin in Acquirer Systems!
Thank you for your support in 2015. We wish you a very happy Christmas and a prosperous 2016!
We've been using the InfluxDb time-series database for almost a year now on one of our projects and it works pretty nicely even though it still didn't hit the v1.0 mark.
We started our InfluxDb journey with v0.8.7 and thus far even though we wanted to, there wasn't an easy way to migrate to v0.9.x. We however came to a point where we needed to upgrade in order to implement new features required by the project.
The first step to take was to see if there are any .Net libraries that supported InfluxDb v0.9 and the one we've been using from start seemed to be the best one. The problem was it wasn't updated for quite a while and it didn't support the latest InfluxDb versions.
So, I decided to fork it, refactor it and make it work with the latest InfluxDb. The code can be found on GitHub, it's under MIT licence and there is also a NuGet package on nuget.org. The integration tests are all working again and the docs have been updated. Rejoice!
In the future, my plan for the library is to support the rest of the TICK stack layers as well as their API's get more stable.
We're also planning on open-sourcing the migration tool that we developed and used to migrate the data from v0.8 to v0.9 in hope it might help someone else as well. :)
Dublin Bus this week launched the Online Payments facility for Standard Fares.
The Dovetail-developed system allows passengers to pay a Standard Fare online. It is mobile-friendly and allows customers to pay a Standard Fare on their mobile, tablet, laptop or desktop computer.
The system is built using C#, CSS and HTML5 and it is integrated with the Standard Fare Backoffice Management System which Dovetail previously developed for Dublin Bus and which is used by three large Irish Transport Operators: LUAS (Dublin Light Rail), Irish Rail and Dublin Bus.
Our work with Dublin Bus, LUAS and Irish Rail is all part of Dovetail's continued involvement with the transport sector.
Recently we've had a bit of a crisis situation when one of our Azure VM's decided to lose a bunch of data. Fortunately backup jobs were set up through Azure's Recovery Services and I've already used that a few times to restore or make copies of various VM's without any problems. A few clicks and you're ready to go. This was supposed to be an easy 20 minute task but this time was different.
For whatever reason instead of getting a restored VM, I started getting the following restore job fail message:
Restore failed with an internal error.
Please retry the operation in a few minutes. If the problem persists, contact Microsoft Support.
Not very descriptive, and not really helpful. :/
The data transfer part of the job would succeed each time, but the "Create the Restored VM" kept on failing. I tried using different restore points from a day, week, or even a month back, but it made no difference. It all came to a point where we had to submit a ticket to Microsoft to resolve this issue.
The two possible solutions that were presented to us were:
- either restore the VM under a new Azure Cloud Service - this worked fine, but wasn't really what we wanted to do (you don't really want to pile up additional Cloud Services just to do a simple restore, it makes no sense and leaves a messy infrastructure behind)
- restore the VM through Azure Powershell - this was a bit trickier, but it worked great in the end
So after a bit of research I realized that the Azure Web Portal doesn't actually use the exact same back-end infrastructure as Powershell which is a bit weird and should probably be emphasized a bit more throughout Azure documentation.
Microsoft support told us to follow this documentation page to restore the VM using powershell, but the tutorial wasn't without its kinks either.
Perhaps this got resolved by now but for the whole thing to work, I first needed Azure Powershell v1. That ended up being a bit of a pain because it required the regular Powershell v3 where Windows 8.1 comes with Powershell v4 and the downgrade was another mission impossible... In the end I somehow managed to resolve this issue by installing the latest Azure Powershell using Microsoft Web Platform Installer. That gave me the much needed Azure tooling for Powershell. Yay!
Now to code - these few Powershell commands will extract the VHD from the backup:
> Select-AzureRmSubscription -SubscriptionName YourSubscription
> $backupvault = Get-AzureRmBackupVault -Name "YourBackupVault"
> $backupitem = Get-AzureRMBackupContainer -Vault $backupvault -Type AzureVM -name "YourVmName" | Get-AzureRMBackupItem
> $rp = Get-AzureRMBackupRecoveryPoint -Item $backupitem
# change the $rp number to select the recovery point you want here
> $restorejob = Restore-AzureRMBackupItem -StorageAccountName "yourStorageAccountName" -RecoveryPoint $rp
> $restorejob = Get-AzureRMBackupJob -Job $restorejob
> $details = Get-AzureRMBackupJobDetails -Job $restorejob
From here I finished the process using the Azure Portal as the rest of the process / powershell commands from the documentation seemed to be out of date and didn't work.
To complete the process, you should go to the Azure Portal, to VM section, and then select the "Disks" tab. From there you'll be able to create an unprovisioned disk which you will then use to create a new VM from. Afterwards click the + icon in the bottom left corner, and choose "create a VM - from gallery", you will see an option to use your newly created disk. Finish the setup and you're good to go. :)
Hope this helps you if you find yourself in a similar situation. Cheers!