{"id":3777,"date":"2026-03-01T12:18:31","date_gmt":"2026-03-01T17:18:31","guid":{"rendered":"https:\/\/www.airsupervision.com\/wp-r\/?post_type=docs&p=3777"},"modified":"2026-03-01T12:39:01","modified_gmt":"2026-03-01T17:39:01","slug":"misc-10","status":"publish","type":"docs","link":"https:\/\/www.airsupervision.com\/wp-r\/docs\/administrator\/airsupervision-settings\/the-system-settings\/misc-10\/","title":{"rendered":"Event report SMS"},"content":{"rendered":"\n

General<\/strong><\/h2>\n\n\n\n
Type Meaning<\/th>Title<\/th>Description (titre)<\/th>Default<\/th><\/tr><\/thead>
Boolean<\/td>Activate
const_event_activate<\/code><\/td>		Activate voluntary event report.<\/td>false<\/td><\/tr>
Boolean<\/td>Display
const_event_display<\/code><\/td>		Display voluntary event report box in homepage.<\/td>false<\/td><\/tr>
Level<\/td>Minimum post level
const_event_min_level<\/code><\/td>		Minimum member’s level to be able to post a voluntary hazard report with minimum information to be evaluated. This option will allow members to post request to be treated by the Security SMS part of the system. Leave 0 to only allow member with proper credentials as manager. For a security reason, anonymous visitor will not be able to post request.<\/td>0<\/td><\/tr>
String<\/td>Sender email
const_event_sender_email<\/code><\/td>		When creating an event report, the system will automatically identify and use the login user as the sender. Setting an email will override the default action or leave it blank.<\/td><\/td><\/tr>
MemberList<\/td>Report to
const_event_reportto<\/code><\/td>		Member to automatic report to for voluntary event report manager. This process can be part of the Security SMS. This is where to mention the security officer.<\/td><\/td><\/tr>
MemberList<\/td>Always show to
const_event_showto<\/code><\/td>		Always show event report to list of below members. They will not be able to interact with the event.<\/td><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Security SMS<\/strong><\/h2>\n\n\n\n
Type Meaning<\/th>Title<\/th>Description (titre)<\/th>Default<\/th><\/tr><\/thead>
Boolean<\/td>Activate
const_sms_activate<\/code><\/td>		Activate the security managment system option. Members will be able to assess risk and keep track of datas from events reports.<\/td>false<\/td><\/tr>
TextArea<\/td>Hazard report
const_sms_hazard_report<\/code><\/td>		Define here the hazard report form template<\/td><\/td><\/tr>
Grid<\/td>Risk severity
const_sms_severity<\/code><\/td>		Each identified hazard has one or more associated risks. It is important for the risk analysis to first identify all reasonable risks arising from each hazard. Each risk can then be defined in terms of its predicted severity and its probability of occurrence. In the schema of CODE|Title|Definition<\/td><\/td><\/tr>
Grid<\/td>Risk probability
const_sms_probability<\/code><\/td>		In the schema of CODE|Title|occurence|Definition<\/td><\/td><\/tr>
Grid<\/td>Risk assessment
const_sms_matrix<\/code><\/td>		To accomplish a risk assessment, our organization will plot the results of each analyzed risk on the Risk Assessment Matrix shown below. This will be accomplished only by the Head, Safety Unit or his designee. The location of the risk on the matrix will determine the priority of corrective actions. In the schema of HTML #COLOR|Title|assessment, assessment, etc\u2026<\/td><\/td><\/tr>
Grid<\/td>Occurence category
const_sms_occurence<\/code><\/td>		List of occurence category<\/td><\/td><\/tr>
Boolean<\/td>Activate ATA
const_ata_activate2<\/code><\/td>		Activate ATA maintenance activities. Automatically add Flight record resources squawks to event report.<\/td>false<\/td><\/tr>
Boolean<\/td>Event report ATA
const_ata_activate<\/code><\/td>		Activate ATA Chapters for squawks event report. Set an ATA indicator for the complaint before the maintenance has analysed the problem. This is an option that will let you stats differences between squawks and maintenance results.<\/td>false<\/td><\/tr>
OptionList<\/td>Passed date alert
sms_close_date_alert<\/code><\/td>		Alert the member if the scheduled date is passed when no closing date has been specified.

\u2022 No alert
\u2022 one day prior
\u2022 3 days prior
\u2022 5 days prior
\u2022 one week prior
\u2022 2 weeks prior
\u2022 3 weeks prior
\u2022 one month prior
\u2022 2 months prior
\u2022 3 months prior
\u2022 6 months prior
\u2022 10 months prior
\u2022 1 year prior
\u2022 2 years prior<\/td>		one week prior<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Event report reminders<\/strong><\/h2>\n\n\n\n
Type Meaning<\/th>Title<\/th>Description (titre)<\/th>Default<\/th><\/tr><\/thead>
Number<\/td>Automatic reminder
const_event_reminder<\/code><\/td>		Set numbers of days the system will send back the even report to the concerned member, unless it is answered, corrected or closed. Leave it 0 to never remind.<\/td>0<\/td><\/tr>
Number<\/td>Automatic reminder
const_event_close_reminder<\/code><\/td>		Set numbers of days the system will send back a closing task reminder to any nominated member assigned to the task, unless it is closed. Leave it 0 to never remind.<\/td>0<\/td><\/tr>
Number<\/td>Limit before alert
const_event_qanumber<\/code><\/td>		Maximum of sent reminders before sending an alert to the quality assurance team members.Leave it 0 to never calculate limit.<\/td>5<\/td><\/tr>
Boolean<\/td>Automatic overdue lock
const_event_overduelock<\/code><\/td>		Automatically lock any member that has an overdue task to do in SMS or QA event. This option can bie disabled individually.<\/td>false<\/td><\/tr><\/tbody><\/table><\/figure>\n","protected":false},"featured_media":0,"parent":719,"menu_order":5,"template":"","doc_tag":[],"_links":{"self":[{"href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/docs\/3777"}],"collection":[{"href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/types\/docs"}],"version-history":[{"count":2,"href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/docs\/3777\/revisions"}],"predecessor-version":[{"id":3779,"href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/docs\/3777\/revisions\/3779"}],"up":[{"embeddable":true,"href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/docs\/719"}],"next":[{"title":"Printing","link":"https:\/\/www.airsupervision.com\/wp-r\/docs\/administrator\/airsupervision-settings\/the-system-settings\/misc-4\/","href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/docs\/3758"}],"prev":[{"title":"Connections","link":"https:\/\/www.airsupervision.com\/wp-r\/docs\/administrator\/airsupervision-settings\/the-system-settings\/connections\/","href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/docs\/3742"}],"wp:attachment":[{"href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/media?parent=3777"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/doc_tag?post=3777"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}