AccuMark Updates for the CAD Relational Database

AccuMark has the ability to store statistical information and thumbnail images for markers,
models and their pieces in an optional CAD Relational Database (RDBMS). The RDBMS can
then be used for querying and retrieving information and thumbnail images for use with a PLM or
ERP system.

Information stored in RDBMS will only come from SQL storage areas and subfolders. Userroot
data is not connected to RDBMS.

Use the SQL Support dialog in AccuMark software to configure the database to be used to store
this information. Consult the AccuMark documentation in the Training Docs folders for details on
how to set it up.

CAD Relational Database Tables

The database tables have fields of information populated from data in the AccuMark SQL
environment. Data is stored into the data tables from AccuMark applications when marker, model
and its piece data is created, updated, deleted, or copied.

This diagram provides a brief overview of the tables and how they are connected to one another.

Uses AMXMPLOT to
generate marker image.

Uses AMXPPLOT to
generate piece images.

Page 1 of 23
Data written into RDBMS
The tables are always updated in the same way, regardless of how the data is modified by
different functions in the AccuMark. Any creation, deletion or modification causes all of the fields
in the data tables that the AccuMark writes to, to be overwritten; there is no selective updates to
rows. If an update is being done, it always updates the same columns regardless of what
function caused the data to be stored.

Currently for deletion of AccuMark data items, no columns are updated except the IsActive
Column, which is set to 0. To physically remove the data items from the relational table, a query
can be created to do this manually.

If the user has selected the “Generate Image” option in SQL Support, the images for markers and
model pieces will get created if they don’t already exist. Images will be updated or regenerated if
changes are made to the markers like piece placement, or for pieces like perimeter changes. To
save process time, images are only updated when needed, if changes are made that do not
require regeneration of the images, then the existing images will remain.

For Marker images any text written on the image is the text as specified through the Annotation
ordered with the marker. For piece images, any text written on the image(s) is the text as
specified through the Annotation table that is referenced in SQL Support (this same annotation
table must exist in all SQL storage areas and subfolders).

Software upgrades and how they affect the RDBMS tables

Newer versions of AccuMark software may be enhanced to write additional information into the
database tables that did not exist previously. Or as in the case of updates in AccuMark version 9
software and later editions, the data item names were increased from 20 characters to 50
characters, size names were increased from 6 characters to 30 characters, and so on. Thus,
when any data is stored in the SQL storage areas or subfolders, these new fields will be added
and existing fields will be updated to reflect the increase in field sizes.

For these reasons, you will need to have a supported version on PDM, PLM or your ERP
software that can handle the updated information. Not using the updated software versions to
retrieve information may cause issues. Consult the AccuMark Release Notes for the software
compatibility chart.

When and How Data is Written into RDBMS

The following provides information for when data is written into the RDBMS. The list may not be
complete, as there are many ways to create, update, and manipulate data throughout the
AccuMark applications.

Markers
The AccuMark functions that cause a marker to be created, updated or deleted on disk will also
create new entries in the CAD Relational Database or update existing records. Depending on the
action or function invoked, different fields in the table(s) will be filled in or updated. These
functions include:

In AccuMark Explorer
Import Zip
Zip files could include multiple data types and either create new data items or overwrite
existing data items (in V8.2.2: updates to the CAD relational database with newly

Page 2 of 23
 imported items is not functioning properly. Run the Sync Relational Data get the
information up to date after importing zip files).
Save As
Save As will create a new marker in the same or different storage area. Save As can use
the existing name and just save to a different storage area.
Rename
Rename will modify the existing marker name in the same storage area.
Copy
Copy creates a new marker in a different storage area.
Copy with Components
Copy with components creates a new marker with all of its associated data in a different
storage area.
Move, Drag and drop
Move or Drag and drop will move a marker to a different storage area.
Move Clipboard
Move Clipboard to move copied data to a different storage area.
Move with Components
Move with Components will move copied data with all of its associated data to a different
storage area. The components for a marker include the models and pieces.
Move Clipboard with Components
Move Clipboard with Components will move copied data with all of its associated data to
a different storage area. The components for a marker include the models and pieces.
Delete
Delete removes data from a storage area. The data is put in the Recycle Bin.
Delete with Components
Delete with Components removes data and all of its associated data from a storage area.
The data is put in the Recycle Bin. The components for a marker include the models and
pieces.
Restore Recycle Bin
Restore Recycle Bin restores deleted items to their previous storage area.
Regenerate Marker
Regenerate Marker is used to update a marker with newer information. If any component
of the marker has a later date than the marker, the order is reprocessed and the marker
is remade using Copy Marker and then restored (versions prior to AccuMark V8.2.2
would create a maker entry called –regen-, this has been fixed. –regen- is a temporary
marker that is used in the process of recreating the marker with updated information )
Open Marker with Auto Update of Marker enabled
Open Marker with Auto Update of Marker enabled is used to update a marker with newer
information. If any component of the marker has a later date than the marker, the order
is reprocessed and the marker is remade using Copy Marker and then restored (versions
prior to AccuMark V8.2.2 would create a maker entry called –regen-, this has been fixed.
–regen- is a temporary marker that is used in the process of recreating the marker with
updated information )
Generate Cut Data with Auto Update of Marker
Generate Cut Data with Auto Update of Marker on (or prompt) will update the pieces in
the marker if they have been changed since the last time the marker was stored.

AccuMark Explorer: Utilities:

Move
Move marker(s) to a different storage area.
Copy
Copy marker(s) to different storage area(s).
Copy while renaming in the New Names column

Page 3 of 23
 Create the same marker with a new name to different storage area(s)
Rename
Create the same marker with a new name into a different storage area(s)
Delete
Remove the marker from the storage area(s)

NOTE: in the Utilities functions variations of copying, etc can be done with same or different
source and destination locations as well as same or new data item names, with or without
overwrite, and “with Components” options

SQL Backup & Restore

SQL Restore from Backup
Restoring of data from SQL Backups puts backed-up data into a storage area. This
could create new items or overwrite existing items.

Pre Version 10: in AccuMark Utilities

