甘特圖在行業中的典型應用

應用于磁電/裝備制造/食品工業/建筑等行業

計劃排程與執行監控

計劃排程與執行監控

在APS系統當中，運用甘特圖實現生產任務層級關系及生產計劃與實際執行情況的實時比對效果

了解更多

原料/人力資源調度

原料/人力資源調度

在資源調度系統當中，利用甘特圖實現任務自由拖動及資源負荷的實時動態計算效果

了解更多

復雜條件下的資源優化

復雜條件下的資源優化

 在資源調度系統當中，應用甘特圖實現任務關聯關系，任務約束及執行狀態的監控效果

了解更多

建筑項目管理

建筑項目管理

在項目管理當中，應用甘特圖實現圖形與數據聯動的聚光燈效果

了解更多

分屏/雙甘特圖：

幾乎所有計劃和調度程序都需要在水平卷動時保持兩個不同模型或同一模型內兩個不同部分的數據一致。FlexGantt 框架包括一個雙甘特圖可以實現上述目標。用戶可以在任何時間分割/取消分割甘特圖。水平分割線能用于調整上下兩部分大小。時間線對象可以從一個拖至另一個。

模型視圖控制器：

FlexGantt 遵從與 Swing 相同 MVC 方法。許多不同的模型用于各種各樣的用途。一個日歷模型跟蹤假日和周末。一個頁面模型支持使用者加載不同的計劃范圍，一個書簽模型存儲了應用程序和用戶自定義書簽。然而，首要的模型是甘特圖，它為甘特圖組件提供數據。它是樹狀圖模型的延伸，因此它能在甘特圖的左手邊填上數據（左手邊是樹狀圖）。它同樣返回成為時間線的對象顯示在右手邊時間線的下方。時間線對象代表活動、工作、事件、重要事件，甚至任何可以放在時間線上的事情，因為它可以被連接到時間點或時間區。下面的圖片顯示了甘特圖模型的結構。

懶加載：

根據應用程序類型，需要顯示的數據量可能十分龐大。在這種情況下，只有使用“懶載入”方法，用戶界面才可以迅速和有較快響應。“懶載入”意味著數據只在用戶真正需要時，從服務器（或數據庫）傳到客戶端。FlexGantt 從最底層設計支持懶載入。例如：實現樹表展開監聽界面的對象將在樹展開前收到一個事件，這樣，父節點的子節點可以被載入。頁面模型是另一個支持懶載入架構的例子。

頁面：

如果一個調度程序需要處理大量的時間線對象，分割時間線到若干頁/時間跨度是有必要的。這一方式將數據分為小塊，甘特表可以更加容易地處理。頁模型處理單獨的頁面。可以在當前頁、前一頁、后一頁、半島外圍網上直營和尾頁查詢。用戶界面提供一個控件用于選擇單獨頁面。

可自定義時間線：

每個程序有著對時間線的自定義的特殊要求。一些需要在日期旁顯示周數，另一些則需要顯示天數（例如“第241天”）。時間線可以靈活設計。它的模型可以被替換，它的顯示可以被替換，甚至整個時間線可以被替換為自定義子類。

層：

FlexGantt 使用獨特的層方法，該方法因在圖片和繪圖程序中的使用而聞名。每個甘特圖由兩個層集合組成，系統層集合提供核心功能（例如繪制垂直網格線），另一個層集合繪制時間線對象（活動、事件、重要事件）。下面的圖片顯示了層棧。程序可以增加任意多的時間線對象層，可以容易地一次完成分組對象、顯示/隱藏的功能。層同樣支持透明化，因此層疊時間線對象能夠容易地被識別。

拖放網格:

時間線對象可以被水平拖動、縮放和垂直拖動。一個可見網格能被拖放操作激活，所以時間線對象可以更容易地被放置在特定時間。網格由策略控制，意味著任何種類的網格都可以被完成。可以設置默認網格策略使得時間線對象可以吸附到從千年、百年、十年、年、月、星期、日以至于毫秒的任何時間。

