Skip Headers

Agile Product Lifecycle Management Product Collaboration User Guide Release 9.3.3 E39292-01 |
| Contents

Previous | Next |

# 3 Sites and Distributed Manufacturing

Note: For information about implementing and configuring Agile multi-site manufacturing, see Administrator Guide.

## 3.1 What is Agile Distributed Manufacturing?

When the Agile administrator enables the Agile PLM Sites license, the Agile Site object is available and Agile PLM multi-site manufacturing functions become available. Agile multi-site manufacturing capabilities are used to assist a company that builds its products in multiple locations (distributed manufacturing). Before taking this step, you must determine and plan how Agile PLM multi-site manufacturing will be integrated with your ERP system.

WARNING: Agile PLM multi-site manufacturing functionality is built differently than ERP sites or organizations. Agile Site objects and ERP sites or organizations are similar, but they are not identical. You should work with an Oracle Consulting - Agile practice representative to plan your Agile PLM to ERP integration before you enable the Agile Sites license. The type of information that you want to track in Agile PLM and how you choose record that information in Agile PLM may depend on how product information is stored in your ERP system.

Agile multi-site manufacturing helps a company that builds its products in multiple locations to do so by enabling parts and documents in those locations that are specific to the manufacturing process. In Agile PLM, revisions are global item attributes. If a part is used in two manufacturing sites, then it must share the revision level, although the effectivity dates and disposition settings can be different.

The Agile multi-site manufacturing features allow you to annotate product data with three types of site relationships:

- Item object-to-Site relationship

An item can be associated with one or more sites by adding the site object to the sites table on the item Sites tab. Item-site relationships are similar, but not identical to ERP item-site relationships. You can see if an Agile part is enabled in any sites by viewing its Sites tab.

- Parts that are not released in any site have only global item effectivity dates and dispositions.

- Parts released in sites can have both site-specific item effectivity dates and dispositions and global item effectivity dates and dispositions.

- BOM row-to-Site relationship

BOM row-site relationships are unique to Agile PLM. A child part can relate to its parent with no site relationship or through one or more specific sites. Each BOM row has either no site relationship or one site relationship. Use multiple rows, one for each site, to represent more than one site relationship for the same child part.

- A child part that reports to its parent without a specific BOM row-site relationship is considered a common part, that is, a part common to all manufacturing sites.

- A child part that reports to its parent with a BOM row-site relationship is a site-specific part, that is, a part that is specific to the related manufacturing site.

- AML table row-to-Site relationship

On the Manufacturers tab of a part, you can specify site-specific AMLs (Approved Manufacturer List). Rows on the part manufacturer table can be common (specify no site) or a site-specific (associated with a site listed on the Sites tab of the part). BOM row-site relationships and AML row-site relationships are independent of one another.

- A manufacturer part without a specific AML row-to-site relationship is a common manufacturer part and can be used at any manufacturing site.

- A manufacturer part with an AML row-to-site relationship is a site-specific manufacturer part, which allows the manufacturer part to be used at the specified manufacturing site.

Other important Agile PLM sites and ERP sites differences to keep in mind:

- In many ERP systems, a part can appear in different sites and have independent revisions. Agile PLM considers the revision to be a global attribute of the part. Therefore, site-based revisions are not supported in Agile PLM. To accommodate this need, simply prefix or suffix the part number with a unique string, for example SJC-P1000 and NYC-P100. These are unique parts which have global revision, but because these parts aren't used in other sites their revisions appear to be site-specific.

- The item-site relationship and the BOM row-site relationship are independent of one another in that you can add a part to a BOM as a site-specific BOM row without first adding the site to the part. Unlike typical ERP systems, Agile does not require that a part must first be released in a site before it can be added to a site-specific BOM row.

