System Modernization Sample Clauses

System Modernization. Service Provider has experience with several large modernization efforts and has provided a methodology, approach, and services associated with this activity. Typically these services are divided into the following tasks:
Sample 1
AutoNDA by SimpleDocs
System Modernization. The parties agree to utilize electronic platforms for the claim and grievance handling, including those currently in use as well as future enhancements or platforms developed for claim and grievance handling. BNSF agrees to provide necessary training on the use of such systems, and the parties will work together on an appropriate implementation date.
Sample 1
System Modernization. 1. The parties agree to utilize electronic platforms for claim and grievance handling. In addition, the parties agree to discuss any future enhancements or platforms developed for claim and grievance handling. BNSF agrees to provide necessary access and training on the use of such systems, and the parties will work together on an appropriate implementation date. 2. The parties agree to utilize electronic platforms for all matters arising under the collective bargaining agreement, including but not limited to, employee notices, issuance of investigation notices, discipline letters, investigation transcripts and exhibits, and publication of bulletins and seniority rosters, etc. BNSF agrees to provide necessary access and training on the use of such systems, and the parties will work together on an appropriate implementation date. 3. The parties agree that if technical issues arise resulting in significant disruption to the claim and grievance or discipline handling process, either party may serve notice upon the other outlining the issue. The parties will meet within fifteen (15) days to discuss remedies to the issue. If the issue cannot be satisfactorily resolved within sixty (60) days following the meeting, either party may suspend the use of the electronic platform(s) until such time as the issue is resolved. 4. It is understood that the parties agree there are certain existing technical issues with the current systems and until those are resolved to the satisfaction of the general chairpersons, the system modernization will not be implemented.
Sample 1

Related to System Modernization

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

  • Start-Up and Synchronization Consistent with the mutually acceptable procedures of the Developer and Connecting Transmission Owner, the Developer is responsible for the proper synchronization of the Large Generating Facility to the New York State Transmission System in accordance with NYISO and Connecting Transmission Owner procedures and requirements.

  • Design Criteria and Standards All Projects/Services shall be performed in accordance with instructions, criteria and standards set forth by the Director.

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

  • System Upgrade Facilities and System Deliverability Upgrades Connecting Transmission Owner shall design, procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Appendix A hereto. The responsibility of the Developer for costs related to System Upgrade Facilities and System Deliverability Upgrades shall be determined in accordance with the provisions of Attachment S to the NYISO OATT.

  • Future Functionality You agree that Your purchases are not contingent on the delivery of any future functionality or features, or dependent on any oral or written public comments made by Us regarding future functionality or features.

  • System Description The wet detention basin is designed to trap 80% of sediment in runoff and maintain pre-development downstream peak flows. The basin has two forebays (smaller ponds) located at the low end of two grass xxxxxx. In addition to runoff conveyance, the grass xxxxxx also allow infiltration and filtering of pollutants, especially from smaller storms. The forebays are each 4 feet deep. They are connected to the main pool by 18 and 24-inch metal pipes that outlet onto a rock chute. The forebays will trap coarse sediments in runoff, such as road sands, thus reducing maintenance of the main basin. The main pool will trap the finer suspended sediment. To do this, the pond size, water level and outlet structures must be maintained as specified in this Agreement (see Figures 1, 2 and 3). The main basin receives runoff from a 67.1 acre drainage area (41.2 acres within the subdivision and 25.9 acres off-site drainage coming from the east). During high rainfall or snow melt events, the water level will temporarily rise and slowly drain down to the elevation of the control structure. The water level is controlled by a 12-inch concrete pipe extending through the berm in the northwest corner of the basin (see Figures 1 and 3). On the face of the 12-inch pipe, there is metal plate with a 3-inch drilled hole (orifice) with stone in front of it. This orifice controls the water level and causes the pond to temporarily rise during runoff events. Washed stone (1- 2” diameter) is placed in front of the orifice to prevent clogging. High flows may enter the grated concrete riser or flow over the rock lined emergency spillway. “As-built” construction drawings of the basin, showing actual dimensions, elevations, outlet structures, etc. will be recorded as an addendum(s) to this agreement within 60 days after [Municipality Name] accepts verification of construction from the project engineer.

  • Quality control system (i) The Contractor shall establish a quality control mechanism to ensure compliance with the provisions of this Agreement (the “Quality Assurance Plan” or “QAP”). (ii) The Contractor shall, within 30 (thirty) days of the Appointed Date, submit to the Authority’s Engineer its Quality Assurance Plan which shall include the following: (a) organisation, duties and responsibilities, procedures, inspections and documentation; (b) quality control mechanism including sampling and testing of Materials, test frequencies, standards, acceptance criteria, testing facilities, reporting, recording and interpretation of test results, approvals, check list for site activities, and proforma for testing and calibration in accordance with the Specifications for Road and Bridge Works issued by MORTH, relevant IRC specifications and Good Industry Practice; and (c) internal quality audit system. The Authority’s Engineer shall convey its approval to the Contractor within a period of 21 (twenty-one) days of receipt of the QAP stating the modifications, if any, required, and the Contractor shall incorporate those in the QAP to the extent required for conforming with the provisions of this Clause 11.2. (iii) The Contractor shall procure all documents, apparatus and instruments, fuel, consumables, water, electricity, labour, Materials, samples, and qualified personnel as are necessary for examining and testing the Project Assets and workmanship in accordance with the Quality Assurance Plan. (iv) The cost of testing of Construction, Materials and workmanship under this Article 11 shall be borne by the Contractor.

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