1 Welcome

Regulatory Database Management SystemBy PDC Corp.

Introduction and Features Overview

IntelliRegs

Including “Hands-On” Training Sessions

2 IntelliRegs: Regulatory Database System

B. Security, and Administration C. Permit-Reg Operations D. RegText/Task Definition Operations E. Unified Operations F. Management of Change (MOC) G. Update TaskTrakker from IntelliRegs H. Integrated Deviations Reporting

I. “Hands-On” PDCDemo Training Session J. “Hands-On” Company/Facility IntelliRegs

A. Introduction to IntelliRegs

3 About A through H Training

• Follow Training Outline: Subject & Proficiency • See User Manual for additional information

A through H review presentations

• Questions welcome in instructor-lead sessions

• For meeting presentation or self-review

• Pace of instructor-lead session based on:

• Users’ IntelliRegs Experience

• Training schedule allocated time

• Questions and Answers addressed• Instructor discretion and judgement

4 Follow Training Worksheet XLS File

Features/Operations IntelliRegs Program Area User Manual Data Entry

Program Functional Operation Item/SubItem Section# Gen Nav Add Edit Del Proc RptsA Introduction/Overview of IntelliRegs

1 Overview of IntelliRegs Operations and Structure O O2 User Manuals, Documentation, Support, Training Assistance O3 TEXAS and BASE IntelliRegs version differences O O4 System requirements, files, installation, & updates O O O5 Initialization and edits based on source files/documents O

Features Outline Worksheet

Subjects for Training and Review

Reference to User Manual Additional Info/Instructions

Operations Review/Training Checklist

and Proficiency

The IntelliRegs Training Worksheet shows program areas, operations, and provides for user proficiency scoring by subject.

MSExcel and/or Printed Worksheets provided by PDC to Students.

5 About I and J “Hands On” Training

• System on local test PC from PDC-provided files • Each student with own system for the training

• I: Uses PDCDemo database

• J: Uses copy of Company/Facility database

• Scripted “suggested” case-study exercises.

• Operations suggested by instructor or students

6 A1: Overview: IntelliRegs Business Objectives

• Permit and Regulations Data Repository• Any permit/regulation mapped into IntelliRegs system• Current and prior-version archived permit data• Effectively reflect permit affected changes• TEXAS: Title V Permit forms and reporting formats

• Implement for Compliance Management

• Citation RegText with version-control processing• Data for explicit and implicit regulatory requirements

• Generic TaskDefinitions “plain English” for compliance • Complementing Management Fields: OpDUP, Status• Maintain Equipment Inventory with status and history• Effective Management of Change for Compliance Data• Exports for TaskTrakker Compliance Updates/Adds

7 A1: Overview: Operations HierarchySecurity & Administration

Area OpDUP OpSys

Connect/Login

Facility

Session LogAdmin Ops

Direct Applic

Equipment

RegAgencyCode

Citation Text

Task Definition(s)

Tasks Export

Posted Applicable RequirementsPAR

PAR QA

Applicability Export

TaskTrakker

Add / UpdateState Operations

State Applicability

8 A1: Overview: Operations Flow Chart

Please refer to the printed version of theProgram Operations Flow Diagram provided by PDC

Security & Admin

Update TaskTrakker

Permit-RegOps

State Special Ops

Unified-Ops

RegText & TaskDefs Ops

9 A1: Overview: Sources and Data

IntelliRegs Facility Database

Data Import or Data Entry from Permit and Regulations files or documents

CMP Loading XLS files PDC Format

Client-form XLS or ASCII files

Computer files (various format)

of permit or regulations

Printed Hardcopy Equipment info, Permit or Regs

Data for IntelliRegs from a variety of format sources

By PDCBy PDC

Citation/Regulation Text & Tasks from RMOC Master Database

IntelliRegs RMOC Add/Update

10 A1: Overview : Any Permit into IntelliRegs

Permit or Regulation Breakdown

General & Special

Conditions

Requirements Text or Tables Referenced

Requirements

Permit RepresentationMethodology

Equipment ID Conventions

RegAgency IDs

Citation Numbering Convention

FacilityID, Area, OpDUP Decisions

IntelliRegs

Title V

NSR

PBRRCRA

WWT

Regulations and Permits various types and format

11 A1: Overview: Any Permit into IntelliRegs

Permit or Regulation

General & Special

Conditions

