MIDIH Reference Architecture Sample Clauses

MIDIH Reference Architecture. One chapter is devoted to each of the tasks and the development made within them, including the same organization: • general information of the Composite Outcome(s) • a short description of each Component that made up the Composite Outcome(s) • the background and foreground for these components In addition, for each specific component that made up the Composite Outcome(s), a factsheet is provided in the Annexes following this schema: • general information of the component • functional description and architecture • manuals both technicians (installation, configuration) and end-users (usage)
Sample 1
AutoNDA by SimpleDocs
MIDIH Reference Architecture. The document follows the same structure as “D4.3 MIDIH Open CPS/IOT Components v1”, where one chapter is devoted to each of the tasks and the development made within them, including the same organization: • general information of the Composite Outcome(s) • a short description of each Component that made up the Composite Outcome(s) • the background and foreground for these components In addition, for each specific component that made up the Composite Outcome(s), a factsheet is provided in the Annexes following this schema: • general information of the component • functional description and architecture • manuals both technicians (installation, configuration) and end-users (usage)
Sample 1

Related to MIDIH Reference Architecture

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

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

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

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

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

  • Information Systems Acquisition Development and Maintenance Security of System Files. To protect City Information Processing Systems and system files containing information, Service Provider will ensure that access to source code is restricted to authorized users whose specific job function necessitates such access.

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

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

  • Alternative Work Schedule An alternate forty (40) hour work schedule (other than five (5) uniform and consecutive eight (8) hour days in a seven (7) day period), or for hospital personnel an eighty (80) hour workweek in a fourteen (14) day period and other mutually agreed upon schedules that comply with applicable federal and state law. Employee work schedules normally include two (2) consecutive days off.

  • Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.

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