<?xml version="1.0" encoding="UTF-8"?>

<!-- <!DOCTYPE sddlschema SYSTEM "sddlschema.xsd">-->

<sddl>

<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<!-- -->
<!--  SDDL Name:  ENG_TRIGGER.SDDL -->
<!-- -->
<!--  Purpose:      This SDDL file defines the ENG_TRIGGER relation.-->
<!-- -->
<!--  Modification History:-->
<!-- -->
<!--    Date       PR      Who                       Reason-->
<!--  - - - -    - - - -   - -    - - - - - - - - - - - - - - - - - - - - - -->
<!--  11/14/00   44862     Baum   Original implementation-->
<lm>  07/03/03   48821     CTB   Converted to XML format </lm> <!-- last mod -->
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
 

    <record name="ENG_TRIGGER_TYPE"> 
 
        <description>This relation is used to name the trigger codes so that
                   reports can use a name rather than a number and to 
                   provide standardized names for constants used in header 
                   files for software processing GS acquisition telemetry. </description>


            <field name="eng_trigger">
                    <type>I4</type>
                    <description>A numeric code indicating the processing to be
                         performed when a change in telemetry value has been
                         detected. A zero value is not a trigger but that entry
                         is used to indicated that the telemetry value should
                         be saved. </description>
            </field>

            <field name="eng_trigger_name">
                    <type>C30</type>
                    <description>A name having for a trigger that implies the purpose
                         of the processing of the telemetry item. </description>
            </field>

    </record>
 
 
    <relation name="eng_trigger">
 
        <type>ENG_TRIGGER_TYPE</type>

        <description>Engineering Telemetry Trigger Relation</description>

        <subsystem_using>OPUS</subsystem_using>

        <index name="eng_trigger_1">
                <type>unique clustered</type>
                <field name="eng_trigger"/>
        </index>

    </relation>
</sddl>
