Priority monitoring methods Sample Clauses

Priority monitoring methods. Figure 3.3, shows that colonial (C) and species-specific breeding bird monitoring schemes (S) are the methods that would produce reliable population size estimates for most of the Priority 1-5 populations, while the January waterbird monitoring (IWC) counts (I) could provide adequate trend information for the vast majority of these populations.
AutoNDA by SimpleDocs

Related to Priority monitoring methods

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • SPECIALIZED SERVICE REQUIREMENTS In the event that the Participating Entity requires service or specialized performance requirements not addressed in this Contract (such as e- commerce specifications, specialized delivery requirements, or other specifications and requirements), the Participating Entity and the Supplier may enter into a separate, standalone agreement, apart from this Contract. Sourcewell, including its agents and employees, will not be made a party to a claim for breach of such agreement.

  • Initial Forecasts/Trunking Requirements Because Verizon’s trunking requirements will, at least during an initial period, be dependent on the Customer segments and service segments within Customer segments to whom CSTC decides to market its services, Verizon will be largely dependent on CSTC to provide accurate trunk forecasts for both inbound (from Verizon) and outbound (to Verizon) traffic. Verizon will, as an initial matter, provide the same number of trunks to terminate Reciprocal Compensation Traffic to CSTC as CSTC provides to terminate Reciprocal Compensation Traffic to Verizon. At Verizon’s discretion, when CSTC expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, Verizon will provide the number of trunks CSTC suggests; provided, however, that in all cases Verizon’s provision of the forecasted number of trunks to CSTC is conditioned on the following: that such forecast is based on reasonable engineering criteria, there are no capacity constraints, and CSTC’s previous forecasts have proven to be reliable and accurate.

  • Terminating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • Loop Testing/Trouble Reporting 2.1.6.1 Think 12 will be responsible for testing and isolating troubles on the Loops. Think 12 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, Think 12 will be required to provide the results of the Think 12 test which indicate a problem on the BellSouth provided Loop.

  • Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit B.

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

  • Monitoring Equipment 2.2.1 24-hour TSP air quality monitoring was performed using High Volume Sampler (HVS) located at each designated monitoring station. The HVS meets all the requirements of the Project Specific EM&A Manual. Portable direct reading dust meters were used to carry out the 1-hour TSP monitoring. Brand and model of the equipment is given in Table 2.1.

  • EODUF Packing Specifications 7.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

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