OPUS10^TM version 6 includes several improvements to both functionality and user interface. Some important changes are:

• Improved modelling of batched re-order of discardable items
• Direct support for modelling of redundancies
• The "OPSA" view has been extended to include an "ITEM-view" and an "ANALYSIS-view"

The changes will be briefly described below. A more detailed description will be sent to all customers with an upgrade and support agreement together with the delivery of the new version. It can also be provided upon request by contacting Systecon.

MODEL IMPROVEMENTS

Redundancy modelling
OPUS10^TM version 6 includes direct support for modelling of standard type redundancies. The redundancies are of type "k out of n" and can either refer to single items or to a set of different items. Furthermore it is possible to specify whether the redundant links are active in operation or passive standby. In previous versions redundancies could be modelled by manual introduction of dummy stocks and dummy items.

Repair together with lateral support
Local repair of items can in version 6 also be modelled at stations within a lateral support group. The local repair pipeline is analogous to the transport pipeline and basically the two are added.

A modified model for batched reorder of discardable items
The model for batched reorder of discardable items has been modified to make it more consistent with the model for repairable items. The new model is solely based on a steady-state approach used everywhere else in OPUS10^TM. As for repairables, the new model is primarily based on the nominal stock level. A reorder is considered as a resupply analogous to repair resupply.

The MoE-calculation is basically the same as before based on the Hadley-Whitin model. The calculation of present value has also been modified and is now based on a continuous interest rate without any adjustments for different types of costs.

Continuous interest rate in calculation of present value
The calculation of life time present values of annual costs has been changed to a model assuming continuous payments and a continuous interest rate. This means that there is no longer any need to make any assumption about a certain point in time during the year when the costs occur (beginning, middle or end). In the new model the costs are instead assumed to occur continuously in the same way as demands and repair actions.

Repair during autonomous missions
It is now possible to model local repair of items at autonomous stations. The repair is not restricted to primary items but can be modelled for items at any level in the material breakdown structure.

LORA Improvements
The same type of optimisation control used in other problem types is now also performed in the problem type LORA-XT.

Another important improvement is the possibility to model different resource costs at different locations. This simplifies the modelling of repair outsourcing alternatives to be included in the LORA optimisation. The location specific resource costs are specified in a new optional input table.

It is also possible to specify different resource occupation times (UTILT) for different items within a team.

Availability calculation in subsystem modelling
It is now possible to model subsystems without using a special type of calculation of the availability.

Replacement of PRU in PM tasks
The model for preventive maintenance, PM, has been improved regarding item replacements. The regularity, scheduled or unscheduled, is now explicitly specified in a new input field. In previous version the regularity was implicitly set based on the replacement fraction. Another new field has been added to explicitly specify whether the replaced item shall be discarded or re-paired.

Specific support organisation for remote system repair
In remote system repair the default is that the system follows the support structure data specified in StationStructure. Similarly to items it is now possible to model specific support structure data for each type of system.

Modifications in the data model
All floating point numbers are now stored in double precision

Miscellaneous
Fill rate / Service Level is now calculated and included as a Measure of Effectiveness (MoE). It is calculated as (1 - ROS) and is the probability that a demand can be served immediately at a stock location.

The variance for the number of backorders is now calculated and available in the reports.

Resource costs can now be specified individually per deployment station. Any values given here will override the costs given per resource type.

PROGRAM IMPROVEMENTS

The system analyser OPSA has been replaced by two new views, the Item view and the Analysis view. Both are item oriented browsers based on a material structure tree to the left and a support organisation plot to the right.

Item view
The Item view is a view on the input document showing the material breakdown structure. When a certain item (or system) is selected in the tree the corresponding data is presented to the right. The upper pane to the right shows a plot of support organisation together with data for the selected item. Graphical symbols show where the selected item is handled (replaced, repaired or reordered). The lower pane to the right shows tabular data for the selected item. Here it is possible to make data changes for the selected item.

Analysis view
The Analysis view is an interactive result browser that shows the support organisation and related data for the selected item. The view looks similar to the Item view but is based on calculated results. Besides input data it shows intermediate results such as demand rates and resupply times. In case the analysis view is invoked from the result window the view also shows point dependent results such as stock levels and expected number of backorders for the current point. The Analysis view also contains the list and scatter panes from OPSA, as well as the reversed system breakdown tree.

Global changes
It is now possible to rename, delete or add new objects in one single command without having to switch between several tables.

There is also a declassify command available that will automatically rename all IDs to a sequence number prefixed by a selected anonymous letter combination. This command can be very useful in case of modelling issues where the help-desk support needs to review files containing classified data.

Miscellaneous
In all input tables an optional notes field has been added where any comments or text regarding the input data values can be entered.

For clarity, colours are now used to distinguish between different views and windows that used to have a similar look.

All numbers in the input and results are now presented with the thousands separator selected in the Windows settings. This improves the readability especially for large values on the cost side.