Solution Specifications (Section 7) - CCS Response

Construction Computer Software
7. Response to Solution Specifications

7.2 Solution Specification

In detail, describe the solution that will be deployed to support the business specifications, solution
specifications and business requirements noted in this RFP. Include, but not limited to:
Core functionality of the solution and alignment to business specifications, solutions specifications
and business requirements
CCS Candy and BuildSmart together include modules for estimating, planning, valuations, forecasting, cash flow,
procurement, accounting, wages, plant, yard and stock management and document control. What distinguishes
CCS from all other software offerings is the degree of interconnectedness of these modules. BuildSmart is unique
and sets itself apart from your typical general accounting ERP systems in that it is pre-customised and designed
to intrinsically cater for the unique demands of the construction industry where information is project based, needs
to be tracked by activity as well as cost type, is being produced and processed in many different locations, and is
needed by management in real-time for effective cost control.
This highly scalable system seamlessly integrates all functions and stages of the construction processes and is
entirely focused on and designed for construction. Because the construction process is unique, complex and
organic, and more crucially because CCS has developed and perfected this system for over 30 years through a
highly interactive and consultative process with the industry, CCS manages the numerous links between all
functions and all the people involved in the construction process in a systemic way based on how these things
were done manually.
Business Development, Estimating & Tendering, Award
CCS Candy encompasses integrated Estimating, Planning, Forecasting, Cashflow, Valuations and Earned Value
components designed from the bottom up by construction engineers to perform and execute these functions in a
way construction people understand.
The CCS solution kicks off with Candy Estimating.
Free format, resource based, analytical, direct and indirect cost estimating produces the estimate against a bill of
quantities, schedule or rates or taken-off drawings. The estimate is the foundation of control for the entire life
cycle of the project, forming the original budget or allowable of expenditure, manpower (including subcontractors),
equipment, material and wastage against which the project performance will be measured.
The estimate linked to a construction schedule or program, provides invaluable and accurate forecasting, cash
flow and procurement scheduling baselines for comparison against throughout the project duration.
In Candy, the estimate only ends at final account. After award of the contract and before the first monthly
progress claim on site, the estimate is re-modelled by the project delivery team and/or estimators to produce more
accurate allowances based on the latest information, drawings, addendums, methodologies, prices and
quantities. This linked to a schedule then provides the essential baseline budget and planned performance for the
contract as well as invaluable procurement data in terms of quantities and value allowed to be procured as well as
equipment, subcontractors and labour requirements and targets.
Candy includes a comprehensive reporting system for each of our modules (Estimating, Planning, Forecasting,
Cashflow and Valuations) for customised and analysis reporting on any and all data entered in Candy. OOB
Candy caters for the majority of reporting requirements, formats and content through its versatile report Manager
facility. All reports can be exported to Excel easily and seamlessly for further customisation if necessary.
Operations
Monthly, measured work done is recorded and quantity, resource and value budgets to date are compared to
forecast and actual costs (including accruals) incurred to date. This budget and cost data is used in the
calculation of accurate cost to complete and cost at completion values at any stage of the project.
Post tender, Candy uses the same estimate as a basis for valuations, variation pricing, applications for client
payment and payment of subcontractors. Candy forecasts costs to and at completion by adjusting resource costs
as the contract progresses, providing essential comparison between historic and future costs and budgets.
The two essential key performance indicators of any construction project accurate and substantiated schedule
and cost variances are effortlessly produced for the integrated Earned Value module.
This single package system can be used by most construction related staff within your organisation:
measurement and take off clerks, estimators, quantity surveyors, cost controllers, planning engineers, commercial
managers, construction managers, site agents, and project managers. Many different work disciplines all use
parts of the same software, so you get standardised, consistent inputs and outputs, accurate analyses and
attractive, informative and timely reporting.
Procurement, Finance. HR and Administration
Buildsmart has been designed for the sole purpose of construction accounting. It has been built around the
construction business process so as to produce accounting information, rather than trying to adapt a system
designed for general accounting to the unique demands of construction where information is project based, needs
to be tracked by activity as well as cost type, is being produced and processed in many different locations, and is
needed by management in real-time for effective cost control.
Construction companies have historically had great difficulty in bringing together Costing, Project accounting and
Enterprise accounting, so much so that many believe this is impossible. Buildsmart has been designed with a
very powerful central SQL database to fully integrate all cost related information for the first time.
Full integration between such different functions as Costing, Procurement, Project Management, Project
Accounting, and then Enterprise Accounting is made possible because information is carried in sufficient detail to
permit the information to be recompiled for the specific needs of each set of users within the construction
organization.
As an example, while estimates are produced using complex resources at whatever level of consolidation the
estimator may find most helpful, each complex resource is built on worksheets that break down each complex
resource into the most basic simple resource level. This then allows detailed resource planning, the forwarding
of shopping lists recompiled for procurement, and then later the management of purchase orders, delivery
notes, invoices and payments as each are reported in real-time to the project and enterprise accounts.
All costs are managed in this same way, from Labour with a full payroll module, to Plant and Equipment, Stock
and Yard Stock, even your own manufactured items. BuildSmarts cost accounting system uses four integrated
ledgers (Contracts, Overheads, Plant & Equipment, and Balance Sheet) instead of the typical two, and the coding
structure carries task/activity information along with cost type. Systems without these features can never provide
the kind of detailed information that is required for effective management control.
Details of all software modules that will be deployed
Candy
Candy Estimating
Candy Planning
Candy Forecasting
Candy Project Cash Flow
Candy Valuations
BuildSmart
BuildSmart SmartQuote eRFQ
BuildSmart SmartBuy Procurement
BuildSmart SmartAct-Accounting
BuildSmart SmartPay - Payroll
Partner Products
SmartBI-Business Intelligence
SmartDM Document Management
SmartHR Human Resources
Smart - Time & Attendance
Proposed deployment methodology (see below) plus additional strategies to minimise risk
BuildSmart: the Project Management / SDLC methodology to be adopted in the Implementation
Project Management team to comprise of ADC Energy and CCS representatives headed up by a Project Leader
nominated by ADC Energy. ADC Energy team representatives assigned to each section (Financial, Commercail,
Plant, HR, Payroll and IT) having a sound knowledge of the business in general and expert knowledge in their
field. The time requi.red by the representatives of the ADC Energy team to dedicate to the project to be clearly
outlined and committed to.
The process of creating or altering the CCS system is not required as the system has been designed in full to
meet the requirements of the Construction Industry and is industry specific.
CCS will meet with ADC Energy representatives (The Project Team) designated to assist with the overall
management of the installation and setup process. This will entail the discussions surrounding the identification of
project managers, key client staff, the overall structure of the locations and use of the system, communications
infrastructure, server and client hardware, agreement on implementation schedules, best practice advice and on
the document process and work flows.
This phase lasts over the entire duration of the implementation of the system. A formal project plan and project
charter will be tabled and agreed.
The design approach in terms of process and blueprint definition:
Based on 30 years of meeting the needs of this specified industry, implementation of the complete integrated
system does not require the design phase as is normally understood in implementing an ERP system. CCS will
be installed and implemented with predefined functionality, user interface and reports that are industry specific.
The design phase, which is client specific, covers the following:
Company Organizational Structure

Design of Chart of Accounts Ledger code structure and format
Contract Cost codes defined which would be implemented in ADC Energy current Candy system
Control Codes Ranges of codes in line with predefined functionality
Project and the Contracts within these Projects
Activity or Task codes in line with the Tasks in Candy an evaluation will be made in conjunction with ADC
Energy on the best practice in the use of these Activity/Task codes in order to obtain the maximum benefit
and value from the Candy BuildSmart
Transactions types in line with the predefined functionality
User Roles and Responsibilities within the system and electronic approvals based on predefined functionality
Masterfile code structure for AR and AP, including separate masterfiles codes for Sub-Contractors
Currency
Fixed Assets coding structure
Plant and Equipment Coding structure
Payroll requirement regarding types of payrolls
Earning and Deductions types and calculations for Payroll
Costing implications within the payroll in line with predefined functionality
The above will be defined by a BuildSmart specialist consultant in consultation with the project or project section
manager or managers as nominated by ADC Energy .
The testing approach (Unit, UAT and SIT testing);
Prior to installation, ADC Energy will install the Windows Operating System on the Server, do the Network
Set-up and provide the SQL installation disks for CCS to install along with the CCS software. All software to
be licensed compiling to licensing requirements.
A trained CCS technical consultant will install all the operating and application software required on the server
and client machines designated to operate the BuildSmart software as per the minimum hardware
specification as stipulated. Technical testing will be carried out and phase signed off by Client
SIT (System Integration Testing) is done at each stage of the implementation. As the CCS system is fully
integrated on installation, the process of checking control codes, conflict reports, balancing and standard
checks are carried out at take on, data capture during the data processing and standard period ends in each
section of the software.
UAT (User Acceptance testing) carried out during the training process where recommendation will be made
on user skills and aptitude. The system has a number of checks and balances within its functionality which
alleviate a number of potential user problems. The roles are clearly defined and cater for skills from a low
based skills level to a high financial acumen level requirement. In consultation with the CCS specialized
consultant, these areas will be clearly defined and users assigned to the role in line with their job description
and skills level.
ADC Energy and its representatives will have an opportunity to review the BuildSmart System configured with
the agreed code structure and populated with ADC Energy static data during the period of Client Evaluation
as identified on the Project Plan.
Running the existing and new systems in parallel:
Due to the architecture of the CCS software being unique, the process of running parallel with the existing
system would not be recommended. Should this be a requirement, the existing system would have to be
investigated in order to establish criteria of comparison between the two systems and at what level the
comparison is made. The work load of implementing a new system, changes to work flows (if required) and
maintaining an existing system has time and effort constraints
Adoption of a new and/or changes to the current chart of accounts:
The Chart of Accounts is the CCS system is flexible with constraints on the number of digits in the cost codes
in order to facilitate the interface with Candy. Should the sections of the CCS fully integrated system require
new codes within sections of software not in the existing software, this is expected. The Chart of accounts
complies to IAS and is client driven and client specific. Input from the CCS consultant will be provided in order
to obtain the maximum added value from the system as a whole.
Changes to business processes to accommodate the new system:
With CCS being fully integrated certain work flows and processes will change. At time of the implementation
of each section, the CCS consultant specializing in the section would make recommendations based on the
value added in line with the system requirement and the desired outcome. For example, the interface
between Candy and BuildSmart of the resources and allowables, will require the cost codes and
tasks/activities between Candy and BuildSmart to be aligned.
The change management approach to be adopted.
Managing the effective planning of the implementation.

Scheduling and planning to minimize the impact on the business units to enable maintenance of business as
usual.
Define and communicate realist deadlines
Building involvement in the development and delivery to create understanding.
Engaging with impacted staff to involve them in the process of transition.
Managing effective two-way communication with all stakeholders during the project.
Confirming the case for change and how CCS initiative will contribute to realizing the organization's strategic
goals, and assessing the capacity and readiness of both individuals and ADC Energy to assimilate change.
Identify and articulate potential blockers and to agree on strategies and plans to deal with these so they don't
derail the initiative.
Prepare model, organizational structures, role definitions, competency frameworks, and governance and
decision-making frameworks. Particular attention to realistic and effective interaction with the project leaders
from ADC Energy and CCS.
Project leaders to be identified by ADC Energy and CCS to clarify how the implementation will be led. Specific
activities include defining the role of the leadership team, how the leadership team will work together both
during implementation and subsequently, and the roles and responsibilities of individual leaders. Identify ADC
Energy decision makers and availability in line with the planned implantation program.
Establish the skills and competencies required for the required roles and processes within the CCS system
and aligned job descriptions.
Delivery of the project ("making it happen"), both "hard" deliverables in the form of project plans, milestones,
progress reports and newsletters, and "soft" deliverables in the form of communications.
Candy Implementation
The Candy implementation can happen independently of BuildSmart but as and when Cost or Ledger codes and
Activity of Task codes have been agreed, they will be adopted in Candy for one to one comparison and CVR.
Candy implementation usually starts in estimation and spawns from there, i.e. using Candy meaningfully for post
tender or Valuations is dependent on a Candy resource based, analytical estimate. Generally 5 days of training (2
days C201 Candy Estimating & Valuations Introduction course) and consultancy (3 days) will be sufficient to get
any user up and running with live data. Training should commence with the estimation department at head office
and core estimation personnel from other departments if applicable.
It will also benefit senior commercial/QS staff as the training will touch on the Valuation side of Candy as well. The
hands-on consultancy should be directed at the core estimation personnel at head office in order to get them
going on live data by either tendering on a current bid or re-tendering a recent submission or awarded contract.
Further specialised (estimation, planning, valuations, forecasting etc) training and consultation at HQ and/or
business units can be arranged on application and on an as needed basis.
Refer to the CCS Implementation plan ADC - CCS Implementation Plan.pdf
Describe how the solution will be used by ADC employees across HO, DO and SO locations.
BuildSmart works effectively in multi-national and multi-organisational environments. BuildSmart allows

information to be entered where it is produced e.g. at the site or in the office, and to be processed and viewed
wherever you are in the world over a secure web-based connection that is easily available through a strict and
secure permission based system.
Within an Enterprise, there is no limit on the number of organisations:
Each organisation may have the same or different base or reporting currency consolidating into an organization at
currency rates as defined by ADC. With reference to Joint Ventures, the 100% JV may be recorded and reported
on, with consolidation percentage (the percentage interest of ADC) taken into account on consolidation. Part or
100% owned subsidiaries would be catered for in the same way.
The organisation tree would then follow:
Multiple Projects which may have multiple Contracts within a Project Contract to Activities and Cost codes
Divisions or Overheads Multiple division with an organisation for Head Office or other departments
CANDY INSTALLATION AND SET UP
Options exist for System, Licence and Data to run stand alone or on a network or in combination, i.e. data and
licences on the server and system on client or data and system on client and data on server. Data can also easily
be transferred by compressed email, common backup areas and/or VPN etc.
The Candy Project Control system can operate in several application and data location configurations. Each
configuration has its pros and cons and the system administrator must weigh these up to design the best option
that fits their business operations.
In terms of user rights, Candy identifies two types of users; Candy administrators with full rights and Candy non-
power users with restricted rights.
Candy user types
Candy administrative user
The admin user is responsible for the installation and maintenance of the Candy software and the Candy licence.
This user must update the software and licence promptly when so requested by the system. Candy admin users
require full administrative rights to the Candy application folder as Candy will require updates and patches to be
installed from time to time. This process is automated and can happen from within the application. The Candy
admin user needs access to the Internet and email to execute the administrative functions effectively. The Candy
network master libraries must be created, maintained, and backed up by the admin user.
Candy non-power user
The non-power user is restricted by the IT department from installing and updating software on the network or on
the users local hard drive. These user profiles have full access rights to their My Documents folders, Windows
roaming and non roaming application data folders, and data home directory. Access rights to other folders are
restricted to read only and execution rights. Candy non-power users require read only and execution rights to the
application folder. The Candy network master libraries can be accessed by this user in read only mode during
master selection within the application.
Installation pre-requirements
General
Before the installation of the Candy application can happen it is very important for the organizations IT
department and the Candy users to perform the list of pre-requirement activities. This will ensure the
understanding of the software requirements, and successful implementation and maintenance of the software by
all stakeholders.
Predefine list of Staff
Establishing a list of the Candy users helps in the planning and implementation of user groups, security settings,
and client tick list. The client tick list is used to establish Candy user profiles and providing access on the
individual client computers.
Predefine list of Roles
The list of Candy users must be categorized as admin-user or non-power-user depending on the users functional
position and in conjunction with the predefined list of Candy events.
Predefine list of Events

