PROTAP Project tasks planning

TBG6 Architecture, Engineering and Construction

The Project Tasks Planning message is used in various industry sectors when there is a requirement for all parties involved to formally establish and exchange planning and scheduling information. This information describes the tasks and resources needed to complete a project or provide a service. This can include such details as what activities or tasks are involved, who is available to do the work, who is doing the work, what must be completed or delivered such as a document or goods, and when the work will be completed or when the item will be delivered. This document may be part of the contractual documents exchanged for the preparation, status, or completion of a project or service.

Send feedback Share via email

Header

Position
Segment
Name
Max use

  1. A service segment starting and uniquely identifying a message. The message type code for the Project tasks planning message is PROTAP. Note: Project tasks planning messages conforming to this document must contain the following data in segment UNH, composite S009: Data element 0065 PROTAP 0052 D 0054 17B 0051 UN

  2. A segment to identify a single planning or scheduling reporting document, its unique identifier, and specific message function.

  3. A segment to identify the report detail type such as network logic, barchart, milestone, line of balance, or task list type of information.

  4. A segment to identify the message preparation, effective, and project baseline processing date information.

  5. Segment group 1
    Repeat 99

    1. A segment to identify references related to the plan or schedule such as a project, program, contract, contract addendum, Request for Quote, or Request for Proposal number.

    2. A segment to provide a description such as the name of the program for any reference number or program.

    3. A segment to provide a structured index number for any reference number, project, plan, or schedule.

    4. Segment group 2
      Repeat 99

      1. A segment to identify related or linked project, plan, or schedule identity numbers.

      2. A segment to identify the type of relationship such as a parent, child, or peer (internal or external to the project).

  6. Segment group 3
    Repeat 99

    1. A segment to provide message sender and receiver information.

    2. A segment to provide address information for each named party.

    3. A segment to provide a structured index number associated with each named party.

    4. Segment group 4
      Repeat 9

      1. A segment to provide a contact person's name for each named party.

      2. A segment to identify the phone number, fax number, e-mail, or other communication number for the contact party.

    5. Segment group 5
      Repeat 9

      1. A segment to describe the data processing environment such as the software application name, version and release.

      2. A segment to provide the effective, processing, or other date stamp for the named software application.

  7. Segment group 6
    Repeat 99

    1. A segment to identify a related file and provide details such as the file name, file format, version, and data format.

    2. A segment to describe the data processing environment used to create the named file such as the name of the software application, version and release.

    3. A segment to provide the created, effective, processing, or other date stamp for the named file.

  8. Segment group 7
    Repeat 999

    1. A segment to identify what the index applies to, such as the entire project or part of a project. Used to indicate whether IND and related segments describes the index structure or describes the index contents. When used to describe a structure, the segment is also used to indicate the structure hierarchical level.

    2. A segment to identify a structured index number definition or contents.

    3. A segment to provide a description for the structured index number definition or contents.

    4. A segment to identify an action (add, change, or delete) for the index data.

  9. Segment group 8
    Repeat 9999

    1. A segment to identify the resource and related action code (add, change, or delete).

    2. A segment to identify any structured index numbers for the resources that are related to the project such as billing or trade skill categories.

    3. A segment to provide reference numbers for the resource such as a working calendar number, charge number or organization code.

    4. A segment to provide a description of the resource or type of resource such as labor or material in clear or coded form.

    5. A segment to provide start and end dates related to the resource.

    6. Segment group 9
      Repeat 99

      1. A segment to identify the quantity of available resources and associated unit of measure such as hours or days the resource is available.

      2. A segment to identify the effective date, or start and end dates for the resource quantity.

    7. Segment group 10
      Repeat 99

      1. A segment to identify the resource unit price.

      2. A segment to identify the effective date, or start and end dates for the resource unit price.

    8. Segment group 11
      Repeat 99

      1. A segment to identify the percentage of availability or efficiency factor for the resource; also used to identify any escalation or inflation percentages.

      2. A segment to identify the effective date, or start and end dates for the resource availability, efficiency, or escalation percentage.

    9. Segment group 12
      Repeat 99

      1. A segment to provide the rate per unit such as a rate per hour for the resource.

      2. A segment to identify the effective date, or start and end dates for the resource rate per unit.

    10. Segment group 13
      Repeat 99

      1. A segment to identify a monetary amount for the resource.

      2. A segment to identify the effective date, or start and end dates for the resource monetary amount.

Detail

