Guiding Principles for Proposal Development and Funding Allocation Sample Clauses

Guiding Principles for Proposal Development and Funding Allocation. The California Containerized Ports Interoperability Grant Program is supplying funding to the five containerized ports in California in support of building cloud-based data systems that enhance interoperability, support federal data initiatives, and advance the California climate goals as outlined in the MOU. Funding will be awarded based on several key factors: ● Individual port shares of TEU volume ● Key performance metrics: ○ Vessel dwell times ○ Container dwell times ○ Truck turn times ● Demonstrated data needs ● Interoperability improvements proposed ● The scoring rubric The TAC will assess funding impact based on annual TEU volume and impacts on port operational efficiency. Efforts will be made to address demonstrated data needs, as each port has unique needs and different capabilities of existing data systems. The intention is to raise the floor of data systems within all ports to enable cohesive future data initiatives. The primary goal of this funding is to support interoperability, which was identified as a primary challenge of the 2021-22 supply chain crisis. The grant administrators interpret data interoperability as making information readily available to port ecosystem stakeholders uniformly. Stakeholders must be able to interface with the ports to access information that increases the efficiency of cargo movements through the ports and general port operations. While interoperability may also extend port-to-port data sharing, this should be a natural byproduct of uniform data interfaces to stakeholders. If port-to-port data sharing is a goal of a grant proposal, it should be done as part of a collaborative effort. Data sharing should ideally be structured around uniform interfaces rather than specific agreements between parties. The intermediary supports the recommendations of the Federal Maritime Commission’s (FMC) Maritime Transportation Data Initiative (MTDI)1. Proposals should follow these recommendations whenever possible. A xxxxx of achieving interoperability is the adoption of standards. The FMC strongly recommends adopting the standards developed by the Digital Shipping Container Association (DCSA). Any new system or improvements to existing systems need to adopt these standards. Automatic interoperability will be achieved by adopting these standards in lexicon, definitions, format, and Application Programming Interfaces (APIs). It also creates a foundation for future systems that can be developed faster and in the same language. Port...
Sample 1
AutoNDA by SimpleDocs

Related to Guiding Principles for Proposal Development and Funding Allocation

  • Scope of Work For the 2022/2023 Grant Period, the Provider will maintain a victim services program that will be available to provide direct services to victims of crime who are identified by the Provider or are presented to the Provider, as specified in the Provider’s 2022/2023 Grant Application as approved by the OAG and incorporated herein by reference.

  • Scope of Services The specific scope of work for each job shall be determined in advance and in writing between TIPS Member, Member’s design professionals and Vendor. It is permitted for the TIPS Member to provide a general scope description, but the awarded vendor should provide a written scope of work, and if applicable, according to the TIPS Member’s design Professional as part of the proposal. Once the scope of the job is agreed to, the TIPS Member will issue a PO and/or an Agreement or Contract with the Job Order Contract Proposal referenced or as an attachment along with bond and any other special provisions agreed by the TIPS Member. If special terms and conditions other than those covered within this solicitation and awarded Agreements are required, they will be attached to the PO and/or an Agreement or Contract and shall take precedence over those in this base TIPS Vendor Agreement.

  • Additional Services Registry Operator shall be entitled to provide the Registry Services described in clauses (a) and (b) of the first paragraph of Section 2.1 in the Specification 6 attached hereto (“Specification 6”) and such other Registry Services set forth on Exhibit A (collectively, the “Approved Services”). If Registry Operator desires to provide any Registry Service that is not an Approved Service or is a material modification to an Approved Service (each, an “Additional Service”), Registry Operator shall submit a request for approval of such Additional Service pursuant to the Registry Services Evaluation Policy at xxxx://xxx.xxxxx.xxx/en/registries/rsep/rsep.html, as such policy may be amended from time to time in accordance with the bylaws of ICANN (as amended from time to time, the “ICANN Bylaws”) applicable to Consensus Policies (the “RSEP”). Registry Operator may offer Additional Services only with the written approval of ICANN, and, upon any such approval, such Additional Services shall be deemed Registry Services under this Agreement. In its reasonable discretion, ICANN may require an amendment to this Agreement reflecting the provision of any Additional Service which is approved pursuant to the RSEP, which amendment shall be in a form reasonably acceptable to the parties.

  • GRIEVANCE PROCEDURE 7.01 For purposes of this Agreement, a grievance is defined as a difference arising between the parties relating to the interpretation, application, administration or alleged violation of the Agreement including any question as to whether a matter is arbitrable.

  • Dispute Resolution All or any disputes arising out or touching upon or in relation to the terms and conditions of this Agreement, including the interpretation and validity of the terms thereof and the respective rights and obligations of the Parties, shall be settled amicably by mutual discussion, failing which the same shall be settled through the adjudicating officer appointed under the Act.

  • Deliverables Upon satisfactory completion of the work authorization, the Engineer shall submit the deliverables as specified in the executed work authorization to the State for review and acceptance.

  • Definitions and Interpretation 1.1 In this Agreement:

  • Audit Notwithstanding any other audit requirement, H-GAC reserves the right to conduct or cause to be conducted an independent audit of any transaction under this Agreement, such audit may be performed by the H-GAC local government audit staff, a certified public accountant firm, or other auditors designated by H-GAC and will be conducted in accordance with applicable professional standards and practices. The Contractor understands and agrees that the Contractor shall be liable to the H-GAC for any findings that result in monetary obligations to H-GAC.

  • Ownership of Work Product A. All right, title, and interest in the Work Product, including all Intellectual Property Rights therein, is exclusively owned by System Agency. Grantee and Xxxxxxx’s employees will have no rights in or ownership of the Work Product or any other property of System Agency.

  • Introduction The Texas Health and Human Services Commission ("HHSC") and the Contractor named in Section I (HHSC and Contractor may be referenced in this document collectively as the “Parties” and individually as the “Party") hereby enter into this Community Services Contract - Provider Agreement (the “Contract”) for the provision of services under the Contract type specified in Section I for the considerations set forth herein. The Contract Begin Date specified in Section I is not valid until this Contract is signed by both parties.

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