Event Users
Install or update Candy application software Admin-user
Install or update Candy licence Admin-user
Install or update Candy documentation Admin-user
Install or update Candy help files Admin-user
Install or update centralized Candy master libraries Admin-user
Install or update local language files Admin-user
Install and control centralized shared Candy data files Admin-user
Create, delete, and modify Candy project data files Non-power-user
Scan, file record lock, and read Candy licence files Non-power-user
Scan and read Candy master libraries Non-power-user
Create and delete Candy shared backup files Non-power-user
Predefine list of User installation types

The list of Candy users must be analyzed to establish the users installation type requirement. Determinates like
hardware; mobility; and critical business processes, will help the IT department in assessing each users
installation type. Users that require 100% uptime, for example, will have standalone installations on a laptop
computer, that can operate independently from any servers and electrical power source.
Single user environment (standalone)

The Candy application files, the user data files and the license are located on the computers local hard drive. In
this environment it is advisable to install the Candy application in the Program Files folder. Windows XP and
Vista require users to login as administrators to install software and updates, although the program may be
operated in a non-privileged mode.
The Candy data folder is best located in the users My Documents folder. This will ensure that the user always
has read write access to the data and the data is secure from other users who are using the computer with a
different profile. If data needs to migrate or get backed up automatically, the My Documents folder is easy to
identify and already contains other required data.
The user is responsible for the installation, updates, and patches of the Candy application. Backup of the Candy
data files is the users responsibility.
Peer to peer environment (p2p)
P2P systems are based on a distributed computing model in which peers share computer resources and
exchange services directly. In P2P systems computers, can act as network clients or servers. To be effective,
users must share a hard drive with full rights to all users. Users can share data files, applications, printers and
other network resources. This environment tends towards low network security. The application response times is
highly coupled to network resources. Data file backups can be centrally managed with some effort.
The Candy application, user data files, and licence can be located in various combinations to suite the users
operational requirements.
Client server environment (c/s)
C/S systems are based on a distributed computing model in which nodes share computer resources and
exchange services through a dedicated network control computer, called the server. The server handles the
communication needs of the other computers in the network. Users can share folders with read write access to
controlled user groups. Users can share data files, applications, printers and other network resources. Very high
network security. Computers with Windows operating systems with the same security capabilities and file
operating systems can operate in this environment.
Data file backups can be centrally managed with ease. Application response times are highly coupled to network
resources.
Candy network installation
General
The Candy installer is Windows compatible. The install file is compressed to about 10mb and can be downloaded
easily from the Candy website. The installation requires 30mb of disc space. The Candy installer is user friendly
and requires only the location of the folder as input from the user. The user that installs Candy requires
administrative rights to the application folder to create and copy the folders and files.
Candy application
The Candy application is a Windows 32 bit native Intel code application obeying the Windows Portable Execution
model. The Windows resource DLLs required by the application are generated using the Microsoft Visual Studio
development platform. Candy can be installed and implemented on any platform that is compatible with the
Windows Network Operating System and obeys the Windows File Operating System rules. The Candy client does
not require any software installation. The Candy application server installation has all required software and
application data available to run a Candy client.
Candy on a wan
The Candy application can be run in a thin client server environment using Micro Soft Terminal Services or
rd
equivalent 3 party software (eg Citrix).
Candy data
The Candy data is stored in a CCS propriety database management system (DBMS). This ensures that the
Candy data is accurate, secure and can be retrieved at real time speeds. The DBMS is scalable and can be
implemented in a client server environment, peer-to-peer, and single user system without much user intervention.
The DBMS relies on the Windows network operating system to provide user access and security to the data. The
rd
Candy DBMS does not require any 3 party software installation and therefore does not interfere with existing
commercial DBMS installations on the users computer or network.
The Candy DBMS system uses and obeys a subset of the Win32 File API that makes it compatible with most
rd
File, Server, and Network operating systems that do the same. Other file operating systems, 3 party disc cache
tools and server configurations that do not emulate the Win32 File API fully will not execute the Candy system
correctly. The Candy system uses the Win32 file sharing, file locking and record locking API. If non Microsoft file
and network systems are used, they must obey the Microsoft Network Client services fully to operate the Candy
system correctly. If non Microsoft systems are used the latest network operating system and software patches
must be installed, and configuration settings on servers must be considered to prevent data loss.
Candy licence
The Candy licence mechanism is supported on Win32 File systems. The Candy licence will fail on Unix, Linux
and DOS based servers that do not emulate the Win32 File API correctly. Virus protection software and archive
utilities that tamper with file attributes, and properties of the licence file will cause it to fail.
The Candy licence can be shared in a centralized location or setup as a single user in the users profile folders.
The licence is served with full rights to the Candy admin user and read only access to the Candy non-power user.
The users can access the licence folder using an UNC or network mapped drive.
Network licence
The Candy licence can be installed on a LAN to make it available to more users. The Candy admin user requires
full rights to Candy licence location. Candy non-power users require read only access to the licence location.
Setting up the candy application server
Installation Pre-requirement
Establish the Candy application server computer name.

Establish the Candy administrator logon name and password.
Establish the Candy application installation folder name.
Establish the share name and share the Candy application folder with the Candy user groups.
Using the list of Candy users ensure that all users have exited the Candy application.
Installation
On the application server create the folder CCSAPPS. This folder must be shared with full rights to the Candy
admin user. The Candy non-power users require read only and execution rights to this folder. Install the Candy
application in the subfolder CCSWIN in the folder CCSAPPS. Within the folder CCSAPPS, create the subfolder
CCSAPPS\CCS. This folder will contain the Candy licence.
Setting up the candy shared data space
On the data server create the folder CCSDATA. This folder must be shared with full rights to both Candy admin
and non-power users. The CCSDATA folder will contain all Candy data that are intended to be shared among the
Candy user group. Within the CCSDATA folder create the following sub folders:
..\CCSDATA\CCSCOM (contains the Candy backups shared by the user group);
..\CCSDATA\CCSMAST (contains the Candy network master libraries); and
..CCSDATA\CCSMULTI (contains the Candy multi user concurrent accessed libraries)
CCSCOM
CCSDATA CCSMULTI
Candy Group
Data Server
CCSMAST
Setting up the users candy data space
On the data server each user will have a unique data home directory. This ensures that application information is
stored separately for each user in a multi-user environment. In each users home directory create the sub folder
CCSDATA. The Candy user requires full rights to this folder which will contain all the Candy data and archive
backups of this user. This folder can be backed up with the other application information of the user during
organisational disaster recovery protection procedures.
Setting up the candy client
General
The Candy file management system is compatible with network mapped drives and UNC path names. To launch
the Candy application on the client the executable file CCSVFX.EXE must be run.
\\<computer name>\<share name>\CCSWIN\SYSTEM\CCSVFX.EXE for UNC.
X:\CCSWIN\SYSTEM\CCSVFX.EXE for network mapped drive.
Launching the candy application
A Windows shortcut or link file can optionally be used to assist the user in launching the Candy application. The
shortcut can be installed on the users Windows desktop using the Candy icon for easy identification. If the user
needs to be guided to the location of the preferred Candy data folder, the start in folder option of the shortcut file
properties can be set to point to Candy data location path, for example <user home directory>\CCSDATA. The
user can access other data folder locations using the data folder manager within the Candy application.
First time launch
On the first time launch of Candy the system will prompt the user to login. The user will be required to enter a user
name, initials, and company name. These settings are important information and will used in the following manner
during the operations of the application:
User name:
o Password and licence settings.
User initials:
o The first three characters must be unique in the Candy user group. These characters will be
recorded against data modifications and identification of users when using the system in multi
user concurrent mode.
Company name:
o Licence settings and system information for support.
The Candy login details can be modified on the company manager document using the Company drop down
menu.
Candy licence
If the Candy licence is not automatically detected at the licence folder ..\CCSAPPS\CCS the user must use the
change tab on licence dialog and select the licence path option to point to correct licence folder.
Candy shared data
To get access to the shared Candy data folders, common backups; network master libraries; and multi user
concurrent access libraries, the folder paths must be set for the user. Using the My Candy Settings tool and the
option Folders and Paths set the following paths accordingly:
Common Backups:
\\<computer name>\<share name\CCSDATA\CCSCOM for UNC.
X:\CCSCOM for network mapped drive.
Candy Network Masters:
\\<computer name>\<share name\CCSDATA\CCSMAST for UNC.
X:\CCSMAST for network mapped drive.
Multi User Company:
\\<computer name>\<share name\CCSDATA\CCSMULTI for UNC.
X:\CCSMULTI for network mapped drive.
Archive backups
Each Candy user must have a unique data folder to store their personal backups of important information. This
folder is the archive backups. To set the archive folder use the My Candy Settings tool and the option Folders
and Paths set the archive backups path accordingly:
<user home directory>\CCSDATA
The users settings will be stored in the Candy configuration file CCS.INI in the Windows virtual folder My
Documents\My CCS.
Candy shared data setup
General
This document must be read in conjunction with the Candy Network Installation document. The Candy Data
Folder can be shared among several users if online real time access to the data is required. The Candy Job
Manager will only allow one user to take ownership of the Job dataset at a specific time instance. Users must
complete their data tasks on the selected job and return to the Job Manager document to release the data files for
the next user to gain access to the same job.
Shared data folders can be setup in a Client/Server Network, Virtual Private Network, or a Wide Area Network
environment. Users can access data servers in a wide area network using Terminal Services.
Concurrent Data access
If concurrent access to the same job is required the job data files must be copied using the Candy backup
function and then added to the multi user company using backup recover function. The Candy multi user
company must be set up as explained in the Candy Network Installation document under the heading Candy
Shared data space. For users to access the shared data, add the shared Candy data folder path to each users
Data Folder Manager.
Data exchange and shared libraries
To enable data file exchange and shared master library access for the Candy user group setup the Candy Shared
data space and each users Candy settings as stated out in the Candy Network Installation document.
Shared Data Folder layout

Data Server in the Internet Cloud

Candy Backup and Recovery
Define what services will be required to implement and support the solution
Implementation and support will be provided by CCS Gulf and South Africa. Hardware and software services
as per the system requirements (see 7.3)
Note any additional third-party components that are required
See 7.3
Note of any requirements that cannot be met with the solution

7.2 Solution Deployment Scenario(s) and Architecture
CCS Candy and BuildSmart are on premise, generic software solutions. Candy is a software application
running on a proprietary database that can be downloaded or installed from file to any client pc, with shared
licence, system and data options. The BuildSmart solution is dot.net solution running SQL database hosted on
the clients server, accessed via the web through Internet Explorer.
BuildSmart System Requirements:
Component Requirement Comments
Server - Microsoft Windows Server 2003 or 2008, 32 The following editions of Windows
Operating or 64 bits Server are supported:
System IIS 6 or newer with .NET Framework 4 (IIS
must be converted to 32 bits) Standard, Data Center and
Latest Service Packs Enterprise editions
THE SERVER MUST NOT BE A DOMAIN
CONTROLLER; EXCHANGE SERVER, OR
ANY VERSION OF A SMALL BUSINESS
SERVER
Database Microsoft SQL Server 2005 or higher The following editions of SQL
Latest Service Packs server are supported - Standard
EXPRESS VERSIONS ARE NOT and Enterprise
ALLOWED
Microsoft Excel Excel to be installed on the server

(Licensed)only if the client will be using our
BuildSmart Business Intelligence module
Server Hardware Dedicated Server HDD must have at least 7200

CPU Physical Dual 3Ghz or better, Intel or RPM, any raid controller
Athlon 32 or 64 bits
RAM 4GB or more
HDD 100GB of free space
Network ADSL or a dedicated line Internet access, External users are required to print
Structure ADSL should be at least 2Mbts, the reports through your firewall/router
dedicated line should be at least 512 Kb thus the required default ports
Microsoft VPN or better or direct Internet should be opened.
access
LAN 100 base-T network cards & hubs We do cater for clients that prefer
Default Ports 80 (HTTP), 1433 (SQL), 3389 to use specific port numbers on the
(RDC) must be accessible externally external fixed IP address or DNS
name.
Workstations Microsoft Windows XP, Vista, 7 All Editions of Windows XP, Vista 7
Operating Microsoft Office 2003 or 2007 and Microsoft Office are supported
System Latest Service Packs
Internet Explorer version 6 or newer
Workstations CPU Single 2.5 GHz or better, Intel or

Hardware Athlon 32 or 64 bits
RAM 1 GB or more for XP and 2 GB or
more for Vista, 7
HDD 30GB of free space

Screen Resolution - 1024/768 or higher
Printers Laser or DeskJet with sufficient speed All Printers could be Local or
according to the volumes Network Printers
Dot Matrix printer for printing Payslips Payslips can also be printed on a
LaserJet
Languages and ASP, VB Script, Java Script, VB, .NET,

Technology Seagate Crystal Reports 8.5, XML, MS
Office
Firewall The Windows firewall on the BuildSmart

Server must be off
Support CCS requires access to the server for

support via Remote Desktop Connection.
Client Machines The user must be able to read; write;

delete and execute to the BuildSmart
folder found at c:\program files\BuildSmart
on the client machines
Candy System Requirements:
1. Operating system
Candy runs and is supported on Windows XP SP2 and SP3, Windows Vista and Windows 7. The latest service
pack should always be installed.
2. 64 bit support
Candy will run correctly on all 64-bit processors and 64-bit Microsoft operating systems.
3. Minimum Hardware requirements
2 GHz Intel P4 or equivalent AMD

1GB of system memory, 2GB or more for Vista
80 GB hard drive with at least 1 GB of available space
Display card and monitor that supports a resolution of 1024x768 or better
Internet access (for support, system updates and licensing)
4. Virtual Environments
Candy functions under a number of virtualized environments including Citrix, MS Remote Desktop.
5. Installed platforms
MS .NET is not a prerequisite to run Candy. However, some special services do make use of this platform and
will require .Net 3.5 or .Net 4.0.
6. File system requirements
Candy uses the Windows 32 bit File API. It relies on services provided by this API for file sharing, file locking and
record locking. Non-Microsoft operating systems and server configurations that do not emulate the Windows 32
File API fully will not execute Candy correctly specifically resulting in data loss. Servers that make use of
proprietary caching software must be correctly configured with Candy in mind.
The Candy licence mechanism is supported on Windows 32 bit File systems. The licence will fail on UNIX, Linux
and DOS based servers. Virus protection software and archive utilities that tamper with file attributes, and
properties of the licence file will cause it to fail.
Candy server installation
General
The Candy application has a very small server footprint and the efficiency of the application is highly coupled to
the number of Candy users accessing the server concurrently and the network traffic generated by other
applications served from the same computer.
Security policies and disaster recovery management procedures also influence the hardware requirements. Anti-
virus software for example that uses heuristic virus protection methods will slow down file access operations.
Candy application
This document must be read in consultation with the Candy Network Installation document. The Candy Project
Control system must be installed by the Candy administrative user. The Candy application folder will require
30MB of disks space. Candy non-power-user requires read only and execution rights to the Candy application
folder.
Server network:
Local Area Network
We recommend a 1Gbps connection speed.
Terminal Services
The minimum bandwidth figures per user session are 10K for Citrix and 30K for Windows terminal server.
Terminal Server bandwidth is highly dependent on what is served. Sound, video and printing for example
require lots of bandwidth.
Candy data files
Project disk space requirements
Average project disk space 10MB.

Large project disk space 24MB.
Mega project disk Space 50MB.
Data files statistics per session

