QUARTS DESIGN Sample Clauses

QUARTS DESIGN. We take a top-down approach to describing the design of Quarts. In Section IV-A, we give a walkthrough of a typical operation of Quarts by using, as an example, an RTCS for control of electric grids that uses a Kalman-filter controller [2]. Algorithm 2: collect_and_vote(Z, H, r, r−) 2 Zcoll ← collect_missing_measurements(Z, r); 3 Hcoll, rcoll ← collect_missing_state(H, r−); 4 S ← indices of entries in Zcoll; 5 send digest(S, rc−oll, r) to all voters; 8 success, Schosen , rc−hosen ← vote(r); 9 if success and rc−hosen = rc−oll and Schosen ⊆ S then 10 return True, Zcoll[Schosen ], Hcoll, rc−oll; 12 return False, Zcoll[Schosen ], Hcoll, rc−oll ; Then, in Sections IV-B, IV-C, we detail the design of the individual building blocks of Quarts.
AutoNDA by SimpleDocs

Related to QUARTS DESIGN

  • Project Design Applicants must design a project that provides access to health services to enable eligible women and men experiencing health needs to secure and maintain safe and accessible quality screening and diagnostic services, comprehensive family planning, and/ or other women’s health services. A. Applicants are encouraged to emphasize the following components in the design of their projects. Projects must: 1. Use a collaborative approach to maximize existing community resources and avoid duplication of effort; 2. Enhance systems and local processes to make it easier for people to transition to, from, and between services; 3. Address barriers to ensure services are accessible to people regardless of setting or location; and 4. Promote improvement and positively impact health and well-being through coordinated service delivery. B. To be effective, services and activities provided or made available as part of the Proposed Project should have policies and procedures in place and include with the application as an attachment that: 1. Delineate the timely provision of services; 2. Deem Client eligibility and service provision as soon as possible and no later than 30 calendar days from initial request; 3. Require staff to assess and prioritize Client needs; 4. Implement with model fidelity to an evidence-based program or based upon best available research; 5. Plan in partnership with the person and are inclusive; 6. Provide in an environment that is most appropriate and based on a person’s preference including reasonable clinic/reception wait times that are not a barrier to care; 7. Provide referral sources for Clients that cannot be served or receive a specific service; 8. Are culturally and linguistically sensitive; 9. Tailor services to a person’s unique strengths and needs; 10. Manage funds to ensure established Clients continuity of care throughout budget year; 11. Continue to provide services to established Clients after allocated funds are expended; 12. Have processes to identify and eliminate possible barriers to care; 13. Do not deny services due to inability to pay; 14. Have appropriate key personnel and required staff to meet the medical and health needs of Clients; 15. Bill services appropriately and timely through TMHP; 16. Effectively communicate and document information related to health care needs with next steps available to Client; 17. Establish outreach and education plan for the community; and 18. Outline successful delivery of direct clinical services to Clients By submitting an Application under this RFA, the Applicant certifies that Applicant has or will have at time of grant award services, policies, or procedures that conform with the requirements in this section as applicable. HHSC, in its sole discretion, may request to review relevant documentation during the project period as necessary to ensure program fidelity.

  • Schematic Design See Section 2, Part 1, Article 2.1.4, Paragraph 2.1.4.2.

  • ROADWAY DESIGN MISCELLANEOUS (ROADWAY)

  • Study Design This includes a discussion of the evaluation design employed including research questions and hypotheses; type of study design; impacted populations and stakeholders; data sources; and data collection; analysis techniques, including controls or adjustments for differences in comparison groups, controls for other interventions in the State and any sensitivity analyses, and limitations of the study.

  • Program Design The County Human Resources Department will operate a Catastrophic Leave Bank which is designed to assist any County employee who has exhausted all paid accruals due to a serious or catastrophic illness, injury, or condition of the employee or family member. The program establishes and maintains a Countywide bank wherein any employee who wishes to contribute may authorize that a portion of his/her accrued vacation, compensatory time, holiday compensatory time or floating holiday be deducted from those account(s) and credited to the Catastrophic Leave Bank. Employees may donate hours either to a specific eligible employee or to the bank. Upon approval, credits from the Catastrophic Leave Bank may be transferred to a requesting employee's sick leave account so that employee may remain in paid status for a longer period of time, thus partially ameliorating the financial impact of the illness, injury, or condition. Catastrophic illness or injury is defined as a critical medical condition, a long-term major physical impairment or disability which manifests itself during employment.

  • Ordering Process 6.4.1 CLEC, or CLEC's agent, shall act as the single point of contact for its End User Customers' service needs, including without limitation, sales, service design, order taking, Provisioning, change orders, training, maintenance, trouble reports, repair, post-sale servicing, Billing, collection and inquiry. CLEC's End User Customers contacting Qwest in error will be instructed to contact CLEC; and Qwest's End User Customers contacting CLEC in error will be instructed to contact Qwest. In responding to calls, neither Party shall make disparaging remarks about each other. To the extent the correct provider can be determined, misdirected calls received by either Party will be referred to the proper provider of local Exchange Service; however, nothing in this Agreement shall be deemed to prohibit Qwest or CLEC from discussing its products and services with CLEC's or Qwest's End User Customers who call the other Party seeking such information. 6.4.2 CLEC shall transmit to Qwest all information necessary for the ordering (Billing, Directory Listing and other information), installation, repair, maintenance and post-installation servicing according to Qwest's standard procedures, as described in the Qwest Product Catalog (PCAT) available on Qwest's public web site located at xxxx://xxx.xxxxx.xxx/wholesale/pcat. Information shall be provided using Qwest's designated Local Service Request (LSR) format which may include the LSR, End User Customer and resale forms. 6.4.3 Qwest will use the same performance standards and criteria for installation, Provisioning, maintenance, and repair of services provided to CLEC for resale under this Agreement as Qwest provides to itself, its Affiliates, its subsidiaries, other Resellers, and Qwest retail End User Customers. The installation, Provisioning, maintenance, and repair processes for CLEC's resale service requests are detailed in the Access to OSS Section of this Agreement, and are applicable whether CLEC's resale service requests are submitted via Operational Support System or by facsimile. 6.4.4 CLEC is responsible for providing to Qwest complete and accurate End User Customer Directory Listing information including initial and updated information for Directory Assistance Service, white pages directories, and E911/911 Emergency Services. The Ancillary Services Section of this Agreement contains complete terms and conditions for Directory Listings for Directory Assistance Services, white pages directories, and E911/911 Emergency Services. 6.4.5 If Qwest's retail End User Customer, or the End User Customer's New Service Provider orders the discontinuance of the End User Customer's existing Qwest service in anticipation of the End User Customer moving to a New Service Provider, Qwest will render its closing xxxx to the End User Customer, discontinuing Billing as of the date of the discontinuance of Qwest's service to the End User Customer. If the Current Service Provider, or if the End User Customer's New Service Provider orders the discontinuance of existing resold service from the Current Service Provider, Qwest will xxxx the Current Service Provider for service through the date the End User Customer receives resold service from the Current Service Provider. Qwest will notify CLEC by Operational Support System interface, facsimile, or by other agreed-upon processes when an End User Customer moves from the Current Service Provider to a New Service Provider. Qwest will not provide the Current Service Provider with the name of the New Service Provider selected by the End User Customer. 6.4.6 CLEC shall provide Qwest and Qwest shall provide CLEC with points of contact for order entry, problem resolution and repair of the resold services. These points of contact will be identified for both CLEC and Qwest in the event special attention is required on a service request. 6.4.7 Prior to placing orders on behalf of the End User Customer, CLEC shall be responsible for obtaining and having in its possession Proof of Authorization (POA), as set forth in the POA Section of this Agreement. 6.4.8 Due Date intervals for CLEC's resale service requests are established when service requests are received by Qwest through Operational Support Systems or by facsimile. Intervals provided to CLEC shall be equivalent to intervals provided by Qwest to itself, its Affiliates, its subsidiaries, other Resellers, and to Qwest's retail End User Customers.

  • No Process or Design Changes Supplier shall not make any process or design changes affecting Products or Services without DXC’s prior written consent.

  • Server Software Subject to the terms and conditions of this XXXX, Vocera grants you the non-exclusive right to (i) install and run (“Use”) the Server Software on computer systems (each, a “Server Computer”) located at End User’s Facilities in the geographic territory designated above (“Territory”); (ii) to Use the Client Software in conjunction with Authorized Client Devices and such Server Computers; and (iii) for pilot licenses for certain Software provided on a trial basis, use such Software for the limited term specified by Vocera in writing. You may Use the standard Server Software on one primary Server Computer (or a primary cluster of computers suitably configured for productive use of the Server Software). You may install backup copies of the Server Software on backup Server Computers to provide redundancy in the event of failure of the primary Server Computer(s) but, unless you have acquired additional licenses or a failover license from Vocera, you may not run such backup or additional copies concurrently with the primary copies. Vocera grants you the right to use the applicable License Key issued by Vocera only to enable Use of the Server Software in conjunction with the licensed Server Computers. Server Software may be licensed for a Subscription Term as specified in the Quote.

  • LIMITATIONS ON REVERSE ENGINEERING, DECOMPILATION AND DISASSEMBLY You may not reverse engineer, decompile, or disassemble the Software, except and only to the extent that such activity is expressly permitted by applicable law notwithstanding this limitation.

  • File Format Standard Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in XXX 0000, Section 5, including all the records present in the actual zone used in the public DNS. Sub-format is as follows: Each record must include all fields in one line as: <domain-name> <TTL> <class> <type> <RDATA>. Class and Type must use the standard mnemonics and must be in lower case. TTL must be present as a decimal integer. Use of /X and /DDD inside domain names is allowed. All domain names must be in lower case. Must use exactly one tab as separator of fields inside a record. All domain names must be fully qualified. No $ORIGIN directives. No use of “@” to denote current origin. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. No $INCLUDE directives. No $TTL directives. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. No use of comments. No blank lines. The SOA record should be present at the top and (duplicated at) the end of the zone file. With the exception of the SOA record, all the records in a file must be in alphabetical order. One zone per file. If a TLD divides its DNS data into multiple zones, each goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.

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