Requirements Text or Tables

Permit Representation

Referenced Requirements

Methodology

Equipment ID Conventions

RegAgency IDs

Citation Numbering Convention

FacilityID, Area, OpDUP Decisions

Facility Equipment

IntelliRegs Data Elements

Citation RegText “FullText”

Direct Applicable

RequirementsRegAgency Chapter

PermitArea(s)

Facility

OpDUP (BusDept)

Task Definitions

For the Permit

12 A1: Overview: TCEQ Title V Permit

Facility Equipment

IntelliRegs TCEQ Title V Base Data

OpUA Data

OpUA Applicable

Requirements

Title V Application or

Revision

Title V Permit

OpREQ1General & Special

Conditions

OpSUM

OpUA

OpReq2 Neg.Applicability

OpReq3 Applicability

OpMON

Unit Summary

NSR Authorization

OpUA Data Not in TV Permit

Permit Shield

Applicable Requirements

Periodic Monitoring

Facility Equipment

OpUA Data

IntelliRegs Reconcile/Matched

Negative Applicable

Requirements

OpUA Applicable

Requirements

Negative Applicable

Requirements

Citation RegTextDirect Applicable

IR DataSet

13 A2: User Manuals, Support, Training

Users Manual PDF for online or printed reference

Latest version PDF from PDC or by PdcCorp.com download.

Telephone and EMail support by PDC experienced technical staff.

Onsite or phone-based training available

(TEXAS and NonTexas versions)

14 A3: TEXAS and Base Versions

Selection of TEXAS or NonTexas directs IntelliRegs to offer different screen and options.

Version 7b 2006 and later!

15 A3: TEXAS and NonTexas Operations

Menu selections different for TEXAS and NonTexas form preference operations.

Note! Texas-only menu items

(not in NonTexas) menu list

16

IT_Master_<Date>.mdbMaster Regs Database

Forms, Formulas, Reg#WizBase.mdb

Facility DatabaseIR_<Company>.mdb

Deviations ProgramDev_**.mde

IntelliRegs ProgramIR_**.mde

A4: Requirements and System Files

Requires MSAccess 97,2000, 2002/3

Company/facility IntelliRegs database MDB

Read-Only Knowledge-Base files from PDC

Compiled “Frontend” program MDE files from PDC.

17 A4: Installation and Updates

• Initial Installation:• Form CD Provided by PDC• All files with instructions provided• Security Codes provided to Administrator

• Updates:• By Email or PDC Website download • Program: On Version/Revision new .mde file• Wizbase: On any form, formula, citation list change• RMOC Master: Quarterly plus interim if required• Facility Database: Stay at facility except for special by PDC

18 B: Security and Administration

Logon, Security, and Administration operations depicted in the flow diagram by the Security and Administration block and designated operations.

19 B1. Startup, Connect, Backup, LogonStartup logon screen

Connect button goes to DB Connect screen* Also to backup option

Enter and then Submit to begin program operations

Passwords provided by PDC to IntelliRegs Administrator

20 B2: MenuBar and Forms OperationsMenuBar and Forms Operations and Navigation

Operations selected from MenuBar.

Program managed data entry screens

Standard Windows Navigation and Ops

21 B3. Security, Session Log, Admin Operations

Administrator Ops: Sessions Log and System KeyValues

(Sessions Log shown)

22 C. Permit-RegOps

Depicted in the IntelliRegs Operations Flow Diagram by the Permit-RegOps block. Optional STATE=Texas shown in the above diagram

23 C1: Permit-RegOps Reports

Reports menu selection to.. Reports select and run screen

Report operations at tabs similar:Designate/select filter (or No Filter=All)Check report(s) then Select RUN button

TEXAS tabs!

Reports available at multiple tabs

24 C2: Facility, Area, OpDUP, OpSYS

Facility, Areas, OpDUP.. select...

Data Entry Form:Add, Edit, Deletes

Facility Data

Areas tab andOpDUP tab

OpSys tab

Data entry

25 C3: Facility Equipment: Select and Filters

Equipment: Select.....

to Optional Filters Form

All Records= No Filter

.. or select filter(s)..

then open form

26 C3: Facility Equipment: Add, Edit Screen

EquipID key data entry tab

OpStatus tab with History

Multiple Equipment form data tabsOpUA Forms & TVNegDirect=TEXAS Only

Enter Equipment values at all appropriate tabs

