<< Click to Display Table of Contents >> Navigation:  Library > Editing the Process > Process Effectivity - Date and Serial Number

From the section Editing the Process, we know that Assembly Planner utilizes an activity-based architecture that heavily relies on parent-child relationships.  Each level in this structure or process tree has a variety of properties, including information about effectivity.  Effectivity refers to the situations which the process is live or valid.  For example, an activity may be mapped to a specific model and have an effective date range for 1 week.

 

The Shop Floor Viewer is designed to show a worker a configured set of work instructions based on information the system knows about the unit.  The unit has properties such as a serial number, model, options, and a scheduled run date.  There are other properties that the Shop Floor Viewer is aware of, such as the line, station, and operator position that the worker is logged on to.  The Shop Floor Viewer also knows the current date and time.  Depending on Shop Floor Viewer system preferences, all of this information can be used to show the worker the configured instruction set.  For Unit Serial Number filtering, the sequence of the units (orders) in the Order List has a significant impact when determining which entities are effective.

 

Within the Assembly Planner authoring database, the engineer is able to define date effectivity and unit serial number effectivity for the following entities/objects.  This information is published to the Shop Floor database.

 

USN filtering is only performed within the Shop Floor system for work instructions and eKitting.  Work instruction reports within the Assembly Planner authoring system allows for filtering by USN.  Other reports within Assembly Planner use the USN input to derive the model and option list before reverting to date based effectivity..

For entities with USN filtering capability, if either the Start or End USN field is populated, these will be given preference over the From/To Effectivity dates within the BOM for filtering. If the data is available in From/To Effectivity Dates and also in these fields, then a combination of effective dates and Unit Serial Number (USN) Start/End will be used to identify the dates for filtering/publishing resulting in the possible narrowest window.

If the USN 'Start' field contains a value which is not present in the Order Management system, then the record is always considered active.  If the USN 'End' field contains a value which is not present in the Order Management system, then the record is always considered inactive.  This is done because the absence of the USN value from the Order Management system is interpreted to mean that the USN was once a valid value, but it has since been deleted.

If the USN is going to be used, the system will concatenate the unit's Line Schedule Date from the OrderList2 table.  The OrderList2 table contains the latest sequence of all orders within the Shop Floor database, including units which may have been deleted. A bigint comparison is then performed between the entity and the current unit the operator is signing on to. (IE the unit scanned is ABC001 and it is at position 10 in the built list.  The line sched date is 09/16/2018.  The string will be 2018091610.  If the activity has USN Start of ABC011 and it is at position 6 in the build list and the line sched date is 09/17/2018, the comparison string will be 2018091706.  Because the value 2018091706 is greater than the value of the current unit of 2018091610, the activity will not be displayed to the operator.)

If the published work instruction set has an effective date range, then the system will check the current date against the effective date of the published instruction set.  If this passes, then the downstream work instruction filtering will occur.

 

Please Consult Your Proplanner Representative for more information on USN filtering in BOM.