Technical Design. The Provider shall use software languages and tools for which resources are widely available in the market. The Provider shall generate a technical system design and update the requirements traceability matrix to reflect the relationship between requirements and design elements. The Provider shall conduct informal reviews of the design as it is developed and provide the Department with access to informal review information and documentation. At the completion of the system development, the Provider shall confirm that the technical system design is updated to represent the “as built” new system components and any necessary integration points with the existing ACCESS Florida System. After the initial approval of the technical system design or updated requirements traceability matrix, or any portion thereof, the Provider shall report all issues with the approved design. The Provider shall maintain a database of all reported issues, document the issues in the issues log, and document the resolution of all reported issues. The Provider shall provide the Department with direct access to the issues log. The following sections define the responsibilities of the Provider and the Department. Provider Technical Design Responsibilities Prepare the technical system design deliverables. Create and refine the database design. Document technical system design issues and decisions in the deliverables. Conduct a walk-through of the deliverables. Revise deliverables as a result of the review and approval process. Department Technical Design Responsibilities Review and approve the technical system design deliverables. Provide policy, regulation, forms, and procedural reference material and interpretations as needed. Design Phase - Business Process Reengineering The Provider shall work with stakeholders to create reengineered, future state Department and Partner business processes to reflect the approved system design and shall document and rollout the new business processes to the Department and Partners. The future state business processes shall be designed to enable the stakeholders to effectively employ the new system components to realize the full benefits of the implementation of the new system components. All in scope business processes shall be documented in a final To-Be Process Models document and provided to the Department for approval. The following sections define the responsibilities of the Provider and the Department. Provider Business Process Reengineering Resp...
Technical Design. In collaboration with the Client and the Project Team, review the Stage 3 report and agree the format, outputs and programme required for the Stage 4 report. Attend Client and Project Team meetings as required.
Technical Design. All information, technical details and/or data (or particulars of the offer) called for in the Goods Information or in the referenced specifications will be submitted by the tendering Supplier with his tender as separate returnable schedules in appropriate format. Each schedule will be titled to reflect its content and will be signed and dated by the tendering Supplier. A list of such schedules will be given in this returnable schedule. Signed Date Name Position Tenderer
Technical Design. All Work to be performed, including general direction and guidance in connection with the Work, is to be coordinated with, and will be subject to the approval of LCI's Technical Representative. Nothing in this paragraph shall diminish Contractor's responsibilities to supervise and manage the NOC project hereunder.
Technical Design. FP.1 Facilitate, chair and attend meetings to discuss and develop the Technical Design and tender process
Technical Design. The ProBleu catalogue is designed to facilitate the sharing of content linked to water literacy subjects. Its primary functions are to allow educators to upload content, search for materials, create resource bundles in preparation of lesson plans, and download this content to their devices. It is intended that these materials will be adapted by educators for the specific needs for their classroom. Finally, sharing resource bundles back in modified form should be supported to aid the efforts of other educators, and result in a gradually expanding catalogue.
Technical Design. 4.5.4.1 Abstract datamodel
4.5.4.2 Interfaces
4.5.4.3 Conformance Criteria
Technical Design. 4.1 Prepare and collate tender information to enable a tender or tenders to be obtained.
4.2 Agree the appropriate form of building contract with the Churches Conservation Trust.
4.3 Pass information to Principal Designer for pre-tender Health & Safety Plan.
4.4 Agree list of tenderers with Churches Conservation Trust.
4.5 Obtain tender prices from agreed list of tenderers, and copy all tender information to Churches Conservation Trust.
4.6 Obtain statutory consents e.g. listed building consent, scheduled monument consent, as necessary (alternatively may be obtained at Developed Design stage if agreed with the Churches Conservation Trust).
4.7 Deal with any subsequent tender actions, e.g. extensions of tender period.
4.8 Provide appraisal and tender report on tender submissions.
4.9 If instructed, revise production information to meet adjustments in Churches Conserva- tion Trust budget.
Technical Design. 4.9.3.1. Interfaces
1. / Statistic/update/<module>?Parameters
Technical Design. Occurs when the Development environment is refreshed with a mirror of the Production environment code base. Development: Occurs after code fixes have been installed in the Development environment. UAT: Occurs after the deployment of the code base from the Development environment to the Stage environment. Once the Gate deliverables are accepted by the State, the Contractor shall proceed with the next Release as specified in the IMS. The Contractor shall participate in development of an integrated plan and schedule for DDI and M&O activities the plan will include project activities that are scheduled to occur through the end of the Contract term.