Average number of data files opened in read write mode 18.
Average number of data files opened in read only mode 8.
Maximum number of data files opened in read write mode 38.
Maximum number of data files opened in read only mode 8.
7.4 Application Licensing
Please describe in detail how the application is licensed and provide a working example of how you
envision ADC using the software to the terms in the most cost- effective way.
Candy:
Candy software is not sold but instead rented on a monthly basis with an initial license fee per installation. This
rental includes all software upgrades, updates and full access to expert assistance should you need help to
perform complex or unfamiliar tasks. Training courses are available covering all the major aspects of the software
and at various levels of expertise. New users are encouraged to attend at least one course to get the best results
from Candy.
Candy licence
The Candy licence mechanism is supported on Win32 and Win64 File systems. The Candy licence will fail on
Unix, Linux and DOS based servers that do not emulate the Win32 File API correctly. Virus protection software
and archive utilities that tamper with file attributes, and properties of the licence file will cause it to fail.
The Candy licence can be shared in a centralised location or setup as a single user in the users profile folders.
The licence is served with full rights to the Candy admin user and read only access to the Candy non-power user.
The users can access the licence folder using an UNC or network mapped drive. The Candy licence can be
installed on a LAN or WAN to make it available to more users as concurrent. The Candy admin user requires full
rights to Candy licence location. Candy non-power users require read only access to the licence location. A
combination of network and stand alone licences are also common as a stand alone and network licence count
cost the same.
o Advantages of a stand alone licence:

Minimal technical set up required. The licence is resident on the computer and can be used by
the user wherever his/her computer goes
Each user has a licence associated with him/her and can be held accountable for that licence and
the use thereof
o Disadvantages of a stand alone licence:
Only that user can use the licence and if inactive no other users can benefit unless given access
to that computer
o Advantages of a Network licence:
One serial number is associated with n number of licence counts, i.e. administration is easier
dealing with one, centralised licence.
Any amount of people can have access to the licence but only the count number at any one point
in time
Multiple junior or training users can have access to the licences without each having to have
his/her own
o Disadvantages of a Network licence:
Users typically (unless they can access the network remotely) cannot work in Candy at home or
away from the LAN environment
If the Network goes down all the users will not be able to work in Candy
For Candy licencing, initially look at a number based on the number of estimation staff employed as Candy
implementation and licencing usually kicks off within the estimation department. Typically recommended is that
the estimation manager(s) have stand alone licences to allow them to have uninterrupted access to Candy.
Candy licences can be set/changed telephonically or via email.

Candy Licencing options:
Buildsmart is based on the number of concurrent users, and not named users. The system license covers the
number of users logged on to the system at any one time. There may be any number of named users, but only
the licensed number of users may be on line at any one time.
CCS Partners:
BuildSmart HR
This module provides a full suite of modular, but fully integrated modules to manage your human resources.
Includes: Basic Module - Full Employee Administration from Engagement to Retirement, Performance
Management, Training Administration, Disciplinary and Grievance management, Medical and Accident
administration, Storing of images associated with the employee, Employee self-service tools, Leave management
and admin, Passport and Visa management, and Reporting tools.
The software licencing is according to number of active employees.
BuildSmart Document Management

The licensing is based on an initial licence per individual user (not concurrent user), and installation, set-up and
training fee, upgrades and telephonic support. Installation usually requires about a week. A corporate licence can
be negotiated for large numbers of users.
BuildSmart Business Intelligence

The various modules within the Business Intelligence are licences separately by named computer
These modules being:
Adminstration
Report Writing access for the user to amend and create reports for ADC
Report Viewing access for the user to run and view reports
BuildSmart Time and Attendance

The licence fee on a rental monthly basis and is based on the number of units installed.
7.5 Maintenance and Support

Please describe how the solution will be maintained and supported considering the current IT
capability noted above. Please describe the responsibility, frequency and general complexity of upgrades
to the solution including a typical change plan following your best practice. Please explicitly note what local
or regional resources are in place to support ADC once the solution is in production.
CCS Offices and distributors are all fully functional business units, and each handle administration, sales, training
and support for their regions, as well as assisting other regions should it be necessary.
Front line product and technical support, and client training, is handled by all our offices. The majority of product
training occurs at our clients offices, as well as in training centres at our offices or externally. The CCS Dubai
office will be the primary source of support for ADC.
In addition to the Buildsmart on-line Log system, our clients have access to a telephone help-line that offers
expert assistance to users needing to perform complex or unfamiliar tasks. Remote desktop assistance can be
used in some situations. Importantly support staffs are specialists in either Accounts or Engineering so clients will
always find support from someone with industry knowledge.
We have a dedicated technical team that supports our clients remotely. CCS requires access to the server via
RDT.
A telephone hotline is available in all regions during normal business hours, as well as emergency contact
numbers after hours.
Online Log based support is available and accessible from each Buildsmart screen.
Over 70 CCS employees provide support at different times at either a support desk, on-line or by telephone.
All staff have strong experience in the construction industry, as well as in their various specialties such as
engineering, accounting, project management, quantity survey, and IT. A majority of the consulting staff have
experience working with the products in construction company offices and have an appreciation for the challenges
those needing support are experiencing.
Support problems are escalated on a mission critical basis. For example, payroll queries are a top priority, as is
support for work with an imminent deadline. The support log escalates support queries by these priority
considerations, and the by a time/date stamp method.
CCS regularly monitors industry developments, but primarily listens to the needs of its many clients to determine
what functionality will provide the greatest benefits, and does so working closely with product partners.
We have onsite available consulting services, with qualified construction accountants, engineers, quantity
surveyors etc.
24 /7 technical and administrative telephone (toll free and mobile) and fax support from within the UAE is backed
up by an international help desk. Telephone, fax, email and web details are organised by geographical region
and time zone and published in the software. We have support personnel available in the UK, South Africa,
Middle East, India, Australia and New Zealand so it is always possible to get technical or licence assistance.
Candy Support options:
Published contacts in the Candy Software:

Uniquely home or mobile numbers are available for emergency support:
Interactive help available in Candy context based:

Candy online support option and contacts:
The Buildsmart Help feature takes the form of on-line manuals and the Support screen from which Logs are
generated:
Updates
CCS development is driven by client requests. Each request is evaluated and those that fit the scope,
functionality, best practice are deemed to be of general value are put into development at no charge to the client
making the request. Updates and enhancement are industry specific and not client specific.
Development work is specified, coding is produced, and then tested in Alpha by our developers, then via selected
CCS consultants, and then via Beta testing by our distributors and selected clients. Only after successfully
passing each of these tests is the new feature included in a periodic release.
CCS does not have standard release cycles, but rather releases product after development and testing have been
satisfactorily completed and important new functionality is ready for general use.
The client receives notification when a new version is available, and the new features provided by that new
version. The client then has the ability to select an Update button on the system to download and install this
version and current updates.
BuildSmart software update:
Product releases in the last twelve months have been:
Candy:
2.00d was released in October 2010 32 minor releases
2.00e was released in March 2011 24 minor releases
2.00f was released in August 10 so far
Major release approximately every 6 months, 4 or 5 minor releases per month.
Buildsmart:
38 Updates Version 11.06.12 to Version 11.07.30
7.6 Implementation & Configuration Methodology
Refer to 7.3 and 7.4 above. Implementaton as per the ADC - CCS Implementation Plan.pdf and configuration
options for Candy and BuildSmart.
Candy and BuildSmart offer generic solutions with complete OOB functionality. Customization is rarely, if ever,
required as a result of both solutions being continually developed by contractors for contractors for 30+ years.
Inherent in both is good practice and procedure based on industry criteria resulting in maximum efficiency and
automation, single data entry and a lean process minimizing, and in most cases eradicating repetition, manual
manipulation and administrative overhead.
Optimal implementation, integration and configuration for an organisations such as ADC could be briefly
described as follows:
1. Candy being used for estimating, planning, forecasting and cash flow at bid and pre contract stage
providing both a financial and engineering budget or allowance for projects. A financial budget is derived
from the engineering budget, i.e. based on the estimated quantity of resources necessary at the
estimated rate of each resource unit, an estimated usage value can be derived for each resource and in
turn each ledger/cost code and/or activity/task code.
2. The engineering (quantity) and financial (value) budgets are uploaded into SmartBuy (BuildSmart
Procurement) as a shopping list for a project restricting the quantity and value of purchases per project.
Being web based and the solution hosted on the company server, BuildSmart can run either centralised
(HO) or decentralised (DO, SO) procurement or a combination of both. The forecasting done in Candy by
linking the resource based estimate to a critical path GANNT or barchart in Candy Planning provides a
procurement schedule identifying when resource (labour, material, equipment, Subcontractors) are and
will be required.
3. BuildSmart requisitions (based primarily on the Candy shopping list) become purchase orders after a
customised and tiered approval process.
4. Delivery of material against the purchase orders are captured in BuildSmart from site or head office and
upon delivery costs are accrued. Other payroll and overhead (office supplies, petty cash, assets etc) and
operational (plant & equipment, yard, inventories, subcontractors etc) costs are also captured in
SmartPay (BuildSmart Payroll) and SmartAct (BuildSmart accounting) to account for all costs for the
project and organisation.
5. Monthly Valuations are done in Candy based on actual work done against bill items and/or progressing
the schedule or barchart. The actual quantity of work done, calculates the allowable of resource that
should have been used, summarised into Cost/Ledger codes and Task/Activity codes for CVR with
BuildSmart accrued and actual (invoiced costs)
6. Actual and accrued costs from BuildSmart and uploaded back to Candy in order to do essential cost to
and at completion calculations in Candy Valuations for yesterday, today and tomorrow CVR and Earned
Value analysis
7. Candy and BuildSmart provide literally hundreds of reports extrapolated to thousands taking into account
various options, criteria, filters etc. for each report. Essential cost and management reports are available
OOB. However, partner products like Business Intelligence allow for company customised reports and
Dashboarding.
8. Workflows and document management and collaboration can be supplemented by our partner product
SmartDM (BuildSmart Document Management) while payroll can be supplemented by our partner
products SmartHR (BuildSmart Human Resource Management) and Time & Attendance.
7.7 Bidder Project Team

Provide a detailed overview of the project team responsible for delivering the solution. Describe the type of
resource, their level of engagement and respective skill set. Provide an overview of the phases, tasks and
deliverables they will be responsible for.
The CCS project team will have an appointed team leader who will have the overall responsibility of the delivery
of the project. The project team leader will have the required skill levels to perform this task as well as the
experience of successfully delivery project of this nature in the UAE as well as other GCC areas and
internationally. The team leader will be assisted by a team of trained construction professionals assigned to the
various sections or modules as outlined in the implementation plan.
The proposed team will consist of:
Name Designation Qualification Section Delivery Comments

Pat Cooper Senior IAC Diploma BuildSmart project Construction industry
Consultant team Leader experience from 1981
Saad Al Saafi Consultant Finance Sub Contractors, Numerous

Degree Debtors, Plant, implementations in the
Inventory, data capture GCC
Kaneez e Ali Consultant BBA Honours Procurement, Fixed 3 years experience

Assets and data with CCS
migration
Mohammed Irfan Consultant Finance Bank and Cash Numerous

Degree management, Payroll implementation in the
GCC
Rubesh Rajan Senior Civil Engineer Candy Estimating, Previously estimator for
Technical Planning, Forecasting, construction company.
Consultant Valuations Candy implementation,
Candy Team Leader training, support and
consulting lead and
experience in MENA
for over 5 years
Gejo Joshua Senior Civil Engineer Candy Estimating, Candy implementation,

Technical Planning, Forecasting, training, support and
Consultant Valuations consulting lead and
Candy Team Leader experience in MENA
for almost 5 years
Graham Technical Candy Estimating, 5+ years QS

Braybrooke Consultant Valuations experience for major
contractor in UAE and
South Africa using
Candy. 1 year
experience Candy
implementation,
training, support &
consulting MENA
7.8 Client Project Team Requirements

Describe the target Client Project Team, expected time commitment through the implementation from each
team resource and deliverables they will be required to provide. If required resources are not defined
on the supplied organisational chart, please describe the function and skill level required. Detail how
you will manage resource unavailability due to other business needs.
As detailed in the Implementation plan, a Project Sponsor is a critical role and this person required an in-depth
knowledge of the business and the business practices. The resources required are identified in the ADC
Organisational chart which a champion for each section requiring identification. Where decisions are required,
particularly in the setup stage, these identified champions will delay the process if unavailable for extended
periods of time. A System Administrator (Financial and not IT) is required to be available through the entire
implementation in order for the complete transfer of ownership of the system. A detail spec of this role is
appended to this response Visio-System Administrator - Admin User - Roles Spec and Process Flow.pdf
7.9 Phased Implementation Solution

Please describe how the solution can be implemented in a phased approach defining the order at which
different modules or components may be deployed.
The Candy implementation can happen independently of BuildSmart but as and when Cost or Ledger codes and
Activity of Task codes have been agreed, they will be adopted in Candy for one to one comparison and CVR.
Candy implementation usually starts in estimation and spawns from there, i.e. using Candy meaningfully for post
tender or Valuations is dependent on a Candy resource based, analytical estimate. Generally 5 days of training (2
days C201 Candy Estimating & Valuations Introduction course) and consultancy (3 days) will be sufficient to get
any user up and running with live data. Training should commence with the estimation department at head office
and core estimation personnel from other departments if applicable.
It will also benefit senior commercial/QS staff as the training will touch on the Valuation side of Candy as well. The
hands-on consultancy should be directed at the core estimation personnel at head office in order to get them
going on live data by either tendering on a current bid or re-tendering a recent submission or awarded contract.
Further specialised (estimation, planning, valuations, forecasting etc) training and consultation at HQ and/or
business units can be arranged on application and on an as needed basis.
SmartBuy and SmartAct are implemented simultaneously and the implementation follows the actual process flow
of the actual activities For example deliveries cannot be implemented before the procurement is complete.
SmartPay is part of the BuildSmart core system and costing would not be complete without the payroll being
processed with cost to contracts, cost codes and activities.
The Business Intelligence would only follow once the core system is running as data is require in the database to
provide meaningful BI reports.
Document Management would not impact on any of the core functions but workflows and alerts integrated to the
Document Management would not be available.
The HR module could be implemented at any stage as the functionality is in place to take Masterfile data from
SmartPay to the HR or from the HR system to SmartPay as the integration works both ways.
7.10 Expected Project Timescales

Base on the Solution Specification noted in Section 7.2 please provide a milestone based plan
detailing the key phases of the plans. In addition, include a milestone plan for a phased implementation
as noted in Section 7.9. The milestone plan must provide key milestones, critical path analysis,
decision points and summary resource requirements for the client project team.
Refer ADC - CCS Implementation Plan.pdf
7.11 Platform & System Integration

Provide a description of how the solution will integrate with current systems in use at
ADC as noted in Section 7.2
Refer our response to 7.2.
CCS provides a complete and interconnected solution, where if implemented fully, no integration with other
systems should be required. If specialised integration with other systems is required, these will be evaluated on
application. MS Excel import and export facilities are available OOB while Business Intelligence may be used in
certain cases where compatible to extract, combine and report on data from different sources. Candy and
BuildSmart are both Windows based applications and standard interfaces exist to MS Outlook, Acrobat/Adobe,
MS Access etc exist where necessary. Import facilities from AutoCAD and other design and take off software
solutions is currently under development in Candy while import/export facilities do exist for the likes of Primavera
and Microsoft Project in Candy Planning and Forecasting. CCS Candy and BuildSmart Integration with current IT
infrastructure software and hardware, being Windows based, are standard.
7.12 Data Migration from Current Systems