27 C3A: TEXAS: Special Equipment TabOps

TEXAS Tabs:

OpUA FormsTV NegApplic DirectTV Unit Summary

Not on NonTexas

TEXAS TabsTV NegApplic Direct shown

28 C3B: TEXAS OpUA Forms, Attributes

For Equipment/Unit select OpUA form to Add or Edit... then Open Form

29 C3B: TEXAS Permit-Reg Operations

OpUA Forms, Attributes, RRT, Applicability

Some of the Texas Forms for OpUA Data Entry

Equipment Type

Miscellaneous Units

Reciprocating Engines

Storage Vessels

Loading/Unloading

Process Heater/Furnace

Boiler/Steam Generator

Flares

Fugitive Emissions

Cooling Tower/Industrial

Emission Point, Vent

Distillation Units

OpUA Form (Tables)

UA 1 (1)

UA 2 (1)

UA 3 (6)

UA 4 (5)

UA 5 (2)

UA 6 (8)

UA 7 (4)

UA 12 (7)

UA 13 (1)

UA 15 (3)

UA 17 (1)

30 C3B: TEXAS OpUA RRT-Applicability

Entered OpUA Attribute Values

RRT Flow and Citations

RRT Logic Determines Applicable Citations

31 C3B: TEXAS RRT Logic Diagrams

OpUA Forms, Attributes, RRT, Applicability

40 CFR 60 Subpart Da-Flowchart

TCEQ

Operating Permits

RRT Decisions (Yes or No)

No

No

No

No

Numbered 01,02.....

Yes

Yes

Yes

Yes

Compliance Blocks (Containing Citations)

Numbered C01,C02.....

End

RRT FlowchartPDF file from TCEQ Website

01

02

03

04

C01

C02

Start

32 C3B: TEXAS OpUA RRT Coding

OpUA Forms, Attributes, RRT, Applicability

TCEQ RRT Decision Logic As Captured in Regulatory Wizard Knowledge Base

RRT Decisions As In RRT Diamonds

Yes-No Flow LogicAs In RRT Flowchart

Example Flow: 1Y>2Y>3N>4Y>(C01)>End

33 C3B: TEXAS RRT Comply-With Table

OpUA Forms, Attributes, RRT, Applicability

Citation and Requirement Type

As In RRT Flowchart

34 C3B: TEXAS Permit-Reg Operations

OpUA Forms, Attributes, RRT, Applicability

UA Applicable

Special Regs

RRT-Determined Citations

Comparison of OpUA RRT-Determined VS OpUA Applicable

ST 60.112b(a)(3) ST 60.112b(a)(3)

RK 60.115b

RK 60.115b(c)

RK 60.116b(a)-(b)

RK 60.115b

RK 60.116b(a)-(b)

RK 60.115b(c)(1) Add

IntelliRegs Expert processing of WizBase OpUA FormData Values

and RRT Rule-Based Logic Processing

As entered and approved as the UA Applicable Regs = Special Regs

IntelliRegs COMPARE Report

Example RRT Citations Example Comparison Example UA Applicability

Match Add Delete

3 1 1

1

1

1 1

1

35 C3B: TEXAS OpUA SpecRegs=UA Applicable

In prior versions of IntelliRegs, the "Net-Applicability" was RRT-Determined + Special Requirements.

Now, (in Version 7), the Special Requirements represent the UA Applicable requirements not influenced by RRT-determined applicability. See report examples for better understanding.

Key Reports and DataSheets for Analysis and Comparison

36 C3B: TEXAS Special Regs = OpREQ3

OpUA Special Regs print in OpREQ3 format from DataSet OpREQ3 data.

37 C3C: TEXAS OpUA Pattern OpsOpUA Patterns: Master-Member and Replication

The “Master” and member equipment items for an OpUA UA Profile are added or revised from the UA Profiles Masters and Details Data Entry screen.

Note: Initially members may be added with UA FDIDNo=0. On member replicate/refresh a new OpUA data row will be created!

Member OpUA attribute values and Applicable/Negative Applicable RRT & Special Reg citations are made identical to the Master’s in the replication/refresh run.

Use of UA Profiles may improve Title V maintenance efficiency greatly............. i.e. 5 to 1, 8 to 1

38 C3D: TEXAS: DataSets

Select TCEQ DataSet OpsOpens DataSet Ops Screen

