SCIOT AML Basic Configuration Reference Documentation

Based on the parsing of SCIOT AML configuration files, covering all basic configurations for system infrastructure, PM project management module, and PLM product lifecycle management module.

Last updated: 2026-06-02

Table of Contents

1. System Infrastructure

• 1.1 Core Identity
• 1.2 User
• 1.3 Permission
• 1.4 TOC Access
• 1.5 Email Message

1. PM Project Management Module

• 2.1 ItemType Definition
• 2.2 Life Cycle Maps
• 2.3 Permission Matrix
• 2.4 Identity and Roles
• 2.5 RelationshipType

1. PLM Product Lifecycle Management Module

• 3.1 ItemType Definition
• 3.2 Life Cycle Maps
• 3.3 Workflow Maps
• 3.4 Permission Matrix
• 3.5 Identity and Roles
• 3.6 Sequence Configuration
• 3.7 List Values
• 3.8 Team

1. System Infrastructure

1.1 Core Identity

The system has built-in core identities that define the basic role hierarchy:

| Identity Name | Category | Description | Purpose |

|---------|------|------|------|

| World | System | Global identity, all users belong by default | Grants the most basic read permissions |

| Creator | System | Creator | Has full permissions over self-created data |

| Owner | System | Owner | Has full permissions over owned data |

| Manager | System | Manager | Has update permissions over managed data |

| Team | System | Team | Enables team-level permission control |

| Team Manager | System | Team Manager | Team Management Role (System Identity – Do Not Edit) |

| Team Member | System | Team Member | Team Member Role (System Identity – Do Not Edit) |

| Team Guest | System | Team Guest | Team Guest Role (System Identity – Do Not Edit) |

| Super User | System | Super User | Advanced Management Permissions |

| Agent Admin | System | System Administrator | Platform Administrator with Highest Privileges |

| Administrators | System | Administrators Group | Administrator Identity Group |

| File Administrators | System | File Administrator | File Management Permissions |

Key Identity ID Reference:

• Owner: System Identity (queried via action="get" select="id")
• Sciot PLM: 56A96DA9E981481688563E2D14D5D878

Recommended Default Values to Set:

• Default Data Visibility: World (discover+get)
• Default Data Creator: Creator (Full Permissions)
• Default Data Owner: Owner (Full Permissions)
• Default Data Manager: Manager (discover+get+update)
• System Administration: Agent Admin, Super User (Full Permissions)

1.2 User

ItemType: User

Core Field Definitions:

| Field Name | Type | Required | Description |

|-------|------|------|------|

| login_name | string | ✓ (keyed) | Login name, unique identifier |

| first_name | string | - | First Name |

| last_name | string | - | Last Name |

| email | string | - | Email |

| password | string | - | Password (MD5 encrypted) |

| logon_enabled | boolean | - | Login Enabled |

| default_vault | item | - | Default Vault |

| wechat_openid | string | - | WeChat OpenID |

| wechat_unionid | string | - | WeChat UnionID |

Identity Definition:

• is_alias default value: 0 (not an alias)
• classification: System or Team

1.3 Permission

Permissions consist of Access records, each granting a specific identity five types of permissions:

• can_change_access: Can modify access permissions
• can_delete: Can delete
• can_discover: Can discover (visible in search)
• can_get: Can read
• can_update: Can update

System Default Permissions (System Item):

| Identity | discover | get | update | delete | change_access |

|------|----------|-----|--------|--------|---------------|

| World | ✓ | ✓ | ✗ | ✗ | ✗ |

1.4 TOC Access

TOC (Table of Contents) controls menu visibility for each ItemType per identity.

RelationshipType: TOC Access

• category: TOC category path
• related_id → Identity
• source_id → ItemType (Data Type)

System-defined TOC categories:

• Portfolio - Project Portfolio (PM module)
• ProductEngineering/Design - Product Engineering/Design (PLM module)
• Document Center - Document Center (PLM module)
• Sourcing - Sourcing (PLM module)

1.5 Email Message

ItemType: EMail Message

Core fields:

| Field Name | Type | Description |

|-------|------|------|

| name | string (keyed) | Email template name |

| subject | string | Email subject |

| body_plain | text | Plain text body |

| body_html | text | HTML body |

| from_user | item→User | Sender |

| query_string | text | Query string (for dynamic recipients) |

| label | ml_string | Label |

2. PM Project Management Module

2.1 ItemType Definitions

#### 2.1.1 Program (Program/Plan)

Basic attributes:

• implementation_type: table
• is_versionable: 0
• TOC category: Portfolio
• Can Add: Project Management

