We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

Timestamp Sample Clauses

Timestamp. Each and every temporary and permanent intermittent employee (hereafter called “hourly employees”) must timestamp in and out as he/she begins his/her work shift/day, finishes his/her work shift/day, and takes meal breaks.
Timestamp. Timestamp is a string generated by the current server time, and can represent the generated random numbers of the server at some point with a nonce. How- ever, if the message is maliciously delayed by an adversary, it is likely to cause that the interval time for transmission delay is always equal or greater than ∆T , then the server rejects the legal login request all the time. However, there is no timestamp in our proposed scheme. Our proposed can avoid this condition.
Timestamp. The AG shall include a time stamp expressed in UTC in every Service Change and NOTIFY commands.
Timestamp. The timestamp value reports the setup time (which is always 0) and the connection time. As shown on the screen, the format is setup time / connection time. Timestamp values are measured in seconds. The CallID is a number that is used to identify a call when SIP is switching information. The length and value of the CallID are randomly generated. Message Log The Message Log is shown in Figure 20. This page shows most recent SIP and ISDN messages received or sent out in TG. The size of this page is approximately 100-150 lines depending on the content in each message. This page is useful to debug problems related to SIP or ISDN signaling. If you need longer history of the messages, the complete message log can be viewed at </var/tmp/message.log>. The size of the log file is 500KB. You may see three message log files in </var/tmp>: “message.log”, “message.log.1” and “message.log.2” with total 1500KB size limitation. “message.log” always contains most recent messages. When “message.log” is full, “message.log.1” will be copied to “message.log.2”, “message.log” will be copied to “message.log.1”, and “message.log” will be emptied to store new messages.
Timestamp. Timestamp is a marker that is used in a message to ensure the freshness of the message [16].

