Introduction	Top

Department SDIs are used to define a business division that deals with a particular area of activity. Departments are used in the following OOB configurations:

Department Hierarchies	Top

Departments can be defined and configured in a hierarchical structure.

A "Site" typically defines a physical location consisting of multiple testing labs. Sites are typically used to determine the lab to which testing is allocated, segregate Samples to improve informatics, and divide work/resources into manageable sets.

Typically, the Site to which the Sample belongs is copied-down from Product, SamplePoint, or Location. Upgrading customers may have already setup Departmental Security on their Samples (where that Department is analogous to a site). For backward-compatibility, LabVantage 8.4 can use Departmental Security that is setup on a site-by-site basis.

For detailed information regarding copy-down from Master Data and resolution of columns, see Master Data Copy-Down and Resolving Sites, Testing Labs, and Work Areas.

Each Site can contain multiple "Testing Labs". These are generally where Samples are tested. Testing Labs are typically used to define the specific lab that conducts testing.

For detailed information regarding copy-down from Master Data and resolution of columns, see Master Data Copy-Down and Resolving Sites, Testing Labs, and Work Areas.

Each Testing Lab can contain multiple "Work Areas". These are generally specific areas of a Testing Lab, but can also define other subsets of the lab such as groups of personnel specializing in specific areas. A Work Area is essentially a subset of a Testing Lab to which work can be assigned. Work Areas are generally used to segregate work for organizational reasons (SDIWorkItem.WorkAreaId), assign work to a group of users rather than an individual) (SDIWorkItem.s_AssignedDepartment), and to estimate utilization and capacity during planning.

For detailed information regarding copy-down from Master Data and resolution of columns, see Master Data Copy-Down and Resolving Sites, Testing Labs, and Work Areas.

Department List Page	Top

In addition to standardized List page operations (Add, Edit, Import, List Control, and Other Tasks), these specialized operations are available:

	"Navigator" opens a Navigator configured to show the Departmental hierarchy of the selected Department. The example below shows a Site hierarchy with its Testing Labs and Work Areas. Users and Instruments are shown for each level.
	"Manage Calendar" and "Manage Core Hours" can be defined for a selected Department. See Calendars for more information.
	"Manage Child Dept Users" opens a ManyToManyMaint page that allows Users to be added to (or removed from) the child Departments of the selected Department. These are "permanent" Department assignments, meaning they are assigned to this Department by the Administrator unless explicitly removed by the Administrator. Selecting a Department shows its child Departments (as in the example below, where the Site contains two Testing Labs). Selecting a Testing Lab shows its Work Areas. Selecting a Work Area shows Departments in the hierarchy that are related to the Work Area. Use the checkboxes to establish the intersecting User-Department relationships.

Department Maintenance Page	Top

This allows you to specify the Department's place in the Departmental hierarchy. When defining the hierarchy, fields dynamically become available depending on options that are valid or required for the selected level.

Note that a Department can also be both a Work Area and a Testing Lab.

Testing Lab Type

If you have multiple Sites, one Test Method may need to be associated with multiple Testing Labs across different Sites. In this case, you can specify a "Testing Lab Type" and "Parent Site". These can be used to determine the actual Testing Lab, thus associating the Test Method to only one Site. The system resolves this by finding the Testing Lab with a Testing Lab Type having a Parent Site that is the same as the Sample's Site ("Tokyo" in the example at the left). Values for "Testing Lab Type" are defined by the "TestingLabType" Reference Type. NOTE:   Only one Testing Lab Type can be defined per Site. Alternatively stated, a Site can have only one "Testing Lab" for each "Testing Lab Type" (see Testing Labs). Here is an example setup: 1. Associate the Test Method to a "Testing Lab Type" (rather than a Testing Lab). 2. Ensure that the Testing Labs have a Testing Lab Type and a Parent Site, there is only one Testing Lab Type per Site. 3. Ensure that the Sample has a Site defined. When you add the Test Method to the Sample (thus creating a Test), you can now derive the specific Testing Lab based on the Testing Lab Type and the Sample's Site, i.e., Sample (Site) + Test Method (Testing Lab Type) + Department (Testing Lab Type, Parent Site) >> Test (Testing Lab) In the example at the left, there is a MicroBiology Testing Lab at each of two Sites. To use a "Bacteria" Test Method at each Site, you could make a copy of that Test Method for each Site (since the Test Method must know the Testing Lab that will do the work). That can become tedious if you do not define a "Testing Lab Type". Rather than associating the "Bacteria" Test Method with a Testing Lab, associate it with a Testing Lab Type called "MicroBio". You would then set each Testing Lab (at each Site) with the "MicroBio" Testing Lab Type. The Sample defines the Site, so the Testing Lab for the Site can be resolved.

