Attachment F14a SPS SaaS HCM Solution

Non-Functional Requirements RFP # 060B3490012

Vendor Responses:
OB - Out of Box RT - Reporting Tool UC - Customization with Cost
CW - Configuration with Cost TP - Third Party UO - Customization without Cost
CO - Configuration without Cost NM - Not Met
CB - Candidate for BPR FR - Future Release

If OB, CW, CO, CB, UC, UO, or RT is used, offerors MUST list the module(s)/Sub-module(s) used to fulfill functionality in Module(s)/Sub-module(s) required column.
If FR is used, offerors MUST list the module used to fulfill functionality in Module(s)/Sub-module(s) required column and specify the release date in the comments column.
If TP is used, Offeror MUST specify the proposed software with details.

Requirements Area To Be Completed by Vendor

Function Process Sub- Category Req. # Requirement Description Module(s)/ Response Comments
Code Process Sub-module(s)
Required
SPS Non-Functional Architecture Accessbility SPSNFR-1 The System shall be 100% Web-enabled, i.e., all functions
can be accessed via a web browser and requiring no
installation on client workstations for Client/Agents/Suppliers
(self-service).

SPS Non-Functional Architecture Accessbility SPSNFR-2 The System shall provide the capability to deliver content to
Mobile devices such as Blackberry, PDAs and smartphones.

SPS Non-Functional Architecture Accessbility SPSNFR-3 The System shall deliver content via popular web browsers
such as Microsoft Internet Explorer, Mozilla, Chrome, Safari,
and Netscape.
SPS Non-Functional Architecture Audit and Control SPSNFR-4 The System shall provide audit on transactions including but
not limited to when the changes were made, by whom the
changes were made, and details of the field values before
the change and the field value after the change.

SPS Non-Functional Architecture Audit and Control SPSNFR-5 The System shall have the capability to log events/actions
(additions, changes, deletions to data).

Page 1 of 34 May 22, 2013

Attachment F14a SPS SaaS HCM Solution
Non-Functional Requirements RFP # 060B3490012

Requirements Area To Be Completed by Vendor

Function Process Sub- Category Req. # Requirement Description Module(s)/ Response Comments
Code Process Sub-module(s)
Required
SPS Non-Functional Architecture Audit and Control SPSNFR-6 The System shall have the capability to log events/actions
related to identification and authentication process.

SPS Non-Functional Architecture Audit and Control SPSNFR-7 The System shall have the capability to log actions
performed by system and technical support personnel.

SPS Non-Functional Architecture Audit and Control SPSNFR-8 The System shall have the capability to log emergency
actions which are performed by system support and security
personnel.
SPS Non-Functional Architecture Audit and Control SPSNFR-9 The System shall provide the capability to log key attributes
of audited events in the audit trails, to include but not limited
to the date and time of the event, user id of a person
performing the action, event type, asset or resource name
and type of access, Success or Failure of event.

SPS Non-Functional Architecture Audit and Control SPSNFR-10 The System shall have the capability to log audit trails of a
specific event such as a Source (terminal, port, location, IP
address) where it is technically feasible.
SPS Non-Functional Architecture Audit and Control SPSNFR-11 The System shall log two (2) or more failed attempts per
system day to access / modify security files, password
tables or security devices
SPS Non-Functional Architecture Audit and Control SPSNFR-12 The system shall provide the capability to capture, retain and
analyze authorized and unauthorized user audit trails

SPS Non-Functional Architecture Audit and Control SPSNFR-13 The System shall have the capability to log two (2) or more
failed attempts to access / modify confidential information
and report within 24 hours.
SPS Non-Functional Architecture Audit and Control SPSNFR-14 The SaaS Provider shall perform all system and
infrastructure audit trails reviews on a weekly/monthly/as
needed basis to alert any inappropriate practices within 24
hours.

Page 2 of 34 May 22, 2013

Attachment F14a SPS SaaS HCM Solution
Non-Functional Requirements RFP # 060B3490012

Requirements Area To Be Completed by Vendor

Function Process Sub- Category Req. # Requirement Description Module(s)/ Response Comments
Code Process Sub-module(s)
Required
SPS Non-Functional Architecture Audit and Control SPSNFR-15 The SaaS Provider shall develop Preventive and detection
controls to prevent or limit the risk of unintentional errors or
unauthorized users accessing the System and modifying
data.

SPS Non-Functional Architecture Audit and Control SPSNFR-16 The SaaS Provider shall provide automated tools to review
The System and infrastructure audit trails of user actions.

SPS Non-Functional Architecture Audit and Control SPSNFR-17 The System shall provide configurable auditing capability
with user defined security controls.
SPS Non-Functional Architecture Audit and Control SPSNFR-18 The System shall provide the capability to audit configuration
transactions.
SPS Non-Functional Architecture Audit and Control SPSNFR-19 The System shall provide auditing of all workflow
transactions and electronic signatures /Approvals.
SPS Non-Functional Architecture Audit and Control SPSNFR-20 The System shall provide the capability to audit internet and
intranet transactions. Data logged includes, but is not limited
to IP Address, Date and Time and historical transaction
records

SPS Non-Functional Architecture Availability SPSNFR-21 The OLTP System shall have 99.5% system availability and
business continuity (i.e. Disaster Recovery, Fail-over).

SPS Non-Functional Architecture Availability SPSNFR-22 The OLAP System shall have 90% system availability and
business continuity (i.e. Disaster Recovery, Fail-over).

SPS Non-Functional Architecture Availability SPSNFR-23 The System shall ensure that only authorized users can
access the information.
SPS Non-Functional Architecture Availability SPSNFR-24 The System shall provide the capability of data retrieval and
management in an accurate, reliable and timely manner.

Page 3 of 34 May 22, 2013

Attachment F14a SPS SaaS HCM Solution
Non-Functional Requirements RFP # 060B3490012

Requirements Area To Be Completed by Vendor

Function Process Sub- Category Req. # Requirement Description Module(s)/ Response Comments
Code Process Sub-module(s)
Required
SPS Non-Functional Architecture Availability SPSNFR-25 The System shall be available to be used 24x7/365 except
scheduled maintenance time, mutually agreed upon and
approved by the State and the SaaS Provider, with no
external hardware/software (Virtual or Cluster) fault
tolerance. This must be achieved with no additional cost.

SPS Non-Functional Architecture Availability SPSNFR-26 The System shall be available to be used from remote
locations outside the State’s owned network.
SPS Non-Functional Architecture Availability SPSNFR-27 The Production OLTP System shall be restored to
operational level within 15 minutes to 1 hour (after specific
configuration changes) from the time a disaster occurs.

SPS Non-Functional Architecture Availability SPSNFR-28 The non-production OLTP System shall be restored to
operational level within 48 hours from the time a disaster
occurs.
SPS Non-Functional Architecture Availability SPSNFR-29 The SaaS Provider shall provide technical and application
upgrade path cycle with no interruption to end-user
availability.
SPS Non-Functional Architecture Backup SPSNFR-30 The System shall provide the capability to use a back up
copy to restore only the needed data to the existing
environment in case small amounts of data is lost due to
accidental deletion or file corruption.

