Overview

The primary role of Arctevity System Registrar (ASR) is to assign a unique identifier to each Arctevity system. ASR also serves as a specialized customer relationship mangement tool. ASR enables capturing supplemental information about each system including which customer the system belongs to and the contact information for people who are involved in designing, deploying, and supporting the system.

A customer may have one or more systems:

• In some cases the same group of customer contacts are responsible for all of the customer's systems.
• In other cases, the customer may designate system-specific contacts.
• The same person may serve as a contact for more than one system and for more than one customer.
• A person who serves as a customer's contact does not need to be an employee of the customer; they may be a third-party vendor or even a tenant.

ARS is fluid and does not enforce a paricular workflow. Specifically, ARS may be used to create contacts - no matter what their involvement - for subsequent association with customers and systems. Similarly, a system may be created and subsequently associated with a customer and/or with designated contacts. Finally, customers may be created and subsequently associated with one or more systems and one or more contacts.

Contacts, systems, and customers can be deleted, but an attempt to delete a contact, system, or customer for which there is an outstanding relationship will present an error message. Further, a deletion involves use of a confirmation dialog that presents a string that must be exactly typed in before the deletion will be allowed.

Searching

ASR provides a search capability that enables users to find a contact, customer, or system by entering a string. Queries are made against the name of the contact, customer, or system. The search is incremental, meaning that the search is performed as the user types. The search is not case-sensitive. Multiple white-space separated search terms form separate search tokens.

For example:

New York NY

seperately looks for matches for each the following in all of the specified object fields:

• New
• York
• NY

Only one match is needed to include the matching System in the search results.

Quoted search terms and non-quoted search terms, seperated from each other by white space, form separate search tokens. For example:

"New York" NY

seperately looks for matches for each the following in all of the specified model object fields:

• "New York"
• NY

Only one match is needed to include the matching object in the search results.

Entering return or an empty string in the search field will return all objects.

Use Model

Contacts are created on the contacts page, customers on the customers page and systems on the systems page. When a customer is created or edited the contacts who are members of the customer's team may be assigned. The responsibilities that these contacts have are in regard to Arctevity. The summary list of customers itemizes each customer's team. When a system is created or edited it can be associated with a customer. It is possible for system-specific contacts to be designated. Designated contacts are assigned when the system is created or edited. The summary list of systems itemizes the designated contacts for each system. Arctevity staff would most likely interact with designated contacts as opposed to the contacts who comprise the system's customer's team.

Identifiers

When a system is created ASR automatically assigns the system a UUID and a 7-character human readable identifer. The UUID is used by the Arctevity technical platform while the id is used to make it easier for people to reference a specific system with precision. When creating or editing a system either of these identifiers can be changed. However, ASR enforces uniqueness among UUIDs and system ids.

When a customer is created ASR automatically assignes the customer a 6-character humman readable identifier. This id enables people to refer to a specific customer with precision. There is no technical need for a UUID as well. When creating or editing a customer this identifier can be changed. However, ASR encforce uniqueness among customers ids.

Note the following:

• System ids are formated as ARC7-XXX-XXXX, where X is a letter or a digit. These ids are case-insensitive. There are more than 78 billion possible combinations.
• Customer ids are formatted as ARC6-XXX-XXX, where X is a letter or a digit. These ids are case-insensitive. There are more than 2 billion possible combinations.
• Different id formats and representations were chosen to avoid potential confusion between customer ids and system ids.
• If for some reason a system's id is changed, then as long as the system's uuid is not altered the operation of the Arctevity technical platform will not be affected.

A contacts email address - as entered by the ASR user - serves as the unique identifer for a contact. Each contact must have an email address. ASR enforces uniques among contact email addresses.

Organizations

Organizations are created as a by-product of creating a customer or a contact. Absent whitespace, case senstivity, and punctuation, The name for an organization must be unique. For example, the names "McDonalds Inc." and "mcdonald's inc" are treated as the same. ARS will not allow a new organization to be established if its name conflicts with an existing organization.

Addresses

When a contact, customer, or system is created or edited it is possible to associate each with a postal address. The desired address may be selected from a list of addresses previously used, or a new address may be entered. When a prior address is used, it is copied. This means that changes to the address for a contact, customer, or system do not alter the addresses for other contacts, customers, or systems.

Contacts

When creating or editing a contact, it is optional as to whether they are associated with an organization and/or whether they are assigned a role.

When adding a contact to a customer or system, the contact must be assigned at least one responsibility. Otherwise an error will be flagged. In contrast, a contact may be assigned multiple responsibilities. Different contacts for a customer or a system may be assigned the same responsibility or responsibilities.