Domains and Coding Sample Clauses

Domains and Coding. The geologic model for the Pxxxxx gold-bearing zones has been developed in two stages. Initially, the CX and Range Front fault zones have been developed based on the geologic logging information. Second, the high-grade portions within the fault zones are defined through a combination of geostatistical and manual methods. The CX and Range Front fault zones have been identified in drill holes based on information defined in the drill logs. This process included a review of core photos (where available) and re-logging of stored core/cuttings from historic drill holes where required. The fault zone intervals were displayed along the drill-hole traces and the subsequent geologic interpretation based on this data was conducted on cross sections. The interpreted sectional polylines were then linked to produce 3-dimensional wireframe solids. The CX and Range Front fault zones are shown in cross section in Figure 17-2 and in an isometric view in Figure 17-3. It should be noted that geologic model has been extended above the current surface topography in the area of the CX pit. The information gained from including the mined-out portion of this zone enhances the estimation of the remaining CX resource. The final contained resource in this zone is limited to the current topographic surface. Figure 17-2: Cross Sectional View of CX and Range Front Fault Zones Figure 17-3: Isometric View of CX and Range Front Fault Zones Following the generation of the fault zones, the high-grade gold-bearing domains (HG zone) were defined as follows. The drill-hole samples were composited to standard 5-foot sample lengths (this step is described in more detail in section 17.4). Samples contained within the fault zones were evaluated both visually and statistically (described in detail in section 17.5) and an indicator threshold of 0.1 opt Au was selected to define the HG portion of the fault zone. Samples within each of the faults were assigned a value of zero (0) if the grades were below 0.1 opt Au and a value of one (1) if the grade was above 0.1 opt Au. Probability estimations were then conducted defining the likelihood of the presence of the HG zone located within the fault zone boundaries. The indicator probabilities within blocks are estimated using an inverse distance weighting (IDW) technique with search directions controlled by “relative elevations” as described below. Although the CX and Range Front fault zones occur as relatively planar structures, local undulations exist as...
Sample 1
AutoNDA by SimpleDocs