SPS Non-Functional Architecture Backup SPSNFR-31 The System shall provide the capability to use a back up
copy to restore an alternate environment in the event of a
disaster that results in damage to or unavailability of data
across an entire system.

SPS Non-Functional Architecture Backup SPSNFR-32 The System shall provide the capability to perform weekly
full cold backup of all relative data (file system).

SPS Non-Functional Architecture Backup SPSNFR-33 The System shall provide the capability to perform full
complete daily 'hot' backups.

Page 4 of 34 May 22, 2013

Attachment F14a SPS SaaS HCM Solution
Non-Functional Requirements RFP # 060B3490012

Requirements Area To Be Completed by Vendor

Function Process Sub- Category Req. # Requirement Description Module(s)/ Response Comments
Code Process Sub-module(s)
Required
SPS Non-Functional Architecture Backup SPSNFR-34 The System shall provide the capability to perform backup
processes during the scheduled maintenance windows.

SPS Non-Functional Architecture Backup SPSNFR-35 The System shall provide the capability to perform backup
processes with built-in error checking / recovery capabilities.

SPS Non-Functional Architecture Backup SPSNFR-36 The SaaS Provider shall establish procedures and standards
to implement an agreed backup policy and strategy that
includes the extent (e.g., full or differential/incremental),
frequency, offsite storage, testing, physical and
environmental protection, restoration, and encryption.

SPS Non-Functional Architecture Backup SPSNFR-37 The SaaS Provider shall establish procedures and standards
to implement retention policies, standards, legal and
business rules, mutually agreed upon and approved by the
State and the SaaS Provider.

SPS Non-Functional Architecture Capacity SPSNFR-38 The SaaS Provider shall size the infrastructure architecture
and demonstrate through Load and Stress testing to
accommodate 800 power & 6000 concurrent ESS & MSS
users and peak events such as but not limited to Benefits
Enrollment.

SPS Non-Functional Architecture Capacity SPSNFR-39 The System shall provide the capability to accommodate a
2% anticipated growth of enrollees in the benefit plans for
the agencies without major system modifications and any
degradation in performance.

SPS Non-Functional Architecture Capacity SPSNFR-40 The System shall provide the capability to accommodate a
2% anticipated (maximum) growth of the State employees
without major system modifications and any degradation of
performance.

SPS Non-Functional Architecture Collaborative SPSNFR-41 The system shall provide the capability to be integrated with
Workspace State e-mail systems including but not limited to Microsoft
Outlook, Gmail

Page 5 of 34 May 22, 2013

Attachment F14a SPS SaaS HCM Solution
Non-Functional Requirements RFP # 060B3490012

Requirements Area To Be Completed by Vendor

Function Process Sub- Category Req. # Requirement Description Module(s)/ Response Comments
Code Process Sub-module(s)
Required
SPS Non-Functional Architecture Data Entry SPSNFR-42 The System shall provide the capability to allow complete
validation and editing of data at the point of entry (on-line or
batch).
SPS Non-Functional Architecture Data Entry SPSNFR-43 The System shall provide the capability to establish rules for
each field/transaction type which determine whether data is
Required, Optional or Not Allowed.
SPS Non-Functional Architecture Data Entry SPSNFR-44 The System shall provide the capability to prevent
transactions from posting until all "required" fields are
completed and validated.
SPS Non-Functional Architecture Data Entry SPSNFR-45 The System shall provide the capability to highlight errors on
the screen for immediate correction (online, immediate
validity checks).
SPS Non-Functional Architecture Data Entry SPSNFR-46 The System shall provide the capability to allow mass
changes or deletes by table-driven data in accordance with
system security requirements and controls.

SPS Non-Functional Architecture Data Entry SPSNFR-47 The System shall provide the capability to validate mass
data entered in batch form.
SPS Non-Functional Architecture Data Entry SPSNFR-48 The System shall provide the capability to establish
Validation rules for mass entries.
SPS Non-Functional Architecture Data Entry SPSNFR-49 The System shall provide the capability to hold the invalid
transactions from a mass upload in a suspend file or in error
tables.

SPS Non-Functional Architecture Data Entry SPSNFR-50 The System shall provide the capability to establish rules for
data precedence (e.g., accept this source file as opposed
another source file).
SPS Non-Functional Architecture Data Entry SPSNFR-51 The System shall provide the capability to store user
preferences for menu, screen, column & field and default
values
SPS Non-Functional Architecture Data Entry SPSNFR-52 The System shall provide the capability of data entry based
on security profiles in accordance with system requirements
and controls to include role based access controls.

Page 6 of 34 May 22, 2013

Attachment F14a SPS SaaS HCM Solution
Non-Functional Requirements RFP # 060B3490012

Requirements Area To Be Completed by Vendor

Function Process Sub- Category Req. # Requirement Description Module(s)/ Response Comments
Code Process Sub-module(s)
Required
SPS Non-Functional Architecture Data Entry SPSNFR-53 The System shall provide the capability to allow electronic
signatures for transactions.
SPS Non-Functional Architecture Data Entry SPSNFR-54 The System shall provide the capability to allow customized
form creation with auto-fill.
SPS Non-Functional Architecture Data Entry SPSNFR-55 The System shall provide the capability to allow colored
fonts in forms and on viewable screens.
SPS Non-Functional Architecture Data Entry SPSNFR-56 The System shall provide the capability to increase/
decrease font size as a personal user preference.
SPS Non-Functional Architecture Data Entry SPSNFR-57 The System shall provide the capability to archive and
retrieve application data, with controls for verifying
referential integrity of data.
SPS Non-Functional Architecture Data Entry SPSNFR-58 The System shall provide the capability to automatically
populate the data values based on security profiles in
accordance with system requirements and controls, relative
to user data entry.

SPS Non-Functional Architecture Data Entry SPSNFR-59 The System shall provide the capability to define data edits
by transaction type and input source.
SPS Non-Functional Architecture Data Entry SPSNFR-60 The System shall provide the capability to validate business
logic (edit checks) for all data input automatically.

SPS Non-Functional Architecture Databases SPSNFR-61 The System shall provide the capability of backward
compatibility for archived data.
SPS Non-Functional Architecture Databases SPSNFR-62 The System shall provide the capability of forward
compatibility for archived data.
SPS Non-Functional Architecture Development SPSNFR-63 The System shall provide the capability to allow for
separate, complete duplication of the software across the
production system, multiple development and test
landscapes.

SPS Non-Functional Architecture Development SPSNFR-64 The System shall provide the capability to be compatible
with common development platforms such as but not limited
to XML, Microsoft framework, .Net, java.

Page 7 of 34 May 22, 2013

Attachment F14a SPS SaaS HCM Solution
Non-Functional Requirements RFP # 060B3490012

Requirements Area To Be Completed by Vendor

