Programming process Sample Clauses

Programming process. Mn/DOT uses ATPs in developing the STIP. ATPs are sub-state, multi-county, geographically based partnerships composed of representative membership from cities, counties, RDCs, MPOs, and state agencies. Counties, cities, RDCs, and MPOs appoint representatives, many of whom are elected officials, to sit on the ATPs. The ATP process was specifically developed to bring a broader cross section of public and private interests to transportation decision-making. The ATP process and membership continue to evolve. Other methods, in addition to obtaining input from ATPs concerning content of the STIP, are used to encourage public involvement, including newsletters, newspaper articles, mailings, and press releases. In addition, the draft STIP is made available for public comment annually. Mn/XXX uses a mechanism entitled “Target Funding” to guide the programming process. ATPs are given estimates of the amount of federal highway and state highway funding they will receive and integrate the project priorities submitted by each partner, to be included in the STIP. REFERENCES • 23 CFR 450 • Mn/DOT STIP Guidance PROGRAMMING PROCESS Summary Table WORK ACTIVITY Mn/DOT ACTION FHWA OUTCOME ACTION Metropolitan Transportation Improvement Program (TIP) Districts work with MPOs to ensure consistency between TIPs and STIP and assure that MPO TIPs meet federal requirements. Districts submit MPO TIPs to OIM. OIM reviews and approves MPO TIPs per 23 CFR 450.312 reference to 23 CFR 450.324 through 330. OIM sends to FHWA no later then submittal of STIP. Review and make joint planning finding with FTA. Make conformity determination as appropriate. Approval of MPO TIPs for inclusion in STIP. Same timeframe as STIP approval (approval part of STIP letter). TIPs accepted for inclusion in STIP. Draft STIP (list of projects) Districts submit draft ATIPs to OIM by April 15. OIM develops draft STIP based on funding constraints. OIM announces availability of STIP for public review in State Register (May). Draft STIP sent to FHWA and ATPs for review and comment (May). Review and comment on draft STIP projects. Comments to be provided to OIM or discussed at a joint meeting by mid-July. Facilitates timely approval of Final STIP. STIP Draft Financial Plan OIM prepares a draft financial plan for the STIP and sends to FHWA by August 1. Review and comment. (21 days) Facilitates timely approval of Final STIP. STIP Approval OIM prepares and submits Final STIP (per 23 CFR 450.216 and 450.220 including cert...
Sample 1
AutoNDA by SimpleDocs
Programming process. The programming process took place from December 2006 to May 2007. The programme was developed following a process of wide consultation with the local stakeholders and potential beneficiaries
Sample 1
Programming process. During the programming process, the definition of the strategy, the selection and description of the thematic objectives and investment priorities of the cooperation programme take into consideration in particular the following Priority Areas (and key actions) of the EUSDR Action Plan 2010 (SEC 2010 1489). TO IP DTP specific objective (integrated approach) Related EUSDR Priority Area (PA) where specific aspects are covered
Sample 1
Programming process. The programming process started on 19th of February 2007 with the first preparatory meeting of the national institutions responsible for the IPA component II, during which the process of programme elaboration was discussed and agreed between the two sides. The process was led by two bodies established for that purpose and with specific responsibilities: the Joint Programming Committee (JPC) and the Joint Drafting Team (JDT). The first meeting of the Joint Programming Committee (JPC) was held on 1st of March 2007 in Zagreb when the Committee and Joint Drafting Team were officially established and during which their ru- les of procedure, mandate and membership were adopted. During the months of March/April 2007, the content of the SWOT (strengths, weaknesses, opportunities and threats) analysis was dis- cussed and presented to the potential beneficiaries during workshops in Dubrovnik, Croatia and Kotor, Montenegro, and the approval of the analysis was made via written procedure on 16 April 2007. Du- ring the month of May the programme beneficiaries discussed the programme’s strategic part (priorities, measures and activities) as well as the implementing provisions, and on 28 May 2007 the Joint Progra- mming Committee adopted the final draft programming document.
Sample 1

Related to Programming process

  • Programming Phase 2.2.1.2. Schematic Design Phase: 2.2.1.3. Design Development Phase:

  • Joint Network Implementation and Grooming Process Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia:

  • Programming (a) Pursuant to Section 624 of the Cable Act, the Licensee shall maintain the mix, quality and broad categories of Programming set forth in Exhibit 4, attached hereto and made a part hereof. Pursuant to applicable federal law, all Programming decisions, including the Programming listed in Exhibit 4, attached hereto, shall be at the sole discretion of the Licensee.

  • Hiring Process i. School District and Teach For America will collaborate in good faith to facilitate the efficient hiring of individual Teachers, in accordance with the School District’s established District hiring practices.

  • 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.

  • Benchmarking Process 2.2.1 The Supplier shall produce and send to the Authority for Approval, a draft plan for the Benchmark Review.

  • Bidding Process 3.1. Bidding shall generally commence based on the sequence of the lot being shown on the PAH Website. However the Auctioneer has the right to vary the sequence without having to give prior notice to the intended bidders.

  • Signaling protocol The Parties will interconnect their networks using SS7 signaling where Technically Feasible and available as defined in GR 905 Telcordia Standards including ISDN User Part (ISUP) for trunk signaling and TCAP for CCS-based features in the Interconnection of their networks. All Network Operations Forum (NOF) adopted standards shall be adhered to. Where available, CenturyLink signaling services to link its Signaling Transfer Points (STPs) for CLEC switches which connect to CenturyLink’s STPs via “A” links or for CLEC’s STPs to connect to CenturyLink’s STPs via “D” links which are dedicated to the transport of signaling for local Interconnection, may be ordered from the CenturyLink Tariff.

  • 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.

  • Evaluation Software If the Software is an evaluation version or is provided to You for evaluation purposes, then, unless otherwise approved in writing by an authorized representative of Licensor, Your license to use the Software is limited solely for internal evaluation purposes in non-production use and in accordance with the terms of the evaluation offering under which You received the Software, and expires 90 days from installation (or such other period as may be indicated within the Software). Upon expiration of the evaluation period, You must discontinue use of the Software, return to an original state any actions performed by the Software, and delete the Software entirely from Your system and You may not download the Software again unless approved in writing by an authorized representative of Licensor. The Software may contain an automatic disabling mechanism that prevents its use after a certain period of time. RESTRICTIONS

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