Step 1- Define System Data in terms of Fields and Frames
The first step in developing an Operator Debrief application is to define the format or record layout of operational and anomaly data that will be input to the Operator Debrief run-time tool. This raw, logged data is normally considered to be a "stream of consciousness" of a collection of operational data occurring during system operations, such as in an aircraft example, time, altitude, speed, and other telemetry readings. In this step of using the tools, you define all of the data elements that may be included in that stream of consciousness, and the characteristics of that data in terms of format. In this tool, a field is an individual parameter that is logged, such as altitude. A frame is a collection of fields, therefore representing the snapshot of data that is collected during normal operations. In order to allow the Operator Debrief tool to fit as many application scenarios as possible, this definition of fields and frames has been left open for user definition. YOU, as the user, have the flexibility to enter this data to fit any type of data format. Fields and frames are how the Operator Debrief will read this data in order to apply diagnostics, filtering logic and present the data to the operator/maintainer as a series of "snapshots" of system conditions at the time of any and all anomalies. FRAMES are a collection of fields, or stored parameters. Multiple frames can be defined to support applications that adapt the amount and type of data logged based upon certain conditions, such as phases of operation (start-up, take-off, cruise, land) or conditions surrounding special circumstances, such as the occurrence or reporting of an anomaly.
NOTE: If you are unable to define your logged data in the framework that we have provided, please contact Giordano Automation technical support. We have strived to make this an open architecture design that allows for definition of any type of data. We may be able to provide technical assistance or, we may be able to modify the data structure and tools to accommodate your requirements.
The screen below is the first screen in Step 1. The first view in Step 1 supports the definition of frame data. The frame view is displayed at startup. To select the frame view, press the radio button at the top left of the screen labeled Frames. In this view, you define each frame that will be contained in the logged data file. In our example below, we have defined two frames - one for fault data and one for operational data.
The following data is entered to define the frame:
Frame ID That identifying tag or code that identifies the frame.
Frame ID Location The bit location of where the Frame ID is located.
Frame ID Size The size, in bits, of the Frame ID
Frame Length The length of the frame, in bits. An entry should be made in this column only if the length is a fixed size.
Frame Length Location If the frame length is variable, enter the location of the frame length. For example, in our sample in the above screen, Frame 2 is of variable length, and the location of the current frame length is at bit 16 through 23 are entered the location of the current frame length.
Frame Length Location Size If the frame length is variable, enter the size of the frame length. For example, in our sample in the above screen, Frame 2 is of variable length, and the size of the current frame length is 8 bits. Therefore, the frame length can be found at bits 16 through 23.
Frame Time Location At what bit location in the frame is the time stamp.
Frame Time Size How many bits are allocated to the time stamp.
Frame Type Use the pull-down list box to select available choices. Choices are either "on Fault Exception" or "Periodic." On Fault Exception means that a logged entry is made to this frame when a fault is reported. Periodic means that a logged entry is made to this frame on a periodic basis.
The second view in Step 1 supports the definition of field data. Fields are entered into frames. To select the field view, press the radio button at the top left of the screen labeled Fields.
Fields are individually stored parameters. The following data is entered to define each field:
Frame - Identify the Frame ID that the field is associated with (In which frame is the field to be stored).
Field Data Type - Enter the data type for the field as 0 or 1. 0 indicates a Number; 1 indicates a String. Use the pulldown box to select "Number" or "String"
Field Location - The location, in the frame, where this field is stored.
Field Data Size - The size, in bits, allocated to this field.
User Interface Tag - A brief description of the data to be stored in the field. This will be later used in the Operator Debrief to display pertinent operational parameters to the user at the time of the anomaly. The description (tag) is limited to 255 characters. This tag acts as a means of identifying the field and does not get displayed to the user. A description for the user will be defined in Step 7.
User Interface Display Criteria defines the criteria for displaying this field during operator debrief session.
Not Displayed - The field will not be displayed during the debrief session.
Value at anomaly time - The value of the field at the time of the anomaly will be displayed.
For example, in our sample screen display, the ninth entry defines a field of data logged on "left
engine oil pressure." Left engine oil pressure is a field of data logged in frame 2. It is stored in the
289th bit location, and is 32 bits in length. It therefore occupies bit locations 289 through 320. The
User Interface Tag is "Left Engine Oil Pressure" which is used to identify the fields inside Operator
Debrief. Minimum of anomaly interval is selected. Therefore, let's assume that we will later define
an anomaly called "Hung Stall" and for that anomaly we will define a time interval of four seconds
prior to and 2 seconds after the anomaly occurs as the anomaly interval. The Operator Debrief
screen will provide a snapshot of operational data surrounding the Hung Stall, and the value to be
displayed for Left Engine Oil Pressure will be the minimum, or lowest, value during that anomaly
period. An example of what would therefore be displayed is shown in the figure below. In this Operator Debrief screen, note that the fault being displayed is Left Engine Hung Stall. The
parameter Left Engine Oil Pressure is included in the list of operational data characterizing that fault
(left engine has been abbreviated to LT here). The "LT Oil Press:" description of the parametric data
will be defined for this field later in Step 7.
When you are done, press Save, and then press Next. If you press Next without pressing Save, you
will be prompted to save your entries.