0:06 Welcome to this Application Explainer video, part of our SLM 101 topic range.
0:11 In this video we’ll cover the subject of using the object tree within SLM.
0:18 The SLM system is an object orientated database with a hierarchy formatted object tree for quick navigation within the SLM modules.
0:29 Following information will be covered in this training.
0:32 Chapter one will be how the SLM object tree is set up.
0:36 Chapter 2 will be requirements of creating, deleting and linking objects.
0:41 Chapter 3 will be searching the object tree.
0:44 Chapter 4 will be rules for importing and exporting data.
0:52 In chapter one, we’ll be covering the parent child relationship hierarchy approach and where to get started.
0:59 As an object orientated database, SLM uses the object tree to allow users to navigate within each of the modules.
1:08 Each module will contain the SLM object tree, but depending on the module, the objects you see may be different.
1:15 The object tree is set up with what we call a parent child relationship.
1:20 Each object is nested underneath an object from the top down.
1:25 Each object has a unique ID, therefore users cannot create two different objects with the same ID.
1:31 Objects with the same ID are considered the same object.
1:36 Users must start within the SLM global module to set up the site level and the unit level within the object tree.
1:44 Once these are completed, users can then navigate to other modules to create different types of objects.
1:51 To create a site object, simply click on the parent that is the Enterprise Edit Tools and Add Site.
1:59 To create Unit object, click on the Site level, Edit Tools and Add Unit.
2:05 These set up the basis for the object tree that then allows for other objects to be created in other modules.
2:16 In Chapter 2, we’ll be covering where and how do you create and delete new objects?
2:21 How are objects linked and unlinked to multiple parents and things to consider the parent child relationships?
2:29 For adding a new object to the SLM system, the user must consider the parent child relationship.
2:34 Where can we create the object from?
2:37 To create a new object, the user must navigate to the parent object and from there, using the Edit Tools button, they can create the desired object that they’re looking for.
2:48 But remember, each object is nested within parents and children.
2:52 So for example, if the user is looking to create an input object, they cannot do it simply from the SIF.
2:59 They would need to create the SIF, the input group, the input voting group, and then from the input voting group level that is the parent of the input.
3:09 They could then use the Edit Tools button to add an input.
3:13 Each object has a specific parent child relationship that becomes nested within the SLM object tree.
3:22 For deleting objects, users can navigate directly to the object with which they want to delete using the Edit Tools button.
3:31 The user will be able to delete the object, but only if that object has no children underneath it.
3:40 So for example, if I click on this input voting group, it has all of these inputs as children.
3:47 So the Edit Tools button will not display a Delete input voting group.
3:51 From here you would have the option to use the Admin Tools button and select Delete and Cascade, which will delete the input voting group object, but it will also delete all of the associated children from underneath it.
4:04 User privileges can be set up within the System module to limit a user’s ability to add or delete objects.
4:11 Some notes to remember, some objects are visible in multiple modules and some are not.
4:17 So an object may have children that are only visible in certain areas of SLM.
4:23 For example, an input object may not have a visible child here in the Instrument and Systems module, but in the Operate and Maintain module, the input may have a Device object, so you may not be able to delete it using the Edit Tools button.
4:39 Objects can be the children of multiple different parents.
4:43 For linking objects to multiple parents, users can do this in a few different ways.
4:50 As an example, say you want to add an input group to a SIF SIF O 4:00, but that input group already exists on a different SIF.
5:02 We want to add the input group IG 12 to SIF O4.
5:07 The user can navigate to SIF O4 using the Edit Tools button.
5:11 Select Add Any Input Group.
5:14 Now instead of creating a new object, we can use the drop down menu here.
5:18 Or we can simply start typing in the input group that we want to add and select it.
5:27 You’ll notice that it will automatically change the action from create new to link selected object and when we save that, it will now associate the IG12 with SIF O four and you can see it now on the object tree in both places.
5:46 Now that you’ve done this, IG 12 is the child of both of these Sifs.
5:51 Not only the input group, but all of the children of that input group are also related to both Sifs.
6:04 These are the same objects across both Sifs.
6:07 So if I’m to change data on input 42 TT, it will change it for both SIF O4 and SIF O5.
6:18 Users can also drag and drop objects between the child and parent relationships on the object tree.
6:28 Let’s say we want to add this input group 10 P 462 to SIFO 5I can simply grab it, click and hold and bring it down and drop it onto SIFO 5.
6:39 It will now associate that and link that object there.
6:45 You have to keep in mind the parent and child relationship.
6:49 For example, I can’t drop an input group object onto another input group object.
6:54 The relationship is invalid.
6:57 You must select the right parent level to drop the object onto.
7:02 Objects that are the children of multiple parents can be unlinked from any of the parent objects as long as they have at least one parent object left.
7:10 Users can navigate to the desired object selecting the Edit Tools button, click Unlink Parents.
7:19 It will then show you all of the parent objects that that particular object is linked to and you can select which specific object you would like the parent unlinked from and click the unlinked button.
7:31 Now it’s no longer there.
7:34 You can also simply hit CTRL shift on your keyboard and click on the object you want unlinked.
7:40 SO10P462 is linked to SIF 4 and SIF 5.
7:45 If I want to unlink it from SIF four, hit CTRL shift and click.
7:50 It will pop up a message saying confirm you want to unlink it and when I select OK it will remove it from SIF 4 and leave it on SIF 5.
8:03 In chapter 3 we will be covering up the object trees open node search features and objects breadcrumb features.
8:11 The SLM object tree has an open node search at the top of it.
8:15 This allows the user to look for a specific tag ID within the object tree itself.
8:21 The text search will allow the user to see all of the different levels of hierarchy for that specific object.
8:27 So IG 12 we can see this this site, this unit, this SIF and this SIF on objects that exist as a child of multiple parents.
8:37 The user can also utilise the SLM breadcrumb functionality to see all of the places that the object exists on the far right of your screen.
8:46 When you select the object, you will see a down arrow.
8:50 When you click on that, it allows the user to see all the levels of the breadcrumb for this particular SIF.
8:56 So it’s in SIF O4IN unit 10 and in unit 42, and of course we’ve clicked on it, it’s in SIF O5IN unit 10.
9:05 Remember, the object has a specific ID.
9:08 It’s related across all of these different places.
9:10 So changing this input group data in one place will change it everywhere if there’s no arrow on the right side of your screen and there’s no other place that that object exists within the object tree hierarchy.
9:26 In Chapter 4, we’ll be covering rules to Remember for importing data, Rules to Remember for exporting data, and things to consider.
9:35 Does SLM know the correct spot for the imported data and how much data do you want to export?
9:42 Quick Rules to remember for importing and exporting For importing data, you must understand the parent child relationship.
9:50 You cannot import an object into the SLM system without the parent object already existing.
9:55 An input group object cannot be imported unless the SIF object is already there and ready to receive it as a child.
10:03 For exporting data, the user can click on the object that they want to export and using the Admin Tools button can download that data set.
10:11 This will export the data for all of that object and all of its associated children.
10:18 So for example, if you want to get the exported data for a specific input, you could click on the SIF object and go through the admin tools and download the data set.
10:28 But that will give you the data for the SIF, the input group, the input voting group, the logic solver, the output group, the output voting group, and the outputs.
10:40 Or you can simply select on the specific input you want and using the admin tools, download the data set.
10:47 Whatever level you export the data from, you receive that data for that level and everything below it.