- When adding a row to a BOM where the parent has sites that are not on the child, Agile PLM prompts the user to add the sites to the child. This occurs only on the initial add of the BOM row - either in authoring mode (direct editing of a part) or in redlining mode (modifying a part through change redline). The user can choose only to Copy the sites onto the child in order to add the row to the BOM. Choosing Close will not add the BOM row. If additional sites are subsequently added to the parent, then the newly added sites are not automatically copied to the child. If sites are removed from the child, then no check is made on whether there is inconsistency between sites on the parent and the child.

- The SmartRule Child Released First is enforced by the Release Audit when a part is released. When a parent part is released, this rule checks the BOM components for site association and whether the BOM components are also released. The Release Audit verifies whether or not the item has been released by a Change or Manufacturer Change after a site was added. In order to correctly pass this SmartRule, the item must be released after adding a site.

## 3.2 What Are Sites?

In Agile PLM, site objects represent manufacturing sites. Companies that practice distributed manufacturing use several different manufacturing sites for their products. For example, Widget Corporation manufactures its products at the corporate location in Austin, Texas, but also at manufacturing plants in Taiwan, Singapore, Mexico City, and Milpitas, California.

Site objects ensure that each ERP has only the relevant information for its production needs. For example, companies can manage what is sent to each internal ERP site or contractor in a Make vs. Buy site association.

Site objects help ease the production transfer from one manufacturing site to another. For example, the Widget Corporation can transfer an entire product from their Taiwan prototype site to their Mexico City production site by adding the production site association to all the parts in the Taiwan BOM that are not in the Mexico City BOM, and then send the BOM to Mexico City through an engineering change order (ECO) or a site change order (SCO).

Site objects also help to formalize the site effectivity process by allowing a user to create a proposed effectivity date change (SCO) against a part revision. For example, if a site production date has to be changed to a later date, then an SCO against the part provides a simple record of approvals and reasons for changing the effective date.

The following diagram illustrates how sites can be used in Agile PLM. The three sites in this diagram vary in ERP system, effectivity date, and manufacturer. Also, Site 3 has added site-specific build instructions.

## 3.3 How Sites Can Be Used

You can use sites to record and manage site-specific AMLs, BOMs, and effectivity dates.

This section includes the topics:

- Different AMLs at Each Site on page 32.

- Different BOMs at Each Site on page 32.

- Different Effectivity Dates and Dispositions at Each Site on page 33.

### 3.3.1 Different AMLs at Each Site

Often, different sites use different manufacturers and manufacturer parts to build the same products. Reasons for the differences could be cost (for example, it may be more cost-effective for a site to use a nearby manufacturer) or status of a manufacturer, to name two examples. The AML for an assembly can include different manufacturer parts for the various manufacturing sites.

See also: How Sites Work on page 33.

### 3.3.2 Different BOMs at Each Site

The BOM of an assembly can include items that pertain only to specific sites. The common BOM lists all items that make up the core assembly, and that BOM is the same for all sites. However, the appropriate users assigned to each manufacturing site can add site-specific items to the BOM (thus creating a site-specific portion of the BOM). Often, these additional items are documents, such as assembly instructions specific to how something is built at a site.

See also: How Sites Work on page 33.

### 3.3.3 Different Effectivity Dates and Dispositions at Each Site

Items may have different effectivity dates and dispositions at each site. This enables, for example, the Austin site to begin using revision B of an item while Singapore continues to use revision A until stock has run out.

Effectivity dates and dispositions are specified on the Affected Items tab of an ECO or an SCO. If you want to create a new revision when you assign the new effectivity date or disposition, then use an ECO. To assign site-specific effectivity dates and dispositions without incrementing the revision, use an SCO.

See also: How Sites Work on page 33.

## 3.4 How Sites Work

Site objects, similar to manufacturer objects, hold information about each site. Users with appropriate privileges can create additional sites.

This section includes the topics:

- Site Information on BOMs and AMLs on page 33.

- Sites Tab of Items on page 33.

- Changes and Sites on page 33.

- Controlling Access to Sites on page 33.

- Common BOM/AML Sections on page 33.

### 3.4.1 Site Information on BOMs and AMLs