Core fields:

| Field Name | Type | Required | Default Value | Description |

|-------|------|------|--------|------|

| name | string | ✓ (keyed) | - | Program name |

| description | text | - | - | Description |

| customer | item→Customer | - | - | Customer |

#### 2.1.2 Project

Basic Attributes:

• implementation_type: table
• is_versionable: 0
• TOC category: Portfolio
• Can Add: Project Management
• default permission: Project
• show_parameters_tab: 1

Core Fields:

| Field Name | Type | Required | Default Value | Description |

|-------|------|------|--------|------|

| project_number | integer | ✓ (keyed) | - | Project Number |

| name | string | - | - | Project Name |

| description | text | - | - | Description |

| comments | text | - | - | Remarks |

| scheduling_mode | list | ✓ | 1 | Scheduling mode (1=default mode) |

| scheduling_method | item→Method | - | Default method ID | Scheduling calculation method |

| update_method | item→Method | - | Default method ID | Update method |

| wbs_id | string | - | - | WBS identifier |

| from_template | item→Project Template | - | - | Source template |

| Date fields: | | | | |

| date_start_sched | date | - | - | Scheduled start (readonly=1) |

| date_due_sched | date | - | - | Scheduled end (readonly=1) |

| date_start_act | date | - | - | Actual start (hidden=1) |

| date_due_act | date | - | - | Actual End (hidden=1) |

| date_start_target | date | - | - | Target Start (hidden=1) |

| date_due_target | date | - | - | Target End (hidden=1) |

| 12 Phase Status Fields (percent_compl + status): | | | | |

| phase_1_percent_compl | decimal | - | - | Phase 1 Percent Complete |

| phase_1_status | string | - | - | Phase 1 Status |

| phase_2_percent_compl | decimal | - | - | Phase 2 Percent Complete |

| phase_2_status | string | - | - | Phase 2 Status |

| ... | | | | (Continues to phase_12) |

| cpi | decimal | - | - | Cost Performance Index |

| spi | decimal | - | - | Schedule Performance Index |

| earned_value | decimal | - | - | Earned Value |

| actual_cost | decimal | - | - | Actual Cost |

| budget | decimal | - | - | Budget |

Important Notes:

• scheduling_mode has a default value of 1 and is a required field
• scheduling_method and update_method have default method IDs
• Schedule date fields are read-only (calculated by the scheduling engine)
• Projects have 12 predefined phases, each with percent complete and status fields

#### 2.1.3 Project Template

Basic Attributes:

• implementation_type: table
• is_versionable: 0
• TOC category: Portfolio
• Can Add: Project Management

Core Fields:

| Field Name | Type | Required | Default Value | Description |

|-------|------|------|--------|------|

| name | string | ✓ (keyed) | "Template" | Template Name |

| wbs_id | string | - | - | WBS Identifier |

| description | text | - | - | Description |

#### 2.1.4 WBS Element

Basic Attributes:

• implementation_type: table
• is_versionable: 0
• Can Add: Project Management

Core Fields:

| Field Name | Type | Required | Default Value | Description |

|-------|------|------|--------|------|

| name | string | ✓ | - | Name |

| proj_num | integer | - | - | Associated Project Number |

| wbs_index | integer | - | - | WBS Index |

| is_top | boolean | - | - | Is Top-Level Element |

| deliv_required | boolean | - | 0 | Deliverable Required |

| Rollup Fields: | | | | |

| cpi | decimal | - | - | Cost Performance Index Rollup |

| spi | decimal | - | - | Schedule Performance Index Rollup |

| earned_value | decimal | - | - | Earned Value Rollup |

| planned_value | decimal | - | - | Planned Value Summary |

| percent_compl | decimal | - | - | Percent Complete Summary |

| duration | decimal | - | - | Duration Summary |

| work_est | decimal | - | - | Work Estimate Summary |

| status | string | - | - | Status Summary |

#### 2.1.5 Activity2 (Project Activity) ⭐

Basic Attributes:

• implementation_type: table
• is_versionable: 0
• instance_data: ACTIVITY2
• Can Add: Project Management

Core Fields:

| Field Name | Type | Required | Default | Description |

|-------|------|------|--------|------|

| name | string | ✓ | - | Activity Name |

| proj_index | integer | - | - | Index within Project |

| proj_num | integer | - | - | Associated Project Number |

| expected_duration | decimal | - | - | Expected Duration |

| work_est | decimal | - | - | Work Estimate |

| percent_compl | decimal | - | 0 | Percent Complete |

| is_milestone | boolean | - | - | Is Milestone |

