Factory calibration Sample Clauses

Factory calibration. The gauge sold by the manufacturer must be calibrated at least in the factory; the drop height must be equal to the value calculated on the basis of the mass of the falling weight and the spring constant. The setup parameters and the control values typifying the measuring unit and the relating tolerances must be stated in writing by the manufacturer.
AutoNDA by SimpleDocs
Factory calibration. The H-340SDI is calibrated in the factory with an apparatus which provides a constant 4in/hour flow rate. The water exiting from the bottom of the rain gauge is captured in a precision graduated cylinder. After 100 bucket tips or more have occurred, the flow is stopped and the volume in the graduated cylinder is measured. The procedure is as follows: 1. Issue an extended “aXRA!” (reset accumulator) SDI-12 command. 2. Empty the graduated cylinder. 3. Start the water flow into the funnel. 4. Wait until at least 100 bucket tips have occurred (1% resolution). 5. Stop the water flow. 6. Observe and record the water volume in the graduated cylinder. 7. Use the formula below to compute the actual rainfall accumulation. 8. Issue a SDI-12 “aM!” measure command and record the “smart bucket” accumulation. 9. Compare the difference between the smart bucket rainfall reading the rainfall volume in the graduated cylinder. 10. Adjust the counterweight as needed and repeat until the two values are identical or within an acceptable difference. The rainfall “volume” equation below converts the volume in the graduated cylinder (mL) into the equivalent rainfall (in inches) captured by an 8 inch diameter funnel. NmL × L × 61.025 in3 RAINFALLinches = 1000mL L = NmL × 1.21405x10−3inches π (4.0in)2 Other related equations of interest: = RAINFALLinches × 60 min hr N min hr

Related to Factory calibration

  • Calibration The comparison of a measurement system or device of unverified accuracy with a measurement system of known and greater accuracy to detect deviation of the unverified measurement system from required performance specifications (of the unverified measurement system or device) and to quantify all measured values to applicable units of the international system of units.

  • TRUNK FORECASTING 57.1. CLEC shall provide forecasts for traffic utilization over trunk groups. Orders for trunks that exceed forecasted quantities for forecasted locations will be accommodated as facilities and/or equipment are available. Sprint shall make all reasonable efforts and cooperate in good faith to develop alternative solutions to accommodate orders when facilities are not available. Company forecast information must be provided by CLEC to Sprint twice a year. The initial trunk forecast meeting should take place soon after the first implementation meeting. A forecast should be provided at or prior to the first implementation meeting. The semi-annual forecasts shall project trunk gain/loss on a monthly basis for the forecast period, and shall include: 57.1.1. Semi-annual forecasted trunk quantities (which include baseline data that reflect actual Tandem and end office Local Interconnection and meet point trunks and Tandem-subtending Local Interconnection end office equivalent trunk requirements) for no more than two years (current plus one year); 57.1.2. The use of Common Language Location Identifier (CLLI-MSG), which are described in Telcordia documents BR 000-000-000 and BR 000-000-000; 57.1.3. Description of major network projects that affect the other Party will be provided in the semi-annual forecasts. Major network projects include but are not limited to trunking or network rearrangements, shifts in anticipated traffic patterns, or other activities by CLEC that are reflected by a significant increase or decrease in trunking demand for the following forecasting period. 57.1.4. Parties shall meet to review and reconcile the forecasts if forecasts vary significantly.

  • Temperature Measurement Temperature will be measured by the nearest automatic Melbourne Bureau of Meteorology Monitoring Station for example (but not limited to): Melbourne, Moorabbin, Dunns Hill, Melbourne Airport, Frankston, and Point Xxxxxx. At the commencement of each project, the onsite management and employee representatives shall agree which is to be the applicable automatic weather monitoring station.

  • Timescales 5.1 Each Party shall use its reasonable endeavours to undertake its responsibilities detailed in this Agreement within the timescales specified or, if no timescales are specified, as soon as reasonably practicable, but time shall not be of the essence.

  • Mileage Measurement Where required, the mileage measurement for LIS rate elements is determined in the same manner as the mileage measurement for V&H methodology as outlined in NECA Tariff No. 4.

  • Service Level Expectations Without limiting any other requirements of the Agreement, the Service Provider shall meet or exceed the following standards, policies, and guidelines:

  • Scaling “Scaling,” as used herein, involves:

  • Reliability Reliability targets (Mean Time Between Failures (MTBF)) are defined in the technical specifications as set out in the Contract. Notwithstanding any possible application of penalties relating to reliability defined in the Contract, Goods shall remain covered by the warranty defined in this Article 16 as long as the reliability commitments have not been reached.

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

  • Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx Xxxxxxx Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

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