Table of Contents. iii

Transcription

1 LSAR Interface

2

3 Table of Contents Logistics Data Interface... 1 Introduction... 1 Overview... 1 The Toolbar... 2 The Main Menu... 2 Using the Information Window... 2 Data Requirements... 3 Export... 5 The Export Preview... 5 Exporting Data to the LSAR... 6 Import The Import Preview Importing Data from the LSAR Index iii

4

5 Logistics Data Interface Introduction Overview The Logistics Data Interface tool provides the two way interface with the Logistics folks and their LSAR database. While primarily driven by the requirements of EAGLE, any B compliant LSAR tool should be able to be used on the other side of the interface. The communications between the two tool sets (ASENT and the LSAR tools) is via the B flat text file that is specified in the Military Standard (now Handbook). Using the Logistics Data Interface tool you can: Export a complete initial load for a new LSAR Export updates of ASENT Data (Reliability, FMECA or Maintainability) Create Reliability, FMECA or Maintainability product trees from LSAR data. Update Reliability, FMECA or Maintainability product trees from LSAR data. Preview LSAR files to determine the type of data that they contain and the possible data that can be imported from the LSAR data File. Preview the ASENT project data to determine the LSAR entries which can be generated from the ASENT data. View any text data file, such as a MS1388-2B flat file. Edit, print or save to file, the diagnostics from importing or exporting or the file you selected to view. The Main Panel of the Interface is shown below: 1

6 LSAR Interface The Information Window in the center of the Main Panel is not initially open when the tool is first invoked. The window is activated to display the diagnostics from Previews, Imports, Exports and also used to view files. The window is fully editable. You can erase and type in data or comments. Buttons are provided to allow you to print the contents of the window, or save it to file. The status bar at the bottom of the main panel is comprised of 3 panels to keep you abreast of the progress of the current process. The left panel displays messages identifying the actions currently being conducted. The center panel is a progress bar that will expand as the process reached completion. The right panel, of course, is a clock so you can see how much overtime you are putting in. The Toolbar The toolbar has a button for each item in the main menu grouped in the same order as the menu items, providing 2 different ways of initiating most actions. The options menu item is the only exception, not having a button on the toolbar. The first two buttons are for the menu items in the File menu, the next two for the items in the Export menu, then the Import menu, and finally a button that brings up the Help file. Holding the mouse over one of these buttons brings up a Hint box that identifies the function of the button. Button Function Closes down the Logistics Interface and returns to the Session Manager View a file (normally LSAR Data, but any file will work with Text and ASCII files working best.) Check ASENT data for export. Export ASENT Data to LSAR. Check LSAR Data for import. Import LSAR Data to ASENT. Display this Help File. The Main Menu The following lists the menu options and the commands found under each menu item. The list also shows the underlined letter ( Hot Key ) that can be used as alternative to selecting the menu item with the mouse or using the arrow keys. Menu Options Description File View Allows you to use the Diagnostics window to view a file. Exit Returns to the Session Manager Export Preview Check ASENT data for export. Create Export ASENT Data to LSAR. Import Preview Check LSAR Data for import. Create Import LSAR Data to ASENT. Options Font Set the font used in the Diagnostics Window. Help Contents Display this Help File. How to Use Help About Using the Information Window Open the tutorial on how to use Help Files. Display ASENT Release Information. The Information window is a highly flexible display which allows you to tailor the presentation as well as edit the contents of the window. Buttons are provided to allow you to print the contents of the window, or save it to file. The Options menu of the main menu allows you to set the font of the window. Selecting this option opens a Font Dialog. 2

7 Logistics Data Interface Select the font, color, size and any special effects desired (in this case, Bold) and press OK. The data in the information window is now displayed in the selected font. Pressing the Print button will send the contents of the window to your Windows Default Printer. Pressing the Save button opens a Save File dialog. The initial directory is the last directory you chose a file from in the Logistics Data Interface, either for import, export or viewing. If this is the first time the tool has been opened, it starts in the ASENT\Reports directory. The contents of the window are saved in Rich Text Format which is generally directly importable into most all word processors. You can edit the contents of the window using the same techniques you use in Word or NotePad, including using the Windows Clipboard for copying, cutting, and pasting. Clicking th OK option button ( Data Requirements ) closes the information window. 3

