Structure and Operation / PAC-TECH-002
Page 1 of 9
PAC Technical Committee
Structure and Operation
Issue 2.0
Issue Date: 27 October 2015Application Date: Immediate
TABLE OF CONTENTS
1TERMS OF REFERENCE3
2OPERATION3
ANNEX 1
PAC DISCUSSION PAPER6
ANNEX 2
DRAFT AGENDA FOR PAC TC MEETING7
ANNEX 3
PAC TC STRUCTURE9
1Terms of Reference
1.1The terms of reference of the PAC Technical Committee (TC) shall be defined in the “PAC Structure” document (PAC-EXEC-005).
2Operation
2.1The PAC TC shall operate as a mirror committee to the International Accreditation Forum Technical Committee(IAF TC).
2.1.1The PAC TC may establish Working Groups(WGs) or Taskforces (TFs) to monitor the developments of the IAF TC as deemed appropriate. One or more representatives from the PAC TC shall be identified to take part in the relevant IAF TC WGs/TFs.
2.1.2Whenever there are any significant aspects/issues to be discussed in the IAF TC, which may lead to concerns by PAC members, the PAC members may request the opinion from the PAC mirror committee. The PAC mirror committees have to respond and share their view with all PAC members at least 2 weeks before the next IAF TC meeting.
2.1.3The PAC TC representatives are responsible for conveying the PAC position to their relevant IAF TC WGs/TFs and for reporting the IAF progress to the PAC TC at its annual meeting.
2.1.4The list of PAC TC representatives to the IAF TC shall be updated each year during the PAC TC meeting. The PAC Secretariat shall keep the updated list.
2.2The PAC TC may develop PAC-specific technical documents to support regional needs for accreditation programs within Asia-Pacific.
2.2.1The PAC TC may establish WGs/TFs to carry out specific activities. The Convenor of each new WG/TF shall be appointed with the approval of the PAC TC during its annual meeting.
2.2.2The Convenor of each WG/TF is responsible for establishing its terms of reference and work program to ensure that the task shall be carried out appropriately. The Convenor shall report the progress to the PAC TC during its annual meeting.
2.2.3The WG membership is open in principle. But to ensure smooth, foreseeable and effective operation of WG, each PAC member should write to the WG convener to formally nominate members of the WG. WG convener should formally approve or reject the nomination. If the nomination is rejected by the WG Convener, he or she shall provide sound reason for such rejection. WG members will be listed and visible to all PAC members. WG meeting conducted through web conference may only accessible to its members.
2.2.4All formal PAC technical documents shall be approved by the PAC TC, either during its annual meeting or by electronic means.
2.3The PAC TC may identify an appropriate person to report the development of relevant ISO/CASCO or other standards at its annual meeting to ensure that PAC TC members are aware of the latest standards development in relation to conformity assessment.
2.4PAC TC members wishing to submit technical papers for discussion have to provide the paper to the PAC TC Chair any time they wish. The PAC TC Chair is responsible for obtaining the view and seeking the consensus among the members by electronic means. The outcome of the discussion shall be recorded.
2.5Discussion papers for the PAC TC annual meeting have to be sent to PAC TC Chairat least 2 weeks prior to the PAC TC meeting. Papers that are submitted after this date may be accepted at the discretion of the PAC TC Chair.
2.5.1The format of the discussion papers shall be the same as that shown in Annex 1.
2.5.2Any PAC TC member who submits a discussion paper shall identify who will present the paper in the PAC TC meeting. The outcome of the discussion shall be recorded in the PAC TC meeting minutes.
2.6Normally, the PAC TC should have its meeting once a year, in conjunction with the PAC Plenary. The typical PAC TC meeting agenda is shown in Annex 2.
2.6.1Should a WG/TF wish to have its meeting in conjunction with the PAC TC,its Convenor shall inform the PAC TC Chair and PAC Secretariat at least 2 months prior to the PAC TC meeting. The information shall include meeting duration and the number of participants so that the Secretary and host member can make appropriate logistical arrangements.
2.6.2The WGs/TFs should normally develop a work-plan and are encouraged to actively maintain on-going progress against the work-plan between face to face meetings. The PAC TC Chair may instruct that a work-plan is required. Work-plans should normally be completed in collaboration with the participants and include responsibilities and milestones. . The WGs/TFs may request from the PAC TC to liaise with the PAC CMC to establish a special section of PAC website for remote discussion purpose. WGs/TFs conveners are also encouraged to use other on-line collaborative tools, like Go-to-meeting, to maintain an active work-plan.
2.6.3During the PAC TC meeting, the Chair shall encourage all members to participate actively in the discussions and ensure that all outcomes are based on consensus among the members. The Chair shall also ensure that the workload of the committee would be shared equally among the members.
2.6.4All PAC members are required to identify one or more representatives to take part in the PAC TC activities, preferably those who have technical background. The list of representatives to the PAC TC shall be updated each year in the PAC TC meeting. The PAC Secretariat shall keep the updated list.
2.6.5The outcomes of the annual TC Meeting shall be recorded in the Minutes to ensure that the PAC members have access to obtain information.The action items shall be identified in the PAC TC Workplan. The draft Minutes shall be distributed to the members for approval within 2 months of the meeting. The Chair is responsible to ensure that the identified activities in the latest Workplan are being progressed in a timely manner.
2.7The PAC TC may have technical co-operation with other bodies, (eg. other IAF regional bodies, APEC SRBs, CB associations), with the approval of the PAC Executive Committee, as deemed appropriate.
ANNEX1
For PAC TC meeting in XXXXX – DATE
PAC Discussion Paper
Name of party submitting issue for discussion (optional):Statement of the issue:
Discussion:
Requested action by the PAC TC:
Consensus of the PAC TC (also to be documented in the meeting summary):
ANNEX 2
Issue x.x / / Agenda Item 2PAC-TC-xxxx-xx
Page 1 of 2
PAC TECHNICAL COMMITTEE MEETING
DATE
LOCATION: <Insert venue name, and room number if known here>
TIME:08.30 – 17.30
DRAFT AGENDA
ITEMDOCUMENT NO.
1.WELCOME AND INTRODUCTION OF DELEGATES
1.1Apologies
2.CONFIRMATION OF DRAFT AGENDA
3.CONFIRMATION OF DRAFT RECORD OF LAST MEETING
3.1Confirmation of Minutes
3.2Matters Arising from 2009 meeting not covered in current Agenda
3.3Review of PAC TC Workplan
4.REPORTS FROM PAC REPS ON IAF TC ACTIVITIES
4.1IAF Standing Working Group
4.1.1xxxxx
4.1.2xxxxx
4.1.3xxxxx
4.2IAF Task Force/Project
4.2.1xxxxx
4.2.2xxxxx
4.2.3xxxxx
4.3New projects
4.3.1xxxxx
4.3.2xxxxx
4.3.3xxxxx
5.PAC TECHNICAL ISSUES
5.1Matters referred to previous PAC TC meeting
5.2Report from PAC WGs/TFs
5.2.1xxxxx
5.2.2xxxxx
5.2.3xxxxx
5.3PAC Discussion Papers / Questions for IAF consideration
6.REPORTS ON THE DEVELOPMENT OF RELEVANT ISO/CASCO COMMITTEES
7.OTHER BUSINESS
8.UPDATE OF PAC TC WORKPLAN
9.CLOSE
PAC-TECH-002_2.doc / Date of Issue: 27 October 2015 / Date of Application: ImmediateIssue 2.0 / PAC TC
Structure and Operation / PAC-TECH-002
ANNEX 3
Page 1 of 9
PAC-TECH-002.doc / Date of Issue: 27 October 2015 / Date of Application: Immediate