Provide a plan for how data will be migrated from the existing systems to the target solution using a
proven methodology. Detail risks and how those risks will be mitigated.
Candy:
Candy implementation and training commences in estimating. Legacy estimate data (coding, resources,
common indirect and direct work items, rates and buildups) can be imported electronically from MS Excel and
the like providing a platform to work from. Candy rate buildup sheets or worksheets make up the core data of
the estimate. Candy worksheets are unique with the free format input which sets Candy apart from its
competitors. Candy worksheets require time and thought in buildup so that they can be used as standard
templates and stored in a library or master for future use. Existing buildups in Excel or similar systems will be
converted and replicated in Candy worksheets with the initial assistance from a Candy consultation session.
Schedules or programs done in MS Project or Primavera can be seamlessly converted into Candy Planning
using standard OOB import/export facilities in Candy. The initial legwork is rewarded in the long term with
standard coding structures, templates and bills of quantity work items to be used repeatedly, easily and
quickly in future. The risk lies in the original data and the person(s) responsible for the conversion/import
export as Candy cannot guarantee another softwares data integrity nor can human error ever be completely
mitigated but as more and more estimates are done and via feedback from project delivery teams and sites,
mistakes and assumptions will be minimised and rectified based on actuals.
BuildSmart:
Masterfile data Suppliers, Sub Contractors, Debtors, Creditors, Assets, Stock items, Ledger Codes and
Employees Masterfiles are migrated by pre-defined templates supplied by CCS. These templates are populated
by ADC and loaded into the system by CCS.
Take on Balances of sub ledgers, specific detailed balance sheet items, costs to date, and other data as defined
in the project management phase are prepared in a template format by ADC and loaded by CCS. At each stage
data verification and or balancing processes are followed and each phase is signed off by ADC. All take on
balances and data must be verified and signed off prior to live transactions.
The data migration is itemised and detail in the implementation plan.
7.13 On-Boarding & Training

Describe the on-boarding (transition) process for ADC business users of the solution. Detail
recommended and required training for the solutions based on role/function. Define the best practice
approach to ensuring business users continue to realise the value of the solution.
Candy Training and on-boarding process:
Based on our extensive experience in implementing, training and supporting Candy, the tried and trusted
approach is to conduct a module/application orientated one or two day training course (see below
options) at a suitable venue or in-house at ADC premises, followed directly by between 1 and 3 days of
hands on consulting applying the theory learnt to practice. Continual and as required email, telephonic
and courtesy visit support and help contribute to the training and on-boarding process.
Essential core courses

Construction Estimating & Valuations (C201)* Forecast Budget & Cash Flow (C301)*
A two-day course suitable for Estimators and (Integration of Estimating and Planning)
Quantity Surveyors new to Candy. A one-day course suitable for Estimators,
The course covers all aspects of the estimating Planners, Site Engineers, Contract Managers
system, including bill creation, worksheets and and Quantity Surveyors who are familiar with
resources. By the end of the course the student Candy Estimating and Planning.
will have learned and applied, subcontract The course concentrates on the integration of
adjudication, pricing, mark up, valuations, Estimating and Planning to create forecasts,
subcontract liability, material adjudication, budgets and a more detailed cash flow analysis.
generating certificates and allowable control. Covers updating the program to generate the
* Knowledge of estimating procedures is required valuation quantities which are used to produce to-
date budgets and remaining forecast budgets.
* Students must have attended the Estimating
(C201) and Planning (C202) courses.
Construction Planning and Programming Post-tender Valuations and Budget Control

(C202)* (C203)*
A two-day course suitable for Planners, Site A two-day course for Quantity Surveyors, Site
Engineers, Site agents, Contract Managers Engineers, Site agents, Contract Managers and
and Estimators new to Candy. Commercial Managers.
Detailed instruction will be given to produce a This course is designed to help the post-tender
working program. Students then continue with commercial team use Candy Valuations effectively
planning and controlling the project, and to generate monthly valuations, price variations,
recording the as-built program as well as and to produce essential management reports.
managing the information from the design teams The course covers post-tender checks, value
as required by the program. Effective reporting engineering (re-modelling), correct coding
on the project status across all levels of structures, pricing and coding of variation orders,
management will be taught.The course covers area bills for location control, management of
bar charts and the linking of activities, activity subcontractors, valuations with actual, claimed,
types and allocating resources. The information paid and final quantities generating resources and
and long lead schedules are covered as well as budget control, including certificates. It also covers
monitoring progress and update reports. By the the Candy Cost & Allowables module.
courses end, students should be able to produce * Knowledge of post-tender procedures is required
complete programmes to control a project.
* Knowledge of the principles of planning and bar
charts is required.
Specialised in-house training

Quantity Surveyor Workshop (C302)*
A one day course suitable for Quantity
Surveyors and Project Managers who submit
the Client certificate and generate the monthly
cost report.
Aspects of checking the original tender, re-
modelling, entering accounting codes for cost
reconciliation, as well as generating engineering
and production information for site control are
discussed.
Post Tender Advanced Course (C401)*

A two day course suitable for Quantity
Surveyors who are not using the full potential
of Candy for the post tender control of their
construction projects.
Topics covered include job re-modelling,
valuations, implementation of resource-based,
locational and functional project control, integration
of Estimating and Planning to create forecasts,
budgets and a more detailed cash flow analysis.
*Students must have attended the General
Estimating course (C201) and have a working
knowledge of Candy.
Management courses
Analysis & interpretation (C402)
A half day seminar for executives and
managers who require an understanding of
the information that can be generated by
Candy, but do not necessarily require hands-
on training.
BuildSmart Training and on-boarding process:
BuildSmart training is a hand on approach where a CCS consultant or consultants will capture
transactions and demonstrate functionality with the users or users with live transactions. The training is
not one to one and users performing the same functions are trained together. Using this methodology,
real live problems are addressed and resolved instantly as well as user capabilities assessed. The aim
is to bring the user up to date to be able to do todays transaction on the same day. As explained in the
implantation phases, this process continues for the whole implementation and training phase with CCS
consultants being available even after sections are completed.
7.14 System Requirements

Detail the system requirements for business users systems (e.g. laptop, workstation, desktop, etc) to use the
solution.
Refer to 7.3 Candy and BuildSmart system requirements.
Candy client can run on a desktop or laptop or terminal service across a LAN or WAN. Using laptops, desktops,
terminal services etc depends on company policy, IT infrastructure and also the role of the user and task at
hand.
BuildSmart being web based and as detailed in the 7.3 ,desktops, workstations vs laptops would depend on the
user and the role the users plays in the business and is not prescribed by the system.
7.15 Mobility
Provide details of accessibility and mobility features of the solution, specifically:
Access to data from mobile devices
Approvals to requests via mobile devices
Review documents via mobile device
Integration into email system
Candy can run on any Windows device but has no specific mobile application. Data from Candy can however
easily be converted to or moved in PDF, MS Excel, MS Word that is readable on most mobile devices. Candy job
data can be sent from within Candy at the press of a button by email via a compressed file.
BuildSmart Procurement is accessible from mobile devices for :
View Requisition,
Approve Requisition,
View Order details,
Capture a Delivery
All reports are available in PDF, MS Excel and MS Word direct from the system which would be readable on a
mobile device and limited to the file size restriction on your email setup.
7.16 Remote Access

Detail how remote users will access the solution from divisional offices, site offices and remote locations (e.g.
home, travelling, etc). Describe any functional limitations that may exist when using remote access
configurations
BuildSmart Remote access:
CCS Buildsmart makes use of a direct connect, through a direct IP address, or a VPN using Internet
Explorer 6 or above. CCS Buildsmart offers the users unparalleled functionality when connecting to
distributed databases.
The asp model allows users access using nothing but an Internet browser and a connection to their
Internet Service Provider.
This allows the following functionality for distributed users:
Users on Site
Place site requisitions on-line for the attention of centralized buyers and approvers.
Track the progress of requisitions and purchase orders.
Take delivery of goods and services as they happen.
Draw reports from the centralized server at any time
Users at Regional Offices
Run the entire Enterprise System from remote locations live and real time.
Head office staff allowed quick and easy consolidation of business units data
Candy installation and remote access options
Options exist for System, Licence and Data to run stand alone or on a network or in combination, i.e. data
and licences on the server and system on client or data and system on client and data on server. Data
can also easily be transferred by compressed email, common backup areas and/or VPN etc.
The Candy Project Control system can operate in several application and data location configurations.
Each configuration has its pros and cons and the system administrator must weigh these up to design the
best option that fits their business operations.
In terms of user rights, Candy identifies two types of users; Candy administrators with full rights and
Candy non-power users with restricted rights.
Candy user types
Candy administrative user
The admin user is responsible for the installation and maintenance of the Candy software and the Candy
licence. This user must update the software and licence promptly when so requested by the system.
Candy admin users require full administrative rights to the Candy application folder as Candy will require
updates and patches to be installed from time to time. This process is automated and can happen from
within the application. The Candy admin user needs access to the Internet and email to execute the
administrative functions effectively. The Candy network master libraries must be created, maintained, and
backed up by the admin user.
Candy non-power user
The non-power user is restricted by the IT department from installing and updating software on the
network or on the users local hard drive. These user profiles have full access rights to their My
Documents folders, Windows roaming and non roaming application data folders, and data home
directory. Access rights to other folders are restricted to read only and execution rights. Candy non-power
users require read only and execution rights to the application folder. The Candy network master libraries
can be accessed by this user in read only mode during master selection within the application.
Installation pre-requirements
General
Before the installation of the Candy application can happen it is very important for the organizations IT
department and the Candy users to perform the list of pre-requirement activities. This will ensure the
understanding of the software requirements, and successful implementation and maintenance of the
software by all stakeholders.
Predefine list of Staff
Establishing a list of the Candy users helps in the planning and implementation of user groups, security
settings, and client tick list. The client tick list is used to establish Candy user profiles and providing
access on the individual client computers.
Predefine list of Roles
The list of Candy users must be categorized as admin-user or non-power-user depending on the users
functional position and in conjunction with the predefined list of Candy events.
Predefine list of Events

Event Users
Install or update Candy application software Admin-user
Install or update Candy licence Admin-user
Install or update Candy documentation Admin-user
Install or update Candy help files Admin-user
Install or update centralized Candy master libraries Admin-user
Install or update local language files Admin-user
Install and control centralized shared Candy data files Admin-user
Create, delete, and modify Candy project data files Non-power-user
Scan, file record lock, and read Candy licence files Non-power-user
Scan and read Candy master libraries Non-power-user
Create and delete Candy shared backup files Non-power-user
Predefine list of User installation types

The list of Candy users must be analyzed to establish the users installation type requirement.
Determinates like hardware; mobility; and critical business processes, will help the IT department in
assessing each users installation type. Users that require 100% uptime, for example, will have
standalone installations on a laptop computer, that can operate independently from any servers and
electrical power source.
Single user environment (standalone)

The Candy application files, the user data files and the license are located on the computers local hard
drive. In this environment it is advisable to install the Candy application in the Program Files folder.
Windows XP and Vista require users to login as administrators to install software and updates, although
the program may be operated in a non-privileged mode.
The Candy data folder is best located in the users My Documents folder. This will ensure that the user
always has read write access to the data and the data is secure from other users who are using the
computer with a different profile. If data needs to migrate or get backed up automatically, the My
Documents folder is easy to identify and already contains other required data.
The user is responsible for the installation, updates, and patches of the Candy application. Backup of the
Candy data files is the users responsibility.
Peer to peer environment (p2p)
P2P systems are based on a distributed computing model in which peers share computer resources and
exchange services directly. In P2P systems computers, can act as network clients or servers. To be
effective, users must share a hard drive with full rights to all users. Users can share data files,
applications, printers and other network resources. This environment tends towards low network security.
The application response times is highly coupled to network resources. Data file backups can be centrally
managed with some effort.
The Candy application, user data files, and licence can be located in various combinations to suite the
users operational requirements.
Client server environment (c/s)
C/S systems are based on a distributed computing model in which nodes share computer resources and
exchange services through a dedicated network control computer, called the server. The server handles
the communication needs of the other computers in the network. Users can share folders with read write
access to controlled user groups. Users can share data files, applications, printers and other network
resources. Very high network security. Computers with Windows operating systems with the same
security capabilities and file operating systems can operate in this environment.
Data file backups can be centrally managed with ease. Application response times are highly coupled to
network resources.
Candy server installation
General
The Candy application has a very small server footprint and the efficiency of the application is highly
coupled to the number of Candy users accessing the server concurrently and the network traffic
generated by other applications served from the same computer.
Security policies and disaster recovery management procedures also influence the hardware
requirements. Anti-virus software for example that uses heuristic virus protection methods will slow down
file access operations.
Candy application
This document must be read in consultation with the Candy Network Installation document. The Candy
Project Control system must be installed by the Candy administrative user. The Candy application folder
will require 30MB of disks space. Candy non-power-user requires read only and execution rights to the
Candy application folder.
Server network:
Local Area Network
We recommend a 1Gbps connection speed.
Terminal Services
The minimum bandwidth figures per user session are 10K for Citrix and 30K for Windows terminal
server. Terminal Server bandwidth is highly dependent on what is served. Sound, video and
printing for example require lots of bandwidth.
Candy data files
Project disk space requirements
Average project disk space 10MB.

Large project disk space 24MB.
Mega project disk Space 50MB.
Data files statistics per session

Average number of data files opened in read write mode 18.
Average number of data files opened in read only mode 8.

Maximum number of data files opened in read write mode 38.
Maximum number of data files opened in read only mode 8.
Candy network installation
General
The Candy installer is Windows compatible. The install file is compressed to about 10mb and can be
downloaded easily from the Candy website. The installation requires 30mb of disc space. The Candy
installer is user friendly and requires only the location of the folder as input from the user. The user that
installs Candy requires administrative rights to the application folder to create and copy the folders and
files.
Candy application
The Candy application is a Windows 32 bit native Intel code application obeying the Windows Portable
Execution model. The Windows resource DLLs required by the application are generated using the
Microsoft Visual Studio development platform. Candy can be installed and implemented on any platform
that is compatible with the Windows Network Operating System and obeys the Windows File Operating
System rules. The Candy client does not require any software installation. The Candy application server
installation has all required software and application data available to run a Candy client.
Candy on a wan
The Candy application can be run in a thin client server environment using Micro Soft Terminal Services
rd
or equivalent 3 party software (eg Citrix).
Candy data
The Candy data is stored in a CCS propriety database management system (DBMS). This ensures that
the Candy data is accurate, secure and can be retrieved at real time speeds. The DBMS is scalable and
can be implemented in a client server environment, peer-to-peer, and single user system without much
user intervention. The DBMS relies on the Windows network operating system to provide user access and
rd
security to the data. The Candy DBMS does not require any 3 party software installation and therefore
does not interfere with existing commercial DBMS installations on the users computer or network.
The Candy DBMS system uses and obeys a subset of the Win32 File API that makes it compatible with
rd
most File, Server, and Network operating systems that do the same. Other file operating systems, 3
party disc cache tools and server configurations that do not emulate the Win32 File API fully will not
execute the Candy system correctly. The Candy system uses the Win32 file sharing, file locking and
record locking API. If non Microsoft file and network systems are used, they must obey the Microsoft
Network Client services fully to operate the Candy system correctly. If non Microsoft systems are used the
latest network operating system and software patches must be installed, and configuration settings on
servers must be considered to prevent data loss.
Candy licence
The Candy licence mechanism is supported on Win32 File systems. The Candy licence will fail on Unix,
Linux and DOS based servers that do not emulate the Win32 File API correctly. Virus protection
software and archive utilities that tamper with file attributes, and properties of the licence file will cause it
to fail.
The Candy licence can be shared in a centralized location or setup as a single user in the users profile
folders. The licence is served with full rights to the Candy admin user and read only access to the Candy
non-power user. The users can access the licence folder using an UNC or network mapped drive.
Network licence
The Candy licence can be installed on a LAN to make it available to more users. The Candy admin user
requires full rights to Candy licence location. Candy non-power users require read only access to the
licence location.
Setting up the candy application server
Installation Pre-requirement
Establish the Candy application server computer name.
Establish the Candy administrator logon name and password.
Establish the Candy application installation folder name.
Establish the share name and share the Candy application folder with the Candy user groups.
Using the list of Candy users ensure that all users have exited the Candy application.
Installation
On the application server create the folder CCSAPPS. This folder must be shared with full rights to the
Candy admin user. The Candy non-power users require read only and execution rights to this folder.
Install the Candy application in the subfolder CCSWIN in the folder CCSAPPS. Within the folder
CCSAPPS, create the subfolder CCSAPPS\CCS. This folder will contain the Candy licence.
Setting up the Candy shared data space
On the data server create the folder CCSDATA. This folder must be shared with full rights to both Candy
admin and non-power users. The CCSDATA folder will contain all Candy data that are intended to be
shared among the Candy user group. Within the CCSDATA folder create the following sub folders:
..\CCSDATA\CCSCOM (contains the Candy backups shared by the user group);
..\CCSDATA\CCSMAST (contains the Candy network master libraries); and
..CCSDATA\CCSMULTI (contains the Candy multi user concurrent accessed libraries)