8 LSAR Interface There is a great difference in the architecture and intent of the LSAR data base and that of ASENT. The Logistics Data Interface was designed to allow the LSAR tool to import the LSAR data file with the minimum of diagnostics or kick out. Both databases have parent-child relationship which require that certain records be in the database before the child records can be entered. The LSAR tools often allow items in the product tree that have no identified parent. The orphaned items will not be imported into ASENT until they are identified with a parent in the product tree. The creation of BK records depend on having Severity Levels established in the FMECA. Also without good criticality data, there is no purpose in creating BK records. Similarly, most failure mode level LSAR data requires good criticality values, so if the criticality calculation did not successfully complete, the BF, BG, BH, BI and BJ records of the LSAR will not be generated. In the FMECA, a next effect is defined as the failure mode of a higher level item. During the import of LSAR data, next effects can only be linked if the description of the next higher effect of an item is the same as the description of a failure mode on the parent item. There are also key pieces of data that are required for a record before it can be added to the database. For the LSAR, the LCN is the key piece of data. Assemblies without LCNs cannot be exported. LCNs can be defined in both the FMECA and the Reliability Product Tree. If FMECA data is selected and LCN data has been entered for the FMECA assembly, this will be the first priority for selection. If LCN data is not entered and the FMECA node is linked to a node in the Reliability Product Tree and LCN data has been entered for the assembly in the Reliability tree, then the Reliability Tree LCN will be used for the assembly. If only Reliability Data is selected, only those assemblies with LCNs will be exported. If MTTR data is selected, only those assemblies in the Maintainability Product tree which are linked to the Reliability Tree and where the Reliability Tree has LCN data will be exported. For ASENT the Part Number is a key piece of data for parts. To import parts, the HG record in the LSAR, which contains the part number, must exist to import parts. The part number is assumed to be unique within a project. Two parts with the same part number are assumed to be identical parts. Alternate configurations may cause some confusion in reporting. The top level of an alternate configuration will generally be reported as having no parent in the tree, although during import, the items will import correctly when the ALC is chosen. This is due to the fact that the preview is looking for a parent with the same ALC, and will not find one. Viewing Files You can check the contents of an LSAR data file, or most any other text file for that matter, by selecting the View option from the File menu. Alternatively you can press the View File button ( which allows you to navigate to and select the file of interest. ) on the Toolbar. This opens a Open File windows dialog 4

9 Logistics Data Interface All file types and extensions are shown in this dialog. The initial directory is the last directory you chose a file from in the Logistics Data Interface, either for import, export or viewing. If this is the first time the tool has been opened, it starts in the ASENT\Reports directory. Select the desired file and press the Open button. The dialog closes and the filename is shown in the left panel of the status bar while the file is loaded. After a brief delay the contents of the file are displayed. Export The Export Preview The Export preview allows you to quickly see what type of ASENT data is available for export and which tables of the LSAR can be populated with the existing data, or what data needs to be added/corrected to allow a productive export. The Preview can be selected by selecting the Preview option of the Export menu or by clicking on the Export Preview button ( ) on the toolbar. The Export Options panel is then presented. The items that are active on this panel are determined by the data available in ASENT. In the example above, the selected project does not have any Maintainability data so the MTTR Data check box is inactive and the selection window for the MTTR Scenario and Prediction is not displayed. The project does have FMECA data though, and so the FMECA related items are active. You can export with only a reliability product tree, but the number of tables in the LSAR that will be populated will be significantly less than when FMECA data is available. Having MTTR data also expands the number of tables that can be populated by the export. Select the options you desire and press OK. After a brief delay, the results of the preview are displayed in the information window. 5

10 LSAR Interface Exporting Data to the LSAR The Export function provides a number of different options to allow you to tailor the contents of the export file to most productively support the development and maintenance of the LSAR. It is strongly suggested that you run the Export Preview prior to exporting data to identify any missing data and disconnects in the ASENT data of the selected project. The Export is initiated by selecting the Create option of the Export menu or by clicking on the Export Data button ( the toolbar. The Export Options panel is presented. ) on 6

