Hi Olivier. 

We have some Deferrals that do not need MOC Authorisation. 

These are Deferred by the Controllers using the Job Stop. I believe that is what is happening in your case.

If Technicians cannot Defer remove the ACTION_DEFER_MEL_TASK and ACTION_DEFER_MINOR_TASK permissions from their Role.

Hi Olivier,

We agree there is a gap in the existing solution that allows users without the permission use the classic Defer Fault workflow to defer a fault using the configuration you have proposed in the new Select Reference workflow.

There is an option to restrict mechanics from deferring a fault using this new feature by implementing the MOC Authorisation functionality. You can give the permission to approve the deferral to technicians only by assigning them the Pending Reference Approvals To Do List button and the permissions API_AUTHORIZE_REJECT_REFERENCE_REQUEST. You must configure all your deferral references to use MOC Authorisation.

Prior to authorisation, the system will still allow mechanics to use the job stop functionality to record actions.

When the configuration parameter DEFER_ON_APPROVAL is set to TRUE, the action of approving the pending reference will perform the deferral. If the parameter is FALSE, the technician will allow the deferral, and the mechanic or technician can Job Stop the task to complete the deferral. Either option will not allow deferral of a fault without proper authorisation.

You can configure the system to have the level of functionality you are looking for, with the knowledge that the term “MOC Authorization” in the product takes a new meaning that better aligns with your business.

Hello Robert, 

In the Change process we identified a smaller change in our organisation to not use MOC approval (means a new menu, a approval list difficult to list for a big fleet)… That’s the reason for the question 

Also the MINOR and MAJOR split cannot be dispatch per role.

And this will prevent us to open select reference button to Mechanic and limit the use to Technician which is counter productive.

When do you think the the gap will be filled on this solution which by the way interresting 

Side question on SP12 the subtask can be called also… really interresting… (JIC can be called only and there is spécific permission to set up?)

Thanks

Hi Olivier,

In order for us to consider a change to the software, the standard support policy applies. A ticket should be raised with support.ifs.com. Your identified combination and resulting behaviour has not previously been raised for review.

To get results for the Follow-up (Recurring Inspections) you will need requirement definitions on the same assembly that are on condition and recurring. You will need the permissions API_TASKDEF_PARM

To get results for the Subtasks you must demarcate the list of accepted subclasses on the ref_task_subclass table using the def_ref_subtask_bool, and implement these same sub classes on the job cards or requirements of your choosing.

​@Robert Bellemare ​@REGD 
Many Thanks for your answers we will manage the new process and the use of Subtasks.
Good added functionality by the way …
I will raise the incident ticket for review.

Best Regards