Markinson Software

Solutions
Unibis Hosting and Support Options for Consideration

Internal
After discussions with Jyothish Kunhambu over the last 4 weeks, Markinson have been asked to investigate several
options (summarised below) around the hosting and support of Unibis and Progress.

Please note, we are proposing a hosting service, not a SaaS model.

Option 1
• Markinson to provide Infrastructure and DBA Support only to TOLL’s current UNIBIS system

Option 2
• Markinson to provide Level 2 Helpdesk Support, with Level 1 remaining with Toll

Option 3
• Professional Services to migrate the current on-premise installation of Unibis and Progress to a cloud instance
(AWS or Azure, owned and managed by Toll)

Option 4
• Hosting of Unibis and Progress in a cloud offering owned and managed by Markinson (based on Azure)
• Professional Services to migrate the current on-premise installation of Unibis and Progress to the Markinson
Cloud
2
Internal
Option 1
• Markinson to provide Infrastructure and DBA Support only to TOLL’s current UNIBIS
system
• Currently estimated at approx. $100k p/year
• Secure remote connectivity and authentication will need to be pre-configured and
approved
• The exact scope and responsibilities will need to be agreed
• Estimated pricing has been based on the current SLA’s (see snip)
• Response time as agreed SLA
• Support hours are 9-5 Monday to Friday. Australian Eastern Standard Time
(AEST)
• Weekends and Public Holidays excluded
• Support outside these house can be attended to if critical and necessary at an
extra cost.

3
Internal
Option 2
• Markinson to provide Level 2 Helpdesk Support, with Level 1 remaining with Toll
• Approx $200k p/year
• The Toll L1 helpdesk to contact Markinson L2 support
• Current process for raising helpdesk tickets to be enforced and managed by Toll
• All helpdesk tickets to be recorded and tracked as per the current Markinson portal.
• Response time as agreed SLA
• The exact scope and responsibilities will need to be agreed
• Existing process and documents defining the work done by Capgemini will need to be provided and
reviewed
• Estimated pricing has based on the below:
• Support hours are 9-5 Monday to Friday. Australian Eastern Standard Time (AEST)
• Weekends and Public Holidays excluded.
• Support outside these house can be attended to if critical and necessary at an extra cost.

4
Internal
Option 3
• Professional Services to migrate the current on-premise installation of Unibis and Progress to a cloud instance
(AWS or Azure, owned and managed by Toll)
• Approx cost $180k, based on time and materials
• A platform migration will need to be performed as neither AWS or Azure offer Solaris as a supported
platform
• Will require the setup and configuration of multiple environments as per current TOLL infrastructure.
QA, EVAL, DR, PRODUCTION.
• Each Environment will require mixture of Linux and Windows.
• The TOLL database will need to be dumped and reloaded due to different platforms.
• Will require the mirroring, configuration, setup and testing of fallback Disaster and Recovery
mechanism.
• Toll will need to provide Markinson with either the documentation or provide assistance to identify and
define the current integration services, as Markinson were not involved in either the development or the
deployment of these services.
• We would also need to understand the availability requirements (from the business perspective) to schedule
and co-ordinate the downtime required for the migration

5
Internal
Option 4
• Hosting of Unibis and Progress in a cloud offering owned and managed by Markinson (based on Azure)
• Cost is approx. $120k p/year.
• VPC, secure VPN tunnel back to Toll network. We would not expose the servers or services to the internet
(unless Toll directed us to do so)
• Infrastructure would be Linux and Windows as Solaris/Oracle isn’t a supported operating system by
either AWS or Azure
• HA, redundant config with primary DC in Sydney and DR in Victoria
• Multiple UNIBIS Environments as current setup. QA, EVAL, DR, PRODUCTION.
• The TOLL database will need to be dumped and reloaded due to different platforms.
• Will require the mirroring, configuration, setup and testing of fallback Disaster and Recovery
mechanism.
• Markinson to manage the Application Patch and upgrade installation deployments.
• Markinson to actively monitor the application and infrastructure with OS and DB monitoring toll and take
proactive measures if necessary to maintain the system working at an optimal standards.
• Support tickets be logged by TOLL and ticket communication to continue using the current Markinson
portal.
• Ticket responses and escalation as per current SLA.
• Admin tasks – setup of new users, roles and security levels with an appropriate Workflow approval
mechanism

6
Internal
Option 5
• Markinson to provide Infrastructure and DBA Support (Option 1)
• Markinson to provide Level 2 Helpdesk Support (Option 2)
• Professional Services to migrate the current on-premise installation of Unibis and Progress to Markinson Cloud
(Option 4)

Summary of Investment for Option 5

• Infrastructure and DBA Support $100k p/year
• Level 2 Helpdesk Support $200K p/year
• Cloud Hosting (Azure) $120k p/year
• Professional Services for Cloud Migration $180k One off

7
Internal
 Secure Virtual Private Cloud to Customer Network
2

1 Markinson Staff (Support &

Professional Services)
6

2 Primary Network in Australia

4
Backup South-East. Network has no
Azure Bastion public facing endpoint.
7
Network

3 Secondary Network in
Australia-East. Network has
no public facing endpoint.

4 Azure Bastion Network that

Database Server Application Server grants access to Primary
Network Resources via
1 Azure Portal

5 Azure Bastion Network that

provides access to
Markinson Staff Secondary Network
VPN Link
Resources via Azure Portal
VPN Link
Customer·s 6 Failover group for
VPN Gateway Application and Database
5 3 Servers
Azure Bastion
Network 7 Customer·s On-Prem
Network

Database Server Application Server

8
Internal
 9
Internal
Assumptions
• All costs are estimates only and in AUD ex GST
• Minimum term for hosting or managed services is 3 years
• Draft hosting agreement is attached
• I would also suggest that we investigate the options of entering into a new support/maintenance agreement as
the current one is quote old and based on the ComOps original agreement.
• The proposal to be overseed and managed through a Project Manager with clear tasks and milestones.

Proposed way forward

• To enable us to firm up the scope, requirements and pricing, I would like to propose a Pilot.
• The pilot would include:
• A migration from the current on-prem to Markinson Cloud, including a platform migration to Linux and
Windows
• Uncovering and documenting the current integration services
• Configuring the integration services to run from the Microsoft Cloud
• Extensive UAT, performance and DR testing
• Timing of the above activities to enable us to understand and manage resources and downtime for a
production move

10
Internal