Transcript No Slide Title

LSAR Interface – ASENT Export
Last revised: 12/16/2009
Introduction
ASENT provides a powerful LSAR Interface so that design
analysis data can be easily passed to your Logistics group. This
time-saving feature allows a wide range of data to be passed in an
automated fashion. For example, the product tree structure, failure
rate and MTBF information, FMEA/FMECA data, RCM Analysis
results, Availability, and Maintenance tasks can all be passed from
ASENT to the LSAR database.
ASENT’S LSAR Interface
ASENT
DB
LSAR
DB
Any 1388-2B
compliant
LSAR tool
Invoking ASENT’s LSAR Interface
From the Session
Manager, rightclick on a project
and select the
LSAR interface
option to invoke
the tool.
ASET
DB
ASENT’s LSAR Interface
ASET
DB
There are Preview
and Create options
available for both
Exports and
Imports. The
preview option
takes you through a
mock run and
highlights any
problems. The
Create option
actually starts the
Export/Import.
ASENT’s LSAR Interface
Here, the Export
screen is displayed.
The user has
complete control
over what data is
passed between
ASENT and
EAGLE. An Initial
load can populate
the LSAR database
or just updates or
changes can be
passed.
ASENT’s LSAR Interface
When the ‘Type of Export’ is set to ‘Initial’, then all the data
necessary to establish an LSAR structure, including the XA, XB,
XC, HA, and HG tables are written out to the fullfile.
If ‘FMECA Data’ is checked, then the BL record is written out for
the selected function and phase. Also, the BA, BB, and BD tables
are populated for each node in the FMECA tree.
If criticality numbers have been calculated in ASENT and severity
levels have been defined, then the BK table is populated. Tables
BG, BH, BI, and BJ are populated as part of the Failure Mode
data export.
Exporting Maintainability Data
If ‘MTTR Data’ is checked, then the HG table entries for the
assemblies are created. Also, for initial exports the AA, AB, AG, and
GA tables are populated.
Tables CA, CB, CC, and CD are populated with assembly, task and
subtask data, associated with the selected Maintainability prediction.
Exporting Maintainability Data
If certain data already exists in
the LSA database, then you can
easily tell ASENT exactly
which tables to export.
To exclude certain table data
merely uncheck its checkbox.
ASET
DB
Exporting Maintainability Data
If an initial export is
being performed and
Maintainability data is
being exported, then
the user will see this
screen.
Determines 4th character in the
task code. HGLNCAA
Determines 5th character in the
task code. HGLNCAA
The values of these
settings will
influence the task
code values for the
C tables.
In this case the task
codes would be
HGLNCAA.
The 3rd character in the task code HGLNCAA represents the 3rd
character in the SMR Code. If blank it is determined by this selection.
Diagnostic Report
ASET
DB
After the user
enters the cage
code and any other
prompted for
information, then
the export runs.
This screen shows
a diagnostics report
for the export. This
can be saved off or
printed by clicking
on the appropriate
button.
Viewing the Export File
ASET
DB
By selecting the
File, View options
the user can select
their export file.
This screen shows
a sample export
file that was
created by
ASENT’s LSAR
interface. The ‘A’
on the far left of
each line indicates
an ADD, followed
by the table name
(XB, XC, XH,
etc…)
ASENT’s LSAR Interface – Common Questions
Q: If my failure rates have changed in ASENT or some descriptive data
was changed and I want the changes reflected in EAGLE what do I do?
A: Export the ASENT data as Change/Follow-on Data. In EAGLE
import the fullfile just like you normally would.
Q: If my product tree structure has changed in ASENT and some new
assemblies or boards have been added, how do I pass this to EAGLE?
A: You would accomplish this in two passes: 1) Export the ASENT data
as an initial load and import this fullfile into EAGLE. This will create
entries for the new items and EAGLE will kick out those that already
exist. 2) Export the ASENT data as Change/Follow-on Data. In EAGLE
import the fullfile just like you normally would and now all of the failure
rates and other data should be updated.
From ASENT, export
Reliability, FMECA, RCM,
and Maintainability data to
EAGLE or any 1388-2B
compliant Logistics tool.
ASENT combines a comprehensive export
feature with its ability to import existing
LSAR data, so that design trade-offs for
upgrades and redesigns can be quickly
accessed.
Data exported from
ASENT to EAGLE
Product Tree Structure
Reliability Prediction Data
FMECA Data
RAMS DB
RCM Analysis Results
Maintainability Data
Availability Data
LSAR DB
Data Exchange
ASENT, EAGLE, and AIMSS are trademarks of Raytheon Company. Microsoft and SQL Server are registered trademarks of Microsoft Corporation.