Systems Development Lifecycle Management Sample Clauses

Systems Development Lifecycle Management. Prior to the commencement of work, the selected Vendor shall submit a description of the SDLC Methodology that it will use for the MEMS, for review, comment, and approval by CHFS. The selected Vendor shall deliver the solution using a phased development approach that supports the Commonwealth’s requirement to review and test iterations of development of logical functional groups of system components, before proceeding to the System Test phase. Therefore, the plan for the Development Phase shall account for durations of Commonwealth testing and feedback, and System updates by the Vendor, prior to the completion of the Development phase for each iteration.
AutoNDA by SimpleDocs

Related to Systems Development Lifecycle Management

  • Program Management 1.1.01 Implement and operate an Immunization Program as a Responsible Entity 1.1.02 Identify at least one individual to act as the program contact in the following areas: 1. Immunization Program Manager;

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

  • Project Management Project Management Institute (PMI) certified project manager executing any or all of the following: • Development of Project Charter • Development of project plan and schedule • Coordination and scheduling of project activities across customer and functional areas • Consultation on operational and infrastructure requirements, standards and configurations • Facilitate project status meetings • Timely project status reporting • Address project issues with functional areas and management • Escalation of significant issues to customers and executive management • Manage project scope and deliverable requirements • Document changes to project scope and schedule • Facilitate and document project closeout

  • Project Management Plan 3.2.1 Developer is responsible for all quality assurance and quality control activities necessary to manage the Work, including the Utility Adjustment Work. Developer shall undertake all aspects of quality assurance and quality control for the Project and Work in accordance with the approved Project Management Plan, Good Industry Practice and applicable Law. 3.2.2 Developer shall develop the Project Management Plan and its component parts, plans and other documentation in accordance with the requirements set forth in Section 1.5.2.5

  • SITE MANAGEMENT We reserve the right, but not the obligation, to: (1) monitor the Site for violations of these Terms of Use; (2) take appropriate legal action against anyone who, in our sole discretion, violates the law or these Terms of Use, including without limitation, reporting such user to law enforcement authorities; (3) in our sole discretion and without limitation, refuse, restrict access to, limit the availability of, or disable (to the extent technologically feasible) any of your Contributions or any portion thereof; (4) in our sole discretion and without limitation, notice, or liability, to remove from the Site or otherwise disable all files and content that are excessive in size or are in any way burdensome to our systems; and (5) otherwise manage the Site in a manner designed to protect our rights and property and to facilitate the proper functioning of the Site.

  • Project Development a. Collaborate with COUNTY and project clients to identify requirements and develop a project Scope Statement. a. Develop a Work Breakdown Structure (WBS) for each project. b. Evaluate Scope Statement to develop a preliminary cost estimate and determinate whether project be vendor bid or be executed under a Job Order Contract (JOC).

  • General Management In the discharge of its general duty to manage the successful performance of the Services, Vendor shall: 3.2.1.1. within thirty (30) calendar days of the Effective Date, identify to Citizens the primary and secondary management contacts responsible for the oversight and management of Services for Citizens; 3.2.1.2. ensure Vendor Staff tasked with management and oversight of the Services are available promptly to perform Services during Business Hours; 3.2.1.3. ensure each assigned Adjuster submits a time record directly to Vendor’s manager or point of contact. At any time during this Agreement, Citizens may require copies of time records from Vendor; 3.2.1.4. ensure that no Vendor Staff carries a weapon on their person while performing Services; 3.2.1.5. ensure that no Vendor Staff uses impairing drugs, chemicals, or alcohol while performing Services; 3.2.1.6. ensure that Vendor Staff avoid using their duties and obligations under this Agreement to engage in any conduct that could create either an actual or perceived conflict of interest, such as due to an ongoing business relationship with an entity other than Citizens that would enable Vendor Staff to receive an improper benefit or unfair competitive advantage; 3.2.1.7. ensure that the Services comply with the Best Claims Practices & Estimating Guidelines as applicable to each Service Category and any other policies or processes set forth by Citizens, including but not limited to: a. monitoring applicable file production on a weekly basis to determine compliance with Citizens’ production requirements; and, b. providing detailed reports to Citizens related to Vendor performance upon request.

  • Staff Development ‌ The County and the Association agree that the County retains full authority to determine training needs, resources that can be made available, and the method of payment for training authorized by the County. Nothing in this subsection shall preclude the right of an employee to request specific training.

  • Synchronization, Commissioning and Commercial Operation 4.1.1 The Power Producer shall give at least fifteen (15) days written notice to the SLDC / ALDC / DISCOM as the case may be, of the date on which it intends to synchronize the Power Project to the Grid System. 4.1.2 Subject to Article 4.1.1, the Power Project may be synchronized by the Power Producer to the Grid System when it meets all the connection conditions prescribed in the Grid Code and otherwise meets all other Indian legal requirements for synchronization to the Grid System. 4.1.3 The synchronization equipment and all necessary arrangements / equipment including Remote Terminal Unit (RTU) for scheduling of power generated from the Project and transmission of data to the concerned authority as per applicable regulation shall be installed by the Power Producer at its generation facility of the Power Project at its own cost. The Power Producer shall synchronize its system with the Grid System only after the approval of GETCO / SLDC / ALDC and GEDA. 4.1.4 The Power Producer shall immediately after each synchronization / tripping of generator, inform the sub-station of the Grid System to which the Power Project is electrically connected in accordance with applicable Grid Code. 4.1.5 The Power Producer shall commission the Project within SCOD. 4.1.6 The Power Producer shall be required to obtain Developer and/ or Transfer Permission, Key Plan drawing etc, if required, from GEDA. In cases of conversion of land from Agricultural to Non-Agriculture, the commissioning shall be taken up by GEDA only upon submission of N.A. permission by the Power Producer. 4.1.7 The Power Producer shall be required to follow the Forecasting and Scheduling procedures as per the Regulations issued by Hon’ble GERC from time to time. It is to clarify that in terms of GERC (Forecasting, Scheduling, Deviation Settlement and Related Matters of Solar and Wind Generation Sources) Regulations, 2019 the procedures for Forecasting, Scheduling & Deviation Settlment are applicable to all solar generators having combined installed capacity above 1 MW connected to the State Grid / Substation including those connected via pooling stations.

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

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