About Service Items

You can view the update status of an item with B.I. Essentials. B.I. Essentials computes the status of the selected items and its Resulting Product.

The Item Update Status menu option in the B.I. Essentials panel contains the following information about any type of item:

Color	Information
Green	The item and its Resulting Product fit the specifications.
Yellow	Unloaded or deleted objects indirectly impact the item or its Resulting Product.
Orange	Unloaded or deleted objects directly impact the item or its Resulting Product.
Pink	The item or its Resulting Product is removed.
Dark Blue	The Resulting Product of the item is not synchronized and does not fit the specifications. The status of the Resulting Product is based on its links and if the user has modified it.
Light Blue	The Resulting Product of the item is not of the latest revision and does not fit the specifications. The status of the Resulting Product is based on its links and if the user has modified it.

The software automatically creates a default root service item under the PPR Context when you enter your app. This root service item is usually a service assembly. However, you can also use other service item types as the root item.

It is possible to add other root service items, using contextual commands under the PPR Context.

At a lower level of the tree, it is possible to insert new and existing objects.

All created service items have a type. This determines aspects of the service item, such as what the service item does and the type of allowed parent.

The Service Assembly creates an assembly.

The Service Assembly allows creating a service assembly structure. It is usually the owner of at least one Service Part.

You can insert all service item types as predecessor.

The Service Part consumes products, and has an implement link to the consumed product.

It is possible to create a Service Part as a predecessor of a Service Assembly. In this case, the tree marks the Service Part as a child.

It is also possible to create a Service Part as a predecessor of a Transform or Remove Material type step. However, in this case, the tree marks the Service Part not as a child but as a sibling.

This item type cannot have a predecessor: no creation is possible from a Service Part.

The Service Kit provides a group of items. The resulting kit is not an assembly because there is no physical link between its constituent elements: they are independent from one another. However, a kit is required to execute the next assembly stage properly.

The aim of the Service Kit is to deliver the group of items together and unsorted.

You can insert the following service item types as predecessor: Service Assembly, Service Part, and Service Kit.

Continuous provided materials have quantities such as length, mass, area, and volume.

Continuous provided materials include:

• Length magnitude: the provided quantity measures as a length (m, mm, inch, and so on)
• Mass magnitude: the provided quantity measures as a mass (kg, pound, and so on)
• Area magnitude: the provided quantity measures as an area (m2, cm2, and so on)
• Volume magnitude: the provided quantity measures as a volume (m3, liter, and so on).

You can insert all service item types as predecessor for continuous provided materials items.

You can create root service items under the PPR Context using the New Content dialog box that appears when you select Add > Content.

The Service Item section of the New Content dialog box lists the available root-service item types.

If you right-click a service item type, the Set attributes at creation command enables you to specify an explicit or implicit creation mode for each service item type. User Preferences stores this information.

When the creation mode for the service item type is explicit, an attributes dialog box appears. You can define attributes for the service item and configuration in the tabs of the dialog box. You can also define the magnitude of a Continuous Provided Material service item in a dedicated tab.

When the creation mode for the service item type is implicit, the attributes dialog box does not appear and the creation mode creates the service item directly.

Implicit creation of Service items occurs in the following cases:

• Create and update Service Assembly structure
• Assign parts using the Assembly Assignment Assistant, Drag & Drop, Smart Zoom, or an assignment command.

For more information, see 3DEXPERIENCE Platform: Creating New Content.

You can create and store Service items as well as access them through libraries.

You can enrich a Service Assembly using a template, which you must make using a copy from a library.

Create the template and store it in a library. Then, you must use the Copy from Library command to enrich the service assembly with the content of the template.

Template reuse cannot be done using the Insert Existing Service Item command. This is because the command requires that the service item you plan to insert has a scope compatible with the scope of the service item you plan to complete. This is to avoid violation of encapsulation rules.

This functionality exists for the insertion of a Service Assembly that possibly has links to implemented parts and a scope.

For more information, see the Design IP Classification User's Guide.

When the tree hides/shows a service item, then the tree also hides/shows the products implemented by the service item.

If the tree hides/shows a service item that has multiple child service items, then the tree also hides/shows all the products implemented by the selected service item and its children.

The possible Hide/Show statuses for service item occurrences are:

• Shown: the tree node icon displays normally
• Partially Shown: the tree node icon is partially gray
• Not Shown: the tree node icon is fully gray.

When you hide a service item using the Hide contextual command:

• The tree hides the selected service item
• The tree hides the children of the selected service item
• The tree hides the products linked with the selected service item
• The tree hides the products linked with the children (and their children).

When you show a service item using the Show contextual command:

• The tree shows the selected service item
• The tree shows the children of the selected service item.
• The tree shows the products linked with the selected service item
• The tree shows the products linked with the children (and their children)
• The tree shows the parents of the selected service item with the tree node icon partially grayed
• The tree shows the products linked with the direct parents.