Function Process Sub- Category Req. # Requirement Description Module(s)/ Response Comments
Code Process Sub-module(s)
Required
SPS Non-Functional Architecture Development SPSNFR-65 The System shall provide web services capability which is
compatible with W3C standards including but not limited to
SOAP, UDDI, WSDL, REST.
SPS Non-Functional Architecture Development SPSNFR-66 The System shall provide the capability to create new
objects such as tables, fields, screens.
SPS Non-Functional Architecture Development SPSNFR-67 The System shall provide the capability to modify/change
objects such tables, fields screens.
SPS Non-Functional Architecture Development SPSNFR-68 The System shall provide the capability to allow for
identification/reporting of user-defined objects.
SPS Non-Functional Architecture Development SPSNFR-69 The System shall provide the capability to include user-
defined objects in the upgrade path.
SPS Non-Functional Architecture Documentation SPSNFR-70 The SaaS Provider shall provide standards and procedures
for formats, templates, document file structure and archival.

SPS Non-Functional Architecture Documentation SPSNFR-71 The SaaS Provider shall provide all documentation, properly
organized for consistency and ease of use to support end
users effectively to:
- Use the features and functions of the
applications;
- Adapt application features and workflows to
match changing business
processes;
- Provide interfaces to and from other
applications;
- Customize vendor provided applications;
- Operate and monitor system and application
processes; and
- Recover from system, application, and data
problems.

SPS Non-Functional Architecture Documentation SPSNFR-72 The SaaS Provider shall provide documentation which is
easy to use, understand and access.

Page 8 of 34 May 22, 2013

Attachment F14a SPS SaaS HCM Solution
Non-Functional Requirements RFP # 060B3490012

Requirements Area To Be Completed by Vendor

Function Process Sub- Category Req. # Requirement Description Module(s)/ Response Comments
Code Process Sub-module(s)
Required
SPS Non-Functional Architecture Documentation SPSNFR-73 The SaaS Provider shall maintain a suitable online file
management process and a system that encourages the
accessibility and sharing of information, as well as protecting
against loss of data.

SPS Non-Functional Architecture Documentation SPSNFR-74 The SaaS Provider shall provide documentation for the
system upgrades, bug fixes, and maintenance patches.

SPS Non-Functional Architecture Documentation SPSNFR-75 The SaaS Provider shall provide ongoing maintenance of
documentation, to include:
- Ensuring documentation, once developed, is reviewed on
a regular basis (e.g., semi-annually), with evidence of review
and necessary updates documented and incorporated;
- Ensuring documentation is updated as part of the
change/configuration control process to reflect changes to
the system and its operational environment;
- Addressing all State requests for documentation
corrections or updates within a specified timeframe (e.g., the
timeframe specified in the contract or 15 calendar days,
which ever is less);
- Ensuring documentation is maintained in a format that is
editable by the State.

SPS Non-Functional Architecture Documentation SPSNFR-76 The SaaS Provider shall provide the documentation for all
products including but not limited to administration, system
development, end user reporting and troubleshooting. The
State must be granted the right to produce unlimited copies
of electronic or printed copies for internal use.

SPS Non-Functional Architecture Integration SPSNFR-77 The System shall provide the capability to be interoperable
with existing systems of the state where interfacing shall be
required with existing systems.

Page 9 of 34 May 22, 2013

Attachment F14a SPS SaaS HCM Solution
Non-Functional Requirements RFP # 060B3490012

Requirements Area To Be Completed by Vendor

Function Process Sub- Category Req. # Requirement Description Module(s)/ Response Comments
Code Process Sub-module(s)
Required
SPS Non-Functional Architecture Integration SPSNFR-78 The System shall provide the capability to use effective
dates for transactions, including support for future dated
entry and automatic processing of retroactive transactions.

SPS Non-Functional Architecture Integration SPSNFR-79 The System shall provide the capability to integrate
toolset(s) accommodating report design, development,
generation, and distribution.
SPS Non-Functional Architecture Integration SPSNFR-80 The System shall provide the capability to integrate
toolset(s) for Compliance management.
SPS Non-Functional Architecture Integration SPSNFR-81 The System shall provide integration toolset(s) for End-user
design.
SPS Non-Functional Architecture Integration SPSNFR-82 The System shall provide the capability to Re-start, recycle
rejected or errored adhoc/batch transactions.

SPS Non-Functional Architecture Integration SPSNFR-83 The System shall provide the capability to configure the
logon screen with "branding" for State of Maryland (logo,
color schemes, and user warnings & messages).

SPS Non-Functional Architecture Integration SPSNFR-84 The System shall provide the capability to attach files of
various formats(including but not limited to xml, pdf, excel,
word) to each transaction
SPS Non-Functional Architecture Integration SPSNFR-85 The System shall provide the capability to attach files at row
level of various formats(including but not limited to xml, pdf,
excel, word) as database content, reference to file server or
files in a document Management system

SPS Non-Functional Architecture Integration SPSNFR-86 The System shall provide scheduling capability for uploads
and downloads of data between integrated Office
productivity tools such as but not limited to Microsoft Office,
Google Office.

Page 10 of 34 May 22, 2013

Attachment F14a SPS SaaS HCM Solution
Non-Functional Requirements RFP # 060B3490012

Requirements Area To Be Completed by Vendor

Function Process Sub- Category Req. # Requirement Description Module(s)/ Response Comments
Code Process Sub-module(s)
Required
SPS Non-Functional Architecture Integration SPSNFR-87 The System shall provide the capability to transfer data
between systems utilizing XML formats. For example, public
safety applications need to follow the Global Justice XML or
HRXML.

SPS Non-Functional Architecture Integration SPSNFR-88 The System shall provide the capability to develop interfaces
for internal and external systems using technology such as
but not limited to WebServices (SOA), XML, SOAP, REST,
EDI.

SPS Non-Functional Architecture Job Scheduling SPSNFR-89 The System shall provide the capability to perform batch
processes within a window that shall not exceed 8 hrs
between 08:00 P.M. EST through 04:00 A.M. EST.

Page 11 of 34 May 22, 2013

Attachment F14a SPS SaaS HCM Solution
Non-Functional Requirements RFP # 060B3490012

Requirements Area To Be Completed by Vendor

Function Process Sub- Category Req. # Requirement Description Module(s)/ Response Comments
Code Process Sub-module(s)
Required
SPS Non-Functional Architecture Job Scheduling SPSNFR-90 The System shall provide the capability for the following
batch processing and interface controls:
- Reconcilling between the source and target application to
ensure that the data transfer is complete and accurate;
- Ensuring errors during interface processing are identified
by balancing processes and promptly investigated, corrected
and resubmitted for processing;
- Establishing a positive acknowledgement scheme to
ensure that files sent from a source system are received by
the target system (i.e., a "handshake" between the systems
so that files are not skipped or lost);
- Ensuring files generated by an application interface (both
source and target) are properly secured from unauthorized
access and/or modifications;
- Establishment and periodic review of an interface
processing log that captures errors and exceptions;
- Use of error and correction facilities to track and correct
errors in interface data;
- Establishing and using a mechanism (e.g., email
message) to notify users when data is rejected. These
messages should repeat daily until they are corrected;
- Ensuring interfaces files are automatically archived or
deleted from the production
environment after processing to prevent multiple processing
iterations of the same data.

Page 12 of 34 May 22, 2013

Attachment F14a SPS SaaS HCM Solution
Non-Functional Requirements RFP # 060B3490012

Requirements Area To Be Completed by Vendor