Version 10: AccuMark Explorer: File: Options: Storage Areas
Sync Relational Data
Sync Relational Data lets the user manually update the CAD relational data tables from
the AccuMark database (storage areas).
Upgrade SQL
Upgrades a previous version’s SQL storage area to the current software version
Restore Last Schema – function not available starting in V10 and later
Restores the storage area to the prior version

Marker Making
Open, Open Next, Open Next Made, Open Next Unmade, Open Previous, Open Original
When a Lectra, Assyst or Investronica marker is opened, the necessary models included
in the marker are created.
Open Marker with Auto Update of Marker enabled including Open, Open Next, Open Next Made,
Open Next Unmade, Open Previous, Open Original
Open Marker with Auto Update of Marker enabled is used to update a marker with newer
information. If any component of the marker has a later date than the marker, the order
is reprocessed and the marker is remade using Copy Marker and then restored (versions
prior to AccuMark V8.2.2 would create a maker entry called –regen-, this has been fixed.
–regen- is a temporary marker that is used in the process of recreating the marker with
updated information )
Save
Save As is used to create a new marker in the same or different storage area. Any
models created by Open are also saved.
Save As
Save As is used to create a new marker in the same or different storage area. Save As
can use the existing name and just save to a different storage area. Any models created
by Open are also saved.
Save Temporary
Save Temporary is used to save the marker in the same storage area. The difference
from Save is the status of ‘Needs Approval’.
AutoMark
Starting with AccuMark V8.3 the user is allowed the option to invoke Automarking. The
AutoMark editor allows the user to automatically make the same marker or to store to a
new marker name. If the destination marker is the same name, then that marker is updated

Page 4 of 23
 in the RDBMS. If the destination marker is a new name, then that new marker is added to
the RDBMS.
Attach Marker
Allows user to keep same name or enter a new one. Versions prior to AccuMark V8.3 did
the attach marker but did not automatically update the CAD Relational database; it only
saved the data into the RDBMS when user selected the save option, whether this was for
the same name or a new name marker.
Attach Marker - Gives user option to delete original markers.
Versions prior to AccuMark V8.3 would allow the user the option to enter a new name
and to delete the original marker, and you would see the data immediately in the
AccuMark Explorer, however the data was not written to RDBMS at that time, and in
Marking you could go and open this new marker without having to specify a save first.
Piece, Add Piece
Allows the user to select one of the existing pieces in the marker and adds a piece of that
size to the maker. When the marker is stored, additional entries for the newly added
pieces are stored in the tables.
Piece, Delete Piece
Allows the user to select one of the existing ADDED pieces in the marker and deletes it
from the maker. When the marker is stored, entries for the deleted pieces are marked
inactive in the tables.
Bundle, Add Size
Allows the user to select one of the existing sizes in the marker and adds a piece of that
size to the maker. (As of AccuMark V8.3.0 beta 2 information regarding an added size is
not totally reflected in the RDBMS)
Bundle, Add Bundle
Allows the user to select one of the existing bundles or a piece in one of the bundles in the
marker and adds a bundle of that size to the marker. Versions prior to V8.3 did not properly
updated the related information in the RDBMS
Bundle, Add New Size
Does a Save and then a Regenerate if Auto Update of Marker is enabled. Then dialog
box prompts for which Model (for those in this marker) and to enter a size. Does a
Regenerate at this time too.
Bundle, Delete Bundle
Allows the user to select one of the existing ADDED bundles in the marker and deletes it
from the maker. When the marker is stored, entries for the deleted pieces of that bundle
are marked inactive in the tables.

Tools, Block Fuse, Create Fusing Marker

Allows the user to create a Fusing marker

Order Process, Batch, AccuNest, AutoMark

Order Process (with and without LayRules), Batch, AccuNest, and AutoMark all create new
markers or can overwrite existing markers.

In Marking or in an Order any modification can occur to an existing marker such as adding or
removing models or pieces, changes to the width or length, etc. The marker can be regenerated
or reordered.

Batch
Create or Update when order process, marked (MED, AutoMark, AccuNest) and again if any
manual approvals are set.

Page 5 of 23
AccuNest
Marker entries will be in the database and updated as the marker is stored from AccuNest.
 If “Restart Marker” the length must change from 0 or if it has an existing length, reset and
report the newly stored length and efficiency information.
 If “Finish Marker” is selected, the existing marker entry fields should all be updated with
the new length and efficiency information.

Pre Version 10: AccuNest PE, EE, PK

 If using AccuNest PE, the store occurs after engine 1.
 If using AccuNest EE, the marker is stored after nesting and again after packing. The
database needs to update with each store.
 If using AccuNest PK, the marker is stored after packing.

AutoMark
Create or update of markers.
 Destination marker name can be the same or different than the source marker name.
 Marker is stored in same location (does not let you choose a different destination
location).
 Can reprocess and change the various placement strategies or piece options.
 Options for writing/saving include:
o Replace if better (so it should not save the marker if the utilization(?) is not
Improved)
o Overwrite Destination Marker If Exists
 If Partial Marker (the marker already exists with some pieces placed) options include:
o Maintain Placed
o Start from Scratch

Marker Edits/Conditions that could affect Data Tables

Note: some of these items require further discussions and investigation to the tables and fields
that are needed to accommodate the desired data.
 Markers share model(s) and a model is edited/deleted/added
 Markers share piece(s) and the piece is edited/deleted

Models
The AccuMark functions that cause a model to be created, updated or deleted on disk include:

In AccuMark Explorer
Import Zip
Zip files could include multiple data types and either create new data items or overwrite
existing data items.
Save As, Rename
Save As or Rename is be used to create a new model in the same or different storage
area. Save As can use the existing name and just save to a different storage area.
Copy
Copy is be used to create a new model in a different storage area.
Copy with Components
Copy with components is be used to create a new model with all of its associated data in
a different storage area.
Move, Drag and drop
Move or Drag and drop is used to move a model to a different storage area.
Move Clipboard
Move Clipboard is used to move copied data to a different storage area.

