Process Details Sample Clauses

Process Details. There are multiple drivers which can result in new firmware for Comms Hubs, the most frequent being: o Mandated Technical Specification uplifts; o Testing defects, operational incidents, production problems, technical issue resolution; and o Manufacturer product enhancement To manage the multiple demands into new firmware for any given Comms Hub product DCC has created the governance mechanisms within this stage of the firmware delivery lifecycle. This allows DCC and service delivery partners to determine the content of Comms Hub firmware releases and this in turn creates the framework to provide clear visibility for the forward schedule of change. As part of this governance, consideration is given to key elements e.g. inputs from the drivers of change into the DCC Change Process, demands of the business and changes in priority. Regular engagement and governance has been established between all key internal DCC stakeholders and our service delivery partners. Primarily this engagement either discusses upcoming required change or ratifies content decisions before they are committed for technical delivery. The meetings also discuss the priority of functionality being developed and the associated delivery timelines with the decisions being made. Where agreements necessitate Comms Hub firmware changes are required, the development, testing and release of the firmware are planned to align with the appropriate SEC System Release, Planned Maintenance Release or Unplanned Maintenance Release. Should the need arise governance and delivery processes for emergency or security releases are also managed within this framework. Such events inevitably require previous agreements to be reprioritized and re-planned, the key stakeholders involved in this process assess the options available and recommend the course of action. The governance process has decision making capability, but decisions are reviewed and endorsed by DCC and Service Delivery Partner leaders, as well as dealing with any contentions which require resolution. The “Firmware OTA Deployment” stage describes Comms Hub firmware deployment but it is worth stating that Comms Hub firmware OTA deployments will not target specific release windows across the whole deployed estate, as the firmware will be deployed to the estate systematically over a period of time.
Sample 1Sample 2
AutoNDA by SimpleDocs
Process Details. It is DCC’s priority to ensure that the end to end firmware lifecycle has been followed before DCC and the CSPs decide to promote the firmware for manufacturing use. This decision point determines when a new firmware version will be manufactured. The fixes in the new firmware or other conditions like adherence to specifications may mean that use of the new firmware for manufacturing may need to be mandated at some point but wherever possible DCC will endeavour to allow the selection process defined above to make the decision. Comms Hub firmware that is deemed suitable for manufacturing will have: ▪ passed all DCC test phases (PIT / SIT) ▪ been tested by DCC Customers in UIT environments ▪ no high severity operational issues accepted against it ▪ DCC Operational Acceptance
Sample 1Sample 2
Process Details. Piloting Comms Hub firmware in partnership with DCC Customers in production is one of the key steps in the introduction of new firmware to the production Comms Hub estate. The pilots provide DCC an opportunity to monitor the performance of the new firmware in the production environment and provide DCC Customers the opportunity to verify the new firmware in relation to the production device combinations they are operating at that time. Significant confidence in the Comms Hub firmware is established in the testing phases described in the Firmware Development and Testing stage, firmware is not granted operational approval if quality criteria has not been met. However, the pilots during the Firmware OTA Deployment stage are crucial in establishing final confidence that the new firmware can be deployed to the production Comms Hub estate. DCC will aim to undertake the roll out of new Comms Hub firmware in partnership with customers so that any impact can be assessed before mass roll out begins. The intention is to follow this pilot approach for as many new Comms Hub firmware releases as possible, however in exceptional circumstances in order to manage the production estate effectively DCC may need to roll out emergency or security releases without pilots. DCC will do its upmost not to remove this vital phase unless required to do so and would still work as closely with DCC Customers before any such deployment. DCC will ensure that the key role of customers and communication is not affected so that these exceptional events can be managed in partnership to deliver successful deployment of any new firmware. The indicative high-level approach to be used during pilots has been outlined below so that customers can gain insight into the approach DCC would aim to follow. Based on experience of running pilots in production factors like change complexity, associated risk and volumes mean pilots need to be adjusted. As a result variables like duration of pilot phases, number of phases and so on need to be set per firmware to ensure the pilots deliver the required confidence. DCC will communicate the details of each pilot plan with DCC Customers and other stakeholders and incorporate any additional changes which may be required. The indicative approach would broadly align to the following three phases.
Sample 1
Process Details. Supporting Restart Participants When a Restart Agreement is approved, Providers should offer post-placement support to Restart Participants and Employers as required. This allows Providers to support Restart Participants and Employers to maximise the success of Restart Placements, including after a Restart Participant is Suspended or Exited from a Provider’s caseload. Restart Amount $10,000 (GST inclusive) is payable per Restart Placement for Employment of a six month duration that satisfies all other eligibility requirements.
Sample 1
Process Details. The community will conduct the following tasks to complete the MVP 2.0 process as outlined in the MVP 2.0
Sample 1
Process Details. The Generator, in accordance with the Rules, shall provide the entire process details, which lead to generation of Hazardous Waste, to the Operator for the purpose of determining the Waste Characteristics and to decide parameters for Comprehensive Analysis, as well as its final pathway of treatment, storage and disposal within 15 days from the date of signing of this Agreement. In case of any change in the process, the Generator shall intimate the changes to the Operator before sending the waste from the changed process to the Facility.
Sample 1

