Control-M Batch Impact Manager (BIM) is sending "Job should have started at time xx:yy and will not start on time" alerts when the problematic jobs involved are actually on time.
BIM reports the service as "will not run", but the BIM Service is actually running on time.
The BIM service and jobs are actually executing on time.

Causes: 
1. One of the jobs in the BIM Service has an IN Condition that is external to the service flow.
This means the condition is added by another job or process that does not belong to this service or is created manually/externally.

2. One of the jobs in the BIM Service has an IN Condition that is being deleted by another job external to the BIM Service.
Somehow BIM is not aware of creation of the required condition and presume that the condition is not available.

3. One or more jobs in the service use STAT conditions and previous executions of the job(s) were put on hold.
BIM estimates held jobs will run at some point and thus the condition is "deleted" which means BIM thinks the related jobs will not run.

Set the parameter AddVirtualOrphanConditions to a different value
- To ignore deletion of a condition by a job if there are other jobs that need this condition and no job that will raise it.
- The valid values are as followed:
  0 : The feature is off (default); BIM assume all conditions are deleted.
  1 : BIM assume a condition is not deleted if
      i.  There is no job that is expected to run and adds this condition (only applies if the conditions are from the same data center)
      ii. There is a job that waits for this condition, belongs to a service and is expected to run in the future.
  2 : The same as 1 but applies to Global Conditions as well
 
- Set the " AddVirtualOrphanConditions" BIM configurable parameter to have a value of "1" or "2"
- Restart the BIM Server for this new value to take effect

In the scenario where STAT conditions are part of held jobs, delete the held jobs to prevent the alerts.