CCSCOM
CCSDATA CCSMULTI
Candy Group
Data Server
CCSMAST
Setting up the users Candy data space
On the data server each user will have a unique data home directory. This ensures that application
information is stored separately for each user in a multi-user environment. In each users home directory
create the sub folder CCSDATA. The Candy user requires full rights to this folder which will contain all the
Candy data and archive backups of this user. This folder can be backed up with the other application
information of the user during organisational disaster recovery protection procedures.
Setting up the Candy client
General
The Candy file management system is compatible with network mapped drives and UNC path names. To
launch the Candy application on the client the executable file CCSVFX.EXE must be run.
\\<computer name>\<share name>\CCSWIN\SYSTEM\CCSVFX.EXE for UNC.
X:\CCSWIN\SYSTEM\CCSVFX.EXE for network mapped drive.
Launching the candy application
A Windows shortcut or link file can optionally be used to assist the user in launching the Candy
application. The shortcut can be installed on the users Windows desktop using the Candy icon for easy
identification. If the user needs to be guided to the location of the preferred Candy data folder, the start in
folder option of the shortcut file properties can be set to point to Candy data location path, for example
<user home directory>\CCSDATA. The user can access other data folder locations using the data
folder manager within the Candy application.
First time launch
On the first time launch of Candy the system will prompt the user to login. The user will be required to
enter a user name, initials, and company name. These settings are important information and will used in
the following manner during the operations of the application:
User name:
o Password and licence settings.
User initials:
o The first three characters must be unique in the Candy user group. These characters will
be recorded against data modifications and identification of users when using the system
in multi user concurrent mode.
Company name:
o Licence settings and system information for support.
The Candy login details can be modified on the company manager document using the Company drop
down menu.
Candy licence
If the Candy licence is not automatically detected at the licence folder ..\CCSAPPS\CCS the user must
use the change tab on licence dialog and select the licence path option to point to correct licence
folder.
Candy shared data
To get access to the shared Candy data folders, common backups; network master libraries; and multi
user concurrent access libraries, the folder paths must be set for the user. Using the My Candy Settings
tool and the option Folders and Paths set the following paths accordingly:
Common Backups:
\\<computer name>\<share name\CCSDATA\CCSCOM for UNC.
X:\CCSCOM for network mapped drive.
Candy Network Masters:
\\<computer name>\<share name\CCSDATA\CCSMAST for UNC.
X:\CCSMAST for network mapped drive.
Multi User Company:
\\<computer name>\<share name\CCSDATA\CCSMULTI for UNC.
X:\CCSMULTI for network mapped drive.

Archive backups
Each Candy user must have a unique data folder to store their personal backups of important information.
This folder is the archive backups. To set the archive folder use the My Candy Settings tool and the
option Folders and Paths set the archive backups path accordingly:
The users settings will be stored in the Candy configuration file CCS.INI in the Windows virtual folder
My Documents\My CCS.
Candy shared data setup
General
This document must be read in conjunction with the Candy Network Installation document. The Candy
Data Folder can be shared among several users if online real time access to the data is required. The
Candy Job Manager will only allow one user to take ownership of the Job dataset at a specific time
instance. Users must complete their data tasks on the selected job and return to the Job Manager
document to release the data files for the next user to gain access to the same job.
Shared data folders can be setup in a Client/Server Network, Virtual Private Network, or a Wide Area
Network environment. Users can access data servers in a wide area network using Terminal Services.
Concurrent Data access
If concurrent access to the same job is required the job data files must be copied using the Candy backup
function and then added to the multi user company using backup recover function. The Candy multi user
company must be set up as explained in the Candy Network Installation document under the heading
Candy Shared data space. For users to access the shared data, add the shared Candy data folder path
to each users Data Folder Manager.
Data exchange and shared libraries
To enable data file exchange and shared master library access for the Candy user group setup the Candy
Shared data space and each users Candy settings as stated out in the Candy Network Installation
document.
Shared Data Folder layout

Data Server in the Internet Cloud

Candy licence
The Candy licence mechanism is supported on Win32 and Win64 File systems. The Candy licence will
fail on Unix, Linux and DOS based servers that do not emulate the Win32 File API correctly. Virus
protection software and archive utilities that tamper with file attributes, and properties of the licence file
will cause it to fail.
The Candy licence can be shared in a centralised location or setup as a single user in the users profile
folders. The licence is served with full rights to the Candy admin user and read only access to the Candy
non-power user. The users can access the licence folder using an UNC or network mapped drive. The
Candy licence can be installed on a LAN or WAN to make it available to more users as concurrent. The
Candy admin user requires full rights to Candy licence location. Candy non-power users require read only
access to the licence location. A combination of network and stand alone licences are also common as a
stand alone and network licence count cost the same.
o Advantages of a stand alone licence:

Minimal technical set up required. The licence is resident on the computer and can be
used by the user wherever his/her computer goes
Each user has a licence associated with him/her and can be held accountable for that
licence and the use thereof
o Disadvantages of a stand alone licence:
Only that user can use the licence and if inactive no other users can benefit unless given
access to that computer
o Advantages of a Network licence:
One serial number is associated with n number of licence counts, i.e. administration is
easier dealing with one, centralised licence.
Any amount of people can have access to the licence but only the count number at any
one point in time
Multiple junior or training users can have access to the licences without each having to
have his/her own
o Disadvantages of a Network licence:
Users typically (unless they can access the network remotely) cannot work in Candy at
home or away from the LAN environment
If the Network goes down all the users will not be able to work in Candy
7.17 Authentication, Audit & Authorisation

Describe the following aspects of the solution for authentication, audit and authorisation.
Integration with Active Directory for single sign-on
Authorisation for activity, approvals, etc
Audit capabilities
BuildSmart does not integrate with Active Directory for single sign-on. The user file are maintained within the
system providing secure sign-on by user ID and Password.
Authorization for activity, approvals or access to any functionality is by secure user permissions and roles..
All transactions or actions within the system are recorded against a user, with the date, time and actions taken. A
complete log is available with multiple search facilities by user, date and action.
Not applicable for Candy.

7.18 Data Protection

Describe the best practice for protecting the data within the solution and its application to the specifications
provided. If additional infrastructure or software is required, please make specific reference.
Candy, being a database system, writes directly to the database negating the need for manually saving or
backing up the data. Hardware can however never be guaranteed and it is thus good practice to backup and
replicate data to a server/external hard drive, archive directory and the like either manually or via a
synchronizing service. Candy also does an automated daily backup of the current job should any damage to
the database occur due to power failures, voltage surges etc.
Data in Candy can also be passworded and through normal windows access rights restricted to certain users
only for security purposes.

BuildSmart allows access rights to specific areas in the system via the User Interface is controlled via Roles
created per user . Only the administrative user account is able to activate or deactivate any user account or
modify a particular users rights and roles. Roles are created that contain appropriate permissions for each job
classification, this means that each user can only view menu items that pertains to the roles and rights that has
been allocated to that particular user.Access to the actual BuildSmart databases are protected via normal
Windows and SQL usernames and passwords
7.19 User Interfacing

Include 2-3 screenshots with a description for each function or module proposed in the solution.
Candy Estimating
Primary estimate working desktop with Bill of Quantities, rate make up or worksheet and resources:
Adjudicating subcontractors and performing subcontract RFQ enquiry:

Marking up the nett cost, Trade Total summary of the project and reporting:
Candy Planning
GANNT or Barchart with precedence network, progress and resource histogram:
Long Lead and Information schedules integrated with schedule
Program filtered by Subcontractor and area or WBS

Program filtered by subcontractor and Area of work (WBS):

Candy Forecasting
Bill of quantities with nett cost forecast per item and cost loaded program:
Estimated resource usage forecast and labour histogram:

Cost or Ledger code expense budget and currency forecast:

Candy Project Cashflow
Cashflow input document using forecast. Parameters of payment lags, interest established in Settings:
Calculated project cash flow summary:

Weekly projected bank balance for project cashflow:
Cashflow graphical:
Candy Valuations
Valuation input of actuals and variation orders:
Allowable usage and value of resources based on actuals and variations:

Subcontract management measurement of work done, extras, contras and MOS with certificate:
Forecast variances between allowable (budget) and costs (from BuildSmart) by Ledger and Activity code:
Earned Value KPI indices and graphical represention of cost vs allowable forecast:
BuildSmart
eRFQ
Create New eRFQ
Supplier Categories
Details of eRFQ by various sort functions

Procurement
Create new Site Requisition
Create Standard Requisition

Sub Contractor Change Orders Status
Sub Contractor Requisition Status with applicable line expanded

BuildSmart Accounting
Profit Allocation as per IAS 11
Revaluation on Currencies
Contract Management
Contract Budgets from Candy prior to valuation

Journals
Complete Journal Register with recurring journals, imports from excel for bulk entries and approvals
Sub Contractors by Contract
Fixed
Assets
Plant
Plant Servicing
Job Cards Maintenance of Plant and Equipment

Internal and External Plant Hire
Plant Hire rates

Payroll
Unlimited Earnings and Deductions
Batch importing
Leave Day Batches

Employee Masterfile in Payroll

Wages Cost Report
Clock Card Capture if not imported or by integrated Time and Attendance

Document Management integrated with Buildsmart
Accessing all document linked to a Buildsmart Contract

Folder view View documents in Folders across Contracts or Projects
Saving emails from Outlook or MS Office into Document Management

List all drawings linked to an area or section of the work
Document Detail showing Date tracking on Correspondence

7.20 Integration with Existing & Future Applications

The Bidder must demonstrate how the solution will integrate with existing applications detailed above.
Integration must consider productivity applications and line of business applications. In addition, describe
how the solution will integrate with other external services and/or systems (e.g. Aconex, etc).
Refer our response to 7.2.
CCS provides a complete and interconnected solution, where if implemented fully, no integration with other
systems should be required. If specialised integration with other systems is required, these will be evaluated on
application. MS Excel and other electronic formats (XML, CSV, TXT) import and export facilities are available
OOB while Business Intelligence may be used in certain cases where compatible to extract, combine and report
on data from different sources. Candy and BuildSmart are both Windows based applications and standard
interfaces exist to MS Outlook, Acrobat/Adobe, MS Access etc exist where necessary. Import facilities from
AutoCAD and other design and take off software solutions is currently under development in Candy while
import/export facilities do exist for the likes of Primavera and Microsoft Project in Candy Planning and
Forecasting. CCS Candy and BuildSmart Integration with current IT infrastructure software and hardware, being
Windows based, are standard.
The CCS approach to integration with a customers enterprise-wide portal:
CCS Buildsmart has no integration issues with a customers enterprise wide portal. Business Intelligence enables
the execution & distribution of authenticated real time reports across intranets or the internet. An add-on module,
Web Reporting, provides worldwide access to a clients business reports through a standard web browser and
integrates well with enterprise wide portals.
This solution provides the following benefits:
Supports a wide variety of export formats across the web including PDF, HTML, CSV, XML, XLS,
XLSX, XLSM, XLSB and GZIP
Fine-grained security controls access to Reports, Scheduling, and Administration functionality through
User Authentication
Report Auditing tracks time, status, and user of every report generated
Access previously requested reports with convenient Reporting History
Comprehensive Report Parameter support including Date, Text and List
Comprehensive Report Parameter support including Date, Text and List
CCS BuildSmart makes use of connection strings through OLE DB objects for MS sequel server 2005 or higher.
Other integration tools include standard XML schemas.
7.21 Local System Administration

Detail recommended and required IT administration training for the solutions based. Define the best
practice to administration to ensure continuous uptime of the solution. Bidders are encouraged to
recommend additional services that could assist with the on-going administration of the solution.
The clients designated BuildSmart super user has access to the server status section within the system and
normally oversees the current status of the system by using our dashboard. The server status section on our
dashboard gives detailed information in this regard. For example the current databases in use; days since last
backup; location of the databases; status (online or offline); size of databases; size of the system log files; what
SQL jobs are currently running; it warnings if the database is running out of storage space. Training is included as
part of the software price during implementation. The training is usually done at the clients offices and at the
users workstations. This can be provided by distributor offices or CCS head office staff depending on the size
and location of the client offices.
BuildSmart has online support log should the client encounter any technical problems.
Candy System Administration almost negligible IT administration of network rights to users, server,
installation/updates and backup is only required. Candy is not a heavy client or server application and only the
data access/recovery/backup needs to be administered. Access directly to Candy development team for database
recovery/fixing and system faults.
7.22 Solution Monitoring

Describe how the solution will or can be monitored for availability, performance and capacity levels.
Detail how notifications and alerts will be delivered to the administrator
CCS BuildSmart system optimisation can take the form of splitting the application server from the database server
and splitting the .MDF from the .LDF. CCS Buildsmart also makes use of temporary data structures for the
storage of reporting information, and utilizes sequel server agents for maintaining and deleting temporary files in a
structured manner. Full performance optimisation is dictated by the specific client server configuration and usage
requirements which must come from a thorough discussion of these issues and the establishment of specific
performance criteria with the clients IT team. As mentioned in question 7.21 above, the Buildsmart super user
has access to our dashboard that enables him/her to monitor the system and get most of the necessary
notifications.
7.23 Disaster Recovery & Service Continuity

Detail the best practice related to disaster recovery and service continuity for the solution.
We have technical online support to fix any systems errors however CCS requires access to the server at all
times. In case of hardware failure we are able to assist with an online reinstallation of BuildSmart as soon as there
is a working server.
During the BuildSmart installation backup scripts are created according to the needs specific to the client. Daily,
weekly and monthly scripts can be created to backup databases. This will allow for a recovery of data in the case
of a hardware/software failure. Individual projects cannot be backed up as all data integrated; however Buildsmart
does not take responsibility of database backups; therefore we urge our clients to conduct adequate backups of
the server and determine the frequency and method that is best for their organisation. We would also recommend
that backups are kept offsite.
The Candy data is stored in a CCS propriety database management system (DBMS). This ensures that the
Candy data is accurate, secure and can be retrieved at real time speeds. The DBMS is scalable and can be
implemented in a client server environment, peer-to-peer, and single user system without much user intervention.
The DBMS relies on the Windows network operating system to provide user access and security to the data. The
rd
Candy DBMS does not require any 3 party software installation and therefore does not interfere with existing
commercial DBMS installations on the users computer or network.
The Candy DBMS system uses and obeys a subset of the Win32 File API that makes it compatible with most
rd
File, Server, and Network operating systems that do the same. Other file operating systems, 3 party disc cache
tools and server configurations that do not emulate the Win32 File API fully will not execute the Candy system
correctly. The Candy system uses the Win32 file sharing, file locking and record locking API. If non Microsoft file
and network systems are used, they must obey the Microsoft Network Client services fully to operate the Candy
system correctly. If non Microsoft systems are used the latest network operating system and software patches
must be installed, and configuration settings on servers must be considered to prevent data loss.
Each Candy user must have a unique data folder to store their personal backups of important information. This
folder is the archive backups. To set the archive folder use the My Candy Settings tool and the option Folders
and Paths set the archive backups path accordingly:
The users settings will be stored in the Candy configuration file CCS.INI in the Windows virtual folder My
Documents\My CCS.
Candy, being a database system, writes directly to the database negating the need for manually saving or
backing up the data. Hardware can however never be guaranteed and it is thus good practice to backup and
replicate data to a server/external hard drive, archive directory and the like either manually or via a
synchronizing service. Candy also does an automated daily backup of the current job should any damage to
the database occur due to power failures, voltage surges etc.

