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.
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
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, exit criteria 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. Communication is undertaken via the weekly Programme UIT review meetings. The purpose of the meetings is to: • Provide customers with an updated view of the firmware release programme and UIT schedule • Gain input as to the progress ...
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.
Process Details. The community will conduct the following tasks to complete the MVP 2.0 process as outlined in the MVP 2.0
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.
