omegaps analyzer workshop analyzer workshop - exercises.pdfextended user training exercise ±...

OmegaPS Analyzer Workshop

May 17th 2010

Extended User Training Exercises

17 May 2010

Ottawa, Canada

OUGM 2010 – Analyzer Workshop


Extended User Training Exercise – OmegaPS Analyzer R4

This document provides user exercises that demonstrate new features that were included after Release 4 of OmegaPS Analyzer. They are intended to be an extension to the basic User Training completed in a standard Analyzer course and should be conducted on release R4.01.

The following exercises are included:

Contents Merging Databases ................................ ................................ ................................ ...................... 3

Multi-PE Operations ................................ ................................ ................................ ..................... 6

Modelling with Scenarios ................................ ................................ ................................ ........... 11

Scheduled Replacements in Sparing Analysis ................................ ................................ ........... 14



Merging Databases The merge database function allows for the bringing together of individual projects into one integrated project database. There are some obvious limitations that need to be managed, but this function will make system analysis more achievable from the many equipment analyses that may have been completed.

To perform a merge of your database, open the ‘File’ menu and select ‘Merge’. A list of all saved databases will appear. .

Select the name of the configuration you wish to merge the file name or the ‘Open’ button to merge into the open database. ‘Cancel’ to cancel the operation.

The project being merged into the open database must be the same version. If it isn’t the same version convert the project first by opening it allowing the automatic conversion to be processed.



Confirm that you really want to merge the selected database into the open data base. Yes to continue the merge No if the identified database is not to be merged Cancel to end the import process

If the merge process is completed you will receive a “successful” message. OK to finish

After any interruptions in the process where the merge is cancelled you should see the message that the open database has been restored to the pre-merge state. OK to end the merge process

After a successful merge it is important to review the resulting data sets. Validation and modifications are made as part of the process to create a logical merged project. Some names may need editing and scenarios revising to complete the new project database.

EExxeerrcciissee –– MMeerrggiinngg aa DDaattaabbaassee

To demonstrate the merging of a database into the current database, perform the following steps: 1. Open the file ‘Training Exercise.mdb’. 2. Close any open configurations or data forms 3. Select File>Merge



The Project being merged into the open database must be the same version. If it is an older version convert it first.

4. Select the Analyzer R4 Demo.mdb project database to merge and the ‘Open’ button. 5. Confirm the merge process and ‘Yes’. 6. When the database merge is completed the ‘Merge Successful’ message is presented. on

‘OK’ 7. Review the newly merged physical structure. Note how a new top item was created and named

‘MERGED SYSTEM’. The original project has been made a child to this new top item and the merged database added as a peer EQP to the original project.

8. Select the top item in the Physical Tree. Rename the ‘MERGED SYSTEM’ to “Communications

Vehicle System”, which is the desired name for the new system being created by merging previous equipment level projects. Press Enter to save the edited name.

9. Right click on the “Communication Vehicle System’ name to display the menu. Select ‘Part

Detail’ 10. Edit the Item name from MERGED SYSTEM to Communications Vehicle System. Edit the

Reference number to 1200CVS. on ‘OK’ to save changes 11. Select File>Close to complete the exercise.



Multi-PE Operations To model variants of the equipment or multiple PE operating in the organization you need to define each individual PE and then assign them to LOM 1 sites in the support organization. To create multiple PE in the physical tree make sure that the EQP labels are all assigned at indenture 2 or lower. There are multiple methods for entering additional PE data as outlined in the basic URG. In this exercise we shall use the previously merged data set for the vehicle. After the merge database function the physical tree will contain both PE (i.e. the original Radio Set mk 15 and the merged in Vehicle) at the second indenture as children to the new system created.

Open the Data>Equipment Configurations and select PHYSICAL to display the physical tree.

The LRUs in Vehicle are ‘collapsed’ in this figure to save space. Use the + or - symbol to expand and collapse trees

