
A practical tutorial by William Doyle (MRICS) explaining 'blockade reporting' for infrastructure projects (especially rail). The video defines a blockade as more than one continuous shift occupying an asset, outlines common challenges (detailed shift planning, real-time updates, stakeholder reporting, handback risk), and gives a three-step approach: Plan (shift planner), Record (shift records: access and works), and Report (dashboards and exportable reports). The presenter demos a live tool showing shift setup, actuals entry, Gantt/tabular views, metrics (lost time, shift scores), and how consistent, concise shift records give real-time stakeholder visibility.
Chapters
Foreign. Gather and in today's video we're going to talk about blockade reporting. Well, a lot of people have been talking about this recently and we often over complicate in my opinions. We worry about the intensity of the doing the works in such a kind of congested blockade environment. So hopefully today we can break it down so it's much, much simpler and easy to understand. So I've got a few slides and then we're going to go split this video into three cuts. Simply plan recalls and report. Let's get into it. So first, what is a blockade? What do we think it is? So most people associate this with rail projects but it's common in other infrastructure types. Highways, utilities and just really a whole range of infrastructure sectors. Again, most people probably think about this as a big seven deck occupation of the railway over Christmas or Easter. But for me it could be much, much simpler than this. We can simply define it as follows. It's more than one shift of continuous occupation of an asset. So we're just not handing it back in between shifts. Basically in railway terms that can be just a long possession where we work multiple shifts over a weekend without handing that asset back. So what are the common challenges? What are the things that we kind of worry about? So planning shifts in detail. We've got a time window. We want to make the most out of that window. Get maximum productivity, getting real time updates from site. What's going on? Why do we need to know that? Well that's linked with the third challenge which is keeping stakeholders informed in blockades. A lot of people are interested. There's a lot of investment in making that happen. It takes a lot of planning in advance, almost a year in advance, some projects to get that access, that infrastructure and then replanning during the shift. Tracking hand back risk. Can we hand back that risk on time? What is the risk to write time, handbag or very common challenges. So to answer those challenges we're going to split this into videos of threes. Simply planning, recording and reporting. That's what we need to do. That is as simple as it needs to be. So we're going to cut into three sections as I mentioned. Feel free to jump ahead. We'll put the markers in the description of the YouTube video. So let's get started. So let's start with shift planner. So we're in our shift planner function. I've already started here. So I've got my five shifts here. You can see one sign on 9 o' clock on the 23rd, which is a Friday night Then a follow up shift with a bit of an overlap here on the 24th and again got that hour overlap on each shift we're receiving 10 shifts access point same as Project Hall 1 Station Ainsdale. We've got three different supervisors. Some of them are doing two shifts out of the five. I want that rotation so you can see they're all possessions as well. Right let's get into it. So if we have a look at here and we can start to see we've got the shifts I've tagged them with the different teams so team one, team two and team three this is how we do that with our tags function. I put in the labor already. So we've got a team of six on each shift, bit of plan materials and worklocks. So yeah you can start to see how teams are there. Saber plant materials, activities. Let's dig into those. So I plan three different activities on each shift. I split it by location. I've got the different activities here. So we've got some root works and we've got some installation of precurs foundations. They put the plan start time and end time for each of those activity you'll probably put an hour by hour program in and you can put all that data in here. Really straightforward. We've done that for each shift. Different time, different activities at different locations. The thing that most people get worried about is the access information. How do I fill a shift record in when I'm still on track? So let's open up all the different shifts we've got planned and we'll go to access, just edit what we've got in there. So all the reference is the same. Where I've done this I put in the references for the work sites but let's just scroll across and have a look. So you can see here got the possession time work site and we've got all the different shifts here. So the first shift we need to capture that we're taking possession of the railway at 11 o'. Clock. We're then quarter past 12 get work site, get the C4 or the isolation and then we're on track. Our machines probably going to start work at 10 past midnight with them we'll say we're going to do work until quarter past six. That's how we've worked out that this shift's going to work and then we're going to look at the rest of ships. So you can see here I've not put any possession time information in. I'm not put any off tracking. We're Just taking over. There's a handover period, second shift is 6 till 4 o'. Clock. So we can see here we've got those handover periods. Same for shift 3 and shift 4. And then only in shift 5 do we actually need to put in the off track C4 and all that process in reverse. So you see that's quite easy for us to do here. So yeah, really easy to capture those individual shift records. Questions I often get is why in the SH2, what records will you get? Better quality, detail. We've got different teams, different team members and those five records are all very important in their own right. So let's save that. So you can see here we've got five shifts. Labor, plant, materials, worklock and attack of the team. Just to help just make it a little bit easier to understand, I'm going to plan those shifts now and that will create five shifts for our team and shift records. Join me in step two where we look how to complete each of these records. Okay, so we can see we've got our shifts here, we've got the different teams tagged, it's all ready for us to go. So very simple example, but you get the idea. Let's go back into our overall menu and we can start to see how that's changed. So we've got the key insights, we'll look at the key insights now. I'll open those on a new tab just so it's easy for you to understand. Okay, so we've got our key insights, gone straight into it, a Gantt chart. We can zoom in, we can zoom out, we can have a look around what this means. So all our activities are here, we can bring in the access ones if you want to, but we just got the construction activities. So I can go over and look at them and these are all the bits we've got planned to do in these shift plans. But if gaps in between shifts, as you can see, and personally I like to look at this in a more of a tabular view. So let's go to our project overview and we can start to see we've got all the planned start times, activities and then we'll drop in. So all these metrics will update as we start to fill in those records. And it's all live. So I know people watching this will do four hourly reports or hourly reports of stakeholders during these kind of key blockades. But it's all there for whenever you need it, either in that tabular format or in the Gantt chart. So this data is really straightforward. You can use obviously this which is Power Bi, which everyone seems to love. You can put it back into P6, you can do Google Timeline. You might even want to use some excellent short client tools, things like Apex to do all this. But ultimately each of these activities needs to be on a shift record of some form. Okay, great stuff. So we back to our project screen. I'm going to go into shift records. I've already started filling this in. We've got all our records here. Most people do this on their mobile device, tablet, phone whilst they're out on site. Freeze I'm sure do it on my laptop today. So I want to go into this record I've already started filling in and the two bits of information we really need to focus on purpose. This video is access and workload only on the shift information in order to confirm the resource should put in those times. So let's start with access Access information. So this is a possession quite a few steps as you can see here we've been pre populated all this information outside so we just need to fill in the actuals so we can put in that. The good thing about gather is that you have to put in the time. We automatically work out the date for you. You can change that if you want to but it's all anchored from that shift start time. So I can you put it manually? I'm going to match this for purpose. So let's assume we do everything to plan. We get the work site on time, takes over 15 minutes. Then to get the isolation on tracking machines. Well yeah, that's on time as well. Well done. All good and we're starting to progress but what happens if it's different? What happens if it actually starts later? Took us longer to travel down site but we have to explain why. So travel time from wrap was longer than expected. So we're actually starting the work a lot later or 20 minutes later. Might be sitting significant, might be significant but understand those differences is really important. Then we'll go and record the works and then we can come back here and put the works complete. So I've started to fill this in already but we've got three activities planned today. We have to fill in all the key times so nice and red here. So I've already put in the quantities but what's missing? So I actually have to put in the actual start type. Why is that important? So those bars we talked about before, well they need to be actualized so we'll just put in this series the same and you can see now it's gone green. We'll do the very same for this one. Just for ease let's assume this all goes to plan and then we'll work out what happens when it doesn't go to plan. So two greens. Great stuff. So first activity in CU123 installing troughing plan 200 meters. What was it actually? What time? What was the reason of variance? So we can record the start times. Let's say we started a little bit later, let's say 150 then we can actually start to put the end times in. What we'll encourage people to is put events in. This takes the date time. Now as you can see I'm filling that in a bit later on as per for this demo and then we can start to add in all this information. So let's say at 1:30 and we can add in. So this can be whatever you want. We can add in the pictures, we can have all the comments, it's all there and you put your name against it. Ultimately we need to say what time we finish. So if we started actually a bit later, we're going to finish a bit later, we'll make it a little much later for the purpose of this exercise. And we're actually saying we're not going to complete everything. Why we don't complete everything? Well, taking much longer to do due to ground conditions or whatever it needs to be. The key information is recording the quantities against the plan, recording the start times and then we're adding as many events, as much narrative as possible. So that's all in there. Then we're going to go back, we're going to complete the works, complete time, we're going to finish on time. That's good. And you can see here there will be no reason for variance and it's as simple as that. So let's go back and have a look at all of our records and have a look at how that affects the program. Okay, before we go any further let's have a look at what the second shift would look like. It's a little bit different, different to the first. So I've already done the the work log element which is good. Let's look at the access. So you'll see here we've only got the works commencement works complete. So we don't have to put in all this other information. They're non compulsory so I know previously been confused about trying to find a full shift record. Well what is compulsory? It's just what time do we start, what time do we finish? If it is different, we have to explain why. So even if it's one minute difference, we have to still put that in, which I'll just do now to get off track. So it's as simple as that. We do actually have to put in a delay category as well. So whatever it needs to be in here, maybe it's done paperwork to fill it. So it's as simple as that. Don't worry about filling the whole shift. Recording for works commence. Works complete. That is the only bit we need to do. Not all this in terms of possession, work site and the handbag stuff. Okay, so we've done two shifts. Let's go back to our key insights again. I'll open these a new tab. So you can see here we've got the program start to be actualized with the yellow bars. We're going. Okay, some things are taking a bit longer than we expected. We can see here the activity is taken a little bit longer and starting a little bit later. So yeah, not looking too good on that front. But we've got plenty of the, the blockade or the five shifts left to go. Again, we can look at this in a more metabular format. So we can see you've got all the planned activities. How do we've actually complete, so fully completed any lost time. So we've lost 0.3 of an hour so far. And we can see all this. We can go straight to the reports if you don't want to. Just look at these dashboards and that'll give you a full shift report for each of those shifts. You can see here Fred's shift will have a full report, so will Derek's. And that's exactly how you look at it during the blockade. It's always available, it's always up to date and we can start to see progress as it happens. Okay, so that's halfway through the blockade. Let's go and finish those records. So I've submitted all those now and they're all done by the supervisor each shift. We can go back into the key insights. We can look at the individual shift reports. So every single one has a report. It's all there. Good to go. Your summary reports, they're ready. You can run a labor report or a progress report if you want to get into detail. Great for going back into tools like P6 or maybe your short term planning solution. Things like Aphex, I mentioned before, you can use all those reports to get that information back in. But for us, let's go back into the key insights again. I'll open it on a new tab and we can start to see it. So all these are actualized now. I can dig into detail for each one. We've got the durations, which I think is really nice of each activity in minutes. So we can see exactly where we're up to. Project overview again, more tabular format. But we've got all these up to date now. All these times actualize. We've got the lost time. Not too bad in terms of lost time there. All the activities have been complete and we can start to see what's happened. We can look at some other metrics. So shift scores always one that's quite interesting. So we can start to look at how it looks. Got two shifts that are efficient, two production issues and one with frustrated access. Imagine if this was a 30, 50 shift blockade. You can start to see all that information in there. Access again. We start to pull out that data so we can start to look at our access timeline again. We've lost a little bit of time here, mainly down to plant and equipment. Shift duration was as planned. Working time was a little bit less as you can see, but it lost working time overall. But ultimately the project has all the information it needs available for stakeholders whenever you need it and gives you that real time information from site. So yeah, blockade reporting often made very complicated, but you can make it really simple by just collecting consistent shift records from each team every single day. Let us know how this works for you. Any comments, any feedback, let us know. Give it a try. Thank you much.