| is_required | boolean | - | - | Is Required |

| is_critical | boolean | - | - | Is Critical Path |

| ES/EF/LS/LF Network Schedule Fields (Read-only): | | | | |

| date_es | date | - | - | Earliest Start (readonly=1) |

| date_ef | date | - | - | Earliest Finish (readonly=1) |

| date_ls | date | - | - | Latest Start (readonly=1) |

| date_lf | date | - | - | Latest Finish (readonly=1) |

| Scheduling Dates: | | | | |

| date_start_sched | date | - | - | Scheduled Start |

| date_due_sched | date | - | - | Scheduled Finish |

| date_start_act | date | - | - | Actual Start |

| date_due_act | date | - | - | Actual Finish |

| date_start_target | date | - | - | Target Start |

| date_due_target | date | - | - | Target Finish |

| date_due_original | date | - | - | Original Due (readonly=1) |

| date_activated | date | - | - | Activation Time (readonly=1) |

| Deliverables: | | | | |

| deliv_required | boolean | - | 0 | Deliverable Required |

| deliv_type | string | - | - | Deliverable Type |

| Responsible Parties: | | | | |

| lead_role | string | - | - | Lead Role |

| signoff_required | boolean | - | - | Sign-off Required |

| managed_by_id | item→Identity | - | - | Managed By Identity |

| owned_by_id | item→Identity | - | - | Owner Identity (readonly) |

| Earned Value Management: | | | | |

| cpi | decimal | - | - | Cost Performance Index (prec=6, scale=4) |

| spi | decimal | - | - | Schedule Performance Index (prec=6, scale=4) |

| earned_value | decimal | - | - | Earned Value (prec=19, scale=4) |

| planned_value | decimal | - | - | Planned Value (prec=19, scale=4) |

| actual_work | decimal | - | - | Actual Work (prec=5, scale=2) |

| status | string | - | - | Status |

| Rollup Fields: | | | | |

| rollup_work | decimal | - | - | Rollup Work |

| rollup_actual_work | decimal | - | - | Rollup Actual Work |

| rollup_percent_compl | decimal | - | - | Rollup Percent Complete |

| rollup_planned_value | decimal | - | - | Rollup Planned Value |

| rollup_earned_value | decimal | - | - | Rollup Earned Value |

Important Notes:

• percent_compl defaults to 0
• deliv_required defaults to 0
• ES/EF/LS/LF fields are read-only, calculated by the scheduling engine
• CPI/SPI precision: prec=6, scale=4
• Earned value field precision: prec=19, scale=4
• Activities support roll-up calculations, allowing data aggregation from sub-activities.

#### 2.1.6 Deliverable

Basic attributes:

• implementation_type: polymorphic
• is_versionable: 1
• Morphs to the Document type.
• Uses the Default lifecycle.

Core fields:

• Inherits all fields from Document.
• Includes additional fields specific to deliverables.

#### 2.1.7 Project Task

Basic definition of a project task, used in conjunction with Activity2.

2.2 Life Cycle Maps

#### 2.2.1 Project Lifecycle

``

Pending ──→ Active ──→ Closed

│ │

└──→ Cancelled ←──┘

↑ │

└─────────┘ (rollback allowed)

`

State Details:

| State | item_behavior | set_not_lockable | Description |

|------|---------------|------------------|------|

| Pending | float | 0 | Initial state, editable. |

| Active | float | 0 | In execution. |

| Cancelled | float | 1 | Cancelled, cannot be locked. |

| Closed | float | 1 | Closed, cannot be locked. |

Transition Rules:

| Transition | Role | Description |

|------|------|------|

| Pending → Active | Owner | Project owner activates, with email notification to Super User. |

| Pending → Cancelled | Owner | Can be cancelled. |

| Active → Closed | Owner | Closes the project. |

| Active → Cancelled | Owner | Cancels an ongoing project. |

| Cancelled → Pending | Owner | Can be rolled back to Pending |

| Closed → Pending | Owner | Can be rolled back to Pending |

#### 2.2.2 Project Template Lifecycle

`

Pending ⇄ Approved (Bidirectional)

`

| Transition | Role | Description |

|------|------|------|

| Pending → Approved | Project Management | Template approval, with email notification |

| Approved → Pending | Project Management | Can be rolled back |

#### 2.2.3 Activity2 Lifecycle

`

Pending ──→ Active ──→ Complete

