Executing Sample Clauses

The 'Executing' clause defines the procedures and responsibilities involved in carrying out the terms of an agreement or contract. It typically outlines who is authorized to sign, the manner in which execution must occur (such as requiring signatures from both parties), and may specify the effective date of the agreement. This clause ensures that the contract is formally and properly put into effect, providing legal certainty and clarity about when and how the obligations become binding.
Executing a) Executing consists of the processes used to complete the work defined in the project plan to accomplish the project's requirements. b) Execution process involves coordinating people and resources, as well as integrating and performing the activities of the project in accordance with the project management plan. c) The deliverables are produced as outputs from the processes performed as defined in the project management plan and other frameworks that might be applicable to the type of project at hand.
Executing. Coordinate with PowerSchool SaaS operations team for deployment of the Essentials environment with required SIS connector. o Cloud environment provisioning o Essentials application installation o SFTP folder setup for file exchange • Coordinate with Customer for setup of VPN connection between Customer SIS source environment and PowerSchool cloud environment. Customer is responsible for configuring VPN for district and source systems. • Configure authentication setup utilizing Active Directory or ▇▇▇▇ integration protocols. Customer to provide required Active Directory or ▇▇▇▇ configuration details to enable the integration, and to assist with testing and validation. Current supported ▇▇▇▇ options are: GSuite, ADFS, and Azure AD. • Configure IT developer, district administrator, principal, teacher, and counselor user roles. Row level security for these roles may be built using student schedules, school assignments, or user roles from Active Directory or SIS. • Deployment of standard Essentials dashboard content. o Note: This SOW includes deployment of the standard dashboard content only. Customizations are not included in this SOW. • Entities and data from source systems will be limited to Unified Insights application requirements. Data domains for this implementation will include up to the following: o Students; Schools; Basic Staff; Enrollment; Attendance; Assessment; Discipline; Courses; Curriculum, Period, and Final Marks; Student Schedules; Basic Special Education • SIS Source Data: o Implementation of 1 Unified Insights SIS connector between Unified Insights and 1 supported SIS source system (Infinite Campus State Edition) ▪ Note: Note: It is assumed that all historical SIS data is in the same format as current data. o Perform SIS connector ‘map and gap’ and business logic confirmation and customization for standard content only: ▪ Compare actual source data loaded in Unified Insights data warehouse against expected data. ▪ Perform data validation and identify data discrepancies by data domain to review with Customer ▪ Review data discrepancies with Customer and identify any business logic changes required in the Connector ETL. ▪ Implement and test ETL changes. • US State & National Assessment data: o Customer will be introduced to the Assessment team and educated on the process of working with that team for initial and ongoing upload of standard supported US State and National assessment data, if applicable. ▪ Note: Customer entitlement for standard...
Executing. Jive engineers custom-configure the Jive solution, building dial plans and other features according to customer-provided specifications and preferences. Engineers also complete any specialized integration requirements. Fulfillment specialists order equipment and monitor the number porting process. Regular status calls ensure the transition process stays on-track with established milestones and timelines. Jive quality assurance specialists test every feature to ensure it is operating correctly and in accordance with customer specifications. Engineers test the network configuration and, if applicable, test and turn up the Jive broadband data connection. Fulfillment specialists test E911 configurations in compliance with Federal regulations. All Jive hardware - including handsets, routers, and other equipment - arrives on the customer location pre-provisioned and ready for immediate plug-and-play. Jive PMs and engineers work with the customer to test and verify all system features and functions. Dedicated project system trainers provide administrator and end user training to familiarize the customer with the Jive solution.
Executing. Coordinate with PowerSchool SaaS operations team for deployment of the Risk Analysis environment. • Deployment of Risk Analysis automated predictive engine. • Deployment of standard Risk Analysis dashboard content. o Note: This SOW includes deployment of the standard dashboard content only. Customizations are not included in this SOW. • Perform dashboard metric fitting to align the Customer’s data with the standard dashboard content. o Note: Fitting does not include changes to dashboard layouts, metrics, or adding / removing dashboard data elements, which could all be addressed separately via a dashboard customization. • Perform final system QA • User Training and Consultation: o Deliver standard instructor-led Risk Analysis User Training o Deliver customized SME system roll-out and Adoption Consultation o Total hours included in this SOW for User Training and Adoption Consultation are specified on Customer’s quote • Perform Support handoff and project close.
Executing. The process of coordinating the people and other resources in the performance of the project or the actual performance of the project. Executive level oversight of the project. Typically the next level of management above the Project Governance Committee.
Executing. Upon written request from Lessor or a lender in connection with a sale, financing or refinancing of the Premises, Lessee and Lessor shall execute such further writings as may be reasonably required to separately document any subordination, attornment and/or Non-Disturbance Agreement provided for herein.
Executing. Infinite Campus Connector managed services Executing: PowerSchool SIS Connector managed services Executing: Customization Maintenance managed services Executing: Community Engagement Refresh managed services
Executing. Having finalized the passage plan, as soon as time of departure and estimated time of arrival can be determined with reasonable accuracy, the passage should be executed in accordance with the plan or any changes made thereto. Factors which should be taken into account when executing the plan include: • the reliability and condition of the vessel’s navigational equipment; • estimated times of arrival at critical points for tide heights and flow; • meteorological conditions, (particularly in areas known to be affected by frequent periods of low visibility) as well as weather routeing information; • daytime versus night-time passing of danger points, and any effect this may have on position fixing accuracy; and • traffic conditions, especially at navigational focal points. It is important for the master to consider whether any particular circumstance, such as the forecast of restricted visibility in an area where position fixing by visual means at a critical point is an essential feature of the passage plan, introduces an unacceptable hazard to the safe conduct of the passage; and thus, whether that section of the passage should be attempted under the conditions prevailing or likely to prevail. The master should also consider at which specific points of the passage there may be a need to utilize additional deck or engine personnel.
Executing.  Hold weekly status meetings  Carry out the project plan  Coordinate team resources  Lead the various CenturyLink teams and partner with customer resources  Distribute project information to project stakeholders
Executing. Having finalized the passage plan, as soon as time of departure and estimated time of arrival can be determined with reasonable accuracy, the passage should be executed in accordance with the plan or any changes made thereto. Factors which should be taken into account when executing the plan include: • the reliability and condition of the vessel’s navigational equipment; • estimated times of arrival at critical points for tide heights and flow; • meteorological conditions, (particularly in areas known to be affected by frequent periods of low visibility) as well as weather routeing information; • daytime versus night-time passing of danger points, and any effect this may have on position fixing accuracy; and • traffic conditions, especially at navigational focal points. It is important for the master to consider whether any particular circumstance, such as the forecast of restricted visibility in an area where position fixing by visual means at a critical point is an essential feature of the passage plan, introduces an unacceptable hazard to the safe conduct of the passage; and thus, whether that section of the passage should be attempted under the conditions prevailing or likely to prevail. The master should also consider at which specific points of the passage there may be a need to utilize additional deck or engine personnel.