PDM-UG: Security classification
From WikiSTEP
This page belongs to the PDM Usage Guide.
A security classification is the level of confidentiality that is required in order to protect product data against unauthorized usage.
Contents |
The Instance Model: EXPRESS entities and attributes
Diagram 61: Part Master with Context Information Instance Diagram
Security classification
The security_classification entity defines the level of confidentiality that is required for the purpose of product data protection.
Attributes
- The name attribute is the label by which the security_classification is known.
- The purpose gives an informal description of the intent of the security_classification.
- The security_level defines the security_classification_level that specifies the required degree of security.
| ENTITY security_classification | Attribute Population | Remarks |
| name | type : label = string | |
| purpose | type : text = string | |
| security_level | type : entity = security_classification_level |
===Preprocessor Recommendations=== None specified.
===Postprocessor Recommendations=== None specified.
===Related Entities=== Date/time and person/organization can be associated with a security_classification by using the entities applied_date_assignment, applied_date_and_time_assignment, applied_organization_assignment and applied_person_and_organization_assignment.
Security classification level
The security_classification_level entity defines a category of security required for product data protection.
Attributes
- The name is the label by which the security_classification_level is known.
| ENTITY security_classification_level | Attribute Population | Remarks |
| name | type: label = string |
===Preprocessor Recommendations=== None specified.
===Postprocessor Recommendations=== None specified.
===Related Entities=== None specified.
Applied security classification assignment
The applied_security_classification_assignment entity is a type of security_classification_assignment that assigns a security_classification to a security_classification_item.
Attributes
- The assigned_security_classification gives the security_classification which is to be associated with product data.
- Items is the set of items to which the security_classification is assigned. A security classification can be assigned to multiple items with one instance of assigned_security_classification.
| ENTITY applied_security_classification_assignment | Attribute Population | Remarks |
| assigned_security_classification | type : entity = security_classification | |
| items | type : entity = security_classification_item | SET [1:?] |
===Preprocessor Recommendations=== None specified.
===Postprocessor Recommendations=== None specified.
===Related Entities=== an assigned_security_classification relates a security_classification to a set to be classified items. The PDM Schema supports the assignment of security classifications to instances of assembly_component_usage, document_file, product_definition and product_definition_formation.
The table below shows the entity types that can be used in the set of items of security classification assignment and the associated semantics.
| entity type | semantics of using applied_security_classification with instances of this entity. |
| assembly_component_usage | classifies the component inclusion in an assembly. |
| document_file | classifies a document file |
| product_definition | classifies the information related to a product_definition, where a product_definition can either model a document representation or a part view. |
| product_definition_formation | classifies the information related to a product_definition_formation, where a product_definition_formation can either model a document version or a part version. |
The Instance Model: STEP exchange file format (ISO10303 Part 21 syntax)
ISO-10303-21;
HEADER;
FILE_DESCRIPTION((''),'2;1');
FILE_NAME('', '20.08.1999, 13:19:42', (''), (''), '', '', '');
FILE_SCHEMA(('PDM_SCHEMA {1.2}'));
ENDSEC;
DATA;
#10 = PRODUCT_CATEGORY_RELATIONSHIP('', $, #20, #30);
#20 = PRODUCT_RELATED_PRODUCT_CATEGORY('Part', '', (#40));
#30 = PRODUCT_RELATED_PRODUCT_CATEGORY('Assembly', $, (#40));
#40 = PRODUCT('as', 'assembly', '', (#60));
#50 = PRODUCT_RELATED_PRODUCT_CATEGORY('part', '', (#40, #170));
#60 = PRODUCT_CONTEXT('', #70, '');
#70 = APPLICATION_CONTEXT('');
#80 = APPLICATION_PROTOCOL_DEFINITION('version 1.2', 'pdm_schema', 2000, #70);
#90 = PRODUCT_DEFINITION_FORMATION('1', '', #40);
#100 = PRODUCT_DEFINITION('vas', 'design view assembly', #90, #110);
#110 = PRODUCT_DEFINITION_CONTEXT('part definition', #70, 'design');
#140 = PRODUCT_CATEGORY_RELATIONSHIP('', $, #150, #160);
#150 = PRODUCT_RELATED_PRODUCT_CATEGORY('Part', '', (#170));
#160 = PRODUCT_RELATED_PRODUCT_CATEGORY('Detail', $, (#170));
#170 = PRODUCT('p', 'part', '', (#60));
#180 = PRODUCT_DEFINITION_FORMATION('1', '', #170);
#190 = PRODUCT_DEFINITION('vp', 'design view part', #180, #110);
#210 = PRODUCT_DEFINITION_CONTEXT_ASSOCIATION(#100, #230, #220);
#220 = PRODUCT_DEFINITION_CONTEXT_ROLE('part definition type', $);
#230 = PRODUCT_DEFINITION_CONTEXT('assembly definition', #70, '');
#240 = NEXT_ASSEMBLY_USAGE_OCCURRENCE('p_usage_1', 'single instance usage', '', #100, #190, $);
#250 = SECURITY_CLASSIFICATION('confidentiality', 'classify as confidental',#260);
#260 = SECURITY_CLASSIFICATION_LEVEL('confidential');
#270 = APPLIED_SECURITY_CLASSIFICATION_ASSIGNMENT(#250,(#180,#190,#240));
ENDSEC;
END-ISO-10303-21;
