Projects are the core architectural component of the OnSite system. At the same time, every organization conducts projects in its own unique way so an effective project management system has to be tailored to how that particular customer works. Within OnSite, we have built a project structure that does exactly that. And we have done it by thinking about projects from three different perspectives: work orders, less complicated or template driven projects, and highly complex dependency driven projects. While the project engine for these types – or buckets – of projects is the same within OnSite, how that engine is utilized differs based on the customer’s practices.
Let’s take a look at the example of an assembly work order. Work orders such as these can be entered directly into OnSite, but typically come from an integrated ERP. While dependencies are certainly important, they are so primarily to order the assembly work steps. So, the usual manner of interacting with work orders in OnSite is in list format – scroll down the list, choose the work order, expand to view activities, and review time, resources, and costs associated with that activity. Likewise, the typical way that the assembly worker will interact with OnSite is via a paper traveler with bar coded activities. A user can view the Gantt chart for a worker order, but it is typically a more confusing way to view the same information.
The second type of projects that OnSite handles are those that are less complicated or template driven. Based on our experience, about half of our customers that do these types of projects load them directly in OnSite and about half import them to OnSite from an integrated project planning system. Example projects that can be categorized into this view include projects such as job shop manufacturing, or mid-size construction projects such as building a short street. In these scenarios, you’ll have more specific resource assignments and you’ll be reviewing dependencies in a different light. Project managers will most likely review these types of projects using both the list and the Gantt views in OnSite, and will more heavily utilize practical project management practices.
OnSite has also been developed with a third perspective for those projects that are highly complex, custom, and dependency driven. For our customers, these types of projects are always managed in a specialized project planning package that is integrated to OnSite. Essentially, in these cases OnSite extracts the data field and record set and operates as a mirror of the project planning package with only that information that is important for employees to perform and record the work exposed. OnSite then packages the data and synchronizes current performance, cost, and status with the project planning package.
While the project management engine in OnSite is the same engine in all three cases, the use and application differs based on customer needs and operations. Providing the flexibility to address a wide spectrum of project experience not only enables our customers current project set, but provides a blend of functionality should their project set evolve.
Work Orders Screenshot
Gantt Chart Screenshot
