In production or project planning the scheduling of backlog items is an essential task. It is important to keep an overview of all work to be done and to include the items step by step in the planning board. In a previous blog post we have already discussed different backlog visualizations. Now, we will see how our Visual Scheduling Widget can help you to perform the handling of backlogs by using Gantt charts.
Operational Agility sounds like one of those “buzzwords” such as Big Data, Freemium or Snackable Content, which keep reappearing on power point slides that typically baffle half of the audience. In the beginning, I took the term Operational Agility as is – quick & easy operations. By taking the simplest dictionary meaning of Operational Agility, it left me with more questions than answers. What does it mean to be quick & easy? How does a firm achieve this? And if this exists, why aren’t all firms practicing it?
During the last years we gained a lot of experience in developing HTML5 Gantt charts. It boiled down to a generalized model for resource planning, that is now basis of our Visual Scheduling Widget. How this model looks like, I started to explain in my previous blog post, when I described the data model and its' different types of objects we think are relevant to visualize resources and their activities.
In this post I explain how to map the members of this data model to interactive graphical representations. So the second (and last 😉) part of my series of blog posts about our generalized model for HTML5 Gantt Charts refers to the concept of mapping.
Resource load plays a key role when it comes to order planning. Planners have to ask themselves whether a certain resource has enough capacity on a certain day to work off a task. Usually, the capacity load is visualized by a capacity curve, also called histogram, in a Gantt chart. In this blogpost I‘ll introduce two other ways of displaying capacity load: by an own resource view and by a calendar view as is known from Microsoft Outlook.
In spite of the steadily growing automation, many small companies still plan their orders manually. Ideally, they use an interactive planning board for scheduling support. In this case, the order backlog (also called order pool or stock of orders) is an important part of this planning board. We have different ways to visualize this backlog for our customers, the presentation depending on whether the orders consist of several sub orders or not, e.g. For all of you dealing with Gantt charts and manual planning I have summed up four visualization versions.
If you enter the term „excel horror stories“ into your search engine you’ll get a long list of stories about financial disasters, wrong scientific insights or organizational nightmares being caused by the spreadsheet software. TransAlta lost 24 million due to a cut and paste error, designations of genes like SEPT2 get changed unnoticed into data by Excel, the NASA had wrong measure data in their Excel tables with which they keep on working, and so forth. Are you sure that there is no mistake hidden in your Excel sheets with which you run your company or plan your production?
Again, some time has passed since in the last post of my loose series of blogs about the basic facts and features of Gantt charts I shared with you some insights on their structure and graphical ingredients.
Now that you’ve learned the basics, you're doubtless eager to create a meaningful and clear-cut chart of your own and this is why today I'd like to shed some light on the preliminary considerations needed and the steps to be followed to achieve this.
It's been a while since I started my loose series of blog posts giving insights into the basic facts and features of Gantt charts by writing about why they are still popular today.
I'm quite sure that to some the actual nature and structure of these charts has become a bit vague over times, what with further developments and extending of application fields. So I considered clarifying the graphical ingredients of a Gantt chart in the first place.
Possibly, you'll be surprised that the text is rather short. But first, as I'd like to clear the above mentioned vagueness, I'm going to keep my explanation as detailed as necessary and as concise as possible. Second, a structure as simple - yet effective - doesn't need much words to be explained. And third, when it comes to a visualization technique like a Gantt diagram, I rather prefer to work with images than with words.