`

State Details:

| State | item_behavior | Description |

|------|---------------|------|

| Pending | float | Initial state |

| Active | float | In progress |

| Complete | float | Completed |

Transition Rules:

| Transition | Role | Method Callback | Description |

|------|------|---------|------|

| Pending → Active | World | pre: Project_promoteActivity2Assgnmts, post: sendEmailToA2Assignee | Activate activity, promote assignments |

| Pending → Complete | World | post: onCompleteActivity | Complete directly from Pending |

| Active → Complete | World | post: onCompleteActivity | Complete activity |

Important Note:

• All transition roles for Activity2 are World, meaning anyone can advance it.
• Activating the activity triggers: promotion assignment + email notification to the assignee.
• Completing the activity triggers the onCompleteActivity method.

#### 2.2.4 WBS Element Lifecycle

`

Active (single state, no transitions)

`

WBS Element has only one state, Active, with no transition definitions. This means the WBS element is active upon creation and requires no approval process.

2.3 Permission Matrix

#### 2.3.1 Project Permissions

| Role | discover | get | update | delete | change_access |

|------|----------|-----|--------|--------|---------------|

| Administrators | ✓ | ✓ | ✓ | ✓ | ✓ |

| Agent Admin | ✓ | ✓ | ✓ | ✓ | ✓ |

| Project Management | ✓ | ✓ | ✓ | ✓ | ✓ |

| Owner | ✓ | ✓ | ✓ | ✓ | ✓ |

| Manager | ✓ | ✓ | ✓ | ✗ | ✗ |

| World | ✓ | ✓ | ✗ | ✗ | ✗ |

Key Conclusions:

• Administrators, Agent Admin, Project Management, and Owner have full permissions.
• Managers can view and update but cannot delete.
• World (everyone) can only view.

2.4 Identities and Roles

#### 2.4.1 Project Management Identity

Members:

• Agent Admin
• Super User

Purpose:

• Holds the 'Can Add' permission for Project and Project Template.
• Project Template Lifecycle Approval Roles
• Project Permissions Full Control Role

2.5 Relationship Types (RelationshipType)

3. PLM Product Lifecycle Management Module

3.1 ItemType Definition

#### 3.1.1 Part

Basic Attributes:

• implementation_type: table
• instance_data: PART
• is_versionable: 1 (Version Managed)
• manual_versioning: 0 (Auto Version)
• TOC category: ProductEngineering/Design
• Can Add: All Employees
• default permission: New Part
• history_template: Default
• default_page_size: 25

Class Structure (class_structure):

`

Part

├── Component

├── Assembly

├── Material

├── Software

└── Variant

`

Core Fields:

| Field Name | Type | Required | Default Value | Description |

|-------|------|------|--------|------|

| item_number | string | ✓ (keyed) | - | Part Number |

| name | string | - | - | Name |

| description | string | - | - | Description (stored_length=256) |

| cost | decimal | - | - | Cost (prec=19, scale=4) |

| cost_basis | list→Goal Basis | - | - | Cost Basis |

| external_id | string | - | - | External ID (stored_length=256, indexed=1) |

| external_owner | string | - | - | External Owner (stored_length=128) |

| allow_team_change_logic | boolean | - | 1 | Allow Team Change Logic (hidden=1) |

| make_buy | list→Make Buy | - | - | Make/Buy |

| unit | list→Units | - | - | Unit |

| state | list→States | - | - | State |

| product_phase | list→Product Phases | - | - | Product Phase |

| drawing_size | list→Drawing Sizes | - | - | Drawing Size |

| specification_type | list→Specification Types | - | - | Specification Type |

| authoring_tool | list→Authoring Tools | - | - | Authoring Tool |

| classification | string | - | - | Classification |

Important Note:

• Part is the most core data type in PLM, supporting versioning.
• allow_team_change_logic default value is 1.
• Has a complete BOM structure relationship.
• Has associations with CAD and Document.

#### 3.1.2 Document

Basic Attributes:

• implementation_type: table
• instance_data: DOCUMENT
• is_versionable: 1 (Version Managed)
• manual_versioning: 0 (Auto Versioning)
• TOC category: Document Center
• Can Add: World (Anyone can create)
• default permission: New Document
• history_template: Default
• default_page_size: 25

Class Structure (class_structure):

`

Document

├── Drawing

├── CAD Model

├── Specification

├── Software

├── Miscellaneous

├── Product

├── Project

├── General

├── Email

├── Process

└── Ad-hoc

