Organization Feature Within RIMS

Real Estate Information and Management System (RIMS) Organization (ORG) enables you to isolate or silo coexisting RIMS projects in your organization.

ORG is typically used in the following business settings:

• A company doing work on behalf of other financial institutions (e.g., Managed Service Provider (MSP) or Appraisal Management Company (AMC); examples include ordering appraisals, performing reviews, or other work for which the financial institution does not have the staff to perform).
  
  
• A merger or acquisition in which, because of the time frame imposed by potential legal proceedings, work must not be shared across the enterprise. All work must be kept separate until the merger is complete.

There are tow types of ORGs:

• Account Officer (AO) ORG - most widely used and common ORG type.
  
  
• Job Manager/Vendor Job Manager (JM/VJM) ORG - less typical ORG implementation - requires consultation with Account Manager to implement.

ORG Types

The AO ORG features the following roles:

• Content Administrator (CA): assigns the AO to an ORG (required element of AO user profile).
• AO: creates Service Request Forms (SRFs).
• JM: completes associated project tasks without limitation by ORG.
• VJM: completes associated tasks assigned to them without limitation by ORG.

In the JM/VJM ORG the following roles exist:

• CA: assigns the AO to an ORG (required element of AO user profile), assigns JM/VJM to an ORG (optional element of the JM/VJM user profile).
• AO: creates SRFs.
• JM: completes associated project tasks limited to their assigned ORG(s)
• VJM: completes associated project tasks limited to their assigned ORG(s)

As shown in the following AO ORG diagram, the AO creates a distinct project - project and associated data is isolated from other ORGs within the financial institution:

As shown in the following JM/VJM ORG diagram, the AO ORG creates a distinct project; however, the JM or VJM can be assigned to more than one ORG: