Deploy. Deploy is the sixth and final stage in the lifecycle. During the Deploy stage the applications are moved to production; all requisite pre-production activities are identified, tracked and completed, and post-production analysis and review is completed. Upon moving to production, the Accela Automation applications are transitioned to the Accela Customer Resource Center (‘CRC”) for ongoing support. A formal transition will occur between the Services team and the CRC that instructs the agency on available communication channels (telephone, email, and online tracking system) and use of the Accela knowledge base. Lastly, all documented issues or enhancement requests will be transitioned from the Services team to the Customer Resource Center. APPENDIX C – DELIVERABLE ACCEPTANCE FORM Please acknowledge acceptance by: A Sign and fax this document to: B Email this document as an attachment to: Xxxxx Software Technologies, Inc. YOUR NAME YOUR TITLE Tel: OR YOUR EMAIL Agency Name: Date: Approving Agency Manager: Xxxxx Manager: Project Name / Code: Contract / Agreement #: Agency agrees that Xxxxx has successfully completed the following Deliverables: Deliverable # Source / Reference Details Service Agreement Agency agrees that Xxxxx has successfully completed the Deliverables described above in accordance with the terms of the related Contract/Agreement. APPROVALS: Agency Name Signature Title Date APPENDIX D – CHANGE ORDER SAMPLE CHANGE ORDER – PAGE 1 Agency: CO #: Project Code: Date: Contract #/ PO #: Initiating Department: Initiated By: Change Category: Product Project Contract Maintenance PROJECT CHANGE DESCRIPTION/TASK SUMMARY:
Deploy. Deployment is defined as the movement of activated volunteers to a staging area or assigned mission location such as the scene of an incident, planned event, or exercise. Out-processing volunteers: Out-processing volunteers refers to the return of equipment, operational debriefing, and any transfer of command or responsibilities. Request: A request is a formal application to ask for a specified number of needed volunteers, typically by local response entities, to the health and medical lead at the local, regional, or state level. Requested timeframe: Requested timeframe is the period of time in which volunteers are requested to report for duty. Responsible entity or entities: A responsible entity or entities refers to an organization at the awardee or subawardee level that is accountable for completing the specific activity or element associated with one or more PHEP performance measures. Tracking volunteers: Tracking volunteers refers to the process, plans, or procedures to capture volunteer activities, roles, or locations. Core Public Pre-Incident Response Volunteers: Volunteers are individuals supporting the public health/medical incident, including medical and non- medical professionals (e.g., from the ESAR-VHP system, Medical Reserve Corps) APPENDICES
Deploy. Deploy is the final phase of the Accela Implementation Methodology. The Deploy Stage starts when all components of the system are developed and unit tested (including all components developed by the Health District), and the system is ready for User Acceptance Testing (UAT). The Health District will prepare for UAT by creating test cases and a test execution plan. Health District will lead the test activities by executing test cases to validate the system is performing processes as defined in the solution inventory. At the completion of UAT, Health District will conduct End User Training and the Health District and Accela will begin to prepare the cutover plan. Once training has completed, the cutover plan will be executed, and the Health District will Go‐Live on the Accela solution. Accela will provide post‐production support to address bugs that are identified. The Accela team will then transition the Health District to the Accela Customer Support team for on‐going support.
Deploy. 1. Cut-Over, contingency planning, and post production support; and
Deploy. D4.1 report on pilot deployment in business informa- tion sector. FP7 ICT DEPLOY Project, January 2010. Deliver- able D21 – Online at xxxx://xxx.xxxxxx-xxxxxxx.xx/.
Deploy. Deploy is the sixth and final stage in the lifecycle. During the Deploy stage, the applications are moved to production; all requisite pre-production activities are identified, tracked and completed, and post-production analysis and review is completed. Upon moving to production, the relevant aspects of Accela Civic Platform applications are transitioned to the Accela Customer Support Center (“CSC”) for ongoing support. A formal transition occurs between the Accela Professional Services team and the CSC. The CSC instructs the Agency on available communication channels (e.g., telephone, email, online tracking system) and usage of the Accela knowledge base. Lastly, all documented issues or enhancement requests will be transitioned from the Accela Professional Services team to the CSC. SCOPE OF SERVICES The purpose of this section is to detail the departments, products and high level activities that comprise the Accela implementation for the Agency. AGENCY DEPARTMENTS The scope of this implementation is limited to the following Agency departments: • Planning • Building • Public Works • Code Enforcement • Fire • Business Licensing • Public Utilities • Audit ACCELA PRODUCTS The following products are licensed for this Implementation; the Parties shall consider ePlanCheck an Accela software product for all purposes stated herein: • Accela Civic Platform Land Management • Accela Civic Platform Licensing and Case Management • Accela Mobile • Accela Citizen Access • Accela GIS • ePlanCheck PROJECT SCOPE The Deliverable Summary table below provides a list of the project deliverables. Appendix C contains a detailed description of each deliverable as well as the responsibilities of Accela and the Agency in the creation, review, and approval of the deliverables. Deliverable Summary Stage Deliverable # Deliverable Name Initiation 1 Project Initiation
Deploy. “Deploy” means to distribute the Products via loan or rental to Provider Customers in connection with a Provider Service.
Deploy. 4.2.1 Configuration The purpose of the “Configuration” process is to make an Element compliant with the relevant standards, and, in the case of non-standard configurations, making them capable of being used in conjunction with the balance of the IT Environment to the extent possible. The Configuration process includes the following activities: 1 Performing the Configure process in accordance with the relevant standards, including initially integrating software , hardware and making any operational selections required; 2 Documenting the configuration of an element and providing the configuration to Configuration Management;
Deploy. Our team works with you to roll out Voilà! to your users community and monitor the new business processes against the business objectives to ensure success and acceptance.
Deploy. Managing XXX’x Computer Inventory: Second Fundamental Principle Adhere to common software images across campus • New computers are configured with a standard set of software including a current operating system, office productivity applications, anti-malware software, and remote administration tools. Note that users may request additional software installations on their computer – see
