Refine Strategy and Approach Sample Clauses

Refine Strategy and Approach. This task includes strategy meetings with County staff and other key stakeholders to refine the approach to the project, which could include, among other options, a change in the Specific Plan final buildout, primary and secondary access points, and a possible boundary change to the west. Consultant will support County staff by guiding the refinement of the project to best achieve General Plan consistency and CEQA compliance, with special attention to water supply and sewer service, project access, General Plan consistency, and scenic vistas and visual character. Consultant will prepare a memo that summarizes and outlines potential recommendations and modifications to the specific plan. Under this task, Consultant will attend four in-person meetings and up to five conference call meetings. Sub-consultant will attend one in-person meeting. It should be noted that change in project buildout, boundary, or access could require revisions to existing technical studies prepared on behalf of Richland Communities. Our scope of work assumes also that no new analysis will be conducted by Consultant to revise technical reports. However, Consultant has the technical expertise to update or oversee updates to the technical reports, if needed, as an optional task, described below in more detail. We recommend establishment of a contingency fund in the event that additional coordination and supplemental analysis is required for the applicant’s technical reports.
Sample 1
AutoNDA by SimpleDocs

Related to Refine Strategy and Approach

  • Target Population The Grantee shall ensure that diversion programs and services provided under this grant are designed to serve juvenile offenders who are at risk of commitment to Department.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • Registry Interoperability and Continuity Registry Operator shall comply with the Registry Interoperability and Continuity Specifications as set forth in Specification 6 attached hereto (“Specification 6”).

  • The Web Services E-Verify Employer Agent agrees to, consistent with applicable laws, regulations, and policies, commit sufficient personnel and resources to meet the requirements of this MOU.

  • Requester and Approved User Responsibilities The Requester agrees through the submission of the DAR that the PI named has reviewed and understands the principles for responsible research use and data management of the genomic datasets as defined in the NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy. The Requester and Approved Users further acknowledge that they are responsible for ensuring that all uses of the data are consistent with national, tribal, and state laws and regulations, as appropriate, as well as relevant institutional policies and procedures for managing sensitive genomic and phenotypic data. The Requester certifies that the PI is in good standing (i.e., no known sanctions) with the institution, relevant funding agencies, and regulatory agencies and is eligible to conduct independent research (i.e., is not a postdoctoral fellow, student, or trainee). The Requester and any Approved Users may use the dataset(s) only in accordance with the parameters described on the study page and in the 1 If contractor services are to be utilized, PI requesting the data must provide a brief description of the services that the contractor will perform for the PI (e.g., data cleaning services) in the research use statement of the DAR. Additionally, the Key Personnel section of the DAR must include the name of the contractor’s employee(s) who will conduct the work. These requirements apply whether the contractor carries out the work at the PI’s facility or at the contractor’s facility. In addition, the PI is expected to include in any contract agreement requirements to ensure that any of the contractor’s employees who have access to the data adhere to the NIH GDS Policy, this Data Use Certification Agreement, and the NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy. Note that any scientific collaborators, including contractors, who are not at the Requester must submit their own DAR. Addendum to this Agreement for the appropriate research use, as well as any limitations on such use, of the dataset(s), as described in the DAR, and as required by law. Through the submission of this DAR, the Requester and Approved Users acknowledge receiving and reviewing a copy of the Addendum which includes Data Use Limitation(s) for each dataset requested. The Requester and Approved Users agree to comply with the terms listed in the Addendum. Through submission of the DAR, the PI and Requester agree to submit a Project Renewal or Project Close-out prior to the expiration date of the one (1) year data access period. The PI also agrees to submit an annual Progress Update prior to the one (1) year anniversary2 of the project, as described under Research Use Reporting (Term 10) below. By approving and submitting the attached DAR, the Institutional Signing Official provides assurance that relevant institutional policies and applicable local, state, tribal, and federal laws and regulations, as applicable, have been followed, including IRB approval, if required. Approved Users may be required to have IRB approval if they have access to personal identifying information for research participants in the original study at their institution, or through their collaborators. The Institutional Signing Official also assures, through the approval of the DAR, that other institutional departments with relevant authorities (e.g., those overseeing human subjects research, information technology, technology transfer) have reviewed the relevant sections of the NIH GDS Policy and the associated procedures and are in agreement with the principles defined. The Requester acknowledges that controlled-access datasets subject to the NIH GDS Policy may be updated to exclude or include additional information. Unless otherwise indicated, all statements herein are presumed to be true and applicable to the access and use of all versions of these datasets.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Provisioning of High Frequency Spectrum and Splitter Space 3.2.1 BellSouth will provide <<customer_name>> with access to the High Frequency Spectrum as follows:

  • GOAL FOR CONTRACTING WITH SMALL AND MINORITY BUSINESSES WOMEN’S BUSINESS ENTERPRISES, AND LABOR SURPLUS AREA FIRMS (if subcontracts are to be let)

  • Signaling Parameters All SS7 signaling parameters will be provided in conjunction with traffic exchange trunk groups, where and as available. These parameters include Automatic Number Identification ("ANI"), Calling Party Number ("CPN"), Privacy Indicator, calling party category information, originating line information, charge number, etc. Also included are all parameters relating to network signaling information, such as Carrier Information Parameter ("CIP"), wherever such information is needed for call routing or billing. GTE will provide SS7 via GR-394-SS7 and/or GR-317-SS7 format(s).

  • Unbundled Channelization (Multiplexing) 5.7.1 To the extent NewPhone is purchasing DS1 or DS3 or STS-1 Dedicated Transport pursuant to this Agreement, Unbundled Channelization (UC) provides the optional multiplexing capability that will allow a DS1 (1.544 Mbps) or DS3 (44.736 Mbps) or STS-1 (51.84 Mbps) Network Elements to be multiplexed or channelized at a BellSouth central office. Channelization can be accomplished through the use of a multiplexer or a digital cross-connect system at the discretion of BellSouth. Once UC has been installed, NewPhone may request channel activation on a channelized facility and BellSouth shall connect the requested facilities via COCIs. The COCI must be compatible with the lower capacity facility and ordered with the lower capacity facility. This service is available as defined in NECA 4.

Time is Money Join Law Insider Premium to draft better contracts faster.