JPA and DII

#1
Middle part of last year, the area I work in, the word was that JPA roll out for Army was heavily dependant on DII implementation, and that the DII implementation was well behind, and Apr 07 was looking unlikely. However over recent montsh all talk of DII has gone away, asking questions about it gets blank looks. This has given rise to the latest conspiracy theory that JPA is pulling out as many stops as possible and keeps saying "Yes April rollout is OK" when in reallity the Project leaders are praying that DII will not be on time, so that they can say "Well JPA was ready, its not our fault!". I only have one example that might back this up, in that a friedn of mine is just undergoing is JPA training, but has no equipment at his unit and has not been told when it will be installed.

So my basic question is how may units are there out there that DO NOT have any JPA equipment yet (and don't know when they will?)

One frightening thing that I have heard is that DII only has to have 80% coverage to fulfill its contractual obligations and JPA can roll out. So thats a possible 20% of units, bundling there occurennces up and taking them over to the closest unit that does to key everything in.
 
#2
That ties in with all occurrences being action by proxy, by the HR admin staff. Individuals will not be allowed use JPA until Sep/Oct 07. 8O

I have also heard that those units deploying on Ops during Mar/Apr will not be given any JPA logins until their return (which could result in a years wait!). Could these be the units not being supplied with equipment?

As for rollout, if you are in a position to see the Unicom Discrepancies e-mail out this month, you will notice that the amount of unequal data between units and what is actually held on record differ so much that data migration will be a problem.

It has always been stressed that as long as the payroll works, JPA will rollout for alll 3 services regardless.

Who is going to benefit if the Army do not roll out? :?
 
#3
Let us not forget of course that a large part of the business case justification for JPA was "manpower savings" by reduction in Unit HR Admin staff (I am sure we used to call them clerks in my day :D )
 
#5
Yes it was and the Navy have been hit quite hard with reductions. The Army played game but also brought out the reason of undermanning in certain ranks. This meant they could gap posts in units that have never been undermanned before and move personnel to units that were severley undermanned. So, in reality, the amount of manpower savings has been very minimal.

(I am sure we used to call them clerks in my day :D )
and still do, and will always be called clerk, HR Adminstrator is too posh :roll: :lol:
 
#9
wickedwitch said:
Great to hear that pampas is stil going, where can I find a system?? lol
Let me check my ebay auctions see if I have any left
 
#10
IT_GEEK said:
Middle part of last year, the area I work in, the word was that JPA roll out for Army was heavily dependant on DII implementation, and that the DII implementation was well behind, and Apr 07 was looking unlikely. However over recent montsh all talk of DII has gone away, asking questions about it gets blank looks. This has given rise to the latest conspiracy theory that JPA is pulling out as many stops as possible and keeps saying "Yes April rollout is OK" when in reallity the Project leaders are praying that DII will not be on time, so that they can say "Well JPA was ready, its not our fault!". I only have one example that might back this up, in that a friedn of mine is just undergoing is JPA training, but has no equipment at his unit and has not been told when it will be installed.

So my basic question is how may units are there out there that DO NOT have any JPA equipment yet (and don't know when they will?)

One frightening thing that I have heard is that DII only has to have 80% coverage to fulfill its contractual obligations and JPA can roll out. So thats a possible 20% of units, bundling there occurennces up and taking them over to the closest unit that does to key everything in.
I heard that this was a 'Mexican standoff ' from DII point of view they were waiting for JPA to say that they could not migrate the army data therefore giving them an excape clause.
 
#11
at_ease said:
I heard that this was a 'Mexican standoff ' from DII point of view they were waiting for JPA to say that they could not migrate the army data therefore giving them an excape clause.

Oooo intresting, wonder who is going to blink first. Just hope they do it soon lol
 

engr172

Old-Salt
Book Reviewer
#12
Beleive me, DII is the biggets waste of man hours this side of the NHS rollout. The MOD is being screwed right over on this one.........it will not be raedy for at least 6 months, minimum. It is a farce
 

engr172

Old-Salt
Book Reviewer
#13
Must check spelling..........
 
#14
engr172 said:
Beleive me, DII is the biggets waste of man hours this side of the NHS rollout. The MOD is being screwed right over on this one.........it will not be raedy for at least 6 months, minimum. It is a farce
No doubting you but last night we had a presentation and were told that 5th of March was when we were getting it!?
 
#15
engr172 said:
Beleive me, DII is the biggets waste of man hours this side of the NHS rollout. The MOD is being screwed right over on this one.........it will not be raedy for at least 6 months, minimum. It is a farce
Totally agree, but didn't everyone say that about unicom when it came out. Now no-one wants to get rid of it!! 8O
 
#16
I never slagged UNICOM, I was a fan. But UNICOMS failing was in its Functional software for the "Other unit users". It was before its time in that it expected normal Unit users to use it, before IT was so prominant, then its second failing was not moving to Windows soon enough to keep users happy
 
#18
wickedwitch said:
Didn't realise the UNIX server could cope with windows software oops.

Could it ?
Nowdays, probably not a problem. Then, perhaps more so. But there was a more up to date version of Oracle that could have been moved to that enabled use of mouse and point and click, rather than Non IT people having to remember Keyboard shortcuts.

PS. WW check you PM's please :D
 
#19
The term 'work-around' will be appearing thick and fast on this subject. Yet again, regardless of the crying and beating of chests we will be told to just get on with it, regardless if the bloody thing works or not.

We of course will succeed: doing more, with less, for less (should be on MOD headed paper!)

I'm not holding my breath for DII(F), as long as I have a compatible system (RLI) I can operate, and will assist all those who require my help. How many Logons/Passwords can you remember?

The one who blinks first should be the one who gets the billion pound fine.
 
#20
Moosaca said:
The term 'work-around' will be appearing thick and fast on this subject. Yet again, regardless of the crying and beating of chests we will be told to just get on with it, regardless if the bloody thing works or not.

We of course will succeed: doing more, with less, for less (should be on MOD headed paper!)

I'm not holding my breath for DII(F), as long as I have a compatible system (RLI) I can operate, and will assist all those who require my help. How many Logons/Passwords can you remember?

The one who blinks first should be the one who gets the billion pound fine.
Having worked on both systems and PAMPAS, the problem of work arounds should be slightly different in JPA. The trouble with UNICOM was that it was sponsored by the 'G', 'Q' and 'A' areas and depending who allocated their budget was a major factor in deciding which work was to be done in the next release.Releases were planned at least 18 month in advance. Unless a fault/ feature was considered a 'show stopper' and there was a work around then the software was not fixed until the next time that it was scheduled for rework. Very frustrating from a servicemans point of view when sometimes it was a quick fix to correct a small error.
With JPA, any software errors that don't have a workaround or are considered 'showstoppers' at least once the coding has been fixed it could be applied centrally to the server and have an imediate effect.
 
Thread starter Similar threads Forum Replies Date
BuggerAll Army Pay, Claims & JPA 7
polar Army Reserve 25
Acid_Tin Army Pay, Claims & JPA 17

Similar threads

New Posts

Latest Threads

Top