Memory Sharing Sample Clauses

Memory Sharing. For VM mode, unless Senselock ELis reset (for example, the device is unplugged or the S4Control()function is used to send COTROL_RESET_DEVICE control code); otherwise after Senselock ELEXF is executed, the system will not clear automatically the contents of external RAM while the contents of internal RAM will be cleared each time. For XA mode, all the memory will not be cleared automatically. Using this feature, we can use the memory ―that is not cleared automatically‖ as ―shared memory‖. This can help share data between different EXFs and can also use them to buffer data among consecutive calls. For instance, if a program in Senselock ELneeds to receive data larger than 250 bytes, it can be done through a process similar to the following sample: #include “ses_v3.h” typedef struct { unsigned short offset; unsigned xxxx xxx; unsigned char buff[1]; } IO_PACKAGE; DEFINE_AT(unsigned char, big_buff[512], 0x400, RAM_EXT); IO_PACKAGE *input = NULL; void main() { input = (IO_PACKAGE *)pbInBuff; LE16_TO_CC(&input->len); if (input->len != 0) { memcpy(big_buff + input->offset, input->buff, input->len); _exit(); } /* now got enough data and you can add operations here… */ _exit(); } In the codes, we use two macros: DEFINE_AT and LE16_TO_CC. The former can define a variable at the specified address of the specified memory area while the use of the latter will be explained later in the topic of ―Big-Endian and Little-Endian‖, so you can temporarily think of it as useless. In this sample, we have defined a 512-byte array of unsigned char at 0x400 of the external memory. Furthermore, we have also declared a structure where offset is designed to specify the location where the data input this time are stored in the variable big_buff. len indicates the length of the data input this time while buff saves the inputted data. Suppose the 512-byte data shall be transported to Senselock ELbefore they are operated, the above codes can be executed four times. At each execution, the following offsets: 0, 128, 256, 384 and their corresponding 128-byte data are transmitted in respectively. At the fifth execution, the variable len is set to 0, indicating no additional data can be transmitted in. At this point, the codes have acquired sufficient 512-byte data and can continue to execute the required functions.
AutoNDA by SimpleDocs