The merge also brought in the Vehicle’s saved configurations for use in analysis runs. If the additional PE are created by other means then create and save the Logistical configuration for the Vehicle that will be used in scenarios by following the steps in Exercise 2.4 in the R4.01 URG. Multi-PE are assigned in the Support Organization. Open the Support Organization definition screen.

From the main ANALYZER menu select Data and Support Organization.



The Open Configuration screen appears.

If previous Support Organizations have been saved they will be available on the open configuration list. Here the merged “Original (Demo)” is also displayed. Open to select the Support Organization configuration. Cancel to stop the process. Delete to remove the selected Support Organization.

When open is selected the Support Organization Entry screen appears.

The Radio Set mk 15 Support Organization is displayed with the PE assigned at LOM 1 sites. Select the LOM 1 operating site to which the PE is to be added. Add PE to select the PE to add to this location

Select the name of the PE to Add. ‘OK’ to Add the PE to the chosen location



the PE can only be added to a site once.

The PE is now assigned to the selected location .

the Configuration can be removed by the ‘Delete’ button

Enter data for ‘Qty PE’ and ‘Operating Hours/PE/month’. Update to save the changes Close to end the process.

Add PE to the operating (LOM 1) sites as required for the operating scenarios. When completed adding and updating the Support Organization Close to end the process.



Yes to Save No to exit without saving Cancel to return to the form

To Save, select the support organization name that is to be updated with the changes. It defaults to the current name. A new name can be typed in the ‘Configuration Name’ field. Add suitable comments. Save to Save the changes. Cancel to return to the form. Delete to remove the selected configuration from the database.

the Configuration can be saved by also the ‘Save’ button.

EExxeerrcciissee –– MMuullttii--PPEE OOppeerraattiioonnss

To demonstrate the Multi-PE operations definition perform the following steps: 1. Open the file ‘Training Exercise.mdb’. 2. the ‘Cancel’ button to close the Saved Configurations form. 3. Select Data>Support Organization menu option.



4. Select the Support Organization configuration name and the ‘Open’ button. 5. Select the Operating Site 1 location. 6. on ‘Add PE’ button.

7. Select ‘VEHICLE’ from the ‘Select a PE to Add’ list. the ‘OK’ button. 8. Enter Qty PE as 10 and Operating Hours/PE/month as 50

9. on ‘Update’ button.

10. Select the next LOM 1 site (Operating Site 2) and repeat steps 6-9. Repeat for all LOM 1 sites,

entering the following data at each location

Site Name Qty PE Operating Hours/PE/month

Operating Site 1 10 50 Operating Site 2 20 45 Training Site 2 150

11. Save the configuration as “Both PE Support Organization” 12. Select File>Close to complete the exercise.



Modelling with Scenarios The R4 model conducts the analyses based on saved Scenarios. A scenario is a defined combination of a saved Support Organization, with assigned PE, and the selected logistical configuration for each PE that is active.

From the main screen on Analysis, then System Analysis, to opens up the Analysis screen.

The top portion of the System Analysis form identifies saved Scenarios. ‘New’ to create a scenario ‘Edit’ to change a current scenario ‘Delete’ to remove a saved scenario

Databases converted from earlier versions will have Scenarios created from the logistical configurations in the database. These will be named with SCENARIO: and the configuration name (E.g. SCENARIO:BASICCONFIG)

After a merge the scenario list contains all merged scenarios. These should be checked as valid definitions in the new database.

When New or Edit is selected the Scenario definition form is presented. A New selection will be empty.



Enter a name for the Scenario From the list of choices select the Support Organization that should be used Enter notes to describe the Scenario Based on the Support Organization selected the Prime Equipment list will be populated with each PE assigned to LOM 1 sites. For each PE select the configuration that is to be used in the analysis ‘OK’ to save the Scenario definition.

After an Echelon is selected it cannot be changed. Use the pull down list under Configuration to select a logistical Configuration that is saved for the PE.

This list only becomes available when the cursor is placed on the configuration field.