7.24 Management Information & Reporting

Detail the capabilities of the platform for dashboard (real-time) and scheduled or manual reports.
Provide a list of standard OOB reports that come with the solution. Detail how additional, custom reports
can be created. Detail how additional means can be used for enhanced reporting (e.g. Crystal Reports,
etc).
Candy Report Manager
Candy Report Managers exist for each application within Candy. The report managers allow users to create their
own reports, specifying content, filters etc or use templates and make selections/customisations as required. As a
result of 30+ years servicing the construction industry only, Candy caters for 99% of contracting company
reporting requirements. In the rare case where the client has specified a layout, content or format not available in
Candy, any report or document with data can be exported to MS Excel or similar for further external
customisation. Candy also provides facilities to write data directly to a client specified Excel template.
Candy Estimating Report Manager:

Candy report or data export to MS Excel or similar for further customisation/enhancement:
Candy Export of data to prescribed Excel template:

Candy Estimating Reports
Report Headings Report Templates Report Description

1. Bill of Quantities
1.1 BOQ - Carried fwd / Brought Bill of quantities with

fwd - Gross customisable layout, styles and
selectionshowing bill with
gross/bid submission rates and
amounts with carried forward
and brought forward totals
1.2 BOQ - Carried fwd / Brought Bill of quantities with

fwd - Selling customisable layout, styles and
selection showing bill with
contractual or selling rates and
amounts with carried forward
and brought forward totals
1.3 BOQ - Collection pages - Bill of quantities with

Gross customisable layout, styles and
gross/ bid submission rates
and amounts with Collection
totals: carry pages, summary
pages and grand summary
1.4 BOQ - Collection pages - Bill of quantities with

Selling customisable layout, styles and
amounts with Collection totals:
carry pages, summary pages
and grand summary
1.5 BOQ - Page totals - Gross Bill of quantities with

customisable layout, styles and
and amounts with page totals
1.6 BOQ - Page totals - Selling Bill of quantities with

amounts with page totals
1.7 BOQ - Continuous Listing - Bill of quantities with

Gross customisable layout, styles and
and amounts in continual listing
format

Selling customisable layout, styles and
amounts in continual listing
format

Net customisable layout, styles and
internal net or allowable rates
and amounts in continual listing
format
2. Specialised Bills
2.1 BOQ - Listing with Bill of quantities with worksheet

Worksheets - Net (rate make up sheet) under
each item
2.2 Currency Analysis Bill Bill of quantities with rates

broken up into multiple
currencies based on resource
purchase currency
2.3 Final Quantity Discrepancies List the difference between

billed (client) quantities and
estimated final quantities
3. Indirect Costs
3.1 Indirect Costs Report Indirect Bill of quantities with

selection showing indirect items
with rates and amounts
3.2 Indirect Costs Barchart Indirect item listing with

associated time bars in GANNT
Format
3.3 Indirect Costs Barchart with Indirect item listing with

Histogram associated time bars in GANNT
Format with hitogram of indirect
costs cumulative at footer of
report
3.4 Simple Indirect Costs Simple report of Indirect costs
3.5 Indirect Costs Histogram Histogram of indirect costs only
3.6 Indirect Costs Monthly Monthly nett or gross Forecast

Forecast of Indirect cost items
4. Price code Lists
4.1 Net Price code list Listing of Price Code templates

and rates.
5. Resource Lists
5.1 Resource List Basic resource listing with

selections
5.2 Resource analysis by Project Resource listing with

codes customisable layout, styles and
selections but by Project code,
i.e. Activity or Location or
combination thereof
5.3 Resource analysis by Trades Resource listing grouped into

and Types Trades and Resource Types
5.4 Resource analysis Trade Resource analysis grouped into
and Type Summary Trades and Resource Types
6. Trade totals
6.1 Trade Total Graph Pie or Histogram representation

of Trade Totals showing
contribution of each trade or
resource type to job nett, gross
or selling total
7. Estimating Bills
7.1 Bill of Quantities (1) A listing of the BOQ showing

the bill items with quantity, unit,
rate and amount
7.2 Trade Spreadsheets (2) A listing of the Price codes used

to price the bill
8. Worksheet Reports
8.1 Worksheets (3)
8.2 Individual Worksheets (4)
8.3 Worksheets in Bill Order (5) A report listing the worksheets

in Bill item order
8.4 Indirect Costs Worksheets Report listing the worksheets for
(6) the Indirect Items in the Bill
8.5 Price code workheets by A further listing of worksheets
Value (7) based on a value search
8.6 Worksheets used only in A further listing of worksheets
Macros (8) which have been used to price
a macro item.
8.7 Macro Worksheets (9) A breakdown of the macro

worksheets into their respective
resource types.
8.8 Macro Bills (10) A bill listing all macro pricing

seperately to the main Bill of
Quantity.
8.9 Print Worksheet Chains (11) A report listing the usages of

complex resources and
worksheets and the build of
thereof.
9. Resource Analysis
Reports
9.1 Bill Resource Analysis (12) A report listing all resources the
budgetary allowances,
utilisation and the breakup into
the resource types.
9.2 Indirect Costs Resource A report listing all indirect

Analysis (13) resources the budgetary
allowances, utilisation and the
breakup into the resource types.
9.3 Bill+Indirect Resource A combination of the reports 9.1

Analysis (14) and 9.2
9.4 Analysis by Group/Cost (15) A resource listing grouping
them into the user defined cost/
group codes.
9.5 Resources by Bill Item (16) A report listing the resources

breakdown used in each BOQ
item.
9.6 Bill Items by Resource (17) A report cross referencing the

use of each resource into the
bill items.
9.7 Bill Production Rates (18) A listing of all the labour

components specific to the
various trades and their
utilisation
9.8 Resource Percentage (19) A report listing all the resources
and the percentage of the total
budget that each resource
consists of.
9.9 Resource Group/Cost A report listing the cost/ group

Summary (20) codes and the split for each into
the resource types.
9.10 Group/Cost Analysis (21) A report listing the cost/ group

codes and the split for each into
the resource types.
9.11 Complex Resource A report listing indicating

Analysis (22) breakdown for any complex
resources
10. Wastage Reports
10.1 Wastage Analysis (23) A report listing the wastage

percentage for each resource
used
10.2 Price code Wastage A report listing the wastage in to

Allocation (24) the price codes.
10.3 Complex Wastage A report listing the percentage
Allocation (25) used, split into the complex
resources.
11. Project Code

Reports
11.1 Project Codes (26) A report with a filter to view
Task, Bill or Work codes.
11.2 Project Codes Resource A report listing the resource
Analysis (27) breakdown into the Task and/ or
Group codes with more filters
available
11.3 Project Codes Quantity A report listing the resource

Analysis (28) quantities into the Task and/ or
Group codes with other filters
available
11.4 Project Codes Production Production rates listed into the

Rates (29) various codes.
11.5 Project Codes Quantity A report listing the total
Summary (30) quantities per various filtered
codes.
11.6 Worksheets by Project A report listing the worksheets

Code (31) split into the various filtered
codes.
11.7 Unallocated Project Codes A list of any items which do not

List (32) have a dedicated Project Code.
11.8 Undefined Code Allocations A list of any codes which are
(33) not used on any bill item and or
resource.
11.9 Allocations for Specified Listing a particular code and

Code (34) where it is allocated.
12. Analysis Reports
12.1 Value Analysis (35) A listing of all the bill items with
the budget and the percentage
in regards to the total budget
12.2 Currency Analysis (36) A listing seperating the different

currencies the utilisation and
the split into the resource types.
12.3 Tax Analysis (37) A list of any taxes used in the

worksheets
12.4 Macro Spreadsheet A report listing the macros split
Analysis (38) into the resource types
12.5 Trade Currency Analysis A listing of the various trades

(39) based on primary currency and
a split into any secondary
currencies.
12.6 Resource Type Currency A listing of all the resources

Analysis (40) based on primary currency and
a split into any secondary
currencies.
12.7 Resource Percentage A list of the resources that are

Analysis (41) used in the job seperating the
positive and the negative
attributes of each.
12.8 Cost Factor Analysis (42) An indication of the total cost of

the job, by factor. Excludes any
markup.
13. Miscellaneous
Listings
13.1 Trades in Bill Order (43) A split of the trades based in the
Bill order
13.2 Resource Listings (44) A comprehensive list of all the
resources, listing final rates,
discounts, etc.
13.3 Buying Schedule (45) An indication for purchasing of

any resource with suppliers
names dates for delivery, etc.
13.4 Section Index (46) Listing the different headings

and sub-headings from the bill.
13.5 Markup (47) A comprehensive markup
breakdown into the bill items.
13.6 Selling Rates (48) The list of selling rates and
percentages onto each bill item.
13.7 Resource Employed by Listing of the resource
Trade (49) quantities by trade
13.8 Engineering Work Code A listing of any specific work
Summary (50) code.
13.9 Dual Currency Bill (51) A list showing the different
currencies split into trades.
13.10 Bill Percentage Listing A bill listing all the quantities
(52) and a percentage split into the
different resource types.
13.11 Print Quantity Calculation A breakdown of the bill items

Sheets (53) which have quantity calculation
sheets attached.
14. Check and Review

Reports
14.1 Page/item Checksum (54) A Running total of bill qty's

using different sequences
14.2 Pricing Check (55) A report highlighting any
unpriced items
14.3 Provisional Listings (56) Any items that have been priced
provisionally
14.4 Gross/Selling Balance (57) Listing the difference of the
Gross to Selling rates per bill
item.
14.5 Cross Reference (58) A cross refernce of different
criteria and where ekse they
have been used in the BOQ.
14.6 Page Total (59) A summary page of all the

brought forward totals of each
BOQ page.
14.7 Price code Quantity A list of all the price codes

Analysis (60) summarising where they have
been used and the total qty
assigned to each one.
14.8 Rate Discrepancy (61) A list of rate discrepancies

within the BOQ
14.9 Tracer (62) A quick search listing for any
codes.
14.10 Worksheet Calculation A report listing any incorrect
Line Check (63) symbols on the worksheets
Candy Planning Reports

1. Activity Lists
1.1 Standard Activity List Report illustrating the list of

activities in a tabular format
1.2 Activity Logic Report illustrating the activities
in the program keeping the
logical sequence between
successor & predecessor
activity
2. Barcharts
2.1 Standard Barchart Barchart report illustrating the

activities in the program in
barchart view based on critical
path network
2.2 Current and Base Program Barchart report illustrating

Barchart thecurrent and base positions of
the activity bars after the
update.Visual comparison can
be made of the planned against
the actual
2.3 Barchart with as-built Barchart report illustrating the

Progress base activity bars with progress
superimposed as a "jagged"
snapshot line
3. Histograms
3.1 Barchart with Resource Report illustrating the printing of

Histogram a barchart ,including selected
histograms
3.2 Resource Histogram - Resource histogram

Current Start report,illustrating the printing of
separate histograms for the
selected resources,including
both daily values and
cumulative curves

Monetary Values report,illustrating the printing of
selected resources,keeping
monetary values and
cumulative curves

Current vs Base Program report,illustrating the printing of
separate histogram for the
selected resources,keeping
current & base program
3.5 Resource Forecast Report illustrating the

forecasted amount across the
various period based on the
resource under selection
3.6 Resource Forecast - Inverted Report illustrating the

forecasted quantity across the
3.7 Activity Density Histogram Report illustrating theActivity

densityacross the various
period showing the peak &
trough in an histogram view
4. Resources
4.1 Barchart with Resource Report illustrating the activities

Allocations in the program with the
resource allocated against the
activity keeping the resource
offset spread
4.2 Resource List with Barchart Report illustrating the specific

resource spread across the
various activities in the program
4.3 Resource List Report detailing out the list of

resources including the cost/unit
& the utilisation of the resource
in the program
5. Management
Reports
5.1 Summary Report - Contract Report illustrating the printing of
and Target Dates contractual & target start & End
dates of activities, for reporting
to the management
5.2 Summary Report - Contract Report illustrating the printing of

Dates contractual & target start & End
dates of activities, for reporting
to the management
5.3 Summary Report - Target Report illustrating the printing of

Dates target start & End dates of
activities, for reporting to the
management
5.4 Progress Diagnosis
5.5 Key dates Report illustrating the printing of

scheduled end type (E,e)
activities for reporting to
management
6. Information/Long Report illustrating at a

Leads summarised level whether the
activities are on program or
behind schedule
6.1 Information Required Report illustrating the printing of

Barchart information schedule in barchart
format with each information
item shown as a arrow head
pointer on a separate line to the
activity's bar
6.2 Detailed Long Leads Report illustrating the printing of

Barchart Long lead schedule in barchart
format with each long lead item
shown as a bar on a separate
line to the activity's bar
6.3 Barchart with Long Lead Report illustrating the printing

symbols ofActivities in barchart format
with each long lead item items
shownwith allocated symbols
against the activities in the
report
7. Networks
7.1 Precedence Network Report illustrating the

precedence network of logical
successor & predecessor
activities.Candy based on CPM
Network
8. Calendars
8.1 Calendar Listing Report listing out in tabular

format the list of calendars used
in the program.
8.2 Year Planner Report illustrating the calendar

in a single page view
9. Program Pricing
9.1 Priced Activity List Report illustrating in detail the

quantities allocated against the
specific activity including the
resource allocation & cost
allowable under the various
resources
10. Time/Location
10.1 Time/Location Report Time location report is a report

showing the method of
summarising and graphically
representing a program against
axes of time and location
Candy Forecasting Reports

1. Linking to Bill of
Quantities
1.1 BOQ with Barchart Report illustrating the BOQ
items in a barchart view keeping
the resource spread offset as
black line with in the red line &
also displaying the activities
allocated against the bill item
1.2 BOQ with Activity Progress Report illustrating the quantities

allocated against the various
activities with program qty to
date view based on progress &
remaining quantity column also
1.3 Barchart with BOQ Report illustrating the Activities

with the boq items allocated as
a barchart view keeping the
resource spread offset as black
line with in the red line
2. Forecasting with
BOQ Links
2.1 BOQ with Budget Forecast Report illustrating the forecast
B.O.Q Nett amounts across the
program time
2.2 Barchart with Budget

Forecast
2.3 BOQ with Resource Usage Report illustrating the fresource
Forecast forecast per bill item across the
program time
2.4 Bill Code Budget by Cost Report illustrating the budget

Code forecast against the various
cost codes in different bill
codedlocations of the entire
project
2.5 Currency Analysis Report illustrating the forecast

amount in the various
currencies used across the
various periods in the program
2.6 Valuation/Planning Report illustrating the

