General Update

Hi

There are a number of things going at the moment and due to outside circumstances which have been beyond my control I have been on leave at intermittent intervals over the last month and just getting myself back up to pace now.

Projects active at the moment are:

• Edge - ITS032 (still)

• CF9 Migration - ITS066
  

I will write a catchup to introduce the current migration for ITS066.

Edge

The edge application has been deployed, the url has not yet been disclosed as the service has not formally been launched at this time.

Prior to me going off the application had been brought up to a stage where it was ready to go on the server and be user tested. During the test some issues were identified (please see darcey gillies email dated 24/03 and points 1 to 4 of the attached issues document) which have since been addressed, additionally more requests have been made for off spec changes to be included (point 4 in the above list) and at this stage the project manager is looking for somewhere to draw a line in the sand.

Prior to making the changes our progress was again hampered by confusion over its location (see alex carters email dated 16/03) , I was advised the application was stored on the T drive as per the mapping on alex's email, unfortunately it wasn't there and was put into O drive instead.

A knock on effect of this was that I had no permissions to access this drive which prevented me from doing any configuration on the application, such as the untested automated login system needing to be in the right environment to work. Permission for access was not actually granted to me for another week which was obviously a massive delay to the client.

As of yesterday the stage we are at is that this application should have been wrapped up weeks ago, we have encountered budget problems, clients changing their minds and requesting new features after the build stage and numerous delays in getting access to locations or resources.

We are now looking to add functionality to check for broken links (again the issues document above point 4) however I have been assured this is not much to do.

We will then be looking to retest and redeploy, hopefully this will close of this project.