11 Logistics Data Interface The items that are active on this panel are determined by the data available in ASENT. The Tree Scope button group is only active if the selected Type of Export is Update/Follow On. For an initial export, the entire product tree is required by the LSAR. The default for the End Item Acronym Code (EIAC) is the first 10 characters of the project name. Enter the EIAC and the Alternate LCN Code for the export. Select the Export data (Reliability, FMECA, MTTR) and select the function/phase or scenario/prediction as appropriate. When the selected Type of Export is Initial the LCN structure edit panel becomes active, allowing you to enter the LCN structure that will be used to create the XA record. This structure is not checked for validity during export, so about any nonblank entry will work. The structure can be easily edited in the LSAR Tool. The checkbox in the lower right side of the panel, concerning descriptions, applies only to Failure Modes. The long description is the default used for the failure modes, with the short description used when the long description is not populated. Checking this box will result in a description being generated in the LSAR of <short desc> - <long desc> when both fields have data. Press the OK button when the option setting correctly reflect your desired export. A panel of export table, that is tables in the LSAR, is then presented. 7

12 LSAR Interface All the tables that are available for the type of export you selected are enabled and checked. For example, since the type of export is not Initial the XA, XB and XC tables are not available. The HA data is available for export but not typically used in an update, so it is available, but not checked. You can check it if you want HA entries added to your export. Uncheck any tables you do not want exported and press OK. If you selected to export MTTR Data, there are a number of selections used in the maintainability tables of the LSAR which are not used in ASENT. The MTTR Export Options panel is presented to allow you to specify these items of data for the LSAR. 8

13 Logistics Data Interface The upper portion of the panel allows you to determine the Task Codes for repair and preventive tasks based on the typical selections, or you can type in the Task Code of your choice. When the drop down menus are used to build the task codes, the task code input windows are disabled,(grayed out) and display the task code that will be used based on the selections in the drop downs. Alternatively, you can click on the edit button next to the task code of interest. The input window becomes active and another Ok and Cancel button is presented on the upper right side of the panel. Type in your task code and press the Ok button to enter your custom task code. The lower portion of the panel is for input/selection of other items used in the Maintainability Related ( C Table ) LMI data. The Maintenance Specialty Code is a free form input, allowing you to type in whatever the expected specialty/job code for the maintenance personnel. The remainder of the edit windows are selection lists from the valid entries listed in the Mil-Spec. Select the items which reflect the project data that you are exporting. The two check boxes at the bottom of the panel specify the criticality of repair, and the data used for task descriptions. The ASENT Maintainability suite allows you to enter a narrative for each task. This can be much more illuminating to the maintainer or logistician than the task description, particularly where the same task appears multiple times in a detailed task list. As an example, the Quarter Turn Quick Disconnect may appear 3 times in a task list, each with different quantities. The narratives for these could be Remove 5 connectors on top of cabinet, Remove 7 connectors on left side of cabinet, and Remove 4 connectors to remove card guide. Checking this box will allow the narratives to be used in place of the task descriptions where narrative data exists. Press the OK button when the option settings correctly reflect your desired export. If the selected Type of Export is Initial, a panel is presented to input the CAGE code for the assemblies in the product tree. ASENT does not utilize manufacturer data in any way, and it is assumed that the majority of the assemblies in the product tree are manufactured by the same group. Enter the CAGE code for this group, as this will be the default cage code used if one has 9

14 LSAR Interface not been entered for the item in ASENT. If parts are being exported, the CAGE of is used as a default for all parts without cage codes. The CAGE codes are easily modified in the LSAR tool after importing the LSAR data file. The CAGE codes and HA records are only generated for the Initial export. Click the OK button when the CAGE Code is correct. The next panel present is the standard Windows Save File dialog that allows you to specify the directory and file name for the new export file, or select an existing file to overwrite the previous contents. Select the directory and file name and press the Save button. The process of generating the export data begins with the progress of the process being conveyed to you via the message panel and the progress bar panel of the status bar. When the export is complete, the information window becomes active and the results of the export is displayed. The data below is an example of a typical Initial export: Diagnostics Report Data Export from the DEMOCD_PRJ 2 the Mov Project Generated at: Thursday 12 July 2001 at 10:7 am The assigned End Item Acronym Code of the export is DEMOCD_PRJ FMECA Data was selected from the Computer / Normal Operation Function / Phase. MTTR Data was selected from the Test / Test Scenario / Prediction. Unable to associate the new node assembly from the MTTR Tree PN: with a LCN MTTR data for this assembly can not be exported Wrote out XA Record The LCN structure provided during the export was not verified as accurately reflecting the LCNs of the Export Data. Wrote out XB Records for 5 Assemblies. Wrote out System XC Record Wrote out HA Records for 5 Assemblies. Wrote out HG Records for 5 Assemblies. Used CAGE code provided (96214) for Assemblies. Wrote out BL Record for this Function/Phase. Wrote out BA, BB, BD & BK Records for 5 Assemblies. Export of FMECA Data complete. Wrote out AA record for System Node. Wrote out AB record for System Node using default "Peace Time" Operational Requirement Indicator code Wrote out AG record for System Node using default 2000 hour annual operating requirement Wrote out GA record. 10