Related to Process Details

  • TECHNICAL EVALUATION (a) Detailed technical evaluation shall be carried out by Purchase Committee pursuant to conditions in the tender document to determine the substantial responsiveness of each tender. For this clause, the substantially responsive bid is one that conforms to all the eligibility and terms and condition of the tender without any material deviation. The Institute’s determination of bid’s responsiveness is to be based on the contents of the bid itself without recourse to extrinsic evidence. The Institute shall evaluate the technical bids also to determine whether they are complete, whether required sureties have been furnished, whether the documents have been properly signed and whether the bids are in order.

  • Contact details (a) Except as provided below, the contact details of each Party for all communications in connection with the Finance Documents are those notified by that Party for this purpose to the Facility Agent on or before the date it becomes a Party.

  • Notice Details Party A: Swiss Re Financial Products Corporation Address: 00 Xxxx 00/xx/ Xxxxxx 00/xx/ Xxxxx Xxx Xxxx XX 00000 XXX Facsimile No.: +0 000 000 0000 Attention: Head of Operations Party B: Permanent Financing (No. 6) PLC Address: Xxxxxxxxx Xxxxx Xxxxxxxxx Xxxx Xxxxxx XX0X 0XX Facsimile Number: 020 7566 0975 Attention: The Secretary With a copy to: (i) the Security Trustee:

  • Tests and Preclinical and Clinical Trials The preclinical studies and clinical trials conducted by or, to the Company’s knowledge, on behalf of the Company, that are described in the Registration Statement, the Pricing Disclosure Package and the Prospectus, as applicable, and are intended to be submitted to FDA or other comparable government entities, were and, if still ongoing, are being conducted in all material respects in accordance with experimental protocols, procedures and controls pursuant to accepted professional scientific standards and all Authorizations and Applicable Laws, including, without limitation, the Federal Food, Drug and Cosmetic Act and the rules and regulations promulgated thereunder and for studies submitted to regulatory authorities for approval, current Good Clinical Practices and Good Laboratory Practices and any applicable rules and regulations of the jurisdiction in which such trials and studies are being conducted; the descriptions of the results of such studies and trials contained in the Registration Statement, the Pricing Disclosure Package and the Prospectus are, to the Company’s knowledge, accurate and complete in all material respects and fairly present the data derived from such studies and trials; except to the extent disclosed in the Registration Statement, the Pricing Disclosure Package and the Prospectus, the Company is not aware of any studies or trials, the results of which the Company believes reasonably call into question the study or trial results described or referred to in the Registration Statement, the Pricing Disclosure Package and the Prospectus when viewed in the context in which such results are described and the clinical stage of development; and, except to the extent disclosed in the Registration Statement, the Pricing Disclosure Package or the Prospectus, the Company has not received any written notices or written correspondence from the FDA or any governmental entity requiring the termination or suspension of any preclinical studies or clinical trials conducted by or on behalf of the Company, other than ordinary course communications with respect to modifications in connection with the design and implementation of such trials, copies of which communications have been made available to you.

  • Program Evaluation The School District and the College will develop a plan for the evaluation of the Dual Credit program to be completed each year. The evaluation will include, but is not limited to, disaggregated attendance and retention rates, GPA of high-school-credit-only courses and college courses, satisfactory progress in college courses, state assessment results, SAT/ACT, as applicable, TSIA readiness by grade level, and adequate progress toward the college-readiness of the students in the program. The School District commits to collecting longitudinal data as specified by the College, and making data and performance outcomes available to the College upon request. HB 1638 and SACSCOC require the collection of data points to be longitudinally captured by the School District, in collaboration with the College, will include, at minimum: student enrollment, GPA, retention, persistence, completion, transfer and scholarships. School District will provide parent contact and demographic information to the College upon request for targeted marketing of degree completion or workforce development information to parents of Students. School District agrees to obtain valid FERPA releases drafted to support the supply of such data if deemed required by counsel to either School District or the College. The College conducts and reports regular and ongoing evaluations of the Dual Credit program effectiveness and uses the results for continuous improvement.

  • Payment Details You will make all Payments due under this Master Agreement by 12:00 P.M., Connecticut time, on the day they are due. You will make all Payments in US Dollars (US$) in immediately available funds. We do not have to make or give "presentment, demand, protest or notice" to get paid. You waive "presentment, demand, protest and notice."

  • Account Details (a) Account for payments to Counterparty: To be provided. Account for delivery of Shares to Counterparty: To be provided.

  • Technical Support Services 2.1 The technical support services (the "Services"): Party A agrees to provide to Party B the relevant services requested by Party B, which are specified in Exhibit 1 attached hereto ("Exhibit 1").

  • Operational Support Systems (OSS The terms, conditions and rates for OSS are as set forth in Section 2.13 of this Attachment.

  • Technology Research Analyst Job# 1810 General Characteristics Maintains a strong understanding of the enterprise’s IT systems and architectures. Assists in the analysis of the requirements for the enterprise and applying emerging technologies to support long-term business objectives. Responsible for researching, collecting, and disseminating information on emerging technologies and key learnings throughout the enterprise. Researches and recommends changes to foundation architecture. Supports research projects to identify and evaluate emerging technologies. Interfaces with users and staff to evaluate possible implementation of the new technology in the enterprise, consistent with the goal of improving existing systems and technologies and in meeting the needs of the business. Analyzes and researches process of deployment and assists in this process.

Time is Money Join Law Insider Premium to draft better contracts faster.