IBSM Program Management

PROGRAM MANAGEMENT

To be a "Building Services Manager" and/or a "Project Manager", it is indeed a prerequisite that they understand how to read a program, and therefore by default - if you they read and assess one, and its content and understand the scope of works, the they should be able to write one...

This does not mean, you should be able use program software but to a degree as a preference, but at the very least be able to write it on paper, for others to copy into program. In fact most planners will not understand the strategy themselves (copy/pasting similar/previous project scopes, then adapting to suit), so will need your skill-set to make one.

"I am going to attempt to show in a video a good way to set off in your careers as trainee/assistants, this method is a little more complicated to start off with, but in time you will fly through your admin, and be on top of things alot more than you first thought possible (once you project file is formatted - this method lends itself to when you have more than one site, and need to keep upto date!), remember the purpose of this site, is me showing you/others, how to do it, in a way I prefer, if your mentor has a better way, by all means listen to him/her."

"At least compare both, and make your own mind up (always be open to new ideas), there are always different of ways to do the same objective, the purpose is to find one that suits you, your needs, and which you can build upon, and develop moving forward in your careers - Simple!" (Ketley)

SETTING THE SCENE
(Video will be available March 2024, and for a charity fundraiser - see charity page!)

Intended for trainees/assistants, but will also aid those BSMs and PMs currently doing well in their acting careers, fighting their way through delivery, this may be useful for the mindset, if worried about programming, planning and/or just tracking.

"Let’s start off by making this, very very simple, before diving in"

Purely for example purposes, if you were asked how to prepare for a mountain hiking trip, and plan for different events/circumstances and equipment needed, could you produce a bullet point list?, then add times/duration to each, and link them together whilst remembering some follow will one another in order, whilst others either at the same time or start later on/not straight afterwards/the end of their predecessor, but will remain dependant on one another.

This includes programming it against the clock to make a specific time (your PC date), baring in mind you will have faster and slower times (resource times) that need to be added all together making an overall general pace vs. waypoints used to represent the critical path of the program, to always be in a position to present tracking and reporting on your progress. Plan your waypoints (milestones in program) and produce/explain it in program format, with kit/equipment and relate this to a construction program for ease of understanding, as it will make more sense that diving into procurement, enabling, temps, site-set up, order placements, critical path milestones, closing out commissioning and aike, as a starting block.

"It is only a thinking exercise, NOT a construction lesson - the video below will screen share an example model program with some fundamentals that are useful, leaving out the complicated ones as to be fair, you can flood a program with data but without the right staff managing and tracking it, it is absolute useless!."

"Keevan will show one he use's to manage projects - just as always to give you ideas to use/dismiss however you feel fit - there is not an absolute right solution, nor a wrong way - as long as you can use it and report against it. You need to understand yourself, track and plan in it anoth to do the job, as the primary purpose."

BASIC EXAMPLES

Shown for example purposes only, to be explained further in mentoring
(Links presently disabled/available upon request)

Commissioning & Witness Approval Example

This view shown was not the one used to track the commissioning, this version was used as a RAG system, to indicate what had been witnessed and accepted, and has been used here to display the vast amount of different uses you can use programs for once you master them. In fact you can open and close a wide array of tracking tools pending on whom you are presenting to, ranging from things like this to baselining dates to show current status vs. contract program for reasons ranging from claims to just mitigating risk and getting back up on track. The limit for use in programming is entirely dependent on your own level of creativity and mindset.

Remember it is only hard, until you find an easy way of both learning, and implementing it...

"Bill Gates" once said; If he had a hard task to complete, he would give it to a lazy person because they would find an easy way to do it.

Once you master this, you will copy/paste and adapt thus, you'll be churning out work faster than your peers, and on top of things, inturn you will feel better in yourself, workplace, and in control of your objectives!.

Enabling & Retained Services Example

(See enabling page)

IST Planning Example

Although these are clear and concise trackers, Keevan prefers to add these into "COMM_TS" programs where/when applicable in an attempt to keep a central source of information, but otherwise as previously stated he will place links in his program to the PC/server filepath to where these documents are filed in his project folder, to keep them updated in readiness for review and witnessing yet still tracked in the program.

We all love a blast from the past here is an example from a 2015 Two-Stage

Shown to display that Keevan has been planning, programing and tracking projects, for many years and therefore in a good place to pass on/teach his knowledge and experience. In fact he started real program training around the year 2000.

The point here is, always keep work from the past, as it may come in handy one day...