To Create a new Archive dataset or refresh an existing dataset

Archive dataset Reports includes TCEQ OpSUM, OpReq2, OpReq3 format print or EFiles

Create or Report on a COMPARE type DataSet

Archive DataSets are extracts from IntelliRegs current tables into TCEQ format data tables.

39 C3D: TEXAS: DataSets Create

40 C3E: TEXAS: Archive DataSet Reports

Select ARCHIVE DataSet then..Select and Run Reportsor Select and Run EFiles

41 C3F: TEXAS: DataSets COMPARECreate by comparing two Archive datasets.

Run COMPARE see comparison counts.

42 C3F: TEXAS: COMPARE DataSet Reports

Select COMPARE DataSet then..Select and Run Reports

43 C4: Facility Equipment: Direct Applicability

Enter Unit-Citation Applicability at the Direct Applicability tab’s data entry form.

44 C5: Permit-RegOps Utilities

Select and run Permit-RegOps Utility operations when needed.

TEXAS utility screen shownNonTexas utility with different items

TCEQ Forms Management of Change (FMOC) for OpUA Forms

45 D: RegText/TaskDef Operations

Regulation Text and TaskDefinition create, manage, export operations

Depicted in the IntelliRegs Operations Flow Diagram by the TaskDefs-Ops block.

46 D1: RegText/TaskDef Reports

Reports menu selection to.. Reports select and run screen

Report operations at tabs similar:Designate/select filter (or No Filter=All)Check report(s) then Select RUN button

Reports available at multiple tabs

47 D1: RegText/TaskDef Ops Main Screen

TaskDefs MainOps select to.. Main Compliance Task Ops Screen

48 D2A: Citation RegAgency Chapter

RegAgency Chapters with PreFixCodes added to enable unique numbering for any Citation into enterprise, multi-state, databases.

Note no PreFixCode for 40CFR and 30TAC base codes. (By Default)

49 D2A: Citation FullText: PDC/RMOC Regs

Citation FullText Data Entry...

RMOC Version Control Data Revised only by RMOC Update

111.111(a)(4)(A) 12/15/1987 Added Method 9 as acceptable observation method

Citation History for Citation Appears here (if any history)

Key fields locked= not user editablePDC RegMOC Maintained

50 D2B: User-Maintain RegText Ops

Citation FullText Data Entry...

RMOC Version Control Data Revised by MOC Update

Citation History for Citation Appears here (if any history) Same as in RMOC Master

Editable (Unless Tasks Exported)User-Maintained (Not 40CFR/30TAC)

51 D3: Historical Citations

Historical Citations

or User-Maintained MOC CreatedPDC RegMOC Created in Updates

52 D4: Create TaskDefinitions: SmartParse

Run SmartParse Processing

Creates TaskDefinitions from RegText

53 D5: TaskDefinitions Editing

Task attribute values entered at multiple tab entry screens.

EditStatus 2,3,4,5,6 TaskStatus See legend. 6=Ready for Export

54 D6: Advanced TaskDef Operations

Advanced filter selection of TaskDefinitions for editing, SQL Update or Reporting.

55 D7: Tasks Export to TaskTrakker

56 E: Unified Operations

Unified: From Permit/Applicability and Reg/TaskDefs

Depicted in the IntelliRegs Operations Flow Diagram by the Unified-Ops block.

1. Merge Direct and State-Special Applicability 2. Perform [G] subcitation expansions (if any) 3. Represents “Approved” not “InWork” applicability 4. Data basis for Applicability TaskTrakker Export

57 E1: PAR=Posted Applicable Requirements

Multiple Tab Operations: (Applicability Updates tab shown)

Number of PAR Records

58 E1: PAR: QA Applicable Regs

Objective QACounts=0

59 E1: PAR: AMOC Operations

Pending Differences

Applicability HistoryReports and DataSheets

Active Applicable vs Current PAR

Update Applicability HistoryFrom Current PAR

60 E1: PAR: Applicability Reports

Applicability ReportsPer Filter and Sort Selections

61 E1A: PAR Export Applicability to TaskTrakker

Creates a file to be imported for Adds or Updates by TaskTrakker

See TaskTrakker instructions on import and update procedures

62 F: Management of Change (MOC) Types

• EMOC= Equipment MOC

• FMOC= Forms MOC

• RMOC= Regulatory MOC– Subscriber 40CFR/30TAC via ITMaster DB– User-Maintain using IntelliRegs MOC ops