When you view an item's BOM or AML (Manufacturers tab), you can choose to view it for all sites or for a specific site. When you view the BOM or AML for a specific site, the common BOM or AML is included in the list.

See also: How Sites Work on page 33, Viewing BOMs by Site on page 79, Viewing AML Information by Site on page 61.

### 3.4.2 Sites Tab of Items

Each item includes a Sites tab. The Sites tab lists the sites where that item can be used. If a site is not listed on an item's Sites tab, then that item cannot be included in the portion of a BOM specific to that site. If all the sites of the parent BOM are not listed on an item's Sites tab, then that item cannot be included in the common portion of a BOM. For a detailed explanation, see Common BOM/AML Sections on page 33.

See also: How Sites Work on page 33, How Sites Can Be Used on page 32.

### 3.4.3 Changes and Sites

Changes can affect all sites of an item or a specific site. The Affected Items tab lets you select sites to affect as you add affected items. Use site change orders (SCOs) to create site-specific changes to an item without changing the revision.

See also: How Sites Work on page 33, Changes and Manufacturing Sites on page 166, Site Change Orders on page 167.

### 3.4.4 Controlling Access to Sites

The use of sites is controlled by:

- Your organization's enabled licenses.

- Your assigned roles and privileges.

- Your assigned Sites property in your user profile.

- Your assigned Default Site property in your user profile determines which site you see by default.

You can create as many sites as you want.

Your organization may have implemented sites in such a way that users can access only the information pertaining to certain sites.

Your user profile Sites list controls which site objects you can discover in the Agile database and which item site-related rows (BOM tab, Manufacturers tab) you can discover. The ability to read site object attributes is controlled by your Read privileges.

Users with Administrator privilege have the ability to assign all sites when modifying a user's User Profile attributes. However, when searching for sites in Web Client or Java Client, the Administrator user can discover only the sites listed in the Sites list of his own User Profile.

See also: How Sites Can Be Used on page 32, How Sites Work on page 33.

### 3.4.5 Common BOM/AML Sections

The common section of the BOM distinguishes information that is shared between all the sites listed on the Sites tab of the item. All the parts in the common section of the BOM of an assembly must have listed on their Sites tabs all the sites that are listed on the Sites tab of the assembly. That is, they have those sites in common.

