FPSAPP.SCH_P_CAL_SHIFTS

START_SHIFT

Shifts can be of any length and it is important that all queries get the shift length based on start_shift and end_shift rather than assuming a set number of hours. (* inherited from FPSINPUT.CAL_SHIFTS)

END_SHIFT

End of shift must be equal to the start of the next shift. Please note that the exact time which is both of the end of the previous shift and the start of the next shift is included in the next shift. In other words, start_shift <= inst < end_shift. (* inherited from FPSINPUT.CAL_SHIFTS)

SHIFT

Name of shift must be unique and can be in any format as long as it is display friendly since this is what we show everywhere. We prefer that other tables should reference start_shift rather than shift in case we want to change the naming convention for the shift. (* inherited from FPSINPUT.CAL_SHIFTS)

START_WORK_DAY

Work days must be 24 hours in length and the start of the work day must be the start of one of the shifts. Contrast this to plan day which is independent of shift. (* inherited from FPSINPUT.CAL_WORK_DAYS)

END_WORK_DAY

It is critical that this field equal the start_work_day of the next work day. (* inherited from FPSINPUT.CAL_WORK_DAYS)

WORK_DAY

START_WORK_WEEK

END_WORK_WEEK

WORK_WEEK

Name of work week must be unique and can be in any format as long as it is display friendly since this is what we show everywhere. (* inherited from FPSINPUT.CAL_WORK_WEEKS)

START_PLAN_DAY

Plan days must be 24 hours in length and the start of the plan day must be the start of one of the shifts. Contrast this to plan day which is independent of shift. (* inherited from FPSINPUT.CAL_PLAN_DAYS)

END_PLAN_DAY

It is critical that this field equal the start_plan_day of the next plan day. (* inherited from FPSINPUT.CAL_PLAN_DAYS)

PLAN_DAY

Name of plan day must be unique and can be in any format as long as it is display friendly since this is what we show everywhere. We prefer that other tables should reference start_plan_day rather than plan_day in case we want to change the naming convention for the plan_day. (* inherited from FPSINPUT.CAL_PLAN_DAYS)

START_PLAN_WEEK

Plan weeks must be 7 days in duration and the start of the plan week must be the start of one of the plan days. (* inherited from FPSINPUT.CAL_PLAN_WEEKS)

END_PLAN_WEEK

It is critical that this field equal the start_plan_week of the next plan week. (* inherited from FPSINPUT.CAL_PLAN_WEEKS)

PLAN_WEEK

Name of plan week must be unique and can be in any format as long as it is display friendly since this is what we show everywhere. (* inherited from FPSINPUT.CAL_PLAN_WEEKS)

START_REPORT_DAY

END_REPORT_DAY

REPORT_DAY

START_REPORT_WEEK

END_REPORT_WEEK

REPORT_WEEK