15 Logistics Data Interface Exported MTTR Information for 1 Assemblies. Wrote out CA, CB, CC & CD records. CA records were generated using a default task frequency of 1.0 Import The Import Preview The Import preview allows you to quickly see what type of data is available in a given LSAR data file for import, the questions you will be asked during the import (such as selecting one on the alternate configurations) and what data needs to be added/corrected to allow a productive import. The Preview can be selected by selecting the Preview option of the Import menu or by clicking on the Import Preview button ( ) on the toolbar. LSAR data files can have more than one project in them, so the first step in the preview is to select the project of interest. From your knowledge of the LSAR, select the options that reflect the LSAR data. If the LSAR contains LCNs for piece parts, then select Assemblies and Parts. The lowest level items on the tree will be assumed to be parts and the data available for creating the ASENT part entries will be analyzed. The standard failure rate data in MS1388-2B data records is in failures per hour, but often the data is inadvertently entered in failures per million hours (since this is a commonly used rate) and selecting the lower option will assure that the failure rates get correctly brought into ASENT. You are also given the option of using the LCN for Assembly Reference Designators where the data in the LSAR for Assembly Reference Designators is blank or missing. Press the Ok button, the message panel and progress bar indicate the processing activity being conducted, and the results of the preview are displayed in the information window. 11

16 LSAR Interface Importing Data from the LSAR The import function allows you to create Reliability Product Tree data in addition to FMECA data and Maintainability Data from the LSAR. This provides a major productivity lift over re-entering the data for system upgrades or modification of systems for which the original R&M data is not readily available. The import option is currently only available for B text fullfiles. It is strongly suggested that you run the Import Preview prior to importing data to identify any missing data and disconnects in the LSAR data of the selected file. The Import is initiated by selecting the Create option of the Import menu or by clicking on the Import Data button ( toolbar. A standard windows Open File dialog is present to allow you to select the LSAR data file of interest. ) on the Navigate to the directory containing the LSAR data file, select the file and click the Open button. The Import Options panel is presented. 12

17 Logistics Data Interface LSAR data files can have more than one project in them, so the first step in the import is to select the project of interest. From your knowledge of the LSAR, select the options that reflect the LSAR data. If the LSAR contains LCNs for piece parts, then select Assemblies and Parts. The lowest level items on the tree will be assumed to be parts and the data available for creating the ASENT part entries will be analyzed. The standard failure rate data in MS1388-2B data records is in failures per hour, but often the data is inadvertently entered in failures per million hours (since this is a commonly used rate) and selecting the lower option will assure that the failure rates get correctly brought into ASENT. You are also given the option of using the LCN for Assembly Reference Designators where the data in the LSAR for Assembly Reference Designators is blank or missing. Press the OK button when the option settings correctly reflect the LSAR data and the data you desire to import. If there is more than one configuration (Alternate LCN Code or ALC) in the LSAR data file, the next step is to select the configuration of interest. Each project in ASENT has only one Reliability Product tree configurations, and alternate configurations are handled by creating additional projects for each configuration and naming the project to reflect the intent or use of the alternate configuration. Select the configuration of interest and press the OK button. If Assemblies & Parts were selected on the import options panel, the next step is identifying the parts in the LSAR, and determining whether the parts, or a similar part exists in ASENT. This is typically the longest part of the import process and can take several minutes for large projects with many parts. 13

18 LSAR Interface Where similar parts are found in ASENT, a panel is presented with the list of candidate similar parts. If you see one that is the same part as in the LSAR file, select the part in the list and press the OK. Pressing Skip will create a Miscellaneous part in the selected project library using the part number form the LSAR data file. Following creation of the parts required for import, the construction of the product trees begins. If a reliability Product Tree exists for the project, then a confirmation panel warning of the pending deletion of the previous tree. Pressing No aborts the import. Pressing Yes continues with import and the panels of the status bar display the process of creating the new Reliability Product Tree. The next step is to process FMECA data, providing FMECA data was available in the LSAR and was selected by the user on the Import Options panel. The tool checks to see if a failure mode library exists, that is, some FMECA work has previously been done on the project. If a failure mode library does not exist, a panel is presented with a list of existing failure mode libraries. 14