Function Process Sub- Category Req. # Requirement Description Module(s)/ Response Comments
Code Process Sub-module(s)
Required
SPS Non-Functional Architecture Job Scheduling SPSNFR-91 The System shall provide job scheduling tools for reports,
interfaces, batch programs etc.. or integration with a third-
party tool that allow users to sequence multiple jobs based
on configurable rules such as but not limited to time of day,
day of week, or calendar date and/or the successful
completion of predecessor.

SPS Non-Functional Architecture Job Scheduling SPSNFR-92 The System shall provide the capability to notify failed jobs
to the business user, administrator and all owners of the
processess until it' s corrected/resolved.

SPS Non-Functional Architecture Job Scheduling SPSNFR-93 The System shall provide the ability for a user to schedule
the automatic generation and distribution of reports based
on a user-defined frequency (e.g., daily, weekly, monthly).

SPS Non-Functional Architecture Job Scheduling SPSNFR-94 The System shall provide the capability for administrators,
report developers and users to notify, report and re-schedule
failed pre-defined tasks at desired times and dates.

SPS Non-Functional Architecture Metadata SPSNFR-95 The SaaS Provider shall provide a common, centralized
metadata repository. The metadata repository should
maintain information about available objects,elements,
formulas and filters for derived attributes, report templates
and job execution schedules.

SPS Non-Functional Architecture Metadata SPSNFR-96 The System shall provide the capability to have a common
metadata model that can be utilized and leveraged by all
components in a manner that allows developers and
administrators to make changes in one centralized location.
Changes should be automatically propagated and be
available for use by all users.

Page 13 of 34 May 22, 2013

Attachment F14a SPS SaaS HCM Solution
Non-Functional Requirements RFP # 060B3490012

Requirements Area To Be Completed by Vendor

Function Process Sub- Category Req. # Requirement Description Module(s)/ Response Comments
Code Process Sub-module(s)
Required
SPS Non-Functional Architecture Metadata SPSNFR-97 The System shall provide metadata reporting capabilities,
e.g. canned metadata browsing such as report definitions,
functions, parameters or dependency analysis.

SPS Non-Functional Architecture Metadata SPSNFR-98 The System shall provide metadata impact analysis
capabilities.
SPS Non-Functional Architecture Monitoring SPSNFR-99 The SaaS Provider shall provide 24/7/365 monitoring for the
overall solution including all tiers of the infrastructure.

SPS Non-Functional Architecture Monitoring SPSNFR-100 The System shall have the ability to proactively monitor
application and supporting infrastructure availability through
monitoring 'dashboards' and provide performance monitoring
alerts that are configurable and allow for user notification
using multiple communication methods.

