Skip to main content Accessibility help
×
Hostname: page-component-78c5997874-fbnjt Total loading time: 0 Render date: 2024-11-10T02:23:57.930Z Has data issue: false hasContentIssue false

3 - Organization of engineering tasks

Published online by Cambridge University Press:  05 April 2014

Stephen Armstrong
Affiliation:
AMGI-Bywater Management Consultants and University of Toronto
Get access

Summary

This chapter explains the organization of tasks using workplan templates within the task guidelines (see Section 6.2). Within this structure, you will be able to see how a task fits with your program plan and to know how to find detailed information about it.

Tasks depend upon two other elements – resources and schedule. Understanding the resources required to perform a task and the schedule within which the task must fit allows us to manage costs effectively. All three elements must be managed in concert with one another. A change in one element has an impact on the others. Prior to a formal process management, these elements, in many organizations, were managed independently. This imbalance would lead frequently to internal power struggles. Functional directors would assign resources as they saw fit without a view of the impact on other tasks within the integrated master schedule.

Tasks are always organized into the processes that define the business process framework, and processes overlap phases. In addition, developing reference manuals that capture the knowledge you gained on previous programs and that document new or established approaches offers tremendous benefits. They describe the worksteps of howto carry out a task, including technical rules. The documentation of these rules allows the organization to “learn.” The process of maintaining design rules lends itself well to intranet application because it allows distributed access to all members of the collaborative project. Further, an intranet permits ease of update and version control. (See Chapter 11 on utilizing product data management.)

Type
Chapter
Information
Engineering and Product Development Management
The Holistic Approach
, pp. 42 - 48
Publisher: Cambridge University Press
Print publication year: 2001

Access options

Get access to the full version of this content by using one of the access options below. (Log in options will check for institutional or personal access. Content may require purchase if you do not have access.)

Save book to Kindle

To save this book to your Kindle, first ensure [email protected] is added to your Approved Personal Document E-mail List under your Personal Document Settings on the Manage Your Content and Devices page of your Amazon account. Then enter the ‘name’ part of your Kindle email address below. Find out more about saving to your Kindle.

Note you can select to save to either the @free.kindle.com or @kindle.com variations. ‘@free.kindle.com’ emails are free but can only be saved to your device when it is connected to wi-fi. ‘@kindle.com’ emails can be delivered even when you are not connected to wi-fi, but note that service fees apply.

Find out more about the Kindle Personal Document Service.

Available formats
×

Save book to Dropbox

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Dropbox.

Available formats
×

Save book to Google Drive

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Google Drive.

Available formats
×