Modeling your organization
To model your organization in Maintenix you create various entities to represent the geographical and functional structure of your company, the different groups of users who will use Maintenix, what each group of users is allowed to do, and associated third party companies.
The top-level entity is the default administrative organization (ADMIN organization type) that is automatically created when you first install Maintenix. The ADMIN organization represents the top level of your company, the parent company, or the service provider.
Under the ADMIN organization, you might have sub-organizations to model divisions such as operators, and maintenance and repair organizations (MROs), departments, and crews. Creating sub-organizations in Maintenix is optional. If you have a simple structure, with a single operator for example, using the default administrative organization to represent your organization might suffice. But if you need to group and segregate different parts of your organization, then you create sub-organizations.
After you decide on the organizations you want, you create the locations where inventory can be located and where people can work. Each location belongs to at least one organization. Organizations link different entities. Aircraft, maintenance programs, locations, users, labor skills, owners, task definitions and other entities are assigned to organizations.
Entities | Types | Description |
---|---|---|
Organizations |
ADMIN Required |
The default ADMIN organization is created automatically when you install Maintenix. There can be only one ADMIN organization so when you create sub-organizations under the ADMIN, they must be different organization types. |
Company: Operator Optional |
Represents companies or divisions that operate a fleet of aircraft. Create Operators as sub-organizations of the root ADMIN organization. Do not create an Operator under another Operator or under an MRO type sub-organization. Although Maintenix doesn't prevent you from creating Operators or MROs as sub-organizations of Operators or MROs, system logic doesn't support this structure. |
|
Company: MRO Optional |
Maintenance, repair and overhaul companies that perform aircraft maintenance activities. Create MROs as sub-organizations of the root ADMIN organization. Do not create an MRO type sub-organization under another MRO type or under an Operator type sub-organization. |
|
Other sub-organizations: Department Optional |
Represents departments within Company or ADMIN type organizations. Examples include heavy maintenance, line maintenance, warehouse, or perhaps even a fleet type, such as Boeing 767 or Airbus 320. Create as a sub-organization of either of
these:
|
|
Other sub-organizations: Crew Optional |
Represents groups of human resources that work together, and to whom tasks can be assigned. Create as a sub-organization of either of
these:
|
|
Authorities Optional |
N/A |
Used to restrict access to the following
potentially sensitive information:
|
Locations Required |
Broadly summarized:
|
A physical location where inventory can be stored or people can work. Each location can have departments assigned to it, as well as capabilities (the type of work that can be performed at the location) and capacity (the speed at which work can be performed). Locations can be subdivided into sublocations. Every location must belong to at least one organization (except VENDOR type locations). When you create locations, you assign organizations to them. Locations can have zero, one, or multiple departments. When you create locations, you assign departments to them. |
Departments Optional |
|
Departments (and indirectly, locations) determine which of the data records users see in their to-do lists tabs, for example, specific inventory records, task definitions, assembly definitions, tasks, and maintenance programs. Departments are the link between users and locations. |
Users Required |
Every Maintenix user requires a user account and must
belong to at least one organization. When a user belongs to
multiple organizations, you identify the user's primary
organization. As part of the model, you create the following
entities that are assigned to users (and organizations):
|
|
Owners Required |
Broadly summarized:
|
Represents inventory owners. Each item of inventory has an owner. Ownership, along with the financial class of the inventory and the ownership type determines what financial transactions are recorded during the life cycle of an item. If you create inventory manually, you can select the owner. Otherwise, when inventory is received and Maintenix creates a record for the item, the owner that's assigned depends on the default owner that's set in the database and on the type of order the item is received for. Depending on your configuration, there can multiple owners in the system.
When you create an owner, you assign an organization to the owner. |
Vendors |
External providers of parts or services. When you create a vendor it is assigned the default organization or if your system includes multiple organizations that use different vendors, you can assign an organization to a vendor. When you a create vendor, a vendor location (type VENDOR) is automatically created. This enables you to ship inventory in Maintenix to and from the vendor location. These automatically created VENDOR locations are not assigned organizations, but you can do this manually. When you create a vendor, an owner, which is the vendor is created. |
|
Financial accounts Required |
Broadly summarized:
|