Work Area Type

The "Department Users" detail lets you add/remove Users to/from this Department. This detail is used to populated the User's Department information as shown in Users and Roles → User Departments. The Department defines a User's Default Testing Lab and Shift (below), both of which can be overridden for the User.

Note that you can assign Users to Work Areas in several ways:

The "Testing Labs" detail is shown when the Department is a Site (see Hierarchy). This lets you add/remove Testing Labs to/from the Site.

The "Department Shifts" detail is shown when the Department is a Testing Lab (see Hierarchy). This lets you add/remove Shifts to/from the Testing Lab.

In addition to the standard Add and Remove buttons, the following buttons are also available:

The "Work Areas" detail is shown when the Department is a Testing Lab (see Hierarchy). This lets you add/remove Work Areas to/from the Testing Lab. See Department Users to assign Users to Work Areas.

The "Contacts" detail lets you add/remove Contacts to/from this Department. 

The "Calendars" detail is available only if the Department is a Site or Testing Lab. This allows Shared Calendars to be added/removed/managed for the Site or Testing Lab. See Calendars.

Master Data Copy-Down	Top

This section describes copy-down of columns related to Departments and general work assignment.

When Master Data is associated with a Site, Testing Lab, or Work Area, creating the Instance Object copies the data from the Master Object to Instance Object (below).

For example, suppose a Testing Lab and Work Area are defined in a Test Method. When the Test Method is added to a Sample, the Test Method's Testing Lab and Work Area are copied down to the Sample's Test. If you use "Assign Analyst" in SDIWorkItem or Data Set List page (as described in Manage Data Sets, Manage Tests, and Manage Worksheets), choosing Users provides a filtered list based on the User's Testing Lab and Work Area.

Copy-Down to Data Sets (SDIData)

Rules for copy-down to Data Sets (SDIData):

•	When a Data Set is added to a Sample, if the Data Set does not belong to a Test Method, "Is Work Plannable", "Testing Lab", "Work Area", "Auto Assign Rule", and "Auto Assign Analyst" are copied from the Data Set's Parameter List.
•	Data Sets get the "Testing Lab" and "Work Area" from the relevant Parameter List. Based on the "Auto Assign Rule" defined in the Parameter List, the "Assigned Department" and "Assigned Analyst" of the Data Set are populated with the values of "Work Area" and "Auto Assign Analyst” (respectively) in the Parameter List.

Copy-Down from Test Methods (WorkItems) to Tests (SDIWorkItems) and Data Sets (SDIData)

Rules for copy-down from Test Methods (WorkItems) to Tests (SDIWorkItems) and Data Sets (SDIData):

•	By default, the "Testing Lab" and "Work Area" of a Test Method (WorkItem) are applied to the Test Method's Parameter Lists (WorkItemItems). If a Test Method does not define a Work Area, the Work Area can be defined at the level of the Test Method's Parameter List (WorkItemItem).
•	When a Test Method (WorkItem) is applied to a Sample, the Test (SDIWorkItem) gets these values from the Test Method (WorkItem) and the Data Set (SDIData) gets these values from the Test Method's Parameter Lists (WorkItemItem).
•	"Auto Assign Rule" for a Test Method can be "None", "Work Area", or "Analyst": • If "Auto Assign Rule" is "Work Area", the Test Method's Work Area is copied to the Test (SDIWorkItem) as the Default Department. This is persisted in the column sdiworkitem.s_assigneddepartment. • If "Auto Assign Rule" is "Analyst", the "Auto Assign Analyst" of the Test Method (WorkItem) is assigned to the Test (SDIWorkItem) as the Default Analyst. This is persisted in the column s_assignedanalyst.
•	Based on the "Auto Assign Rule" defined in the Parameter List, the Assigned Department and Assigned Analyst of the Data Set are populated with the values of "Work Area" and "Auto Assign Analyst” (respectively) in the Parameter List.

Copy-Down to Samples

Rules for copy-down to Samples:

