|
Home | Governance
Governance
This last section of the Toolbox describes how ongoing management and reporting can help ensure the WARP services are kept up to date with the WARP community needs and provides advice to ensure sustainability of the WARP. Policies are also described which will help a WARP maintain ongoing compliance with the WARP code of practice. An important tool to help in this management and compliance is to conduct an independent audit of your WARP, and the audit experience of the pilot WARPs has been included in this section.
Building trust over time will ensure the sustainability of the WARP as well as encourage sharing of incident data and a CPNI sponsored research paper is provided to help people understand some of the issues surrounding trust. This research will be applied in later versions of the Toolbox with the inclusion of ticklists and guidence on building trust.
Finally, it is important that this Toolbox is kept up to date with feedback from emerging WARPs. Your journey through this step by step guide to building and running a WARP concludes by asking for this feedback, not only by comments under Contact us but also by contributing directly to future issues of the Toolbox.
This section of the Toolbox includes the following:
-
Management and reporting
-
Policies
-
Audit
-
Toolbox development
1. Management and reporting
Regular management reports are vital to ensuring that the WARP is performing to expectations, and an important part of these reports includes the use of metrics and key performance indicators. The following examples are some indicators which other WARPs have found useful to monitor on a regular basis:
Scale:
-
Number of WARP members
-
Number of WARP filtered warnings registrations
-
Number of incident reports from WARP members
-
Number of best practices reported by WARP members
-
Number of one-to-one relationships (contacts made between WARP operator and WARP members)
-
Number of hits on WARP website
-
Number of Warnings/Advisories sent (generated by UNIRAS)
- Number of Warnings/Advisories sent (generated by WARP)
Quality:
Efficiency:
-
% WARP operator time spent on FWA
-
% WARP operator time spent on moderating discussions
-
% WARP operator time spent on managing incidents
-
% WARP operator time maintaining website
-
% WARP operator time managing contacts
Cost:
-
Cost of managing WARP services (hourly rate)
-
Cost of managing website (hourly rate)
-
Overhead costs (hourly rate plus general costs)
Back to top
2. Policies
The WARP code of practice within the WARP registration decribes how WARPs have a responsibility to conduct
their business in a responsible manner consistent with a set of values which
engenders trust. This section within WARP Governance describes Policies which will help a WARP meet these responsibilities.
WARP Guest Accounts
WARPs provide a range of services for a defined community, normally with restrictions on size to establish trust and facilitate information sharing. The WARP registration process requires providers to agree to the CPNI WARP code of practice, which states that they should encourage the creation of further WARPs.
One way of assisting this process is for an established WARP to create guest accounts for people who are not part of that WARPs community. This will allow the guest to sample the benefits of a WARP and thereby encourage them to create a WARP of their own. The introduction of a guest to a WARP community must be handled very carefully so the trust within that community is not compromised.
The following guidelines describe how a WARP should manage the concept of WARP guest accounts across all WARP services and should form the basis of a specific policy for their WARP.
  WARP guest accounts - policy guidelines (V1.0 June 2005)
Back to top
3. Audit
The IAAC (Information Assurance Advisory Council) were commissioned by CPNI to conduct an audit of some of the pilot WARPs to ensure that the learning opportunity was maximised. You can find out more about IAAC by visiting Useful links under reference sites.
A review of the implementation of the WARP concept in London Connects (LCWARP) and Kent Connects (SKWARP) over the period January 2002 to April 2004 is described in the IAAC audit report below.
IAAC WARP audit report (V1.0 April 2006)
Back to top
4. Toolbox development
As a reader of this Toolbox, it is hoped that you have now been successful in building and running your own WARP. To help other WARPs, we ask that you spend some time to reflect on your own learning experience and identify those aspects which you found difficult and the solutions you invoked to address these difficulties.
This Toolbox in itself needs to be self sustaining, so we invite you to make a direct contribution to this Toolbox, by writing a case study for inclusion in the Toolbox. Also, if you have developed templates or documents which can be included as examples or any reference material they would also be greatly received.
To help you in this process we include below a report which describes the rationale behind choosing the MS Word templates we have used in this Toolbox. If you are faced with designing your own MS Word templates, then this report may be of particular interest.
A generic template for WARP Toolbox documents (V1.0 April 2004)
To help you write Toolbox documents for submission to the CPNI WARP editor, the following MS Word templates are included below:
 Toolbox reference document template (V1.0 June 2004)
Toolbox example document template (V2.0 June 2004)
Toolbox example document template with front sheet (V2.0 June 2004)
When you have written your first draft, please send it to the WARP editor at:
Although the Governance page is the last step in the process of building a WARP, if you revisit this site you may find it helpful to go directly to the download section to find specific files. The first one contains all the downloads in the Setting up a WARP group of pages.
Back to top
|
