8.

1 General Principles and Requirements

8.1 Statement of Work
Company expect contractor to apply best practices and expertise to meet
maximum requirement through standard system instead of Customization.

8.2 Integration with ERP system

The new system must integrate with Companys Navison ERP
system (Navison 2009 R2 customized, with 2 x NAS licenses
available) and provide components that will allow bi-directional flow
of customer, customer contacts/actions, orders, license, product
price and availability, demo/content downloads and support tickets.

All communication between the site server and the ERP system
shall be encrypted using SSL (HTTPS).

8.3 Multi language

Any component must be capable of managing and presenting data
correctly in any language, and convert characters correctly to
Navision and any back-end system.

8.4 Multi-currency
Any component must be capable of managing pricing in multiple
currencies across multiple markets and be able to process orders
using new EU VAT rules for selling of digital services.

8.5 Registration, Authentication and Authorization

Must be flexible and extendable to provide support for multiple
access management federations
(https://en.wikipedia.org/wiki/Federated_identity, predominantly for
education/government sectors in the United Kingdom, Germany,
Austria, Ireland, Norway, Sweden, Finland and Denmark) as well as
traditional authentication and authorization of internally stored
account data for commercial clients. Suggested solution would be
https://shibboleth.net. Also allow for customers to login via social
accounts such as Facebook.

New registrations need to be associated as far as possible and as

automatically as possible with the correct Company legal entity. If
company, via email address domain cant be associated with an
existing Navison account then use address lookup web service at
least ensure accurate address and company information if
applicable.
 8.6 Design
Design must be optimized for speed (fast), and fully responsive to
meet the view ports of all device types. All client side
HTML/CSS/JavaScript must be standards compliant and cross
browser compatible. The minimum browser requirements are still
to be decided.

8.7 Software
The platform shall be the latest applicable version of Magento
2.1.3. Where possible Company would like to use standard well
supported software components to provide the core functionality
and where possible to extend these software components using
either existing plugins and connectors or those written for specific
tasks using the supported APIs of the core software components.
Where possible Open Source software or perpetual commercial
licenses with no on going licence or support and maintenance
costs would be preferable. The more flexible and manageable
connector and/or extension shall be preferred.

8.8 Multi-Company/Country
The Website must seamlessly switch between Company
companies based on customer identification or selected country,
and able to present company specific headers, footers, about
pages and country specific product portfolio, currency, and
pricing. Each company have a unique Merchant ID and shall have
the most fail-safe/integrated/customer friendly payment solution
from our provider DIBS. Technical information to be found here:
http://tech.dibspayment.com/D2

8.9 Cookie Management

Must support Cookie privacy management.
 9.1 Functional
Requirements
Basic site overview as
follows:

BASIC SITE
STRUCTURE
Home Newsletter Sign Up Form
(Select Country/Language (Company (Available on home page and product pages
Company/Currency/ product portfolio) initially will send data direct to email marketing
based on domain or IP Address) management system)

Products
Select top level Training and Support Company
product Events
category

Product Training & Events Downloads Contact Us

Category Categorized by (See Downloads Office details
Lists products product category. /Demos/Resour and contact
within category Click through to ces Workflow) form
single event page

Knowledge
Base
Product Detail Event Detail Listed and
Description About Us
Description Categorized by
Information Start and End product
News Date category. Click
Details Available Places through to single
License Options Price
Video Location
Link to Training Speaker
Support Hours News
Product Selection Listed and
Wizard (See Support Categorized by
Ecommerce Tickets product
Workflow) Event (See Account category. Click
Registration Management through to single
(Form to capture Workflow) new page
attendee data)
Connect to shop
for payment
where necessary Search
Must be a
global search
across main
site, shop,
downloads and
knowledge base
 9.1 Company Information
Provide for the management and presentation of general
company/information pages and contact us form.

9.2 Training and Events

Provide for the management and presentation of training and
events. Staff must be able to manage events easily and efficiently.
Customers must be able to browse and search for events by date
and by product category. Customers must be able to register and
pay for training and events online. Registration data must be
captured, emailed, and stored.

9.3 Ecommerce
Each Company company have individual merchant IDs.
Ecommerce component as previously stated must be able
to cope with multiple languages, currencies and
territories.
Support for current international rules regarding VAT.
Support for business to consumer transactions via debit card,
credit card, PayPal, and multiple other payment methods. If
PayPal, then customer must provide their PayPal email
address.
Automated ESD feature of site to be kept in sync with
Navision License Registry, where applicable.
Support for business to business transactions via purchase
order, credit card, PayPal, Invoice, and multiple other payment
methods. A customers discount profile and payment terms to
be based on Customer profile in Navision and applied to online
transactions.
Consumer shall be able to choose between opening an
account or one-time purchase without creating account.
Benefit of account like storage of license keys and access
to installer to be promoted before/during choice.
Support for promotion codes from both print and digital
marketing.
Order history including access to license information and
download links where appropriate.
Pricing to be updated on a schedule from ERP system.
Orders to be processed on a schedule and passed through
to ERP system.
Customers chosen Organization Type and Platform settings to
be stored and applied to future purchases, cross-sell and up-
 sell purchases.
