Exchange Network Policy Framework

From Exchange Network Wiki

Authority

In designing a Policy Framework for the Exchange Network, the ENLC recognized that ordinary governmental relationships and authority structure were not sufficient.  The ENLC cannot require any partner to use the Exchange Network.  There can be no penalty for misuse, other than to restrict access to shared services.

However, both the Environmental Council of the States and EPA formally endorsed the Exchange Network as the preferred way to exchange environmental information between states, tribes, territories, and EPA.  The ENLC also recognized that an appropriate language is needed to allow implementers to distiguish between "rules" and suggestions.  That means that even if no "penalty" can exist, Exchange Network partners in good standing will always comply with that which is required, and exercise a good faith effort to follow guidance.  Words like "Mandatory" and "Required" are used in policy, proceure, and standards documents to imply that something is considered important enough to warrant that language. 

Most important, Exchange Network policy is driven by practicality.  Foir the most part, exchanges or partners that ignore policy will not achieve the benefits afforded by the Network, and if the violation is significant, may not work at all. 

Framework Overview

The Policy Framework is based on the governence establising only that minim set of requirements that are necessary to achieve the objectives of the Network.  In all cases, the framwork allows for waivers of requirements that would be excessively onerous or might result in a failure to meet business objectives.  Policy 000 spells out how waivers may be obtained.  Broadly, the framwork consists of:

• Policy--these top-level documents may only be created by the ENLC, and establish foundational principles for the Exchagne Network.  Compliance with policy is mandatory.
• Procedures--these documents spell out what Network Implementers must do (e.g. how to create Scema).  Only the Network Operations Board (NOB) can adopt procedures.  Compliance is mandatory.
• Standards--These documents are similar to procedures, but tend to lack action directives.  The Node Specification and Protocol is a Network standard.  The NOB also adopts standards, except that Data Standards are a special case adopted only by the ENLC.  Compliance with Standards is mandatory 
• Guidance--these documents define best practices, lessons learned, and information that is of value, but not necessarily required.  Any of the governance bodies can create guidance.  Compliance is optional.