Structnet

Improveing project management sucess with the process of "Structured Scheduling".

Project management scheduling.

We have revolutionized the process creating & operating Industrial size Microsoft Project schedules. If you use something other then Microsoft Project, we can fulfill your scheduling needs also. Our methods work effectively for all industrial Projects & programs. Be they construction or aerospace and more.

We can build a project schedule with:

  • Full vertical & horizontal integration.
  • Milestones are fully linked, Horizontal & Vertical.
  • fulfills all government standards & requirements (DOD).
  • we can generate sub schedules for your subcontractors that are fully integrated.

When we have finished a Product Breakdown Plan we produce a project schedule. The schedule is numbered & labeled to match the PBS. From PBS to ready to work project schedule to you in 24 hours.

The Structnet method of "Structured scheduling" works regardless of industry. Whether it be Aerospace, Construction, Industrial, Manufacturing or Software. We have tailored our training to be industry specific. Click one of the following links to learn of our method for your work type.

What is different about Structured Scheduling?

If "Structured Scheduling" uses all of the same rules; how can it be different, and help to address problems that others have had difficulty solving? There are several subtle differences that are used. With the exception of the Structnet algorithm, most of the differences are features that any scheduler should know and understand. These are just good scheduling techniques. Some of these techniques are difficult and time consuming to religiously follow when building a schedule manually. They are still good practices. Vertical linking, following the Parent/Child relationship, is one of those difficult things and is frequently ignored. particularly during the proposal process, yet it is the way drawing trees are established, assemblies are designed and systems are built. Whether it is building production units, linear or vertical production scheduling in construction, the principles are the same. The use of the Structnet algorithm is the thing that takes the drudgery out of building a schedule framework. The difference is that the Structured Schedule Framework (Framework) uses these features in a very consistent and repeatable manner for every schedule. One of the goals established when this was originally conceived was "If you put 5 schedulers in a room at 8:00 AM with the same set of criteria, by 5:00 PM, 4 of the 5 schedule frameworks would be virtually identical, would meet all of the current Government requirements, and would be ready to input durations and resources to find the critical path to each major IMP Event. The system had to be easy to teach, easy to learn, and easily understood by nontechnical members of the program team. That goal has been achieved by Structnet. The following are some of the features contained in a Structnet Structured Framework that differentiate it from many manually built schedules."

Consistency.

Consistency in form and function leads to repeatability. Repeatability leads to re-usability. These words are music to some people's ears and like scratching on a blackboard to others. Due to the time & effort it takes to process the organization & consistency structnet provides. I understand why industry dos not follow our ideals. I am going to go out on a limb and make a general statement that any one can easily argue is untrue, but like all generalizations they are flawed in some way. Engineers like consistency, Artist like to reinvent the wheel and put their perspective on each piece of art that is created. Some consider planning and scheduling as an art and some consider it as science. I submit that planning and scheduling is both an art and a science. Leonardo Di Vinci was both and considered one of the world's geniuses. Developing a team that respects the existence of both art and science will improve the team's communications and better performance should follow. Vive La Difference.

Product Breakdown Structure (PBS) and Common Elements are built following 881C exactly like the system will be assembled, which should match the drawing tree. It is another way of creating an exploded view of a system that is consistent with the drawing tree and the sequence of assembly.
 

Weaving the Fabric (Linking the IMP/IMS)

Manual Linkage
The schedule can be manually linked.

Structnet letterhead
Loomwork_hand

Horizontal Linkage is easy. Linking the 41 tasks and milestones is a simple task. It is a list that can be linked finish to start with a few exceptions.

Vertical, parent to child or child to parent linkage can be done, but is much more difficult and time consuming than horizontal linkage.

Weaving with an Algorithm

An algorithm can be used to weave schedule framework into a strong and usable fabric, where all of the vertical and horizontal linkages are established.

Loom-machine
  • A framework to design a system consisting of 50 underlying products, parts and assemblies, and build 20 Engineering Design Models (EDM) or production deliverable units; can be generated in 1 Day.
  • A fully linked Milestone Network is created within the Framework.
  • The Design and Production phases follow the same PBS.
  • Production schedules for one or more, 20 for example, deliverable systems are built with the framework. This can be used for production earned value management as a stand alone or in conjunction with an MRP system.
  • There is only one task without a predecessor and one task without a successor.
  • There are no constraints. Allowing Schedule Risk Analysis to be conducted as soon as durations have been input into the Framework.
  • Buffers (Margin) are included off of each IMP event to aid Schedule Risk Analysis. Buffers may also be added to each product SLPP to aid the Schedule Risk Analysis.
  • Each Framework, is initially created at the Summary Level Planning Package (SLPP) level, then, using Rolling Wave for the processes, decomposed to Control Accounts, Work Packages and Planning Packages.
  • There is an IMP in every schedule including the 7 major IMP Events.
  • Every IMP Event is vertically linked, not just traceable, from the lowest terminal element in each leg of the product structure to the related IMP Event.
PERT Chart Expert-1

Structnet provides a consistent, repeatable, reliable schedule. One that is easy for all stake holders to understand. Our consistency provides a schedule that any stake holder can relate to their pertinent data necessary to fulfill their job at hand. Further more Our schedule will better fulfill tomorrows proposals & jobs with reliable data from todays successful programs.

Structnet Home | Scheduling | Overview | Structnet Concept | Training | Support | Consultants | Tools | Roles | Contact Us | FAQ |
[Construction] [Manufacturing] [Software]

This website is produced and maintained by STRUCTNET Construction Web Services since 1996