`

Core Fields:

| Field Name | Type | Required | Default | Description |

|-------|------|------|--------|------|

| item_number | string | ✓ (keyed) | - | Document Number |

| name | string | - | - | Name |

| description | string | - | - | Description (stored_length=128) |

| authoring_tool_version | string | - | - | Authoring Tool Version (stored_length=32) |

| drawing_size | list→Drawing Sizes | - | - | Drawing Size (Drawing class only) |

| allow_team_change_logic | boolean | - | 1 | Allow Team Change (hidden=1) |

| authoring_tool | list→Authoring Tools | - | - | Authoring Tool |

| specification_type | list→Specification Types | - | - | Specification Type |

| state | list→States | - | - | State |

| external_id | string | - | - | External ID |

| classification | string | - | - | Classification |

Important Note:

• The 'Can Add' permission for Document is set to World, meaning anyone can create documents.
• Has rich file attachment relationships (Document File).
• Supports filtering by multiple file types.

#### 3.1.3 CAD (CAD Document)

Basic Properties:

• implementation_type: table
• instance_data: CAD
• is_versionable: 1 (Version-controlled)
• manual_versioning: 1 (Manual versioning)
• TOC category: Document Center
• Can Add: (Controlled via permissions)
• default permission: New CAD
• history_template: Default
• default_page_size: 50

Class Structure (class_structure):

`

CAD

├── Mechanical

│ ├── Part

│ ├── Assembly

│ ├── Drawing

│ └── Simulation

└── Electronic

├── Design

├── Assembly

├── Fabrication

├── Logical

├── Manufacturing

├── Panelization

└── Physical

`

Core Fields:

| Field Name | Type | Required | Default Value | Description |

|-------|------|------|--------|------|

| item_number | string | ✓ (keyed) | - | CAD Number |

| name | string | - | - | Name |

| description | string | - | - | Description (stored_length=256) |

| authoring_tool_version | string | - | - | Authoring Tool Version (stored_length=32) |

| allow_team_change_logic | boolean | - | 1 | Allow Team Change (hidden=1) |

| external_id | string | - | - | External ID (indexed=1) |

| authoring_tool | list→Authoring Tools | - | - | Authoring Tool |

| state | list→States | - | - | State |

| classification | string | - | - | Classification |

Important Note:

• CAD is the only type with manual_versioning=1, i.e., manual version control.
• Divided into two main branches: Mechanical and Electronic.
• Supports file attachments: viewable_file, view_file, CADFiles.
• default_page_size: 50 (larger than other types).

#### 3.1.4 Product

Basic Properties:

• implementation_type: table
• is_versionable: 0 (not versioned)
• TOC category: ProductEngineering/Design
• Can Add: CM (Configuration Management Group)
• default permission: Product

Core Fields:

| Field Name | Type | Required | Default Value | Description |

|-------|------|------|--------|------|

| item_number | string | ✓ (keyed) | - | Product Number |

| name | string | - | - | Product Name |

| description | string | - | - | Description |

Lifecycle: Default (single state: Released)

#### 3.1.5 Manufacturer

Basic Properties:

• implementation_type: table
• is_versionable: 0
• TOC category: Sourcing
• Can Add: Component Engineering, Sciot PLM

Core Fields:

| Field Name | Type | Required | Default Value | Description |

|-------|------|------|--------|------|

| name | string | ✓ (keyed) | - | Manufacturer Name |

Lifecycle: Default (Single State: Released)

#### 3.1.6 Manufacturer Part

Basic Attributes:

• implementation_type: table
• is_versionable: 0
• TOC category: Sourcing
• Can Add: Component Engineering, Sciot PLM

Core Fields:

| Field Name | Type | Required | Default Value | Description |

|-------|------|------|--------|------|

| item_number | string | ✓ (keyed) | - | Manufacturer Part Number |

Lifecycle: Default (Single State: Released)

#### 3.1.7 Change Management Types

| ItemType | Description | Versioned | TOC Category |

|----------|------|-----------|---------|

| ECR (Engineering Change Request) | Engineering Change Request | 0 | - |

| ECN (Engineering Change Notice) | Engineering Change Notice | 0 | - |

| PR (Problem Report) | Problem Report | 0 | - |

| Express DCO | Express Deviation Change Order | 0 | - |

| Express ECO | Express Engineering Change Order | 0 | - |

| Simple ECO | Simple Engineering Change Order | 0 | - |

| Simple MCO | Simple Manufacturing Change Order | 0 | - |

| PE_Deviation | Deviation | 0 | - |

| PE_Waiver | Waiver | 0 | - |

| PE_Rework Order | Rework Order | 0 | - |

3.2 Life Cycle Maps

#### 3.2.1 Part Life Cycle (Core) ⭐

`

┌──→ Obsolete ──┐

│ │

Preliminary → In Review → Released → Superseded

