SupportParameter Metadata Sample Clauses

SupportParameter Metadata. ParameterName The name of the SupportParameter. ParameterDescription (Optional) Description of the SupportParameter. ParameterKey (optional) Identification Key that can be used to refer to that Physical Parameter, if needed for cross-reference. ParameterType Similarly to the ParameterType entry of the PhysicalParameter metadata, we define a list of UCDs describing the Support Parameter Types: - loc Location/Pointing - loc.ephem Ephemeris (location) - loc.att Attitude (orientation) - xxx.xxx Incidence angle - inst Instrument Status - inst.mode Instrument Mode - inst.integrationTime Integration Time - inst.integrationBand Integration Bandwidth - inst.other To be specified in ParameterDescription -... (to be completed) InstrumentKey The Instrument associated with the DataSet are listed in the InstrumentDescription entry at the DataSet level. This entry contains the list of the associated Instruments referenced by their InstrumentKey. AxisKey The Instrument associated with the DataSet are listed in theAxisFrame entry at the DataSet level. This entry contains the list of the associated Instruments referenced by their AxisKey. Unit (Optional)
AutoNDA by SimpleDocs

Related to SupportParameter Metadata

  • Interoperability To the extent required by applicable law, Cisco shall provide You with the interface information needed to achieve interoperability between the Software and another independently created program. Cisco will provide this interface information at Your written request after you pay Cisco’s licensing fees (if any). You will keep this information in strict confidence and strictly follow any applicable terms and conditions upon which Cisco makes such information available.

  • Interface A defined set of transmission facilities that separate Load Zones and that separate the NYCA from adjacent Control Areas. Investor-Owned Transmission Owners. A Transmission Owner that is owned by private investors. At the present time these include: Central Xxxxxx Gas & Electric Corporation, Consolidated Edison Company of New York, Inc., New York State Electric & Gas Corporation, Niagara Mohawk Power Corporation, Orange and Rockland Utilities, Inc., and Rochester Gas and Electric Corporation.

  • Interfaces Bellcore’s GR-446-CORE defines the interface between the administration system and LIDB including specific message formats. (Bellcore’s TR-NWP-000029, Section 10)

  • Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.

  • COVID-19 Protocols Contractor will abide by all applicable COVID-19 protocols set forth in the District’s Reopening and COVID-19 Mitigation Plan and the safety guidelines for COVID-19 prevention established by the California Department of Public Health and the Ventura County Department of Public Health.

  • Architecture The Private Improvements shall have architectural features, detailing, and design elements in accordance with the Project Schematic Drawings. All accessory screening walls or fences, if necessary, shall use similar primary material, color, and detailing as on the Private Improvements.

  • Vehicle Base Specifications Note: The actual vehicle awarded may exceed the minimum specifications stated below. The Authorized User may elect to add additional Options, delete Options, or substitute a vehicle feature that is an Option with another Option. See Contract Section III.6

  • Purchase Order Flip via Ariba Network (AN) The online process allows suppliers to submit invoices via the AN for catalog and non- catalog goods and services. Contractors have the ability to create an invoice directly from their Inbox in their AN account by simply “flipping” the purchase order into an invoice. This option does not require any special software or technical capabilities. For the purposes of this section, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider of MFMP the right and license to use, reproduce, transmit, distribute, and publicly display within the system the information outlined above. In addition, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider the right and license to reproduce and display within the system the Contractor’s trademarks, system marks, logos, trade dress, or other branding designation that identifies the products made available by the Contractor under the Contract.

  • Functionality Customer is entitled to additional functionality previously purchased or bundled with the software if available in the version or update released on or after the start date of the Agreement. Customer acknowledges that certain functionality in current and previous software versions may not be available in future upgrades. Added functionality may require additional paid services (clinical and technical) to configure and support.

  • Network Interface Device (NID) 2.7.1 The NID is defined as any means of interconnection of end-user customer premises wiring to BellSouth’s distribution plant, such as a cross-connect device used for that purpose. The NID is a single-line termination device or that portion of a multiple-line termination device required to terminate a single line or circuit at the premises. The NID features two independent xxxxxxxx or divisions that separate the service provider’s network from the end user’s customer-premises wiring. Each chamber or division contains the appropriate connection points or posts to which the service provider and the end user each make their connections. The NID provides a protective ground connection and is capable of terminating cables such as twisted pair cable.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!