策略控制行為：

調度程序在顯示信息、編輯數據、響應用戶交互方面有著千差萬別。FlexGantt 的策略框架能夠根據這些不同而被用于設定相適應的甘特圖。策略是小的決定者，通常不包含很多的代碼。它們同樣是無狀態的。在許多情況下，它們僅僅返回標記（booleans）和命令。標記用作控制程序流，而命令被用作實現實際的數據修改（通過一個包含撤銷和恢復的命令棧）。

彈出/注釋：

時間線下方的欄是顯示一個事件的好區域，但是由于空間限制，它只能顯示有限的信息。當鼠標指針懸停在這一欄上，顯示彈出/注釋是一個很好的特性，這樣就能顯示足夠多的信息，提供給計劃者用作制訂調度決定。FlexGantt 的彈出可以與 Swing 組件一樣被自定義。不同的顯示可以被映射到不同種類的彈出對象。彈出對象由特定的彈出策略導出。下面的圖片顯示了默認的彈出顯示，它顯示了序列化形式的彈出對象。

可變行高:

FlexGantt 圖的每行可以有自己的高度。這樣特性在樹表節點代表不同類型的對象或一個量與每個節點相關聯是十分有用。在此情況下，行高可以反映這樣量（例如一個資源的容量）。

多行排序：

甘特圖左手邊的樹表支持多行排序，意味著用戶可以同時選擇多個樹表列，表中數據將基于此選擇排列。 FlexGantt 使用快速排序算法進行排序，支持升/降序排列。

日歷模型：

日歷模型提供甘特圖中有關周末、假日、或任何特殊時間范圍的數據。日歷模型的入口顯示在整個層容器的高度（右手邊）。最顯著的使用日歷模型的例子是對周末的定義。周末的背景將會以灰色顯示。

自動卷動：

如果 FlexGantt 圖頻繁更新它的“現在時間/系統時間”，有時使程序注意這樣時間是有必要的。當自動卷動被激活，現在時間光標（垂直虛線）將提留在層容器的中央，即使時間流逝。當程序具有更多監視功能而不是交互調度功能時，這是一個非常有用的特性。

書簽：

用戶日益習慣于書簽的概念。FlexGantt 同樣支持它們，而且用戶可以使用它們來快速調整時間線設置，這樣一個特定的時間點、間隔和范圍會被顯示在甘特圖上。定義過的書簽被列在菜單的導航控件中。 當用戶點擊菜單按鈕時，如果控制鍵被按下，將會顯示被標簽的時間間隔的小預覽圖片

命令框架：

FlexGantt 提供一個小但強大的命令框架。它被用來支持編輯操作的撤銷和恢復。命令框架包含命令、命令棧、命令棧監聽器和進度監視器。命令通過甘特表被執行、撤銷和恢 復，甘特表內部使用一個可置換的命令棧。為了保證用戶界面的相應，命令在自己的線程中進行。命令棧事件在命令執行時被提交。進度監視器用來顯示命令的進 度。子進度監視器用來監視包含其他許多命令的混合命令。一旦一個命令結束執行，它將被加入到命令棧的撤銷列表中。當一個命令被執行而無法撤銷時，這一列表 將被清空。命令框架使用一個高級抽象層次，這一已存在的命令架構（傳統代碼）可以被重用。

打印：

甘特表顯示的計劃是一份文檔，而任何文檔都應該能打印。內建的打印支持使得用戶指定需要打印的時間范圍和間隔（見下圖）。結果表可以被打印成具有多頁的寬度和高度。

關系：

時間線對象之間具有某種關系是很普遍的。例如項目計劃軟件通常在它們之間定義約束。一些約束的例子：“在……之后開始”，“在……之前完成”，“同時開 始”，“同時完成”。FlexGantt 通過繪制它們之間的線條來顯示關系。每個程序有自己的顯示方式（不同的約束有不同的顏色和/或不同的線風格）。通過插入自定義關系顯示，可以實現任何種類 的關系顯示