↑ │ │ ↑ │

└────────────┘ │ │ │

↓ │ ↓

Manual Change Obsolete

│

└──→ Released

`

State Details:

| State | item_behavior | set_is_released | Permission Template | Description |

|------|---------------|-----------------|---------|------|

| Preliminary | float | 0 | New Part | Initial state, editable |

| In Review | float | 0 | In Review Part | Under review |

| Released | fixed | 1 | Released Part | Released, locked |

| In Change | fixed | 1 | - | Under change |

| Manual Change | fixed | 0 | SCIOT Full | Manual change |

| Superseded | fixed | 1 | - | Superseded |

| Obsolete | - | 1 | - | Obsolete |

Transition Rules (All transition roles are Sciot PLM, unless noted):

| Transition | Role | Description |

|------|------|------|

| Preliminary → In Review | Sciot PLM | Submit for review |

Preliminary → Released | Owner (pre: PE_CheckChangeItemUsage) | Owner can directly release, but must check change items

Preliminary → Released | Sciot PLM | Sciot PLM can also directly release

In Review → Released | Sciot PLM | Review approved

In Review → Preliminary | Sciot PLM | Return to initial

Released → In Change | Sciot PLM | Initiate change

Released → Manual Change | Sciot PLM | Manual change

Released → Superseded | Sciot PLM | Mark as superseded

Released → Obsolete | Sciot PLM | Obsolete

In Change → Superseded | Sciot PLM | Supersede after change

Manual Change → Released | Sciot PLM | Change back to released

Superseded → Obsolete | Sciot PLM | Obsolete superseded part

Key Conclusions:

• Sciot PLM is the dominant role in the Part lifecycle, controlling almost all transitions
• Owner has one special path: Preliminary → Released (requires checking change items)
• The three statuses Released/In Change/Superseded are marked as released (set_is_released=1)
• Obsolete has no item_behavior setting (default)

#### 3.2.2 Default Lifecycle

`

Released (single state, no transitions)

``

Types using this lifecycle:

• Product
• Manufacturer Part
• Manufacturer
• Deliverable
• Program

3.3 Workflow Maps

The PLM module uses Workflow Maps to implement change approval processes:

| Workflow Name | Purpose | Description |

|-----------|------|------|

| ECR | Engineering Change Request Approval | Full change request process |

| ECN | Engineering Change Notice Approval | Change execution approval |

| PR | Problem Report Process | Problem report handling |

| Express DCO | Express Change Order | Simplified change process |

| Express ECO | Express Engineering Change Order | Simplified change execution |

| Simple Change | Simple Change | Most streamlined change process |

| CM2 CN | CM2 Change Notice | CM2 standard change notice |

| CM2 CR | CM2 Change Request | CM2 standard change request |

| CM2 Incident | CM2 Incident | CM2 incident management |

| CM2 IR | CM2 Incident Report | CM2 incident report |

Important Note:

• The PM module does not use Workflow Maps; it only uses Life Cycle Maps.
• The PLM module uses both Life Cycle Maps and Workflow Maps.
• Workflows are used for scenarios requiring multi-level approvals (e.g., change management).

3.4 Permission Matrix

#### 3.4.1 New Part Permissions

| Role | discover | get | update | delete | change_access |

|------|----------|-----|--------|--------|---------------|

| All Employees | ✓ | ✓ | ✗ | ✗ | ✗ |

| Creator | ✓ | ✓ | ✓ | ✓ | ✓ |

| Owner | ✓ | ✓ | ✓ | ✓ | ✓ |

| Sciot PLM | ✓ | ✓ | ✓ | ✓ | ✓ |

| Manager | ✓ | ✓ | ✓ | ✗ | ✗ |

| erp_Sale | ✓ | ✓ | ✗ | ✗ | ✗ |

| ACC SUB-USER | ✓ | ✓ | ✗ | ✗ | ✗ |

| ID_STORE_KEEPER | ✓ | ✓ | ✗ | ✗ | ✗ |

| Team | ✓ | ✓ | ✗ | ✗ | ✗ |

#### 3.4.2 New Document Permissions

| Role | discover | get | update | delete | change_access |

|------|----------|-----|--------|--------|---------------|

| All Employees | ✓ | ✓ | ✗ | ✗ | ✗ |

| Creator | ✓ | ✓ | ✓ | ✓ | ✓ |

| Owner | ✓ | ✓ | ✓ | ✓ | ✓ |

| Sciot PLM | ✓ | ✓ | ✓ | ✓ | ✓ |

| Manager | ✓ | ✓ | ✓ | ✗ | ✗ |