Page 6 of 23
Move with Components
Move with Components is used to move copied data with all of its associated data to a
different storage area. The components for a model include the pieces.
Move Clipboard with Components
Move Clipboard with Components is used to move copied data with all of its associated
data to a different storage area. The components for a model include the pieces. The
components for a marker include the models and pieces.
Delete
Delete is used to remove data from a storage area. The data is put in the Recycle Bin.
Delete with Components
Delete with Components is used to remove data with all of its associated data from a
storage area. The data is put in the Recycle Bin.
Restore Recycle Bin
Restore Recycle Bin restores deleted items to their previous storage area.

AccuMark Explorer, Utilities:

Move
Move model(s) to a different storage area.
Copy
Copy model(s) to different storage area(s).
Copy while renaming in the New Names column
Create the same model with a new name to different storage area(s)
Rename
Create the same model with a new name into a different storage area(s)
Delete
Remove the model from the storage area(s)

NOTE: in Utilities variations of copying, etc can be done with same or different source and
destination locations as well as same or new data item names, with or without overwrite and “with
Components” options.

Restore from SQL Backup

Restore from a SQL Backup puts backed-up data into a storage area. This could create
new items or overwrite existing items.

Pre Version 10: In AccuMark Utilities

Version 10: in AccuMark Explorer: File: Options: Storage Areas
Sync Relational Data
Sync Relational Data lets the user manually update the data tables from the AccuMark
database.
Upgrade SQL
Upgrades a previous version’s SQL storage area to the current software version
Restore Last Schema – function not available starting in V10 and later
Restores the storage area to the prior version

Model Editor
Save
Save As is used to create a new model in the same or different storage area.
Save As
Save As is used to create a new model in the same or different storage area. Save As
can use the existing name and just save to a different storage area.

Page 7 of 23
PDS
Create/Edit Model
Add/Remove Pieces is used to add or remove pieces to/from a model.
Edit Model
Edit Model opens the Model editor.
Create Piece
An option in all of the Create Piece functions updates the model when this option is
enabled.
Split Piece
An option in all of the Split Piece functions updates the model when this option is
enabled.
Combine/Merge
An option in all of the Combine/Merge functions updates the model when this option is
enabled.

Order Functions that can create a Model

Data Conversion Utility
Pattern Conversion Wizard
Process – The Pattern Conversion Wizard is used to import pieces and models from
other file formats.
Style Converter
Process – The Style Converter is used to import pieces and models from the MicroMark
format.
CSV Tools
Import/Run – CSV can be used to write models to the AccuMark database from a CSV
file.
Toolkit
Command line – The Toolkit can be used to write models to the AccuMark database from
an outside source.
Marker Making (see previous section)

Model Edits/Conditions that could affect Model and Piece information Data Tables
Note: some of these items require further discussions and investigation to the tables and fields
that are needed to accommodate the desired data, for instance – whether a deleted piece should
be marked as inactive or its reference physically removed from the relational database
 Add or remove pieces from a model
 Reorder the pieces in a model (update piece position in Cad_Model_Details)
 Comment pieces, with and without fabric codes
 Remove a piece from a model
 Replace (rename) a piece in a model with another that exists
 Replace (rename) a piece in a model with another piece name that does not exist (yet)
 Physically delete a piece that a model uses
 Pieces that are used in more than one model
 Update a piece (i.e. change the shape)
 Change the base size dimensions
 Pieces that are used in more than one model
 Assign new grade rule table
 Duplicate piece names listed in model
 Delete - Does only the model get marked as deleted (isActive in Cad_Model_details) or does
each of its pieces (Cad_Piece_Details) as well? If the pieces also get marked as deleted,
does it have to determine if that piece is used by any other models
 Model options
 Use of size code tables

Page 8 of 23
 Use of half piece sharing
 Restore Deleted Items does not restore Active state in RDBMS (A-8521). Deleted Model
w/components. Noticed that the status became Inactive in the Relational Database for both
the model and the pieces. Then Restored the data back to the storage area and the status
remained Inactive. The model and pieces should have become Active

Pieces
Only pieces that exist in a model are updated in the data tables. This is determined by searching
the piece name in the CAD_Model_Details table. The AccuMark functions that cause a piece to
be updated or deleted on disk include:

Explorer
Import Zip
Zip files could include multiple data types and either create new data items or overwrite
existing data items.
Save As, Rename
Save As or Rename is be used to create a new piece in the same or different storage
area. Save As can use the existing name and just save to a different storage area.
Copy
Copy is be used to create a new piece in a different storage area.
Copy with Components
Copy with components is be used to create a new piece with all of its associated data in
a different storage area.
Move, Drag and drop
Move or Drag and drop is used to move a piece to a different storage area.
Move Clipboard
Move Clipboard is used to move copied data to a different storage area.
Delete
Delete is used to remove data from a storage area. The data is put in the Recycle Bin.
Restore Recycle Bin
Restore Recycle Bin restores deleted items to their previous storage area.
Verify Digitized Data
Verify Digitized Data creates pieces, these pieces could already be listed in a model.

AccuMark Explorer, Utilities:

Move
Move pieces that belong to model(s) to a different storage area.
Copy
Copy piece(s) that belong to model(s) to different storage area(s).
Copy while renaming in the New Names column
Create the same pieces of model(s) with a new name to different storage area(s)
Rename
Create the same piece(s) of model(s) with a new name into a different storage area(s)
Delete
Remove the pieces belonging to model(s) from the storage area(s)

NOTE: in Utilities variations of copying, etc can be done with same or different source and
destination locations as well as same or new data item names, with or without overwrite.

Page 9 of 23
Restore from SQL Backup
Restore from a SQL Backup puts backed-up data into a storage area. This could create
new items or overwrite existing items.

Pre Version 10: In AccuMark Utilities

Version 10: in AccuMark Explorer: File: Options: Storage Areas
Sync Relational Data
Sync Relational Data lets the user manually update the data tables from the AccuMark
database.
Upgrade SQL
Upgrades a previous version’s SQL storage area to the current software version
Restore Last Schema – function not available starting in V10 and later
Restores the storage area to the prior version

Model Editor
Piece categories and descriptions can be edited in the model and are saved directly to disk
without using a Save function (Rename Mode)

