Proposed Network Sample Clauses

Proposed Network. CDCR has recently adopted a new network equipment standard for replacing/refreshing currently deployed equipment. The current core HP 5412s standard has been replaced by the HPE/Aruba 8400s as the new standard. All IDF switching is being standardized to the Aruba 3810 with POE+. A complete list of the Network Equipment and Specifications that the Contractor must purchase and use to adhere to CDCR’s standards is shown in Attachment 9. The general network topology is not changing as is shown below in Figure 2-4: New Equipment Standard. CDCR has architected an Inmate Network utilizing VLANs assigned on their IDF network switches to isolate the incarcerated individual traffic from the CDCR network. The Contractor shall incorporate the CTS network connectivity through the use of VLANs that are assigned by CDCR on the IDF switches and allow the CTS traffic to utilize the CDCR pathway to the MDF where it will then be handed off to the CTS Contractor’s router/switch/firewall and access the CTS Contractor’s ISP. This allows the Contractor to use the existing fiber pathway from each of the IDFs that are home run back to the MDF distribution switches. This is depicted at a high level in Figure 2-5: CTS Proposed Network.
AutoNDA by SimpleDocs

Related to Proposed Network

  • Proposed Goods and Services Proposed Goods and Services pdf D/M/WBE Certification OPTIONAL No response Warranty No response

  • PROPOSED MOBILITY PROGRAMME The proposed mobility programme includes the indicative start and end months of the agreed study programme that the student will carry out abroad. The Learning Agreement must include all the educational components to be carried out by the student at the receiving institution (in table A) and it must contain as well the group of educational components that will be replaced in his/her degree by the sending institution (in table B) upon successful completion of the study programme abroad. Additional rows can be added as needed to tables A and B. Additional columns can also be added, for example, to specify the study cycle-level of the educational component. The presentation of this document may also be adapted by the institutions according to their specific needs. However, in every case, the two tables A and B must be kept separated, i.e. they cannot be merged. The objective is to make clear that there needs to be no one to one correspondence between the courses followed abroad and the ones replaced at the sending institutions. The aim is rather that a group of learning outcomes achieved abroad replaces a group of learning outcomes at the sending institution, without having a one to one correspondence between particular modules or courses. A normal academic year of full-time study is normally made up of educational components totalling 60 ECTS* credits. It is recommended that for mobility periods shorter than a full academic year, the educational components selected should equate to a roughly proportionate number of credits. In case the student follows additional educational components beyond those required for his/her degree programme, these additional credits must also be listed in the study programme outlined in table A. When mobility windows are embedded in the curriculum, it will be enough to fill in table B with a single line as described below: Component code (if any) Component title (as indicated in the course catalogue) at the sending institution Semester [autumn / spring] [or term] Number of ECTS* credits Mobility window … Total: 30 Otherwise, the group of components will be included in Table B as follows: Component code (if any) Component title (as indicated in the course catalogue) at the sending institution Semester [autumn / spring] [or term] Number of ECTS* credits Course x … 10 Module y … 10 Laboratory work … 10 Total: 30 The sending institution must fully recognise the number of ECTS* credits contained in table A if there are no changes to the study programme abroad and the student successfully completes it. Any exception to this rule should be clearly stated in an annex of the Learning Agreement and agreed by all parties. Example of justification for non-recognition: the student has already accumulated the number of credits required for his/her degree and does not need some of the credits gained abroad. Since the recognition will be granted to a group of components and it does not need to be based on a one to one correspondence between single educational components, the sending institution must foresee which provisions will apply if the student does not successfully complete some of the educational components from his study programme abroad. A web link towards these provisions should be provided in the Learning Agreement. The student will commit to reach a certain level of language competence in the main language of instruction by the start of the study period. The level of the student will be assessed after his/her selection with the Erasmus+ online assessment tool when available (the results will be sent to the sending institution) or else by any other mean to be decided by the sending institution. A recommended level has been agreed between the sending and receiving institutions in the inter-institutional agreement. In case the student would not already have this level when he/she signs the Learning Agreement, he/she commits to reach it with the support to be provided by the sending or receiving institution (either with courses that can be funded by the organisational support grant or with the Erasmus+ online tutored courses). All parties must sign the document; however, it is not compulsory to circulate papers with original signatures, scanned copies of signatures or digital signatures may be accepted, depending on the national legislation. * In countries where the "ECTS" system it is not in place, in particular for institutions located in partner countries not participating in the Bologna process, "ECTS" needs to be replaced in all tables by the name of the equivalent system that is used and a weblink to an explanation to the system should be added. The section to be completed during the mobility is needed only if changes have to be introduced into the original Learning Agreement. In that case, the section to be completed before the mobility should be kept unchanged and changes should be described in this section. Changes to the mobility study programme should be exceptional, as the three parties have already agreed on a group of educational components that will be taken abroad, in the light of the course catalogue that the receiving institution has committed to publish well in advance of the mobility periods and to update regularly as ECHE holder. However, introducing changes might be unavoidable due to, for example, timetable conflicts. Other reasons for a change can be the request for an extension of the duration of the mobility programme abroad. Such a request can be made by the student at the latest one month before the foreseen end date. These changes to the mobility study programme should be agreed by all parties within four to seven weeks (after the start of each semester). Any party can request changes within the first two to five-week period after regular classes/educational components have started for a given semester. The exact deadline has to be decided by the institutions. The shorter the planned mobility period, the shorter should be the window for changes. All these changes have to be agreed by the three parties within a two-week period following the request. In case of changes due to an extension of the duration of the mobility period, changes should be made as timely as possible as well. Changes to the study programme abroad should be listed in table C and, once they are agreed by all parties, the sending institution commits to fully recognise the number of ECTS credits as presented in table C. Any exception to this rule should be documented in an annex of the Learning Agreement and agreed by all parties. Only if the changes described in table C affect the group of educational components in the student's degree (table B) that will be replaced at the sending institution upon successful completion of the study programme abroad, a revised version should be inserted and labelled as "Table D: Revised group of educational components in the student's degree that will be replaced at sending institution". Additional rows and columns can be added as needed to tables C and D. All parties must confirm that the proposed amendments to the Learning Agreement are approved. For this specific section, original or scanned signatures are not mandatory and an approval by email may be enough. The procedure has to be decided by the sending institution, depending on the national legislation.

  • Unbundled Network Elements 35.4.1. The charges that CLEC shall pay to Sprint for Unbundled Network Elements are set forth in Table One of this Agreement. 35.5. Collocation 35.5.1. The charges that CLEC shall pay to Sprint for Collocation are set forth in Table Two of this Agreement. 35.6. Call Related Databases 6.1. The charges that CLEC shall pay to Sprint for Call Related Databases purchased pursuant to Part J are set forth in Table One of this Agreement.

  • Notice of Network Changes If a Party makes a change in the information necessary for the transmission and routing of services using that Party’s facilities or network, or any other change in its facilities or network that will materially affect the interoperability of its facilities or network with the other Party’s facilities or network, the Party making the change shall publish notice of the change at least ninety (90) days in advance of such change, and shall use reasonable efforts, as commercially practicable, to publish such notice at least one hundred eighty (180) days in advance of the change; provided, however, that if an earlier publication of notice of a change is required by Applicable Law (including, but not limited to, 47 CFR 51.325 through 51. 335) notice shall be given at the time required by Applicable Law.

  • WHOIS query RTT Refers to the RTT of the sequence of packets from the start of the TCP connection to its end, including the reception of the WHOIS response. If the RTT is 5-­‐times or more the corresponding SLR, the RTT will be considered undefined.

  • Bona Fide Request/New Business Request Process for Further Unbundling 6.1 BellSouth shall, upon request of <<customer_name>>, provide to <<customer_name>> access to its network elements at any technically feasible point for the provision of <<customer_name>>'s telecommunications service where such access is necessary and failure to provide access would impair the ability of <<customer_name>> to provide services that it seeks to offer. Any request by <<customer_name>> for access to a network element, interconnection option, or for the provisioning of any service or product that is not already available shall be treated as a Bona Fide Request/New Business Request (BFR/NBR), and shall be submitted to BellSouth pursuant to the BFR/NBR process. 6.2 <<customer_name>> shall submit any BFR/NBR in writing to <<customer_name>>’s Account Manager. The BFR/NBR shall specifically identify the requested service date, technical requirements, space requirements and/or such specifications that clearly define the request such that BellSouth has sufficient information to analyze and prepare a response. The BFR/NBR also shall include <<customer_name>>’s designation of the request as being (i) pursuant to the Telecommunications Act of 1996 or (ii) pursuant to the needs of the business.

  • Unbundled Network Element Combinations 5.1. Unbundled Network Element Combinations shall include: 1) Enhanced Extended Links (EELs); 2) UNE Loops/Special Access Combinations; 3) Loop/Port Combinations; and 4)

  • RDDS query RTT Refers to the collective of “WHOIS query RTT” and “Web-­‐based-­‐ WHOIS query RTT”.

  • DISADVANTAGED BUSINESS ENTERPRISE OR HISTORICALLY UNDERUTILIZED BUSINESS REQUIREMENTS The Engineer agrees to comply with the requirements set forth in Attachment H, Disadvantaged Business Enterprise or Historically Underutilized Business Subcontracting Plan Requirements with an assigned goal or a zero goal, as determined by the State.

  • Help Desk A help desk for Product support issues (the “Help Desk”) will be available to Customer. Unless specified in an Order, Customer should contact 000.000.0000 to receive a telephone number for the applicable supporting Solutions & Support Center. Customer will appoint one Product administrator and one backup administrator to serve as the primary point of contact regarding maintenance services.

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