可插入顯示和編輯器：

Swing 定義了許多顯示和編輯類用作它的用戶界面組件，例如樹、表格或列表。FlexGantt 與之相同，定義了樹表單元、列頭、彈出、日期線模型、時間線對象、事件線對象的顯示。時間線對象編輯器在甘特表左手邊的透明窗口里顯示。

多線：

多線特性使得甘特表在同一行上下顯示時間對象。這樣原可能互相重疊的時間線對象可以正常顯示。

Split Screen / Dual Gantt Chart

A feature required by almost any planning and scheduling application is the ability to keep the data of two different models or two different sections of the same model in synch while scrolling horizontally. The FlexGantt framework includes a Dual Gantt Chart that is capable of doing exactly that. The user can split / unsplit the Gantt chart at any time. A horizontal divider can be used to resize the upper and lower part. Timeline objects can be dragged from one to another.

Relationships

It is quite common that timeline objects have some kind of relationship with each other. Project planning software for example often defines constraints between them. Some examples for constraints are: 'start after', 'finish before', 'same start', 'same end'. FlexGantt can visualize them by drawing lines betwen them. Each application has its own way of visualizing them (different colors and / or line styles for different constraints). By plugging in a custom relationship renderer it is possible to implement any kind of relationship rendering.

Lazy loading

Depending on the application type the volume of data that needs visualization can be rather massiv. In these situations a user interface can only be fast and responsive if it uses a 'lazy loading' approach, which means that data will only be transferred from the server (or database) to the client when the user actually requests it. FlexGantt has been designed from the ground-up to support lazy loading. Example: objects that implement the tree table expansion listener interface will receive an event before the tree expands so that the child nodes of the expanding parent node can be loaded. The paging model is another example for infrastructure that supports lazy loading.

Model-View-Controller (MVC)

FlexGantt follows the same MVC approach that Swing is using. Several different models are used for various purposes. A calendar model keeps track of holidays and weekends. A paging model supports the user in loading different planning horizons, a bookmark model stores the application- and user-defined bookmarks. The primary model, however, the one that feeds the Gantt chart component with data is the Gantt chart model. It is an extension of a tree table model so that it can populate the left-hand side of the Gantt chart with data (the left-hand side is a tree table). It also returns so-called timeline objects that are displayed on the right-hand side underneath the timeline. Timeline objects represent activities, tasks, events, milestones, pretty much anything that can be placed on a timeline because it can be associated with a time point or a time span. The following graphic depicts the structure of a Gantt chat model.

Bookmarks

Users have become more and more used to the concept of bookmarks. FlexGantt supports them as well and users can use them to quickly adjust the timeline settings, so that a specific time point, granularity and horizon will be shown in the Gantt chart. The defined bookmarks are listed in a menu in the naviagtion controls. Small preview images of the bookmarked time span will be shown if the control key is down when the user clicked on the menu button.

Layers

FlexGantt uses a very unique layering approach that is known from graphics and mapping applications. Each Gantt chart consists of a set of system layers, which provide the core functionality (e.g. a drawing vertical grid lines) and a set of layers dedicated to rendering timeline objects (activities, events, milestones, ...). The picture below depicts the layer stack. Applications can add as many timeline object layers as they like, allowing them to easily group objects and show or hide them all at once. Layers also support transparency so that overlapping timeline objects can be easily identified.

Drag & Drop Grid

Timeline objects can be dragged and resized horizontally and dragged vertically. An invisible grid can be enabled during these drag & drop operations so that a timeline object can be more easily placed at a specific time. The grid gets controlled by a policy, which means that any kind of grid can be implemented. The default grid policy can be configured to make timeline objects snap to anything from millenium, centuries, decades, years, months, weeks, days, all the way to milliseconds.

Policy controlled behaviour