Discrepancies descrepancies between the
quantity allocated against the
activities in the program & the
quantities in the valuation boq
3. Estimate Resource
Forecasts
3.1 Estimate Resource Resource histogram

Histogram report,illustrating the printing of
selected estimating
resource,including both daily
values and cumulative curves
3.2 Estimate Resource Forecast Report illustrating the

forecasted amount across the
imported from the Estimating
Tab in Candy
3.3 Estimate Resource Forecast Report illustrating the
- Inverted forecasted quantity across the
imported from the Estimating
Tab in Candy
Candy Cashflow Reports

1. Cashflow
1.1 Weekly Cashflow

A graph depicting the Inflow,
Outflow, Cashflow, Cost,
Valuations, etc as per the user
defined parameters.
Candy Valuations Reports

1. Valuation Bill of
Quantities
1.1 Valuation Selling Bill - A BOQ view based on the
Carried fwd / Brought fwd valuation to date with carried
and brough forward totals
1.2 Valuation Selling Bill - Page A BOQ view based on the

Totals valuation to date with individual
page totals
1.3 Continuous Valuation Bill - A BOQ view based on the

Selling valuation to date with no page
totals with a summary at the
end.
1.4 Net Valuation grouped by BOQ view with the net rates
Project Codes and net amount
1.5 Variation Order bills - Net A seperate BOQ to see the
progress of any variation
1.6 Archive Valuation Quantities BOQ view with archived
quantities, this is to show the
months movement.
1.7 Listing with Worksheets - BOQ view with remaining costs

Cost and the worksheet breakdown.
2. Indirect Costs
2.1 Indirect Costs Report A list of all the Indirect Costs
2.2 Indirect Costs Barchart An activity barchart showing the

durations for the indirect items
only.
2.3 Indirect Costs Barchart with An activity barchart showing the

Histogram durations for the indirect items
only with a histogram for the
different resources.
2.4 Simple Indirect Costs A list of all the Indirect Costs

which are based on simple
resource pricing.
2.5 Indirect Costs Monthly A list of all the Indirect Costs

Forecast with the monthly net forecast
3. Costs and
Allowables
3.1 Allowables Summary A summary filtered into cost
and/or task codes with actual
qty to date and remaining qty.
3.2 Quantities Summary A summary filtered into cost

and/or task codes with actual
qty to date, remaining qty. and
total qty.
3.3 Costs Summary A summary filtered into cost

and/or task codes with total
amounts
3.4 Cost Allowables by period Comparison of allowable to cost

by Cost Code divided into To-
date, Remaining and
Completion stages
3.5 Cost Allowables by type Comparison of allowable to cost

by Cost Code divided into
Allowable, Cost and variance
amounts stages
4. Resource Lists
4.1 Resource List The list of resource usage

based on the actual qty's to-
date.
4.2 Resource analysis by Project The list of resource usage
codes based on the actual qty's to-
date which can be filtered into
Task codes, etc.
5. Trade Totals
5.1 Trade Total Graph Various graph views filtered into

the different trades
6. Post Tender S/C
Control
6.1 Subcontract Payment Report A summary of the payments
made to the different
Subcontractors
7. Valuations Bills
7.1 Interim Payment Claim (64) A BOQ view of the monthly

claim/ valuation based on
claimed qty.
7.2 Valuation Listings (65) A BOQ view of the monthly

claim/ valuation Witha choice of
quantities to choose from.
7.3 Trade Spreadsheets (66) BOQ items split into the

different trades each on a
seperate trade.
7.4 Dual Currency Listing (67) BOQ view with the primary
currency and the foreign
currency split.
7.5 Value Analysis (68) A listing of all the bill items with
the claimed budget and the
percentage in regards to the
total budget
7.6 Turn-about Document (69)
8. Resource Analysis
Reports
8.1 Valuation Resource Analysis A report listing all resources the
(70) budgetary allowances,
utilisation and the breakup into
the resource types based on the
qty to-date.
8.2 Resources by Bill Item (71) A report listing the resources
breakdown used in each BOQ
item based on the qty to-date
8.3 Analysis by Group/Cost (72) A resource listing grouping

them into the user defined cost/
group codes
8.4 Valuation Production Rates A listing of all the labour

(73) components specific to the
various trades and their
utilisation based
8.5 Resource Percentage (74) A report listing all the resources

and the percentage of the
budget that each resource
consists of to-date.
8.6 Resource Group/Cost A report listing the cost/ group

Summary (75) codes and the split for each into
the resource types based on
claimed qty's.
8.7 Group/Cost Analysis (76) A report listing the cost/ group

codes and the split for each into
the resource types based on
claimed qty's.
8.8 Complex Resource Analysis A report listing indicating

(77) breakdown for any complex
resources based on claimed
qty's.
9. Project Codes
Reports
9.1 Project Codes (78) A report with a filter to view
Task, Bill or Work codes.
9.2 Project Codes Resource A report listing the resource
Analysis (79) breakdown into the Task and/ or
Group codes with more filters
available
9.3 Worksheets by Project Code A report listing the worksheets

(80) in Project code order
9.4 Project Codes Production Production rates listed into the
Rates (81) various codes.
9.5 Project Codes Quantity A report listing the resource
Analysis (82) quantities into the Task and/ or
Group codes with other filters
available
9.6 Project Codes Quantity The project code Quantity

Summary (83) summary reports the total
quantity for each task
10. Wastage Reports
10.1 Wastage Analysis (84) A report listing the wastage

percentage for each resource
used based on qty's to-date
10.2 Price code Wastage A report listing the wastage in to

Allocation (24) the price codes.
10.3 Complex Wastage A report listing the percentage

Allocation (25) wastage, split into the complex
resources based on qty's to-
date
11. Check and Review
Reports
11.1 Page Checksums (85) A Running total of bill qty's
using different sequences
11.2 Pricing Check (55) A report highlighting any
unpriced items
11.3 Provisional Listings (56) Any items that have been priced
provisionally
11.4 Gross/Selling Balance (57) Listing the difference of the
Gross to Selling rates per bill
item.
11.5 Cross Reference (58) A cross refernce of different
criteria and where ekse they
have been used in the BOQ.
11.6 Page Total (59) A summary page of all the

brought forward totals of each
BOQ page.
11.7 Price code Quantity A list of all the price codes

Analysis (60) summarising where they have
been used and the total qty
assigned to each one.
11.8 Rate Discrepancy (61) A list of rate discrepancies

within the BOQ
11.9 Tracers (86) A quick search listing for any

codes.
11.10 Worksheet Calculation A report listing any incorrect
Line Check (63) symbols on the worksheets
11.11 Location Code Check (87) A report listing and
discrepancies in the allocation
fo the Bill Codes
12. Worksheet Reports
12.1 Print Worksheets (88) Worksheet report where the

user can generate the report
keeping either price code
related worksheet orresource
related worksheet based on
selection
12.2 Individual Worksheets (89) Report listing out the selected
price code & Complex
worksheet
12.3 Worksheets in Bill Order A report listing the worksheets
(90) in Bill item order
12.4 Indirect Costs Worksheets Report listing the worksheets for

(91) the Indirect Items in the Bill
12.5 Worksheets by Value (92) A further listing of worksheets
based on a value search
12.6 Worksheets used only in A further listing of worksheets
Macros (93) which have been used to price
a macro item.
12.7 Macro Worksheets (94) A breakdown of the macro

worksheets into their respective
resource types.
12.8 Macro Bills (95) A bill listing all macro pricing

seperately to the main Bill of
Quantity.
12.9 Print Worksheet Chains A report listing the usages of

(96) complex resources and
worksheets and the build of
thereof.
Candy Valuations Subcontract Reports

1. Valuation with
Subcontract Reports
1.1 Continuous Bill with
A report in BOQ format
Subcontract progress
seperating the SC packages
with an indication of the actual
amounts paid.
2. Subcontract Bill
Reports
2.1 Subcontract Payment Report A report in BOQ format
seperating the SC packages
and the payments made.
3. Subcontract
Summary Reports
3.1 Subcontract Summary
A summary report of the
Report
different SC packages with the
respective cost codes and the
total liability for each.
4. Subcontract
Manager Reports
4.1 Extra costs report Extra costs report for each

Subcontractor
4.2 Repairs charged to others Repairs report for each
report Subcontractor
4.3 Contra charges from Main Contra Charges report for each
Contractor report Subcontractor
4.4 Charges from other Charges from subcontractors to
Subcontractors report another subcontractor
4.5 Materials on Site report A summary report for the
materials on site claim from
each subcontractor
BuildSmart Reports
All reports are available in MS Excel, MS Word and PDF Crystal Reports
Section Report Name Report Brief Detail

ERFQ
List Pending
List Current
List Closed
List All
Suppliers
Categories
PROCUREMENT
Purchase Orders Range All Purchase orders
PO Numbers List of PO numbers
POs Per Org Separated per Organization
Requisitions All Requisitions
Requisitions waiting for
Awaiting Approval approval
Order Items Listing Listing by Item
Orders Listing List of orders
Orders By Contract PO's per Contract
Orders By Plant PO's by Plant
Orders By Balance Sheet PO's by Balance Sheet

Orders By Overhead PO's by Overhead
Orders By Supplier PO's by Supplier
Suppliers PO's by Ledger code
Orders By Selection Multiple Selection Matrix
Deliveries Listing List of all deliveries
Deliveries By GRN Delivery list by GRN
Deliveries By Contract, GL Delivery list by contact

Deliveries By OH Delivery list by Overhead
Deliveries By PE Deliveries by Plant Item
Deliveries By BS Delivery by Balance sheet
Deliveries By Stock Deliveries By Stock
Deliveries By Contract, Supplier Deliveries By Contract, Supplier

Deliveries By Selection Multiple Selection Matrix
Deliveries reconciled -
Deliveries matched to an
Reconciled Deliveries Invoice
Deliveries which are
Unreconciled Deliveries unreconciled - no invoice

Unrec Del by Contract unreconciled by contract
Unrec Del by OH unreconciled by Overheads
Unrec Del by Plant unreconciled by Plant

Unrec Del by BS unreconciled by Balance sheet
Unrec Del by Stock unreconciled by Stock

unreconciled by Supplier
Unrec Del by Supp Contract Contract
Unrec Del by Supp unreconciled by supplier
Listing Cancelled Orders List of cancelled orders

Orders not delivered or part
Outst. Orders Listing delivered
Oder's not fully delivered by
Outst. Orders by Contract Contract
Outst. Orders by Contract by Orders not fully deliveries by
Ledger Contract by Cost
Order not fully delivered by

Outst. Orders by Balance Sheet Balance Sheet Ledger code
Orders not fully delivered by
Outst. Orders by Plant Plant Item
Outst. Orders by Stock Stock item

Overhead Ledger code by
Outst. Orders by Overheads Overhead division
Outst. Orders Summary Summary
Committed Cost Report Order placed by Contract
Reconciled Deliveries Invoice Deliveries reference to an
Numbers invoice number
Expected delivery date vs.
Required Vs Delivery Dates actual delivery date
Outstanding Deliveries By
Selection Multiple Selection Matrix
Product By Supplier Supply listing by items
Resources from Candy

showing Tender, Ordered,
Delivered and outstanding in
Resource by Contract quantity, rate and total value
Resources from Candy

showing Tender, Ordered,
Delivered and outstanding in
quantity, rate and total value for
Resource By Stock stock
Resources List of resources from Candy
ACCOUNTS
Admin Reports
List of Users Complete User list
Permissions and rights given to
User Permissions the user
List Of Roles List of roles
List Transaction Types list of transaction types
List of Contacts Complete list of contacts
Setup Reports
List of Organisations Organization list
List of Projects All projects
List of Contracts All Contracts
List of Activities All Activities
List of Ledger Codes All Ledger codes
List of Banks Bank list
List of Currencies Currencies to be used
Budget Listing Budget report
Master File Reports
List of Creditor names and
Creditors addresses
Creditors Age Analysis either

Creditors Age Analysis by open item or all transactions
Creditors Age Analysis either

G1 Creditors Age Analysis by open item or all transactions
Report on Creditors
transactions with option for
single creditor or range of
Creditors Transactions creditor or all
Report on Creditors
single creditor or range of
G1 Creditors Transactions creditor or all
Report on creditors foreign
Creditors Forex Transactions transactions
List of Debtors - Contract
Debtors Debtors, Other and Staff
Debtors Age Analysis reflecting

balance, advance payment and
Debtors Age Analysis retention
Debtors Statement with open

Debtors Statements items or all transactions
Report on Debtors transactions

with option for single debtor or
G1 Debtors Transactions range of debtors or all
Report on Debtors transactions

with option for single debtor or
range of debtors or all -
Debtors Transactions alternate format
Debtors statement with
Debtors Statements Full progressive balance
List of Sub Contracts Names
Sub-Contractor and Addresses
Report on Sub Contractor

single sub Contractor or range
G1 SubCon Transactions or all
Report on Sub Contractor

single sub Contractor or range
Sub Con Transactions or all
Sub Con Commitments Sub Contractor Orders
Sub Contractors by contract

reflecting Work Done, Advance
Payment, retentions, Variation
Sub Contractors By Contract and totals
Sub Contractors by Trade Sub Contractors by trade

Identified key commodities and

Key Commodities the transactions
Asset Reports
Asset Details Details of each asset
Report of depreciation - Book

Value, Last year depreciation,
Depreciation Posting Detail this period and net book value
Deprecation with codes and
Depreciation Schedule values
Asset Master Asset Master report with values

Plant Reports
Plant Location Turnaround Plant Location
Job Card Summary Report Job Card numbers and values
Report on Fuel Consumption

Fuel Consumption including external fuel
Plant Master New Plant Master details
Plant and Equipment details by
P&E Summary by Category Plant category
Plant Location Plant Location
Plant service reports by plant
Plant Servicing Report item, range or all
Plant Readings Report Service Meter reading report

Plant Story Line Report Plant details report
Budget report by Plant Ledger
Plant Budget Report code
Master List Plant Master Report
Plant Transaction by plant item,

Transactions by ledger code, range or all
Utilisation
Detailed costs by plant item for

Detailed Costs a period, range or all
Pivot Table report to create a Pivot Table
Plant and Equipment summary

P&E Summary Report report with total per plant item
Plant transaction by plant item,

by ledger code, range or all -
G1 Plant Transactions alternate format
Plant summary report by Plant
Summary Report Ledger code
Report on cost of tyres per
Type Report plant item
Internal Plant Invoice List of internal plant invoices

Stock Reports
Master stock list by store, by

stock item, with quantity, rate
Stock Master and total value
Stock transactions - receipts,

issues and transfers including
Stock Transactions Detail adjustments
Stock Delivery Note Delivery note of stock received

Delivery note of stock received
Stock Delivery Note per Req by requisition
Stock aged as to how long the

item has been in the store - 30,
Stock Aging 60 90
Stock items containing serial

numbers reported by serial
Serial Number Report number
Stock Reorder List Min quantity report
Stock take sheet with quantity

in stock or with no quantity
Stock Sheets reflected
Stock transaction with drill
Stock Transactions down
Yard Stock Reports
Stock Hire Plant Pivot Internal Yard stock Hire
Contract Stock Summary Yard stock per contract

Yard Stock Hire Yard stock hire by item
Stock Hire Invoice Invoice for internal hire
Stock Hire Report Report on yard stock
Yard Stock Levels Yard stock levels by item
Yard stock location and
Stock Movement Report movement
Costing Reports
Committed Costs Order placed by contract
Detailed transaction of all costs,

accrual and committed costs,
by contract, by period, by
Detail Contract Costs ledger code - ranges or all
Buildsmart Act/Allow Actuals vs. allowable report
Subcontracts by Contract with

