Project Definition PMO
Brian logs in to the internet portal. He kicks off the project, by adding and defining the new project. He attaches a draft CAD design and an E-Mail from Alan, the senior manager, as the information is automatically passed on to the next person in charge.
Erick Souza attaches the related norms, the specs book, and a first general CAD design, before approving the project.
Damon Bradley is at the airport when he receives a text message that alerts him of a new task. He accesses his portal through his Smartphone and realizes that this project is quite similar to what he worked on in the past. Using the Content Management tool, he finds the information from the previous project and attaches it with the new one.
Charles White calculates the budget of the Pump House Project and attaches it after approving the project.
Distribution of Projects - Board of Engineers
Frank Wilson provides the Electrical installation Specifications. Elen Ford provides the mechanical Specifications. Geena Smith provides the Civil Specifications.
In this case three steps are portrayed by one icon to simplify the look of the workflow. Each icon could present a whole independent workflow.
Project Outsourcing - Suppliers
After sending in his first proposal Greg Hilson, the engineer of a supplier, receives comments from the Board of Engineers. To make the necessary changes to the CAD design he has to “check out” out the form, for security and convenience purposes. After making the necessary changes to the CAD design and the invoice he checks the forms back in.
Projects Approval - Board of Engineers
Frank, Elen and Geena receives the designs for final approval.
A great feature about Lab245 is that it encourages proper indexing of documents as we have seen throughout this project. Once a project is approved it is very easy to archive final documents. NOTE: Not only content or information will be archived, but also workflow processes. Also, each user’s steps can be retraced for regulatory purposes.
Construction - Construction Staff
Alan Silva receives the final project to proceed to execution. In this case this could lead to a new workflow process that manages the execution of the Pump House Facility.
Brian checks on the progress of the Pump House Project using the Graphics Analysis feature. This tool also allows users to create graphical reports and track the progress of the project. Brian realizes that the “Environmental Approval” step is taking too much time and has created a bottleneck.
Brian goes back to the IT department to streamline the current workflow. By rearranging the current process they get rid of the bottleneck to save project time.
The following scenario is simplified for the purpose showcasing Lab245’s capabilities and features. There are no boundaries as to the complexity or purpose of processes that can be managed using our solution. While this is a scenario for a company in the Oil&Gas industry, we have successfully implemented Lab245 in a variety of industries including Pharmaceutical, Banking, and Chemical.
SCENARIO: Brian Smith is the manager of a field engineering group. He receives a request to build a Pump House Facility for the new exploration plant in the Amazon Rainforest. Brian thinks about all the people involved in the process and all the information they will need for the project’s final approval:
As Brian has already a project plan created in MS Project he import data to Folder245FlowBuilder.
Project Management Office (PMO):
1) Charles White will provide the Budget Limit.
2) Erik Souza attaches related norms, Specifications book, and first CAD Design.
3) Damon Bradley will gather environmental aspects and analyze its impacts.
4) Frank Wilson will provide Electric Specifications.
5) Elen Ford provides Mechanical Specifications.
6) Geena Smith provides Civil Specification.s
7) Ed Chapman, Engineer from a Supplier, receives the requests and provides project designs.
8) Greg Hilson, Engineer from another supplier, receives the requests and provides project designs.
9) Frank, Elen, Geena, make final approval on the project.
10) Alan Silva receives final project ready for execution.
With this plan Brian goes to the IT department and together they develop a workflow using our Folder245FlowBuilder. Once a workflow process is developed it is archived for future use, saving time in re-work. For this scenario we assume that this is the first such process and we need to build it from scratch.