Locations are auditBus - stops, determining the objects to be inspected geographically and hierarchically. Although named as "location" and mainly prepared to store address data, it could be any other object to be inspected by the checklist as well. 

By assignment of Checklists to location and auditor, the order to the auditor is placed.

Grouping of locations on different Layers with specific privileges local managers und leadauditors increase efficiency of work processes. Moreover, layers allow easy definition of subsets for processing and analysis.

You may select locations and grouped Layers from the menu-tree on the left. To open content of any layer just click it's name next to the folder icon, to enfold packed sites only, just click the folder icon itself. To select a location object, select the name. Data of the currently selected object is shown in the site header, above the desktop tabs. To edit location's information, you open the editor by a click on the header.

In order to add new location objects manually, you select the node, the new object should belong to and then select "add location here".

Definition of "Company Name" and "CompanyShortName" of the new object are mandatory. "CompanyShortName" is used for the terms, used on the menu tree on the left. Furthermore you may save the fully qualified address and any further informations that might be useful.

There are no predefined rules concerning the amount and hierarchy of location objects, following the structure of the represented Organisation.

Furthermore the structure once built on set up isn't final. It can be extended and rearranged any time by adding mew objects and move single objects or whole branches. Nodes and  branches are morst important for arrangement of user rights and subsets for evaluation.

auditBus supports distribution of questionnaires among your team without overlaps and complete control of correctness, completeness and efforts.

Auditors get direct access to all locations, containing empty checklists assigned to their personal id. 

Administrators, leadauditors and customers get access by assignment of one or multiple content layer(s).

Assigned checklists and content layers determine access to locations and sites. User roles ( administrator, auditor or customer ) determine available methods and functions.

For optimal usability and performance, users get nothing but tools needed to complete their tasks.

Auditors usually doesn't get content layers assigned because they are already owners of assigned checklists and get access to sites and locations this way, as long as they don't have any further obligations. Access of auditors to specific sites expires automatically at completion of the questionnaire.

Leadauditors have to organize teams and efforts. To allow permanent access, you just have to add these auditors to related content layer(s). In combination with the user role, they get extended rights, may add checklists to locations, assign auditors and see statistics - but not the right to delete anything or change content of different auditors.

Administrators have full access to the System including right to edit any content. Administrator's rights are only limited

Viewer-Role (or: Customer) do have read access to reports, questionnaires in progress and overall evaluation. They may not execute operations, writing to the database.

More than a checklist.

Questionnaires become multi-funktional objects: Guideline for auditors, object key to save and retrieve data on your network and finally basis for all your Documents, starting with input forms, generating single reports and finally visualisation of over all evaluations.

Almost any change of the assessments is achievable by changing the underlying questionnaire and affect derivational content immediately.

Filtered questions consider different circumstances. Single or multiple questions spread over the whole questionnaire as well as huge blocks may be shown or hidden based on underlying filter-questions. With this ability, auditors will be guided through audit processes the best possible way.

In consideration of this importance, it shouldn't be obscured, that production of questionnaires is the most challenging and laborious part of any new set up. On the other hand, it covers easily 85% of work to be done.

The XML - syntax provides one breakdown level for specific sections of your questionnaire and mainly four different types of questions ( differentiable by additional attributes ): Main types are lists with single- or multiple selection, text fields providing just one line, large textboxes and option to upload image- or document-files. The amount of sections per questionnaire as well as the number of questions one section may have, is categorically not determined.

auditBus has a simple XML - Editor included, which takes care about right syntax of source codes. Of course, more powerful tools like Oxygen® or XMLSpy® will facilitate working with XML significantly.

In order to add a checklist to a location, we first have to select the desired layer and generate an empty template (For example: "MyNewChecklist"). Below, we create one single section with just two questions: A simple Textbox first, and additionally one closed question having three alternative options to answer:

Assessmets are expandable copies of a questionnaires template, owned by a user.

The template is "mother" of all assessments. on creating a new assessment, you place a working copy of the current questionaire to a specific site and user. This working copy is protected against changes by mistake - in particular against retroactive changes if the assessment has been started. But changes to the template can easily be transferred to existing assessments, as long as these are empty.

Moreover, the working copy may be widened by addition of deviations, comments and evidences.

auditBus presentations depend on content of questionnaires, nested structure of folders and sites and the user role. Therefore, all descriptions use a concrete common example.

"Euro Workshops" shall be some cross border Service-Organisation for electrical devices.

For all sales regions, Countries and subsidiaries, about 50 auditors have to execute inspections concerning quality of service and repair, based on two different questionnaires ("Workshop1" and "Workshop2") in several hundred locations within a given period.

auditBus ist multilingual.

As default, auditBus uses the language of the web-browser's installation. In doubt English is used as default. The user may switch between available languages.

In case, questionnaires have been added in different languages, auditBus automatically translates between the currently selected and the language, a working-copy, was originally added.

For each language available, auditBus creates one translated PDF-Report and saves it. The currently selected language determines which PDF translation is selected. For input, the system automatically translates between languages. If both are identical, only the original languge is shown.

To make use of multilingualism, you just have to add a translated copy of the original questionnaire with the required language selected on the system. For our example, we use unreadable dummy text and therefore no translations.

auditBus provides as much content-layers as required

All locations (content-layers) get reached by users via the menu tree on the left. By selection of "Euro Workshops", the whole organisation is selected, on the next level is flipped open. The amount of layers and its structure is neither limited, nor final.

Above the menu tree, users may change own credentials by clicking the own username.

In order to activate the user functions, select e layer with some content:

Organisation of content-layers

By clicking any folder-icon the next level will be unfolded (or vice versa) and it's content is shown (or hidden). To activate a layer, select its name. The amount of elements inside of the selected folder as well as the given hierarchy may be changed any time. Administrators may add new locations and nodes or move branches and sites including all their content. Either by moving from one branch of the tree to another, or by dragging above the header of a different node.

The location menu is user based

The locations-tree is calculated at login, based on questionnaires und content-layers currently assigned to the account. Content is limited to users needs. No more and no less.

Role specific functions

For different tasks, auditBus provides mainly three different user-roles: Admin (Projektmanager), auditor (inspection and collecting data), observer (or customer with option to retrieve statistics, audits and interim results).

Based on a users role, different tabs allow users to switch between input sections, user-management, template design, evaluation, scheduling and handling of deviations and tasks (if any):

• Audit (admin, auditor, observer): Management-Informations concerning efforts and performance, data collection and search.
• User (Admin): edit user accounts, allocate and revoke locations and content layer.
• Templates (Admin): Addition and maintenance of questionnaires.
• Results (Admin, Betrachter): Downloads and statistics, benchmark and KPI's related to questionnaires.
• Schedule (Admin, Auditor, Observer): planned visits of locations.
• Tasks (Admin, Auditor, Observer): Deviations and corrective actions.

Project course

Create locations [Admin] => Create Checklist(s) anlegen [Admin] => Distribute Checklists [Admin, Leadauditor] => Schedule [Auditor] => Collect data [Auditor] => Finish / Report  [Admin, Leadauditor, Auditor] => Action-Plans [Admin, Leadauditor, Auditor].