Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

ProWrite has 3 levels of unique identifiers to help you keep your documents organized. These are:

  • CUID
  • DUID
  • GUID (AKA UUIDs).

CUID


These are your Customers Unique IDentifier. The field(s) that are used outside your company. This is a new umbrella term for the existing class of identifier that was previously the primary user facing representation of uniqueness.

So for example-

  • PQR #
  • WPS # when combined with WPS Rev #
  • WPQ# when combined with WPS #, WPS # Rev, Welder Identifier
  • Welder ID

This new structure allows duplicate CUIDS so something like a tracking number that your customer "John Smith Co" demands be on "WPS 1" while "Pyramid Co." demands a different value be on "WPS 1" can be accommodated. Those 2 companies requirements may directly conflict or "WPS 1" may have already been in use in its present form and should be kept in that exact state permanently but the new company wants some change that, though not impacting on qualification, is an alteration and they still require the same WPS number and revision as was originally submitted to them in their documentation.

DUID


These are your human readable Dataset Unique IDentifiers. A system generated human usable unique identifier that does not appear on the printed documents, welders or reports. It follows the format-

<Entity Type>-<Date in YYYYMMDD>-<incrementing #>

so for example-

Welder-20151210-1
WPS-20151210-2

This field will be unique for each PQR, WPS, WPQ and Welder in your database but will not be unique across all ProWrite databases in the world.

GUID


Globally Unique IDentifier
A system generated near guaranteed globally unique value that represents 1 PQR, WPS, WPQ or Welder and only 1 in the world. Be aware for those using a ProWrite Offline DB or an on site MS SQL Server copying the database manually does, of course, duplicate the entity GUIDs. That's one of the limitations of a non-hosted solution that can't be easily overcome.

Typical GUID/UUID 36 character format like below

8EAB0AF5-D323-4ADF-99F1-11E842E8CC18



  • No labels