Functional Testing Sample Clauses

Functional Testing. Contractor shall conduct comprehensive functional tests to validate the operation of each SCADA control panel, ensuring all inputs and outputs perform as expected. This testing will be done in unison with the County’s SCADA software supplier and coordinated to test the control system back to the SCADA control center.

Functional Testing. Commissioning Agent shall conduct functional testing in accordance with the Functional Test plans, and shall document and submit to Owner a record of all test results. Commissioning Agent shall prepare completion reports summarizing results of testing, description of deficiencies identified, and corrective action required to correct deficiencies.

Functional Testing a. Following completion of all Work, the subcontractor shall develop and perform a full functional test of all components of the vessel’s switchboard to confirm proper operation. b. This testing shall be performed in conjunction with the vessel’s crew and in the presence of DOT. c. Following acceptance by DOT, the switchboards shall be left in a ready to use condition. d. The subcontractor shall furnish a full report on functional testing performed. e. The subcontractor shall note that this testing may have to be performed when the vessel is back at the SIF Ferry Maintenance Facility (FMF). The subcontractor shall allow for performing the Work at this location. All associated costs shall be borne by the subcontractor.

Functional Testing. Functional testing shall include: 1. Operating the systems and all components through each of the written sequences of operation, as well as all significant modes of operation. 2. Start-up 3. Shutdown

Functional Testing. The Contractor will provide functional testing services, including but not limited to –

Functional Testing. Customer and SEI shall develop an acceptance test plan which will include on-line entry of data, on-line inquiry and reporting, execution of batch posting and reporting processes, and interface testing. The acceptance testing will commence after Customer provides certification of the Trial Database.

Functional Testing. 2.5.1 During Functional Testing, the CxA shall: 2.5.1.1 Review and analyze submittal documents independent of the A/E, and CM if any; 2.5.1.2 Attend meetings with the Contracting Authority/Owner, A/E, and CM if any; 2.5.1.3 Perform site visits and conduct equipment, systems and work verifications; 2.5.1.4 Participate in systems and equipment start-up activities; 2.5.1.5 Perform functional testing, re-testing, and verifications; and 2.5.1.6 Provide reports and checklists related to its activities at this stage to the Contracting Authority/Owner. 2.5.2 The CxA shall functionally test all major HVAC equipment and a percentage of miscellaneous equipment as agreed upon with the Contracting Authority/Owner. If functional testing reveals consistent problems, the CxA shall test a larger sampling in accordance with established industry standards.

Functional Testing. The main purpose of the Functional Test phase is to confirm that decisions made during the configuration phase of the project are in line with THE CITY’s business requirements and that the initial configuration operates as expected. Functional testing will take place on clean, controlled data that is created specifically for the purpose of testing a business function by THE CITY. This allows the project team to isolate and test the configuration prior to moving toward Integrated Testing where converted data will be introduced (along with possible problems). Functional Testing is delivered in two stages. The first stage utilizes scripted scenarios that are common to most UNIVERUS Utility clients. Data (accounts, persons, locations, etc.) are entered into the system and verified at the start of testing. This ensures that the initial testing of the configuration decisions is on “clean data”, to ensure that initial data conversion issues do not cause confusion and to allow the testing to start promptly. In addition, entering this data is an excellent way for the core team to become more familiar with the Univerus Unity suite, our CIS and the SAP Business ByDesign solution. UNIVERUS has developed several core functional testing scenarios that will be the basis for THE CITY’s testing scenarios. The scenarios are divided into two categories, Primary and Secondary, with Primary scenarios being the most common functions and cover the breadth of the Solution’s functionality. Secondary tests are the less often used or back-office functions that while necessary, do not characterize the general operability of the Solution. Primary tests are often used as ‘regression’ tests, used to validate the Solution after every software update and data conversion. The second stage involves Functional Testing of each customized modification, interface, report, form or letter. THE CITY will validate that the functionality provided meets the functional requirements and specifications. The objective of Integrated Testing is to confirm that the delivered UNIVERUS Solution performs as specified in the approved Discovery/Scope Document and Functional Specifications. This includes, but is not limited to: Univerus Unity CIS, SAP ByDesign and Harmony Payroll configured functionality, modifications, interfaces, CSS, bills, service orders, letters, portals, and reports. Most importantly, this testing is conducted on converted data and includes running billing and collection batch processes. In...

Functional Testing. In conjunction with the County, Contractor shall develop tests, which check the compliance of the Project with the functionality and performance described in the performance criteria. Such tests shall be submitted to the County for review and approval. After approval of the tests, Contractor shall run the tests in the presence of County personnel designated by the County.