The following items are the primary considerations for setting up Organizations within Unanet:
- Customer Profiles
- Custom Images
- Financial Organizations
- Organization Types
- Person Organizations
- Project Organizations
- Project Owning Organizations
- Vendor Profiles
- ACME (all of the organizations below this hierarchy have an Organization Type of INTERNAL)
- ACME- SW
- CUSTOMERS (all of the organizations below this hierarchy have an Organization Type of CUSTOMER)
- VENDORS (all of the organizations below this hierarchy have an Organization Type of VENDOR)
- The organization that "owns" a project is generally the organization that assumes the costs and revenue of the project and holds the "remit to" information for billing purposes. In this example a project might be "owned" by ACME-SW-PROFSERV. Unanet calls this type of organization the Project Owning Organization.
- ACME's customers are also set up as Organizations in Unanet. When used in this way, customers are referred to as Project Organizations(different from project owning organizations).
Similarly, vendors are referred to as Vendor Organizations.
Finally, when using Unanet Financials, a Financial Organization represents a legal entity for which a separate set of books is maintained for the various departments, regions, and divisions within the legal entity. The designation of Financial Organization is a flag on the organization itself. All Person Organizations (for employees but not contractors) and all Project Owning Organizations must be organizations which have been designated in the organization profile as Financial organizations.
Organizations are used in Unanet for reporting and restricting access.
- Reporting: Organizations are a primary and key reporting field. In creating any report, the first thing the report criteria will ask you for is if you would like to filter by organization. As a result, you will typically set up your Organizations to represent such external and internal entities as customers, internal divisions, departments, or lines of business.
- Restricting Access: Organization relationships are helpful for restricting access since users can be assigned organizational access to any or all of the organizations within a given org "tree".
Organizations can be displayed in a list view:
Organizations can be displayed in a Tree view:
TIPS: If Organization Codes begin with a similar name, users can generate reports using that name as a filter (e.g. all Government organizations begin "GOV-Client name", all Commercial organizations begin with "COM-Client name").
Generic top level "Project" and "People" organizations can also be used to help avoid confusion when a user is looking for Project or People Organizations in reports.