Answer To: Project Notification Form Project Status and Control Report Name of Project PPMP...
Tanmoy answered on Jan 02 2021
TENDER
DOCUCUMENT
XYZ COUNCIL
NSW
IMPLEMENTATION
OF
CORPORATE PLANNING & REPORTING SYSTEM
JANUARY 2020
1
Tender Schedule 1 – Tender Form
Project #:
14041
Project Name: Corporate Planning and Reporting System (CPRS)
Dated: 03/01/2020
Registered name of Tenderer: Microsoft Dynamics 365
Trading name: Microsoft
Registered office / business address: 718 Washington Ave. N, Suite #101, Minneapolis, MN 54001, United States
.............................................................................................................................................................
Mailing Address: : Level 8, 1 Pacific Highway, North Sydney, NSW 2060, Australia
.............................................................................................................................................................
Australia Business Number (A.B.N.): ABN 260036825111
Contact person: Power objects, Microsoft Dynamics 365
Office telephone number: +61 1800 013 664
Outside USA telephone number: +1 612 339 3355
Facsimile number:
Email address:
Website address: https://www.powerobjects.com/contact/dynamics-365-services-australia/
The party/parties [delete whichever is not applicable] specified above hereby tender to provide the Services based on the Conditions of Contract in consideration of the
making of the following payments by Council.
1. Lump Sum for Services under the Contract .......................................
$ 678500
2. 10% Goods and Services Tax .............................................................. $ 67850
3. Total Lump Sum tendered (Sum of items 1 & 2 above) .................... $ 746350
.........................................................................................
Signature of Authorised Person
.........................................................................................
Name of Authorised Person (Please print)
2
Tender Schedule 2 – Breakdown of Lump Sum Tendered
Please provide below a breakdown of the lump sum tendered in Tender Schedule 1:
Item
Item Description
Person Days
Price
Including GST
Allowed
(If applicable)
1
Software including licence to facilitate up to 120 concurrent users.
Description of Software:
Not applicable
$600000
CLOUDERA HADOOP SOFTWARE
...............................................................................
...............................................................................
...............................................................................
2
Software modifications required to base product to meet Council’s system requirements
......................
$10000
3
Software delivery
......................
$2500
4
System administration training
......................
$5000
5
System configuration and Integration services
......................
$8000
6
Acceptance testing
......................
$8000
7
End user training
......................
$10000
9
Support and maintenance for the first 12 months
Not applicable
$25000
10 Other1
......................
$10000
Total Lump Sum
Tendered
$678500
Note 1 – Please specify any additional costs that the Tenderer will need to incur to successfully implement the proposed solution that are not included in Items 1 to 10.
3 Tender Schedule 3 – Optional Modules
The optional modules may be purchased by Council in addition to the CPRS and associated items, as priced in Tender Schedule 2. No guarantee is given that any of the modules will be purchased by Council.
Item
Item Description
Supply and
Installation1 Cost
Including GST
1
Risk Management Module
(if not included in Tender Schedule 2)
This module will enable users to create, store and report on the Strategic and Operational Risk Register.
...............................................................................
$ N.A.
2
Project Planning Module
(if not included in Tender Schedule 2)
This module will handle project planning, selection, budgeting, and programming.
...............................................................................
$N.A.
3
Performance Planning Module
This module will enable users to create, store and report on the Staff Performance Plans.
$ N.A.
$ N.A.
Supply and
Item Item Description Installation1 Cost
Including GST
5 Other (Please specify)
N.A. $ N.A
...............................................................................
NOTE 1 - Installation costs include all the Items (1 to 11) listed in Tender Schedule 2.
4
Tender Schedule 4 – Ongoing Items
Item
Item Description
Price
Including GST
1
Annual support and maintenance services fee for CPRS (after the first 12 months included in Item 9 of Tender Schedule 2) including
helpdesk services, new releases, updates, software patches and fixes.
$ 25000
2
Software licence fee for each additional user (beyond the 120 users included in Item 1 of Tender Schedule 2)
$ 600000
3
Other (If there are any additional ongoing fees, please specify below)
...............................................................................
$ .N.A..
5
Tender Schedule 5 – Technical and Functional Requirements
Council’s technical and functional requirements are weighted as either “Mandatory”, “Highly Desirable” or “Desirable”, as defined below:
Weighting
Code
Description
Mandatory
M
A requirement that is considered essential to the day-to-day running of Council business. If this requirement is not met, Council will not
be able to operate at an acceptable level.
Highly Desirable
HD
A requirement that is important to Council. If this requirement was not met, Council would still be able to operate, albeit at a sub-optimal
level.
Desirable
D
A requirement that provides some benefit to Council but would not create significant additional work if it were not met.
The Tenderer shall indicate the extent to which its tender response complies with the technical or functional requirements in the tables below by ranking each requirement as either “Complies”, “Partially Complies” or “Does Not Comply”, as defined below:
Level of Compliance
Code
Description
If ‘Complies’ is nominated, this means that the tendered solution currently fulfils the requirement “out of the box” (i.e. without
Complies
C
configuration) or has the ability to be configured to fully comply with the requirement, the requirement is met within the overall cost of
the tendered solution, and can be demonstrated within the production version of the nominated application/s at the time of submitting
the tender response. If ‘Complies’ is nominated, then the ‘Explanation’ column should NOT be completed.
If ‘Partially Complies’ is nominated, the extent to which the solution complies must be explained in the ‘Explanation’ column. If it is
expected that a modification is required to comply with the requirement, then an appropriate comment should be made in the
Partially Complies
P
‘Explanation’ column and costs included in the ‘Price’ column and in Tender Schedule 2. Failure to qualify ‘Partially Complies’ responses
with a reasonable explanation will be treated as a statement of non-compliance.
If the Tenderer believes that an alternative that satisfies the intent of the requirement is available and the requirement can be met via an
alternative within the overall cost of the tendered solution, then this must be explained in the ‘Explanation’ column.
Does Not Comply
D
If ‘Does Not Comply’ is nominated, this will mean that the proposed solution does not comply with the requirement and the Tenderer
does not propose the development of the solution to provide any level of compliance.
5.1 System Features
To implement an integrated corporate reporting system with the following technical features and requirements that are to apply across all modules of the system 5.1.1 User Interface
Level of
Weighting
Item Requirement Compliance Explanation (M, HD or D)
(C, P or D)
General
The system must support the following client interfaces:
-
Workstation Windows 10
1
M
-
Common internet browsers
2
M
-
Thin client (citrix)
3
M
All user interfaces to the system must support the following:
- Compliance with the World Wide Web Consortium
M
4
(W3C) accessibility requirements
- Concurrent display of multiple windows and simple
M
5
switching between these windows
- The ability to scroll through data lists
M
6
- Common keystrokes for cutting, copying and pasting
M
7
-
Drag and drop
M
8
- The ability to use context sensitive / smart picklists to
M
9
achieve consistent data input
Weighting
Level of
Item
Requirement
Compliance
Explanation
(M, HD or D)
(C, P or D)
10
- The ability to cancel an operation and return to the
M
previous screen
11
- Calculator pop-ups for all numeric fields and calendar
HD
pop-ups for all date fields
12
Personalised portal showing customisable dashboard
M
13
Personalised portal showing outstanding actions
M
(customisable by user/group)
14
Ability to easily re-use last update where little or no change
HD
has occurred
15
Ability to spell check both user reporting updates and action
HD
items from plans
Workstation
16
Where tables or lists are displayed, it must be possible to
M
sort a column by selecting the column header.
The system must support the use of default file locations for
17
functions such as import and save, based on individual user
M
preferences
18
The system must ensure that printing is accomplished via
M
the MS Windows environment printer settings
19
The system must utilise function keys for shortcuts in
M
navigation.
20
The system must utilise pop-up windows or similar for
M
access to reference information
21
The system must provide mouse-overs for help on screen
M
items.
22
The system must provide context sensitive help, including
M
full use of the mouse, and right-click menus
Browser User Interface
Weighting
Level of
Item
Requirement
Compliance
Explanation
(M, HD or D)
(C, P or D)
23
The system must be capable of delivering all modules of the
HD
application through an Internet browser
24
The system must support the latest version of Internet
M
Explorer
25
The system must provide secure access for external
M
contractors
The system must recognise the user logged on to the
Council network via Council Active Directory and provide
26
permissions relating to their user profile. Otherwise the
M
system must require a username and password for all users
to logon
27
Passwords sent over the network or internet must be
M
suitably encrypted
The system must restrict external access to designated
workstations using the following methods:
28
- IP Address or IP Address range
M
29
- Public/Private Keys
M
30
Each transaction type undertaken in the browser
M
environment must be supported by encryption
31
The browser user interface must generally mirror the
HD
windows client layout and functionality as practical
32
Printer-friendly pages must be available (i.e. Pages without
HD
menu options and cut down header and footer)
33
A user must have the ability to initiate multiple distinct
HD
sessions in separate browser windows
34
Every page must have a context sensitive link to a relevant
HD
help page
The system must provide the following rules for logging out
of system:
Weighting
Level of
Item
Requirement
Compliance
Explanation
(M, HD or D)
(C, P or D)
35
- A user must be able to explicitly logout
HD
36
- The user must be automatically logged out of system
HD
when the browser is closed
37
- Logging out must occur after a pre-defined timeout
HD
38
The system must not cache any user data
HD
39
The system must not use cookies to store user data
HD
5.1.2 Data Management
Weighting
Level of
Item
Requirement
Compliance
Explanation
(M, HD or D)
(C, P or D)
Transactions
Data Entry
- When entering data, the system must support
comprehensive rule checking and real-time validation
M
including display of field descriptions for confirmation
or appropriate error / warning message where invalid.
- The system must have the ability to date and time
M
stamp all data entry.
- The system must support simultaneous data entry by
M
multiple users.
- Where applicable, the system must enable dynamic
creation of reference codes during data entry (on the
M
fly) for completion later, subject to security e.g. valid
combination of account elements.
- The system must automatically populate appropriate
fields with the ability to overwrite and change, subject
M
to a users' permission
Processing
- The system must have the ability to prioritise execution
HD
by specific user groups
- The system must be able to put a process on 'hold'
letting the user carry out an enquiry, then return to the
HD
original transaction.
- The system must provide batch and real-time
M
processing when appropriate
- The database must possess version control of all
HD
committed data to facilitate rollback/roll-forward
Weighting
Level of
Item
Requirement
Compliance
Explanation
(M, HD or D)
(C, P or D)
- The system must carry out validation of data on
individual fields and field dependencies and validations
M
against parameters, tables etc.
- The system must be able to provide on-line real-time
validation of input fields, including display of field
M
descriptions for confirmation or appropriate
error/warning message where invalid.
- The system must provide user-defined export of
HD
transactions/records to other software systems
- The system must support retrospective changes to data
M
(e.g. for a previous period) subject to strict security
- The system must handle multi-user file access for
M
updating/ reporting
- The system must be capable of handling transition to
and from Daylight Savings periods with no manual
HD
intervention or impact on business processes
Database
General
- The system must be able to run on Microsoft SQL
M
Server 2005
- The software development procedures must comply to
HD
ISO 12207 standards
- The system must be certified for the virtual
M
environment
- The system must enable user defined queries to be
HD
built and stored within the database
- The system must be able to prevent simultaneous
M
update of the same record (i.e. record locking)
Archiving
- The system needs to have an effective archiving tool
HD
plus ability to access archived data
Weighting
Level of
Item
Requirement
Compliance
Explanation
(M, HD or D)
(C, P or D)
- The system must have the ability to create output files
for archival purposes on a periodic basis, for example,
HD
monthly, and retrieve them easily
- The system must have the ability to re-import archived
HD
data if it is required for reporting purposes.
- The system must have the ability to archive data in a
standard form (e.g. XML) such that it can be imported
HD
into a third-party data warehousing/reporting tool
System Documentation
- The tenderer must supply complete and
HD
comprehensively documented database schemas
- The tenderer must supply documented entity
relationship diagrams clearly defining the relationships
HD
between all entities and attributes
- The tenderer must supply a comprehensive
documented data dictionary clearly defining all entities
HD
and attributes
- The tenderer must supply documentation describing all
HD
database views, stored procedures and queries
- All interfaces must by comprehensively documented
(including data, primary/foreign keys, file/message
M
formats, interface methods, and timing)
- Upgrades to documentation must be provided with
M
application upgrades
- The system must provide for application/ management
'tools' with user support documentation where
M
appropriate
Administration
User Maintenance
- The system must allow the setup and control of:
Weighting
Level of
Item
Requirement
Compliance
Explanation
(M, HD or D)
(C, P or D)
>
Users
M
>
Groups of Users
M
- The system must ensure that user control is centralised
and applied to all its components i.e. the administrator
M
should not have to create separate users for each of the
system's components
- The system must allow the Administrator to add, make
inactive and re-activate users, user groups and business
M
units
- The system must have the ability to disable or enable
logins to the Server for all clients or groups with an
M
appropriate message displayed to the user, including
timing out unused sessions
- The system must allow a system administrator to
perform the following tasks with respect to system
users:
> Create new users on the system
M
> Assign access privileges to screens
M
> Assign access privileges to queries and reports
HD
> Assign user privileges for all functions i.e. access,
M
read, update, delete
> Assign user privileges for specific data within
M
datasets i.e. access, read, update, delete
· The system must ensure that a user's access privilege
also controls data accessible by screens, reports and
M
report writers, not just on-line access
· The systems must provide the following functions for maintenance of User Groups:
Weighting
Level of
Item
Requirement
Compliance
Explanation
(M, HD or D)
(C, P or D)
> Security set-up by user group/ templates (to
M
minimise maintenance)
> Security set-up by user, allocating to specific user
M
group/ template
- The system must provide the following user-related
reports:
> Users by user group
HD
> Users by system function
HD
> Users by business unit
HD
> Users by security classification
HD
> User groups by system function
HD
> User groups by business unit
HD
> User groups by security classification
HD
> System functions by user
HD
> System functions by user group
HD
Security
- System databases must be secure from direct access
from other applications, tools, or end-user application
M
packages
- The system must ensure that it is not possible to
circumvent security restrictions simply by accessing the
M
database directly.
- The system must ensure that there is automatic
consistency between application security controls and
M
database security controls
Weighting
Level of
Item
Requirement
Compliance
Explanation
(M, HD or D)
(C, P or D)
- The system must ensure that users can only access the
data to which they have assigned rights, including data
M
in reports and queries
- The system must allow the system administrator to
M
monitor and control system usage.
- Access to the server must not circumvent access
M
control mechanisms
- The system must provide the following security
controls:
> Prevention of unauthorised access via external
M
database connections e.g. ODBC
> Set-up and modification of security components
M
by the System Administrator.
> Define the level of security and privileges for
M
specified Internet customers
- The system must integrate with Microsoft Active
Directory logon security and provide both pass-through
M
authentication and manual sign-on
- A common user security control must be used for all
M
environments
- The system must identify each user as they logon
M
· The system must log security violations (i.e.
unsuccessful logons) by showing date, time, terminal
M
ID, user ID and password attempted.
-
The system must provide the following password
security functions:
> Passwords must be valid for a period defined by
M
the System Administrator.
> Encrypted password storage
M
> Provide the user with the ability to change their
M
password
Weighting
Level of
Item
Requirement
Compliance
Explanation
(M, HD or D)
(C, P or D)
> User ID must be disabled after several
unsuccessful attempts to be defined by the
M
System Administrator.
> Allow a minimum password length to be set
M
> Prevent password re-use
M
Upgrades
- The solution must ensure that any system upgrade is
M
seamless to the end user
- A system upgrade must be performed with no
requirement for staff to physically visit the end user's
M
PC
- The system must display to the user the version history
M
and features/functions installed
- System upgrades must not adversely affect existing
M
functionality
- All software upgrades must be fully tested and
documented at the supplier's cost, before delivery and
M
installation.
- The tenderer must support the current and two
previous major releases of all components which are
M
part of the system
- Software upgrades must be backward compatible with
M
previous versions of the software and data.
- The setup programs for the client software must be
capable of being run completely in silent mode,
M
obviating the need for any user input during the setup
process
- The system must upgrade mobile devices when docked
M
into the network
Auditing
Weighting
Level of
Item
Requirement
Compliance
Explanation
(M, HD or D)
(C, P or D)
- The system must provide an audit trail of all transaction
additions, changes and deletions showing date, time,
M
user id and network address
- The system must provide an audit trail of all views,
additions, changes and deletions to tables and fields
M
showing date, time and user id
- The system must have the ability to generate audit trail
reports/ enquiries with administrator control over their
M
deletion/ retention.
- The system must provide an audit trail of all reports
and queries generated (i.e. report log) showing date,
HD
time submitted/ time completed, user id and no. pages.
- The system must create an audit trail (including the
operator and time) of all changes to the security
M
settings
- The system must provide queries and reports to enable
M
the System Administrator to view each audit trail
- The system should provide auditing reports based on a
M
specified user or specified function
Monitoring
- Data Monitoring:
> The system must be able to time, date and user
M
stamp all database entities
> The administrator must be able to edit prompts
and warnings associated with data edit, and
D
whether these prompts and warnings appear to
the user
> System Administrator or Power users must be
able to create and set dependent fields i.e. If
'roads' is selected as an asset category, then only
M
roads related assets and related fields appear in
the asset sub-category
Weighting
Level of
Item
Requirement
Compliance
Explanation
(M, HD or D)
(C, P or D)
- User Monitoring:
> The system must allow the System Administrator
to monitor the extent of usage for all
environments, including queries and reports
HD
generated by users and summary statistics of
data usage
> The system must have the ability to check current
HD
logins to the Application Server
> The system must have the ability to terminate
D
user sessions
> The system must provide queries and reports to
enable the Administrator to view:
# Number of users using the system
D
#
Highest concurrent usage
D
# Number of users licensed
D
#
Database requests
D
# Database Read Write requests
D
> The system must have the ability to report on the
following information about users:
# Queries run (SQL statement)
D
# Server response time for queries
D
# Number of objects returned by query
D
# License usage (in minutes)
D
#
Datasets accessed
D
Weighting
Level of
Item
Requirement
Compliance
Explanation
(M, HD or D)
(C, P or D)
# ...