Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Development Studio

Teamwork Overview

  • Last UpdatedOct 06, 2025
  • 2 minute read

AVEVA Teamwork is a cloud-based, integrated business continuity platform for knowledge management, skill management and communication for your factory and its workers. It provides a structured, hierarchical model for organizing plant assets and supporting collaboration across teams.

With Development Studio, you can build a Teamwork model using your System Platform configuration model as a source.

Teamwork allows you to:

  • Organize plant assets using a fixed five-level hierarchy.

  • Map areas and assets from the source model to create a new Plant, Production Line, Workstation, or Equipment in Development Studio.

  • Edit, publish, and update your Teamwork model, with each publish tracked by a report.

  • Manage changes over time by switching versions.

Teamwork Hierarchy

Teamwork uses a fixed five-level hierarchy:

  • Division: Highest level in the Teamwork hierarchy. Used to group one or more plants, often for regional or product-type organization. Division names must be unique across the Teamwork server.

  • Plant: Contains one or more production lines and forms the base location for employees. Each user is assigned a home plant. Plant names must be unique across the Teamwork server.

  • Production Line: Contains one or more workstations. Represents functions within a plant.

  • Workstation: Contains one more more equipment items managed by an operator. Used to represent subdivisions of a line based on process steps or sectors.

  • Equipment: The most detailed level within the hierarchy. Represents a single machine or tool. Does not include small items like valves or pumps.

    Note: Teamwork administrators can rename these levels, but Development Studio always refers to them by their original names.

Restrictions and Rationale

  • Development Studio follows a fixed five-level hierarchy to stay consistent with Teamwork’s structure.

  • Division cannot be mapped to an asset or area.

  • Development Studio ignores any custom names set in Teamwork and always refers to the original level names.

Teamwork Workflow

The workflow for Teamwork integration is:

  1. Configure Teamwork: Configure Teamwork server URL and a Teamwork API key in Development Studio. For more information, see Configure AVEVA Teamwork.

  2. Create and map model: Use the editor to map assets or areas to Teamwork levels in Development Studio. For more information, see Create and map model

  3. Publish: Publish your model to AVEVA Teamwork server. For more information, see Publish to Teamwork

  4. View Report: Review the publish report for success, errors, and audit details. For more information, see View publish report

  5. Make Changes: Edit your model as needed.

  6. Publish and View Report: Re-publish and verify updates.

    Note: Only users with the Teamwork Publisher role can publish to Teamwork.

TitleResults for “How to create a CRG?”Also Available in