work done, retentions, advance
Subcontractor by Contract payments contract charges
Contract Budget Report Contract budget listing
Activity Budget Report Budget listing by Activity
Variance report of actual vs.
Budget Variance Revised budget
Summary of contracts reflecting

Revenue, Costs, Profit Take,
Current period, Year to Date
and Life to date showing
Contract Summary balance in WIP
Combination of Cost by
Consolidated Cost by Contract Contract
Consolidated Costs Consolidation of contract costs

Activity Costs Activity cost report
Activity type report - types

being - Materials, Labour, Sub
Contractors, Plant or as
Activity Cost Type Report specified
Cost summary by Activity by
Costs by Activity Contract
Details contract costs by
Detail Costs by Activity Contract by activity
Summary Contract costs by
Summary Amounts Cost code
Summary costs by debit and

Contract TB credit by cost code by contract
Contracts within a project in
Summary By Project summary form
Summary by Contract Contract cost by summary
Summary Contract Costs Summary costs for current year

Cost Type Report Costs type as defined
Cost Graph Data used for graph
Identified key commodities by
Key Commodities contract
Ledger Reports
List of transaction with
Transaction ID List transaction ID
G2 Trial Balance Trial Balance
Transaction listing by batch, by
Transaction Listing period by ledger code
Transaction listing by batch, by

period by ledger code by
Transaction Analysis reference
BS Transaction list Transaction listing
Transactions by period -
Transactions Per Period selection of periods or all
Batch Transactions All All batched
Transactions by Batch Transactions by specified batch
Transactions Batch By Order Transaction sorted by Order

transactions sorted by
Transactions by Reference reference
Trial Balance Trail Balance
Trial Balance Detail Details trial balance
Trial Balance Month Trail balance - period or month
Overhead expenses by
overhead division - details or
Overhead Expenses summary
Overhead Budget Overhead Budget vs. actual
Plant Budget Plant Budget vs. Actual
Income Statement Income statement
Alternate Format Income
NEW Income Statement Statement
Detailed Income Statement Income Statement with detail

Cash boom details for each
Cash Book bank account
Balance sheet as per balance

sheet setup specified in the
Balance Sheet Setup
Forex Transactions Foreign transactions report

Divisional Reports
Divisional Overheads
Pivot Table
G1 Divisional Overheads
Cost-Budget Report
Consolidation Reports
Consolidated trail balance as
Trial Balance per Org structure
Contract TB consolidated as
Contract TB per Org Structure
Contract Costs consolidated as
Consolidated Cost per Org structure
Overhead Costs consolidated

OverHead Cost as per Org Structure
PAYROLL
Report of all costs and entries

GL Post Report from the payroll to the GL
Costs and all entries per

employee included in ledger
Employee GL Post Report transaction
GL Post Summary Report Summary of GL entries

Total earning and deductions
Period End Report for the month
Period End Validation Validation at month end
Audit Reports
Report of employee, hours and
Audit Trail Hours cost codes
Audit Trail Adv Amounts Advised amounts report
Audit Trail Adv Amounts Cost Audit trail report of all advised
Allocation amounts affecting costs
Report of employees with no

hours or a specific number of
Employees With No Hours hours
Hours by the pay point

assigned to the employee - not
Employee Hours By PayPoint the cost code
Bank Changes By Date Changes in banking details

Bank Changes By Period Changes in banking details
Check on duplicate employee
Duplicate Bank Accounts bank accounts
Inactive Employees Employees no longer active
Contract dates of employees

assigned as limited duration
Limited Duration Contracts contract employees
Financial Reports
Earning and deductions by

employee, range or all, by ED
Earnings & Deductions or range or all
Earnings & Deductions by Earnings and deductions from

Periods between Periods and to a period - range
Earnings & Deductions by Earnings and deductions by

Paypoint pay point assigned to employee
Earnings and deduction by

Earnings & Deductions by employee, range or all by
Period period
Earnings and deduction not
Provisional EDs fixed
Earnings and Deductions by

period, by employee - range or
Periodic ED all
Summary of earnings and
Periodic ED summary deductions
Summary of earnings and
Periodic ED summary by Period deductions by period
Periodic Nett Amounts by
Paypoint Net amount paid
List of earnings and deductions
Periodic ED List by period
Consolidation of Earnings and

Consolidated ED deductions between payrolls
Earning and Deductions by

individual earning and
ED per ED deduction
Payslips Print pay slips
Pay slip report of summary pay
Payslips Summary slips
Coinage report for cash

Coinage Report breakdown
Print cheques for payment by
Cheques cheque
List of all employee and the net
Check List amount payable
Employee Nett Listing Net pay report
Details of balance of loans by
Employee Loans employee by loan
Workmen's Compensation
WCA - Employees detailed report
Summary Hours Per Contract Summary hours
List of employees paid early

due to early settlement for
Early Pay advance leave
Payroll Sheet reflection

employee details, package,
actual earning and deductions
Payroll Sheet with totals
Cost Reports
Cost report by employee, by

contract by cost code by
Detailed Cost activity.
Cost report by employee by
Activity Based Cost contract sorted by activity
Consolidated Cost per Paypoint Costs by assigned pay point

Consolidated Contract Cost,
Hours Hours per contract
Costs by employee, by contract
Consolidated Occupational Cost by occupation
Employee Reports
Master File Master file details
Master File - HR Master file details - alternate 1
Master File - HR2 Master file details - alternate 2
Master File - HR3 Master file details - alternate 3

Contract Allocation Versus Assigned pay point vs. contract
Paypoint allocation
Labels Labels for employees
Active Employees List of Active Employees
Terminated Employees List of Terminated employees

List of terminated employees by
Terminations by Period period
Blocked Employees List of employees blocked
Employee Details Employee full details
Employees Per Paypoint Employee details by pay point
Employee Log Changes made to employee file

Changes made to employee
Employee Rates Log rates
Changes made to employee
Employee Rates Log by Period rates by period
Service Certificate Printed service certificate
Long Service Awards Printed long service award
Key Employees List of Key employees
Employee Occupation Employees by occupation
Employees with contract expiry
Contract Expiry dates
Employee Memo Memo file in employee file
List of employees engaged per
Engagements by Period period
Leave and sick days report -

total due, taken and balance
Leave & Sick Days due
Employees On Leave List on employees on leave
Other Reports
General Log Log of payroll entries
ED Sets List of the Ed setup
Payroll Periods Pay period and the dates
Materiel multiple selection

User Defined matrix
BuildSmart HR Reports
Company & Audit
Reports Accidents Summary
Audit Detail
Audit Trail
Bank Information
Clothing Summary
Company Details
Company Funds and Deductions

Details / Rules
Company Insurances
Company Organisation (Linked
Employees)
Company Organisation
Summary
Company Vehicles
Contract Summary
Disciplinary & Misconduct
Summary
Education Summary
Equipment Summary
Expiry Audit Summary
Grievance Summary
Labour Turnover Summary
(new)
Language Summary
Licence Summary
Mandatory Information
Marital Status Summary
Mass Capture Details HR Info

Medical Summary
Passport Summary
Project History Summary

SMS Audit
Shares Summary
Visa Summary
Employee
Reports Accident Details
Active Employee Information

Anniversary List
Birthday List
Certificate of Service
Clothing Details
Contract Details
Custom Report
Dependant, Next of Kin &

Emergency Contact Details
Disciplinary Actions, Misconduct

and Grievance Details
Education Details
Email Notification Employee
Details
Employee Due to Retire List
Employee Engaged/Transferred
In List
Employee Head Count Totals

Employee Head Count by
EEquity
Employee Head Count by
Employment Type
Employee Language Details

Employee Maintenance Details
Summary
Employee Maintenance
Mandatory Details Exception
Employee Mass Capture Leave
Records
Employee Personal Information

Update Form
Employee Service/Anniversary
Summary
Employee
Terminated/Transferred Out List
Employment Details Summary
Employment Status by Interval
Employment Status Summary

Engagement Checklist
Equipment Details
Exit Details
Housing Details
Insurance Details
Job History Details
Length of Service
Licence Details
Marital Details
Medical Details
Membership Details
Monthly Package for the Year

Offences Details
Package/Rate of Pay Details

Passport & Visa Details
Previous Employment Details

Project History Details
Rate of Pay (Change)
Rate of Pay (Current)
Recruitment History Details

Shares Details
Staff Movement (inc. Headcount
Details)
Summary of Employee Cost
Centre Splits
Summary of Employee Details
Summary of Employee Funds
Summary of Employee Statistics
Termination / Suspension /
Transfer Details
Vehicles and Licences Details

Annual Leave Details &
Forms and Templates: Requests
Clothing Request Form
Dependent Record Form
Disciplinary Record Form

Emergency Contact Record

Form
Employee Basic Appraisals
Employee Maintenance Form
Employee Personal Information

Update Form
Employee Take-on Form
Populated
Employee Take-on Form
Engagement Checklist Form
Equipment Request Form

Grievance Record Form
Loan Application
Misconduct Record Form

Next of Kin Form
Notice to attend Disciplinary

Enquiry Form
Sick Leave Details and
Requests
Absenteeism Summary (% vs.

Leave Reports Theoretical) (By Leave Type)
Booked Leave (all leave types)
Current Leave Entitlements (By

Leave Type)
Current Theoretical Leave Cost

Per Day (By Leave Type)
Custom Leave Report
Employee Annual Leave
Movement
Employees On Leave (By Leave
Type)
Leave Liability (as per payslip)

Outstanding Leave (Stat vs.
Additional)
Sick Leave Analysis (days of the
week)
Sick Leave Cycle Information
Sick Leave, Family

Responsibility & Child Care
Record Summary
Summary of Annual Leave

Details (as per leave screen)
Summary for Annual Leave
Records
Summary of Annual Leave

Taken & Adjustment Records
Loans, Garnishees &
Savings Reports Employee Loan Balances
Employee Requested Loans

Employee Requested Savings /
Provisions
Employee Savings Balances

Performance and
Succession Reports Appraisals Details Template
Appraisal Summary
Employee Appraisal Details
Employee Performance and

Potential Analysis Details
Employee Risk and Retention

Analysis Details
Employee Promotability Analysis

Details
Skills and Training Annual Training by Occupational

Reports category (by Employee)
Annual Training by Occupational

category (by Intervention)
Development Need Summary
Development Plans Summary
Employee Development Need

Details
Employee Development Plan

Details
Employee Master Training
Details
Employee Training Details by

OFO Major Group & Codes
Employee Training Details by

Occupational Category
Employee Training Restriction
Details
Employee Training Summary

Experience Summary
Learning Matrix Summary

Skills Matrix Summary
Skills Summary
Skills and Training Details

Training Age Profile
Training Cost Summary
Training Not Received Summary
Training Received Summary
Training Restrictions Summary
Training Summary by OFO

Major Groups & Codes
Training Summary by
Occupational Category
Workplace Profile
Advanced Module
Reports:
Position Management Organisational Unit Position

Reports Hierarchy Report
Organisational Unit Detail
Report
Position Audit Report
Position Budget vs Actual Costs
Report
Position Detail Report
Position Linear Hierarchy Detail
Report
Position Vacancy Report

Job Description Employee Job Comparison
Management Reports Report
Employee Training and

Development Gap Analysis
Report
Job Budget vs Actual Costs
Report
Job Description Detail Report

Job Profile Report
Training Management
Reports List Course Master Details Report
External Venue Details Report
Internal venue Details Report

Business Intelligence is used for reports specific to ADC

See mgt dashboard final v1.wmv
Management Pack.xls
C Form - Generic Example.xls

BuildSmart Time and Attendance
BSmart Mobile Time and Attendance is the approved Time and Attendance product Partner to
BuildSmart.
It is the only Time and Attendance System that is fully integrated with the SmartPay and BuildSmart
Human Resource Management system, and therefore allows you to observe your labour costs on a daily
basis.
Benefits:
Cost Saving
Increased profits
Eliminate Ghost Workers
Live - Real - Time Control and Costing
Speed up administration processes in office
Electronic audit trail
Eliminate manual capturing of timesheets
Provide accurate and live management reports
Effective Management of Labour Production
Live Real - Time Labour and Sub-Contractor Attendance register
Seamlessly integrate into the payroll and HR to ensure accurate labour costs are recorded in real-time
Features:
Software Hardware
Web based GPRS and GPS, WLAN, 3.5G, GSM, HSDPA, Wi-Fi
Effortless implementation
From Entry Level Devices up to Advanced Devices
User Friendly
Accurately track contract labour by project, Optical Biometrical Readers
contract, and activity costing
Options of Mobile and Fixed units for different applications
Track production in BuildSmart, labour costing
by task by trade Access Control and Time and Attendance
Ensure Biometric readers function effectively
every time (Even when fingerprintsare not
visible with the naked eye)
Mobile Time and Attendance Software

Desktop Software
Optical Biometric Fingerprint Recognition
Web Based Management Console

Cost Reallocation
SmartPay Integration
Importing Clock Cards

Clock Card Batch Imported
BuildSmart Timesheet View

Solution Specifications (Section 7) - CCS Response

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Solution Specifications (Section 7) - CCS Response

Transféré par

Droits d'auteur :

Formats disponibles

Construction Computer Software

7. Response to Solution Specifications

7.2 Solution Specification

Business Development, Estimating & Tendering, Award

The CCS solution kicks off with Candy Estimating.

Procurement, Finance. HR and Administration

Details of all software modules that will be deployed

BuildSmart: the Project Management / SDLC methodology to be adopted in the Implementation

The design approach in terms of process and blueprint definition:

The design phase, which is client specific, covers the following:

Company Organizational Structure

The testing approach (Unit, UAT and SIT testing);

Running the existing and new systems in parallel:

Adoption of a new and/or changes to the current chart of accounts:

Changes to business processes to accommodate the new system:

The change management approach to be adopted.

Managing the effective planning of the implementation.

Refer to the CCS Implementation plan ADC - CCS Implementation Plan.pdf

BuildSmart works effectively in multi-national and multi-organisational environments. BuildSmart allows

Within an Enterprise, there is no limit on the number of organisations:

The organisation tree would then follow:

CANDY INSTALLATION AND SET UP

Candy user types

Candy administrative user

Candy non-power user

Predefine list of Staff

Predefine list of Roles

Predefine list of Events

Predefine list of User installation types

Single user environment (standalone)

Peer to peer environment (p2p)

Client server environment (c/s)

Candy network installation

Setting up the candy application server

Establish the Candy application server computer name.

Setting up the candy shared data space

..\CCSDATA\CCSCOM (contains the Candy backups shared by the user group);

..\CCSDATA\CCSMAST (contains the Candy network master libraries); and

..CCSDATA\CCSMULTI (contains the Candy multi user concurrent accessed libraries)

Setting up the users candy data space

Setting up the candy client

\\<computer name>\<share name>\CCSWIN\SYSTEM\CCSVFX.EXE for UNC.

X:\CCSWIN\SYSTEM\CCSVFX.EXE for network mapped drive.

Launching the candy application

First time launch

o Password and licence settings.

o Licence settings and system information for support.

Candy shared data

\\<computer name>\<share name\CCSDATA\CCSCOM for UNC.

X:\CCSCOM for network mapped drive.

Candy Network Masters:

\\<computer name>\<share name\CCSDATA\CCSMAST for UNC.

X:\CCSMAST for network mapped drive.

Multi User Company:

\\<computer name>\<share name\CCSDATA\CCSMULTI for UNC.

X:\CCSMULTI for network mapped drive.

<user home directory>\CCSDATA

Candy shared data setup

Concurrent Data access

Data exchange and shared libraries

Shared Data Folder layout

Data Server in the Internet Cloud

Candy Backup and Recovery

Note any additional third-party components that are required