News – Page 3 – Logistic Engineering Services Software

As I advised in a previous post, our next release of eMRD (V3.3.3) will be out by the end of this year. The main focus of this release is the inclusion of RCM Functionality compliant with DEF(AUST)5692 Issue 2. However, we are including a lot more enhancements, and here is the list so far:

ISSUE: 1597 PSS REPORTS – OUTPUT FORMAT Part 2

ACTION: The previous ‘2 Page Nos / page (B6 turn & tumble)’ option for printing PSS reports has been replaced by a true ‘B6 turn & tumble (on A5)’ option.
The report design has been modified to print one card per page on A5 paper.
The top and bottom margins alternate so that it formats correctly when printed in duplex (double-sided) to flip on the top/bottom edge.

ISSUE: 2189 Publication Library ‘Where Used’ function for tech pubs.

ACTION: Added a WhereUsed button on the Publications Library form to show all usages of a Publication.
The types of useage are:
1. a publication linked to a Task (CH table);
2. a publication linked to a UOC Servicing (WR table); and
3. a publication used in an IPB reference for a Provisioned Item (HK table).

ISSUE: 2390 More functionality required when restoring a database using eMRD

ACTION: Modified the SQL Server Database Restore function to allow a single database to be selected from a backup file containing multiple databases.
Note that the user must have Create Database permissions on SQL Server to be able to Create a new database or Restore from a SQL Server backup or Copy Database (when copying to a new SQL Server database).

ISSUE: 2511 eMRD Functional Group – Physical tree update

ACTION: Modified the way PLCNs are displayed when an FLCN other than the top level (typically X/00) is selected, ie, when the user wants to see the PLCNs linked to an FLCN.
Only the linked PLCNs together with their parents up to Indenture Level A are displayed.
The linked PLCNs appear in black and the non-linked ones appear in red (as before).
The (linked) PLCN tree loads much more quickly than it used to and displaying the hierarchy of each linked PLCN gives a much better appreciation of its position in the Physical structure.

ISSUE: 2512 eMRD Copy or Reference Task option – Increased Functionality

ACTION: Implemented a new function to allow a Task to be copied to or referenced by multiple other instances.
This function is accessed by right-clicking a Task on the Main screen and then selecting which LCN/ALCs to copy it to as a standalone task or as a Slave task.
If the selected Task is a Slave, it can only be copied.

ISSUE: 2513 eMRD ACRN set and ACRNs libraries – Clean-up function

ACTION: Provided functionality on the ACRN and ACRN Sets Library forms to select and delete multiple ACRNs and ACRN Sets.
Only the unassigned ACRNs / ACRN Sets can be deleted from the Library forms.

ISSUE: 2578 Extra TMP Task validation required

ACTION: Added a validation when creating/editing a TMP Task to check that an LCN with a Throw Away On Condition Task does not have any other TMP Task.
Also added an Anomaly check under Business Rules to find any existing instances of this situation.

ISSUE: 2580 Need a Fix DB option to tidy up Nomenclatures and Ext. Nomenclatures

ACTION: Added a Fix Database option to replace commas, periods and multiple contiguous spaces with a single space in Nomenclature and Extended Nomenclature.

ISSUE: 2581 Need an option to find all uses of a PartNo/Cage

ACTION: Modified the PartNo Library form to provide the ability to list all uses of a PartNo/Cage.
The WhereUsed button now provides the new function.
The Find/GoTo button re-implements the original WhereUsed function, ie, to locate the PartNo/Cage in the structure and optionally go to it.

ISSUE: 2583 Servicing tasks not showing in the Main form Servicing Tree

ACTION: On the Main form Servicing Tree, there is now the ability to drill down into a servicing to see the tasks linked to it.

ISSUE: 2586 Normal and Extended PSS Signup reports require different Supervisor column heading

ACTION: Modified the ADO Reports Parameters form to provide an option for the user to select ‘P’ or ‘S’ for the supervisor column heading for Normal and Extended Signup reports.
The associated reports were modified to use the user’s selection.

Patches for eMRD and eLSA were released on Issue Tracker earlier today (27 March 2015). The patches resulted from minor bugs and enhancements in eMRD and further intensive ADAASS Functionality testing in eLSA. See this recent post for further info. As stated in that article, we are now providing installable patches so there is no need to copy files into program directories anymore.

The patches were released under the following Issue Numbers:

eMRD – Issue# 2358

eLSA – Issue# 2359

PLEASE READ THE ISSUES FULLY BEFORE INSTALLING OR UPDATING.

For online release notes for eMRD and eLSA see these links:

http://www.les.net.au/less/index.php/our-software/emrd-release-notes/

http://www.les.net.au/less/index.php/our-software/elsa-release-notes/

As always if you have any queries or need assistance please don’t hesitate to call or email us.

Hi All,

As you are probably aware we recently released updates to our complete suite of applications as Version 3.3.0. Shortly afterwards some of our users detected a couple bugs in eMRD which we rectified through patch release V3.3.1 under Issue Tracker Issue# 2251.