Position
Segment
Name
Max use

  1. A mandatory service segment placed before the first user segment in the detail section to avoid segment collision.

  2. Segment group 14
    Repeat 99

    1. A segment to provide the reference used to identify a given calendar.

    2. Segment group 15
      Repeat 999

      1. A segment to provide details about a calendar work period pattern such as Monday through Friday.

      2. A segment to identify the quantity of working time units per day, quantity of working shifts per day, or quantity of working time units per shift for a given calendar.

      3. A segment to provide precise date details about a given calendar such as specific non-working or holiday dates.

  3. Segment group 16
    Repeat 9999

    1. A segment to identify the task, indicate if it is an activity or milestone event, provide an action code (add, change, delete), and provide a schedule level reference.

    2. A segment to provide a work status indicator (work has begun or work has been completed) for the task.

    3. A segment to identify any structured index numbers such as a bill of materials or work breakdown structure for the task.

    4. A segment to provide reference numbers associated with the line item (task) such as charge numbers, cost accounts, statement of work numbers, and calendar or work shift references.

    5. A segment to provide a description of the task.

    6. A segment to provide the party name of a work team for a given line item (task).

    7. A segment to provide information about a product or assembly associated with a given line item (task).

    8. A segment to provide planned start and finish dates, target dates, actual start and finish dates, estimate start and finish dates, and other related dates for the line item (task).

    9. A segment to provide additional text for the line item (task). Can be used to provide additional details about the task, events surrounding the task such as an explanation for a behind schedule over cost situation, or further explanation about data associated with the task.

    10. Segment group 17
      Repeat 9

      1. A segment to provide a responsible person's name for the line item (task).

      2. A segment to identify the phone number, fax number, e-mail, or other communication number of the responsible person for the line item (task).

    11. Segment group 18
      Repeat 99

      1. A segment to provide the unit of measure (such as hours) and quantities (such as budget, actual, or earned) associated with a line item (task). Also used to provide the duration of the task when expressed as a quantity of time units such as 10 working days; lead time duration such as a lead of 5 working days is required before the next task can start; and progress information such as a remaining duration of 5 working days.

      2. A segment to provide a single pair of start and end dates or a series of start and end dates (for example, to describe monthly allocations) associated with hour quantities (budget, actual, earned value) for the task.

    12. Segment group 19
      Repeat 99

      1. A segment to provide the percent complete for the line item (task).

      2. A segment to provide effective, or start and end dates for the percent complete for the task.

    13. Segment group 20
      Repeat 99

      1. A segment to provide monetary amounts (such as budget, actual, or earned value costs) for the line item (task).

      2. A segment to provide a single pair of start and end dates or a series of start and end dates (for example, to describe costs broken down by month) monetary amounts for the task.

    14. Segment group 21
      Repeat 9999

      1. A segment to identify a related constraint activity, interface activity, assigned resource, or milestone event (when the line item is an activity). For constraint activities, also used to indicate if the cited constraint activity is a predecessor or successor. For milestone events associated with a task, also used to provide a work status indicator (work has begun, work has been completed, or the milestone event has been revised).

      2. A segment to identify the type of relationship. Used for constraint type of activities to describe finish to start, start to start, start to finish, and finish to finish types of relationships.

      3. A segment to identify an action (add, change, or delete) for the interface activity, constraint activity, assigned resource, or milestone event.

      4. A segment to identify any structured index numbers such an organization breakdown structure, or trade skill for an assigned resource.

      5. A segment to provide reference numbers associated with the interface activity, constraint activity, assigned resource, or milestone event such as a calendar or shift, department, work package, charge number, or work order number.

      6. A segment to provide a description of the interface activity, constraint activity, assigned resource, or milestone event. When an assigned resource, can also use this segment to indicate the type of resource in coded form (such as a consumable, recurring, or non-recurring resource).

      7. A segment to provide start and finish dates, actual start and finish dates, scheduled start and finish dates, planned or revised dates for assigned resources or milestones.

      8. Segment group 22
        Repeat 99

        1. A segment to provide quantity information about the interface activity, constraint activity, assigned resource, or milestone event. For activities, used to provide the duration of lead or lag time when expressed as quantities of time units. For assigned resources, can be used to indicate the number of resources available for the task (level per calendar unit or total for the duration of the task). For assigned resources and milestone events, can be used to provide associated budget, actual, or earned value hour quantities.

        2. A segment to provide an effective date, a pair of start and end dates, or a series of start and end dates associated with an interface activity, constraint activity, assigned resource, or milestone quantity.

      9. Segment group 23
        Repeat 99

        1. A segment to provide availability or efficiency factors for an assigned resource or to provide an earned value percentage for a given milestone (used to calculate the amount of value earned when a milestone is complete).

        2. A segment to provide an effective date, or start and end dates associated with the availability, efficiency, or earned value percentage.

      10. Segment group 24
        Repeat 99

        1. A segment to provide monetary amounts (such as budget, actual, or earned value) for the assigned resource or milestone event.

        2. A segment to provide an effective date, a pair of start and finish dates, or a series of start and finish dates associated with the budget, actual, or earned value monetary amount for the assigned resource or milestone event.

      11. Segment group 25
        Repeat 99

        1. A segment to identify a rate for the assigned resource.

        2. A segment to provide the effective date, or start and end dates for the assigned resource rate.

Summary

Position
Segment
Name
Max use

  1. A segment to provide control totals for the message such as the total number of activities, milestones, resources, or constraints.

  2. A service segment ending a message, giving the total number of segments in the message (including the UNH & UNT) and the control reference number of the message.

    1. 0062, the value shall be identical to the value in 0062 in the
    corresponding UNH segment.
Stedi.comDocumentationContact us

Stedi is a registered trademark of Stedi, Inc. Stedi's EDI Reference is provided for marketing purposes and is free of charge. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.