19 Logistics Data Interface Selecting a library and pressing OK will create a failure mode library for the selected project by copying the contents of the library selected from the project list. When the panel is initially presented the COMMON_FMD91 library is highlighted because it is a common default. If the COMMON_FMD97 project exists, then this is a newer version of the same library, which contains various part types and their corresponding failure modes and failure mode ratios. The next step in the FMECA import is the creation of the Function and Phase. The user is presented with a panel to define the name of the function and phase names as well as the description of the phase. Unlike the Reliability Product Tree, a project may have multiple functions and phases, each phase with its own product tree. Subsequent imports of FMECA data will simply add additional phases to the FMECA. The combination of Function Name and Phase Name must be unique within a project. The date and time are added to the phase name to allow creation of additional phases with little or no input from the user and with very little risk of violating the uniqueness requirement noted above. The Description window may be filled by typing in a description, or you may select from the drop down list of descriptions from the BL table of the LSAR data file. Press the OK button when the names and descriptions are satisfactory. The status bar indicates the progress of building the FMECA product tree. The final step is to build the Maintainability Product tree, if MTTR Data was selected on the Import Options panel. Like the FMECA, a project may have many scenarios, so subsequent imports of MTTR data will simply add additional scenarios. The Scenario name must be unique within a project, so to avoid problems during, the scenarios are always named Import with the time and date added. So no user interaction is required during the import of the Maintainability Data. The status bar indicates the progress of building the Maintainability product tree. All the nodes on the tree are originally created and linked to their counterparts in the reliability tree. Following completion of the Maintainability Import, the information window is activated and the results of the import are presented. The example below shows some typical information based on the selections shown in the figures above. Diagnostics Report for the C:\build\bike_ff_full.txt LSAR File Current As Of: Thursday 12 July 2001 at 12:15 pm 15

20 LSAR Interface For the BICYCLE ASSEMBLY project. EIAC = BICYCLE Part Number APSE-801A was created as a "Miscellaneous" part during the import. Part Number B-BB-12-4MM was created as a "Miscellaneous" part during the import. Part Number B-CU-E5682 was created as a "Miscellaneous" part during the import. Part Number BC-336R was created as a "Miscellaneous" part during the import. Part Number CC-012F was created as a "Miscellaneous" part during the import. Part Number CC-012R was created as a "Miscellaneous" part during the import. Part Number CS-9488 was created as a "Miscellaneous" part during the import. Part Number CS-HG30-7 was created as a "Miscellaneous" part during the import. Part Number DK7-S380P SIS was created as a "Miscellaneous" part during the import. Part Number FD-CT91-T was created as a "Miscellaneous" part during the import. Part Number FSS-749 was created as a "Miscellaneous" part during the import. Part Number HBC-MT-3667 was created as a "Miscellaneous" part during the import. Part Number IT-851 was created as a "Miscellaneous" part during the import. Part Number JY-295A was created as a "Miscellaneous" part during the import. Part Number JY-990A was created as a "Miscellaneous" part during the import. Part Number KMC-UG50 was created as a "Miscellaneous" part during the import. Part Number MRX was created as a "Miscellaneous" part during the import. Part Number PA65E was created as a "Miscellaneous" part during the import. Part Number S-MM-9E was created as a "Miscellaneous" part during the import. Part Number SP-200 was created as a "Miscellaneous" part during the import. Part Number TU-604L was created as a "Miscellaneous" part during the import. Part Number VL-764EM was created as a "Miscellaneous" part during the import. Part Number YCS-301F was created as a "Miscellaneous" part during the import. Added 13 assemblies to the product tree. Added 26 parts to the product tree. Initiated New FMECA libraries for the Project. Added 13 assemblies to the FMECA product tree. Added 26 parts to the FMECA product tree. Added 21 Failure Modes to the Failure Mode Library. Added 10 Failure Modes to the FMECA product tree. Unable to link Failure Modes to Next Higher Effects due to differing descriptions. FMECA Import Completed. Please run the Check FMECA Utility to identify data which was not available from the LSAR file. Added 13 assemblies to the MTTR product tree. 16

21 Index D Data Requirements... 3 E Exporting Data to the LSAR... 6 I Importing Data from the LSAR O Overview... 1 T The Export Preview... 5 The Import Preview The Main Menu... 2 The Toolbar... 2 U Using the Information Window... 2 V Viewing Files