7.1.1 User clicks Cancel on the Confirm Create State Agency or EPA Region screen. 7.1.2 System displays the Create State Agency or EPA Region screen with selections and entries still populated. N/A 7.1.3 Use case terminates. N/A NetDMR allows System Administrators and Internal Administrators to view instance settings. A list of Instance Settings is provided in the table below with who can see what. Table : View Instance Settings Settings System Admins Internal Admins General Information Agency or EPA Region Name X X Time Zone X X Allow multiple signatory requests in a subscriber agreement? X X Are Permit Administrators required to have signatory for their permit? X X State Agency or EPA Region Status X X Submittal Postal Code X X Contact Name X X Contact X X Contact Phone X X DMR Information for User Download NAAS ID X
addresses are sent submission acknowledgements anytime a DMR is submitted for this State Agency or EPA Region X Failed DMR Submission Notifications Email addresses are sent a notification anytime a DMR submission fails X Custom News and Notices News/Notice items are displayed on the NetDMR Welcome Page X Use Case Assumptions: None. Preconditions: None. IMG02 – View Instance Settings Step User Input Step System Response Mapping to Business Rule Table Flow: 1* User logs in to NetDMR as a System Administrator N/A 2 User clicks a hyperlinked State Agency or EPA Region Name to view instance details. 3 System displays the State Agency or EPA Region Details screen for the selected instance. Row 48 4 Use case terminates. N/A Alternate Flows: 1.1 User Logs in to NetDMR as an Internal Administrator 1.1.1 User clicks State Agency or EPA Region under the Manage menu. 1.1.2 System displays the Manage State Agency or EPA Region screen. Row 49 1.1.3 Use case terminates. N/A
8 System displays the Confirm Update State Agency or EPA Region Downtime screen. N/A 9* User clicks Save. 10 System stores the modified instance downtime data in the database. N/A 11 System displays the Agency or EPA Region Downtime Schedule page with a message indicating the scheduled downtime has been created. N/A 12 Use case terminates. N/A Alternative Flow(s): 6.1 User Cancels Update State Agency or EPA Region Downtime 6.1.1 User clicks Cancel on the Update State Agency or EPA Region Downtime screen. 6.1.2 System discards any selections and entries and displays the State Agency or EPA Region Downtime Schedule screen. N/A 6.1.3 Use case terminates. N/A 9.1 User Cancels Confirmation 9.1.1 User clicks Cancel on the Confirm Update State Agency or EPA Region Downtime screen. 9.1.2 System displays the Update State Agency or EPA Region Downtime screen with selections and entries still populated. N/A 9.1.3 Use case terminates. N/A NetDMR allows for a scheduled Instance Downtime to be deleted by a System Administrator. Use Case Assumptions: None. Preconditions: User has the System Administrator role and has successfully logged in to NetDMR. IMG08 – Delete Scheduled Instance Downtime Step User Input Step System Response Mapping to Business Rule Table
Flow: 1 User clicks the State Agency or EPA Region Downtime link under the Manage menu. 2 System displays the State Agency or EPA Region Downtime Schedule screen. N/A 3 User clicks the Delete icon in the row of interest. 4 System displays a pop up window requesting confirmation to delete the scheduled instance downtime. N/A 5* User clicks OK. 6 System displays the Confirm Delete State Agency or EPA Region Downtime screen. N/A 7* User clicks Delete. 8 System validates the data according to the business rules. Row 63 8.1 If the data are invalid, the System displays an error message Use case continues at Step 7 Else Use case continues at Step 9 N/A 9 System inactivates the selected scheduled instance downtime in the database. N/A 10 System displays the State Agency or EPA Region Downtime Schedule screen with a confirmation message. N/A 11 Use case terminates. N/A Alternative Flow(s): 5.1 User Cancels Delete Agency or EPA Region Downtime 5.1.1 User clicks Cancel on the confirmation delete pop up window. 5.1.2 System redisplays the State Agency or EPA Region Downtime Schedule screen. N/A 5.1.3 Use case terminates. N/A 7.1 User Cancels Confirmation 7.1.1 User clicks Cancel on the Confirm Delete State Agency or EPA Region Downtime screen. 7.1.2 System displays the State Agency or EPA Region Downtime Schedule screen with downtime still populated. N/A 7.1.3 Use case terminates. N/A
NetDMR allows the NetDMR scheduled jobs data flows to CDX to be temporarily disabled through the Schedule Data Flow Downtime function. Only System Administrators can perform this function. The scheduled jobs that are disabled are: DMR Submission, BPDF/ESDF Solicit, and Status. Effectively disabling these scheduled jobs will ensure the data flows between NetDMR and CDX are disabled. Use Case Assumptions: None. Preconditions: User has the System Administrator role and has successfully logged in to NetDMR. IMG09 – Schedule Data Flow Downtime Step User Input Step System Response Mapping to Business Rule Table Basic Flow: 1 User clicks the Data Flow Downtime link under the Manage menu. 2 System displays the Data Flow Downtime Schedule screen. Row 71 3 User clicks Schedule Another Downtime. 4 System displays the Schedule Data Flow Downtime screen. N/A 5* User selections and enters data. N/A 6 User clicks Save. 7 System validates the data according to the business rules. Rows 64 - 70 7.1 If the data are invalid, the System displays an error message Use case continues at Step 5 for data correction Else Use case continues at Step 8 N/A 8 System displays the Schedule Data Flow Downtime Confirm screen. N/A 9* User clicks Save. 10 System stores the new data flow downtime data in the database. N/A 11 System displays the Data Flow Downtime Schedule screen with a message indicating the scheduled downtime has been created. N/A 12 Use case terminates. N/A
Alternative Flow(s): 5.1 User Cancels Schedule Data Flow Downtime 5.1.1 User clicks Cancel on the Schedule Data Flow Downtime screen. 5.1.2 System discards any selections and entries and displays the Data Flow Downtime Schedule screen. N/A 5.1.3 Use case terminates. N/A 9.1 User Cancels Confirmation 9.1.1 User clicks Cancel on the Schedule Data Flow Downtime Confirm screen. 9.1.2 System displays the Schedule Data Flow Downtime screen with selections and entries still populated. N/A 9.1.3 Use case terminates. N/A NetDMR allows for a Scheduled Data Flow Downtime to be edited by a System Administrator. Use Case Assumptions: A Scheduled Data Flow Downtime row exists. Preconditions: User has the System Administrator role and has successfully logged in to NetDMR. – Edit Scheduled Data Flow Downtime Step User Step System Response Mapping to Business Rule Flow: 1 User clicks the Data Flow Downtime link under the Manage menu. 2 System displays the Data Flow Downtime Schedule screen. Row 71 3 User clicks the Update icon in the row of interest. 4 System displays the Update Data Flow Downtime screen. N/A 5 User modifies the data flow downtime settings as needed. N/A 6* User clicks Save. 7 System validates the data according to the business rules. Rows 72 - 74
CDX NetDMR user account management and administration is implemented in CDX. Refer to Table 42: NetDMR User Management Roles and Functions for a list of user account management and administration functions performed at CDX. The following functions are no longer performed in NetDMR because they are performed at CDX: Create User Account Request or Remove user account Edit User data such as phone number, address Manage password and security questions. User data are passed from CDX to NetDMR using web services. In for CDX to successfully handoff a user to NetDMR, the CDX userid must match the NetDMR users.user_name_txt exactly. NetDMR saves pertinent user data to the database so NetDMR can identify each user and grant their proper roles and permissions so they can perform functions within NetDMR. Table 44: CDX and NetDMR Data Element Mapping provides details of user data that are passed from CDX to NetDMR and the corresponding tables and fields where these data are saved in the NetDMR database. Table : CDX and NetDMR Data Element Mapping Data Element at CDX Data Description at CDX Data Definition at CDX Set into CDX Profile at Stored at Data Mapping at NetDMR Data Definition at NetDMR User Information uid User ID for the logged in user N/A N N N/A N/A userId User ID for the logged in user Y Y NOT NULLABLE Title Name (e.g. Mr, Mrs, etc.) of the logged in user Y Y firstname First Name of the logged in user Y Y NOT NULLABLE middleinitial Middle initial of the logged in user Y N N/A N/A lastname Last Name of the logged in user Y Y NOT NULLABLE suffix Name suffix (e.g. Jr., II, etc.) of the logged in user Dropdown Y N N/A N/A fullname Concatenates Title, Middle, First, Last, and Suffix N/A N N N/A N/A
1 Internal User clicks Request Access. 2 System displays Request Access Summary (no screen title displays) screen. Row 70 3* User enters Permit ID and clicks Update. 4 System refreshes the Request Access Summary screen. The Permitted Feature dropdown contains only Permitted Features for the selected Permit ID. Rows 69, 76 5 User selects Permitted Feature and clicks Update. 6 System refreshes the Request Access Summary screen. The Limit Set dropdown contains only Limit Sets for the selected Permitted Feature. Row 69 7 User selects Limit Set and clicks Update. 8 System refreshes the Request Access Summary screen. The Monitoring Period End Date dropdown contains only Monitoring Period End Dates for the selected Limit Set. Row 69 9 User selects Monitoring Period End Date and clicks Add Access Request. 10 System refreshes the Request Access Summary screen with the new Request to the Access Requests section. Row 69 11 User clicks Submit. 12 System validates the data according to the business Rows 69 – 70 12.1 If the data are invalid, the System displays an error message Use case continues at Step 3 for data correction Else Use case continues at Step 13 N/A 13 System displays the Confirm Access Requests screen. N/A 14* User clicks Confirm. 15 System stores the new role data in the database. N/A 16 System displays the Access Request(s) Sent screen. N/A 17 Use case terminates. N/A Alternate Flows: 3.1 User Requests Access as External User 3.1.1 User enters Permit ID and clicks Update. 3.1.2 System validates the data according to the business rules. Rows 69, 72, 73, 76
1.2.3 User makes selections under the Roles section and clicks Save All Changes. 1.2.4 Confirm User Account Changes screen displays. N/A 1.2.5 User clicks Save. 1.2.6 Use case continues at Step 7 of the Basic Flow. N/A 1.3 User Approves/Denies Request from View Permit Details Screen 1.3.1 User clicks Permits under the Search Menu. 1.3.2 System displays the Permit ID screen. N/A 1.3.3 User enters Permit ID and clicks Search. 1.3.4 System validates the data according to the business rules. Row 77 1.3.4.1 If the data are invalid, the System displays an error message Use case continues at Step 1.3.3 for data correction Else Use case continues at Step 1.3.5 N/A 1.3.5 System displays the View Permit Details screen. N/A 1.3.6 User makes selections under the Pending Access Requests section of the View Permit Details screen and clicks Submit. 1.3.7 System displays the Verify Permission Changes screen. N/A 1.3.8 User makes selections and clicks Ok. 1.3.9 System displays the Permit Permissions Modified screen with a confirmation message. N/A 1.3.10 Use case terminates. N/A 4.1 User Cancels Pending Access Requests 4.1.1 User clicks Cancel. 4.1.2 System discards all changes and displays the homepage. N/A 4.1.3 Use case terminates. N/A 7.1 User Cancels Confirm Access Requests 7.1.1 User clicks Cancel on the Confirm Access Requests screen. 7.1.2 System discards all changes and displays the homepage. N/A 7.1.3 Use case terminates. N/A
3 User enters Permit ID and clicks Update. 4 System validates the data according to the business rules. Rows 69, 71, 72, 76 4.1 If the data are invalid, the System displays an error message Use case continues at Step 3 for data correction Else Use case continues at Step 5 N/A 5 System refreshes the Request Access Summary Screen with the Roles dropdown populated. N/A 6 User selects Signatory from Roles Dropdown and clicks Add Request. 7 System refreshes the Request Access Summary screen with the new Request added to the Access Requests section. N/A 8 User clicks Submit. 9 System displays Additional Information Required screen N/A 10* User enters criteria and clicks Sign on Paper. 11 System validates the data according to the business rules. Rows 74 – 75d 11.1 If the data are invalid, the System displays an error message Use case continues at Step 6 for data correction Else Use case continues at Step 8 N/A 12 System Displays Confirm Access Requests screen. N/A
1.3.4.1 If the Permit ID is invalid, the System displays an message Use case continues at Step 1.3.3 for data correction Else Use case continues at Step 1.3.5 N/A 1.3.5 System displays the View Permit Details screen. N/A 1.3.6 Use case continues at Step 3 of the Flow. N/A 3.1 User Clicks View Details Icon 3.1.1 User clicks Icon in the View Details column in the Pending Access Requests – External Signatory section. 3.1.2 System Displays the View User Account Details screen. N/A 3.1.3 Use case terminates. N/A 3.2 User Cancels Process Subscriber Agreement Details 3.2.1 User clicks Cancel on the Process Subscriber Agreement Details screen. 3.2.2 System discards all changes and displays the Process Subscriber Agreement with previous data populated. N/A 3.2.3 Use case terminates. N/A 3.3 User clicks Subscriber Agreement 3.3.1 User clicks Print Subscriber Agreement 3.3.2 System displays the Subscriber Agreement for the permit requested by the user. See Section 4.19, Subscriber Agreement, for details on the SA. N/A 3.3.3 Use case terminates. N/A 6.1 User Cancels Confirm Subscriber Agreement Responses 6.1.1 User clicks Cancel on the Confirm Subscriber Agreements screen. 6.1.2 System discards all changes and displays the Process Subscriber Agreement Details screen. N/A 6.1.3 Use case terminates. N/A
BPDF cannot be requested if a previous BPDF has been requested and has not completed, failed, or been cancelled by a user. BPDFs can also be configured to run automatically through a scheduled job. This sections deals with the manual BPDF. Automated requests are addressed in the Scheduled Jobs section of this design document. User Case Assumptions: None. Preconditions: User has the Internal Administrator role and has successfully logged in to NetDMR. NAM02 – Request Basic Permit Data Flow Step User Step System Response Mapping to Business Rule Table Basic Flow: 1 User clicks on Network Activity under the View menu. 2 System displays View Network Activity screen with a listing of transactions and status of each. The list is displayed in chronological order starting with the most recent NetDMR Created Date. N/A 3* User clicks Update Permit Information under the Request Basic Permit Data Flow section. 4 System displays the Confirm Request for Permit Data Flow screen. N/A 5* User clicks Confirm. 6 System creates a BPDF request to retrieve the list of permits that are applicable for the instance. N/A 7 System redisplays the View Exchange Network Activity screen with a new row added for the BPDF Request. N/A 8 Use case terminates. N/A Alternate Flows: 3.1 User attempts to Update Permit Information under the Request Permit Data Flow section. 3.2 System prevents user from requesting a BPDF since a previous BDPF request has not completed, failed, or been cancelled. 5.1 User Cancels Basic Permit Data Flow Request 5.1.1 User clicks Cancel on the Confirm Request for Basic Permit Data Flow 5.1.2 System discards all changes and redisplays the View Exchange Network Activity screen. N/A 5.1.3 Use case terminates. N/A
4.1 If the data are invalid, the System displays an error message Use case continues at Step 3 for data correction Else Use case continues at Step 5 N/A 5 System refreshes the View Exchange Network Activity screen with the Permitted Feature options for the specified Permit. N/A 6 User selects a Permitted Feature from the populated dropdown list and clicks Update. 7 System refreshes the View Exchange Network Activity screen with the Limit Set options for the specified Permitted Feature. N/A 8 User selects Limit Set from the populated dropdown list and clicks Update. 9 System refreshes the View Exchange Network Activity screen with Monitoring Period End Date options for the specified Set. N/A 10 User selects Monitoring Period End Date from the populated dropdown list and clicks Update DMR Information. 11 System displays the Confirm Request DMR Information by Date Range screen. N/A 12* User clicks Confirm. 13 System creates an ESDF Request with the specified parameters. N/A 14 System redisplays the View Exchange Network Activity screen with a new row added for the ESDF request. N/A 15 Use case terminates. N/A Alternate Flows: 12.1 User Cancels Empty Slot Data Flow Request by Date Range 12.1.1 User clicks Cancel on the Confirm Request for DMR Information for One DMR screen. 12.1.2 System discards all changes and redisplays the View Exchange Network Activity screen. N/A 12.1.3 Use case terminates. N/A
3 System displays the CDX Logout screen. N/A 4 Use case terminates. N/A NetDMR will a user’s session to timeout after a 30 minute period of inactivity. NetDMR keeps a Session Lockout Timer of 30 minutes visible in the header of the screen. After 28 minutes of inactivity, NetDMR will display a pop up message instructing the user that they will be timed out in two minutes. In order for a user to reset the Session Lockout Timer, a link has to be selected or the page has to be refreshed. If a user continues to be inactive, they will be logged out of both NetDMR and CDX. Use Case Assumptions: None. Preconditions: User has successfully logged into NetDMR. SC05 – Session Timeout Step User Input Step System Response Mapping to Business Rule Table Basic Flow: 1 User does not perform an action using the NetDMR interface that requires a response from the server for a period of 28 minutes. 2 System displays a pop-up indicating that the session will end at a specific time two minutes from the time of the pop up. The internal session countdown continues. N/A 3 User clicks Ok. N/A 4* User does not perform an action requiring a server response for 2 minutes. 5 System ends the session, discarding any unsaved information. N/A 6 System displays the Session Timeout screen. N/A 7 Use case terminates. N/A Alternate Flow (s): 4.1 User Performs Action 4.1.1 User performs an action that requires a response from the server. 4.1.2 System displays new screen with countdown timer reset to 30 minutes. N/A 4.1.3 Use case terminates. N/A