Rationale and Introduction Sample Clauses

Rationale and Introduction. ‌ As discussed in the previous section about the IoT Reference Architecture dependencies and model influences, business scenarios play an important role in the external validation of the architectural reference model (ARM). Business scenarios help defining application-specific requirements, i.e. they are one source of input regarding what potential systems and applications need to implement and deliver, if they are to realise certain business scenarios. At the same time, business scenarios help understanding the IoT Reference Model as such, as the domain components described in the reference model are reflected in the respective business scenarios, i.e. the reference model provides a formalised and abstracted model of the entities and their relationships that are brought to life within the different business scenarios. The primary aim of business scenarios is to provide an external validation of the ARM in economic terms, i.e. business scenarios should demonstrate that concrete systems built utilising ARM-compliant concrete architectures are economically viable and beneficial, so that it makes sense for business stakeholders to develop business scenarios based on IoT-A models and best practices. Ideally, business scenarios should cover a diverse set of relevant application fields in order to demonstrate the broad applicability of IoT-A, especially since one of the primary goals of IoT-A is to develop an IoT Reference Architecture that transforms the isolated island solutions of the “intranets of things” as we know them today into a domain-spanning interoperable infrastructure of IoT platforms. This infrastructure should be viable from an economic point of view and should facilitate novel business opportunities. Within this section of the deliverable, we will only briefly discuss the application fields for which viable business scenarios compliant to IoT-A can be developed, but instead focus only on central application fields in the focus of the project. As IoT-A work package 7 explicitly focuses on health and retail as the primary application fields for which technical demonstrators are to be developed and validated both in terms of being relevant for the application fields as such (the stakeholder group was selected partly based on the industry or domain the stakeholders are experts in) and in terms of technical and economic viability, it makes sense to concentrate on these use cases for a more in-depth analysis of business cases. In that respect, we do p...
AutoNDA by SimpleDocs

