Get Started

auditBus provides a framework to process large amounts of checklists by different auditors, project managers and customers within one software solution. Avoid unnecessary error sources caused by heterogeneous technologies and join all resources in a single system.

Fast, efficient, reliable and easy to use.

Roll out your audits just by arranging locations, questionnaires and sites. Experts schedule on site inspections autonomous and collect data online by using the web browser or offline with smartphone or tablet. Track progress within the system and get all questionnaires, reports and interim analyses any time. 

auditBus connects:

  • Locations
  • Users
  • Checklists

Locations are objects you want to inspect. These are mostly sites like warehouses, shops, workshops, offices or any other organisational or technical unit that can be physically visited.

Users are mainly auditors visiting locations and collect data.

Checklists define stuff to be inspected and some object related informations for evaluation and report.

auditBus turns this informations into objects for auditing and provides individual tools for each user in order to get the job done. Without installation of additional software, directly within Firefos or Chrome and on almust any hardware.

There is generally no need to further alignment of any content or responsibility outside of auditBus. Everything is handled within your cloud.

 

 

Location

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.

User

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.

 

 

Questionnaire

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.

 

 

 

 

Contentlayer

Every auditBus content is layered.

Each layer represents at least one location and each site, can have subordinated sites. Individually or grouped by other layers. The shape of the branches is neither determined, nor uniformly and follows the hierarchical structure of a given organisation.

Access to any content is organised ba access to specific layers.

  • Questionnaires are accessible, by assignment to a specific layer and give users access to it. Rights to access automatically include subordinated items.
  • Users get access by adding layers to their account.
  • By selection of a specific layer, evaluations, counts, key figures and banchmarks for the selected node are calculated.

 

 

All data is with reference to the selected layer respectively node. Comparision of different subsets is achieved by switching between layers.

 

New layers and sites will always be added to the currently selected node. For example, to add a new location to "Germany" like shown on the left, select  "Germany" first, and "add Location" next.

Shape of Branches can be edited any time by drag and drop. In order to split "Central" into "Central-South" and "Central-North" for example, add both new layers to the folder "Central" and then move "Austria" to "Central-South" and "Germany" to "Central-North".

This way to cluster data is a comfortable method to organize user rights by competence and grants highest flexibility for reporting.