Coordination Process Sample Clauses
The Coordination Process clause establishes the procedures and responsibilities for parties to communicate, collaborate, and synchronize their activities throughout the course of a project or agreement. Typically, this clause outlines how meetings will be scheduled, how information will be shared, and who will serve as the primary points of contact between the parties. By setting clear expectations for coordination, the clause helps prevent misunderstandings, ensures timely decision-making, and facilitates smooth project execution.
Coordination Process. The goal of Flint’s coordination process is to achieve an LOD 350 model at time of submission to the AHJ. This requires three (3) distinct phases of coordination which are listed below. Project specific collaboration procedures are further defined in section H of the Project BIM execution plan.
Coordination Process. The Contractor shall assign one lead individual, with the authority to obligate the contractor, to be responsible for communications with the Government for overall contract administration. This individual must be available 24 hours / day and respond to Government inquiries within two (2) hours. The Contractor shall assign one lead individual for each DO who shall coordinate all aspects of the job with the designated Government representative and vice versa. The Contractor’s designated representative will keep the Government's representative apprised of schedule, technical, material and financial issues pertaining to the order. The designated “lead individual” for the IDIQ-MAC and individual DOs may be the same employee as long as all contract and DO-level requirements are met. All communication with other Government organizations, Commands and Departments shall be via the Contracting Officer unless otherwise authorized. The Contractor’s employees shall not visit vessels or military activity associated with a DO without prior approval from the Contracting Officer or Project Manager. All visits shall be coordinated by the Government Maintenance Team.
Coordination Process. 5.1 Slot-requests based on historical rights from the corresponding previous season, will be allocated during initial coordination.
5.2 Slot series which cannot be confirmed during initial coordination will be put on a waiting list.
5.3 According to the availability, all other slot-series will be allocated on a provisional basis and without entitlement for historical rights after the IATA SC.
5.4 Night slots that are not based on historic rights will be confirmed with - Action code “T” and - Status information tag “NIGHTRESTR” in the Score database, subject to availability.
5.5 The priorities for the allocation from the night flight pool are as follows:
a) Extensions of existing slot series holding historical rights (also single flights, the extension itself does not create historical rights)
b) Slot series having been confirmed in the corresponding previous season
c) New slot series
5.6 Requests for single flights will be accepted and provisionally coordinated only after the Historics Baseline Date for the relevant season.
5.7 Slot requests for GA/BA flights are accepted maximum 28 days ahead of the planned operation.
5.8 For each season a waitlist will be maintained of all outstanding requests. This waitlist will be reviewed regularly to replenish any slot capacity available by cancellations or changes. Criterions for the waitlist-handling are number of frequency, extensions of already coordinated slot series, sequence of requests, etc.
Coordination Process. SCAG shall engage in a consultative process with VCTC and Transit Operators in accordance with applicable federal and state laws and regulations, and successors thereto, pertaining to the roles and responsibilities of the Parties in metropolitan transportation planning.
a. SCAG shall provide timely notice of the opportunity to comment on its Draft RTP and Draft FTIP to the parties and the opportunity to participate in Overall Work Program development.
b. SCAG shall continue maintaining the Regional Transit Technical Advisory Committee or a successor group, to provide a forum for VCTC, other CTCs, and Transit Operators, to participate in the metropolitan transportation planning process.
c. VCTC agrees to participate in SCAG's Technical Working Group or any successor group established to serve the same function which shall also serve as a forum to ensure that local transportation projects, plans and programs are effectively integrated into the RTP and FTIP updates.
d. The Executive Officers of SCAG and the CTCs shall continue to meet regularly to ensure executive coordination of regional/county/local transportation issues, including issues regarding transit coordination.
e. VCTC shall ensure that Transit Operators’ plans, programs, studies and other issues are integrated into the county and regional transportation planning process. VCTC shall provide Transit Operators the opportunity to propose projects for inclusion in VCTC's TIP and CMP. Projects and programs adopted by the VCTC in the Ventura County TIP and CMP shall be submitted to SCAG and recommended for inclusion in the FTIP and RTP, respectively.
f. The Parties shall cooperatively develop an annual listing of projects for which funds under 23 U.S.C. or 49 U.S.C. Chapter 53 were obligated in the preceding program year, in accordance with 23 CFR 450.334.
g. The Parties shall cooperatively develop estimates of funds that will be available to support RTP implementation, and reasonable financial principles and information that support revenue and cost estimates, to be used in the RTP and FTIP financial plan, in accordance with 23 CFR 450.324(f)(11).
h. The Parties agree to collaborate to implement federal performance reporting and performance-based planning provisions in accordance with 23 CFR 450.306(d)(2)(iii), and subject to applicable final rulemaking. The Parties further agree to coordinate to the maximum extent practicable in the selection of performance targets, and will cooperatively develop and s...
Coordination Process. C.14.1. The Contractor shall assign one separate dedicated Contractor Lead Project Manager as a single point of contact for each delivery order and this person shall coordinate all aspects of the delivery order with the designated Government representative and vice versa. The Contactor Lead Project Manager will keep Government representatives apprised of schedule, technical, material and financial concerns pertaining to the delivery order.
Coordination Process. 2.1 The Parties agree to establish a process, as set forth in this section, for coordinating the development of proposed standards, in accordance with the principles in Section 1 of this MOU.
2.2 The JIC shall be responsible for the coordination process. The JIC shall be composed of representatives from NERC holding one-third of the votes, representatives from NAESB WEQ holding one-third of the votes and representatives from the ISO/RTO Council holding one-third of the votes. Each Party will determine its representatives to the JIC, with every effort to have each segment or area represented. The quorum necessary for the transaction of business at meetings of the JIC shall require a majority of the representatives of each of any two Parties. Any or all members of the JIC may participate in a meeting, including being counted as part of the quorum, by means of a communication system by which all persons participating in the meeting are able to hear each other. Use of notational balloting or proxies will not be permitted. NERC, NAESB and the ISO/RTO Council will separately determine whether designated alternates will be permitted to participate in place of their absent JIC representatives. The JIC will have co-chairs, one representing NERC, one representing NAESB, and one representing the ISO/RTO Council chosen by each Party from among its JIC representatives.
2.3 Decisions of the JIC will be by a simple majority of all votes cast, with each NERC representative present at a meeting having a vote equal to 33.3% divided by the number of NERC representatives participating in the meeting, each NAESB representative having a vote equal to 33.3% divided by the number of NAESB representatives participating in the meeting, and each ISO/RTO Council representative having a vote equal to 33.3% divided by the number of ISO/RTO Council representatives participating in the meeting. In the event any Party fails to be represented by at least one representative and quorum requirements are met, the remaining two Parties shall each receive 50% of the vote, to be divided equally among the Party’s representatives. In the event of a tie vote, the matter will be referred to the Chairmen of the Parties present for the tie vote [or their Board level designee(s)] for resolution. In the determinations made under Section 2.6, each Party may abstain from voting on any question in which it determines it does not have a material interest. 4 The Parties expressly agree that reliability and bu...
Coordination Process. The Contractor shall assign one lead individual, with the authority to obligate the Contractor, to be responsible for communications with the Government for overall contract administration. This individual must be available 24 hours / day and respond to Government inquiries within two (2) hours. The Contractor shall assign one lead individual for each DO who shall coordinate all aspects of the job with the designated Government representative and vice versa. The Contractor’s designated representative will keep the Government's representative apprised of schedule, technical, material and financial issues pertaining to the order. The designated “lead individual” for the IDIQ-MAC and individual DOs may be the same employee as long as all contract and DO-level requirements are met. All communication with any Government organizations shall be via the Contracting Officer or the Contracting Officer’s Representative (COR) unless otherwise authorized. All visits shall be coordinated by the Government Maintenance Team.