The main use case I have in mind is a Shift Brief form that dispatchers complete during or at the end of their shift. The form could contain fields such as:
Date/Shift
Dispatcher
Staffing issues
Assets or units out of service
Equipment issues
Open or pending transports
Operational concerns
Weather concerns
Important follow-up items
General shift notes
The goal would be to have the information entered into these fields available for reporting, rather than requiring someone to open and review each individual Shift Brief form.
For example, a supervisor could run a Shift Brief Report for a selected date range and see the information submitted by each shift. This would make it easier to identify recurring issues, review operational concerns, track out-of-service units or staffing problems, and see items that may require follow-up.
More broadly, I think it would be useful if fields created on custom forms/tabs could be made available within the reporting system. The Shift Brief is one example, but the same functionality could potentially be useful for QA/QI forms, weather decision forms, equipment logs, post-flight debriefs, and other customer-created forms.
Problem this would solve: Currently, valuable operational information can be collected on a custom form, but it is difficult to review that information across multiple requests or over a period of time. Making those fields reportable would allow customers to use the information they are already collecting for operational review, trend analysis, and management reporting.
The Shift Brief would be my initial use case, but I believe allowing custom form fields to be used in reports would provide much broader value.
Created CAD-6772 on this idea. If you have any other questions, please reply here.
The main use case I have in mind is a Shift Brief form that dispatchers complete during or at the end of their shift. The form could contain fields such as:
Date/Shift
Dispatcher
Staffing issues
Assets or units out of service
Equipment issues
Open or pending transports
Operational concerns
Weather concerns
Important follow-up items
General shift notes
The goal would be to have the information entered into these fields available for reporting, rather than requiring someone to open and review each individual Shift Brief form.
For example, a supervisor could run a Shift Brief Report for a selected date range and see the information submitted by each shift. This would make it easier to identify recurring issues, review operational concerns, track out-of-service units or staffing problems, and see items that may require follow-up.
More broadly, I think it would be useful if fields created on custom forms/tabs could be made available within the reporting system. The Shift Brief is one example, but the same functionality could potentially be useful for QA/QI forms, weather decision forms, equipment logs, post-flight debriefs, and other customer-created forms.
Problem this would solve:
Currently, valuable operational information can be collected on a custom form, but it is difficult to review that information across multiple requests or over a period of time. Making those fields reportable would allow customers to use the information they are already collecting for operational review, trend analysis, and management reporting.
The Shift Brief would be my initial use case, but I believe allowing custom form fields to be used in reports would provide much broader value.
Hello. Would you provide more specific examples such as the brief you have set up and the fields you are wanting to report on?