1. 1 Module: Enviance Glossary Speaking the Same Language

2. 2 Glossary System Model The Enviance System is customized for each (Your “Name” Here) customer to meet their specific needs. The System Model, as viewed via the software interface, reflects this customization. The System Model is the highest level of organization in the Enviance System and it represents the corporation or line of business.

3. 3 Glossary Tree Structure The Tree Structure is the cascading file structure (or hierarchy) within the Enviance System Model. It visually depicts the organization of the System Model; and, it also serves as a navigational device between the various levels of nested data.

4. 4 Glossary System Model Frame The left pane of the Enviance interface is the System Model Frame. It houses the System Model Tree Structure. From this frame you can navigate to one of four sections: Requirements, Citations, Documents, and Reports, or navigate through the System Tree.

5. 5 Glossary Navigation Frame The frame across the top of the Enviance interface is the navigation frame. It contains the main menu items plus links to the User Profile, Online Help and Logout links. The rights that a user is assigned determines the functions they can access here.

6. 6 Glossary Profile / User Guide Your System Administrator creates your profile when. they add you as a new user, but select Profile here to update your profile and change your password. The User Guide is a robust and simple-to-use reference guide to help you use the System. You must log out to ensure security and end your session.

7. 7 Glossary Content Frame The right pane of the Enviance interface. This is the area where most of your interactions take place such as viewing tasks and entering, updating or viewing data.

8. 8 Glossary Objects Every item defined under Requirements in your System Model is considered an object. (i.e., Facilities, Units, POIs, and Requirements.) Object Path The path indicating where an object is located in the System Model. i.e.,

9. 9 Glossary Facilities Level 1: Facilities are the first-level objects in the system model hierarchy. A Facility is a parent* to all other system model objects. A Facility may represent an actual physical facility (i.e., plant, equipment), a regulatory program (i.e., air quality requirements or Title V permits), or a project. Remember that a Facility DOES NOT have to refer to a physical building or plant; a Facility is simply the first level of organization within your System Model. *ParentThe level above an object in the System Model. A Facility is a parent to all objects in a system model.

10. 10 Glossary Units Level 2: Units are divisions - or children* - of a Facility.They may represent parts of a plant or regulatory program areas. Much like a Facility is the first level of organization within your System Mode, a Unit is your second. A Unit is basically a folder under which you can logically group objects you need to track. *Children The levels below an Object in the System Model. A Unit object is a child of a Facility object.

11. 11 Glossary Points of Interest Level 3: The third layer of organization within your System Model is a Point of Interest (POI) It is a child within a Unit or a Facility. A POI is basically a folder under which you can logically group objects you need to track.

12. 12 Glossary requirements Level 4: Compliance objects set up in the system to allow monitoring and tracking of compliance obligations. They may pertain to an entire Facility, to a specific Unit, or to a Point of Interest. The system allows three broad categories of compliance requirements: 1) Non-numeric requirements 2) Calculated requirements 3) Parameter (numeric) requirements

13. 13 Glossary Parameters Parameters are numeric requirements set up to record data. The data can be directly entered or electronically imported into the database. The parameter - also called a variable - may be: a pollutant (e.g., total suspended solids, ammonia), an operational measurement (e.g., flow, temperature), or, any other numeric requirement for which data must be directly entered (as opposed to being calculated by the system).

14. 14 Glossary System Variable A System Variable is a type of numeric requirement used to define a parameter, set a constant value, and use its value in one or multiple calculations. System Variables are typically used to store emission factors, properties of equipment, properties of materials, and localized data that is constant throughout the location. System Variables seldom need to be edited, but when the value changes, the value is applied throughout the System based upon the “begin” and “end” dates. System Variables are often set up for reference purposes.

15. 15 Glossary Calculated Calculated Requirements can be defined using arithmetic, algebraic, and statistical functions. Calculations can be set for rolling periods or fixed periods. Calculations are defined through an expression builder similar to the calculator on a standard personal computer. Numeric parameters, variables and previously defined calculated parameters are available to include in the calculation definition.

16. 16 Glossary Event Log Event Logs are used to monitor one or more notebook requirements for periods of time in which they are potentially out of compliance or when further documentation is needed for reporting purposes. The primary use of Event Logs is to store information about deviations. A secondary use is to store non-deviation information about one or more requirements for specific periods, such as records of safety incidents. There are two types of Event Logs: 1) Automatic 2) Manual

17. 17 Glossary Event Instance An Event Instance captures or records detailed information about a non-compliance issue. However, an Event Instance can also be used as a check list or form that is completed on a recurring basis. There are two types of Event Instances: Automatic: An automatic event instance is created by the Enviance system when a limit has been exceeded or data is non-compliant. Manual: A manual event instance is created when the user enters information directly into the event log.

18. 18 Glossary Task A Task is simply a compliance activity; it is the lowest object in your System Model. A Task answers the questions Who, What, Where, and How Often, and the underlying requirement provides the answer Why.

19. 19 Glossary Notification A communication associated with a task that notifies the assignee(s), assignor, or any other interested parties when the status of the task changes. Task Notifications may be edited at any time to add or delete notifications or change the criteria or recipient of a notification.

20. 20 Event objects store data related to incidents or periods of time when a requirement is not determined to be in compliance.

21. 21 Glossary Question In which frame will you view tasks & enter data? System FrameNavigation FrameContent Frame

22. 22 Glossary Question What is the first level object in the system model hierarchy, and a parent to all other system model objects?

23. 23 Glossary Question Facility What is the first level object in the system model hierarchy, and a parent to all other system model objects? What are divisions called within a facility? They may represent parts of a plant or regulatory program areas.

24. 24 Glossary Question Facility What is the first level object in the system model hierarchy, and a parent to all other system model objects? Unit What are divisions called within a facility? They may represent parts of a plant or regulatory program areas. What is the third level of organization within your System Model?

25. 25 Glossary Question Facility What is the first level object in the system model hierarchy, and a parent to all other system model objects? Unit What are divisions called within a facility? They may represent parts of a plant or regulatory program areas. Point of InterestWhat is the third level of organization within your System Model?

26. 26 Glossary Question The lowest object in your System Model will be? A Task An Event A Point of Interest A Requirement

27. 27 Glossary Question The lowest object in your System Model will be? A Task An Event A Point of Interest A Requirement

28. 28 Glossary Question The three broad categories of compliance requirements are:

29. 29 Glossary Question The three broad categories of compliance requirements are: 1) Non-numeric requirements 2) Calculated requirements 3) Parameter (numeric) requirements

30. 30 For More Information Contact: Enviance Customer Service (760) 496-0200 www.enviance.com