Standard Fields

The Assembly Planner database comes with several fields built in. The tables below lists each of Assembly Planner's standard fields, along with its description, whether it is generated automatically by Assembly Planner or by a user, and whether or not the field is editable after initially defined. All other fields you may see have been created as custom fields by clients.Additional custom fields may be added by an administrator.

Routing

Field	Description	Generated by Assembly Planner or by User?	Editable?
ID	The ID is the tag that Assembly Planner uses to track the routing in the database and the application.	User	No
Type	Some MRP systems require multiple routing types. If this is the case, the type field can be used to reflect multiple types. The default value for type is M (main) and need not be changed unless required.	User	No
Description	A description for the routing. This may be left blank if desired.	User	Yes
Plant ID	The name of the plant the routing is present within.	User	No

The tables for Operations and Activities include whether the field is global or local. For an explanation of global and local properties, see Editing the Process.

Operation

Field	Description	Generated by Assembly Planner or by User?	Editable?	Global or Local?
Status	The status field contains a lock icon if the operation is checked in to the database, a red circle if it is checked out by another user, and is blank if you have it checked out.	Assembly Planner	No	Global
ID	The ID is the tag that Assembly Planner uses to track the operation in the database and the application.	Assembly Planner	No	Global
Type	Some MRP systems require multiple operation types. If this is the case, the type field can be used to reflect multiple types. The Operation type will match its routing type.	Assembly Planner	No	Global
Description	A description for the operation. This may be left blank if desired.	User	Yes	Global
Time	The Time column displays the rolled-up total time for the operation. The rolled-up time is calculated by using the Time Standard Rank to sum all of the activity times.	User	No	Global
Operation Text	Text that is meant to be specific instructions about the specific operation. Similar to description, but can be longer and includes a spell check tool.	User	Yes	Global
OpSeqNo	Operations in the Operation List are arranged by default in the order of the Operation Sequence Number.	Use	Yes	Local
Work Center	The title of the work station at which this operation occurs. The work station should be created in the Plant Editor and then associated with the appropriate operation.	User	Yes	Local
EffectiveFromDate	The date FROM which the operation is effective (is in use) under its routing. By default, this is set to the date that the operation is created.	User	Yes	Local
EffectiveToDate	The date TO which the operation is effective (is in use) under this routing. Operations become obsolete after the Effective To Date. By default, this date is set to December 31, 2030.	User	Yes	Local

Activity

Field	Description	Generated by Assembly Planner or by User?	Editable?	Global or Local?
Status	The status field contains a lock icon if the activity is checked in to the database, a red circle if it is checked out by another user, and is blank if you have it checked out.	Assembly Planner	No	Global
ID	The ID is the tag that Assembly Planner uses to track the activity in the database and the application.	Assembly Planner generates only if User does not	No	Global
Type	Some MRP systems require multiple activity types. If this is the case, the type field can be used to reflect multiple types. The activity type will match its operation type.	Assembly Planner	No	Global
Description	A description for the activity. This may be left blank if desired.	User	Yes	Global
Est. Time	The estimated time entry for the activity.	User	Yes	Global
Est VA %	The percentage of the activity's estimated time that is Value-Added. This may also be in time units, not %.	User	Yes	Global
Est NVA %	The percentage of the activity's estimated time that is Non-Value-Added. This may also be in time units, not %.	User	Yes	Global
Est SVA %	The percentage of the activity's estimated time that is Semi-Value-Added. This may also be in time units, not %.	User	Yes	Global
Work Zone	The side or area of the line in which the activity must take place, if it needs to be restricted. Activities should have no more than one work zone and most activities will likely have no work zones.	User	Yes	Local
EffectiveFromDate	The date FROM when the activity is effective (is in use) under this operation. By default, this is set to the date that the activity is created.	User	Yes	Local
EffectiveToDate	The date TO which the activity is effective (is in use). Activities are obsolete for the parent operation after the Effective To Date passes. By default, this date is set to December 31, 2030.	User	Yes	Local
Group ID	An entry here assigns the activity to a group of tasks.	User	Yes	Local
Frequency	The number of times this activity is repeated under the particular operation.	User	Yes	Local
ActSeqNo	The Activity Sequence Number orders the activities under an operation.	User	Yes	Local
OperatorID	The OperatorID is used to indicate which operator is assigned to an activity. During the default line balance, Assembly Planner will assign Operator IDs in sequential order (1, 2, 3, etc.). The user can rename the Operator IDs as they choose. When a line balancing scenario is applied, the OperatorID is one of the fields that is filled in with results from the scenario.	Assembly Planner or User	Yes	Local

