And here's the latest from AMP:
1. You will be aware that the launch of JPA has not gone smoothly and that system performance/access is very limited. My purpose in writing is to explain the latest position and detail the actions that are being taken to deliver a working system.
2. A number of issues will have been apparent to, and largely contained by, your Admin staff over the last 4 weeks. The System’s performance deteriorated significantly immediately prior to the Easter weekend. Since then, AFPAA, EDS and Oracle staff have been working hard to diagnose and resolve the problem. However, whilst memory and software patches have been applied, the root cause of the problem has yet to be identified.
3. This issue has had a knock-on effect to the JPAC Enquiry Centre (EC). The JPAC EC relies on JPA to provide its Customer Relations Management system. At times when the system has been particularly slow, the EC has been deluged with calls. They too have been locked out of the JPA system in a similar fashion to other users. A system notice board has now been added prior to the JPA logon screen to apprise users of current performance.
4. I realise that the system performance and accessibility aspect of JPA is unacceptable and I have made this point to DCDS(Pers), who owns AFPAA. Moreover, I recognise the impact that this has on specialist staff who rely upon the system, as well as self-service users. Therefore, I have implemented a contingency plan, the full details of which will be sent out this afternoon. In short, system use will be phased to allow professional access (eg PMA & unit HR specialists) for the period 0700-1200hrs and self-service user access 1200-1700hrs. System maintenance, payroll and other core functions will take place outside of these times. I must stress that this is a short-term arrangement for business continuity purposes. It will remain under constant review and be lifted at the earliest opportunity.
Well, what can you expect when EDS is involved??
