question

I'm going to start by describing the general case for the timetable and how to access the time of the next stop.

In the timetable's resume function you have access to the tablerow of the table found at:

Table(getvarnode(current,"table"))

This table currently tells you the time of day (in model units) of the stops - the first being at 10 hours - 36000 seconds, corresponding to this stop:

Since you know the stoppage row from which you are resuming you can determine the time of the next stoppage and write that onto your object. Then you can use that label to determine if you should close/stop ports or use some other mechanism to restrict the processing.

Table stops=Table(getvarnode(current,"table"));
double tablenow=stops[tablerow]["Time"]+stops[tablerow]["Duration"];  //check
double repeattime=getvarnum(current,"repeattime");
double stopend=tablenow;
double nextstop=0;
int nextstate=0;
int searching=1;
int looped=tablerow==stops.numRows;
int firstcheckrow=(tablerow==stops.numRows)?1:tablerow+1;
for (int nextrow=firstcheckrow;searching;nextrow++){
    if (nextrow>stops.numRows){
        looped=1;
        nextrow=1;
    }
    nextstop=stops[nextrow]["Time"]+looped*repeattime;
    nextstate=stops[nextrow]["State"];
    if (nextstop!=stopend)
        break; //searching=0;
    stopend=nextstop+stops[nextrow]["Duration"];
}
double nextModelStopTime=time()+nextstop-tablenow-looped*getvarnum(current,"modelstarttime");
print("Row:",tablerow, current,"next stop:", nextModelStopTime);
downobject.nextstop=nextModelStopTime;
downobject.nextstate=nextstate;

Since this only happens when an object resumes you may need a method to put this value on the object when the model starts but since you're only concerned with the stop at the end of the day the break at 10:00 am probably isn't of concern.

All you need next is the expected or 95% makespan time to figure out if you have enough time to start an item.

If you only want to consider certain states then you can modify the code to check only for the offshift states, or you may find it easier to have the objects a member of production schedule and break schedule as two distinct timetables, in which case the logic above should work fine to tell you when the production time for the day will end, but you will may need the reset code below to set the label to show the first stop time:

Object current=Model.find("Tools/TimeTables/TimeTable1");
Table stops=Table(getvarnode(current,"table"));
double modelStart=getvarnum(current,"modelstarttime");
int n;
for (n=1;stops[n]["Time"]<=modelStart;n++){1;}
treenode memberlink=getvarnode(current,"members").first;
while (memberlink){
    Object member=ownerobject(memberlink.value);
    member.nextstop=stops[n]["Time"]-modelStart;
    member.nextstate=stops[n]["State"];
    memberlink=next(memberlink);
}

You can put that code or something similar (more robust) in the onModelReset trigger.