Baseline configuration for SMR events are completed under the Events Administration area of System Administration.  There is a tab for Self Monitoring to allow users to create defaults or baseline configurations for specific event types.  E.g. Semi-Annual SMR vs. Quarterly SMR.  Once Create they may be applied to an industry or a group of industries.  There are four key ‘action’ buttons at the bottom of the admin screen in addition to the creation details of the event type. 

First set up the SMR Event Types you want to use.  Most likely you will want to use the same name used in Generic events, although this is a good time to change it.

Best Practices:

1.    Include the Reporting Frequency in the name of the SMR Event Type

2.    The IU will be in NC typically 30 days after Report Period End Date and SNC typically 45 days after the Report Period End Date.  Later when we schedule SMR Events, we will have the Due Date be equal to that NC Date of 30 days after Report Period End Date.

3.    So here we want to use 0 for days late allowed NC.  That way any report received the day after the Due Date will be consider in NC.

4.    Auto Scheduler Freq you should enter the same value as Reporting Frequency. This means an SMR Event is scheduled every 6 months.

Note: Some users may have event types like “1st Qtr SMR, 2nd Qtr SMR, etc.”.  In those cases, the Auto Sched Freq would be Annual b/c they want that 1st Qtr SMR to be scheduled once per year. Others prefer event types of simply, Qtrly, SemiAnnual, Annual, and schedule them with a frequency equal to the event type name.

After all Self Monitoring Event Types are defined, you can use those to create Reporting Frequency Defaults.

Reporting Frequency Defaults are like reporting requirement templates of the various kinds of SMR Reports you need to accept.  These templates contain configuration data like Period Start Dates.  If you create a Template, you can later copy the contents of that template to an Industry or group of Industries, greatly simplifying the process of setting up Reporting Requirements for your Industries.

As your cursor enters a field, tips are displayed explaining the data that is expected.

Best Practices:

1.    The name should represent what group of industries these reporting frequencies will be copied to.  It also should include the reporting frequency in case those industries have more than 1 SMR report they need to submit.

2.    Using a Generic Linko Event we set Days Late Allowed NC to 0 because we intend the Due Date of the SMRs to be 30 days after the Report Period End Date. So here we enter 30 for “Report Due Within”. This determines the Due Date of the SMR Events.  In this case 30 days plus Report Period End Date = SMR Due Date.

3.    How far out should LinkoCTS maintain the reporting schedule? Just like COCs works.  In other words, when you are looking at the list of SMRs how far into the future do you want to see scheduled SMRs?

4.    If you own LinkoExchange, this controls how long the SMR will appear in the IU’s Scheduled Reports list.  As soon as the date passes, the report can no longer be seen or submitted in LE.

5.    Schedule Future Reports Out should be configured to create the next SMR Event on the Reporting Period Start date of that SMR.  In other words, set it to the same value as the Reporting Frequency. This will allow the report to be visible in both LinkoCTS and LinkoExchange so if the report is submitted before the Report Period End date, the user can update the SMR Event record.

6.     

After defaults are created, we can easily copy those default to groups of Industries saving us lots of time.  (This is kind of like Copy Limits in Mon Points, except that only supports copying to one industry.)

1.    Select the Industry Group that you need to create Reporting Frequencies too.

2.    Period Start Date must match the very first Reporting Period Start date you want to accept a report for.

a.    Semiannual would be Jan 1 or Jul 1 for example (assuming the Pretreatment year starts in Jan or Jul). 

b.    Quarterly would be Jan 1, Apr 1, Jul 1, Oct 1

c.    Weekly will vary based on Authority preference.  The day of week (Tuesday) is displayed to assist in determining when you want the first week to start, such as Sunday or Monday)

d.    Assuming Jan 1 2019 is used for Categorical Semiannual SMR, later when the SMR Events are scheduled for those Industries, they will have the first SMR Event like this:

                                       i.    SMR Event Type of “Semiannual SMR”

                                      ii.    Reporting period of Jan 1 2019 – Jun 30 2019

                                     iii.    Due date of Jul 30 2019

3.    Press Copy Defaults and these configurations are copied to all Active Categorical IUs.

a.    If an industry in the group already has a Reporting Frequency for that Event Type and Period Start Date, user must choose to overwrite it or not.

b.    User can also apply the default frequencies to any Industries that do not have it yet. Use Group, then select “Active IUs w/o Report Frequencies” from the Industry Group dropdown.

c.    Choosing to overwrite will delete and replace the reporting frequencies, it will not delete any scheduled SMRs (this is just like MP Limits Copy works)

d.    If user enters a different Period Start Date, any previously defined reporting frequencies for that Industry are retired and the new one is created (also like MP Limits)

4.    Repeat the process for all Industries that are required to submit SMRs

Best Practice:

Rather than Copy Default to all Industries immediately, get familiar with the process by doing just one industry or even a fake test industry. This will allow you to see and learn the entire process without worry of affecting too many industries in case a mistake is made.