Related to Rationale and Introduction

  • BACKGROUND AND INTRODUCTION The Federal-aid Highway Program (FAHP) is a federally-assisted program of State-selected projects. The Federal Highway Administration (FHWA) and the State Departments of Transportation have long worked as partners to deliver the FAHP in accordance with Federal requirements. In enacting 23 U.S.C. 106(c), as amended, Congress recognized the need to give the States more authority to carry out project responsibilities traditionally handled by FHWA. Congress also recognized the importance of a risk-based approach to FHWA oversight of the FAHP, establishing requirements in 23 U.S.C. 106(g). This Stewardship and Oversight (S&O) Agreement sets forth the agreement between the FHWA and the State of Florida Department of Transportation (FDOT) on the roles and responsibilities of the FHWA and the State DOT with respect to Title 23 project approvals and related responsibilities, and FAHP oversight activities. The scope of FHWA responsibilities, and the legal authority for State DOT assumption of FHWA responsibilities, developed over time. The U.S. Secretary of Transportation delegated responsibility to the Administrator of the FHWA for the FAHP under Title 23 of the United States Code, and associated laws. (49 CFR 1.84 and 1.85) The following legislation further outlines FHWA’s responsibilities: • Intermodal Surface Transportation Efficiency Act (ISTEA) of 1991; • Transportation Equity Act for the 21st Century (TEA-21) of 1998; • Safe, Accountable, Flexible, Efficient Transportation Equity Act: A Legacy for Users (SAFETEA-LU) of 2005; and • Moving Ahead for Progress in the 21st Century Act (MAP-21) of 2012 (P.L. 112-141). The FHWA may not assign or delegate its decision-making authority to a State Department of Transportation unless authorized by law. Xxxxxxx 000 xx Xxxxx 00, Xxxxxx Xxxxxx Code (Section 106), authorizes the State to assume specific project approvals. For projects that receive funding under Title 23, U.S.C., and are on the National Highway System (NHS) including projects on the Interstate System, the State may assume the responsibilities of the Secretary of the U.S. Department of Transportation under Title 23 for design, plans, specifications, estimates, contract awards, and inspections with respect to the projects unless the Secretary determines that the assumption is not appropriate. (23 U.S.C. 106(c)(1)) For projects under Title 23, U.S.C. that are not on the NHS, the State shall assume the responsibilities for design, plans, specifications, estimates, contract awards, and inspections unless the State determines that such assumption is not appropriate. (23 U.S.C. 106(c)(2)) For all other project activities which do not fall within the specific project approvals listed in Section 106 or are not otherwise authorized by law, the FHWA may authorize a State DOT to perform work needed to reach the FHWA decision point, or to implement FHWA’s decision. However such decisions themselves are reserved to FHWA. The authority given to the State DOT under Section 106(c)(1) and (2) is limited to specific project approvals listed herein. Nothing listed herein is intended to include assumption of FHWA’s decision-making authority regarding Title 23, U.S.C. eligibility or Federal-aid participation determinations. The FHWA always must make the final eligibility and participation decisions for the Federal-aid Highway Program. Section 106(c)(3) requires FHWA and the State DOT to enter into an agreement relating to the extent to which the State DOT assumes project responsibilities. This Stewardship and Oversight Agreement (S&O Agreement), includes information on specific project approvals and related responsibilities, and provides the requirements for FHWA oversight of the FAHP (Oversight Program), as required by 23 U.S.C. 106(g).

  • Vaccination and Inoculation (a) The Employer agrees to take all reasonable precautions, including in-service seminars, to limit the spread of infectious diseases among employees.

  • Dispatch and Scheduling 4.3.1 The Power Producer shall be required to schedule its power as per the applicable Regulations / Requirements / Guidelines of CERC / GERC / SLDC / RLDC and maintain compliance to the Grid Code requirements and directions, as specified by SLDC / RLDC from time to time. Any deviation from the schedule will attract the provisions of applicable Regulation / Guidelines / Directions and any financial implication on account of this shall be to the account of the Power Producer.

  • Additional Wet Weather Procedure 14.15.1 Remaining On Site Where, because of wet weather, the employees are prevented from working:

  • Weekend Scheduling It is the policy of the Employer to schedule those nurses who so desire every other weekend off, with the exception of those nurses who have signed an authorization to work consecutive weekends. Nurses who have volunteered to work consecutive weekends may withdraw such authorization upon two (2) weeks’ written notice prior to the date a new schedule must be posted.

  • Step 3 – Contract Language Disputes (a) If a grievance concerning the interpretation or application of this Agreement, other than a grievance alleging that a disciplinary action (reduction in base pay, demotion, involuntary transfer of more than 50 miles by highway, suspension, or dismissal) was taken without cause, is not resolved at Step 2, the grievant or designated representative may appeal the grievance by submitting it to the Office Manager for the Office of the General Counsel of the Department of Management Services, 0000 Xxxxxxxxx Xxx, Xxxxx 000, Xxxxxxxxxxx, Xxxxxxx, 00000-0950, or by email to: Xxxx0Xxxxxxxxxx@xxx.xxxxxxxxx.xxx within 15 days following receipt of the decision at Step 2. The grievance shall include a copy of the grievance forms submitted at Steps 1 and 2, together with all written responses and documents in support of the grievance. When the grievance is eligible for initiation at Step 3, the grievance shall be filed on the grievance form contained in Appendix B of this Contract, setting forth specifically the facts on which the grievance is based, the specific provision(s) of the Contract allegedly violated, and the relief requested.

  • DISTRIBUTION OF CONTRACTOR PRICE LIST AND CONTRACT APPENDICES Contractor shall provide Authorized Users with electronic copies of the Contract, including price lists and Appendices, upon request. OGS CENTRALIZED CONTRACT MODIFICATIONS Contract Updates will be handled as provided in Appendix C – Contract Modification Procedures.

  • HOURS OF WORK AND SCHEDULING 15.01 The normal hours of work for an employee are not a guarantee of work per day or per week, or a guarantee of days of work per week. The normal hours of work shall be seven and one-half (7-1/2) hours per day, and seventy-five (75) hours in any bi-weekly period.

  • Hours of Work and Scheduling Provisions (b) In the event an Employee is scheduled to work on the evening or night Shift(s) on the day(s) or the night Shift commencing on the day(s) on which the Employee is called as a juror or witness in matters arising out of the Employee’s employment with the Employer, the Employee shall be granted a leave of absence for those scheduled Shift(s).

  • Technical References Technical References that describe the practices, procedures and specifications for certain services (and the applicable interfaces relating thereto) are listed on Schedule 2.3 (the “Technical Reference Schedule”) to assist the Parties in meeting their respective responsibilities hereunder.

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