Related to Memory Sharing

  • Scholarly Sharing On an ad hoc basis, the Authorized Users may transmit to a third party, in hard copy or electronically, minimal, insubstantial amounts or a portion of the Licensed Materials for personal use or scholarly, educational, or scientific research or professional use in the nature of collaboration, comment, or scholarly exchange of ideas but in no case for resale or commercial purposes or in a manner that would substitute for direct access to the Licensed Materials via services offered by the Distributor and/or the Publisher.

  • JOB SHARING North Bay; Perth-Huron; Peterborough, Victoria & Haliburton; Sarnia- Lambton Taking into consideration the fact that the Employer wishes to retain well- qualified staff who are unable or prefer not to provide a full-time commitment and the job-sharing can enable this to happen, the parties agree to the following provisions: (a) Job-sharing requests with regard to full-time positions shall be considered on an individual basis, and the Employer shall reserve the right to determine the appropriateness of such arrangements, including the number of job-shared positions after discussions with the Union at the Labour Management Committee. (b) Any incumbent full-time Nurse wishing to share their position may do so without having their half (½) of the position posted. The other half (½) of the job-sharing position will be posted, and selection will be in accordance with the Collective Agreement. (c) Save and except as provided for herein, all job-sharers shall be treated as part-time employees and shall receive percentage in lieu of benefits. (d) If one (1) of the job-sharers leaves the arrangement, their position will be posted. If there is no successful applicant to the position, the shared position must revert to a full-time position. The remaining Nurse will have the option of continuing the full-time position or reverting to a part-time position for which they are qualified. If they do not continue full-time, the position must be posted in accordance with the Collective Agreement. (e) Posted schedules for the job-sharers shall be based on the schedules that would apply to a full-time Nurse holding that position. Such schedule shall conform to the scheduling provisions for full- time. (f) Total hours worked by the two job-sharers shall be equal to one full- time position. The division of these hours over the schedule shall be determined by mutual agreement between the two Nurses and the immediate Supervisor. This does not exclude the Nurses from opportunities for extra available work. (g) Each job-sharer may exchange shifts with their partner, as well as with other Nurses in accordance with the Collective Agreement, provided such exchange creates no additional labour cost to the Employer and meets continuity requirements. (h) It is expected that both job-sharers will cover each other’s absences including incidental illnesses and vacation. If, because of unavoidable circumstances, one cannot cover the other, the Supervisor must be notified to book coverage. Job-sharers are not required to cover for their partners in the case or prolonged or extended absences but may be offered the opportunity to do so. (i) Job-sharers will not be required to work in total more paid holidays than would one full-time Nurse, unless mutually agreed otherwise. Job-sharers will have the right to determine which partner works the scheduled holidays. (j) Either party may discontinue the arrangement with one month’s written notice and the employees shall revert to their former status without posting if such positions are still available. 14.14 Christmas/New Year’s Xxxxxxxxxxxx, Xxxxxxxx & Haliburton

  • Leave Sharing Consistent with RCW 28A.400.380 and WAC 392-126, a leave sharing program is established as follows: A. A district employee is eligible to receive donated leave if: 1. The staff member suffers from, or has a relative or household member suffering from, an extraordinary or severe illness, injury, impairment, or physical or mental condition which as caused, or is likely to cause, the staff member to: a. Go on leave without pay status; or b. Terminate his/her employment; 2. The staff member’s absence and the use of shared leave are justified; 3. The staff member has depleted, or will shortly deplete, his/her annual leave and sick leave reserves; 4. The staff member has abided by district rules regarding sick leave use; and 5. The staff member has diligently pursued and been found to be ineligible to receive industrial insurance benefits. Any employee who wishes to receive leave under this provision shall submit a request in writing to the personnel office. The employee shall submit, prior to leave sharing approval, documentation from a licensed physician or other authorized health care practitioner verifying the severe or extraordinary nature and expected duration of the condition. Employees meeting the criteria indicated above shall be eligible for leave sharing. A staff member shall not receive more leave than the number of normal work days remaining in the current school year. In the event that the condition requiring the employee’s absence continues beyond the current school year, the employee shall not receive a total of more than 261 days of leave. B. District employees may donate leave as follows: 1. An employee who does not earn annual leave (vacation) and who has an accrued sick leave balance of more than sixty (60) days may request that the superintendent or designee transfer a specified amount of sick leave to another staff member authorized to receive such leave. A staff member may request to transfer no more than six (6) days of sick leave during any twelve (12) month period, and may not request a transfer that would result in an accrued sick leave balance of fewer than sixty (60) days. Employees who accrue vacation must transfer vacation days prior to sick leave days. Sick leave as defined in RCW 28A.58.099 (28A.400.300) means leaves for illness, injury, and emergencies. The number of leave days transferred shall not exceed the amount authorized by the donating staff member. 2. The value of any leave transferred under this policy which remains unused shall be returned to its original value to the staff member who donated the leave. To the extent administratively feasible, the value of unused leave which was transferred by more than one staff member shall be returned on a pro-rata value basis.

  • Profit Sharing Profit sharing, bonuses, or other similar compensation of any kind paid by CM/GC to its employees.

  • Line Sharing 4.1 ‘Line Sharing’ is an arrangement by which Verizon facilitates ICG’s provision of ADSL (in accordance with T1.413), Splitterless ADSL (in accordance with T1.419), RADSL (in accordance with TR # 59), Multiple Virtual Line (MVL (a proprietary technology)), or any other xDSL technology that is presumed to be acceptable for shared line deployment in accordance with FCC rules, to a particular Customer location over an existing copper Loop that is being used simultaneously by Verizon to provide analog circuit-switched voice grade service to that Customer by making available to ICG, solely for ICG’s own use, the frequency range above the voice band on the same copper Loop required by ICG to provide such services. This Section 4 addresses Line Sharing over loops that are entirely copper loops. 4.2 In accordance with, but only to the extent required by Applicable Law, Verizon shall provide Line Sharing to ICG for ICG’s provision of ADSL (in accordance with T1.413), Splitterless ADSL (in accordance with T1.419), RADSL (in accordance with TR # 59), MVL (a proprietary technology), or any other xDSL technology that is presumed to be acceptable for shared line deployment in accordance with FCC rules, on the terms and conditions set forth herein. In order for a Loop to be eligible for Line Sharing, the following conditions must be satisfied for the duration of the Line Sharing arrangement: (i) the Loop must consist of a copper loop compatible with an xDSL service that is presumed to be acceptable for shared-line deployment in accordance with FCC rules; (ii) Verizon must be providing simultaneous circuit-switched analog voice grade service to the Customer served by the Loop in question; (iii) the Verizon Customer’s dial tone must originate from a Verizon End Office Switch in the Wire Center where the Line Sharing arrangement is being requested; and (iv) the xDSL technology to be deployed by ICG on that Loop must not significantly degrade the performance of other services provided on that Loop. 4.3 Verizon shall make Line Sharing available to ICG at the rates set forth in the Pricing Attachment. In addition to the recurring and nonrecurring charges shown in the Pricing Attachment for Line Sharing itself, the following rates shown in the Pricing Attachment and in Verizon ’s applicable Tariffs are among those that may apply to a Line Sharing arrangement: (i) prequalification charges to determine whether a Loop is xDSL compatible (i.e., compatible with an xDSL service that is presumed to be acceptable for shared-line deployment in accordance with FCC rules); (ii) engineering query charges, engineering work order charges, or Loop conditioning (Digital Designed Loop) charges; (iii) charges associated with Collocation activities requested by ICG; and (iv) misdirected dispatch charges, charges for installation or repair, manual intervention surcharges, trouble isolation charges, and pair swap/line and station transfer charges. 4.4 The following ordering procedures shall apply to Line Sharing: 4.4.1 To determine whether a Loop qualifies for Line Sharing, the Loop must first be prequalified to determine if it is xDSL compatible. ICG must utilize the mechanized or manual Loop qualification processes described in the terms applicable to xDSL and Digital Designed Loops to make this determination. 4.4.2 ICG shall place orders for Line Sharing by delivering to Verizon a valid electronic transmittal service order or other mutually agreed upon type of service order. Such service order shall be provided in accordance with industry format and specifications or such format and specifications as may be agreed to by the Parties. 4.4.3 If the Loop is prequalified by ICG through the Loop prequalification database, and if a positive response is received and followed by receipt of ICG’s valid, accurate and pre-qualified service order for Line Sharing, Verizon will return an LSR confirmation within twenty-four

  • Cost Sharing a) With respect to the funding in C6.1a), should there be an amount of employee co-pay, the Trust shall advise boards what that amount shall be. Unless advised otherwise, there will be no deductions upon the Participation Date. b) Any further cost sharing or funding arrangements as per previous local collective agreements in effect as of August 31, 2014 remain status quo.

  • Sick Leave Sharing The program permits employees to donate sick leave to a fellow employee who is suffering from or has a relative or household member suffering from an extraordinary or severe illness, injury, impairment, or physical, or mental condition which has caused or is likely to cause the employee to take leave without pay or to terminate employment

  • Information Sharing (a) HHSC will provide the MA Dual SNP with resources regarding the LTSS covered by Medicaid in accordance with this section. (b) Texas Medicaid benefits are described in Attachment B, Texas Medicaid Summary of Benefits. The MA Dual SNP must include the Texas Medicaid Summary of Benefits in its Member Handbook for the MA Product. (c) HHSC and the MA Dual SNP will identify and share information, such as the following: (1) HHSC will provide the MA Dual SNP with links to online Medicaid LTSS provider information for the traditional fee-for-service and STAR+PLUS programs. Within thirty (30) business days after receiving such information, the MA Dual SNP must post a link to this information on its website. (2) The MA Dual SNP must: A) Notify Dual Eligible Members and Other Dual SNP Members, via its member communication materials that information concerning Medicaid provider participation is available on the MA Dual SNP’s website; and B) Notify Dual Eligible Members and Other Dual SNP Members that they may request written copies of Medicaid Provider directories by contacting their STAR+PLUS MCO, C) Assist the Dual Eligible Members and Other Dual SNP Members in obtaining printed copies of Medicaid Provider directories from their STAR+PLUS MCO, and D) Verify that the Dual Eligible Members and Other Dual SNP Member received the requested directory. (3) The MA Dual SNP must notify Network Providers that information concerning Medicaid provider participation is available on the MA Dual SNP’s website. The MA Dual SNP must provide this notice in the Network Provider agreement, Network Provider manuals, bulletins, faxes, policies and procedures, provider manual updates, or other contractual documents. (4) The MA Dual SNP must have written procedures for ensuring that Dual Eligible Members and Other Dual SNP Members have access to the services identified in the MA Product, including policies regarding network adequacy that are consistent with the requirements of the MA Agreement. The MA Dual SNP must provide HHSC with a copy of these policies no later than 5 business days after a request. (d) The MA Dual SNP must encourage Network Provider SNF to electronically submit to the HHSC Medicaid claims administrator a resident transaction notice within 72 hours after a Dual Eligible Member’s admission or discharge from the nursing facility, in accordance with 40 Tex. Admin. Code § 19.2615. (e) The MA Dual SNP is required to notify HHSC of significant changes to the terms of its CMS contract within 10 business days of such changes, which may include but is not limited to the following: changes in the services areas; plan benefit package (PBP) changes; non-renewal; terminations or deficiencies of the contract; notices of intent to deny; and any novation agreements. Plans must submit any CMS warning letters or corrective action plans within 10 business days of receipt to the HHSC point-of- contact identified in Section 9.06. (f) The MA Dual SNP is required to notify HHSC in the event the Plan receives less than a 3.0 star Medicare rating on either its Part C or Part D scores. The Plan must provide an outline of the steps proposed or implemented to improve the low score. (g) The MA Dual SNP must participate in meetings with HHSC, telephonic or in person, relating to the health care provided under this Agreement and their compliance with this Agreement's terms, and to timely provide any necessary information and data upon HHSC's request. (h) The MA Dual SNP, upon request from HHSC, must provide all documents it provides to and receives from CMS, within 30 days of the HHSC request, unless an extension is granted by HHSC.

  • Job Sharing / Time Sharing (a) Job sharing shall be interpreted to mean two employees sharing one full- time position (10 shifts bi-weekly). (b) Time sharing shall be interpreted to mean two employees sharing one full line (14 shifts bi-weekly). Clarifying Note: One full-time and a regular part-time “shadow” does not constitute a time sharing arrangement. (c) The introduction of job/time sharing arrangements in a Home will be subject to mutual agreement between the Union and the Employer. Job/time sharing requests shall be considered on an individual basis. Such approval will not be unreasonably withheld. (d) The employees involved in job share/ time sharing are entitled to all the regular part-time provisions except those which are modified as follows: i) Schedules and scheduling language shall be established by the mutual agreement of the Union and the Home. This will include the division of hours between the job/time sharers. ii) Each job/time sharer may exchange shifts with her or his partner as well as other employees as provided by the Collective Agreement. Employees who are currently in a job/time sharing arrangement and are full-time will retain that status and be covered by the full-time provisions of the collective agreement. For clarity, this grandparents employees in time sharing arrangements, not positions. When individuals leave these positions, the vacant position will be posted under (f) and (g) below.

  • Data Sharing The GRANTEE BENEFICIARY agrees to share data with the AGENCY as deemed necessary by AGENCY, in its sole discretion, for expenditure validation, trend review, and performance monitoring.

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