Communication Process. ADOT is the single source of information regarding the P3 Agreement procurement. The procurement process begins on the date of issuance of this RFQ, and is anticipated to be completed with the award of the P3 Agreement.
(a) Except as set out in this RFQ or the conflict of interest policy in Attachment 1, following issue of the RFQ, no Proposer or any of its team members may communicate with another Proposer or its team members with regard to the Project or SOQs. A Proposer may communicate with a subcontractor that is permitted to be on both its team and another Proposer’s team, so long as those Proposers establish a protocol to ensure that the subcontractor will not act as a conduit of information between the teams. Proposers and team members are permitted to attend ADOT-sponsored workshops and meetings together provided the requirements in this Section are complied with;
(b) Contact between Proposers and ADOT shall only be through the ADOT Procurement Manager and Proposer’s designated representative and shall be in writing as set out in Section 3.4;
(c) Proposers shall not contact ADOT employees, advisors, and any other person who will evaluate the SOQs regarding the Project or the procurement;
(d) Proposers shall not contact Stakeholders and those parties identified under Section 7.3.1
Communication Process. Pursuant to City Resolution 6619 (1989 Series) the City agrees with the Union to improve communications and provide for the following:
A. Monthly Conferences There will be a monthly meeting between the department head and management member(s) and a least two (2) union representatives to discuss problems or other subjects of mutual interest. Minutes of the meeting will be maintained to reflect topics discussed, actions to be taken, the party responsible for any action and the expected completion date.
B. Quarterly Meetings Two to four representatives of the Union, the City Manager (or designee), department head (or designee), and management representative(s) designated by the City will meet quarterly if there are issues of concern to the parties. No issues will be brought to this quarterly meeting without first having been discussed with the department head at a scheduled monthly meeting.
Communication Process. Pursuant to City Resolution 6619 (1989 Series) the City agrees with the Union to improve communications and provide for the following:
A. Monthly Conferences There will be a monthly meeting between the Fire Chief or designee and management member(s) and a least two (2) union representatives to discuss problems or other subjects of mutual interest. Minutes of the meeting will be maintained to reflect topics discussed, actions to be taken, the party responsible for any action and the expected completion date.
B. Quarterly Meetings Two (2) to four (4) representatives of the Union, the City Manager (or designee), Fire Chief (or designee), and management representative(s) designated by the City will meet quarterly, if requested by the Union or Fire Chief if there are issues of concern to the parties. No issues will be brought to this quarterly meeting without first having been discussed with the Fire Chief at a scheduled monthly meeting.
Communication Process. Outgoing wire transfer requests made by the State shall be delivered to the Contractor in batch data files throughout each business day. The Contractor shall accept and process such outgoing wire transfer requests on behalf of the State, provide outgoing wire transfer confirmation data files and incoming wire transfer data files to the State throughout the business day via the industry standard secure connection established by the Contractor as provided in Section A.13 below and in accordance with pages [PAGE NUMBERS FROM SUCCESSFUL PROPOSAL WHICH RESPOND TO SECTION C.2.3. of RFP ATTACHMENT 6.2] of the Contractor's Proposal, and in accordance with the Operating Procedures developed pursuant to Section A.2 above. Advance notification of incoming wire transfers to the State shall entail an immediate e-mail transmission to the State upon receipt of the incoming wire by the Contractor. The Contractor shall provide an electronic interface between the Contractor’s wire transfer system and the State’s in-house wire system, which in-house system is known as the Automated Cash Management Entry system (ACME). Such interface shall ensure that no re-keying of data in the ACME system by the State will be necessary to (i) send wires, (ii) confirm the execution of outgoing wires, or (iii) to receive wires in the ACME system. The Contractor shall provide a communication process for the State to securely and timely request international outgoing wire transfers where either the U.S. dollar amounts need to be converted to a foreign currency, or certain foreign currency amounts need to be converted to U.S dollars. Such communication process for international outgoing wire transfer requests shall enable the State to access timely and accurate information for conversion of the foreign currency amount to the U.S dollar amount when necessary for the wire request, and shall be in accordance with pages [PAGE NUMBERS FROM SUCCESSFUL PROPOSAL WHICH RESPOND TO SECTION C.2.3. of RFP ATTACHMENT 6.2] of the Contractor’s Proposal, and in accordance with the Operating Procedures developed pursuant to Section A.2 above.
Communication Process. 1. The MCO must take all necessary and appropriate steps to ensure all MCO staff are aware of, and follow, the following communication process: Unless otherwise directed by XXX, the MCO must copy the ODM-provided regulatory email address on all submissions and communications to ODM. The MCO is prohibited from contacting entities that contract with ODM, unless necessary to fulfill the requirements under this Agreement or when specifically instructed by ODM. Under the terms of this Agreement, the MCO must meet all program requirements, regardless of delegation of functions. The MCO must ensure that its subcontractors communicate with ODM as requested by ODM. ODM may meet with MCO subcontractors at any time and does not need to have approval of the MCO to do so. To ensure that the MCO is meeting its obligations in accordance with this Agreement, the MCO must notify the ODM Contract Administrator within one business hour of the MCO’s receipt of a legislative or media inquiry that raises a pattern of concern regarding the MCO’s provision of services, ongoing provider relations issues, or a matter of significant concern to the community at large. This provision shall not be relied upon by the MCO to deny or delay responding to the inquiry. As necessary and appropriate, ODM will facilitate and/or require a response to the inquiry’s underlying issue or issues in a matter designed to meet the mission and goals of this Agreement (see Introduction). In the case of an inquiry made pursuant to sections 103.412 and 103.413 of the Ohio Revised Code, the MCO need not provide notification unless authorized by the individual making the inquiry.
Communication Process. ADOT is the single source of information regarding the Contract procurement. The procurement process begins on the date of issuance of this RFQ, and is anticipated to be completed with the award of the Contract.
(a) Except as set forth in this RFQ or the conflict of interest policy in Attachment 1, following issue of the RFQ, no Respondent or any of its team members may communicate with another Respondent or its team members with regard to the Project or SOQs. A Respondent may communicate with a subcontractor that is permitted to be on both its team and another Respondent’s team, so long as those Respondents establish a protocol to ensure that the subcontractor will not act as a conduit of information between the teams. Respondents and team members are permitted to attend ADOT-sponsored workshops and meetings together provided they comply with the requirements in this Section 7.1.1.
(b) Contact between Respondents and ADOT shall only be through the ADOT’s and Respondent’s designated representative and shall be in writing. The ADOT Procurement Manager identified in Section 3.4 and ADOT Project Manager identified below are the only ADOT designated representatives authorized to discuss this procurement with any interested parties, including Respondents, except for additional ADOT representatives while attending a forum established pursuant to the RFP or while engaged in post-selection negotiations and discussions. The ADOT Procurement Manager will serve as the primary point of contact during the RFQ procurement, unless otherwise notified. This restriction is in effect until the Contract is executed and effective. Any information from other sources may not be accurate and cannot be relied upon. The ADOT Project Manager is:
(c) Respondents shall not contact ADOT employees, advisors, and any other person who will evaluate the SOQs regarding the Project or the procurement.
(d) Respondents shall not contact employees of FHWA, MAG and those parties identified under Section 7.3.1
Communication Process. The first agreed step was to establish a task force in WP6 which could ensure a smooth flow of communication between the two initiatives. The members of the task force were identified among the following partners in WP6 Table 1: Members of the communication task force Partner Member Xxxx Xxx Xxxxxxxxx, Xxxxxxx Xxxxxx, Xxxx Xxxxxxxxxxxx Trust-IT Xxxxxxx Xxxxxxx, Xxxxxx Xxxxx, Xxxxx Xxxxxxxx Inria Xxxxx Xxxxxx, Xxxxxxx Xxxxxx The task force is holding regular meetings every week where information about upcoming initiatives and events from both sides are shared and strategic and operational activities are agreed and planned. Minutes with decisions, responsibilities and deadlines are issued after each meeting and shared between the task force members. Members of Adra are regularly reporting decisions, activities and outcomes of the task force to the Adra Board of Directors, while Adra-e members are doing the same in the monthly WP leaders calls. The idea is that the task force will remain in place for the whole lifetime of the project. From Adra´s perspective, this task force is named the “Communication and Marketing Topic Group”. The Adra members and secretariat have access to the documents of the Topic Group through the OnlyOffice platform.
Communication Process. Pediatric Provider Communication Agreements Complementary Medicine Provider Communication Agreements:
Communication Process. 1. The OhioRISE Plan must take all necessary and appropriate steps to ensure all OhioRISE Plan staff are aware of, and follow, the following communication process: Unless otherwise directed by XXX, the OhioRISE Plan must copy the ODM- provided regulatory email address on all submissions and communications to ODM. The OhioRISE Plan is prohibited from contacting entities that contract or subcontract with ODM, unless necessary to fulfill the requirements under this Agreement or when specifically instructed by ODM. However, ODM reserves the right to contact the subcontractor directly at its discretion. Under the terms of this Agreement, the OhioRISE Plan must meet all program requirements, regardless of delegation of functions. To ensure that the OhioRISE plan is meeting its obligations in accordance with this Agreement, the OhioRISE Plan must notify the ODM Contract Administrator within one business hour of the OhioRISE Plan’s receipt of a legislative or media inquiry that raises a pattern of concern regarding the OhioRISE Plans’s provision of services, ongoing provider relations issues, or a matter of significant concern to the community at large. This provision shall not be relied upon by the OhioRISE Plan to deny or delay responding to the inquiry. As necessary and appropriate, ODM will facilitate and/or require a response to the inquiry’s underlying issue or issues in a matter designed to meet the mission and goals of this Agreement (see Introduction). In the case of an inquiry made pursuant to sections 103.412 and 103.413 of the Ohio Revised Code, the OhioRISE Plan need not provide notification unless authorized by the individual making the inquiry. Events of a potentially concerning nature may include, but are not limited to, those that involve: An individual who is a member of the OhioRISE Plan; or A provider serving a member of the OhioRISE plan; or An employee of a CME or the OhioRISE Plan.
Communication Process. Each Rebalancing requires written notice of the Advisor by e-mail to BJB from an authorised person specified in Appendix 2. Such notice shall contain all necessary details of the Rebalancing, including the date as of which the Rebalancing shall become effective. Such notice (i) must be received by BJB as soon as practical prior to the effective date of the respective Rebalancing and (ii) is subject to confirmation (by e-mail) by BJB. The Advisor is obliged to contact BJB should his written notice not be confirmed within 1 hour. Absent any objection and upon confirmation by BJB, BJB will use its best effort to implement the Rebalancing as soon as practical. Rebalancing notices must be submitted within the Trading Hours as defined in Appendix 1 to the following e-mail address: “XXX@xxxxxxxxxx.xxx”. BJB shall communicate any rejections of potential new constituents of the Basket or any other objections against any Rebalancing without undue delay prior to the effective date of the Rebalancing.