Scheduling applications vary too a large extent in the way they visualize information, edit data, and respond to user interaction. FlexGantt's policy framework can be used to tailor the Gantt charts to these variations. Policies are small little decision makers and usually do not contain a lot of code. They are also stateless. In many cases they return flags (booleans) and commands only. The flags are used to control the program flow, while the commands are used to perform the actual modification of data (via a command stack with undo and redo capabilities).

Pluggable Renderers & Editors

Swing defines several renderer and editor classes that are used for its UI components such as tree, table or list. FlexGantt does the same and defines renderers for tree table cells, column headers, popups, dateline models, timeline objects, eventline objects. Editors are available for tree table cells and timeline objects. A timeline object editor gets displayed in a transparent window within the right-hand side of the Gantt chart (in-place editing, see picture below)

Paging

If a scheduling application needs to deal with a large amount of timeline objects then it often makes sense to divide the timeline horizon into several pages / time spans. This way the data gets broken into smaller chunks that the Gantt chart can deal with more easily. The paging model manages the individual pages. It can be queried for the current page, the previous page, the next page, the first page, and the last page. The user interface provides a control that can be used to select individual pages.

Popups / Annotations

A bar underneath a timeline is a nice representation for an activity but it can only carry a limited number of information due to space restrictions. Popups / annotations that show up when the mouse cursor hovers over such a bar is a nice feature that can display a wealth of additional information that the planner might need to make a scheduling decision. FlexGantt's popups can be customized in the same way that any Swing component can be customized. Different renderers can be mapped to different types of popup objects. The popup objects are looked up from a specialized popup policy. The image below shows the default popup renderer that displays popup objects in its serialized form.

Printing

A plan shown in a Gantt chart is a document and every document needs to be printable. The built-in printing support for FlexGantt lets the user specify a time span and a granularity to be printed (see picture below). The resulting chart can be printed on several pages wide and high.

Command framework

FlexGantt provides a small but powerful command framework. It is used to support editing operations that can be undone and redone. The framework consists of commands, a command stack, a command stack listener and a progress monitor. Commands are executed, undone and redone via the Gantt chart, which internally uses a replaceable command stack. Commands are executed in their own thread in order to keep the user interface responsive. Command stack events are issued during the execution of the command. Progress monitors are used to display the progress made by a command. Sub-progress monitors are used for compound commands that consist of several other commands. Once a command has finished execution it will be added to the command stack‘s list of undoable commands. This list will be cleared when a command gets executed that can not be undone. The command framework uses a high level of abstraction so that an already existing command infrastructure (legacy code) can be reused.

Multiline

The multiline feature enables a Gantt chart to display timeline objects within the same row but above and below each other. This way timeline objects that would otherwise overlap each other can be displayed without problems.

Variable row heights

Each row in a FlexGantt chart can have its own height. This feature is very useful when the nodes in the tree table represent different types of objects or if a quantity is associted with each node. In this case the row height can reflect this quantity (e.g. the capacity of a resource).

Multi-column sorting

The tree table on the left-hand side of the Gantt chart supports multi-column sorting, which means that the user can select several tree table columns at the same time and the data in the table will be sorted based on this selection. FlexGantt uses a quicksort algorithm for fast sorting and supports ascending and descending sorting.

Calendar Model

The calendar model provides data for the Gantt chart related to weekends, holidays, or any other kind of special time span. Entries in the calendar model are rendered across the entire height of the layer container (right-hand side). The most prominent example for the use of the calendar model is the definition of those days that are considered weekend. The background of weekend days will grayed out.

Autoscrolling

If a FlexGantt chart updates its 'time now / system time' frequently then it sometimes makes sense to make the application focus on this time. When autoscrolling is enabled then the time now cursor (a vertical dashed line) will remain in the center of the layer container even when time progresses. This is a very useful feature when an application has more of a monitoring function then an interactive scheduling function.

Customizable Tmeline

Each application has its own requirements for the timeline. Some require the week of the year to be shown next to the date, others want to show the number of the day in the year (for example 'day 241'). The timeline has been designed with flexibility in mind. Its model can be replaced, its renderers can be replaced, even the entire timeline can be substituted with a custom subclass.