Share System Hierarchy Video
Video Transcript: System Hierarchy
Hello, and welcome to the CMPRO series of training videos.
Systems in CMPRO are one of the most powerful ways in which to manage your data and measure a project’s progress at any given point. As an integral part of its functionality, a system provides organization to the information associated to it. (i.e., CMPRO records).
When more than one system is involved, System and Subsystem are used as the framework for establishing a hierarchical relationship, which is formed using a Connector Record.
This structure is referred to as a “System of Systems Hierarchy.”
We are going to show you what a system hierarchy might look like; then demonstrate how to create one. But first, there are a few housekeeping items to tend to so we can work with Val. Systems
A valid program must be in place before we can create a system.
The Val. Systems Create function must be enabled on our menu.
We must also have the necessary module permissions in order to create and manage Valid System records.
The first step in creating a desired system hierarchy is planning. This can be done using a software program or even pen and paper.
We will be demonstrating how to create a simple hierarchy. However, CMPRO allows for extensive and sophisticated system of systems hierarchy to accommodate every customer’s management and reporting needs.
In this hierarchical structure, a system may be the parent to a lower level system and the child of a higher level system…this is also true in a system/subsystem structure. Creating a system hierarchy, however, provides greater benefit in terms of reporting and visual concepts.
The relationship of parent/child systems in CMPRO is created via “connector records.” With a System Hierarchy, the connector record constructs a ‘behind the scenes’ record, so to speak.
Once we have our system structure organized, we can import that information using the Valid System Import utility, which allows us to mass import Valid System records.
CMRPO provides starter spreadsheets for the majority of import processes, which can be downloaded from the associated Import screen.
The data we have entered on our import spreadsheet will provide the necessary information for CMPRO to build our system structure according to our plan.
Here’s how that works…
Starting at the top of the worksheet, working our way down through our hierarchy, we listed the systems in the order they would appear as a true hierarchical tree structure breakdown.
On the first row under the System column we entered the information for the top level system: HUM V22.
Each System must have the properly assigned Program Abbreviation listed, and it is useful to enter something in the Description column.
Referencing our planning document, we then entered what will comprise the next level of indent on the tree structure: Highlighted here. [highlighted COMPUTING thru SENSORY].
Each entry was made under the System column even though these are subsystems of the HUM V22 system.
The next rows on the spreadsheet begin the entries for the connector records, which are the behind-the-scenes linkages that serve to establish the hierarchy in CMPRO.
To establish this connection, we entered the top-level system again, the HUM V22 under the System column, and here in the subsystem column we entered the four child systems to the HUM V22.
Continuing with the next level of indenture, we entered the connector records for the Navigation system and its child systems.
We used the entry Connector in the Description column, as it helps to differentiate the connector entries from the considered “normal” entries.
We recommend this practice, which provides a visual clarification, especially if you have a more complex system hierarchy.
Thus far, the entry in the column labeled Allow this System to be selected on all List of Values, has been Y for YES.
Because Connector records establish behind-the-scenes structure, and should not appear in LOVs, this column should now switch from Yes to No.
This setting is key to the structural development.
If for any reason this setting needs to be changed after the import is complete, this field on the Val. System Detail screen provides that option.
We saved the spreadsheet and successfully uploaded it via a Valid Systems Import.
Conducting a Valid System Search on the top-level system we just created provides a quick view of all its structural components.
Accessing the detail screen of the top-level system, we can get a quick view of its hierarchical structure using any of these Tree View links.
This structural view can be accessed for any system/subsystem relationship.
Again, a system of system hierarchy provides for more flexible and accurate reporting method when documents and drawings are tied together through related systems.
For instance, selecting a top-level system as the basis for a system baseline, and having the baseline show all child systems will present a more visually complete hierarchy of the overall system.
Conversely, if all we need to report on at the moment is the status of say… the Navigation system, we can access the system at that level.
Selecting the lowest applicable system to get the information you need is the key.
To learn more about the functionality of Valid Systems, including System Baselines, please view related videos, and click on this useful icon (?) to view the related section of System Data topic in the CMPRO User’s Guide.
Thank you for watching.