Jürgen,
What you are asking for are 'ImmediateBreakdown' and 'ImmediateMaintenance' inputs for ResourceUnit. Unfortunately, it is not obvious how these features should work for resources. If the ResourceUnit seized by a SimEntity breaks down, should the SimEntity immediately stop whatever activity it is doing at the time? This would have to be implemented specially for every type of object that can receive a SimEntity, some of which do not implement breakdowns/maintenance themselves, such as EntityDelay and Queue.
The first problem you described is much easier to solve. Both ResourceUnits ('Machine1' and 'Machine2') use the same DowntimeEntity ('Maintenance') as the input to their ForcedMaintenanceList input. Since these are 'forced' maintenance activities, it is necessary for BOTH Machine1 and Machine2 to be idle before the downtime event can begin. This is a requirement because both machines must be maintained at the same time. However, when the entity delay duration is greater than 1 second, there is no time at which both machines are idle! The solution is to assign a separate DowntimeEntity to each machine so that they can be maintained separately.
Harry