GNF » Go No Further

Save time localizing your equipment with Noah. (GoNoFurther) is a web software development company, founded on the idea that people shall be involved in the applications they would use. Since 1996 the company has worked hard to create applications that are meaningfull to the customer and easy to use by the users. has focus on development of web applikations and systems developed in cooperation with our customers and by utilizing the knowledge and experience with Asset Management and other areas of expertice. Development is mainly done in PHP, MySQL and javascript.

Today – supplies products that are developed based on users needs and requests.

Snail Mail:
J.M. Thielesvej 6 1tv.
DK-1961 Frederiksberg
CVR: 16143103

Contact Information

We would like to know who might have an interest in Noah. So we hope you will provide a bit of info.


If you have any questions regarding Noah, need support or anything else reach us using the form below.

Easy to use, easy to understand

If you can not find the answer here, feel free to contact our support!

Noah Documentation!

Reason for Noah and primary features

The base design of Noah is of simplicity, usability and accessibility.

You need to have easy access to your data and they need to be shown in a simple and meaningfull way.

Noah ® is built on the idea that any asset has a unique identifier. We call it an asset id (AssetID). It is a number starting at one and ending at (insert a very large number here).

How to connect the AssetID in Noah with the real world? It is common to print the asset id on an adhesive sticker – some print it with barcodes for easier registration using a barcode reader. / recommends Zebra Label printers for their ability to print 2D Bars – and low pricing. ( Extract asset data for importing into Zebra Label Printing software.
Others include the AssetID in the hostname or ID on virtual servers.

The AssetID is the focal point of the system. Every asset in Noah has an AssetID. So it is always possible to find the asset just by searching for the AssetID or locating the asset within the customer it is owned by.

Almost every aspect of the system is based on the fact that users update the assets database and keep the information as correct as possible. Remember it is datadiscipline that secures correct data at all times!

The menu is kept simple with the most basic options easy available. Top most is a search field and a “goto ticket id” field – direct accessible. Just enter search value or ticket id and press enter.


Many functions are based on real world need and usage. And some of these are based on workflows and processes from customers.


  • Orders have the current flow implemented (See Stages):
  • 1 : A user creates an order for item(s) (See Orders for details)
  • 2 : The order is created with an budgetmanager appointed (required)
  • Look at Job Functions for setting the Budget Manager approval level.
  • 3 : Budget manager receives a mail with the option to approve or reject the request.(And a link to the order where it is also possible to approve or decline the request.)
  • 3-1 : If approved, the order will be marked as approved, creator of the order as well as Purchaser will receive a mail stating the approval.
  • 3-2 : If rejected, the order will be marked as rejected, creator of the order will receive a mail stating the rejection.
  • 4 : Items are being verified purchaseable - delivery time, pricing and correct items verified - and purchased.
  • 5 : Items are received - and marked as such.
  • 6 : Order is marked as Complete by creator and as such ready for closure or invoicing.
Order Stages

An order has 6 stages defined:

  • Budget Descision : Order awaits Approval/Rejection
  • Item(s) received : Items have been received
  • Order Complete : All items have been received and marked as Complete
  • Purchased : All items have been received.
  • Rejected : Order has been Rejected
  • Verification from Purchaser(s) : Items await purchase


Maintenance can be used in several ways.

  • Service window for patch, upgrade or repair.
  • Revision on performed maintenance or patch

When maintenance task is finished, user must acknowledge the task done by marking it in View Maintenance

These "Ack's" can be seen in the tab "Revisions" on the asset, circuit or location.


Some things are ment to be done in a certain way or are thought out to work in a specific way for a reason. Below is some of these functions described for easier understanding of usage.


Clicking "Assets" in top menu, gives a list of all the Assets registered. This is where you can get all of the information regarding an asset, by clicking a link for viewing the asset.

Remember, there is an almost hidden field – Passwords. Click to view them. (Not everybody looking at your screen need to know the specific passwords to any given asset). If the passwords are dimmed with stars(*), you are not permitted to see the passwords!

It is possible to set a Security Clearance level for a password under an asset. That is, if you are Cleared to view the passwords. If not, you are not able to add or delete (edit) any passwords for that asset.

You may filter the list by using the above Dropdown boxes by Type, Customer, Position and Status.

In a virtual world there usually is a management station that handles the virtual machines. Include the AssetID in the name of the virtual machine.

Noah ® has an export function where it is possible to export the assetids to csv format. Import into eg. Microsoft Excel – or any other compaitble application – and print to adhesive stickers.


Creating an asset requires an name for the asset and which customer it is assigned to. After pressing “Create Asset” you are forwarded to Edit Asset, ready to enter additional information regarding the asset – See, Edit Asset.

Deleted Assets/Customers/Users

Why is it not possible to delete an asset or a customer? The history will be lost for the deleted asset or customer. So is the relation to the tickets (tickets). “Deleted Assets” and “Deleted Customers” (with CustomerID 1 and 2) is pre-built customers that will hold all deleted asset and customers. So they never “die”. They will just face a long period of “storage” or recycling by moving the asset to another customer.

Users and Customers can be Deactivated / Activated. They cannot be deleted. The reference to the assets and its tickets and history would be lost.

Deactivated Assets, Customers or Users will be marked with the color Red or just be placed under Deleted Assets or Deleted Customers.

Reserved AssetID's

Sometimes it is needed to print asset labels in advance – or reserve assets to a specific location/server type/amo. This is where you reserve the assetid’s. It shows the last available assetid (as Asset ID Start) and plus one (+1 – Asset ID End) as the last. Edit the fields to accomodate your needs. After you press Create Printed Assets, you will be forwarded to List Assets with the option “Printed Assets” activated.

IP Address

Assets can have an IP address ( or attached. Or several for that matter. It is possible to use the CIDR annotation to assign routed networks to an interface. Interfaces has a list of those IP’s assigned to the assets owner – Noah will try to show the IP’s found assigned for the customer in a dropdown menu while entering.

An owner can have an IP segment assigned. And the interfaces on the assets can have assigned the ip’s owned.

Edit Asset

Editing an Asset gives you the ability to alter the various values regarding the Asset. That could be the name, location and even the number of interfaces and the ip addresses connected to the interface. Each field that is not completely self explanatory has an help icon (icon: ) with supporting information on moving your mouse pointer over the questionmark. When clicking it a field in the top of the browser will show the same information – but stay until clicked..

There are many fields that can be filled out, and in some cases, with many different options. Some fields are self-explainatory, others have the help given as mentioned above.

Some elements may have multiple fields – eg. Licenses or Network Interfaces.

To add an interface line, click the button (icon: ).

To remove an interface line, click the button (icon: ).

View Asset

This is where you get all of the information regarding an asset. Remember, there is an “almost” hidden field – Passwords. Click to view them. (Not everybody looking at your screen need to know the specific passswords to any given asset). If your level of secrecy is below that of the password, the password will NOT be shown!

It is possible to set a Security Clearance level at a password under an asset. That is, if you are Cleared to view the passwords.


Listing of customers registered. Listing of a “sub customers” will show inherited data from the main customer, indicated by

You may choose a parent/main customer editing the customer. In the “List Customers” it will be shown as sub-customers. It can be used as a Customer with solutions connected instead.

Creating an asset requires an Customer name. Optional is an Alias or a Main Customer. After pressing “Create Customer” you are forwarded to Edit Customer, ready to enter additional information regarding the customer- See, Edit Customer.


The frontpage of Tickets gives an overview of RFC (Request For Change), Opened, Active and Closed Tickets. It is possible to go to Update Ticket by clicking the Update Ticket link (icon: ). If you think it is in need of being marked as Spam, click the icon (icon: ).

Default it will show tickets that is assigned directly to the current user and the groups the user is assigned to (Admin). It is possible to view another user or another group tickets (selected via pulldown). Clicking “My Tickets” alters the view to current user/group tickets.

A SLA (Service Level Agreement) can be connected to an asset or a customer. If the SLA is breached, an “B” will be shown by the Customer or the Asset.

It is possible to escalate a ticket to the leader of the creator of the ticket. By pressing the icon (icon: ) the ticket will be registered as escalated and a mail will be sent to the leader.

An ticket must be connected to a customer. A binding to an asset is not needed but it is known to be nice to have that connection. Requiered is Title and Description.

It is possible to nest tickets as master/slave tickets. You can create/edit an ticket and relate it to a master ticket.

Creating an Followup to an ticket is done by clicking the Update Ticket link (Icon) and fill out the Followup field. After that you need to assign the followup to a user or group. Or simply Close the Ticket.

Setting Ticket type to Request for Change (RFC) will show two required fields – Approver 1 and Approver 2. Selecting an Approver in the first field will fill the Approver 2 field with users, minus the user selected as approver in the first field.

Approvers will receive a mail with request to approve or reject the ticket.

The RFC will also be shown in the ITS for the approvers and the creator of the RFC.

Approvement status is shown by viewing the RFC.

Invoiceable : By clicking the checkbox, finance window pops up. If Finance System is activated, options to select Project and Activity is displayed.
Remember that users in Noah needs to have their Employee Handle set in their profiles (Finance ID)

Priority is calculated based on Urgency and Impact. These are editable in Configurations {Impact Types and Urgency Types}

Calculated Priority based on Impact and Urgency

Global Large Limitied Localized
Critical P1 P1 P2 P3 High P1 P2 P3 P4 Medium P2 P3 P4 P5 Low P3 P4 P5 P5

See Ticket Types

The Ticket Overview shows the users and how many tickets they have been involved in per week, month and year. Calculated time spent by the user combined in all tickets is also shown.

Creating an Followup to an ticket is done by clicking the Update Ticket link (icon: ) and fill out the Follow Up field. After that you need to assign the followup to a user or group. Or simply Close the Ticket.

If it is you that has created an followup, you are allowed to delete or edit the followup. Use the links(icons: or ) in the followup for this.

Optionally it is possible to link to an followup by clicking on this image:

That will give the complete url to the ticket and followup.

Noah Findings

Current Status of Noah and listing of found errors (there should be none )

This is where different “mismatches” or oddities in the Noah Database are listed. It should of course not be possible to have “mismatches” but it happens. Look here for something to amend.


Agreement Relation Purge

Once you have imported Agreements (and the relations to assets) this is where you may remove the relation between the imported agreement and assets. The assets will not be removed.!Warning! This is irreversible!


Create and edit Applications that your company has responsibility for.

Proof of entitlement is a person that has the responsibility for the reason to accuire the application.

Life span is divided into Perpetual and Non Perpetual. They may be based on an onetime license or subscriptional license.

Asset Stati

During a lifespan of an asset, from birth to death, it changes status.

  • Default Stati:
  • Unknown : Current status is unknown
  • Not In Operation : Asset could be mounted and powered on. It could be fully installed. But it is not part of production.
  • Switched off : Asset is without power.
  • Under Decommision : Asset is being removed from production.
  • Ready for Operation : Asset is in final test fase.
  • Ready for Deployment : Asset has been marked as fit for deployment.
  • In Deployment : Asset is being deployed with preparation for Ready for Operation.
  • In Operation : Asset is fully operational and is in production.

You may create your own stati and colorize/iconize them.


Definition of backup types. Adheres to assets or applications on how they are backed up.

No defaults.


It is possible for a user to escalate a ticket.

Escalation Administration is where you may define what to happen when a ticket is being escalated.

Options selected will be matched by the crontab/crontab_ticket_checks.php script. (so it needs to be running for this to work. See Crontab Scripts)


It is possible to do some lowkey imports into Noah. Be aware that there are limitations to the setup of import file!

You need to create an CSV-file (must be in CSV format seperated by , or ;) with the basic information. Spreadsheet programs like Google Docs, OpenOffice Calc and Microsoft Excel makes it easy to create and edit CSV files.

Import Assets

IMPORTANT: Your CSV-file must be formated as a table and included a header or top line defining the fields in your table.
IMPORTANT: Headers must be: customer_id, asset_id, asset_name, type_id
Most important is the matching of existing customers and asset types. If in doubt, look for the corresponding ID in either Customers or Types lists.

Follow the guide onscreen for valid data import.

These are the options for importing data:

– Assets

customer_id, asset_id, asset_name, type_id

Import Customers

IMPORTANT: Your CSV-file must be formated as a table and included a header or top line defining the fields in your table.
IMPORTANT: Headers must be: customer_name, customer_alias, customer_address1, customer_address2, customer_pono, customer_city, customer_primary_phone, customer_comment

Follow the guide onscreen for valid data import.

These are the options for importing data:

– Customers

customer_name, customer_address, customer_pono, customer_city

Import Agreement

IMPORTANT: Your CSV-file must be formated as a table and included a header or top line defining the fields in your table.
IMPORTANT: Headers must be: asset_serial, agreement_number, supplier_name, expire_date, responsible_id

– Agreement Data (Agreement with serialnumber)

The system will try to match the serialnumber with that entered in assets. If found, it will connect the serialnumber, agreement and the asset.

It will also create the Agreement(agreement_number) and/or the Supplier (supplier_name) if not already found!

asset_serial, agreement_number, supplier_name, expire_date

Mail Incoming

It is possible to make Noah fetch mails sent to a specific mail address and create tickets based on data in the mail. See Core Settings for additional setup options.

Mail Rules

Create rules for defining what to happen to mails received.

It is possible to select what Noah is to do with the mail based on the rule.
Archive Mail: Do nothing.
Create Ticket and leave ticket open:
Create Ticket and set to selected user: Select user in list.
Create Ticket and set to selected group: Select group in list.
Inform (cc): Send the received mail to set email address(user)
Forward Mail to: Send the received mail to set email address(user).


Marking a ticket as spam puts sender in the blacklist. All mails with sender will be bounced to ">dev\null".

NDocs - Noah Document System

One place for documentation

Reclaim Deleted

If you have deleted a document, it is possible to "undelete" it (if not purged already).

Purge Deleted

Purging the deleted documents will delete the permanently!


Operational Acceptance Test. A process to make sure an asset has validated settings and are ready for change of status.

OAT Templates

It is possible to create different templates of OAT - depending on the status change and the asset type.

An OAT is a set of questions or scripts to be run that needs to be performed and/or verified. The setup is, set an question (or script to be run), provide the option of freetext or Yes/No answer - and you may also suggest the correct answer/expected result.

The template will be activated upon request for change to an specific status on an asset with the specified asset type.


Where all your assets are..


Physical or Virtual places where assets are placed. Virtual locations can be used to group servers.


Positions = rack space.

Positions is areas within Locations.


Project Stati

Will display the current status of a project in project listing and view project..

Defaults are:

  • Awaiting customer
  • Awaiting design
  • Awaiting finance
  • Awaiting resources
  • Design ready
  • Handover done
  • Implementing
  • Information Gathering
  • Initial phase

These stati are set by the project manager in Edit Project.

Project Tasks

Every project consists of a set of tasks.
Initialy there is no tasks set to a project. You may add the first task by pressing Add Task.

Project Templates

Available from the Administration menu.
Create templates of projects defining sets of skills required or specific tasks set.

Now you have can create the first task by entering data into the fields.


Skills is a definition of what a user is able to handle. Skills are used in Project Skill Request - and probably other funtions in future versions of Noah.


IO Groups

IO Groups are segments in relation to Storage Systems.


Ah.. Tickets. It is the way of getting things done, tasks delegated and keep in touch with what is going on. Create RFC's getting control of your changes or just look for incidents created by API/customers.

Ticket Categories

A way to segment tickets.


  • Customer Created
  • Dev. Request : Request for development task
  • Hardware : An hardware issue has occured
  • Software : An Software issue occured

Ticket Types

A way to segment tickets.


  • Order - Order of Items
  • Backup Order - Order for Backup
  • Missing Items - Location of missing Items
  • Request for Change - An RfC - Request for Change - is when an incident is planned.
  • Customer Created - A customer has called in and claimed there is an issue
  • Surveilance - Surveilance has tagged an incident
  • Caffein incident - Any kind of caffein incident will do
  • Dev. Ticket - Tickets marked for Development

System locked Types are : Order, Backup Order, Missing Items and Request for Change.

Ticket Sub Types

Further segmentation of Ticket Types.

Defaults [Ticket Type]:

  • Storage - Test for storage [Request for Change]
  • SW Upgrade - Upgrading software on asset(s) [Dev. Ticket]
  • ITS - Development on ITS System [Dev. Ticket]
  • NDocs - Development on NDocs System [Dev. Ticket]
  • Asset - Development in the cmdb [Dev. Ticket]
  • TestSub - Test of sub ticket additional lines [Customer Created]

List RFC-PDF Saved Tickets

It is possible to get Noah to save your Request For Changes as PDF files on a given path. This is set up in Configurations / Core Settings / Save Closed RFC tickets as PDF

If no path is set, default path will be set (set in config.php) - Current Path is shown in header.



Agreements from Suppliers. Related to assets, circuit and licenses.

Remember to assign a responsible user to the agreement.


Alter the Asset types or even add a new.

Optional, choose which elements should be part of the asset type. These are the parts shown in ViewAsset and EditAsset pages.

Currently these parts are available:

  1. Administrative
  2. Licenses
  3. Passwords
  4. Local Storage
  5. External Storage
  6. HBA Interfaces
  7. Network Interfaces
  8. Files
  9. Domains


Circuits can be defined as connections between two endpoints.


Contact person related to supplier or customer.


Defintion of the brain of the computer.


Events are related to the Calendar. Optional to select icon and color of icon.


Items are related to users and items handed out. Eg. Cards, keys or other forms of items..

Used in User Equipment


Define service windows on assets, circuits or locations. Users will have the option to mark the Maintenance done. This will give a revision trail on the maintenance.

Operating System

System type installed to handle commands between applications and hardware..


Alter the Password types or even add a new.

Defaults are :

ILO: Mainly used by HP equipment

Root: main user name. Administrator on windows systems.

Snmp: password used to make snmp walks aso. on equipment.


SLA is short for Service Level Agreement. Ranges between Fix-time, Reaction-time, 2Hours, 4Hours aso.. It is possible to connect an SLA to Assets, Circuits or Customers. So when a ticket is created, the adhered SLA will be matched against ticket data.



Listing of users in Noah. Option to look into Admin, Edit or Responsibilities..

Admin : Gives the possibility to set group assignments, change passwords aso.

Edit : Gives the possibility to change some personel related features.

Responsibilities : Users may be responsible for domains, licenses and/or agreements. This is listed here. (Currently unable to edit from here.)


Get users to sign of on equipment received. Laptops, Cell phones aso.

Print Receipt for signing and upload the signed document for future ref.

User Groups

Giving one user a right is easy. But giving several the same right can be tedious. But assign them to a group and just give the right to the group. All users in the group inherits the right. It also makes it possible to message (tickets) several users in one go about the same ticket.


In Create Ticket you are able to select a predefined ticket type. It might be related to a workflow.

The workflow is created in Administration/Workflows. The events are drag and drop. On creation of a workflow, it needs to be approved before it can be used in the Tickets part. This also applies when you have edited a workflow.

The ticket you create - where the type is related to a workflow - will be created as a Master Ticket and the workflow will create and relate tickets to this Master Ticket. When the "subtickets" are closed, the Master Ticket will be updated with this status as a followup, and next subticket (workflow event) will be activated.

Job Functions

Definitions of Job functions for users in Noah.

Used specificly in Orders related to amount allowed for Approving.

Default Job Functions are :

  • Budget Manager - 10000 : Can approve orders up to 10.000
  • Budget Manager - 100000 : Can approve orders up to 100.000

Job Titles

Definitions of Job titles for users in Noah.

Selecting a title also displays a list of users with the corresponding title assigned.


System License

Get an overview of the licenses used for running Noah. It is possible to use more than one license – Noah uses all valid licenses entered.

Licenses name and License Key are required.

Crontab Scripts

Crontab scripts (placed int /scripts/crontab) that you may (de)activate and/or set to run on a specific time/interval.

Master Script (controlling the running of background scripts) must be set to run in the server crontab (AT scheduler on windows).

Unix example:
* * * * * /usr/bin/php /var/www/ > /dev/null

Some scripts are to be run at intervals:


Check for expire dates in agreements and sends an email to the responsible user.


Creating 2DBar images in /var/2DBarImages/


Reads IMAP account and creates or updates Tickets based on mail received.

The scripts looks for an TicketID indicator in the subject of the email. See Core Settings/Tickets/Ticket Indicator. Also, it looks for names/numbers that could match an asset, circuit or customer in the subject.

crontab_imap_ticket.php recieves mail from the mail server given in IMAP Host set in Core Settings/IMAP. Remember to select if the mails should be deleted after processing or not in the field “Keep Email”!


(Obsolete since 1.65 rel 01) Checks for an upgrade on and downloads the file if available.


Checks for tickets that has been breach according to SLA. Script will warn user of possible breach at set warning time and/or breach at specificed breach time (set upon creation of ticket based on found SLA). It will send an email to creator of email or the leader of that creator.


Various checks related to tickets. Reminders, handling aso..


Summarizes ITS stats. Fastest/Slowest Ack/Closure on Overview page.


Checks for Asset Warranty Expire dates. Sends an email to responsible for the asset..


Updates the Portal with data to and from Noah DB. Use in conjunction with enabling the Portal.


Checks for upcomming maintenanance windows and emails alerts within the warning time.


(Obsolete since 1.65 rel 01) Check for SNMP data. Uses the ip address and snmp login set in asset interfaces.


Looks into active and approved workflows and creates tickets based on criterias set in workflow tasks.


For every active user registered in Noah, update user data from LDAP server. Recommended running once dayly(default) or weekly.

Requirements for the AD user: Given name and Email is set.

Will also impact option for selecting Ticket Owner (who supplies the task/problem).


Creates reports and mails it to the user requesting in selected intervals.


(Work in Progress) Scans requested network segment (set in Edit IP Segment) and puts responding hosts into a database table.

It is possible to de/activate each script and set various intervals and time to start.

Core Settings

Basic settings for Noah. Includes

- Password expire period : If set to 0 (null), users password will not expire. Otherwise the password will expire after “set” days. (if you set it to 90 – users passwords will expire after 90 days.)

- Superuser email : Noah sends alerts aso. to this email.

- LDAP : ldap host, domain, user and password may be set to connect via an LDAP server (Open Ldap and Microsoft Exchange 2003 tested).

Optional for uploading your own logo. The viewable field is locked to 25pixels in height.

Enclosure Templates

Predefine enclosure setups. Simple "Row/Column" setup on the front and back of the enclosure..

PHP Info

Shows the current PHP setup running on the host. Noah currently supports PHP version 5.x and 7.x.

Portal Rights

Sets file rights for portal access.


Administrators need no file rights. But users/groups may be allowed to only access certain parts of Noah. Eg. Salesgroup need not to alter an asset, but may alter a customer. Note: If you have access to edit something. You have access to delete it also. Access to portal is set via Contacs

Rights Group

Create / Alter groups for rights assignment. Makes it easier to assign rights to users/groups.

Rights Templates

Templates used in assigning individual rights to users. Gives a better overview.

Security Types

Used to differntiate users towards security levels on customers. If user does not have the same Security Type as the customer, the user may not see information regarding the specific customer.

Status / Log

An error log for those errors that should not be there..

Incoming Mail

List of emails reveived via /scripts/crontab/crontab_imap_ticket.php

Left Menu (Main)


Your default frontpage with optional windows of data.


View your calendar, alter which users are included in the calendar or select your default calendar.

Impact View

When an asset is rendered unusable – or just broken down – it is often a tedious task to get an overview over what other assets are impacted. This tool gathers the information already registered (interface connections registered / Parent/Child relations) and locates the impacted assets, showing them in a treeview parted in the related segments (Storage/Network aso).


In the Documents (NDocs) part of Noah, it is possible to create documents, attach files to the documents and folders. It is also possible to create/edit folders and put documents and attached files into the folders.

Selecting a folder:

Selecting a folder in NDocs is based on a dropdown menu. In the dropdown the Main folder (exept the root folder (marked by a + (plus) sign) are marked with a * (star) sign.

Ordinary folders are marked by a – (minus) sign.

Uploading of files:

After a selection of files (or one file) the upload will start immediately. So remember to enter a comment and selecting a folder / document before selecting files. After the upload, alterations to the comment aso. is not possible (or will have no effect).

Selecting a folder will alter the select a document list with the documents currently in the selected folder.


Currently the following stats are available:

  • Assets created per week
  • Customers created per week
  • Tickets Closed per Group per Week
  • Tickets Open / Closed per Week
  • Tickets Created per Week
  • Tickets Closed per User per Week
  • Tickets Escalated per Week


Get an overview of the registered users, click their username for more details.

Left Menu (Functions)

Address Book

List of addresses possible to use as delivery addresses..


Get an overview of the agreements available with their expiredates and suppliers.

An agreement requires an supplier. So remember to create a supplier first.

Choose an responsible user. The user will be alerted by mail when the agreement is close to expirering (1 mail within a month, 1 mail within a week and one mail a day before expiry)


Applications are registered and related to Customers, Assets, Suppliers or Licenses. Applications are related to environments and users - this to register compliance with Segregation of Duty.


Backups are defined as backupsystems related to Assets and/or Customers.


Get a list of current registered circuits.

A circuit is defined as a connection. That is, it can be anything from a physical PSTN line, a ADSL connection to a vpn connection. The circuit types are administerable in the Administration menu.

Set an A and B fix point for the circuit. It could be an asset, a customer or just a simple comment.


A list of clusters registered with their nodes and shares.

Use the +/- sign to toggle the Nodes/Hosts and Shares connected to the Cluster.


There is a procedure to go through here:

A cluster contains two or more nodes (assets registered as anything but Cluster) and usually some shares (storage to be shared by the nodes).

The process is in two stages. Assigning an asset as a Cluster. Then, using the assigned “cluster” asset, creating the cluster.

Before creating a cluster, remember to assign an asset as a Cluster.

(if not already done) First, create/alter an asset with the type “Cluster”.

Second, in Create Cluster, select the customer under which the ClusterAsset is registered. Next, the Cluster Types Assets will be shown in a dropdown box. Please select the asset and click Create Cluster. Now it is possible to assign nodes (edit the node assets and select the just created Cluster as “Cluster master”) and Cluster Shares – created in Edit Cluster.

Creating a cluster starts with selecting the customer the cluster should be assigned to. Then select an Asset to assign as “Cluster”.

After that, select the cluster you just created in Edit Asset on the assets you want to add as nodes.

Cluster Shares

Cluster Shares are added in Edit Cluster which is found in List Clusters or by link in View Assets (if it the asset is a cluster). Assigning Storage to Shares is done in two tempi. First by assigning External Storage to the cluster asset in Edit Asset. Then by Edit Cluster and there select which External Storage source is to be used as a Share.

Disksystem and Diskgroups

Assigning Lun’s or Vdisk’s is started with an asset that is defined as a disksystem (Asset Type). After this is created, it is possible to assign diskgroups to this asset in the Storage menu. This is also where you may list the disksystems with attached storage guests (Lun or Vdisk assigned.)

Creating a diskgroup requires the above step done (a Disksystem created as an asset). It is possible to assign a name to the diskgroup, disktypes (FiberChannel, SATA aso.), speed of the disks and Raid type (0, 1, 5 or 10).

Assigning external storage to an asset requires a disksystem/diskgroup to assign storage from.


Get a list of all registered contacts and their data.

Set portal rights for contacts (requires Portal enabled in Configurations/Core Data)

Customer, Name and Email are required fields.


Get a list of all registered Domain names and the connected customer.

When creating a domain, write only the domainname in the appropriate field. The Icann List is used to select the icann notation. (that is, .com, .net aso.)

As an option, it is possible to connect a domainname with an asset and/or a customer.

Assigning a customer to a domain will - if enabled - make Noah look for customer related to domainname set in From: email received (crontab/crontab_imap_ticket.php)


Enclosures are units that can contain a number of blade servers.

They are created (as templates) in Configurations/Enclosure Templates and as units/assets in Create Enclosure.

It is possible to assign assets to both slots on the front and on the back of the enclosure. This is done from the View Enclosure page by clicking the clip shown:


Some pre-defined extractions are created. Combine them with further selections and create specific extractions. Save the extractions for later re-use. The result of the extraction will be saved as a CSV file. Perfect for importing into eg. “Excel” or “Calc” for further manipulating.


Customer Extraction

Ticket Extraction

It is possible to extract ticket data based on several search options and ticket options. After extraction is created, it is optional to export the table to Excel by pressing the button .

Creating an Extraction gives you an opportunity to vary your selection. Below are listed some of the possible Extractions and their Options.

“Asset -> OS Types” : Display Assets running a specific OS type. Choose OS type.

“Asset -> Created Dates ” : Select Assets created between two dates. Choose Dates.

“Asset -> Locations” : Select Assets from a specific location. Choosa a location.

“VLAN -> IP” : Get Customers IP addresses connected to VLANs.

“IP -> Asset” : Get Assets with registered IP addresses connected to VLANs.

“Circuit -> Locations” : Display Circuits from specific location. Choose a location.

“Clusters -> Shares” : Display Clusters and their Shares. Select a customer to narrow it down to one customer only.

“Asset -> Asset Types” : Display Assets based on a specific type.

“Asset – Asset Location” : Display Assets without location/position assigned.

“Inactive Assets with License” : Display Inactive Assets with License(s) still assigned.

“AssetData for 2D Labels” : Extract Asset data for labeling with 2D Bar.

“Asset -> CPU Types” : Display Assets with a specific CPU type.

(List can be expanded per version.)


This is where you select the customer and areas needed to export. It will create an csv file (comma delimited file) viewable in the Extractions List.

Creating an Extraction gives you the option to save it for later use. This gives a list over the saved Extractions.


Collecting solutions in tickets builds up a knowledgebase of - knowledge. Here is the option to list and edit the entries. The list is populated by marking a Ticket Followup as an "Solution".


Get an overview of your registered licenses. Under each asset, it is possible to register the usage of licenses.


This is a representation of the physical address/place.

– Positions

This is a representation of the physical place in a Location (above) – it could refer to floor/rackspace.


Get a list of Maintenance/Service windows..

It is possible to create Maintenance/Servicewindows for handling infrastructure(up/downgrade / reinstallation / moving hardware and much more). This way you may be reminded of the task and others may be able to relate downtime to the window.

Recurrence as well as RACI is optional.


Create and mark an IP segment for a specific customer and / or VLAN.

Update the segment with new data, split or merge super/sub nets.

Overview of the registered Vlans with their IP Segments and customers assigned. Also the assets with interfaces using the vlan is showed.

VlanID is a required number field in the range 1-65535.

Assigning vlans to ip segments is done in Edit IP Segment, available in List IP Segments.


The OAT is activated when an request for changing the current status of an asset is performed (edit_asset.php).

Initially it is an process for securing the validity and readiness of an asset before it changes status.
An OAT includes questions and/or scriptlines to be answered / performed to be validated. You may respond with the result in the OAT. Until it is submitted, it is editable. On submitting the OAT, an ticket will be created with the category "OAT Ticket" and sent to TicketOverview as Open. A Handler (another user of Noah set in the OAT Template) will be assigned the ticket where the OAT will be evaluated and Approved (and the status change will be performed) or Rejected (status will not change).
Upon either Approval or Rejection, an PDF will be created, stating the OAT lines and Aprroved or Rejected. This PDF will be attached the ticket.


The main page gives a list and status of the current open or closed orders.

Creating an order requires the knowledge of who is supposed (not a demand) to deliver the item(s) and who are supposed to purchase and receive the item.
The order is created with an budgetmanager appointed (required). Look at Job Functions for setting the Budget Manager approval level.
Budget manager receives a mail with the option to approve or reject the request.(And a link to the order where it is also possible to approve or decline the request.)
If approved, the order will be marked as approved, creator of the order as well as Purchaser will receive a mail stating the approval.
If rejected, the order will be marked as rejected, creator of the order will receive a mail stating the rejection.
if the order has been approved, purchaser(s) will receive an email giving the approval and link to the order, stating it ready to purchase verification.
Items are being verified purchaseable - delivery time, pricing and correct items verified - and purchased.
Items are received - and marked as such by whom ever receives the item(s). The Receiver is responsible for confirming the receipt.
Order is marked as Complete by creator and as such ready for closure or invoicing.


An order has 6 stages defined:

Budget Descision :: Stage: Order is due to be Approved or Rejected based on budget, need/nice to have or any other reason.
Verification from Purchaser(s) :: Stage: Items are being verified for purchase. Eg. are they available, is the price correct aso.
Purchased :: Stage: Item is being purchased and should be enroute.
Item(s) received :: Stage: All items have been received.
Order Complete :: Stage: All items has been marked as received and order has been completed - Master ticket and all subtickets have been closed.
Rejected :: Stage: Order has been rejected.


Projects is larger tasks that is split in smaller tasks. Each small task is created as a Ticket.




Creating a SLA (Service Level Agreement) giving the breachtime in minutes. It will affect those assets/customers assigned the SLA. If a ticket is created with an customer or asset that is assigned a SLA will be marked with a “B” indicating a SLA breach. The “B” is also a link to the SLA for comfort.

It is possible to “ACK” a breach of the SLA – removing it from view. The breach will not be removed from statistics aso!


Get a list of the registered Disksystems and diskgroups with their connected assets

– Create Disk Group

Before creating a DiscGroup, remember to assign an asset as a DiskSystem.

A diskgroup is a collection of disks in a disksystem. Hense you register what kind of disks are in the group (size, speed aso).

Currently the disk options are :

Speed: 7,2K, 10K(default) and 15K

Type: ATA, FATA, SATA, FC(default), SAS, SSD, USB and SDD

Raid: 0, 1, 5(default), 6 and 10


List over suppliers of agreements.

Enter supplier values as address, zip code aso. Remember the emailaddress for their dispatch/support aso.

You will also see a list of the agreements the supplier has made.


This part is mainly used to permit access to the portal (still to be documented) and serves as a list of persons that are allowed to create tickets on behalf of the customer(s) the contact is connected to.

The crontab script crontab_imap_ticket.php looks for contacts when parsing received mail if the Core Settings setting "Everyone allowed?" is unchecked.

Export Settings

The supplier may have the need to gain access to the API in Noah. This is where you allow the access to an IP/URL with an autherization token. (See API page for details.)

Try Noah or register for Cloud