Task T1.2 on architecture design Sample Clauses

Task T1.2 on architecture design. Based on the IoT6 requirements definition (from Task T1.1), the objectives of this Task are to design and describe the IoT6 IPv6-based Service Oriented Architecture to be developed in order to integrate heterogeneous subsystems of the Internet of Things. During the first year of the project, different architectural options were evaluated against the scenarios and requirements, discussed among the IoT6 participants and the advisory board members. These activities resulted in the initial IoT6 architecture presented in deliverable D1.2 [47], designed to enable integration and interaction among various components of the Internet of Things (including sensor networks, mobile phones, STIS (RFID) and building automation systems), as well as their integration with cloud computing applications (Software as a Service) and business processes management tools. The initial IoT6 architecture identifies the main system components and their functionality, interaction patterns, interfaces and the underlying communications links. In this document, an updated version of the IoT6 architecture is described, further specifying various IoT6 system components as well as the ontology to be used in order to assure heterogeneous integration and provide interoperability among them. The work done in WP2 (IPv6 Connectivity) and WP5 (Smart Board and Intelligence distribution) has been taken into account, in particular in the areas of security and privacy aspects of the interactions (how the IPv6 features support security mechanisms in the transport of information and how security and privacy could be integrated within the interactions with the objects based on the service layer being proposed and their implications on the architecture design). Particular care was given to consider the privacy issues from an end user perspective provided by MI and its supported UN delegates. In addition to the input from other work packages of the IoT6 project, inputs were taken from interactions with the IoT community, in particular with the IoT-A project. IoT6 participated in an IoT-A project workshop on IoT architecture providing feedback to IoT-A and discussing their proposed Architecture Reference Model in particular in the communication domain. Furthermore, the IoT6 project participated in meetings with the FI-PPP project FI-WARE and has aimed to align these initiatives as well as co-organized a workshop with IoT-A on IoT architecture during the 2013 IoT week in Helsinki. The final update of the I...
AutoNDA by SimpleDocs

Related to Task T1.2 on architecture design

  • Architecture The Private Improvements shall have architectural features, detailing, and design elements in accordance with the Project Schematic Drawings. All accessory screening walls or fences, if necessary, shall use similar primary material, color, and detailing as on the Private Improvements.

  • Schematic Design Phase Services § 3.2.1 The Architect shall review the program and other information furnished by the Owner, and shall review laws, codes, and regulations applicable to the Architect’s services.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Research Design The data generated by excavations at the prehistoric site(s) will be used to examine at least three topics: (1) chronology; (2) technology; and (3) subsistence practices. Insights into changing patterns of community organization may also be granted, as may insights into changes in social organization. The data recovered will then be compared to data from other regional sites.

  • Design Development Phase Services 3.3.1 Based on the Owner’s approval of the Schematic Design Documents, and on the Owner’s authorization of any adjustments in the Project requirements and the budget for the Cost of the Work, the Architect shall prepare Design Development Documents for the Owner’s approval. The Design Development Documents shall illustrate and describe the development of the approved Schematic Design Documents and shall consist of drawings and other documents including plans, sections, elevations, typical construction details, and diagrammatic layouts of building systems to fix and describe the size and character of the Project as to architectural, structural, mechanical and electrical systems, and other appropriate elements. The Design Development Documents shall also include outline specifications that identify major materials and systems and establish, in general, their quality levels.

  • Design Professional to Design Work The Design Professional Contract requires the Design Professional to design and to prepare the Contract Documents, a copy of which shall be furnished to the Contractor upon request. The Design Professional Contract requires the Design Professional to designate a readily accessible representative (either on Site or by computer, phone or fax or otherwise) who shall have authority promptly to render decisions and to furnish information required of the Design Professional.

  • Physical Architecture 59.2.1 CenturyLink's network architecture in any given local exchange area and/or LATA can vary markedly from another local exchange area/LATA. Using one or more of the NIMs herein, the Parties will agree to a physical architecture plan for a specific LATA, or if appropriate based on other requirements in Section 59, Local Calling Area. The physical architecture plan, as described in the Local Interconnection POI Profile, will be discussed during joint implementation planning. CLEC and CenturyLink agree to Interconnect their networks through existing and/or new Interconnection Facilities between CLEC switch(es) and CenturyLink's End Office Switch(es) and/or Tandem Switch(es). The physical architecture plan will be in accordance with Forecasting and Planning requirements in Article IV.

  • DEVELOPMENT OR ASSISTANCE IN DEVELOPMENT OF SPECIFICATIONS REQUIREMENTS/ STATEMENTS OF WORK Firms and/or individuals that assisted in the development or drafting of the specifications, requirements, statements of work, or solicitation documents contained herein are excluded from competing for this solicitation. This shall not be applicable to firms and/or individuals providing responses to a publicly posted Request for Information (RFI) associated with a solicitation.

  • Software Development Software designs, prototypes, and all documentation for the final designs developed under this agreement must be made fully transferable upon direction of NSF. NSF may make the software design, prototype, and documentation for the final design available to competitors for review during any anticipated re-competition of the project.

  • Modified Work/Return to Work Programs The Hospital and the Union recognize the purpose of modified work/return to work programs, is to provide fair and consistent practices for accommodating nurses who have been ill, injured or permanently disabled, to enable their early and safe return to work. The parties undertake to provide safe and meaningful employment for both permanently or temporarily disabled nurses based on the following principles:

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