| Team | ✓ | ✓ | ✗ | ✗ | ✗ |

#### 3.4.3 New CAD Permissions

| Role | discover | get | update | delete | change_access |

|------|----------|-----|--------|--------|---------------|

| Creator | ✓ | ✓ | ✓ | ✓ | ✓ |

| Owner | ✓ | ✓ | ✓ | ✓ | ✓ |

| Sciot PLM | ✓ | ✓ | ✓ | ✓ | ✓ |

| Manager | ✓ | ✓ | ✓ | ✗ | ✗ |

| All Employees | ✓ | ✓ | ✗ | ✗ | ✗ |

#### 3.4.4 New Change Permissions (Change Management)

| Role | discover | get | update | delete | change_access |

|------|----------|-----|--------|--------|---------------|

| Sciot PLM | ✓ | ✓ | ✓ | ✓ | ✓ |

| CM | ✓ | ✓ | ✓ | ✓ | ✓ |

| Owner | ✓ | ✓ | ✓ | ✓ | ✗ |

| Creator | ✓ | ✓ | ✓ | ✓ | ✗ |

| Manager | ✓ | ✓ | ✓ | ✓ | ✓ |

| World | ✓ | ✓ | ✗ | ✗ | ✗ |

#### 3.4.5 SCIOT Full Permissions

| Role | discover | get | update | delete | change_access |

|------|----------|-----|--------|--------|---------------|

| Sciot PLM | ✓ | ✓ | ✓ | ✓ | ✓ |

| All Employees | ✓ | ✓ | ✓ | ✓ | ✓ |

| World | ✓ | ✓ | ✓ | ✓ | ✓ |

3.5 Identity and Roles

#### 3.5.1 PLM Core Identities

| Identity Name | Description | Members |

|---------|------|------|

| Sciot PLM | Internal identity for SCSAI (Primary Identity) | Internal system identity |

| All Employees | All Employees | Agent Admin, Super User, ACC SUB-USER, Lisa Andrews, Gustavo Achong, Kim Akers, Humberto Acevedo, Manoj Agarwal, CRB, Robin Wakefield, ES Admin, ID_STORE_KEEPER, Hatim Aiad, erp_Purchase |

| CM | Configuration Management Group | Change Specialist I, Change Specialist II, Change Specialist III, Change Leader, Change Implementation Leader, Audit Release Analyst |

| Change Control Board | Change Control Board | CM Group + Agent Admin |

| CRB | Change Review Board | Kim Akers, Gustavo Achong |

| Component Engineering | Component Engineering | (Can create Manufacturer/Manufacturer Part) |

#### 3.5.2 Additional Roles in Fongs_Base

| Role Name | Description |

|---------|------|

| DOC Team | Documentation Team |

| Engineering Team | Engineering Team |

| Procurement Team | Procurement Team |

| QA Team | Quality Assurance Team |

| QP Admin | Quality Planning Administrator |

| QP Daemon | Quality Planning Daemon |

| Quality Planning | Quality Planning |

| R+D Mechanical Team | R&D Mechanical Team |

| R+D Project Lead | R&D Project Lead |

| R+D Team | R&D Team |

| Reference Library Group | Reference Library Group |

| Sales Team | Sales Team |

| PROENGQA | Engineering QA |

| TEST-* | Test-Related Groups |

#### 3.5.3 Business Roles

| Role Name | Description |

|---------|------|

| erp_Sale | ERP Sales |

| erp_sales_team | ERP Sales Team |

| erp_service_team | ERP Service Team |

| erp_Purchase | ERP Purchase |

| ACC ADMIN USER | Account Admin User |

| ACC SUB-USER | Account Sub-User |

| ID_PURCHASE_ADMIN | Purchase Administrator |

| ID_SALE_ADMIN | Sales Administrator |

| ID_SALE_SERVICE | Sales Service |

| ID_SERVICE_TEAM | Service Team |

| ID_STORE_KEEPER | Warehouse Keeper |

| workshop_team | Workshop Team |

| QC Team | Quality Control Team |

| All Customers | All Customers |

| All Partners | All Partners |

| All Suppliers | All Suppliers |

3.6 Sequence Configuration (Sequence)

| Sequence Name | prefix | initial_value | step | pad_to | pad_with | suffix | Format Example |

|---------|--------|---------------|------|--------|----------|--------|---------|

| Default Part | - | 100000 | 1 | - | - | "-001" | 100000-001 |

| Default Document | - | 100000 | 1 | - | - | - | 100000 |

| CAD Document | "CAD-" | 0 | 1 | 8 | 0 | - | CAD-00000001 |