The information for Items, BOMs and Resources can be imported. Refer to the Import Data section for more information.

Item Standard Fields

Field	Description	Mandatory to Import
ID	Each item must have an ID that is unique. It can be alpha-numeric.	YES
Revision	Each Item must have a revision. The revision rules section explains what revisions are supported.	YES
Description	A description for the item being imported. This field can be up to 512 characters long or left blank.	NO
ItemType	Proplanner has seven item types. The default item type is Assembly. ▪Assembly ▪EndItem ▪Item ▪Manufactured ▪Purchased ▪RawMaterial Each of these item types has a different icon that will be associated with the item in the Assembly Planner system.	NO
PrimaryUnitOfMeasure	The default unit of measure is EA (each). Possible units of measure are: ▪EA - EACH ▪PC - PIECE ▪IN - INCH ▪FT - FEET ▪BF - BOARD FEET ▪OZ - OUNCE ▪KG - KILOGRAM ▪GR - GRAM ▪LT - LITER ▪SC - SQUARE CENTIMETER ▪SM - SQUARE METER ▪MM - MILLIMETER ▪ML - MILLILITER ▪M - METER ▪LB - POUND ▪IG - IMPERIAL GALLON ▪GA - US GALLON ▪QT - QUART ▪PT - PINT If you would like to add different units of measure, please contact Proplanner.	NO

BOM Standard Fields

Field	Description	Mandatory to Import
ID	Each item must have a unique ID. However, since items are often used in multiple operations, Assembly Planner allows the item IDs to be repeated in the BOM import file.	YES
Revision	Each Item must have a revision. The revision rules section explains what revisions are supported.	YES
Description	A description for the item being imported. This field can be up to 512 characters long or left blank.	NO
ParentID	Each Parent item must have an ID.	YES
ParentRevision	Each Parent item must have a revision.	YES
ItemType	Proplanner has seven item types. The default item type is Assembly. ▪Assembly ▪EndItem ▪Item ▪Manufactured ▪Phantom ▪Purchased ▪RawMaterial Each of these item types has a different icon that will be associated with the item in the Assembly Planner system.	NO
PrimaryUnitOfMeasure	The default unit of measure is EA (each). Possible units of measure are: ▪EA - EACH ▪PC - PIECE ▪IN - INCH ▪FT - FEET ▪BF - BOARD FEET ▪OZ - OUNCE ▪KG - KILOGRAM ▪GR - GRAM ▪LT - LITER ▪SC - SQUARE CENTIMETER ▪SM - SQUARE METER ▪MM - MILLIMETER ▪ML - MILLILITER ▪M - METER ▪LB - POUND ▪IG - IMPERIAL GALLON ▪GA - US GALLON ▪QT - QUART ▪PT - PINT If you would like to add different units of measure, please contact Proplanner.	NO
EffectiveFromDate	The date FROM when the item becomes effective under the parent. The default date is the same as the import date.	NO
EffectiveToDate	The date TO when the item stays effective under the parent.	NO
Quantity	Quantity of the child under the parent. The default value is 1.	NO

Resource Standard Fields

Field	Description	Mandatory to Import
ID	Each resource must have a unique ID and must be created by the user.	YES
Description	A description for the item being imported. This field can be up to 512 characters long or it may be left blank.	NO