For example, if part 300 is to appear on the Milpitas-specific portion of the BOM of assembly 234, then part 300 and assembly 234 must both have the Milpitas site listed on their Sites tabs. If assembly 234 has three sites (Milpitas, India, and San Jose) on its Sites tab, for part 300 to appear on the common portion of the BOM of assembly 234, then part 300 must also have at least those three sites (Milpitas, India, and San Jose) included on its Sites tab. That is, they must have those sites in common. (Part 300's Sites tab may also include additional sites that do not relate to assembly 234.) A SmartRule (Items Released First) controls whether Agile checks an item's BOM components for the appropriate site association at release. Compliance with the SmartRule is checked when an ECO, SCO, or MCO releases the assembly. You can also use the change Audit Release feature to check for compliance before release.

See also: Creating a Common BOM on page 6, Creating a Site-Specific BOM on page 6.

## 3.5 Where Sites Are Documented

You can find information about sites in the following sections:

Topic | Section or chapter
--- | ---
Site objects | This chapter
Sites tab of items | This chapter and Chapter 1, Items on page 1
Viewing site-specific information | The following chapters: Chapter 1, Items on page 1 Chapter 4, Bills of Material on page 73 Chapter 6, Affected Items of Changes on page 175 Chapter 3, Manufacturing Objects on page 45
Site-specific BOMs | Chapter 4, Bills of Material on page 73
Site-specific AMLs | Chapter 3, Manufacturing Objects on page 45
SCOs | Chapter 5, Changes on page 151, and Chapter 6, Affected Items of Changes on page 175
Effects of changes on sites | Chapter 5, Changes on page 151, and Chapter 6, Affected Items of Changes on page 175
Redlining site-specific information | Chapter 6, Affected Items of Changes on page 175
Site-specific effectivity dates and dispositions | Chapter 6, Affected Items of Changes on page 175

## 3.6 Site Objects

A site object contains general information about a site. Unlike items, sites do not need to go through a release process.

This section includes the following topics:

- General Info Tab - Sites on page 36

- Attachments Tab on page 38

- History Tab on page 38

To locate and open a site object, follow the instructions in Getting Started with Agile PLM.

The following table lists the tabs for sites.

The Agile administrator may have added additional sections to the Title Block or General Information tab, called Page Two and Page Three by default (Web Client). In Java Client, these are separate tabs. These sections or tabs contain custom fields defined by the administrator.

Site tab name | Tab information includes
--- | ---
General Info | General information about the site
Attachments | Attached drawings, files, and URLs pertaining to the site
History | Actions taken on the site, for example, when attachments were added and removed

### 3.6.1 General Info Tab - Sites

The General Info tab has fields that contain basic information about a site. Some fields are filled in automatically and you complete the rest. You may not be able to edit the content of some fields.

This section includes the following topics:

- General Info Tab Fields - Sites on page 36

- Site Lifecycle Phase on page 37

- AML Required on Buy Field on page 37

- Site AML Allowed Field on page 38

#### 3.6.1.1 General Info Tab Fields - Sites

By default, the site object General Info tab contains the fields listed in the following table.

Field | Definition
--- | ---
Name | The name of the site. This field must be filled in with a unique value.
Type | The subclass (type) of the site object.
Lifecycle Phase | The current state of the site: Enabled or Disabled.
Site ERP Code | The ERP system in use at the site, if applicable.
Address, Geography, Province/Region/State, Country/Area, City, Postal Code, Phone, URL, Fax, | Contact information for the site.
Contact | The name of the contact person for the site.
Email | The email address of the contact person.
Buyer | The buyer code for the item at this site. Select one from a list of codes that have been assigned for sites.
Planner | The planner code for the item at this site. Select one from a list of codes that have been assigned for sites.
Color | The color associated with this site. Choose from a list of colors. This color will be used on the BOM, Manufacturers, and Affected Items tabs to distinguish common items from site-specific items. The same color can be used for more than one site.
Site AML Allowed | For items specified as Buy, indicates whether a site-specific manufacturer value is required, allowed, or disallowed.
AML Required on Buy | Indicates whether a manufacturer value is required for an item when the item is specified as a Buy (as opposed to a Make) for this site. Whether an item is Buy or Make is shown by the Make/Buy field on the Sites tab of the item.

See also: Site Objects on page 35, Site Lifecycle Phase on page 37, AML Required on Buy Field on page 37, Site AML Allowed Field on page 38.

#### 3.6.1.2 Site Lifecycle Phase

- A site can be in one of the following states, as indicated in the Lifecycle Phase field on the General Info tab of the site:

  - Enabled - When a site is enabled, users can define all site properties of the site itself. Also, users can associate the site with an item, define item-site properties, create site-specific BOMs and AMLs, and create changes for site-specific items.

  - Disabled - All sites are disabled when they are first created. When a site is disabled, users cannot create site-specific BOMs, AMLs, or changes. However, disabled sites are displayed in searches and reports. Any in-process changes that involve a site that has been disabled are allowed to continue through release, but users will not be able to edit the site-specific Affected Item table rows associated with the disabled site, and users cannot make any redline add or redline edit modifications to in-process changes when the site has been disabled.

To change a site's lifecycle phase, select a lifecycle phase from the dropdown list.

See also: General Info Tab Fields - Sites on page 36.

#### 3.6.1.3 AML Required on Buy Field

The AML Required on Buy field of a site determines whether an AML is required for an item when the item is specified as a Buy for a given site.

Note: Whether an item is specified as a Buy is determined by the value in the Make/Buy field on the Sites tab of the item.

When an item is released, the system checks to determine the sites for which the item is being released, as indicated on the Affected Items tab of the releasing change. The system then checks the Make/ Buy field on the item's Sites tab to determine if any of the sites are specified as Buy. If an item is specified as a Make for all sites, then this rule is ignored.

Possible AML Required on Buy values are Yes or No (the default).

- No - Default value. At time of release, the Agile PLM system does not check for whether or not the item has an AML for the site. The item can still be released. However, the Agile PLM system does perform additional checking on the setting of Site AML Allowed property.

- Yes - The item being released must have either a common AML or an AML that is specific to the sites that are specified as Buy sites for the item.

When AML Required on Buy is set to Yes, if an autopromotion attempts to release the item (via a change), but the item does not have a site-specific AML for the appropriate sites, then the promotion fails, and the appropriate person is notified.

See also: General Info Tab Fields - Sites on page 36.

#### 3.6.1.4 Site AML Allowed Field

This field, used when the item is specified as a Buy for a given site, governs whether an AML for an item:

- Must be specific for the site

- Can be modified for a specific site

- Can use only the common site AML

Note: Whether an item is specified as a Buy for a given site is determined by the value in the Make/Buy field on the Sites tab of the item.

When an item is released, the system checks to determine the sites for which the item is being released, as indicated on the Affected Items table of the releasing change. The Site AML Allowed field of the site object is then checked to determine if any of these sites are required or allowed to have a site-specific AML.

Possible Site AML Allowed values are Allowed (the default), Required, and Disallowed:

- Allowed - The item being released is allowed to have a site-specific AML for the site, but it is not required. The item can be released.

- Required - The item being released must have a site-specific AML for the sites specified as Buy sites for the item. The item cannot be released until this condition is satisfied.

If an auto-promotion attempts to release the item (through a change), but the item does not have a site-specific AML for the appropriate sites, then the promotion fails, and the appropriate person is notified.

- Disallowed - The item being released cannot have a site-specific AML for the site. If the item has a site-specific AML, then it cannot be released.

If an autopromotion attempts to release the item (via a change), and the item includes a site-specific AML, then the promotion fails, and the appropriate person is notified.

If a site-specific AML is created for an item (through modification to the AML or redline of the AML), then, when the item is released, the system checks the Site AML Allowed field of the sites to determine if any of the sites have Site AML Allowed set to Disallowed. If a site is disallowed, then you cannot release a site-specific AML for that site.

See also: General Info Tab Fields - Sites on page 36.

### 3.6.2 Attachments Tab

All objects have an Attachments tab. On the Attachments tab, you can attach files and URLs to the object by referencing those files and URLs in a file folder object. On the Attachments tab, you can view, copy (get), or print attached files if you have the appropriate privileges.

Individual attached files are stored in file folder objects and can be attached to multiple objects. The files in a file folder object can be drawings or scanned images, documents, non-viewable files, compressed files, and so on.

For detailed information about working with file folder objects and the Attachments tab, see Getting Started with Agile PLM.

See also: Site Objects on page 35.

### 3.6.3 History Tab

The History tab shows a summary of actions taken against an object, including a description of the action, which user took the action, the date of the action, and other details.

Note: If you do not have the appropriate Read privilege for an object, then you cannot see the contents of the fields on the History tab. See Details about Discovery and Read Privileges on page 237.

The types of actions recorded for sites are:

- Creating the site

- Attachment actions: view, open, add, delete, and get

- Save As

- Send

- Print

- Change subclass

- Modification of any field of a site

See also: Site Objects on page 35.

## 3.7 Creating Sites

The process for creating new objects involves two main steps: creating an empty object, and then filling in the object tabs with information specific to the object.

To create a site, you must have the appropriate Create Site privilege.

In Web Client, you can create a site with the Create New > Sites command or the Actions > Save As command.

In Java Client, you can create a site with the File > New > Sites command or the New Object button , or the Save As command, on the More Actions menu (click the More button at the top of the object window) and on the right-click shortcut menu.

Note: The site name must be unique to a site, just as an item number must be unique to an item.

Choose a color to make it easier to distinguish common items from site-specific items on the BOM, Manufacturers, Changes and Affected Items tabs. In Java Client, the site colors also appear on the item Where Used tab. For more information about site colors, see General Info Tab Fields - Sites on page 36.

When you create a site, you automatically have access to information specific to that site. The new site is included in the Sites field in your user profile.

### 3.7.1 Creating a Site Using the Save As Feature

Using the Save As feature is a quick way to create a site that is similar to an existing site.

All General Information and Page Two field values and Page Three (depending on Agile system settings) field values are copied to the new site. The new site's lifecycle phase is Disabled. The Attachments are created using the preferred method selected by the Agile administrator (Create New, Reference Existing, Do Not Copy Files, or by prompting). The History tab of the original site reflects that the new site was copied from it.

For more information about creating a site using Save As, see Getting Started with Agile PLM.

See also: Creating an Item Using Save As on page 17 and Creating Sites on page 38.

## 3.8 Associating a Site with an Item

This section includes the following topics:

- Fields on the Sites Tab on page 40

- Adding Sites to the Sites Tab on page 41

- Removing Sites from the Sites Tab on page 42

To make an item available to site-specific BOMs, you must add the sites to the item's Sites tab. If a site is not listed on an item's Sites tab, then you cannot define a site-specific BOM or AML for the item. A site can be listed only once on the Sites tab.

The Sites tab is not under change control, so you don't need to create a change to modify the information on this table.

### 3.8.1 Fields on the Sites Tab

The following table lists default fields on the Sites tab of items.

Field | Definition
--- | ---
Site Name | The name of the site. Not editable from the Sites tab.
Buyer | The buyer code for the item at this site. Select one from a list of codes that have been assigned for sites.
Planner | The planner code for the item at this site. Select one from a list of codes that have been assigned for sites.
Make/Buy | Indicates whether this site makes or buys the item.
Cost | Yes or No. Indicates, for this site, whether there is a cost associated with the item.
Quote As | Select from list. Indicates, for this site, how the item is to be quoted, for example, assembly or component.
Currency | Default currency for this site.
Standard Cost | Standard cost for the item for this site.
Target Cost | Target cost set for the item for this site.
First Released Change | The change that first released the item to this site. This is automatically filled in when the item is released. Not editable from the Sites tab.
Site Lifecycle Phase | The current state of the site: Enabled or Disabled. Not editable from the Sites tab.
Site Type | The subclass of the site. Not editable from the Sites tab.

See also: Adding Sites to the Sites Tab on page 41, Removing Sites from the Sites Tab on page 42.

#### 3.8.1.1 Modifying the Make/Buy Field on the Item Sites Tab

If you have the appropriate modify privileges, then you can modify the Make/Buy field in the Sites table of an item, even if the item has been released. However, the Make/Buy setting is not revision-specific. When you modify the Make/Buy setting on any item revision, it is also modified for all revisions. The following restrictions apply when modifying the Make/Buy setting:

- When the item is included on the affected items table of a change order, the release audit validates the Site AML Allowed and AML Required on Buy settings of the site with the item Sites tab Make/Buy setting for that revision. Past revisions are not audited. (A release audit is performed automatically when the change order is released.)

- Because the Make/Buy setting is not revision-specific and can be changed without using a change order, any validation violations caused by a modification to Make/Buy remain on the latest released revision of the item and may not be detected until the next time the item is added to a change order and the change order is release audited.

For more information, see AML Required on Buy Field on page 37 and Site AML Allowed Field on page 38.

### 3.8.2 Adding Sites to the Sites Tab

When you add sites to the Sites tab of an item, you select the sites from a list. That list includes all enabled sites that you have access to-sites with a lifecycle phase of Enabled that are included in the Sites field of your user profile. Disabled sites do not appear in the list because disabled sites cannot be added to the Sites tab of an item.

After you add a site to the Sites tab of an item, you can edit the table to enter values for the other fields in the Sites table. You cannot change the Site Name value in the Sites table. To change which site is listed, remove the site and then add a new one.

See also: Removing Sites from the Sites Tab on page 42.

To add a site to the Sites tab in Web Client:

1. Click the Add button or press Ctrl-I to open the search pop-up.

2. To select Sites to add you can type the Site names:

   a. If you know the names of the Sites you want, then, in the pop-up field, type the names separated by semicolons.

   b. Begin typing a Site name in the pop-up field and Agile PLM displays a list of Sites that match the typed characters.

   c. Use the up arrow and down arrow keys to highlight the Site you want.

   d. Press the Tab key to add the Site to the pop-up field.

   e. Repeat to add additional sites.

   f. Press the Enter key to add the objects to the table.

   To cancel, press the Escape key to close the search pop-up.

3. You can also search for Sites to add:

   a. Click the pop-up Search button to open the Sites Search palette.

   b. Type the search criteria.

   c. Press the Enter key or click the Search button to run the search.

   d. Double-click a search result row to add the Site to the table.

   e. Type new search criteria to run a different search.

   f. When you are finished, press Enter to close the Sites Search palette.

   After you add a site to the Sites tab of an item, you can double-click a cell on the Sites table to begin editing and enter values for the other fields in the Sites table

   To add a site to the Sites tab in Java Client:

1. On the Sites tab of an item, you can use the Add button in two ways:

2. Click the Add button to display the dialog that allows you to select multiple sites. When you have made your selections, click OK.

3. Click the dropdown arrow portion of the add button to select the site name you want in the dropdown list.

   After you add a site, you can select the site row on the Sites table and edit it to enter values for the other fields in the Sites table

### 3.8.3 Removing Sites from the Sites Tab

You can remove a site from the Sites tab of an item, as long as the item has not been released to that site and you have the appropriate privileges. When an item has been released to a site, the site cannot be removed from the Sites tab of the item. Deleting a site from the Sites tab does not delete the site object from the database.

If you try to remove a site that is referenced by a site-specific BOM or AML, then the system displays a warning. Removing such a site also removes the corresponding site-specific BOMs and AMLs and site-specific Affected Item table rows and site-specific redlines on changes.

When a site is released on an item, the site is not allowed to be removed

To remove a site from an item's Sites tab in Web Client:

1. Select the site that you want to remove.

2. lick the Remove button on the Sites tab.

To remove a site from an item's Sites tab in Java Client:

1. Select the site that you want to remove.

2. Click the Remove button on the Sites tab.

See also: Adding Sites to the Sites Tab on page 41.

## 3.9 Deleting Site Objects

For important details about deleting site objects, see Deleting Agile Objects on page 245.

## 3.10 Editing Sites

Any user with the necessary privileges can modify values entered for a site. Sites are not required to go through the change control process and all modifications go into effect immediately.

To edit a site in Web Client:

1. Display the site's General Info tab.

2. Click Edit.

3. Make the changes you want.

4. Click Save.

To edit a site in Java Client:

1. Display the site's General Info tab.

2. Make the changes you want.

3. Click Save.

Keep the following in mind regarding some of the fields on the General Info tab:

- Name - If you change a site name, then the change is made to the Sites tab of the items where the site is listed and to any other tabs where the site is listed, such as the BOM tab. You cannot change the site name to the same name as another site.

- Buyer or Planner - A buyer or planner cannot be removed if listed on the Site table of an item.

- AML Required on Buy and Site AML Allowed - If you edit AML Required on Buy or Site AML Allowed, then released items are not affected. The new values are enforced with any new items and newly released changes.

See also: Creating Sites on page 38.

## 3.11 Printing Sites

You can print object tabs and other data from your Agile PLM system. You can print the current tab or all tabs. Attachments are printed from their native applications or from the AutoVue for Agile viewer.

In Web Client, with the object open, choose Actions > Print.

In Java Client, with the object open, use the Print button .

For additional information about printing objects, see Getting Started with Agile PLM.