Conventions for Describing Data Values Sample Clauses

Conventions for Describing Data Values. ‌ The following table describes the data types used by the BCRC for its external interfaces (inbound and outbound). The formatting atandards used with each data type correspond to the requirements of the interface layout. This key is provided to augment the rules prescribing the formatting of data values that are provided within the PAP Data Exchange Layout fields. These standards should be used unless otherwise noted in the layouts. Table 3-7: Data Type Key Data Type/Field Formatting Standard Examples Numeric Zero through 9 (0-9) Padded with leading zeroes Populate empty fields with spaces Numeric (5): “12345” Numeric (5): “00045” Numeric (5): “ “ Alpha A through Z Left justified Non-populated bytes padded with spaces Alpha (12): “TEST EXAMPLE” Alpha (12): “EXAMPLE “ Alpha-Numeric A through Z (all alpha) + 0 through 9 (all numeric) Left justified Non-populated bytes padded with spaces Alphanum (8): “AB55823D” Alphanum (8): “MM236 " Text Left justified Non-populated bytes padded with spaces A through Z (all alpha) + 0 through 9 (all numeric) + special characters: Comma (,) Ampersand (&) Space ( ) Dash (-) Period (.) Single quote (‘) Colon (:) Semicolon (;) Number (#) Forward slash (/) At sign (@) Text (8): “AB55823D” Text (8): “XX299Y “ Text (18): “XXXXXXX@XXXXXX.XXX” Text (12): “ 000-000-0000” Text (12): “#34” Date Format is field specific Fill with all zeroes if empty (no spaces are permitted) CCYYMMDD (e.g. “19991022”) Open ended date: “00000000” Filler Populate with spaces - Internal Use Populate with spaces -
Sample 1Sample 2Sample 3See All (28)
AutoNDA by SimpleDocs
Conventions for Describing Data Values. The table below defines the data types used by COBC for their external interfaces (inbound and outbound). The formatting standard defined for each data type corresponds to the data type identified for each field within the interface layout. This key is provided to assist in understanding the rules behind the formatting of the data values in the layout fields. Data Type Key Data Type /‌ Field Formatting Standard Examples Numeric • Zero through 9 (0 € 9) • Padded with leading zeroes • Numeric (5): “12345” • Numeric (5): “00045” Alpha • A through Z • Left justified • Non-populated bytes padded with spaces • Alpha (12): “TEST EXAMPLE” • Alpha (12): “EXAMPLE “
Sample 1
Conventions for Describing Data Values. The table below describes the data types used by the COBC for its external interfaces (inbound and outbound). The Formatting Standards used with each data type correspond to the requirements of the interface layout. This key is provided to augment the rules prescribing the formatting of data values that are provided within the PAP Data Exchange Layouts. Data Type Key Data Type / Field Formatting Standard Examples
Sample 1

Related to Conventions for Describing Data Values

  • DATA FOR CALCULATIONS The initial calculations for any payments owing under this Agreement shall be based upon the valuations placed upon the Qualified Property by the Appraisal District in its annual certified appraisal roll submitted to the District pursuant to § 26.01 of the TEXAS TAX CODE in or about July of each year of this Agreement. The certified appraisal roll data shall form the basis from which any and all amounts due under this Agreement are calculated, and the data utilized by the Consultant will be adjusted as necessary to reflect any subsequent adjustments by the Appraisal District to the District’s appraisal roll. Any estimates used by the Consultant to make calculations as required by this Agreement shall be based on the best and most current information available. The Consultant shall from time to time adjust the data utilized to reflect actual amounts, subsequent adjustments by the Appraisal District to the District’s certified appraisal roll, or any other relevant changes to material items such as student counts or tax collections.

  • PAYEE DATA RECORD FORM STD 204: This form must be completed by all contractors that are not another state agency or other governmental entity.

  • NASPO ValuePoint Summary and Detailed Usage Reports In addition to other reports that may be required by this solicitation, the Contractor shall provide the following NASPO ValuePoint reports.

  • Shift Schedule The words "shift schedule" when used in this Agreement shall mean a timetable of the shifts and off days assigned to a position or group of positions which commences at the beginning of a pay period and includes one complete rotation of said shifts.

  • Reporting of Metered Data and Parameters 7.2.1 The grid connected Solar PV power plants will install necessary equipment for regular monitoring of solar irradiance (including GHI, DHI and solar radiation in the module plane), ambient air temperature, wind speed and other weather parameters and simultaneously for monitoring of the electric power (both DC and AC) generated from the Project.

  • Offense Level Calculations i. The base offense level is 7, pursuant to Guideline § 2B1.1(a)(1).

  • Benchmarking Report For the purposes of this Framework Schedule 12 “

  • Sentencing Guidelines Calculations 8. Defendant understands that in imposing sentence the Court will be guided by the United States Sentencing Guidelines. Defendant understands that the Sentencing Guidelines are advisory, not mandatory, but that the Court must consider the Guidelines in determining a reasonable sentence.

  • Contract Description The Description and Location of the Contract and related project(s) are as follows.

  • 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.

Time is Money Join Law Insider Premium to draft better contracts faster.