• Home
  • Our Team
  • Useful links
  • Blog
  • Contact
P2G LLP

The Monthly Report

7/10/2019

0 Comments

 
The principle of all PFI projects is that Project Co (and their subcontractors) should self-report against their own performance and declare to the Authority any areas of underperformance against the Service standards. The Monthly Report is where they should do this. 

It is perhaps naive to believe that this is going to work. How many times have you sped down the motorway and then called the police at the end of your journey in the knowledge that you will be fined and awarded penalty points? It just isn’t human nature and, certainly, it isn’t typical for commercial organisations to create a culture that expects their staff to purposefully diminish their returns on a contract in order to be contractually compliant.

On this basis alone, it is important for any public sector organisation to actively read and question the Monthly Report and to ensure that it properly addresses all of the requirements under the contract. 

The minimum requirements for the Monthly Report are typically set out in both Schedules 14 and 18 of standard form contracts and will include the following:
​
  • Incidences reported to the helpdesk, including the target Response Times and/or Rectification Times and those achieved;
  • Maintenance and other task based activities carried out in the month;
  • Maintenance and other task based activities planned for the next month;
  • A summary of all Failure Events and Quality Failures (or equivalent);
  • The effects of these Failures;
  • A time frame, in hours, of any event not Rectified on time;
  • The deductions to be made from the Service Payment in respect of Failure Events; and
  • The number of Service Failure Points awarded in respect of each Service for that Contract Month.

However, for each Service that is covered by the Project Agreement, it is important to go back to the Service Level Specification and look at the requirements. 

On most standard form contracts the Key Performance Indicators (KPI’s) or Service Parameters (SP’s) for each Service are typically well defined and stipulate what should be measured to demonstrate compliance. There can be up to 45 KPI’s per Service on a typical contract, so if there are say 11 Services (General, Estates, Helpdesk, Cleaning, Catering, Portering, Security, Telecoms, Pest Control, Waste and Energy Management) that could easily amount to in excess of 350 individual scores that need to be reviewed and critiqued each and every month. 

What is not always well defined, though, is the method of monitoring and the source data that will be utilised. 

For Reactive tasks, the method of monitoring is invariably measured using the Helpdesk, provided that Project Co (and their Service Providers) are properly reporting all reactive tasks using the Helpdesk (see our ‘Follow on tasks’ post). What is often missing, however, is clarity around the method of measurement for qualitative or planned tasks. It is therefore important to sit down with the Project Co and Service providers to check whether the contents of the monthly report do in fact evidence compliance with each of the KPI’s or SP’s.

Typically, the Authority will have a defined time frame to raise any issues with the self-declared scoring. This is typically two months, although in order to get any issues properly credited in the current month’s invoice, you may have as little as 5 days. Once two months have passed, the Monthly Report and the data it contains become the sole record for the period, with no challenges able to be raised except in cases of deliberate misrepresentation, gross incompetence, gross negligence, or fraud.

P2G actively monitor the performance and monthly reporting on a number of NHS PFI projects and our experiences to date suggest that there is a large divergence between reported and actual performance when measured against the contract. If you are interested in checking whether you are receiving the Services for which you are paying, please feel free to get in touch. 

0 Comments

Programmed Maintenance Follow on Tasks

17/6/2019

0 Comments

 
On many of the PFI contracts for which we provide performance management services, we see an absence of self-reporting of issues to the Help Desk. This is particularly prevalent in tasks that are identified through planned maintenance activities. Here we discuss the background to the issue and what your Project Company and service providers should be doing.

In the vast majority of PFI contracts there is an obligation to agree an annual planned maintenance programme, often referred to as the Schedule of Programmed Maintenance. These are pre-approved activities that the Hard FM contractor will carry out over the course of the year and for which they traditionally receive an Excusing Cause, in other words they are relieved from their obligation to maintain the Availability of areas whilst undertaking the planned maintenance activity without penalty. 

Programme descriptions are often cursory in nature, therefore to understand the true nature of the planned tasks that sit behind an activity, it is often necessary to ask to review the ‘task sheets’ that sit within the CAFM system and which stipulate the individual tasks that make up the planned activity. 

The important point to remember is that the relief that the Excusing Cause provides is limited to the planned works on the programme, not consequential works that are discovered whilst undertaking the planned maintenance activities. 

So, taking an example of fixed wire testing, the planned activity is to conduct the test. If the test results show elements of the electrical system that are not compliant, this constitutes a fault and should be reported to the Help Desk by your service provider. Thereafter, it should be responded to and rectified in accordance with the requirements of the contract. 

It appears to be common practice on some contracts for service providers to utilise systems outside of the Help Desk to manage the need for consequential maintenance activities that are necessary to address faults discovered as a result of planned maintenance activities. It is our belief that this is primarily an attempt to avoid the maintenance works being subject to the requirements under the contract terms to respond to and rectify faults within specific timeframes. 

There are clearly examples where future maintenance needs identified as a result of planned maintenance activities do not represent faults. For instance a lift inspection may identify that a component is nearing the end of its useful life and, whilst still compliant at the date of the inspection, may need replacing within the next 6 months. It is perfectly acceptable practice in this regard for your Project Co to update their planned maintenance programme to pick up this requirement.

What is not acceptable, however, is for issues that are faults (ie issues that do not meet the contract standards) to be programmed at a future point or not logged on the Help Desk. 

If you think that your service providers may be operating outside of the approach outlined above, please do not hesitate to contact us for further advice. 

0 Comments

    Authors

    The authors have experience of more than 100 PFI projects in multiple sectors.

    Archives

    March 2022
    January 2022
    September 2021
    March 2021
    April 2020
    March 2020
    October 2019
    September 2019
    June 2019
    March 2019
    May 2018
    June 2017
    October 2015
    July 2015
    June 2015
    April 2015
    March 2015
    February 2015
    January 2015
    October 2014
    August 2014
    July 2014
    June 2014
    May 2014
    October 2013
    July 2013
    June 2013
    May 2013

    Categories

    All
    Charitable Donation
    Code Of Conduct
    Contracts
    Covid 19
    Covid-19
    Damage
    Honesty
    Insurance
    Monthly Reports
    News
    PF2
    Pfi
    PFI Handback
    PPM
    Profit
    Public Sector
    Relationships
    Savings
    Secondary Market
    Special Purpose Companies
    Vacancy

    RSS Feed

P2G LLP
A Social Enterprise Partnership
Registered in England & Wales
No. OC375527
​P2G Contract Support LLP
Registered in England & Wales
No. OC419519