• AMOC= Applicability MOC

63 F1: EMOC Equipment Change

EMOC = Equipment and Operations Management of Change

Changes in Equipment/Operations are reflected into the database with the add, delete, or edit of Facility-Equipment or the revision of Equipment-attributes.

Title V Permit change impacts:

* Units identified for the Title V Permit may be added, removed, or revised based on Equipment/Operations changes.

* Permit Shield and/or Applicability added, deleted, or revised base on Equipment/Operations changes.

Compliance Activity change impacts:

* Changes in TVUnitID(Rename) or OpDUPID (Department) or a change in OPStatus (Active,Idle,Shutdown) are processed as Applicability changes. (See AMOC)

64 F2: FMOC = Forms Management of ChangeChanges in Title V Permit forms and formulas require prior version forms data to be revised to match the new form. Revised decision formulas must be used in place of older formulas. IntelliRegs provides for the migration of data from old form to new and the reprocessing of decisions based on revised decision formulas.

 

TCEQ Forms and Formulas Change Management:

Latest version OpSUM, OpUA, OpREQ2, and OpREQ3 forms and RRT(Regulatory Rule Table) formulas are in the IntelliRegs program. Prior version data archived in TCEQ DataSets preserves history.

 

OpUA form updates are made using the Utilities-OpUA form updates operation. This "maps" prior values to new OpUA form fields operations and map all prior values the new form or formula. Revised, latest version RRT applicability is determined based on the formulas in the WizBase database.

65 F3: RMOC Regulatory Management of Change

When a regulation changes the resulting revisions to referenced regulation text, Unit+Regulation applicability, and/or Compliance Task activity need to reflect those changes immediately.

These changes then are forwarded into your TaskTrakker Compliance Management system by creating the export file(s).

It is also important to retain prior version and date-of-change data in the Historical Citations table so that compliance history maps to the regulation in force at the time.

66 F3A: RMOC 40CFR/30TAC Subscription

IntelliRegs provides an optional RMOC Subscription service that maintains latest version regulation data for US 40CFR and TX 30TAC.

Subscribers to the RMOC Subscription service receive an updated Master Regulations database at least once per quarter. IntelliRegs connects to this Master Regulations database and enables UPDATE and ADD-NEW operations. The UPDATE operation either confirms that the existing Citation is the latest version or archives prior version to the Citation History table and updates to the lastest, current version.

67 F3A: RMOC Subscription Operations

Run RMOC Version Updates then run RMOC Import(AddNew)

Review performed Updates and Adds in Session Log Reports

Optional: Review data in the RMOC Master Database before importing it.

68 F3B: Management of Change(MOC)

RMOC for USER-MAINTAIN Citations

Permits and Regulations not in US 40CFR and TX30TAC are RMOC managed using IntelliRegs program functions referred to as "User-Maintain" regulations.

Enter the MOC password (at the TaskDefs Summary tab) then ....

At the REG MOC Analysis screen.....

Select the old citation then (at the Management of Change Tab) enter the new text, new number, and change comment then select to ACCEPT CHANGE. Old data will be stored into the Citation History table and the new, latest data will become the current Regulation data.

See next screen for the REG MOC Analysis form.

69 F3B: RMOC for User-Maintained Citations

User-Maintain Reg MOC Analysis and change processing available only on MOC password

UPDATE:Archives old to Historical CitationsMakes New=Current with TaskDefs

70 F4: Management of Change(MOC)

AMOC = Applicability Management of Change

A change in Unit-Citation applicability add new tasks , remove tasks, or activate or reassign compliance activities. The change in applicability may also be a Title V Permit change if the reported Unit Regulatory Applicability is revised.

IntelliRegs provides for recording/storing applicability into the Unit-Applicable table which establishes the StartDate and EndDate of applicability based on a 9-Key value in the Applicability Management of Change (AMOC) operations. Any change in the key fields value is processed as an applicability change recorded as an EndDate for the old applicability and StartDate for any 9-Key applicable value not in force.

Analysis and reports for AMOC are available in IntelliRegs. When a regulation changes the resulting revisions to referenced regulation text, Unit+Regulation applicability, and/or Compliance Task activity need to reflect those changes immediately.

 

71 F4: AMOC=Applicability Mgmt of Change

72 F4: AMOC Instructions/Information

