{"id":8830,"date":"2023-07-13T11:44:30","date_gmt":"2023-07-13T10:44:30","guid":{"rendered":"https:\/\/www.threesl.com\/blog\/?p=8830"},"modified":"2023-11-01T11:59:07","modified_gmt":"2023-11-01T11:59:07","slug":"july-newsletter-2023","status":"publish","type":"post","link":"https:\/\/www.threesl.com\/blog\/july-newsletter-2023\/","title":{"rendered":"July Newsletter 2023"},"content":{"rendered":"

Welcome to the July 2023<\/strong> newsletter from 3SL!<\/p>\n

This newsletter contains a mixture of news and technical information about us, and our requirements management and systems engineering tool “Cradle”. We would especially like to welcome everyone who has purchased Cradle in the past month and those who are currently evaluating Cradle for their projects and processes.<\/p>\n

We hope that 3SL and Cradle can deliver real and measurable benefits that help you to improve the information flow within, the quality and timeliness of, and the traceability, compliance and governance for, all of your current and future projects.<\/p>\n

If you have any questions about your use of Cradle, please do not hesitate to contact 3SL Support<\/strong><\/a>.<\/p>\n

PDUIDs<\/h2>\n

When we work with information, we need a way to distinguish each piece of information from all other pieces of information so we can be sure we have found what we were searching for. We do this by marking each piece of information in a unique way.<\/p>\n

For information in databases, the markings are unique values called keys<\/em><\/strong> or identities<\/em><\/strong>. A piece of information can have multiple identities, each for a different purpose. For example, although a company\u2019s payroll system is likely to identify each person by a unique Employee ID, each person\u2019s details will also include their governmental tax ID (such as a National Insurance number<\/a>, a Unique Taxpayer Reference<\/a>, a Sozialversicherungsnummer or a Social Security Number<\/a>). This tax ID will also be unique and so could also be used as an identity for that person\u2019s information.<\/p>\n

Cradle has two forms of identity, item identities<\/em><\/strong> and Project Database Unique IDs<\/em><\/strong> (PDUIDs).<\/p>\n

We will publish a series of blog posts about PDUIDs, describing what they are, how to view them, how to use them, and how PDUIDs can be managed when you import information into your databases.<\/p>\n

Item Identities<\/h3>\n

There are several basic item types in Cradle. Each basic item type uses a different combination of attributes to create a unique Item ID<\/strong><\/em> for items of that type:<\/p>\n

\"Item<\/p>\n

An item is identified by this Item ID<\/strong><\/em> and a unique Instance ID<\/strong><\/em>, typically a version and draft.<\/p>\n

PDUID Structure<\/p>\n

Project Database Unique IDs<\/strong><\/em> (PDUIDs) are a single, consistent, numbering system for all database information. Each PDUID is a 26 character string that contains a Database ID<\/strong><\/em> to identify a Cradle system, a Project ID<\/strong><\/em> to identify a project database and a Unique ID<\/strong><\/em>:<\/p>\n

\"Cradle
Structure of PDUIDs<\/figcaption><\/figure>\n

A PDUID references all instances of an item. Therefore the combination of a PDUID and an Instance ID<\/strong><\/em> (a version and draft) will identify a specific item. So, this is an alternative to the Item ID and Instance ID and has the advantage of being consistent and a single numbering sequence for all types of item.<\/p>\n

Further Details<\/h3>\n

For further details in this part 1 of a description of PDUIDs, please see the full blog entry here<\/a>.<\/p>\n

Remote Databases<\/h2>\n

A Cradle system can contain any number of databases. For the best performance, we recommend that databases are stored on disks connected to the machine that runs your Cradle Database Server (CDS)<\/a>. But, this may not be possible.<\/p>\n

For example:<\/p>\n