PRIDE ® -EEM
Enterprise Engineering Methodology
PHASE 3 - PHYSICAL ENTERPRISE ANALYSIS
ACTIVITY C - PREPARE POSITION MODEL

EXAMPLES   TOOLS & TECHNIQUES   FUNCTIONAL MATRIX   CHECKLIST   SUPPORT   FORMS

TRANSLATE THIS PAGE TO... Chinese (simple)   Japanese       Dutch   French     German     Italian    
Free Translation courtesy of ALS      Chinese (traditional)   Korean       Portuguese       Russian       Spanish         

CONTENTS

This section contains the following:


 
    BUSINESS PURPOSE

    The purpose of this activity is to define and/or modify as required the physical model of the enterprise, in part or in full. Depending on the scope of the project, this activity may be used to define or modify the entire enterprise or for a single area within it (e.g., Marketing, Administration, Manufacturing).  

    OVERVIEW

    POSITION DESCRIPTIONS

    During this activity, Position Descriptions are prepared and/or refined as required. Although companies may use various techniques for preparing a job description, it should at least contain the following elements:

    • SCOPE OF WORK - Stating the primary and, where applicable, secondary objectives of the position.

    • DUTIES AND RESPONSIBILITIES - A listing of the specific actions and/or decisions to be performed.

    • REQUIRED KNOWLEDGE/SKILLS/EXPERIENCE - Establishing the criteria for resources to effectively perform the work.

    • EVALUATION OF PERFORMANCE - Establishing the criteria for evaluating how a resource performs the position.

    Although Enterprise Engineering has the responsibility for the preparation of Position Descriptions, it is not unusual for others to prepare them; e.g., User Management, Personnel Administration, Human Resource Management.

    PREPARING THE PHYSICAL MODEL

    Contrary to the logical model of the enterprise, which is structured in a specific manner, the physical model may be structured many ways. Whereas functions are used to provide a generic description of the enterprise, positions are used to show how the enterprise actually works, and the two models will not necessarily match. For example, one function may be implemented by multiple positions; and one position may implement many functions.

    The physical structure of the enterprise is based on how management wishes to organize and operate the enterprise. It represents administrative reporting with levels of authority. Ultimately, it depicts the "chain of command" for an enterprise.

    The enterprise may have evolved into an elaborate organization structure with many layers of management, or it may be very "flat" with few levels of reporting. One structure is not necessarily better than another (although there are some good arguments for flattening the organization). What is important is that the enterprise be structured in the most productive means possible.

    REPRESENTING RELATIONSHIPS

    EEM does not mandate any particular organizational structure; any can be represented. To do so, certain resource relationships must be observed in the IRM:

    • DIRECT/DOTTED RELATIONSHIPS - This denotes the administrative reporting relationship. Direct means that one job is under the direct administrative authority of another. A dotted relation represents an indirect authority. One example of "dotted" is where an outside consultant is contracted to perform a job, such as a lawyer, accountant, programmer, etc.

      • For physical positions (OE resources), the "direct" relationship is used to denote administrative reporting. "Dotted" refers to a temporary or external job subordinate to a parent position. The result is a hierarchy showing superior/subordinate/lateral relationships. Consult the "Organizational Resource Relationships" below for additional details.

    • LINE/STAFF RELATIONSHIPS - This is used to describe the role a position (OE) plays in an organization. "Line" refers to a job that has the responsibility for performing the principal work effort. "Staff" refers to a job that supports another position. For example, secretarial and clerical positions are often used to expedite or provide assistance for other jobs.

    The following "Organizational Resource Relationships" Chart shows the types of relationships between all of the organization resources.

    ORGANIZATIONAL RESOURCE RELATIONSHIPS

    -------------- | SKILL | | (SD) | -------------- A A Many-to-Many | Relationship V V -------------- -------------- | FUNCTION | Many-to-Many | ENTERPRISE | | (FE) |<<------------------------------->>| (FE) | -------------- -------------- D A i L A r i | Many-to-Many e n | Relationship c e V t V -------------- Direct or Dotted -------------- | POSITION | Line or Staff | POSITION | | (OE) |<-------------------------------->>| (OE) | -------------- One-to-Many -------------- D A Relationship i L | r i | e n | c e V t V -------------- A Human Resource (RE) may report | RESOURCE | administratively (directly) to only | (RE) | one position. -------------- A A | V V -------------- | SKILL | | (SD) | -------------- NOTE: Arrows represent one (<) or many (<<) relationships.

    MACHINE RESOURCES

    Defining human resources is a relatively simple task in comparison to defining machine resources. Quite often a company is unaware of all of the equipment at their disposal and how it is applied.

    Machines such as computers, robots, and other equipment should be identified as machine resources (RE) and cross-referenced as a "dotted/line" relationship to the positions they support (OE to RE). In addition, their particular skills and proficiencies should be noted. For example, a computer can have the skill of "Transaction Processing"; its proficiency may be based on how fast it can process transactions.

    One of the benefits from cataloging machine resources is that equipment utilization can be inventoried and monitored.  

    STEPS IN EXECUTION

    1. Enterprise Engineering prepares and/or modifies as required descriptions about human and machine resources. Pertinent skills are attached to each resource. From this, Human/Machine Resource Profiles and a Resource/Skill Matrix is prepared.

    2. Enterprise Engineering prepares and/or modifies as required Position Descriptions. These descriptions are written in accordance with installation standards.

    3. Enterprise Engineering establishes the administrative and indirect relationships between positions and resources. This includes "direct/dotted" and "staff/line" relationships. From this, an Organization Chart is prepared showing the administrative reporting relationships of the enterprise.

    4. Enterprise Engineering cross-references the positions (OE's) to the logical functions (FE) they support.

    5. Enterprise Engineering reviews the documentation with Quality Assurance for adherence to standards. Adjustments are made as required.

    6. Enterprise Engineering reviews the documentation with User Management for accuracy. Adjustments are made as required.

  


Copyright © 1971-2009 by M. Bryce & Associates
Palm Harbor, Florida, USA
All rights reserved.