PDS
Save
Save is used to create a new piece in the same or different storage area.
Save As
Save As is used to create a new piece in the same or different storage area. Save As
can use the existing name and just save to a different storage area.
Create/Edit Model
Piece names can be changed in Add Pieces.

Order Functions that can create a Piece

Data Conversion Utility

Pre Version 10
Pattern Conversion Wizard
Process – The Pattern Conversion Wizard is used to import pieces and models from
other file formats.
Style Converter
Process – The Style Converter is used to import pieces and models from the MicroMark
format.
DXF Import
DXF Lookup – DXF can be used to import dxf files and save them as AccuMark pieces.
Lconvert
Convert – Lconvert can be used to import Lectra IBA and VET files and save them as
AccuMark pieces.

Piece Edits/Conditions that could affect Piece information Data Tables

Only information about pieces that belong to a model are tracked within the same storage area or
subfolder. Users often work on a piece level and may expect different results. For example, a
model and its pieces exist in both a sql storage area and a subfolder. One of the pieces belonging
to a model is modified in the subfolder, and thus its data as related to the model(s) in that same
subfolder are updated in the RDBMS. Now the user copies the modified piece into the parent
storage area, but does not see any updates made to the model in the parent storage area. This is
correct. The updates will only trigger if the model and its component pieces are copied.

Page 10 of 23
How Graphics are generated
In AccuMark Utilities, SQL Support an option is available to enable image generation. If this
option is enabled, an optional annotation table can be used to specify the text written with the
image. The annotation table specified in SQL Support is used when images of pieces are
generated and must exist in the storage area or subfolder. When images of markers are
generated, the annotation table specified in the marker order is used.

AMXMPLOT is used to generate the image for the marker and AMXPPLOT is used to generate
the image for the piece. When the images are generated, they are temporarily stored in
userroot\temp. This requires permissions to the userroot\temp directory. Like all other data in the
userroot\temp directory, it is removed at boot up or reboot.

Relational Data Tables

The purpose is to determine when rows (entries) should be created in the tables and when the
entries should be updated. Also which fields should be written to initially and which fields to be
updated when updates to markers or models and their related pieces occur, and the appropriate
values for each field.

Items in this blue – do not know what they are or if they are used
Items in this red – not updated by AccuMark

