Quality Control – 1(Quality Control versus Testing)

• Quality Control: (Doing right things; the right way!)– A set of activities designed to ensure that the development and/or

maintenance process is adequate to ensure a system will meet its objectives.

• Testing: (Results = Expectations)– The process of executing a system with the intent to evaluate a

developed work product and find defects. (Note that the "process of executing a system" includes test planning prior to the execution of the test cases.)

Quality Control – 2 (Testing)

• Usability Testing– Conducted by users; to ensure that the new components and features will

function in a manner that is acceptable to the customer

• Unit Testing– Conducted by the developer(s); to ensure that proper functionality and

code coverage have been achieved during coding

• Integration Testing– Conducted by testing team; to ensure that unit tested components are

correctly integrated together; weed out errors caused due to integration

• User Acceptance Testing– Conducted by users; to verify that the product is ready for distribution,

acceptable to the customer and iron out potential non-conformance issues

Quality Control – 3(Quality Control)

• “Controlled” inputs– Use of libraries– Use of defaults; drop downs– Alerts: Compressor not associated to at least one suction group

• “Mapping” DOE Inputs to parameter values – System Type = Integral, Standalone, Multiplex– Condenser Type = Air-cooled, Evaporative

• “Out of bounds” limits for kWh– T12 fluorescent lamps with magnetic ballasts replaced by T8 fluorescent

lamps and electronic ballasts; kWh saving 3 to 10%– Anti-sweat heater controls; kWh saving 2 to 4%– Floating-head pressure controls: kWh saving 3 to 10%

• Transparency Reports