Please note that from the 1st February 2010, the ACS RPL process is changing and this means that the information and samples on this site will only be useful for historical reference. Please check the ACS upcoming changes page for more details.

Project Reports - 2231-79 NEC-1

Author Profile

I have 24 years of IT experience. All of this has been systems management related, working on large systems. 20 years in the software industry and 4 years banking. I have extensive experience of IBM mainframe systems and a wide range of PC and mainframe software products.

Currently work as a product specialist working backline support for a number of Mainframe automation, storage and scheduling products.

Before emigrating, I lead a mainframe technical support team as Support Delivery Manager ensuring support objectives and service levels were met.

I have strong MVS assembler language skills and spend a lot of my time using IBM's IPCS debugging tool to analyse client's system dumps.

Worked for many years at the same international software company in a number of Roles including front line technical support, backline specialist support and pre sales consultant for MVS mainframe products.

Left university and trained as a MVS systems programmers at a large financial institution just outside London.

Graduated from university with a BSC honour in Civil Engineering, but never entered that career path

ASCO Project Reports - 2231-79 NEC-1 Project Report Examples

Complete RPL application form including Project Reports

This includes all the CBOK sections and both Project Reports detailed below for this RPL.

 

Project Report 1

"COMPANY C is a large insurance company based in Southern England. They requested a health check on their usage of the COMPANY B mainframe tape management solution DYNAM TLMS (TLMS) and advice on how they could consolidate their tape library..."

 

Project Report 2

"Recent structural changes in the support organisation meant that COMPANY B was looking to use global frontline queues to deal with clients' issues. As part of this process I realised that it is not only important to know if the local technicians are available to work issues, but also the whereabouts of everybody else in the global team. I needed to implement the usage of a local planning system across all Technical Support teams worldwide..."