Top

Technical Committee

Function of the Technical Committee

The Technical Committee is the primary body responsible for providing balanced stakeholder oversight of matters relating to the integrity and quality control of the water stewardship system on behalf of members.

It is responsible for reviewing and approving changes to AWS Standard, assurance processes, policies for trademark use by third parties as well as guidance material and policy documents.

The committee is also the primary body responsible for resolution of disputes within the water stewardship system.

The Committee is intended to reflect the broadest diversity possible of AWS members, and if possible should be comprised of a minimum seven members balanced between each stakeholder group (public sector, private sector and civil society).

While there are no specific requirements set in terms of gender and regional origin these matters will be considered by the Board Nominations Committee in recommending members for election at the Annual Members’ Meeting.

Members of the Technical Committee serve for a term of three years with half retiring at each Annual Members’ Meeting.

The Technical Committee Terms of Reference give further information on their role and responsibilities.

Technical Committee Members

Alasdair McGregor (Exova BMTrada), Thomas C. Annear, Jeremy Dufour (Olam), Carlo Galli (Nestle), Professor John Langford (University of Melbourne), Xue Bai (China National Institute of Standards), Tyler Farrow (Water Witness International), Sanjib Bezbaroa (ITC Ltd.), Peter Easton (Easton Consult), Dr. Brigitte Dittrich-Krämer (BASF), Fallight Xu (TUV Rheinland), Dr.Howard Dryden (Dryden Aqua), Laura Kowalski (Sheahen) (Ecolab), Elizabeth Soal (Waitaki Irrigators Collective), Dale K. Phenicie (Council of Great Lakes Industries), Nicole Tanner (WWF), Ruth Mathews
(Water Footprint Network) and Helen Murdoch (Goulburn-Broken Catchment Management Authority).

Work Programme Q1-2 2017

Further details of the 2017 Work Plan for the Technical Committee will be published here soon.

Project

Scope

Tasks

Timeline

AWS Standard Review

Review of implementation to date of the Standard and identification of scope of the revision.

 

·      Devise and launch the review to get feedback on the standard from users.

·      Analyse the feedback and make recommendation to the full Technical Committee for the scope of the AWS Standard revision.

·      Launch end Feb 2017 for 30 days

·      Recommendations April 2017.

·      Start 1st Draft April 2017.

AWS Theory of Change & Impacts

 

Devise Theory of Change for AWS, to guide AWS Impacts work. ·      Review and revise as needed current Draft ToC.

·      Update Impacts Procedures.

·      Review ToC February 2017.

·      Impacts Report for ISEAL by 31st March 2017.

Risk Framework

 

Plan to address risk to the integrity of the AWS assurance system. Such a plan must include the most significant risks in the system and the strategies employed to address these risks. ·      Analyse the Assurance System to assess risks.

·      Produce plan to address the risks.

·      February 2017.

 

·      April 2017.

AWS Assurance Requirements – Rapid Review

 

Review barriers to uptake whilst maintaining integrity of the system ·      Review Certification and Accreditation Requirements.

·      Present recommendations to the TC.

·      February 2017.

 

 

 

·      Re-launch April 2017.