TABLE: Cad_Cats
Written to when the Cad_Marker_Details or Cad_Model_Details is updated. We run a stored
procedure provided by WebPDM: pGetCadCatID given the arguments (database name, object
name, code, type (model or marker), then fill in all columns in table. This table is only edited
when a marker is created, not updated.

Variable Name Type, Default Values Description

Value
CADCatId Int, not NULL Unique Primary key
primary key
Name Varchar(50), SA name Storage area (support for 20 characters)
NULL only, not
path
IsActive Int, -1 -1 = exists Indicates whether the marker can be used in
0 = deleted new WebPDM Folders.
ParentId Int, 0 If this is a subfolder, then references it parent
storage area’s Cad_Cats ID
IsLeaf Int, 0 -1 Indicates if it has subfolders
Type Int, 0 0, 1 ?
RootId Int, 0 1, 2 ?
Level1 Int, 0 1,2,… Subfolder level
Last_Updated Datetime, Stored as Last time something in storage area was
NULL UTC updated (?)

Page 11 of 23
TABLE: AccuMark Paths
Used by the AccuMark to trace back where the source is.

Variable Name Type, Default Value Values Description

Server Varchar(50), not Includes instance name SQL server name (as
NULL where appropriate defined in AM Utilities,
SQL Support) (primary
key)
Storage_Area Varchar(50), not SA name only, no path Storage area of data
NULL objects (primary key)
Support 20 character
storage area names
Name Varchar(100), not marker or model name Data object name
NULL (primary key) Support
maximum of 50
character data item
name
TypeId Int, not NULL Datatype: references TypeId in
10 = mark (marker) AccuMarkTypes table
13 = model (primary key)
CategoryGuid Uniqueidentifier, not Used with subfolders (?)
NULL (primary key)
Code Int, not NULL Links to references
1=Cad_Marker_Details Marker_code in
2=Cad_Model_Details Cad_Marker_Details or
Model_code in
Cad_Model_Details
depending on the value
of TypeId
UnitFlag tinyint NULL

TABLE: LastKeyUsed
Updated when any table has a new entry added. Lists the last key code used.
Variable Name Type, Default Value Values Description
TableName Varchar(50) not NULL Name of RDBMS table (i.e.
CAD_Marker_Details)
LastKey Int, NULL last key ID used for that
table

TABLE: PPFImages
Updated when the Cad_Marker_Details or Cad_Piece_Details is updated. Contains image serial
number and image file details. There is one row for each image generated.

Variable Name Type, Default Values Description

Value
ImageSerialNumber Int, not NULL (Links to Cad_Piece_Details or
Links to Cad_Marker_Details ) and
Links to PPFRepresentatives for WMF and
Links to PPFThumbnails for BMP
OriginalFileName Varchar(100), NULL Not updated by AccuMark
NULL

Page 12 of 23
BlobType Int, NULL 0 ?
ThumbNailFileName Varchar(100), Name of file for image (bmp) thumbnail.
NULL initially stored in \userroot\temp. Support
maximum of 50 character data item name
RepFileName Varchar(100), Name of image file (wmf)
NULL initially stored in \userroot\temp. Support
maximum of 50 character data item name
IsVector Int, not NULL -1 ?
RedLineFileName Varchar(100), NULL Not updated by AccuMark
NULL
Name Varchar(50), Index Related data item name (piece or marker
NULL name)
OriginalFileSize Int, NULL NULL Not updated by AccuMark

TABLE: Blocks
Updated when PPFImages is updated. There is one row for each image generated.
Variable Name Type, Default Value Values Description
BlockId Int, not NULL Unique id serial number of image
in PPFImages table (primary key)
WhenCreated Datetime, NULL Date block/image was created
WhoCreated Varchar(50), NULL Who the block/image was created
by. Stephen says it cannot be
filled in.
WhenModified Datetime, NULL Date the block/image was last
modified
WhoModified Varchar(50), NULL Who modified the block/image.
Who the block/image was created
by. Stephen says it cannot be
filled in.
StatusApproved Int, not NULL 1
WhenApproved Datetime, NULL NULL Not updated by AccuMark
WhoApproved Varchar(50), NULL NULL Not updated by AccuMark
BlockType Int, not NULL 17
LockedBy Varchar(50), NULL NULL Not updated by AccuMark
NoteApproved Varchar(255), NULL NULL Not updated by AccuMark
PrimaryBlockId Int, NULL NULL Not updated by AccuMark
Notify Varchar(255), NULL NULL Not updated by AccuMark

TABLE: PPFRepresentatives
Updated when the Cad_Marker_Details or Cad_Piece_Details is updated. WMF representation
of image. There is one row for each image generated.

Variable Name Type Meaning

ImageSerialNumber Int, not NULL Link to PPFImages (primary key)
ImageSize Int, NULL Size of the image in bytes
ImageBLOB Image, NULL Data for WMF image drawing

Page 13 of 23
TABLE: PPFTable2Image
Updated when the Cad_Marker_Details or Cad_Piece_Details is updated. There is one row for
each image generated.

Variable Name Type Values Description

DataTableId Int, not NULL Links to DataTables Always set to 13
(primary key)
DTRecordId Int, not NULL Links to Cad_Marker_Details or
Cad_Piece_Details(primary key)
ImagePosInRec Int, not NULL Always set to 1(primary key)
TableName Varchar(50), Cad_Marker_Details or
not NULL Cad_Piece_Details(primary key)
ImageSerialNumber Int, NULL index Links to PPFImages
ImageContext Varchar(50), NULL Not updated by AccuMark
NULL
LongDesc Varchar(50), NULL Not updated by AccuMark
NULL
ShortDesc Varchar(15), NULL Not updated by AccuMark
NULL

TABLE: PPFThumbnails
Updated when the Cad_Marker_Details or Cad_Piece_Details is updated. BMP representation of
image. There is one row for each image generated.

Variable Name Type, Default Values Description

Value
ImageSerialNumber Int, not NULL Links to PPFImages (primary key)
ImageSize Int, NULL Size of image in bytes
ImageBLOB Image, NULL Binary data for BMP image

TABLE: Cad_Marker_Details
Updated when any marker is updated. Iinformation about a marker. There is one row for each
marker in a SQL storage area or subfolder.

Variable Name Type, Default Values Description

Value
Marker_Code Int, not NULL, Matches Code in AccuMark Paths table
0 (primary key)
Marker_Name Varchar(100), Name of marker.
not NULL Support maximum of 50 character data
item name
Location Varchar(510), Server and storage area name [ +
NULL subfolder/s ]
Last_Updated Datetime, Stored in Date & time marker was last updated
NULL UTC/GMT (Stored)
IsActive Int, NULL, -1 -1 = exists Indicates whether the marker can be used
0 = deleted in new
WebPDM Folders.
IsLinked Int, NULL -1
ClassifierId Int, not NULL 0
SystemId Int, not NULL 1
Marker_Description Varchar(510), Description/comments as stored in marker

Page 14 of 23
 NULL
Marker_CrOpId Varchar(100), Name of user who created marker
NULL
Marker_Create Datetime, Date & time marker was originally created
NULL (stored)
Marker_RevOp1 Varchar(100), Person who made first revision updates
NULL
Marker_Rev1 Datetime, Date & time marker was recently stored.
NULL Initially this field = Last updated. If user
manually edits in WebPDM the fields
won’t match.
Marker_RevOp2 Varchar(100), Person who made last modifications
NULL
Marker_Rev2 Datetime, Last modified date and time
NULL
Marker_Width Float, NULL Width of marker in Imperial
Marker_Length Float, NULL Length of marker in Imperial
Marker_Total_Perim Float, NULL Total perimeter length of all [placed]
pieces in the marker in Imperial
Marker_Total_Area Float, NULL Total area of all [placed] pieces in the
marker in Imperial
Marker_Goal Float, NULL NULL Not updated by AccuMark
Marker_Efficiency Float, NULL The efficiency of marker when it was
stored
Marker_Notches Int, NULL Total number of notches of all [placed]
pieces
Marker_DrillHoles Int, NULL NULL Not updated by AccuMark
Marker_Corners Int, NULL Total number of corners of all [placed]
pieces. The numbers of corners are the
same as reports.
Marker_Message Varchar(100), NULL Not updated by AccuMark
NULL
Marker_nModels Int, NULL Total number of models in this marker
Marker_nPieces Int, NULL Total number of pieces ordered with
marker this includes added pieces.
Marker_PlacPieces Int, NULL Total number of placed pieces in marker
Marker_nSizes Int, NULL Number of unique sizes for all pieces in
marker for all models
Marker_nBundles Int, NULL Total number of bundles ordered in
marker. This includes placed/unplaced
and added bundles.
Marker_Plac_Bndl Int, NULL Total number of placed bundles
Marker_Bias Int, NULL 0 Not updated by AccuMark
Marker_Flip Int, NULL 0 Not updated by AccuMark
Marker_Nap Int, NULL 0 Not updated by AccuMark
Marker_NCEdits Int, NULL 0 Not updated by AccuMark
Marker_Spread Int, NULL 0 Not updated by AccuMark
Marker_Closed Int, NULL 0 Not updated by AccuMark
Marker_DieBlk Int, NULL 0 Not updated by AccuMark
Marker_Tublar Int, NULL 0 Not updated by AccuMark
Marker_StripePlaid Int, NULL, 0 0=no, Indicates if stripe or plaid lines are present
-1=yes
Marker_nStripes Int, NULL NULL Not updated by AccuMark
Marker_nPlaids Int, NULL NULL Not updated by AccuMark

Page 15 of 23
Marker_5_Star Int, NULL 0=no, Indicates if 5-star matching is used
-1=yes
Marker_Max_Splice Float, NULL NULL Not updated by AccuMark
Marker_nSplices Int, NULL Total number of splice marks in marker
Marker_XVariance Float, NULL Stripe offset - Imperial
Marker_YVariance Float, NULL Plaid offset - Imperial
Marker_Image_SN Int, NULL Links to PPFImages
Marker_Image_Name Varchar(1000), N/A List of the Model Materials. List of all
NULL fabric codes, including of multiple models.
If no material used then = N/A . Fabric
codes increased from 1 character to 10.
(comma separated).
Marker_Comments Text, NULL NULL Not updated by AccuMark
CADCatId Int, not NULL Index The category id used by WebPDM to
organize CAD Data. Links to CAD_Cats.
Category Varchar(100), NULL Not updated by AccuMark
NULL
SubCat Varchar(100), NULL Not updated by AccuMark
NULL
SubCatType Varchar(100), NULL Not updated by AccuMark
NULL
Class Varchar(100), NULL Not updated by AccuMark
NULL
UserDefined1 Varchar(100), NULL Not updated by AccuMark
NULL
UserDefined2 Varchar(100), NULL Not updated by AccuMark
NULL
UserDefined3 Varchar(100), NULL Not updated by AccuMark
NULL
UserDefined4 Varchar(100), NULL Not updated by AccuMark
NULL
UserDefined5 Varchar(100), NULL Not updated by AccuMark
NULL
PreferMetric Int, NULL 0 Not updated by AccuMark
IsCosting Int, NULL 0 Not updated by AccuMark
IsApproved Int, NULL 0 Not updated by AccuMark
Sizes Varchar(8000), Size-quantity [ 10(1) = 1 size 10 ] 8(10,
NULL 10(2), 12(2), 14(1). ORDERED size name
(if a size code table is used it is the
ordered size as specified in size code
table not the actual size). Support for 30
character alpha size names.
EfficiencyType Int, NULL Indicates if marker stored with total or
current efficiency.
LastCADRefresh Datetime, NULL Not updated by AccuMark
NULL
PlotFileLocation Varchar(510), NULL Not updated by AccuMark
NULL
NotchFile Varchar(100), P-Notch parameter table used when
NULL marker was ordered
AnnotationFile Varchar(100), Annotation table used when marker was
NULL ordered
StorageType Int, NULL 1= This indicates the source type of the
userroot, storage area. (usually if = 1 then pull from

Page 16 of 23
 2= SQL accumark)
storage
area or
subfolder
mMarker_Width Float, NULL Width of marker in Metric
mMarker_Length Float, NULL Length of marker in Metric
mMarker_Total_Perim Float, NULL Total perimeter length of all placed pieces
in the marker in Metric
mMarker_Total_Area Float, NULL Total area of all [placed] pieces in the
marker in Metric
Yield_per_Bundle Float, NULL ?
Yield_per_Dozen Float, NULL Not updated by AccuMark
mYield_per_Bundle Float, NULL Not updated by AccuMark
mYield_per_Dozen Float, NULL Not updated by AccuMark
LayLimits* Varchar(100), Name of lay limits table used with the
NULL marker
BlockBuffer* Varchar(100), Name of block buffer table used with the
NULL marker
Matching* Varchar(100), Name of matching table used with the
NULL marker
Fabric Cost* float Fabric Cost
Fabric Weight* float Fabric Weight
CostPerBundle* float Cost / Bundle
CostPerDozen* float Cost / Dozen
Marker_Cost* float Cost / Marker
Marker_Weight* Float Marker Weight
NetWeightBundle* float Net Weight / Bundle
GossWeightBundle* float Gross Weight / Bundle

*These items added in V9

TABLE: Cad_MK_Model
Updated when any model is updated. Linked to Cad_Marker_Details or Cad_Model_Details.
There is one row for each model in a marker.

Variable Name Type, Default Values Definition

Value
Marker_Code Int, not NULL, index Links to Cad_Marker_Details(primary key)
0
Model_Code Int, not NULL, Links to Cad_Model_Details(primary key)
0
Model_Name Varchar(100), Name of this model. Support maximum of
not NULL 50 character data item name
Last_Updated Datetime, NULL
NULL
IsActive Int, NULL -1 = Indicates whether the marker can be used
exists in new
0 WebPDM Folders.
=deleted
IsLinked Int, NULL 0
ClassifierId Int, NULL NULL

Page 17 of 23
SystemId Int, NULL NULL
Model_Description Varchar(255), NULL
NULL
Model_nMaterials Int, NULL NULL
Model_nPieces Int, NULL NULL
Model_nSizes Int, NULL NULL
Model_Image_SN Int, NULL NULL Not updated by AccuMark
Model_Materials Varchar(1000), This Model_Materials column is being set
NULL to the fabric code associated with the
model in the marker. Fabric codes
increased from 1 character to 10.
(comma separated)
Model_Comments Text, NULL NULL Not updated by AccuMark
OptionName* Varchar(100), Model option name for this model, NULL if
NULL no model options
SizeCode* Varchar(100), Size code table name used for this model,
NULL NULL if no sizecode used

*These items added in V9

TABLE: Cad_MK_Piece
Updated when any piece is updated of a marker and the marker is reprocessed, saved, auto-
updated, etc. Linked to Cad_Marker_Details or Cad_Piece_Details There is one row for each
size of each piece in the marker.

Variable Name Type Values Description

Marker_Code Int, not NULL, index Links to Cad_Marker_Details (primary
0 key)
Piece_Code Int, not NULL Comes from Last_Key_Used (primary key)
Piece_Name Varchar(100), Name of a piece in marker. Support
not NULL maximum of 50 character data item name
Last_Upadated Datetime, NULL
NULL
IsActive Int, NULL -1 = Indicates whether the marker can be used
exists in new
0 WebPDM Folders.
=deleted
IsLinked Int, NULL
ClassifierId Int, NULL
SystemId Int, NULL
Model_Code Int, NULL
Piece_Description Varchar(510),
NULL
Piece_Category Varchar(510),
NULL
Piece_Message Varchar(510), NULL Not updated by AccuMark
NULL
Piece_Standard Int, NULL 0 Not updated by AccuMark
Piece_XVariance Float, NULL NULL Not updated by AccuMark
Piece_YVariance Float, NULL NULL Not updated by AccuMark
Piece_IsMirror Int, NULL, 0 0=no,
-1=yes

Page 18 of 23
Piece_Area Float, NULL Area of this piece
Piece_Perimeter Float, NULL Perimeter of this piece
Piece_DieAll Float, NULL NULL Not updated by AccuMark
Piece_SpecBlkX Float, NULL NULL Not updated by AccuMark
Piece_SpecBlkY Float, NULL NULL Not updated by AccuMark
Piece_BlockX Float, NULL NULL Not updated by AccuMark
Piece_BlockY Float, NULL NULL Not updated by AccuMark
Piece_Fold_State Int, NULL NULL Not updated by AccuMark
Piece_nUnflipped Int, NULL Quantity of this piece in its original position
Piece_nOpposite Int, NULL Quantity of this piece in Flip X, Flip Y, or
Flip X,Y positions
Piece_nPlaced Int, NULL Quantity of this piece placed in the marker
Piece_Size Varchar(64), Each Size of this piece in marker (not in
not NULL Toolkit?) ORIGINAL size name (if a size
code table is used it is the actual size as
specified in size code table not the ordered
size). Support maximum of 30 character
alpha size name
Comments Text, NULL NULL Not updated by AccuMark
Piece_nUnplaced Int, NULL Quantity of this piece unplaced
XVarianceFlag Int, NULL Not updated by AccuMark
YVarianceFlag Int, NULL Not updated by AccuMark
XPriBlockFlag Int, NULL Not updated by AccuMark
YPriBlockFlag Int, NULL Not updated by AccuMark
XSecBlockFlag Int, NULL Not updated by AccuMark
YSecBlockFlag Int, NULL Not updated by AccuMark
mPiece_Area Float, NULL Area of this piece in metric
mPiece_Perimeter Float, NULL Perimeter of this piece in metric

Cad_MK_Piece, Cad_MK_Size tables have new columns Piece_Name and Size_Name

TABLE: Cad_MK_Size
Updated when any marker is updated. Linked to Cad_Marker_Details or Cad_Model_Details
There is one row for each size in a marker.

Variable Type, Values Description

Name Default
Value
Size_Code Int, not NULL List of all sizes (starts counting at 1 ) (primary
key)
Size_Name Varchar(60), Name of a size. ORDERED size name (if a
NULL size code table is used it is the ordered size as
specified in size code table not the actual size).
Support maximum of 30 character alpha size
name
Quantity Int, NULL Quantity of this size in the marker
Marker_Code Int, NULL, 0 Index Link to Cad_Marker_Details
Model_Code Int, NULL, 0 index Link to Cad_MK_Model

Page 19 of 23
TABLE: Cad_Model_Details
Updated when any model is updated. – information for a model. There is one row for each
model in a storage area or subfolder.
Variable Name Type Values Description
Model_Code Int, not NULL, 0 Matches Code in AccuMark Paths table
(primary key)
Model_Name Varchar(100), Name of model. Support maximum of 50
not NULL character data item name
Last_Updated Datetime, NULL Date & time model was last updated (Stored).
IsActive Int, NULL, -1 -1 = exists Indicates whether the marker can be used in
0 =deleted new
WebPDM Folders.
IsLinked Int, NULL -1
ClassifierId Int, not NULL 0
SystemId Int, not NULL 1
Marker_Code Int, NULL The category id used by WebPDM to organize
CAD Data.
Model_Description Varchar(255), Description/comments as stored in model
NULL
Model_CrOpId Varchar(50), Name of user who created this data item
NULL
Model_Create Datetime, NULL Date & time model was originally created
(stored)
Model_RevOp1 Varchar(50), Name of user who modified this data item just
NULL recently
Model_Rev1 Datetime, NULL Date & time model was last stored (initially
Last_updated, then becomes Previously
updated)
Model_RevOp2 Varchar(50), Name of user who Last modified (prior to
NULL Rev1)
Model_Rev2 Datetime, NULL Last time this item modified (prior to Rev1)
Model_GRTable Varchar(50), NULL Not updated by AccuMark
NULL
Model_MTMFile Varchar(50), NULL Not updated by AccuMark
NULL
Model_SAName Varchar(50), NULL Not updated by AccuMark
NULL
Model_SYNTable Varchar(50), NULL Not updated by AccuMark
NULL
Model_ HPTable Varchar(50), NULL Not updated by AccuMark
NULL
Model_SampleSize Varchar(60), Model sample size (If multiple sample sizes are
NULL in the model then field is set to ‘Vary By
Pieces’ (if a size code table is used, it is the
actual size or the ordered size as specified in
size code table). Support maximum of 30
character size name
Model_nMaterials Int, NULL 0, 1-n Number of fabric codes for all that are ordered
Model_nPieces Int, NULL Number of different pieces in the model (rows)
including comment pieces.
Model_nSizes Int, NULL 1-n, or “Vary Total number of unique sizes for this model
by piece”
Model_Image_SN Int, NULL NULL Not updated by AccuMark
Model_Image_Name Varchar(255), Server and storage area name [ + subfolder/s ]

Page 20 of 23
 NULL
Model_Comments Text, NULL NULL Not updated by AccuMark
PreferMetric Int, NULL 0 Not updated by AccuMark
UserDefined1 Varchar(50), NULL Not updated by AccuMark
NULL
UserDefined2 Varchar(50), NULL Not updated by AccuMark
NULL
UserDefined3 Varchar(50), NULL Not updated by AccuMark
NULL
UserDefined4 Varchar(50), NULL Not updated by AccuMark
NULL
UserDefined5 Varchar(50), NULL Not updated by AccuMark
NULL
Total_Area Float, NULL NULL Not updated by AccuMark
LastCADRefresh Datetime, NULL NULL Not updated by AccuMark
PlotFileLocation Varchar(255), NULL Not in use
NULL Not in use
NotchFile Varchar(50), NULL Not updated by AccuMark
NULL
AnnotationFile Varchar(50), NULL Not updated by AccuMark
NULL
StorageType Int, NULL 2 1=userroot, 2=sql

TABLE: Cad_Piece_Details
Updated when any piece that belongs to a model is updated. One row for each piece for each
fabric type in a model (for each model in a SQL storage area or subfolder).
Variable Name Type, Default Values Description
Value
Piece_Code Int, not NULL, Piece id (primary key)
0
Piece_Name Varchar(100), Name of a piece. Support
not NULL maximum of 50 character data
item name
Last_Updated Datetime, Date & time piece was last stored
NULL
isActive Int, NULL, -1 -1 = exists Indicates whether the marker can
0 = deleted be used in new WebPDM Folders.
IsLinked Int, NULL 0
ClassifierId Int, NULL 0
SystemId Int, NULL 1
Model_Code Int, NULL, 0 index Links to Cad_Model_Details
Material_Code Int , NULL Not used by WebPDM
Piece_Description Varchar(510), Description for piece
NULL
Piece_Category Varchar(510),
NULL
RuleTableName** Varchar(64), Name of rule table used with this
NULL piece
Piece_CrOpId Varchar(100), Name of user who created this
NULL piece
Piece_Create Datetime, Date this piece was created
NULL
Piece_RevOp1 Varchar(100), Name of user who recently
NULL updated this piece

Page 21 of 23
Piece_Rev1 Datetime, Date this piece was recently
NULL modified
Piece_RevOp2 Varchar(100), Name of user who modified this
NULL piece the last time (before rev1)
Piece_Rev2 Datetime, Date this piece was last modified
NULL (before rev1)
Piece_Message Varchar(510), NULL Not updated by AccuMark
NULL
Piece_HPTable Varchar(100), NULL Not updated by AccuMark
NULL
Piece_Bias Int, NULL 0 Not updated by AccuMark
Piece_Flip Int, NULL 0 Not updated by AccuMark
Piece_Nap Int, NULL 0 Not updated by AccuMark
Piece_Ign_Splice Int, NULL 0 Not updated by AccuMark
Piece_Standard Int, NULL NULL Not updated by AccuMark
Piece_Buffering Int, NULL NULL Not updated by AccuMark
Piece_nSplits Int, NULL Number of times piece is allowed
to split as specified in the model
Piece_Tilt_CW Float, NULL NULL Not updated by AccuMark
Piece_DieBlock Float, NULL NULL Not updated by AccuMark
Piece_Pri_XBlock Float, NULL NULL Not updated by AccuMark
Piece_PriXBlkType Int, NULL NULL Not updated by AccuMark
Piece_Pri_YBlock Float, NULL NULL Not updated by AccuMark
Piece_Pri_YBlkType Int, NULL NULL Not updated by AccuMark
Piece_Sec_XBlock Float, NULL NULL Not updated by AccuMark
Piece_Sec_XBlkType Int, NULL NULL Not updated by AccuMark
Piece_Sec_YBlock Float, NULL NULL Not updated by AccuMark
Piece_Sec_YBlkType Int, NULL NULL Not updated by AccuMark
Piece_XVariance Float, NULL NULL Not updated by AccuMark
Piece_XVar_Type Int, NULL NULL Not updated by AccuMark
Piece_YVariance Float, NULL NULL Not updated by AccuMark
Piece_YVar_Type Int, NULL NULL Not updated by AccuMark
Piece_nUnflipped Int, NULL Quantity of piece in its unflipped
(original) position from model as
specified in the model
Piece_nOpposite Int, NULL Quantity of piece in its X-flipped
position from model as specified
in the model
Piece_nFlipY Int, NULL Quantity of piece in its Y-flipped
position from model as specified
in the model
Piece_nFlipXY Int, NULL Quantity of piece in its X,Y-flipped
position from model as specified
in the model
Piece_IsMirror Int, NULL, 0 0=no, - Indicates if piece is mirrored
1=yes
Piece_Area Float, NULL Area of piece in Imperial
Piece_Perimeter Float, NULL Perimeter of piece in Imperial
Piece_PreRotation Float, NULL NULL Not updated by AccuMark
Piece_Image_SN Int, NULL Links to PPFImages
Piece_Image_Name Varchar(100), 1 char or N/A Fabric Code. If multiple fabric
NULL types on one line in model, or
piece listed multiple times for
each fabric, will be the same in

Page 22 of 23
 the data table. Fabric codes
increased from 1 character to 10.
(comma separated)
Piece_Comments Text, NULL NULL Not updated by AccuMark
UserDefined1 Varchar(100), NULL Not updated by AccuMark
NULL
UserDefined2 Varchar(100), NULL Not updated by AccuMark
NULL
UserDefined3 Varchar(100), NULL Not updated by AccuMark
NULL
UserDefined4 Varchar(100), NULL NULL Not updated by AccuMark
NULL
UserDefined5 Varchar(100), NULL Not updated by AccuMark
NULL
Piece_Size Varchar(64), NULL
NULL
Piece_Tilt_CCW Float, NULL NULL Not updated by AccuMark
Piece_CW_TYPE Int, NULL NULL Not updated by AccuMark
Piece_CCW_TYPE Int, NULL NULL Not updated by AccuMark
Piece_PreRotationType Int, NULL NULL Not updated by AccuMark
Piece_Position Int, not NULL, This is the row position within the
0starts at 1? Model (listed order)
mPiece_Area Float, NULL Area of piece in metric
mPiece_Perimeter Float, NULL Perimeter of piece in metric
PieceXVariance Float, NULL Shrink and Stretch information for
model in X
Piece_XVar_Type Int, NULL Indicates if shrink or stretch
PieceYVariance Float, NULL Shrink and Stretch information for
model in Y
Piece_YVar_Type Int, NULL Indicates if shrink or stretch
Piece_Size Varchar(64), The sizes of the pieces with each
not NULL of the sizes in the model being
separated by commas for multiple
sizes

** updated since 8.4.1 hotfix

Additional Tables in RDBMS – not used by AccuMark?

Cad_SystemIds
DataTableSettings
gtAccuMarkTypes
SystemSettings

In V10 and later updates made:

Cad_Piece_Details table now contains Shrink / Stretch information from models -
Piece_XVariance, Piece_XVar_Type, Piece_YVariance, Piece_YVar_Type
Piece Size information - Piece_Size

Page 23 of 23