Since that release other minor bugs have surfaced – we have also taken this maintenance opportunity to roll in some enhancement requests that have been waiting in the wings. Have a look here to see the bugs and enhancements addressed in the next patch of eMRD (V3.3.2). This patch will be released by Friday 27 March – so please keep an eye for release notification (either through Issue Tracker or through a Blog Site release Notice).

We are trying something new with the release of patch V3.3.2. With previous patches, LES provided a zip file with the one or more individual files that the user needs to copy into the appropriate directory or directories. This has worked OK up til now, but with Microsoft operating systems becoming more protective of sensitive folders such as Program Files and Program Data, we felt it was time to make our patch releases a little more sophisticated. What this means for you, is all you will have to do is download the patch and run it (as you would an installation file). The patch will automatically update the requisite files for you. We have tested it here and it works well – we’ll be interested in your feedback.

Also – as we advised recently, eMRD and eLSA now have ADAASS functionality (for producing ADAASS Project Databases). We have been user testing this rigorously and have been quite happy with the results – particularly in the integrated way a WSDB and ADAASS Data Set can be created. Today, we discovered a small ADAASS related bug in eLSA, so an eLSA patch (V3.3.1) will also be released within the week or so.

eMRD, eLORA, eLSA and eMRD Companion V3.3.0 were released on Issue Tracker earlier today (09 Feb 15). There were many changes across the suite including some that affected all applications (hence the complete suite release). For those users of one or more of eMRD, eLORA and/or eLSA these applications must be replaced at the same time.

The applications were released under the following Issue Numbers:

eMRD – Issue# 2239

eLORA – Issue# 2242

eLSA – Issue# 2240

eMRD Companion – Issue# 2243

PLEASE READ THE ISSUES FULLY BEFORE INSTALLING OR UPDATING.

For online release notes for eMRD and eLORA see these links:

http://www.les.net.au/less/index.php/our-software/emrd-release-notes/

http://www.les.net.au/less/index.php/our-software/elora-release-notes/

http://www.les.net.au/less/index.php/our-software/elsa-release-notes/

http://www.les.net.au/less/index.php/our-software/emrd-companion-release-notes/

As always if you have any queries or need assistance please don’t hesitate to call or email us.

In the past few years LES staff have worked on a number of acquisition projects that have required a WSDB and associated ADAASS. The traditional way of completing these tasks was to build these two products separately. The challenge we faced when doing this was always ensuring the WSDB CI’s and their respective ADAASS Header data aligned (eg part numbers, LCN and ALCs). Several events would occur during the project which would require us to spend many man hours realigning WSDB and ADAASS. Examples of these are:

An LCN renumber (which happens a few times during an Acquisition Project)
Update of IPC/IPB info (where most of the BDS information is sourced for ADAASS)

While this was necessity to ensure a good product was delivered – it really frustrated us as we knew there was a better way of doing this. The best way (in our opinion) was to manage this data (during Acquisition anyway) in the one database. So we modified eMRD and eLSA to do this. This article provides an overview of the ADAASS Functionality we have built in to eMRD and eLSA. This functionality will be available in V3.3.0 of eMRD and eLSA. We designed this with Acquisition in mind (ie producing an ADAASS Project Database for upload to the running system ADAASS) – but if, after reading this, you see application in through life we would be happy to hear from you.

eMRD already allows the creation of Modified Classical LCNs. Given that most PIDs in an ADAASS are not CIs (or Items Under Analysis in WSDB speak) then Modified Classical LCNs suit themselves well to grouping BDS data for ADAASS purposes (see the figure below). Note LCN AXX000101/00 are BDS meant for a System ADAASS (yes this can be done for Functional LCNs!).

eMRD was modified to allow the creation of a special ADAASS “task” (see the figure below) with a task code of XXXXXAA. NOTE: This works just as well for Physical LCNs as for Functional LCNs. This means that this method can be used for creating System ADAASSs. Using a special task code like this allows for straight forward batch deletion of these tasks once the ADAASS Project Tool is complete and this data is no longer need in the WSDB. Also, careful assignment of the Modified Classical LCNs (eg having them all end in “ZZ”) also allows for straight forward batch deletion at a later date.

Assigning BDS (PIDs) (see the figure below) and assessing docs is straight forward in the task and very little time is actually spent in the task doing this. We have modified the Task Provisioning screen to help with this process. Even though 99% of the time the parts from the previously created Modified Classical BDS LCNs will be added – any LCN can be added here and appear in the ADAASS PID listing.

ADAASS Tasks in eMRD (see the figure below) are easily recognisable.

eLSA is used to manage the ADAASS data (see the figures below), validate and export to an ADAASS Project Tool back end database.

Please remember we have designed this for the Acquisition phase but there may be some use for this in-service. If you want to know more about this functionality please contact us or leave a comment.