One-page checkout.
The following page is a good example for one-page checkout,
the cross-sell and up-sell feature to be used on our website:
https://www.idera.com/buynow/cart?pid={525edc81-1049-
4459-ac7a-c1236cdcbc6a}
 The following page is a good example on sales-
oriented tiles to be used on our front page. A buy
option need to be added to the tile.:
https://www.idera.com/productssolutions/sqlserve
r
9.4 Ecommerce
Workflow
9.5 Product
Selection Wizard
 9.6 Product Selection Wizard mock-up

Product Selection Wizard (PSW) mock-up

Notes:
Mock-up only an
example. Published
PSW should be
different.

Selection grouping to
occur on mobile phone,
if needed.

When previous selection

makes an option un-
applicable then the un-
applicable option shall be
greyed out/un-focusable.

Some options shall have

the function of changing
the Add to cart button to
Contact us and link to a
Contact us form or
Contact us email
address.

Displayed definitions
could be a fixed frame or
a floating tooltip textbox.
Whatever works best on a
mobile phone.
9.7 Batch Order Process
Workflow
9.8 Batch Abandoned Basket
Process Workflow
 9.9 Account Management
Login to view account details.
Edit account details. Invoice address will not be editable if an
existing customer with a fixed or mandatory invoice address
in Navision ERP (Bill-To Customer Card).
New users given option to be connected to existing company
cards based on email domain.
Allow for email invoice address, for pdf invoice.
Allow for electronic invoice by checkbox in applicable
countries (customer must submit electronic invoice ID)
View order history. License details and download details to be
available from Navison ERP customer data.
Two step email verification for new customers and contacts
(see Ecommerce workflow diagram for login and registration
workflow).
Create and manage support tickets.
Accounts to be kept in sync with Navision
Support tickets to be kept in sync with Navision Support
Registry Table. Automated renewal reminders including
renewal quotes generated from Navison license registry table.
Information includes expiry date, item number and renewal
price.
Admin/super user account capability (for Customers with
many accounts who place purchase orders individually).
Admin/super user account to be designated by Company in
Navision.
9.10 Account Management
Workflow
9.11 Batch Account
Management Workflow
9.12 Batch Support Ticket
Process Workflow
9.13 Downloads/Demos and Resources
o Clients can browse and download software trials,
brochures, white papers and other documents.
o Login and register to download files and other
resources. Customers must accept the privacy policy
to download.
o Download interactions to be recorded and sent back to
Navision (Lead Registry Table) and email marketing
system. Email address, title, first name, surname,
language and country are a minimum requirement.
o Demo downloads must be published in such a way that
they do not infringe/breach Google Adwords policies.
(https://support.google.com/adwordspolicy/answer/6023
676?hl=en#354)
9.14 Downloads/Demos and
Resources Workflow
9.15 Batch Downloads/Demos and
Resources Workflow
 9.16 News
Provide for the management and presentation of news articles.
Staff must be able to easily and efficiently manage news, press
releases and other communications. Customers must be able to
browse and search for news by date, product category, country
and market.

9.17 Search
While it is anticipated that various applications will make up the
complete system it is vital that search functionality is global and
intelligent and that it will recognise the difference between a
product and a download for example and be able to display different
meta-data for different results types and to display results based on
market and language selected. Search should also be able to
manage related keywords and should be able to return suggested
(by Company) results for specific keywords. Searching for Endnote
for example will return top links for core purchasing product page
and for downloading a trial in the same way that Google returns
sponsored links. Search history must be stored and available for
analysis.

9.18 Newsletter sign up

Site must include access to a newsletter sign-up form that will be
able to send data to a specified email marketing management
system on sign up.

9.19 Knowledge Base

Provide for the management and presentation of knowledge base
articles. Staff must be able to easily and efficiently add and edit
knowledge base articles. Customers must be able to browse and
search for knowledge base articles by date and by product
category.
10.1 SEO and Social Media
SEO Friendly URLs.
Retain good existing page rank using redirects where
necessary. Automated breadcrumbs.
Editable SEO metadata for all data components including
pages, products, downloads, news and knowledge base
articles.
Generate XML site map for Google Webmaster.
Google Analytics including ecommerce integration and other
conversion goals.
Integration with Social Media where appropriate.

11.1 Data Migration

Data will need to be extracted and transformed where
possible from existing systems.
12.1 User Experience and Design

Company would like the design and user experience to focus on a

tiled/grid system. The diagrams below are purely for illustration.
Designs and wireframes across major responsive breakpoints will
be required to be developed as part of the production process.
13.1 Copyright and Intellectual Property
Ownership of all assets including content, imagery and any
software components, plugins and connectors written specifically
for the project will remain the sole ownership of Company AB.