73 G: Updating TaskTrakker from IntelliRegs

• Export Applicability from Posted Applicable Requirements

• Export changes Task Definitions or Export all Task Definitions

74 G1: Create IntelliRegs Export/Exchange Files

• Export only changed data ... – or Export all data

• Export Applicability: IR/TT Contract.. – Equipment all applicability (never partial)

• TaskDefs: Export changes since last ... – or Export all TaskDefs

75 G1A: Export Applicability Log Data

Exports recorded in Log with changes documentation

76 G1A: Export TaskDefinitions Log Data

Exports recorded in Log with changes documentation

77 G2: Updating TaskTrakker from IntelliRegsTaskTrakker Updates Processing: Applicability & TaskDefs

• Import Applicability File

• Import Task Definitions File

• Generate/Update Tasks– Option 1: Global Changes Screen

• Bulk Add/Update of Sitewide/Unit/Equip Tasks

– Option 2: Update Tasks Screen• Add/Update Of Individual Tasks

78 G2: Update TaskTrakker: Import Files

Import IntelliRegs Applicability and Task Files

79 G2: Update TaskTrakker: Global ChangesGlobal Task Changes (Auto Generate Screen)

80 G2: Update TaskTrakker: Update Tasks

81 G2: Update TaskTrakker: Update Tasks

82 H: Deviations ProgramDeviations Program Objectives:

1. Provide for preparation and submittal of TCEQ Deviations Reports

2. Provide integration with IntelliRegs permits and compliance implementation data to ensure agreed-on UnitID+Citation associations.

3. Provide for import and workflow management from external datafiles and from TaskTrakker Deviations data.

4. Provide for management reports and graphical analysis

83 H1: Deviations: Integrated Program Ops

IT_Master_<Date>.mdbMaster Regs Database

Forms, Formulas, Reg#WizBase.mdb

Facility DatabaseIR_<Company>.mdb

Deviations ProgramDev_**.mde

IntelliRegs ProgramIR_**.mde

The Deviations Program shares the IR<Facility> and IT_Master databases with IntelliRegs.

84 H2: Deviations: Main Screen

Shared data elements status

85 H2: Deviations: Event Data Entry

This Operating Permit Requirement has 5 Deviation Events

Unit, Citation, and Unit-Citation-Applicability are in IntelliRegs Facility database

86 H3: Deviations: Print and Submit Report

Output from Program is accepted by TCEQ for Deviation Report submittal.

87 I. “Hands-On” PDC Demo Training Follow instructor screen operations during demo work session

Phase 1: Facility, Equipment, and Export Applicability

Phase 2: RegText, Tasks, and Export TaskDefs

A. Add new FacilityID, Area, OpDUP, OpSysB. Add new Facility Equipment C. Add Equipment Direct Applicability D. Update PAR for new ApplicabilityE. Export Applicability for TaskTrakker

A. Add new Citation FullText: RMOC ImportB. Create, Edit, Approve Task DefinitionsC. Export Task Definitions for TaskTrakker

88 I. “Hands-On” PDC Demo Training Follow instructor screen operations during demo work session

Phase 3: MOC operations: EMOC, AMOC

Phase 4: RegText, Tasks, and Export TaskDefs

A. Add/Change Equipment Direct Applicability B. Update PAR for new ApplicabilityC. Export Applicability for TaskTrakker

A. Revise a prior exported Task DefinitionB. Export changed TaskDefs for TaskTrakker

Phase 5: MOC “What if” case examplesA. Student suggested or followups

89 J. “Hands-On” Company/Facility IntelliRegsA copy of the Company/Facility IntelliRegs database will be put into the training directory for student review.

Facility IntelliRegs Database Review and OperationsA. Facilities, Areas, OpDUPs, OpSYS, Permits B. Facility Equipment

• OpStatus Review• TEXAS OpUA and UA Applicability Review

• TEXAS DataSets ReviewC. PAR Review: QA CountsD. RegText and TaskDefinitions CountsE. Advanced TaskDefs Review ES<6F. Export Logs review and Exports StatusG. Questions, Answers, Exported additional opsH. Status and Suggested-Next-Action discussions

90 Contact PDC for Additional Information

This concludes the Introduction to IntelliRegs

Presentation

Contact PDC for additional informationOr visit www.pdccorp.com

For latest available documentation and downloads

Contact PDC for Advanced IntelliRegs Training