# Presentation: 301157

## Dear Phase IVb

- Guidance on Attributes for System Entities

## Attributes for Entities within a System

- The following slides describes the three attributes that will be captured for an entity
- within a subject system (the system or sub-system for which information is being collected) and
- its relationship with interface systems (other systems with which is interacts).
- Each attribute’s value will be its current state, not as planned for the future.

## Authoritative Source

| Department | The department controls all values for the entity through subject system. |
| --- | --- |
| Bureau | The bureau controls all values for the entity through subject system. |
| Subset | Only a certain set of values for the entity are controlled and owned by subject system.  The controlled set of values could be by location (state, region) or by program or other parameters. |
| Non-Authoritative | The subject system does not control or own the data, it receives the data from an interface system.  |
| TBD | The subject system is not yet in production and the authorative source is yet to be determined. |
| Unknown | The authoritative source is not known at this point. |
|  | 
Note: All subsystems within a subject system (under the same management control) have the same authoritative source. |

- This denotes the level of ownership and control of the entity values within a subject system.

## Form of Sharing

- This describes how an entity’s values in the subject system are shared with other systems

| Duplicate | The data is copied from an interface system to the subject system.  |
| --- | --- |
| Access | The data is stored in an interface system.  The subject system accesses the data in the interface system and displays, but does not store, the data in the subject system. |
| Multiple | The data in the subject system has more than one interface system and each interface system has its own form of sharing.  |
| Not Shared | The data in the subject system is not shared with any other system. |
| TBD | The subject system is not yet in production and the form is shared is yet to be determined. |
| Unknown | The form of sharing is not known at this point. |

## Transformation Type

- This describes what types of actions the system can perform on an entity. (CRUD)

| Create | The subject system can only create occurrences of the entity. The system can read the data but cannot update the data.  |
| --- | --- |
| Read | The subject system can read occurrences of the entity. This value is used only if the subject system is not able to create, update or delete occurrences.  |
| Update | The subject system can only update existing occurrences of the entity. The system can read the data but cannot create occurrences. |
| All | The subject system can create, read, update or even, delete occurrences of the entity.  In general, a system will be able to create and update occurrences, so ‘All’ would be the default choice.  |
| TBD | The subject system is not yet in production and how the data is transformed is yet to be determined. |
| Unknown | It is not known what actions can be taken on an entity for the subject system.  |

## Examples

**Nightly Replication**

- A stand-alone system

- A real-time access system

**Real-Time Interface**

- A System w/ Duplicate Data

**Nightly Replication**

**Nightly Replication**

_**Legend**_
- Source: Authoritative Source
-       Dept: Department
-       Non-Auth: Non Authoritative
- Txform: Transformation Type
- Share: Form of Sharing
-       Dupe: Duplicate

**Examples**
**of the EMPLOYEE Entity in Different Systems**