Application Roadmap Sample Clauses

Application Roadmap. Examples of Samsung’s perception of technology and application areas are show in Figure 9, here the main driving factors are performance and low power consumption. Based in this, a similar roadmap can be determined, where key barrier is technology – this is what E2SWITCH project is aiming to contribute in finding solutions.
AutoNDA by SimpleDocs

Related to Application Roadmap

  • Application Form To apply for a pole attachment or conduit occupancy license under this Agreement, Applicant shall submit to SWBT two signed copies of the appropriate application forms. SWBT represents that the forms specified in subsections (a)-(b) are forms in use prior to the effective date of this Agreement and that SWBT is in the process of revising such forms to conform to the provisions of this Agreement and to streamline the application process. The parties therefore agree that the forms specified in subsections (a) and (b) will be interim forms only. SWBT reserves the right to change the format and content of these forms upon 60 days written notice to Applicant. (a) To apply for a pole attachment license, Applicant shall submit to SWBT two signed copies of SWBT’s Form SW-9434 (“Access Application and Make- Ready Authorization”) together with completed Form SW-9433 (“Pole Attachments”). An application for a pole attachment license will not be complete or subject to processing by SWBT until these forms have been submitted to SWBT; provided, however, that such forms will be deemed to be substantially complete if they contain the information specified in subsections (c)-(h) below, as applicable. Copies of Forms SW-9433 and SW-9434 are attached to this Agreement as parts of APPENDIX III. (b) To apply for a conduit occupancy license, Applicant shall submit to SWBT two signed copies of SWBT’s Form SW-9434 (“Access Application and Make-Ready Authorization”) together with completed Form SW-9435 (“Conduit Occupancy”). An application for a conduit occupancy license will not be complete or subject to processing by SWBT until these forms have been submitted to SWBT; provided, however, that such forms will be deemed to be substantially complete if they contain the information specified in subsections (c)-(h) below, as applicable. Copies of Forms SW-9434 and SW-9435 are attached to this Agreement as parts of APPENDIX III. (c) Each application for a license under this Agreement shall include, at a minimum, the following information: (1) the poles, ducts, and conduits (including all manholes) along Applicant’s proposed route to or within which Applicant desires to attach or place its facilities; (2) a description of the facilities to be attached to SWBT’s poles and a description of the facilities to be placed within each component of SWBT’s conduit system (including but not limited to ducts, conduits, manholes, and handholes) along the proposed route; (3) for poles, the proposed points of attachment; (4) for building entrance or building distribution ducts or conduits or other space within a building, a conspicuous statement, as required by Section 5.06 of this Agreement, that the application pertains to a building entrance or building distribution duct or conduit or other space within a building; (5) if applicable, a conspicuous notation that the space requested is not to be assigned (or billed) to Applicant until SWBT has received Applicant’s written instruction to make such assignment or issued a license authorizing Applicant to occupy the space requested; and (6) if applicable, a conspicuous statement that Applicant intends to occupy the space before the issuance of a license, as provided in Section 8.03 of this Agreement. (d) Facilities descriptions which apply to multiple pole attachments or conduit occupancies need only be described once on any form. Facilities descriptions shall include, at a minimum, the following information: (1) the number and types of cables, including the physical size (diameter) and weight (weight per foot); (2) the number and types of strands, if any, which will be used to support the cables, including the rated holding capacity expressed in thousand pound increments (e.g., 2.2M) of such strands; and (3) sufficient information to identify and describe the physical characteristics (size, dimensions, and weight) of apparatus enclosures and other facilities to be attached to SWBT’s poles or placed in SWBT’s conduit system. (e) When it appears to Applicant that facilities modification, capacity expansion, or make-ready work may be required to accommodate Applicant’s access requests, Applicant shall describe the facilities modification, capacity expansion, or make-ready work which Applicant proposes. Applicant shall also describe its plans, if any, to use any infrequent construction technique or connectivity solution authorized under Section 6.03 to avoid high or unusual expenditures and state its reasons for the use of such technique or solution. (f) Applicant acknowledges that the poles along a particular pole line or route may include poles owned by firms (such as electric utilities) other than SWBT, that it may be necessary for SWBT to rearrange its facilities or perform other make-ready work on poles other than poles it owns or controls in order to accommodate Applicant’s request for access to SWBT’s poles and that, at the time an application is submitted, it may be difficult for Applicant to determine with certainty whether a particular pole is owned or controlled by SWBT or by another entity. Accordingly, the application shall, to the extent feasible, identify all poles utilized by SWBT (without regard to ownership) along Applicant’s proposed route. (g) Each application for a license under this Agreement shall be accompanied by a construction schedule showing Applicant’s projected dates for beginning and completing construction at the sites specified in the application. Information on this schedule may be used by SWBT’s engineering and outside plant construction personnel in scheduling work required to process Applicant’s applications and scheduling such capacity expansions, make- ready work, and facilities modifications, if any, as may be necessary to accommodate Applicant’s facilities. (h) Applicant may include multiple cables in a single license application and may provide multiple services (e.g., CATV and non-CATV services) under the same cable sheath or jacket. When both CATV and non-CATV services are provided under the same cable sheath or jacket, or CATV and non-CATV services are provided using different cables attached or lashed to the same strand or otherwise occupying the same space on a pole or the same duct or inner duct within a conduit, Applicant will so advise SWBT and SWBT shall, if permitted by law, adjust its charges to enable SWBT to charge Applicant the rate applicable to telecommunications carriers rather than the rate applicable to cable television systems solely to provide cable service.

  • Application Procedure 7.4.1. Application Priority........................................ 7.4.2. [Reserved].................................................. 7.4.3. Advance Payments............................................

  • Application Process The employees wishing to enter into a job share arrangement will apply in writing to the Employer and forward a copy to the Union outlining the proposed commencement date of the job share, how the hours and days of work will be shared and how communication and continuity of work will be maintained. The Employer shall communicate a decision on a job share request in writing to the applicants. Applications to Job Sharing shall not be unreasonably denied.

  • Application Submission Submissions of a rental application does not guarantee approval or acceptance. It does not bind us to accept the application or to sign a Lease contact.

  • Application Procedures i) An employee applies for a listing on the system-wide registry through the employee’s Human Resources Department by completing the form in Appendix A. ii) The institution will immediately forward the completed form to the PSEA who will list eligible employees on the system-wide registry. iii) A registrant is responsible to ensure the information is current and to immediately notify the Employer and the local Union if the registrant is no longer available for employment through the Registry.

  • Directory Assistance Service Updates 8.3.3.1 BellSouth shall update end user listings changes daily. These changes include: 8.3.3.1.1 New end user connections 3.3.1.2 End user disconnections

  • 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 License Terms (a) Software that is made available by a Provider to Recipient in connection with any Service (any such Software being referred to herein as “TSA-Licensed Software”) provided hereunder will be subject to the terms set forth in this Section 3.5 except as otherwise provided in the applicable Service Schedule. The Provider hereby grants to the Recipient a non-exclusive, non-transferable license to use, in object code form, any TSA-Licensed Software that is made available by the Provider pursuant to a Service Schedule. For the avoidance of doubt, the Provider that makes available any TSA-Licensed Software in connection with the provision of any Service retains the unrestricted right to enhance or otherwise modify such TSA-Licensed Software at any time, provided that such enhancements or other modifications do not disrupt the provision of such Service to the Recipient. (b) The Recipient may not exceed the number of licenses, agents, tiers, nodes, seats, or other use restrictions or authorizations, if any, specified in the applicable Service Schedule. Some TSA-Licensed Software may require license keys or contain other technical protection measures. The Recipient acknowledges that the Provider may monitor the Recipient’s compliance with use restrictions and authorizations remotely, or otherwise. If the Provider makes a license management program available which records and reports license usage information, the Recipient agrees to appropriately install, configure and execute such license management program. (c) Unless otherwise permitted by the Provider, the Recipient may only make copies or adaptations of the TSA-Licensed Software for archival purposes or when copying or adaptation is an essential step in the authorized use of TSA-Licensed Software. If the Recipient makes a copy for backup purposes and installs such copy on a backup device, the Recipient may not operate such backup installation of the TSA-Licensed Software without paying an additional license fee, except in cases where the original device becomes inoperable. If a copy is activated on a backup device in response to failure of the original device, the use on the backup device must be discontinued when the original or replacement device becomes operable. The Recipient may not copy the TSA-Licensed Software onto or otherwise use or make it available on, to, or through any public or external distributed network. Licenses that allow use over the Recipient’s intranet require restricted access by authorized users only. (d) The Recipient must reproduce all copyright notices that appear in or on the TSA-Licensed Software (including documentation) on all permitted copies or adaptations. Copies of documentation are limited to internal use. (e) Notwithstanding anything to the contrary herein, certain TSA-Licensed Software may be licensed under the applicable Service Schedule for use only on a computer system owned, controlled, or operated by or solely on behalf of the Recipient and may be further identified by the Provider by the combination of a unique number and a specific system type (“Designated System”) and such license will terminate in the event of a change in either the system number or system type, an unauthorized relocation, or if the Designated System ceases to be within the possession or control of the Recipient. (f) The Recipient will not modify, reverse engineer, disassemble, decrypt, decompile, or make derivative works of the TSA-Licensed Software. Where the Recipient has other rights mandated under statute, the Recipient will provide the Provider with reasonably detailed information regarding any intended modifications, reverse engineering, disassembly, decryption, or decompilation and the purposes therefor. (g) The Recipient may permit a consultant or subcontractor to use TSA-Licensed Software at the licensed location for the sole purpose of providing services to the Recipient. (h) Upon expiration or termination of the Service Schedule under which TSA-Licensed Software is made available, the Recipient will destroy the TSA-Licensed Software. The Recipient will remove and destroy or return to the Provider any copies of the TSA-Licensed Software that are merged into adaptations, except for individual pieces of data in the Recipient’s database. The Recipient will provide certification of the destruction of TSA-Licensed Software, and copies thereof, to the Provider. The Recipient may retain one copy of the TSA-Licensed Software subsequent to expiration or termination solely for archival purposes. (i) The Recipient may not sublicense, assign, transfer, rent, or lease the TSA-Licensed Software to any other person except as permitted in this Section 3.5. (j) The Recipient agrees that the Provider may engage a third party designated by the Provider and approved by the Recipient (such approval not to be unreasonably withheld) to audit the Recipient’s compliance with the Software License terms. Any such audit will be at the Provider’s expense, require reasonable notice, and will be performed during normal business hours. Such third party will be required to execute a non-disclosure agreement that restricts such third party from disclosing confidential information of the Recipient to the Provider, except to the extent required to report on the extent to which the Recipient is not in compliance with the Software License terms.

  • Notice, Application In the case of any Loan, the Administrative Agent shall have received a Notice of Borrowing and, in the case of any Issuance of any Letter of Credit, the Issuing Lender and the Administrative Agent shall have received an L/C Application or L/C Amendment Application, as required under Section 3.2.

  • New Application for Licensure Any time after the three-month period has lapsed from the Effective Date of this Agreement and Respondent has paid the Administrative Penalty set forth in Section III, Paragraph 1 of this Order, Respondent may apply for a new mortgage loan originator license or, as applicable, petition for the reinstatement of an MLO Activity Endorsement in any or all of the Participating States with the understanding that each State Mortgage Regulator reserves the rights to fully investigate such application for licensure or petition for reinstatement of an MLO Activity Endorsement and may either approve or deny such application or petition pursuant to the normal process for such licensing or endorsement investigations. No license application or petition described in this paragraph will be denied solely based on the facts, circumstances, or consensual resolution provided for in this Agreement. Respondent further agrees that Respondent must satisfy the Administrative Penalty provision prior to submitting an application for a new mortgage loan originator license or, as applicable, petition for the reinstatement of an MLO Activity Endorsement.

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