Related to Domains and Coding

  • Procurement of Goods and Services (a) If the HSP is subject to the procurement provisions of the BPSAA, the HSP will abide by all directives and guidelines issued by the Management Board of Cabinet that are applicable to the HSP pursuant to the BPSAA. (b) If the HSP is not subject to the procurement provisions of the BPSAA, the HSP will have a procurement policy in place that requires the acquisition of supplies, equipment or services valued at over $25,000 through a competitive process that ensures the best value for funds expended. If the HSP acquires supplies, equipment or services with the Funding it will do so through a process that is consistent with this policy.

  • Other Methods of Procurement of Goods and Works The following table specifies the methods of procurement, other than International Competitive Bidding, which may be used for goods and works. The Procurement Plan shall specify the circumstances under which such methods may be used: (a) National Competitive Bidding (b) Shopping (c) Direct Contracting

  • Particular Methods of Procurement of Goods and Works International Competitive Bidding. Goods and works shall be procured under contracts awarded on the basis of International Competitive Bidding.

  • Trunk Group Architecture and Traffic Routing 5.2.1 The Parties shall jointly establish Access Toll Connecting Trunks between CLEC and CBT by which they will jointly provide Tandem-transported Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic from and to CLEC's Customers. 5.2.2 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access and non-translated Toll Free traffic (e.g., 800/888) to allow CLEC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier that is connected to the CBT access Tandem. 5.2.3 The Access Toll Connecting Trunks shall be one-way or two-way trunks, as mutually agreed, connecting an End Office Switch that CLEC utilizes to provide Telephone Exchange Service and Switched Exchange Access Service in the given LATA to an access Tandem Switch CBT utilizes to provide Exchange Access in the LATA.

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • License Types (a) A Team License shall mean a subscription license that provides a limited number of licenses to a set amount of developers for a named Customer. Customer must procure enough active licenses for each individual who has Programmatic Access. A Team License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer. A Team License cannot be used as a floating license. (b) A Project License shall mean a subscription license which covers one named Customer application. The license fees are based on the total number of developers working on a named project, regardless of whether such developers are directly using the Licensed Product. For the purposes of pricing and license administration, a “Project Group” is deemed to be a distinct Customer software team within a Customer’s business unit that works towards a distinct business purpose for the benefit of a single application. Customer is required to identify the name of each such Project Group to Syncfusion; such name must be unambiguous in nature. It is acknowledged and agreed by Customer that each identified Project Group shall exist for a valid business purpose and not just as a means for consolidating software licenses to minimize license fees that are otherwise due. If, in the sole opinion of Syncfusion, multiple Customer teams would each individually meet the above definition of a Project Group, such multiple teams shall not be combined for the purpose of consolidating licenses under a single Project Group. Customer is responsible for providing information about each such Project Group to Syncfusion. By entering into this Agreement, Customer represents that after the effective date, it will not withhold information that Syncfusion requires to properly license each such Project Group, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement. (c) A Division License shall mean a subscription license which will cover one named Division and allow for development work on more than one project within such Division. A Division shall mean a business unit within Customer’s organization that works towards a distinct business purpose. Customer is required to identify the name of such Division to Syncfusion; such name must be unambiguous in nature. License fee determinations will be at the sole discretion of Syncfusion and be based on such factors including, but not limited to, Customer’s Division size, developer count, and the scope of the Division’s business purpose. By entering into this Agreement, Customer acknowledges that it is responsible for providing information about the named Customer Division to Syncfusion sufficient for Syncfusion to price the Division License, and Customer represents that it will not withhold information that Syncfusion requires to properly license each such named Customer division, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement. (d) A Global License shall mean a subscription license for all development for a named Customer, where the license fees are based on the overall size of a named Customer. A Global License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer. (e) A Retail License shall mean a single named user, non-transferable license to use the Licensed Product. Retail Licenses will only made available to Customers in Syncfusion’s sole discretion and only when the number of such End-Users is finite and readily ascertainable. Accordingly, Syncfusion will make a determination as to whether or not the provision of Retail Licenses is appropriate under the circumstances applicable to any given Customer, and Syncfusion reserves the right, in its sole discretion, to refuse to make available Retail Licenses to a Customer and instead require a given Customer to procure a Project License, Division License, or Global License as circumstances dictate. A Retail License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer.

  • Other Methods of Procurement of Goods and Works. The following table specifies the methods of procurement, other than International Competitive Bidding, which may be used for goods and works. The Procurement Plan shall specify the circumstances under which such methods may be used: (a) National Competitive Bidding (b) Shopping (c) Direct Contracting

  • Particular Methods of Procurement of Goods Works and Services (other than Consultants’ Services)

  • Procurement of Goods and Works Except as ADB may otherwise agree, Goods and Works shall only be procured on the basis of the methods of procurement set forth below:

  • Safety Glasses Section 1. The City shall supply prescription safety glasses with plastic lenses to employees who are required to wear safety glasses and who are members of the classifications contained in Appendix C to this contract. Safety glasses which are authorized must be industrial grade safety glasses which meet or exceed the requirements of ANSI Specification Z87. 1. All employees who are required to wear safety glasses shall also be required to wear side xxxxxxx, either permanent or snap-on, whenever an eye hazard exists. Solid tinted glasses will not be approved unless required by prescription. Photogray, progressive, scratch coating and/or anti-glare lenses may be considered for those employees who primarily work outdoors or as prescribed. In the event that additional classes are identified as needing either prescription safety glasses or protective eyewear, such classes may be added to the classification list in Appendix C upon approval of PAGE and the City. Section 2. The City agrees to pay the full cost of required prescription safety glasses, with frames not to exceed $75.00. This excludes the cost of the eye examination which will be the responsibility of the employee. The effected employees will be allowed one (1) replacement of safety glasses every two (2) years. In the event the safety glasses become lost, unserviceable, or broken on the job, the employee must present a written request for replacement to the Department Head and Human Resources Director. If the employee breaks his safety glasses while on the job, the Department shall replace the glasses at no cost to the employee. The replacement of lost glasses or glasses that are broken off the job will be at the discretion of the Department Head and Human Resources Director. If an employee has been provided safety glasses by the City, the employee shall be permitted to retain possession of the glasses after separation from the City without reimbursing the City for any costs associated with the glasses. Section 3. An employee who is required to wear prescription safety glasses must present a written request to his department head or designated representative. Section 4. The employee must obtain a current prescription and the employee is authorized the use of sick leave not to exceed two (2) hours to accomplish this examination. The employee will obtain a purchase order from the Department Head prior to ordering the safety glasses. The employee will present the purchase order to the appropriate vendor when ordering. The vendor will contact the appropriate Department Head when the glasses are ready for delivery. The Department Head will then notify the employee who will present himself at the vendor for fitting and pickup. Section 5. In the event a probationary employee has been issued safety glasses and terminates his employment with the City for any reason during the probationary period, he shall be required to reimburse the City for any expenses incurred in the purchase of safety glasses.

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