| ECR | - | 1 | 1 | - | - | - | 1 |

| ECN | - | 1 | 1 | - | - | - | 1 |

| PR | - | 1 | 1 | - | - | - | 1 |

| Express DCO | - | 1 | 1 | - | - | - | 1 |

| Express ECO | - | 1 | 1 | - | - | - | 1 |

| Express EDR | - | 1 | 1 | - | - | - | 1 |

| Simple ECO | - | 1 | 1 | - | - | - | 1 |

| Simple MCO | - | 1 | 1 | - | - | - | 1 |

| CM2 AO | - | 1 | 1 | - | - | - | 1 |

| CM2 Incident | - | 1 | 1 | - | - | - | 1 |

| CM2 IR | - | 1 | 1 | - | - | - | 1 |

| PE_Deviation | - | 1 | 1 | - | - | - | 1 |

| PE_Rework Order | - | 1 | 1 | - | - | - | 1 |

| PE_Waiver | - | 1 | 1 | - | - | - | 1 |

Key Notes:

• Part numbering starts from 100000 with a step of 1, and includes the suffix "-001".
• CAD numbering uses the prefix "CAD-" with 8-digit zero-padding.
• All change management types start numbering from 1.
• Document numbers start from 100000

3.7 List Values

#### Core Lists and Options:

| List Name | Option Values | Description |

|---------|--------|------|

| Make Buy | Make, Buy, Phantom, Ref | Make/Buy type |

| Units | mm, cm, m, inch, ft, kg, g, lb, oz, ... | Unit |

| States | (Global country/region list) | Country/Region |

| Product Phases | Concept, Design, Prototype, Pilot, Production, ... | Product phase |

| Drawing Sizes | A0, A1, A2, A3, A4, B, C, D, E, ... | Drawing size |

| Specification Types | Performance, Design, Process, Material, ... | Specification type |

| Authoring Tools | (Extensive list of authoring tools) | Authoring tool |

| Goal Basis | Target, Estimate, Quote, ... | Cost basis |

| Change Categories | - | Change category |

| Change Priorities | Emergency, High, Medium, Low | Change priority |

| Change Severity | Critical, Major, Minor | Change severity |

| Change Sources | Customer, Internal, Supplier, ... | Change source |

| Change Types | - | Change type |

| Affected Item Actions | Add, Remove, Modify, Replace, ... | Affected item action |

| Affected Item Disposition | Use As Is, Rework, Scrap, Return, ... | Affected Item Disposition |

| Currency | USD, EUR, CNY, JPY, ... | Currency |

| Duration Unit | Hours, Days, Weeks, Months | Duration Unit |

| Countries | (Complete global country list) | Countries |

| CM2 Status | - | CM2 Status |

| Problem Status | Open, In Work, Closed, ... | Problem Status |

3.8 Team

Example Team: Product Team

| Role | Member |

|------|------|

| Team Manager | Lisa Andrews |

| Team Member | Humberto Acevedo |

| Team Member | Kim Akers |

Team Identity System:

• Team Manager - System Identity (Non-editable)
• Team Member - System Identity (Non-editable)
• Team Guest - System Identity (Non-editable)

4. Summary of Key Design Patterns

4.1 PM vs. PLM Comparison

4.2 Permission Models

4.3 The Central Role of the Sciot PLM Identity

Sciot PLM is the "master key" for the entire PLM module:

• Controls all transitions in the Part lifecycle (except one Owner path)
• Has full permissions for all PLM data types
• Is the full controller in New Part/New Document/New CAD permissions
• Is the full controller in New Change permissions
• Used for the SCIOT Full permission template

4.4 Summary of Default Values

5. Precautions and Common Pitfalls

1. CAD's manual_versioning=1: It is the only type with manual versioning, different from other PLM types.
2. Activity2 transition role is World: Anyone can advance the activity status; pay attention to permission control.
3. Sciot PLM is the master role: It controls almost all PLM lifecycle transitions.
4. PM has no Workflow: The PM module only has a Life Cycle, no approval workflow.
5. Document's Can Add=World: Document creation permissions are very permissive.
6. Part has two Preliminary→Released paths: Sciot PLM and Owner (requires checking change items).
7. Product/Manufacturer uses the Default lifecycle: Created as Released, no approval required.
8. Team Manager/Member/Guest are system identities: Not editable, marked as "System Identity – Do Not Edit".
9. scheduling_mode default=1 and mandatory: The scheduling mode must be specified when creating a Project.
10. WBS Element has no lifecycle transition: It is in Active state immediately after creation.