Award notice observed
Latest variant observed by Bidwake on .
Open this official Contracts Finder notice
Record references
- Release reference
779455a6-618f-4a15-b800-d133e380411c-199799- Published tags
- award
Loading records…
Public procurement
See the published facts, notice history, awards and supplier links in one place. Open the original Contracts Finder notice for the full record.
ocds-b5fd17-7d5a13bd-1c00-441a-8a27-25151f0ce5a4Published facts
779455a6-618f-4a15-b800-d133e380411c-199799The backdrop for this requirement is our PR18 periodic review of Network Rail which needs to take into account: • Network Rail's reclassification as a public sector arm's length body; • a revised funding structure for the CP6 control period ; • our route level approach for PR18; and • the separate funding arrangements and periodic review determination that apply to Scotland. We wish to commission a report that sets out whether Network Rail's allocation of costs to its Scotland route (about 10% of the total) is reasonable, and consistent with best practice. The report will feed into the work of ORR's Regulatory Finance team on the financial framework for PR18. We expect to publish minded to positions on a range of financial issues in spring 2018 and our draft PR18 determination in June 2018. The consultant will be required to produce a report that addresses the following questions: In the context of the separate funding settlement for Scotland - 1. Are Network Rail's cost allocations to Scotland reasonable and consistent with best practice for each type of cost? These costs include overheads (e.g. HR costs), central activities (e.g. timetabling) and central programme costs, e.g. digital railway. 2. How could the Scotland route participate in any company-wide risk fund pooling or self-insurance arrangements? If Network Rail has used an approach, is the calculation of the contribution to be paid by Scotland reasonable? 3. Are there instances where Network Rail uses a top down approach to cost allocation (e.g. allocating HR costs by number of staff) where it could instead use a bottom up approach? For example, what is the cost of providing HR services to Scotland? A further example of this issue would be the allocation of working capital balances in the NR financial model. 4. Where relevant, how robust is NR's bottom up challenge to its top down allocations? How extensive has this been and how does this compare to best practice? 5. Is a policy of allocating some project development costs across all routes, even where the project may not have commenced in some routes (for example trial costs associated with new technology) reasonable with respect to the Scotland route, given its separate funding? 6. Are there any arguments for moving away from a policy under which infrastructure projects costs are always attributed to the route in which the infrastructure is built (for example Carstairs junction). Reference can be made to the question we asked on this issue in our first consultation on the financial framework and the responses received. Reference may also be made to earlier review work commissioned by ORR on this point. Additional information: Prospective bidders are advised to register on to the tender via ORR's eTendering Portal early as all further information regarding this tender will through the portal.Bidders should note the end dates/times for the submission of requests for clarification and proposals as set out in the ITT document.
Observed notice trail
Events follow the publisher date where one is available. “Seen by Bidwake” is the date this service first found the record.
Award notice observed
Latest variant observed by Bidwake on .
Open this official Contracts Finder notice
779455a6-618f-4a15-b800-d133e380411c-199799Awards and suppliers
Buyer: OFFICE OF RAIL AND ROADSupplier: CAMBRIDGE ECONOMIC POLICY ASSOCIATES LIMITED
ocds-b5fd17-7d5a13bd-1c00-441a-8a27-25151f0ce5a4-1End dates, recurrence wording and links are shown as they appear in public notices. They do not create a new opportunity. If no later linked record appears here, that means Bidwake did not find one in the records it has loaded; it does not prove that none exists.