•	Copy-down from Sample Point, Location, and Product: • If a Sample has a Sample Point, the Sample's Work Area and Testing Lab are copied from the Sample Point. • If the Sample does not have a Sample Point, the system checks if the Sample has a Location. If so, the Sample's Work Area and Testing Lab are copied from the Location. • If the Sample does not have a Sample Point or Location, the system checks if the Sample has a Product. If so, the Sample's Work Area and Testing Lab are copied from the Product. • If a Sample has a Sample Point, Location, and Product with all foreign keys populated, the order of copy down priority is the same: Sample Point takes precedence over Location, and Location takes precedence over Product.
•	Based on the "Auto Assign Rule", Assigned Analyst (s_sample.assignedanalystid) and Assigned Department (s_sample.assigneddepartmentid) are populated with the "Work Area" and "Auto Assign Analyst" defined by the relevant Master Data.
•	A Sample's Assigned Department and Assigned Analyst are copied to the Sample's Tests (SDIWorkItem) and Data Sets (SDIData). If not defined in the Test Method (WorkItem), the Test Method's Parameter List (WorkItemItem) or at the Parameter List level, the Test (SDIWorkItem) and Data Set (SDIData) get the Default Assigned Department and Assigned Analyst from the Sample.

Configuring Foreign Key Order when Copying Sites from Referenced SDIs to Samples

Configuration of Foreign Key Order when Copying Sites from Referenced SDIs to Samples:

•

The "Copy Site from Referenced SDI to Sample" collection in the Batch Sample Policy can be used to maintain the order in which referenced SDIs will be searched and copy the Site to the Sample from the first referenced SDI available with a Site Id. This allows changing the copy down order, introducing a new foreign key link, and disabling a link if required. This is shown in Resolving the Site for a Sample.

•

With specific regard to Request Samples: Request Samples can have their Site copied from Request or RequestItem. The Site can be specified for Requests of "Submission" type. The OOB setting for "Copy Site from Referenced SDI to Sample" specifies RequestItem before Request. Therefore, if the RequestItem has Site, it will get preference over the Site defined in the Request.

Copy-Down of Assigned Analyst and Assigned Department to a Test (SDIWorkItem)

The flow below describes how Assigned Analyst and Assigned Department are copied-down to a Test (SDIWorkItem). Analysts and Departments (as "Work Areas") are assigned to Tests in the SDIWorkItem List page using the Assign Analyst and Assign Work Area operations.

 

 

Copy-Down of Assigned Analyst and Assigned Department to a Data Set (SDIData) that belongs to a Test (SDIWorkItem)

The flow below describes how Assigned Analyst and Assigned Department are copied-down to a Data Set (SDIData) that belongs to a Test (SDIWorkItem). Analysts and Departments (as "Work Areas") are assigned to Data Sets in the Data Set List page using the Assign Analyst and Assign Work Area operations.

 

  

Copy-Down of Assigned Analyst and Assigned Department to a Data Set (SDIData) that does not belong to a Test (SDIWorkItem)

The flow below describes how Assigned Analyst and Assigned Department are copied-down to a Data Set (SDIData) that does not belong to a Test (SDIWorkItem). Analysts and Departments (as "Work Areas") are assigned to Data Sets in the Data Set List page using the Assign Analyst and Assign Work Area operations.

 

 

 

 

Resolving Sites, Testing Labs, and Work Areas	Top

Overview

This section describes resolution of columns related to Departments and general work assignment. Note that Departmental Security is taken into account when resolving Sites for Samples. 

Resolving the Site for a Sample

The flow below describes how the Site for a Sample is resolved.

 

  

Resolving the Site for a Consumable Quality Sample

The flow below describes how the Site for a Consumable Quality Sample is resolved.

 

  

Resolving the Site for a QC Sample in a QC Batch

If Departmental Security is enabled for the QC Batch and the QC Sample, the Sample gets its Security Department from the QC Batch.

If the Security Department of the QC Sample is a Site, it becomes Sample’s site as well.

If the Security Department of the QC Sample is not a Site, the Sample is checked to see if it has a parent Department. If so, the parent Department becomes the Sample's Site.  

Resolving the Testing Lab and Work Area for a Data Set (SDIData) that belongs to a Test (SDIWorkItem)

The flow below describes how the Testing Lab and Work Area for a Data Set (SDIData) that belongs to a Test (SDIWorkItem) is resolved.

 

  

Resolving the Testing Lab and Work Area for a Data Set (SDIData) that does not belong to a Test (SDIWorkItem)

The flow below describes how the Testing Lab and Work Area for a Data Set (SDIData) that does not belong to a Test (SDIWorkItem) is resolved.

 

  

Resolving the Testing Lab for a Test (SDIWorkItem) Across Multiple Sites

The flow below describes how the Testing Lab for a Test (SDIWorkItem) is resolved across multiple Sites.

 

  

Resolving the Work Area for a Test (SDIWorkItem)

The flow below describes how the Work Area for a Test (SDIWorkItem) is resolved.