JPA - specific feedback of faults -

Discussion in 'Army Pay, Claims & JPA' started by MikeJenvey, Oct 12, 2007.

Welcome to the Army Rumour Service, ARRSE

The UK's largest and busiest UNofficial military website.

The heart of the site is the forum area, including:

  1. Thought that this might be of interest here - a cut & paste from a thread I have just started on PPRuNe.

    Rather than hijack any other JPA thread, this is an attempt to focus on specific JPA/JPAC faults that can be forwarded onto someone who might be able to influence things......

    This began when someone shortlisted JPA for an award - Computing Awards for Excellence 2007 - it's under "Public Sector Project of the Year" Now, whilst the Drugs Squad finds the person concerned, there is a chance to add your feedback either via the comments here (15 pages so far - no complimentary remarks at all) or if you wish, straight to a more direct source.

    The chief reporter from Computing contacted me asking for information; I have her permission to list her contact details:

    Over to you guys!! :wink:
  2. Apart from being a new system, which the army always has difficulty with at first, it is a system that relies heavily on the individual taking responsibility for maintaing his or her own record.

    In the past there were Pay & Docs clerks within a unit who knew the nuances of the soldiers, their jobs and in some cases what allowances they were allowed. Now a days, the Admin Office is 20% or more undermanned because JPA is to be funded on the back of savings, but this is in fact a false economy.

    Soldiers who have a low educational standard or be inexperienced in life skills will find this challenging until they have done things regulalrly. Updating things like Next of Kin or Emergency Contacts is likely to be the main cause for worry. Soldiers have a habit of changing their minds about who they want the MoD to notify because of things like family disputes, falling out with girlfriends/boyfriends etc. There will come a time when Mrs Smith finds out her son was killed in the paper or on the news because Pte Smith's new girlfriend of a week is down as the EC and or NOK.

    I believe that JPA is an attept to push the responsibilty of admin onto the soldier and for the "system" to wash their hands of any administrative difficulties.

    The support for JPA is poor at best, with JPAC failing on a regular basis to contact the soldiers when queries have been raised but still closing the calls none the less. They are Hardly ITIL compliant. The SLA's that have been set up benefit them and not us, with few avenues for complaint or redress that are effective in resolving an issue quickly and expediently.

    Almost everyone who has had to do something on JPA from all 3 services has had something adverse happen, and whilst claims get paid quickly, it is likely to be a system that holds back servicemen from a service they have always enjoyed under the old way with their old pay and admin services.

    JPA is certainly the future, but a retrograde future in my opinion
  3. Brillaint read of the comments, I have added my own, though I think they must have got the message by now :D
  4. Bowmore_Assassin

    Bowmore_Assassin LE Moderator Book Reviewer

    Claims paid more quickly - all good and that is about all that is good. You cannot replace a decent military clerk with a software programme.
    Bad - OJARs on JPA - all bad, takes 3 times longer to write one as opposed to the 'old' OJAR system. Also, JPA is not up to date in terms of organisational nomenclature and you cannot put your posting preferences on it, even though you are supposed to. I could go on but suffice it to say overall it is a time consuming pain in the arrse and not user-friendly.
  5. I find it strange that when the standards of reading and writing of our recently joined soldiers are falling, we deploy a super HR IT system. If soldiers find it difficult to read and write (or type), then how the hell are they going to ensure that their JPA accounts are accurate?

    As an aside, and as a degree educated bod, I find that JPA's use of a different language to the one that I have used for years, is intensely irritating. But this is progress, right?

  6. At a SPS sminar last weekend lots of points were raised on the nuances and problems with JPA, the party line is "this is what you've got, get used to it and get on with it" - no more money left to add any more changes! Word is some of the bolt ons we currently have may be removed due to the amount of re engineering required before deploying updates and the cost thereof.
  7. No, just shows how incompetent the MOD is at purchasing IT projects. If we have a good project, its down to the contractors honesty and integrity - which does exist
  8. I've been forwarding comments from PM's sent to me via PPRuNe, some of the JPA errors or overall difficulties are amazing. If the system was linked to a civilian organization, the Financial Director (or equivalent) would be reading his P45.

    I hope that lots of you have been emailing the reporter direct!!
  9. msr

    msr LE

    Bearing in mind the recent DIN...

  10. <<<< Bearing in mind the recent DIN... >

    Would that stop wives, partners, significant others, passing on useful information about JPA fiascos, loss of pay, etc, etc....???
  11. Grownup_Rafbrat

    Grownup_Rafbrat LE Book Reviewer Good Egg (charities)

    Sadly the experience of JPA is very common in civvie street as well as in the military and pretty much all public IT now. Successive Governments and trendy business leaders have 'saved money' by 'outsourcing' their IT to the lowest bidder. This means that the low bidder does not need to deliver a working system which meets the needs of its users, only to meet the dates and contractual obligations outlined in the contract. i.e. 'If it meets the contract, it works and we get big bonuses'. Those who draw up the contracts, being novices, don't do it well enough to enforce the development of decent software.

    The way these companies work is to turn the development of IT into a production line, rather like the car industry. Only instead of starting with a design, a chassis and adding bits to it until it looks like a car, they start with a Project Manager, a Requirements Manager, a Contract Manager, a Testing Manager, a Commercials Manager, a Communications Manager, and some other Managers to check that the Project Metrics are correct. Remember, a system is fantastic if the Project Metrics are all green, not if it is fit for purpose!

    The actual work is done by separate teams - one lot will look at the requirements (or fit them to the off-the-shelf package which the company knows because they are 'technology partners' with the supplier), another lot does coding, another lot does testing, another lot designs the security, the networks, etc. They may or may not work in the same country or speak the same language. The chances of any of them understanding the business of the end user, whether it's a soldier, a worker in a Job Centre or a Bank Clerk, are nil. All they know is which 'technology partners' they must use.

    Because the jobs are de-skilled and there's a need to keep costs low, they're all paid rubbish wages, morale is at rock bottom, and that's another reason why a rubbish job is done.

    No individual or person has any responsibility for making sure that the delivered system provides useful functionality. Key checkpoints are missed due to the time constraints imposed by contracts, and at the end it's all thrown live because there's no money left to finish the job.

    When it fails final testing, there's always a bunfight where all the suppliers blame one another and fix the problem onto network/coders/late requirements/reluctance to change, etc.

    No-one takes into account the time spent by end users or helpful people doing the job which the system doesn't do, as the 'savings' have to be clawed back quickly to demonstrate success and get the massive bonuses for the Client-Facing Directors of the Company.

    Post live enhancements then take years and years because there's no money left. And what budget there is has to be used first to change key operational components when their supplier is taken over by the competition.

    And of course, the High-ups in the Bank/MOD/DWP/Client end up with jobs or directorships in Accenture, EDS, IBM, CSC, BT ad nauseam.

    After nearly 30 years in the IT Industry, I'm totally disillusioned by this mess, and frankly shocked that any IT works at all. Ever.

    Rant over. Better go and lie down now.
  12. However, if my facts are correct, JPA was a military version of a civilian application (can't remember the name). However, the complexity of the huge number of military differences (trades, qualifications, units, dozens more!) has dragged JPA into a never-ending stream of "bolt-on" fixes. Likewise, the huge number of military personnel needing to access JPA clearly wasn't trialled adequately. Many civilian companies use a personnel system that can be accessed (securely) via a PC/laptop. At one unit in the Middle East, there are over 400 "permanent" personnel + dozens of transit/short stay personnel. One JPA terminal...... useless.
  13. Its Civvy Name is Oracle i believe, the name has been left there so that we feel we're getting the same.

    I told my wife that JPA was based on Orace and she laughed, her company (a large multinational) stopped using it because it couldn't keep up with people moving around on business.......lucky we don't get involved in moving around then isn't it?!!!!!
  14. Most of the big banks use Oracle......Its a VERY powerful piece of software, its just a pity that the forces have bastardised it as usual.....
  15. We bought a COTS version of Oracle and rather than bastardising it to suit our purposes, we changed our practices to meet the needs of the system.

    Is anyone else having problems accessing