Related to Timestamp

  • System Timeout The system providing access to PHI COUNTY discloses to 11 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY 12 must provide an automatic timeout, requiring re-authentication of the user session after no more than 13 twenty (20) minutes of inactivity.

  • Timesheets Employees are required to submit complete and accurate electronic time sheets. In the event that a time sheet is revised or changed, the supervisor will promptly notify the employee.

  • DATA REPORTING a) CONTRACTOR shall agree to provide all data related to student information and billing information with XXX. CONTRACTOR shall agree to provide all data related to any and all sections of this contract and requested by and in the format require by the LEA. CONTRACTOR shall provide the LEA with invoices, attendance reports and progress reports for LEA students enrolled in CONTRACTOR’s NPS/A. b) Using forms developed by the CDE or as otherwise mutually agreed upon by CONTRACTOR and XXX, CONTRACTOR shall provide LEA, on a monthly basis, a written report of all incidents in which a statutory offense is committed by any LEA student, regardless if it results in a disciplinary action of suspension or expulsion. This includes all statutory offenses as described in Education Code sections 48900 and 48915. CONTRACTOR shall also include, in this monthly report, incidents resulting in the use of a behavioral restraint and/or seclusion even if they were not a result of a violation of Education Code sections 48900 and 48915. c) The LEA shall provide the CONTRACTORS with approved forms and/or format for such data including but not limited to invoicing, attendance reports and progress reports. The LEA may approve use of CONTRACTORS-provided forms at their discretion.

  • Extra Trips All trips other than regular runs or supplemental runs shall be awarded to drivers according to the following procedures: 9.7.1 All extra trips shall be assigned in compliance with the following section of this Agreement; provided, however, that no driver shall be eligible to work more than forty (40) hours in any workweek, exclusive of hours worked on Saturday or Sunday, when another eligible driver is available and would not be put into overtime. 9.7.2 Assignment of extra trips shall be made on the basis of a “Trip Board.” The most senior driver who signs up for the extra trip shall be awarded the trip. No driver may give up any extra trip or supplemental run or regular run previously awarded in order to take an extra trip, if Section 9.7.1 above would be violated. There shall be no pre-empting of regular runs by drivers who wish to take extra trips. 9.7.3 Trips are to be dated as they are received by the Transportation Office. All extra trips shall be awarded to the most senior appropriate driver signing the “Trip Board.” If the extra trip is posted before a driver’s regular run clock-out time, the driver has until the driver’s next regular run clock-in time to reply. If there is no reply, the dispatcher shall assign the extra trip to the next senior driver on the sign-up sheet. 9.7.4 Drivers shall not be eligible for extra trips during periods of absence due to illness. Drivers absent for personal illness on the last working day before a Saturday, Sunday, or holiday trip shall not be eligible to drive such trip and will lose his/her turn on the list until the process begins anew. Drivers absent for other reasons will be able to drive such trips provided they contact the Transportation Office by 3:30 p.m. on the last working day prior to the scheduled trip to verify their availability and confirm the start time of the trip. 9.7.5 The dispatch book shall be made available for driver viewing by the Transportation Office.

  • Localization Should any Seller Affiliate and any Customer Affiliate wish to enter into an agreement for the provision of Deliverables, Products and/or Services ("Local Agreement") in the Netherlands, Canada, Hong Kong, the United States, Australia, Ireland, Singapore, South Africa or the United Arab Emirates (as applicable) Local Agreement(s) can be agreed between the Parties and added as Exhibit(s) to this Agreement by way of addendum. The terms of this Agreement shall be incorporated into each such Local Agreement except to the extent that the Local Agreement expressly states that any amendments shall take precedence.

  • Customs Valuation The Parties shall determine the customs value of goods traded between them in accordance with the provisions of Article VII of GATT 1994 and the Customs Valuation Agreement.

  • Monthly Data Download Not later than fifteen (15) days after the end of each month, beginning with the month in which the Commencement Date occurs and ending with the Final Shared-Loss Recovery Month, Assuming Bank shall provide Receiver:

  • Searchable Whois Notwithstanding anything else in this Agreement, Registry Operator must offer a searchable Whois service compliant with the requirements described in Section 1.10 of Specification 4 of this Agreement. Registry Operator must make available the services only to authenticated users after they logged in by supplying proper credentials (i.e., user name and password). Registry Operator must issue such credentials exclusively to eligible users and institutions that supply sufficient proof of their legitimate interest in this feature (e.g., law enforcement agencies).

  • GRIEVANCE REPORT FORM Grievance # School District Distribution of Form 1. Superintendent

  • Customs Cooperation 1. The Parties shall enhance their cooperation in customs and customs-related matters. 2. The Parties affirm their commitment to the facilitation of the legitimate movement of goods and shall exchange expertise on measures to improve customs techniques and procedures and on computerized systems in accordance with this Agreement. 3. The Parties shall assist each other, in the areas within their competence, in the manner and under the conditions set out in this Chapter to ensure that the customs legislation is correctly applied, in particular by preventing, detecting, and investigating operations in breach of that legislation. 4. The Parties shall commit to: (a) pursuing the harmonization of documentation used in trade and data elements in accordance with international standards, for purposes of facilitating the flow of trade between them, in customs-related matters regarding the importation, exportation, and transit of goods; (b) intensifying cooperation between their customs laboratories and scientific departments and working towards the harmonization of customs laboratories methods ; (c) exchanging customs' experts of the Parties; (d) jointly organizing training programs on customs-related issues for the officials who participate directly in customs procedures; (e) developing effective mechanisms for communicating with the trade and business communities; (f) assisting each other, to the extent possible, in tariff classification, valuation, and determination of origin, for the preferential tariff treatment of imported goods, and other customs matters including non- preferential origin; (g) promoting strong and efficient intellectual property rights enforcement by customs authorities, regarding imports, exports, re-exports, transit, transshipments, and other customs procedures, and in particular regarding counterfeit goods; and (h) improving the security, while facilitating trade, of sea-container and other shipments from all locations that are imported into, trans-shipped through, or transiting Korea or Peru. The Parties agree that the objectives of the intensified and broadened cooperation include, but are not limited to: (i) working together to reinforce the customs- related aspects for securing the logistics chain of international trade; and (ii) coordinating positions, to the extent possible, in any multilateral fora where issues related to container security may be appropriately raised and discussed.