What We Do

01. Co-ordinate

02. Correct

03. Collaborate

04. Connect


[custom_works template=”one_fourth_gallery” effect=”grayscale” hide=”date,author,comments-link,categories,tags,button-1″ entry_ids=”2339, 2347, 2377, 2383″]

[/custom_works]

[divider style=”none”]

[/divider]

Our Business Process

01. Engagement

When a customer first engages NEDSS, we hold an introductory meeting to determine what you wish to achieve and your requirements/business objectives. This also gives you, the customer, an opportunity to learn more about what we do and how our products and services can benefit your organisation.

[frame linking=”lightbox” link=”” align=”center” style=”simple” shape=”square”][/frame]

[one_sixth valign=”top” animation=”none”]

[/one_sixth]

02. Site Assessment

Following on the initial meeting, a NEDSS consultant will then perform a site visit in order to evaluate the customer premises or existing system. Site assessment may entail a building/premises walk-through, equipment checks for specifications, operation parameters and current outputs and documentation via text, images and video recordings (with customer’s permission).

03. Design

The next step is to plan and design a solution that best fits your needs, a process which is always undertaken by NEDSS and AVAYA engineers to ensure you obtain the best possible solution. We utilise an iterative methodology and as such, solutions presented to the customer are tweaked and improved upon, with your feedback, until final approval.

[one_sixth_last valign=”top” animation=”none”]

[/one_sixth_last]

[frame linking=”lightbox” link=”” align=”center” style=”simple” shape=”square”][/frame]

04. Implementation

For largescale projects, solutions are developed and tested in a simulation lab environment before implementation and configuration in a live production environment. A project plan is then developed, outlining roles and responsibilities of each party in addition to the implementation strategy. A final meeting is held to ensure that all criteria are met and determine cut over date, after which your solution is implemented, tested and users trained.

[divider style=”simple”]

[/divider]