EExxeerrcciissee -- CCrreeaattiinngg aann AAnnaallyyssiiss SScceennaarriioo To demonstrate Creating Scenario definitions perform the following steps: 1. Open the file ‘Training Exercise.mdb’. 2. the ‘Cancel’ button to close the Saved Configurations form. 3. Select Analysis>System Analysis menu option. 4. on ‘New’ button.

5. Enter the following scenario definition:

Name: Both PE Operations Echelon: BOTH PE SUPPORT ORGANIZATION (select from pick list) Notes: Uses the Support Organization with multi-PE ops Prime Equipment: Will auto enter the two PE assigned in the support

organization. Configuration: Use the pick arrow displayed when the cursor is positioned on

the field. Select basic configurations for both PE.

6. on ‘OK’ button.

7. Note that “Both PE Operations” is now available on the Select Scenario list. 8. on ‘Cancel’ to close the System Analysis form. 9. Select File>Close to complete the exercise.



Scheduled Replacements in Sparing Analysis In many equipment maintenance plans component parts are removed and replaced from the PE before failure occurs. This is generally based on the item’s condition (e.g. CBM, when vibration reaches a specified level) or elapsed time (e.g. 3 monthly). This replacement task requires a spare part to be available prior to failure. Its demand rate is at the Scheduled rate. However, in reality, not all failures are prevented. Because of the random nature of most failures it is impossible to “prevent” everyone through a scheduled replacement, therefore, a multiplier, known as the survival rate is applied. This basically determines what percentage of time the item survives to the scheduled replacement, or conversely, what percentage of failures still ok with the scheduled replacements. The Sparing analysis blends the SM replacements and the un-prevented failure replacements into a revised demand rate value. The SM sparing requirements are entered in the Demand Calculator for the part of interest. When the part is highlighted in the equipment configuration tree select the Demand Calculator (extended info) button beside the MTBR (units) field.

- Ann Sched Replace is the annualized rate for SM: e.g. 6 monthly = 2 - Fleet Ann Rep is a calculated field. - Survived Items (%) is the expected level of items that will not fail before the SM replacement occurs. ‘OK’ to save the calculations.

In this example it can be seen that there are 0.5 Annual Scheduled Replacements (every two years) and an expected survival rate of 80%. This therefore determines that: 23 RPM Hrs becomes 4.6 un-prevented RPMHrs (23 * 0.2 ( 0.2 = 1 - 80% non-survived)) MTBM has become 217,391.3 UMUBR. The calculated fleet replacements is 64 based on 128 PE



When running sparing analysis the Failures Per Year value used will be a ‘blend’ of scheduled replacement parts and un-prevented corrective parts.

EExxeerrcciissee -- SScchheedduulleedd RReeppllaacceemmeenntt SSppaarreess To demonstrate the use of scheduled replacement spares perform the following steps: 1. Open the file ‘Training Exercise.mdb’. 2. the ‘Cancel’ button to close the Saved Configurations form. 3. Select Data>Equipment Configurations menu option.

4. Select Radio Set mk 15: Basic Config 5. on ‘Open’ button.

6. Select LRU: Power Amplifier

7. on ‘Extended Info’ button beside MTBR (hours) field

8. Enter the following data:

Ann Sched Replace: 0.5 Survived Items (%): 80.00

9. Select Unprevented MUnitsBR field. Confirm value updates to 217,391.30.

10. Select U/P RPM Units field. Confirm value updates to 4.60.

11. on ‘OK’ button.

12. Close the equipment details form. Confirm to save changes. Name configuration as Basic

Config - SM

13. Select Analysis>System Analysis menu option.

14. Create a new Scenario named “Basic with SM” using the new logistical configuration just saved (Basic Config – SM). on ‘Sparing’ button.

15. Complete the Sparing analysis and review the Provisioning Report.



16. Close the Provisioning Report. 17. on ‘Cancel’ to close the Sparing Report Selection form. 18. Select File>Close to complete the exercise.

omegaps analyzer workshop analyzer workshop - exercises.pdfextended user training exercise ±...

Documents