Network Project Sample Clauses

The 'Network Project' clause defines the scope and parameters of a project involving the design, installation, or maintenance of a network infrastructure. It typically outlines the specific tasks to be performed, such as setting up hardware, configuring software, or ensuring connectivity between different systems. This clause ensures that both parties have a clear understanding of the project's objectives, deliverables, and responsibilities, thereby minimizing misunderstandings and helping to manage expectations throughout the project's lifecycle.
Network Project. The Agreement for the implementation of the project in South Sudan was signed in February 2012. The project is at an advanced stage of implementation.
View SourceView Similar (3)
Network Project. The Agreement for the implementation of the project in South Sudan was signed in February 2012. The project is at an advanced stage of implementation. India has two battalions of about 2,000 personnel in the UNMISS, deployed in two of the largest states in South Sudan - Jonglei and Upper Nile. Additionally, there is a police component of around 49 Indian Police officers who are assisting the South Sudan National Police Service in building up the police structures, and a number of civilian officials are in various other departments of UNMISS. The Indian army contingents have been undertaking several social welfare initiatives viz. holding medical camps, donating books to educational institutions, building roads etc., which have been highly appreciated by the local population. On 09 April 2013, 36 Indian soldiers who were escorting a UN convoy from Pibor to Bor in Jonglei State came under heavy attack from the rebels. One senior Indian Army officer and four soldiers got killed and four Indian soldiers were injured. Two Indian soldiers were also killed in an attack on the UN Base at Akobo (Jonglei State) on 19 December 2013. Two Indian soldiers suffered injuries during an attack on the UN Base at Bor, in Jonglei State in April 2014. Presently, there are about 500 Indian nationals in South Sudan. Some of them have set up businesses in Juba and others are working for various companies. A small number of Indian nationals also work in Christian missionary organizations in South Sudan. In addition, as mentioned above, there are 2,000 Indian army peacekeepers, 49 police officers and some civilian officials attached to UNMISS. Indians have been among the first to open hotels, borehole companies, printing press and departmental store in Juba in early 2006. Indian nationals in Juba have formed an Indian Association, whose membership is presently around 300. The Embassy maintains regular contacts with the Indian community in South Sudan and facilitates their various social projects. Athree day medical camp was organized in prominent local hospital in Juba recentlyby a private hospital in India, for the local South Sudanese community and a blood donation camp was organized in January 2014).
View SourceView Similar (2)

Related to Network Project

  • Project 3.01. The Recipient declares its commitment to the objectives of the Project. To this end, the Recipient shall carry out the Project in accordance with the provisions of Article IV of the General Conditions.

  • Infrastructure Modification of the location and/or sizing of the infrastructure for the Project that does not materially change the functionality of the infrastructure.

  • Information Systems Acquisition Development and Maintenance a. Client Data – Client Data will only be used by State Street for the purposes specified in this Agreement.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • NETWORK MAINTENANCE AND MANAGEMENT 38.1 The Parties will work cooperatively to implement this Agreement. The Parties will exchange appropriate information (for example, maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the government, escalation processes, etc.) to achieve this desired result. 38.2 Each Party will administer its network to ensure acceptable service levels to all users of its network services. Service levels are generally considered acceptable only when End Users are able to establish connections with little or no delay encountered in the network. Each Party will provide a twenty four (24)-hour contact number for Network Traffic Management issues to the other’s surveillance management center. 38.3 Each Party maintains the right to implement protective network traffic management controls, such as “cancel to”, “call gapping” or seven (7)-digit and ten (10)-digit code gaps, to selectively cancel the completion of traffic over its network, including traffic destined for the other Party’s network, when required to protect the public-switched network from congestion as a result of occurrences such as facility failures, switch congestion or failure or focused overload. Each Party shall immediately notify the other Party of any protective control action planned or executed. 38.4 Where the capability exists, originating or terminating traffic reroutes may be implemented by either Party to temporarily relieve network congestion due to facility failures or abnormal calling patterns. Reroutes shall not be used to circumvent normal trunk servicing. Expansive controls shall be used only when mutually agreed to by the Parties. 38.5 The Parties shall cooperate and share pre-planning information regarding cross-network call-ins expected to generate large or focused temporary increases in call volumes to prevent or mitigate the impact of these events on the public-switched network, including any disruption or loss of service to the other Party’s End Users. Facsimile (FAX) numbers must be exchanged by the Parties to facilitate event notifications for planned mass calling events. 38.6 Neither Party shall use any Interconnection Service provided under this Agreement or any other service related thereto or used in combination therewith in any manner that interferes with or impairs service over any facilities of AT&T-21STATE, its affiliated companies or other connecting telecommunications carriers, prevents any carrier from using its Telecommunications Service, impairs the quality or the privacy of Telecommunications Service to other carriers or to either Party’s End Users, causes hazards to either Party’s personnel or the public, damage to either Party’s or any connecting carrier’s facilities or equipment, including any malfunction of ordering or billing systems or equipment. Upon such occurrence either Party may discontinue or refuse service, but only for so long as the other Party is violating this provision. Upon any such violation, either Party shall provide the other Party notice of the violation at the earliest practicable time. 38.7 AT&T TENNESSEE hereby commits to provide Disaster Recovery to CLEC according to the plan below. 38.7.1 AT&T TENNESSEE Disaster Recovery Plan 38.7.2 In the unlikely event of a disaster occurring that affects AT&T TENNESSEE’s long-term ability to deliver traffic to a CLEC, general procedures have been developed by AT&T TENNESSEE to hasten the recovery process in accordance with the Telecommunications Service Priority (TSP) Program established by the FCC to identify and prioritize telecommunication services that support national security or emergency preparedness (NS/EP) missions. A description of the TSP Program as it may be amended from time to time is available on AT&T TENNESSEE’s Wholesale – Southeast Region Web site. Since each location is different and could be affected by an assortment of potential problems, a detailed recovery plan is impractical. However, in the process of reviewing recovery activities for specific locations, some basic procedures emerge that appear to be common in most cases. 38.7.3 These general procedures should apply to any disaster that affects the delivery of traffic for an extended time period. Each CLEC will be given the same consideration during an outage, and service will be restored as quickly as possible. AT&T TENNESSEE reserves the right to make changes to these procedures as improvements become available or as business conditions dictate. 38.7.4 This plan will cover the basic recovery procedures that would apply to every CLEC.