SPS Non-Functional Architecture Monitoring SPSNFR-101 The System shall provide the capability to monitor/ manage
all Application components from a main, web based
'console'.
SPS Non-Functional Architecture Monitoring SPSNFR-102 The System shall have the capability to monitor, manage,
and track down all application transactions.
SPS Non-Functional Architecture Performance SPSNFR-103 The System shall provide an average of a two (2) second
screen/transaction response time during peak times
(measured utilizing a controlled environment within the
State’s internal network (Intranet) and the system software
application.

SPS Non-Functional Architecture Performance SPSNFR-104 The System shall not diminish the average two (2) seconds
response time during peak usage periods upon execution of
saved and/or adhoc queries/reports.

SPS Non-Functional Architecture Performance SPSNFR-105 The System shall provide the ability to administer/control the
priority of processes based on configurable criteria.

Page 14 of 34 May 22, 2013

Attachment F14a SPS SaaS HCM Solution
Non-Functional Requirements RFP # 060B3490012

Requirements Area To Be Completed by Vendor

Function Process Sub- Category Req. # Requirement Description Module(s)/ Response Comments
Code Process Sub-module(s)
Required
SPS Non-Functional Architecture Performance SPSNFR-106 The System shall provide the capability for the system
administrator to track performance and usage.
This should include:
- The ability to track and log which users or user groups
have the highest usage and what they are accessing;
- The ability to provide statistics on system performance;
- The ability to track and log, which reports or database
elements are being, used the most.

SPS Non-Functional Architecture Platform SPSNFR-107 The SaaS Provider shall support all the environments
without exception such as but not limited to Production,
Development, Test, and Training.
SPS Non-Functional Architecture Platform SPSNFR-108 The System shall provide the capability to retrieve data from
the following data sources: SAS, IBM DB2, Microsoft SQL
Server, Oracle, text files (character delimited and fixed
length fields), XML files, Microsoft Excel files, and any
ODBC or JDBC accessible data sources.

SPS Non-Functional Architecture Platform SPSNFR-109 The System shall provide the capability to access and query
all data contained in the system.
SPS Non-Functional Architecture Platform SPSNFR-110 The System shall allow output (queries, reports, charts,
graphs, and maps) to be produced in any of the following
formats: HTML, PDF, Microsoft Excel, CSV, XML, fixed
width and delimited text files, and the solution's native output
format.

Page 15 of 34 May 22, 2013

Attachment F14a SPS SaaS HCM Solution
Non-Functional Requirements RFP # 060B3490012

Requirements Area To Be Completed by Vendor

Function Process Sub- Category Req. # Requirement Description Module(s)/ Response Comments
Code Process Sub-module(s)
Required
SPS Non-Functional Architecture Platform SPSNFR-111 The System shall provide all end user functionality through a
zero footprint Web interface. The end users should not need
any software beyond a web browser. The solution must not
require the use of any Bidder specific/proprietary Web
browser capabilities or software, with the exception of Adobe
Flash and Adobe Acrobat Reader. The solution should not
require the use of ActiveX controls.

SPS Non-Functional Architecture Platform SPSNFR-112 The System shall provide the capability for users to
customize the user interface to their individual settings per
their security level.
SPS Non-Functional Architecture Post-Implementation SPSNFR-113 The SaaS Provider shall provide production support
including but not limited to day-to-day functional and
technical production support for the State as necessary.

SPS Non-Functional Architecture Post-Implementation SPSNFR-114 The SaaS Provider shall resolve any operational issues that
might affect the 99.5% operational level requirement.

SPS Non-Functional Architecture Regulatory SPSNFR-115 The System shall be in compliance with the State of
Maryland IT Non-Visual Access
(MD IT NVA) standards. Link :
http://doit.maryland.gov/policies/Pages/nva.aspx

SPS Non-Functional Architecture Reporting SPSNFR-116 The System shall provide the capability for report
repository / library.
SPS Non-Functional Architecture Reporting SPSNFR-117 The System shall provide the capability to create reports
with drill down capabilities.
SPS Non-Functional Architecture Reporting SPSNFR-118 The System shall provide the capability to create & generate
ad-hoc reports by end users.
SPS Non-Functional Architecture Reporting SPSNFR-119 The System shall provide the capability to save ad-hoc
report/query definitions.
SPS Non-Functional Architecture Reporting SPSNFR-120 The System shall provide the capability to modify report
queries on-line by end-users, with appropriate security.

Page 16 of 34 May 22, 2013

Attachment F14a SPS SaaS HCM Solution
Non-Functional Requirements RFP # 060B3490012

Requirements Area To Be Completed by Vendor

Function Process Sub- Category Req. # Requirement Description Module(s)/ Response Comments
Code Process Sub-module(s)
Required
SPS Non-Functional Architecture Reporting SPSNFR-121 The System shall provide the capability to save ad-hoc
report results by end-users.
SPS Non-Functional Architecture Reporting SPSNFR-122 The System shall provide the capability to export data to any
spreadsheet application for manipulation and/or reporting of
data by end-users.
SPS Non-Functional Architecture Reporting SPSNFR-123 The System shall provide the capability to report on any
user-defined parameter values or ranges.
SPS Non-Functional Architecture Reporting SPSNFR-124 The System shall provide the capability to create reports
which can include end-user defined headings and borders.

SPS Non-Functional Architecture Reporting SPSNFR-125 The System shall provide the capability to filter reports
based upon user-defined criteria.
SPS Non-Functional Architecture Reporting SPSNFR-126 The System shall provide the capability to create and print
reports on special forms.
SPS Non-Functional Architecture Reporting SPSNFR-127 The System shall provide the capability to create on-line,
real-time reports and query with the ability to reference a
data dictionary.
SPS Non-Functional Architecture Reporting SPSNFR-128 The System shall provide the capability to create reports that
can suppress or print information based on the defined
access permissions for the user.
SPS Non-Functional Architecture Reporting SPSNFR-129 The System shall provide the capability to print reports to
any printer such as but not limited to laser jets, networked
copiers.
SPS Non-Functional Architecture Reporting SPSNFR-130 The System shall provide end-user definition of
reporting/query criteria's such as but not limited to wildcards,
text searches.

SPS Non-Functional Architecture Reporting SPSNFR-131 The System shall provide the capability to distribute reports
such as but not limited to via links, emails.
SPS Non-Functional Architecture Reporting SPSNFR-132 The System shall provide the capability to define limits on
the time a report or query takes to execute and the number
of records to be retrieved.

Page 17 of 34 May 22, 2013

Attachment F14a SPS SaaS HCM Solution
Non-Functional Requirements RFP # 060B3490012

Requirements Area To Be Completed by Vendor

Function Process Sub- Category Req. # Requirement Description Module(s)/ Response Comments
Code Process Sub-module(s)
Required
SPS Non-Functional Architecture Reporting SPSNFR-133 The System shall provide the capability to define limits for
other types of query functions such as but not limited to
number of table joins.
SPS Non-Functional Architecture Reporting SPSNFR-134 The System shall provide the capability to generate, publish,
convert and distribute reports in various formats such as but
not limited to Screen, Printer, XML, HTML, RTF, PDF, word,
excel.

SPS Non-Functional Architecture Reporting SPSNFR-135 The System shall provide standard ad hoc reporting
templates and allow users to create new reporting
templates.
SPS Non-Functional Architecture Reporting SPSNFR-136 The system shall run reports on a predefined automated
schedule and provide report routing.
SPS Non-Functional Architecture Reporting SPSNFR-137 The system shall have the ability to access/extract data for
analysis.
SPS Non-Functional Architecture Reporting SPSNFR-138 The System shall provide the capability to organize reports
and queries with description and tags in customized
directories and folder.
SPS Non-Functional Architecture Reporting SPSNFR-139 The System shall provide Microsoft Office integration:
- Ability to render reports in Excel while maintaining the
report format and enabling Excel users to easily refresh the
data;
- Ability to deploy functionality, such as parameterized
reporting, dashboards, scorecards and OLAP, in an Excel
client.

SPS Non-Functional Architecture Reporting SPSNFR-140 The System shall provide a Graphical User Interface that
allows end users to create new (and modify existing) queries
through a drag and drop process. The user interface must
display a list of defined objects that can be included in the
query as result elements and filters. End users must not be
required to enter SQL syntax to create queries.

Page 18 of 34 May 22, 2013

Attachment F14a SPS SaaS HCM Solution
Non-Functional Requirements RFP # 060B3490012

Requirements Area To Be Completed by Vendor

Function Process Sub- Category Req. # Requirement Description Module(s)/ Response Comments
Code Process Sub-module(s)
Required
SPS Non-Functional Architecture Reporting SPSNFR-141 The System shall provide the capability for users to
seamlessly turn any ad-hoc queries, they created, into
reports.
SPS Non-Functional Architecture Security SPSNFR-142 The SaaS Provider shall deploy and routinely update
appropriate anti-virus, anti-spyware and file extension
blocking solutions at the gateway entry points for desktop
and server systems.

SPS Non-Functional Architecture Security SPSNFR-143 The SaaS Provider shall develop firewall or other boundary
protection mechanisms that have the ability to (1) evaluate
source and destination network addresses, and (2) compare
the request (including destination ports) to predefined
access control lists for filtering purposes.

SPS Non-Functional Architecture Security SPSNFR-144 The SaaS Provider shall deploy Intrusion Detection System
and Intrusion Prevention System (IDS/IPS) solutions at
appropriate network location(s) and monitor to detect when
the agency is under attack so to trigger the deployment of
detection and defense strategies.

SPS Non-Functional Architecture Security SPSNFR-145 The SaaS Provider shall secure certain internal data and
services (Personnel Services, for instance) from other data
and system networks.
SPS Non-Functional Architecture Security SPSNFR-146 All confidential or sensitive data on any infrastructure
components that require internet access shall be placed
behind a de-militarized zone (DMZ).
SPS Non-Functional Architecture Security SPSNFR-147 The System shall establish procedures to protect
documents, computer media, information/data, and
documentation from unauthorized disclosure, modification,
removal, and destruction. The System shall establish
measures to properly dispose of discarded or unused media.

Page 19 of 34 May 22, 2013

Attachment F14a SPS SaaS HCM Solution
Non-Functional Requirements RFP # 060B3490012

Requirements Area To Be Completed by Vendor

Function Process Sub- Category Req. # Requirement Description Module(s)/ Response Comments
Code Process Sub-module(s)
Required
SPS Non-Functional Architecture Security SPSNFR-148 The SaaS Provider shall establish procedures and standards
to protect information and physical media containing
information in transit, including facsimile machine usuage,
exchange agreements between the agency and external
parties, transportation of physical media, and monitoring
such as but not limited to audit logging, monitoring system
use.

SPS Non-Functional Architecture Security SPSNFR-149 The SaaS Provider shall implement security level monitoring
including intrusion detection, penetration testing, and
violation analysis.
SPS Non-Functional Architecture Security SPSNFR-150 The System shall adhere to access control and
authentication requirements set forth in the Information
Security Policy (Link:
http://doit.maryland.gov/support/Documents/security_guideli
nes/DoITSecurityPolicy2013.pdf).
Also, the proposed SaaS HCM Product shall be SOC 2 Type
II compliant.

SPS Non-Functional Architecture Security SPSNFR-151 The System shall use FIPS 140-2 approved encryption
technologies (Link:
http://csrc.nist.gov/publications/fips/fips140-2/fips1402.pdf).

SPS Non-Functional Architecture Security SPSNFR-152 The System shall provide the capability to restrict all
reporting and query functions with the same security profiles
and related data access limitations of the core application.

SPS Non-Functional Architecture Security SPSNFR-153 The System shall provide the capability to access all
Application components with one universal sign-in or log-in.

SPS Non-Functional Architecture Security SPSNFR-154 The System shall provide the capability to have strong and
documented boundaries between extranet, Internet and
internal system.

Page 20 of 34 May 22, 2013

Attachment F14a SPS SaaS HCM Solution
Non-Functional Requirements RFP # 060B3490012

Requirements Area To Be Completed by Vendor

Function Process Sub- Category Req. # Requirement Description Module(s)/ Response Comments
Code Process Sub-module(s)
Required
SPS Non-Functional Architecture Security SPSNFR-155 The System shall provide the capability to administrators to
restrict data access by Role, group or user based on
security role definition.
SPS Non-Functional Architecture Security SPSNFR-156 The System shall provide the capability to administrators to
restrict data access by user type such as but not limited to
employee, contractor, and retiree.

SPS Non-Functional Architecture Security SPSNFR-157 The System shall provide the capability to administrator to
restrict data access by IP address.
SPS Non-Functional Architecture Security SPSNFR-158 The System shall provide the capability to administrator to
restrict data access by Screen/page field and menu and
transaction type.
SPS Non-Functional Architecture Security SPSNFR-159 The System shall provide the capability to administrator to
restrict data access by Report.
SPS Non-Functional Architecture Security SPSNFR-160 The System shall provide the capability to administrator to
restrict data access by Database table.

SPS Non-Functional Architecture Security SPSNFR-161 The System shall provide the capability to administrator to
restrict data access by Job function / position.

SPS Non-Functional Architecture Security SPSNFR-162 The System shall provide the capability to administrator to
define security profiles that restrict user ability to log on.

SPS Non-Functional Architecture Security SPSNFR-163 The System shall provide the capability to administrator to
define security profiles that restrict user ability to
add/change/delete/update and view data.

SPS Non-Functional Architecture Security SPSNFR-164 The System shall provide the capability to allow
administrators to view or obtain security reports showing
Authorized/Unauthorized system use

Page 21 of 34 May 22, 2013

Attachment F14a SPS SaaS HCM Solution
Non-Functional Requirements RFP # 060B3490012

Requirements Area To Be Completed by Vendor

Function Process Sub- Category Req. # Requirement Description Module(s)/ Response Comments
Code Process Sub-module(s)
Required
SPS Non-Functional Architecture Security SPSNFR-165 The System shall provide the capability to generate warning
message to notify administrator if multiple security profiles
applied to a single user are conflicting.

SPS Non-Functional Architecture Security SPSNFR-166 The System shall provide the capability to effective date all
addition, deletion, updates and modifications to the security
settings and parameters.
SPS Architecture Security The System shall comply with security certification and
acredition guidelines (Link:
http://doit.maryland.gov/support/Documents/security_guideli
nes/CA_Guidelines.pdf).

SPS Non-Functional Architecture Security SPSNFR-168 The System shall provide the capability to ensure transmittal
of passwords using secure protocols/algorithms.

SPS Non-Functional Architecture Security SPSNFR-169 The System shall provide the capability to define User
Access Groups based on job responsibilities to ensure
separation of duties.
SPS Non-Functional Architecture Security SPSNFR-170 The System shall provide the capability to maintain the
password and security related configuration files in an
encrypted state.
SPS Non-Functional Architecture Security SPSNFR-171 The System shall provide the capability to administer
security in a de-centralized manner.
SPS Non-Functional Architecture Security SPSNFR-172 The System shall provide the capability to isolate sessions
such that a failure in one session does not impact other
sessions.
SPS Non-Functional Architecture Security SPSNFR-173 The System shall provide the capability to automate the
creation and deactivation of user accounts relative to
employment status.
SPS Non-Functional Architecture Security SPSNFR-174 The System shall provide the capability to automatically
deactivate a user logon id after an administrator-defined
period of inactivity.

Page 22 of 34 May 22, 2013

Attachment F14a SPS SaaS HCM Solution
Non-Functional Requirements RFP # 060B3490012

Requirements Area To Be Completed by Vendor

Function Process Sub- Category Req. # Requirement Description Module(s)/ Response Comments
Code Process Sub-module(s)
Required
SPS Non-Functional Architecture Security SPSNFR-175 The System shall provide the capability for administrator to
activate, disable, delete, restrict, allow only certain data sets
and revoke user accounts or passwords.

SPS Non-Functional Architecture Security SPSNFR-176 The System shall provide the capability for administrator to
define required password characteristics.

SPS Non-Functional Architecture Security SPSNFR-177 The System shall provide the capability to have security to
read, write, view and access data based on organization
hierarchy level such as but not limited to Agency,
department, Division, Section, Unit, Union.

SPS Non-Functional Architecture Security SPSNFR-178 The System shall provide the capability for administrator to
restrict data access for each security profile by application
module.
SPS Non-Functional Architecture Security SPSNFR-179 The System shall provide the capability for administrator to
restrict data access for each security profile by application
screen or page.
SPS Non-Functional Architecture Security SPSNFR-180 The System shall provide the capability to allow
administrators to view or obtain security reports based on
security profiles.
SPS Non-Functional Architecture Security SPSNFR-181 The System shall support hierarchical, role-based security
for view and edit access for all transactions, inquiries, and
reports.
SPS Non-Functional Architecture Security SPSNFR-182 The System shall support the control of role-based security
based on changes within the Position Management function,
such as an employees change of position, agency or of
employment with the state.

SPS Non-Functional Architecture Security SPSNFR-183 The System shall control create, display, and change access
to the transactions within The System, and allow for user-
defined assignment of these privileges on a transaction
specific basis.

SPS Non-Functional Architecture Security SPSNFR-184 The System shall provide the ability to secure transactions
and attachments as ‘read only.’

Page 23 of 34 May 22, 2013

Attachment F14a SPS SaaS HCM Solution
Non-Functional Requirements RFP # 060B3490012

Requirements Area To Be Completed by Vendor

Function Process Sub- Category Req. # Requirement Description Module(s)/ Response Comments
Code Process Sub-module(s)
Required
SPS Non-Functional Architecture Security SPSNFR-185 The System shall provide security on update/viewing of data
fields by user, department, direct report, organizational level,
etc.
SPS Non-Functional Architecture Security SPSNFR-186 The System shall provide the capability for the creation of
security rules that:
- Control access by user group
- Control access by individual user
- Control access by database table or logical entity
- Control access by database field or logical attribute
- Control access by row (row-level security)

SPS Non-Functional Architecture Security SPSNFR-187 The System shall provide a common security model that is
utilized by all components. The solution must enforce users
and role/function security rules regardless of the interface
that is used. The solution must enforce authentication and
authorization rules at all times and prevent bypassing of
security via direct link/URL calls.

SPS Non-Functional Architecture Security SPSNFR-188 The System shall provide the capability to automatically
tailor the content presented to every user based on their
security profile.
SPS Non-Functional Architecture Service Management SPSNFR-189 The SaaS Provider shall maintain the system in terms of
code change easability, upgrade applications, patches and
migrations.
SPS Non-Functional Architecture Service Management SPSNFR-190 The System shall provide the capability to utilize automated
scripts/tools for Data Masking for production size non-
production environments. This includes data scrambling and
data anonymization.

SPS Non-Functional Architecture Service Management SPSNFR-191 The System shall provide the capability to use automated
scripts/tool for Database Subsetting to create cut-down
version of production databases for use in development or
testing.

Page 24 of 34 May 22, 2013

Attachment F14a SPS SaaS HCM Solution
Non-Functional Requirements RFP # 060B3490012

Requirements Area To Be Completed by Vendor

Function Process Sub- Category Req. # Requirement Description Module(s)/ Response Comments
Code Process Sub-module(s)
Required
SPS Non-Functional Architecture Service Management SPSNFR-192 The system shall provide utilities/tools to identify and
migrate configurations across environments/releases.

SPS Non-Functional Architecture Service Management SPSNFR-193 The SaaS Provider shall support clearly segregated
development/test/QA/production environments as well as
provide robust procedures to migrate objects across
environments.

SPS Non-Functional Architecture Usability SPSNFR-194 The System shall provide a consistent, unified and intuitive
user experience across all interfaces.
SPS Non-Functional Architecture Usability SPSNFR-195 The System shall provide the capability to integrate error
messages with on-line help function.
SPS Non-Functional Architecture Usability SPSNFR-196 The System shall provide the capability to associate Help
functions with functional transaction at menu, screen, field
level.

SPS Non-Functional Architecture Usability SPSNFR-197 The System shall allow users to send system error reports
(automatically or Administrator defined) to application
administrator.
SPS Non-Functional Architecture Usability SPSNFR-198 The System shall provide a consistent user interface across
all components, including Consistent function keys and
Consistent Navigation patterns.
SPS Non-Functional Architecture Usability SPSNFR-199 The System shall allow users to access all user
documentation such as but not limited to help manuals
online and organized by:
- Functional area
- Transaction

SPS Non-Functional Architecture Usability SPSNFR-200 The System shall include help menus for system
functionality for each transaction and window, with both
standard and customizable help text.

Page 25 of 34 May 22, 2013

Attachment F14a SPS SaaS HCM Solution
Non-Functional Requirements RFP # 060B3490012

Requirements Area To Be Completed by Vendor

Function Process Sub- Category Req. # Requirement Description Module(s)/ Response Comments
Code Process Sub-module(s)
Required
SPS Non-Functional Architecture Usability SPSNFR-201 The System shall provide advanced search functionality,
with the ability to search among and between predefined
groups of transactions and transaction types. For example:
- The ability to search all transactions related
to a single employee, using
key words
- The ability to retrieve all transactions related
to a particular vendor

SPS Non-Functional Architecture Usability SPSNFR-202 The System shall provide Online Help Facility with the
following capabilities:
- Window level help
- Field level help
- Error message help
- Context sensitive help
- Windows hypertext help
- Indexed help
- Definable coaches, wizards, or tutors

SPS Non-Functional Architecture Usability SPSNFR-203 The System shall provide error message capabilities as
follows:
- Minimum 30 characters (providing extended
error message text upon
request)
- Indicates which field is in error by highlighting
field
- Provide information on all applicable errors
after edits are performed
- Provide user customizable error messages
text stored in system tables

Page 26 of 34 May 22, 2013

Attachment F14a SPS SaaS HCM Solution
Non-Functional Requirements RFP # 060B3490012

Requirements Area To Be Completed by Vendor

Function Process Sub- Category Req. # Requirement Description Module(s)/ Response Comments
Code Process Sub-module(s)
Required
SPS Non-Functional Architecture Usability SPSNFR-204 The System shall provide features to reduce errors and
keystrokes, including but not limited to:
- Ability to derive certain transaction type
codes by user default
- Single choice user default values for
individual transactions selectable
from the menu (defined at a user profile level
based on authority level
and predominant transaction type)
- Inferences based on user ID
- Inferences based on entered data

SPS Non-Functional Architecture Usability SPSNFR-205 The System shall allow any inquiry available online to be
printed.
SPS Non-Functional Architecture Usability SPSNFR-206 The system shall allow search capability for attached
documents and the ability to associate key words with each
document.
SPS Non-Functional Architecture Usability SPSNFR-207 The system shall provide online access to policy documents
and other reference materials.
SPS Non-Functional Architecture Workflow SPSNFR-208 The System shall provide the capability to use workflow to
electronically route documents associated with transactions.

SPS Non-Functional Architecture Workflow SPSNFR-209 The System shall provide the capability for approval process
initiators to track the approval process.
SPS Non-Functional Architecture Workflow SPSNFR-210 The System shall provide the capability for Workflow rules to
be established based on User-defined criteria.

SPS Non-Functional Architecture Workflow SPSNFR-211 The System shall provide the capability to re-route workflow
assignments to different authorized approvers based upon
availability.
SPS Non-Functional Architecture Workflow SPSNFR-212 The System shall provide the capability to integrate workflow
alerts with State email System such as but not limited to
Microsoft Exchange 2007, Gmail Cloud.

Page 27 of 34 May 22, 2013

Attachment F14a SPS SaaS HCM Solution
Non-Functional Requirements RFP # 060B3490012

Requirements Area To Be Completed by Vendor

Function Process Sub- Category Req. # Requirement Description Module(s)/ Response Comments
Code Process Sub-module(s)
Required
SPS Non-Functional Architecture Workflow SPSNFR-213 The System shall provide the capability for Workflow rules to
be established based on Events, User, Role, Percentage
and numerical thresholds.
SPS Non-Functional Architecture Workflow SPSNFR-214 The System shall provide the capability to allow delegation
of Workflow approvals.
SPS Non-Functional Architecture Workflow SPSNFR-215 The System shall provide the capability to allow workflow
escalation and denial based on system and user-defined
rules.
SPS Non-Functional Architecture Workflow SPSNFR-216 The System shall provide the capability for configurable
user-defined rules-based automated notifications, including
but not limited to:
- System alerts (e.g., pop-up windows)
- Automatically generated e-mails with variable
narrative or appropriate
web links
- Automatically generated faxes
- Automatically generated, print-ready,
formattable letters (both printed
and e-mail attachable files)

SPS Non-Functional Architecture Workflow SPSNFR-217 The System shall allow rules-based automatic notifications
to user-defined persons based on events including, but not
limited to:
• Pending approvals on a system transaction;
• Aging of open personnel actions;
• Employee benefits, address, application, and time sheet
changes;
• When the balance of position budget reaches a pre-defined
threshold (e.g., $500 or
5% of total allowance);
• Contractual employee term expirations.

Page 28 of 34 May 22, 2013

Attachment F14a SPS SaaS HCM Solution
Non-Functional Requirements RFP # 060B3490012

Requirements Area To Be Completed by Vendor

Function Process Sub- Category Req. # Requirement Description Module(s)/ Response Comments
Code Process Sub-module(s)
Required
SPS Non-Functional Architecture Workflow SPSNFR-218 The System shall allow for specifying preferred and/or
multiple delivery options for all notifications (user, vendor,
employee, applicant) including but not limited to:
• Letter (printed for mailing)
• E-mail
• Web posting
• Electronic Data Interchange (EDI)
• Fax
• Extensible Markup Language (XML)
• Telephone (e.g., Interactive Voice Recognition (IVR))
• E-mail attachment (spreadsheet or word processing
document)

SPS Non-Functional Architecture Workflow SPSNFR-219 The System shall allow either sequential or concurrent
approval processing by transactions, based on predefined
configurations.
SPS Non-Functional Architecture Workflow SPSNFR-220 The System shall allow for the delegation of approvals (or
proxy approvals) for limited or unlimited time periods (e.g.,
vacations).

Page 29 of 34 May 22, 2013

Attachment F14a SPS SaaS HCM Solution
Non-Functional Requirements RFP # 060B3490012

Requirements Area To Be Completed by Vendor

Function Process Sub- Category Req. # Requirement Description Module(s)/ Response Comments
Code Process Sub-module(s)
Required
SPS Non-Functional Architecture Workflow SPSNFR-221 The System shall provide unlimited levels of approval for
each transaction, including but not limited to:
- Human resource transactions (e.g.,
personnel actions)

SPS Non-Functional Architecture Workflow SPSNFR-222 The System shall provide capability for electronic
routing/workflow of documents that shall be editable at each
stage and during approval.
SPS Non-Functional Architecture Workflow SPSNFR-223 The System shall allow users to specify whether or not to
provide e-mail notifications of pending approvals.

SPS Non-Functional Architecture Workflow SPSNFR-224 The System shall provide control and monitoring
functionality for workflow.
SPS Non-Functional Architecture Workflow SPSNFR-225 The System shall provide auto-escalation rules for a
workflow process.
SPS Non-Functional Architecture Workflow SPSNFR-226 The System shall allow the user to establish case-by-case
escalation rules for a workflow process.

Page 30 of 34 May 22, 2013

Attachment F14a SPS SaaS HCM Solution
Non-Functional Requirements RFP # 060B3490012

Requirements Area To Be Completed by Vendor

Function Process Sub- Category Req. # Requirement Description Module(s)/ Response Comments
Code Process Sub-module(s)
Required
SPS Non-Functional Architecture Workflow SPSNFR-227 The System shall provide the capability to list prior approvals
and modifications to a transaction and the list shall be
available to all users in the workflow routing for each
transaction and transaction type.

SPS Non-Functional Architecture Workflow SPSNFR-228 The System shall provide the capability to notify by e-mail,
as necessary, of pending work such as review and approval
for all the transaction that are routed via electronic workflow.

SPS Non-Functional Architecture Workflow SPSNFR-229 The System shall provide a reporting and/or inquiry tool that
can report on the status of the transaction moving through
workflow.

SPS Non-Functional Architecture Workflow SPSNFR-230 The system shall provide the capability to customize and
configure workflow for the routing and approval of actions
based on transaction type.
SPS Non-Functional Business Reporting SPSNFR-231 The System shall provide a Graphical User Interface for
Intelligence users to specify report layout and formatting options. End
Reporting users must be able to add, move, and delete columns,
specify row sorts, specify row groupings, and change other
layout options via a drag-and-drop, or a pick-and-click
interface. In addition end users must be able to add graphs
to reports as well as add free form text to annotate both
graphs and reports.

SPS Non-Functional Business Reporting SPSNFR-232 The System shall provide the capability for power users to
Intelligence use SQL directly instead of using SQL generated based
Reporting upon the application's metadata. It should be possible to
enable or disable this feature on a per user basis.

SPS Non-Functional Business Reporting SPSNFR-233 The System shall provide the capability to drill up or down a
Intelligence defined hierarchy of data via the Web based GUI.
Reporting

Page 31 of 34 May 22, 2013

Attachment F14a SPS SaaS HCM Solution
Non-Functional Requirements RFP # 060B3490012

Requirements Area To Be Completed by Vendor

Function Process Sub- Category Req. # Requirement Description Module(s)/ Response Comments
Code Process Sub-module(s)
Required
SPS Non-Functional Business Reporting SPSNFR-234 The System shall provide the capability that enables users to
Intelligence edit and modify existing queries or reports and then save
Reporting them as their own.
SPS Non-Functional Business Reporting SPSNFR-235 The System shall provide the capability to display data in a
Intelligence cross-tabular report format. The solution must allow users to
Reporting change the fields used to produce the columns and rows of
the cross tabular report via GUI functionality. The solution
must not require that a database query be re-executed to
produce a new cross tabulation of data previously retrieved
for a report.

SPS Non-Functional Business Reporting SPSNFR-236 The System shall allow a user to undo changes in cross
Intelligence tabulation layout.
Reporting
SPS Non-Functional Business Reporting SPSNFR-237 The System shall allow users to publish a finished query or
Intelligence report so that's available to other users.
Reporting
SPS Non-Functional Business Reporting SPSNFR-238 The System shall allow users to save a finished query or
Intelligence report complete with data such that it is static and need not
Reporting be rerun.
SPS Non-Functional Business Reporting SPSNFR-239 The System shall provide the capability for users and
Intelligence developers to easily create, save and publish a new report
Reporting format (also called template or layout).
SPS Non-Functional Business Reporting SPSNFR-240 The System shall provide the capability of content search
Intelligence globally and locally such as but not limited to report, subject
Reporting area, table, column, keyword, field.
SPS Non-Functional Business Reporting SPSNFR-241 The System shall provide the capability to collaborate with
Intelligence workflow.
Reporting
SPS Non-Functional Business Reporting SPSNFR-242 The System shall provide the capability for data visualization
Intelligence such as but not limited to pie charts, line graphs.
Reporting

Page 32 of 34 May 22, 2013

Attachment F14a SPS SaaS HCM Solution
Non-Functional Requirements RFP # 060B3490012

Requirements Area To Be Completed by Vendor

Function Process Sub- Category Req. # Requirement Description Module(s)/ Response Comments
Code Process Sub-module(s)
Required
SPS Non-Functional Business Reporting SPSNFR-243 The System shall provide the capability of OLAP by which
Intelligence end users can analyze data with extremely fast query and
Reporting calculation performance, enabling a style of analysis known
as "slicing and dicing". This capability will span a variety of
storage architectures such as relational, multidimensional
and in-memory.

SPS Non-Functional Business Reporting SPSNFR-244 The system shall have the capability to build
Intelligence Dashbords,KPI's and Reports per State's HR Business
Reporting Analytics (Attachment 13a)
SPS Non-Functional Business Reporting SPSNFR-245 The System shall provide the capability to have embedded
Intelligence BI analytics within the OLTP system
Reporting
SPS Non-Functional Self Service Collaborative SPSNFR-246 The Self Service shall allow the users to create and track
Workspace action items.
SPS Non-Functional Self Service Content Management SPSNFR-247 The Self Service shall have the content personalized /
authorized for each user based on user's profile and the
assigned role.
SPS Non-Functional Self Service Content Management SPSNFR-248 The Self Service shall provide capability to bookmark
frequently needed and accessed contentby users.
SPS Non-Functional Self Service Content Management SPSNFR-249 The Self Service shall provide the orgnizational hierarchy
chart.
SPS Non-Functional Self Service Security SPSNFR-250 The Self Service shall provide access to Internal and
External Application Links.

Page 33 of 34 May 22, 2013