Docstoc

Addendum _2 Appendix B Functional Requirements

Document Sample
Addendum _2 Appendix B Functional Requirements Powered By Docstoc
					SALT LAKE COUNTY                                                                  INSTRUCTIONS                                               RATING LEGEND
Functional Requirements Matrix                                                                                     SUP   Supported as delivered "out-of-the-box"
                                                                     Complete the worksheet by placing an X in           Supported via modifications (screen configurations, reports, GUI
                                                                        the most appropriate column for each       MOD
                                                                                                                         tailoring, etc)
                                                                       criterion. The X's should represent the
                                                                        current state of a particular product or   3RD   Supported via a third party solution
                                                                    service. (More than one response to a single   CST   Supported via customization (changes to source code)
                                                                         requirement will be treated as a non
                                                                                       response)
                                                                                                                   FUT   Will be supported in a future release
                                                                                                                   NS    Not supported

       SYSTEM MECHANICS / INFORMATION
                                                                               RATING RESPONSE                                    ADDITIONAL COMMENTS
                TECHNOLOGY
                                                                     SUP      MOD       3RD      CST      FUT      NS                                                              Resp
 IT       General Operating Requirements Section
          The system should support real time on-line updates as
 IT1                                                                                                                                                                                NS
          the primary processing mode.
          The system should provide the ability to selectively
          archive system data based on a user-defined number of
 IT2      years or other user-defined criteria. The archived data                                                                                                                   NS
          should be able to be accessed via another medium,
          such as tape or DVD.
          The system should provide the ability to schedule batch
 IT3                                                                                                                                                                                NS
          jobs.
          The system should provide the ability to backup,
 IT4                                                                                                                                                                                NS
          recover, restart, and cancel jobs.
          The system should use common master files across all
 IT5      functional modules, i.e.. Purchasing and AP should                                                                                                                        NS
          share a single vendor master file.
          The system product database should allow access by
 IT6                                                                                                                                                                                NS
          an SQL-based language.
          The system should provide a product data model that
 IT7      can be used for the review of major data entities and                                                                                                                     NS
          relationships.




                                                                                               Page 1 of 169
      SYSTEM MECHANICS / INFORMATION
                                                                         RATING RESPONSE                  ADDITIONAL COMMENTS
               TECHNOLOGY
                                                                   SUP   MOD   3RD    CST     FUT    NS                         Resp
         The system should contain a date/time stamp and user
IT8      information reflecting an audit trail on every data                                                                    NS
         element.
         The system should provide the ability to maintain
IT9                                                                                                                             NS
         separate testing & production environments.
         The system should allow for vendor-approved
IT10     modifications of the product made by the Client without                                                                NS
         voiding product support.
         The system should utilize standard Internet connection
IT11                                                                                                                            NS
         and TCP/IP protocol to access all user interfaces
         The system's access requirements through firewalls
IT12     must be clearly identified and follow standard port                                                                    NS
         designations.
         The system should support Fiber Channel SAN
IT13                                                                                                                            NS
         Technology.
         The system and all application parameters should be
IT14                                                                                                                            NS
         table driven.
         The system's database management system should be
IT15                                                                                                                            NS
         ODBC and/or OLE DB compliant.
         The system should be an integrated native web based
IT16     system with common architecture and database, not a                                                                    NS
         web-enabled add-on.
         The system should provide field level encryption using
IT17                                                                                                                            NS
         3DES standards at a minimum.
         The system should have a thin client base and an n-
IT18                                                                                                                            NS
         tiered architecture design
         The system database should run on the Microsoft SQL
IT19                                                                                                                            NS
         Server RDBMS platform
         The system should run on a Windows 2003 Server (or
IT20                                                                                                                            NS
         current Windows Server) operating system.




                                                                                     Page 2 of 169
   SYSTEM MECHANICS / INFORMATION
                                                                              RATING RESPONSE                  ADDITIONAL COMMENTS
            TECHNOLOGY
                                                                        SUP   MOD   3RD    CST     FUT    NS                         Resp
           The system should provide access from outside of the
IT21       firewall by non-domain external users in accordance                                                                       NS
           with generally accepted security standards.
           The system should provide self service capabilities in
           order to allow vendors and employees to inquire on and
IT22       update their current information. Users would be able to                                                                  NS
           login remotely using a web browser to view/change their
           information. (non-domain required)
           The system should contain toolsets to accommodate
IT23
           the following:
IT23   1   Archiving/purging of data                                                                                                 NS
IT23   2   Database maintenance                                                                                                      NS
IT23   3   End-user interface design                                                                                                 NS
IT23   4   System upgrade administration and patches                                                                                 NS
IT23   5   System security                                                                                                           NS
IT23   6   API Maintenance                                                                                                           NS
           The proposed solution should offer a full suite of utility
IT24       tools required to execute various system maintenance
           functions including:
IT24   1   Backup management                                                                                                         NS
IT24   2   Multiple monitoring sessions                                                                                              NS
IT24   3   Performance monitoring (application and system)                                                                           NS
IT24   4   Ability to monitor executing jobs                                                                                         NS
           Sufficient instrumentation to monitor batch progress and
IT24   5                                                                                                                             NS
           send alerts about abnormal batch status.
IT24   6   Database optimization                                                                                                     NS
IT24   7   Sotrage archival and retrival                                                                                             NS
           The system should allow for the assignment of
IT25       alphanumeric manual or automatic document                                                                                 NS
           numbering.




                                                                                          Page 3 of 169
   SYSTEM MECHANICS / INFORMATION
                                                                           RATING RESPONSE                  ADDITIONAL COMMENTS
            TECHNOLOGY
                                                                     SUP   MOD   3RD    CST     FUT    NS                         Resp
       The system should not use any proprietary fundamental
IT26   components (e.g.: vendor's proprietary programming                                                                         NS
       language or DBMS.)
       The system should complete 100% of simple, single-
IT27   screen online inquiry transaction in under 1 second,                                                                       NS
       during peak usage.
       The system should track system uptime and transaction
IT28   response times in order to demonstrate operation within                                                                    NS
       acceptable levels.
       The system should allow searches for documents or
IT29                                                                                                                              NS
       tables by code page or name.
       The system should provide the ability to use portable
IT30   hard drive storage medium for storing archived historical                                                                  NS
       data and recovery logs.
       The system should provide the ability for the database
IT31   to run its backup, while simultaneously allowing inquiry                                                                   NS
       access to the database.
       The system should provide automated transaction back-
       out/roll-back should the system fail during transaction
IT32                                                                                                                              NS
       processing and/or a transaction fails to reach normal
       processing completion.
       The system should provide for and support the ability to
IT33   control the priority of batch jobs based upon multiple                                                                     NS
       user-defined criteria.
IT34   The system should support decentralized data entry.                                                                        NS
       The system should enable the client to enter
       organization-specific values in coding fields (i.e., lookup
       tables). These and other user configurations should be
IT35                                                                                                                              NS
       preserved around software updates (i.e., product
       upgrades/software releases should not overwrite client-
       specific coded data or configurations.)



                                                                                       Page 4 of 169
   SYSTEM MECHANICS / INFORMATION
                                                                          RATING RESPONSE                  ADDITIONAL COMMENTS
            TECHNOLOGY
                                                                    SUP   MOD   3RD    CST     FUT    NS                         Resp
IT36   The system should support searches by wild cards.                                                                         NS
       The system should allow on-line search capabilities
IT37                                                                                                                             NS
       based on any field or any combination of fields.
       General Requirements GAP
       System Help Section
       The system's on-line help should be available at the
IT38                                                                                                                             NS
       system, function, screen, and field level.
       The system's on-line help should be able to be printed, if
IT39                                                                                                                             NS
       necessary.
       The system's on-line help should be updated with each
IT40                                                                                                                             NS
       new version release.
       The system's on-line help should provide an index and
IT41                                                                                                                             NS
       search capability
IT42   The system's on-line help should be context sensitive.                                                                    NS
       The system help information should be able to be edited
       and/or augmented by the Client for specific additional
IT43                                                                                                                             NS
       help information. This information should be retained
       during upgrades.
       The system help feature should be linked to the vendors
IT44                                                                                                                             NS
       web-site for additional help.
       The vendor's support site should contain a knowledge
IT45   base where users can access system related reference                                                                      NS
       material and documents.
       The vendor's support site should contain complete and
       up-to-date manuals for all system modules and
IT46                                                                                                                             NS
       functionalities. The manuals should be available for all
       available versions of the software.
       The system should allow override or block/no-override
IT47   ability on specific error conditions and/or for specific                                                                  NS
       users.




                                                                                      Page 5 of 169
   SYSTEM MECHANICS / INFORMATION
                                                                          RATING RESPONSE                  ADDITIONAL COMMENTS
            TECHNOLOGY
                                                                    SUP   MOD   3RD    CST     FUT    NS                         Resp
       The system should allow the configuration of error
IT48                                                                                                                             NS
       messages to reflect override or block/no-override ability.
IT49   The vendor should provide access to a help desk.                                                                          NS
       The system's error messages should be integrated with
       online help functions, allowing the data entry person to
IT50                                                                                                                             NS
       be able to click on an error message and open the
       online help document to the appropriate section.
       The system should provide the ability to establish a
IT51                                                                                                                             NS
       standard rounding method.
IT52   The system should indicate required fields.                                                                               NS
       System Help GAP
       General Integration/Compatibility Section
       The system should provide full integration with standard
       desktop applications such as Word, Access, Excel and
IT53                                                                                                                             NS
       Adobe Acrobat. This includes the ability to import or
       export data directly into these desktop applications.
       The product should provide for integration and tools to
IT54                                                                                                                             NS
       easily export data to a data warehouse.
       The system should support Microsoft Internet Explorer
IT55                                                                                                                             NS
       version (7) or higher.
       The system should provide enterprise application
IT56                                                                                                                             NS
       integration (EAI) functionalities.
       The system should support data-transfer via flat files in
IT57   a range of formats (e.g., ASCII, variable and/or fixed                                                                    NS
       length, comma-delimited, etc.)




                                                                                      Page 6 of 169
   SYSTEM MECHANICS / INFORMATION
                                                                           RATING RESPONSE                  ADDITIONAL COMMENTS
            TECHNOLOGY
                                                                     SUP   MOD   3RD    CST     FUT    NS                         Resp
       The system should provide the ability to interface or
       integrate with Windows Active Directory and support a
       single user sign on if on a Windows system. This should
IT58                                                                                                                              NS
       include the ability to use Active Directory if the user is
       present, while at the same time allow other users who
       may not be found in Active Directory.
       The system should have the ability to interface or
IT59                                                                                                                              NS
       integrate with Microsoft Exchange.
       The system should provide a Software Development Kit
IT60   (SDK) that allows the technical staff to enhance and                                                                       NS
       integrate the system.
       General Integration/Compatibility GAP
       User Interface Section
       The system should provide the ability to configure
IT61                                                                                                                              NS
       screens/windows per user role.
       The system should provide the ability to AutoFill based
IT62   on a related field (i.e. auto completion of one field based                                                                NS
       on prior data entry).
       The system should provide data validation by providing
       error messages immediately after each field is entered,
IT63   rather than waiting until the entire screen, record or                                                                     NS
       transaction is finished. (account number, vendor ID,
       etc.)
       The system should provide a user-defined executive
IT64   dashboard (financial information, key performance                                                                          NS
       indicators, etc.) based on user profile
       The system should provide the capability for creating
IT65   "favorites" or shortcuts to frequently used screens and                                                                    NS
       reports.




                                                                                       Page 7 of 169
   SYSTEM MECHANICS / INFORMATION
                                                                       RATING RESPONSE                  ADDITIONAL COMMENTS
            TECHNOLOGY
                                                                 SUP   MOD   3RD    CST     FUT    NS                         Resp
       The system should provide the capability to tailor and
       configure functions, workflows, screens, outputs, codes
IT66                                                                                                                          NS
       and other normal processing items (in house) without
       invalidating the vendor support agreements.
       The system's controlled values should be available in a
IT67                                                                                                                          NS
       drop down boxes or popup windows.
IT68   The system should provide detailed error messages.                                                                     NS
       System error messages should appear in a consistent
IT69   format across all system modules and should be                                                                         NS
       customizable.
       The system should have the ability for a user to
       concurrently open multiple sessions/windows for both
IT70   inquiry and updating across any combination of                                                                         NS
       application modules, without losing any data previously
       entered on an open screen.
       The system should provide the ability to create new
IT71                                                                                                                          NS
       items by copying existing items.
       The system should provide cut and paste capabilities to
IT72                                                                                                                          NS
       move data from field to field.
       The system should allow data entry staff to have a
       choice of updating the system through use of a
IT73                                                                                                                          NS
       grid/spreadsheet interface options, or through GUI-
       based features.
       The system should be able to print in batch mode and
IT74                                                                                                                          NS
       interactively.
       The system should allow transactions to be selected by
IT75   any combination of date range, transaction type, User                                                                  NS
       ID, account number, etc.
       The system should have a built in calendar allowing
IT76   adjustments in processing and transaction dates for                                                                    NS
       holidays, weekends, etc.



                                                                                   Page 8 of 169
   SYSTEM MECHANICS / INFORMATION
                                                                           RATING RESPONSE                  ADDITIONAL COMMENTS
            TECHNOLOGY
                                                                     SUP   MOD   3RD    CST     FUT    NS                         Resp
       The system should provide the ability to send broadcast
IT77   message by specified users to users at any time, as well                                                                   NS
       as messages that are displayed at logon
       The product source code should be available to the
IT78                                                                                                                              NS
       Client
       The system should provide the capability to store,
       retrieve, display and print imaged documents. The
IT79   solution must provide the capability to receive scanned                                                                    NS
       documents from document scanners having industry-
       standard connection protocols (SCI, TCP/IP, etc.)
       The system should be able to accept scanned or
IT80   electronic documents in any format (pdf, xls, doc) and                                                                     NS
       link them to a data record.
       The product source code should be available for placing
       into escrow to be available to the Client in the event that
IT81                                                                                                                              NS
       the vendor is acquired by another company or goes out-
       of-business.
       The system should provide transaction logging or
       journalizing at the data base level. The system should
IT82                                                                                                                              NS
       be able to be recover all on-line transactions from the
       transaction log.
       The system should provide the ability to access any data
IT83   elements and files (permanent or temporary) within the                                                                     NS
       system
       The system should provide the ability to list all records
IT84                                                                                                                              NS
       included in a purge.
       The system should provide migration paths for new
IT85                                                                                                                              NS
       fields during software upgrades.




                                                                                       Page 9 of 169
   SYSTEM MECHANICS / INFORMATION
                                                                          RATING RESPONSE                   ADDITIONAL COMMENTS
            TECHNOLOGY
                                                                    SUP   MOD   3RD     CST    FUT     NS                         Resp
       The full system backup and/or restore should be able to
IT86   be accomplished within a maximum of 4 hours.                                                                               NS
       (preferably 2 hours)
       The system should be scalable to accommodate a
       potential increase in the number of users. (Vendors:
IT87                                                                                                                              NS
       please describe a common approach for application
       scalability under the "Additional Comments" column.)
       The system should allow the online creation of new user-
       defined data fields for miscellaneous data tracking,
IT88   alteration of database structure, and update of a global                                                                   NS
       data dictionary with these elements through proper
       security.
       The system should lock records at the lowest database
       level when multiple users are accessing the same
IT89                                                                                                                              NS
       record. (Vendors: please describe how this process
       works under the "Additional Comments" column.)
       The system should provide various program checks for
IT90   controlling data files, verifying correct processing, and                                                                  NS
       ensuring data integrity.
       The system should use appropriate rules and
IT91                                                                                                                              NS
       constraints to enforce and maintain referential integrity.
       The system should have the ability to define global
IT92                                                                                                                              NS
       business rules.
       The system should provide table look-up fields that can
IT93                                                                                                                              NS
       be linked or refer to other tables.
       The system should provide the ability to roll back
IT94                                                                                                                              NS
       transactions.
       The system should be able to validate the integrity of the
IT95                                                                                                                              NS
       database before and after a purge.



                                                                                      Page 10 of 169
    SYSTEM MECHANICS / INFORMATION
                                                                            RATING RESPONSE                   ADDITIONAL COMMENTS
             TECHNOLOGY
                                                                      SUP   MOD   3RD     CST    FUT     NS                         Resp
        The system should have the ability to create new items
IT96                                                                                                                                NS
        by using pre-defined item templates.
        The system should have the capability to assign default
IT97                                                                                                                                NS
        values for fields in order to reduce the data entry effort.
        The system should provide simultaneous access to data
IT98    by multiple users, without degradation to the system                                                                        NS
        response time.
        The system should allow for mass updates to certain
IT99                                                                                                                                NS
        fields.
        The system should provide active notifications based on
IT100   specific events and conditions. (Vendors: Explain how                                                                       NS
        this works in the system).
        The system should integrate with existing user
IT101                                                                                                                               NS
        authentication and security.
        The system should provide an application system log for
IT102                                                                                                                               NS
        system supporting staff.
        The system should provide efficient application level
        load-balancing functionality. (Vendors: please describe
IT103                                                                                                                               NS
        the application architecture and how this works under
        the "Additional Comments" column.)
        The system should be able to run on servers in a cluster
IT104                                                                                                                               NS
        environment.
        The system should provide a suspense log for rejected
IT105                                                                                                                               NS
        or unposted transactions.
        The system should provide the capability to print
IT106   specialized business forms such as checks, purchase                                                                         NS
        orders, invoices, 1099's, etc.
        The system should provide the use of signature pads in
IT107   order to capture required signatures for credit card                                                                        NS
        payments.




                                                                                        Page 11 of 169
    SYSTEM MECHANICS / INFORMATION
                                                                             RATING RESPONSE                   ADDITIONAL COMMENTS
             TECHNOLOGY
                                                                       SUP   MOD   3RD     CST    FUT     NS                         Resp
        The system should provide the use of digitized
IT108                                                                                                                                NS
        signatures in order to print electronic signatures.
        The system should allow for the definition of default
IT109                                                                                                                                NS
        printers for each user
        The system should provide the ability to define system
IT110   key words to fit current business practicies and have                                                                        NS
        those key words propagate throughout the system.

        The system should provide the ability to electronically
IT111                                                                                                                                NS
        interface with the State, banks and vendors.
        User Interface GAP
        Reporting & Related Requirements Section
        The system should provide a robust report writer to
        develop customized reports. Report writing should be
IT112                                                                                                                                NS
        security enabled so that only users with the proper
        access can write reports.
        The system should provide real time reporting and
IT113                                                                                                                                NS
        inquiry.
        The system should support the ability to send report to
IT114                                                                                                                                NS
        printer, file and email (Exchange).
        The system should be able to generate customized
IT115                                                                                                                                NS
        reports that can be viewed on-screen before printing.
        The system should present data in a graphical manner,
IT116   including bar charts, line charts, pie charts, Gantt charts,                                                                 NS
        etc. in reports.
        The system should provide a report design wizard to
IT117                                                                                                                                NS
        guide users through the report creation process.
        The system should have the capability to view the report
IT118                                                                                                                                NS
        on screen while it is in development.




                                                                                         Page 12 of 169
    SYSTEM MECHANICS / INFORMATION
                                                                            RATING RESPONSE                   ADDITIONAL COMMENTS
             TECHNOLOGY
                                                                      SUP   MOD   3RD     CST    FUT     NS                         Resp
        The system should provide HTML preview that allows
IT119   report authors to see how reports will look when                                                                            NS
        published to the web.
        The system should provide the ability to perform auto
IT120   saving of a report (during development) after a user-                                                                       NS
        defined period of time has passed.
        The system should provide intuitive reporting tools such
IT121   as vertical rulers and guides, grids - to facilitate report                                                                 NS
        design and formatting
        The system should allow for automatic/template report
IT122   styles and the optional auto arrangement of report fields                                                                   NS
        that have been selected to appear on the report.
        The system should provide the ability to use a click-and-
IT123   drag graphical user interface to facilitate the creation of                                                                 NS
        reports.
        The system should provide the ability to setup (multiple)
IT124                                                                                                                               NS
        user defined subtotals and totals within a report.
        The system should provide the ability to move and
IT125                                                                                                                               NS
        resize objects and select multiple objects.
        The system should provide font formatting by style and
IT126                                                                                                                               NS
        size.
IT127   The system should provide vertical text rotation.                                                                           NS
        The system should provide the setup of horizontal or
IT128                                                                                                                               NS
        vertical page numbering.
        The system should allow hyperlinks to be embedded
IT129                                                                                                                               NS
        into reports.
        The system should allow users to redo an action and
IT130                                                                                                                               NS
        undo multiple times (to undo a series of actions).
        The system should allow for the setup of report and
IT131                                                                                                                               NS
        page footers.



                                                                                        Page 13 of 169
    SYSTEM MECHANICS / INFORMATION
                                                                           RATING RESPONSE                   ADDITIONAL COMMENTS
             TECHNOLOGY
                                                                     SUP   MOD   3RD     CST    FUT     NS                         Resp
        The system should allow for the customization of report
IT132   headers and column titles, and the creation of other                                                                       NS
        user defined text fields.
        The system should provide automated alerts and
IT133   checks that quickly find broken links, formula errors, and                                                                 NS
        dependency issues.
        The system should provide a formula editor to assist in
IT134                                                                                                                              NS
        adding formulas to the report.
        The system should provide the ability to export to XML,
IT135                                                                                                                              NS
        PDF, HTML, XLS (and XLSX), DOCX (and DOCX), etc.

IT136   The system should provide mail merge with MS Word.                                                                         NS

        The system should be able to publish directly to a
IT137                                                                                                                              NS
        document management system (Sharepoint 2007, etc.)
        The system should provide the ability to customize
        report prompts (this includes the actual verbage of the
IT138   question prompt, the default response (if any), and the                                                                    NS
        specific rules established in association with the report
        prompt)
        The system should provide the ability to setup prompts
        based on dynamic values. This means that report
IT139   designers do not have to maintain static prompt value                                                                      NS
        lists within individual reports. Instead, they can reuse
        existing prompts stored in the repository.

        The system should enable security setup for reporting.
IT140   This may include restricting users from running reports                                                                    NS
        on activity that is unrelated to what they do.




                                                                                       Page 14 of 169
    SYSTEM MECHANICS / INFORMATION
                                                                           RATING RESPONSE                   ADDITIONAL COMMENTS
             TECHNOLOGY
                                                                     SUP   MOD   3RD     CST    FUT     NS                         Resp
        The system should provide for calculations based on
        report columns, such as adding or subtracting one
IT141                                                                                                                              NS
        column from another or setting up analysis/variance
        columns.
        The system should provide the ability to report or inquire
        on any data field within the General Ledger or any other
IT142   subsystem. Selection for a report should allow mixing                                                                      NS
        and matching of either/or General Ledger and
        Project/Activity accounts.
        The system should allow for developing customized
IT143   reports that can extract information from several                                                                          NS
        subsystems and produce them on the same report.
        The system should provide the ability to schedule/queue
IT144                                                                                                                              NS
        numerous reports for automatic printing. (schedule jobs)

        The system should allow users to set up folders to
IT145   organize the various types of previously created reports                                                                   NS
        (such as by department or function of the report)
        The system should allow sorting, and grouping of data
IT146                                                                                                                              NS
        on customized reports in user-specified orders
        The system should provide complex selection criteria
IT147   utilizing operators, such as dashes to indicate a range,                                                                   NS
        and wild cards.
        The system should provide the ability to drill down, drill
        up, and/or drill around (create cross tabs) to supporting
IT148                                                                                                                              NS
        documents and related transactions from any field within
        the system.
        The system should provide reports that can drill down to
        the lowest level (i.e.: the transaction, attached images,
IT149                                                                                                                              NS
        etc.). Reports should also allow for drill-around
        functionality.



                                                                                       Page 15 of 169
    SYSTEM MECHANICS / INFORMATION
                                                                             RATING RESPONSE                   ADDITIONAL COMMENTS
             TECHNOLOGY
                                                                       SUP   MOD   3RD     CST    FUT     NS                         Resp
        The system should allow for system generated reports
IT150   be copied over to user libraries where they can be                                                                           NS
        modified without altering the original report.
        The system should provide the capability to use
        "English" descriptions and/or an industry standard
IT151                                                                                                                                NS
        vocabulary for data elements, rather than specifying the
        exact data element name.
        The system should allow the creation of reports based
IT152   on any data tables or data element, including all                                                                            NS
        subystems and audit logs.
        The system should allow users to run reports on prior
IT153                                                                                                                                NS
        period and prior year information for any subsystem.
        The system should allow the system administrator to
IT154   define the number of jobs that can be executed at the                                                                        NS
        same time.
        The system should allow authorized users to change the
IT155                                                                                                                                NS
        priority of their job to place it first in the queue.
        The system should allow users to view the jobs currently
IT156                                                                                                                                NS
        being executed and the jobs waiting to be processed.
        The system should provide details about jobs that are in
IT157   the queue, such as the creator, date and time the job                                                                        NS
        was created, size of job, etc.
        The system should allow the system administrator to
IT158                                                                                                                                NS
        purge jobs.
        The system should allow the flexibility to create
        conditional rules on a report. For example, if a user
        runs a financial statement before the month is closed,
IT159                                                                                                                                NS
        the report will indicate "draft." If the report is run after
        the month has been closed, the report will not indicate
        "draft."



                                                                                         Page 16 of 169
    SYSTEM MECHANICS / INFORMATION
                                                                               RATING RESPONSE                   ADDITIONAL COMMENTS
             TECHNOLOGY
                                                                         SUP   MOD   3RD     CST    FUT     NS                         Resp
        The system's report writer should come with a library of
        canned reports that have been specifically developed for
        the report writer application. These pre-developed
        reports should be available as a starting point to allow
IT160                                                                                                                                  NS
        the client to modify and refine them to their own needs.
        Examples of reports may include account listings,
        purchase order status reports, accounts payable
        detailed transaction listings, etc.
        The system should provide a full set of reports that are
IT161   in compliance with AICPA, GASB, FASB and GAAP                                                                                  NS
        standards.
        The system should provide a foundation of standard
        government accounting reports and provide a user
IT162                                                                                                                                  NS
        friendly report writer to develop new reports or edit
        standard reports to meet the client's needs.
        The system should provide for the incorporation of
IT163   general information into reports, such as the current                                                                          NS
        date, time, requestor, etc.
        The system should allow reports to be sent to an
IT164   individual or multiple individuals as a distribution list, via                                                                 NS
        email.
        The system should provide the capability to generate
IT165                                                                                                                                  NS
        letters and notices to user-defined groups.
        The system should provide the capability to produce
IT166                                                                                                                                  NS
        mailing labels.
        The system should provide the ability to create and
        define an unlimited number of user defined reports
IT167                                                                                                                                  NS
        utilizing query, third party report writing tools (e.g.
        Crystal Reports, Business Objects).
        Users should be able to create and save their own
IT168                                                                                                                                  NS
        reports.




                                                                                           Page 17 of 169
    SYSTEM MECHANICS / INFORMATION
                                                                         RATING RESPONSE                   ADDITIONAL COMMENTS
             TECHNOLOGY
                                                                   SUP   MOD   3RD     CST    FUT     NS                         Resp
        The system should allow users to add or remove reports
IT169                                                                                                                            NS
        and templates to/from menus with proper security.
        Reporting & Related Requirements GAP
        System Security Section
        The system should track the use of the system by
IT170                                                                                                                            NS
        authorized users.
        They system should provide a "forget password" reset
IT171                                                                                                                            NS
        process.
        The system should provide the ability for users to
IT172                                                                                                                            NS
        change their own password.
        The system should have the ability to report attempts by
IT173                                                                                                                            NS
        unauthorized users to use the system.
        The system should have the ability to suspend after "x"
IT174   attempts to access the system with an incorrect                                                                          NS
        password if authentication is internal to the system.
        The system should provide the ability to assign sunset
        dates to user defined passwords and/or prevent user
IT175                                                                                                                            NS
        defined passwords from expiring if authentication is
        internal to the system.
        The system should have the ability to copy a security
IT176                                                                                                                            NS
        profile.
        The system's Ad Hoc/Query/Reporting should be
IT177                                                                                                                            NS
        subject to application security.
        The system should provide e-commerce security
IT178   including customer authentication and encryption to                                                                      NS
        protect customer data.
        The system's e-commerce capabilities should be PCI-
IT179                                                                                                                            NS
        compliant.
        The system should support standard Internet security
IT180   including, but not limited to Secure Hypertext Transfer                                                                  NS
        Protocol (HTTPS).



                                                                                     Page 18 of 169
    SYSTEM MECHANICS / INFORMATION
                                                                              RATING RESPONSE                   ADDITIONAL COMMENTS
             TECHNOLOGY
                                                                        SUP   MOD   3RD     CST    FUT     NS                         Resp
            The system should support standard Internet security
            including, but not limited to Secure Socket Layers (SSL).
IT181                                                                                                                                 NS
            If SSL is not supported, please describe the supported
            Digital Certificates.
            System audit trails should distinguish between
IT182                                                                                                                                 NS
            administrative and/or financial actions.
            The system should retain audit trail information for the
IT183
            following:
IT183   1   System activity (system logins)                                                                                           NS
IT183   2   Document and data changes, including approvals                                                                            NS
            User name, ID, time, date, revised amount, and before
IT183   3                                                                                                                             NS
            and after update results
            The system should have the ability to define user
IT184
            access based on:
IT184 1     Departments/Organizations                                                                                                 NS
IT184 2     Roles                                                                                                                     NS
IT184 3     Individuals                                                                                                               NS
IT184 4     Application                                                                                                               NS
IT184 5     File or document type                                                                                                     NS
IT184 6     User ID and administratively-defined groups.                                                                              NS
IT184 7     IP address.                                                                                                               NS
IT184 8     Menu                                                                                                                      NS
IT184 9     Module                                                                                                                    NS
IT184 10    Report                                                                                                                    NS
IT184 11    Screen                                                                                                                    NS
IT184 12    Transaction type                                                                                                          NS
            The system should have the ability to define user
IT185
            access based on:
IT185   1   Databases                                                                                                                 NS
IT185   2   Tables                                                                                                                    NS
IT185   3   Documents                                                                                                                 NS
IT185   4   Data Elements                                                                                                             NS



                                                                                          Page 19 of 169
    SYSTEM MECHANICS / INFORMATION
                                                                               RATING RESPONSE                   ADDITIONAL COMMENTS
             TECHNOLOGY
                                                                         SUP   MOD   3RD     CST    FUT     NS                         Resp
            The system should have the ability to define and lookup
IT186
            a user based on:
IT186   1   User Name                                                                                                                  NS
IT186   2   Role                                                                                                                       NS
IT186   3   User ID                                                                                                                    NS
IT186   4   Organization Name/Number                                                                                                   NS
IT186   5   Date user was created                                                                                                      NS
IT186   6   Last login                                                                                                                 NS
            The system should allow users to review security
IT187                                                                                                                                  NS
            transaction history online or in a report.
            The system should allow users to review security
IT188                                                                                                                                  NS
            transaction history in a report.
            The system should be able to automatically sign a
IT189       dormant user off of the system after a user-defined time                                                                   NS
            period.
            The system should accommodate both decentralized
IT190       (functional area security administrators) and centralized                                                                  NS
            (IT security) security.
            The system should allow multiple security roles to be
IT191                                                                                                                                  NS
            assigned to the same user.
            When conflicting multiple roles are assigned to the
IT192                                                                                                                                  NS
            same user, the most restrictive role should prevail.
            The system should provide for a secure database
            environment available only to defined processes (e.g. no
IT193                                                                                                                                  NS
            direct entry/update outside of the application, except for
            designated administrators)
            The system should provide the ability to define security
IT194       profiles to authorize users to view, update and approve                                                                    NS
            data.
            The system should provide the ability to set up a
IT195       security profile based on pre-defined job function/role,                                                                   NS
            user and/or organization.



                                                                                           Page 20 of 169
    SYSTEM MECHANICS / INFORMATION
                                                                                 RATING RESPONSE                   ADDITIONAL COMMENTS
             TECHNOLOGY
                                                                           SUP   MOD   3RD     CST    FUT     NS                         Resp
            The system should record unsuccessful logon attempts.
IT196       This information should be retained for a user-defined                                                                       NS
            period of time.
            The system should provide the ability to configure User
            ID/password rules such as length, alpha/numeric,
IT197                                                                                                                                    NS
            upper/lower case, password definition and expiration
            period.
            The system should support role inheritance, so system
IT198       administrator can combine roles, and modify the parent                                                                       NS
            role to form a new role.
            The system should have the ability to synchronize
            application security with database security. Application
IT199                                                                                                                                    NS
            security should not be violated when logging into the
            database directly using the same user ID and password.
            The system should allow for the definition of security on
            reports at any level. For example, read/write security
IT200       can be placed on the report itself, on the entire folder (to                                                                 NS
            enable the same security on all reports within the
            folder), or on any higher level
            The system should allow for the definition of security
            roles on system reporting. This would enable users with
IT201                                                                                                                                    NS
            similar reporting needs to be assigned to the same
            reporting role.
            The system should provide ability to view or obtain
IT202
            security reports showing:
IT202   1   Security breaches or attempts                                                                                                NS
IT202   2   Authorized system use                                                                                                        NS
IT202   3   Changes to security profiles                                                                                                 NS
            Security snapshot on a specific time period specified by
IT202   4                                                                                                                                NS
            the user
            System Security GAP



                                                                                             Page 21 of 169
    SYSTEM MECHANICS / INFORMATION
                                                                          RATING RESPONSE                   ADDITIONAL COMMENTS
             TECHNOLOGY
                                                                    SUP   MOD   3RD     CST    FUT     NS                         Resp
        System Training Section
        The system should provide computer based training
IT203   programs so users can train independent of classroom                                                                      NS
        training.
        The system should provide the ability to customize
IT204   computer based training to meet specific Client                                                                           NS
        processes
        The vendor should provide development tool training
IT205                                                                                                                             NS
        and support via classroom, on line, hard copy, etc.
        System Training GAP
        System Workflow Section
        The system should provide for the electronic
        management, approval routing, and reporting of work
IT206   generated by individuals such as requisitions (including                                                                  NS
        capital asset requisitions & project requests), purchase
        orders, journal entries, etc.
        The system should come with a library of canned
        workflow models that have been specifically developed
IT207   for the workflow application. These pre-developed                                                                         NS
        models should be available as a starting point to allow
        the client to modify and refine them to their own needs.
        The system should provide a work queue that can be
IT208   managed or owned by an individual, variable work                                                                          NS
        group, department, or location.
        Workflow activities should be able to be done
IT209   sequentially, concurrently, or a combination of both                                                                      NS
        (within an entire workflow set of processes).
        The system should provide a series of queue's that can
        be defined based upon system exception conditions
IT210                                                                                                                             NS
        requiring follow-up, items requiring review and approval,
        or to do items.



                                                                                      Page 22 of 169
    SYSTEM MECHANICS / INFORMATION
                                                                             RATING RESPONSE                   ADDITIONAL COMMENTS
             TECHNOLOGY
                                                                       SUP   MOD   3RD     CST    FUT     NS                         Resp
        The system should provide for e-mail notification or on-
IT211                                                                                                                                NS
        line notification of documents pending approval.
        The system should allow the flow of work to be defined
        based on any data element or combination of data
        elements from initiation of a work queue item through
IT212                                                                                                                                NS
        various in-process, review, and approval activities (for
        all system modules). The work queue will follow a logical
        progression.
        The workflow tools should integrate with Exchange
IT213   capabilities, such as the recipient list, calendaring, blind                                                                 NS
        copy, task creation, etc.
        The system should have the ability to re-direct an
IT214                                                                                                                                NS
        approval based on workflow rules and setup.
        The system work queue items should allow for on-line
IT215                                                                                                                                NS
        modification based on user defined parameters.
        The system work queue items should be able to have
IT216   minor edits without the system re-triggering the approval                                                                    NS
        back to the person who initiated it.
        The system should have the ability to allow user-defined
        corrections to a document after it has been approved
IT217                                                                                                                                NS
        without affecting the approval status. (e.g. correcting an
        object code)
        The system work queue items should have the ability to
IT218                                                                                                                                NS
        be deleted/cancelled on-line.
        The system work queue items should have the ability to
IT219   be reassigned to another individual, work group,                                                                             NS
        department or location on-line.
        The system should have the ability to cancel all (or
IT220   selected) previous approvals once the document is                                                                            NS
        rejected.




                                                                                         Page 23 of 169
    SYSTEM MECHANICS / INFORMATION
                                                                           RATING RESPONSE                   ADDITIONAL COMMENTS
             TECHNOLOGY
                                                                     SUP   MOD   3RD     CST    FUT     NS                         Resp
        The system should have the ability to "force" a modified
IT221                                                                                                                              NS
        document to go through the approval process again.
        The system should be able to generate stagnant work
IT222   notifications and/or escalate to the next approver in the                                                                  NS
        queue.
        The system should provide for work queue usage and
IT223                                                                                                                              NS
        performance reporting
        The system should provide the capability to route
IT224   scanned documents and/or reports to designated users                                                                       NS
        (groups, individuals).
        The system should provide for notes/comments on
IT225                                                                                                                              NS
        transactions
        The system should record user id and date on
IT226                                                                                                                              NS
        notes/comments
        The system should provide the ability to view a log of all
        activities (approvals, notes, name of approver, date of
IT227                                                                                                                              NS
        approvals, etc) in association with a given workflow
        item.
        The system should be able to send a standardized
        and/or customized notification to a user explaining why
IT228                                                                                                                              NS
        the document was rejected or unapproved (with user
        and date information)
        The system should allow the viewing of workflow items
IT229   by their status (pending approval, approved, rejected,                                                                     NS
        etc.) in real time.
        The system should provide adequate levels of
        management review and approval throughout the
IT230                                                                                                                              NS
        system. This may include an automatic queuing or
        routing of transactions pending management approval.




                                                                                       Page 24 of 169
    SYSTEM MECHANICS / INFORMATION
                                                                         RATING RESPONSE                   ADDITIONAL COMMENTS
             TECHNOLOGY
                                                                   SUP   MOD   3RD     CST    FUT     NS                         Resp
        The system should provide the ability to establish
IT231                                                                                                                            NS
        approval based on user defined thresholds.
        The system should allow electronic approval to be
IT232   delegated to another individual in the event of ones                                                                     NS
        absence
        The system should provide error detection event
IT233   triggers to forward user defined alerts to workstations,                                                                 NS
        pagers, phones, and e-mail.
        System Workflow Average GAP
        SLCO Requirements Section
        The system should provide multi company capability
IT234   and be able to generate financial statements for one                                                                     NS
        company or combined companies.
        The system should provide for a 4 digit year throughout
IT235                                                                                                                            NS
        the system to allow for the year 2000+.
        The system/product utilizes a windowed / web based (N-
IT236                                                                                                                            NS
        Tier) environment offering GUI desktop environment.
        The system should have a thin client base and n-tiered
IT237                                                                                                                            NS
        architecture design
        The system user manual should be provided in hard
IT238                                                                                                                            NS
        copy format.
        The system user manual should be provided in
IT239                                                                                                                            NS
        electronic format.
        The system should be 100% compatible with industry
IT240                                                                                                                            NS
        standard firewall technology.
        The system should provide navigation using the
IT241                                                                                                                            NS
        keyboard
        The system should provide navigation using user
IT242                                                                                                                            NS
        defined hot keys.




                                                                                     Page 25 of 169
    SYSTEM MECHANICS / INFORMATION
                                                                           RATING RESPONSE                   ADDITIONAL COMMENTS
             TECHNOLOGY
                                                                     SUP   MOD   3RD     CST    FUT     NS                         Resp
        The system should support the input of values into fields
IT243   without the use of a drop down box by typing in first few                                                                  NS
        letters until valid value appears in box.
        The system should provide the capability to print directly
IT244                                                                                                                              NS
        from any screen.
        The system should provide the ability to recover the
IT245                                                                                                                              NS
        system from the transaction log
        In general terms, the solution will promote a central
IT246   repository for purposes of data security, control, backup                                                                  NS
        and recovery.
        The product will be available and support 24 hour by 7
IT247                                                                                                                              NS
        day a week business operations.
        The solution should provide full recovery features for all
IT248                                                                                                                              NS
        on-line transactions.
        The system should restrict users to only the data they
IT249                                                                                                                              NS
        are authorized to access.
IT250   The system should provide field level security.                                                                            NS
        The vendor should provide a comprehensive computing
IT251                                                                                                                              NS
        site disaster recovery or business recovery approach.

        The system should provide ability to generate warning
        message to notify administrator if multiple security roles
IT252                                                                                                                              NS
        assigned to a single user are conflicting. Such
        instances shall be recorded by system.
        The system should provide ability to view or obtain
IT253                                                                                                                              NS
        security reports showing profiles by user.
        The system should provide a foundation of standard
        government accounting reports and provide a user
IT254                                                                                                                              NS
        friendly report writer to develop new reports or edit
        standard reports to meet the County’s needs.
IT255   The system should provide user defined fields.                                                                             NS



                                                                                       Page 26 of 169
    SYSTEM MECHANICS / INFORMATION
                                                                            RATING RESPONSE                   ADDITIONAL COMMENTS
             TECHNOLOGY
                                                                      SUP   MOD   3RD     CST    FUT     NS                         Resp
        The system should have the capability to maintain
IT256                                                                                                                               NS
        individual workload "to do lists".
        The system should have the capability to classify and
        define the status of documents, transactions, files,
IT257                                                                                                                               NS
        records, etc. under the requirements of the GRAMA
        laws in the State of Utah.
        The system should allow users to perform on-line
IT258   inquiries from all of the subystems with flexible selection                                                                 NS
        criteria options in order to define report parameters..
        The system should have the ability to save tables or
IT259   documents that are commonly used in a central                                                                               NS
        location.
        The system should allow users to print directly to any
IT260                                                                                                                               NS
        printer defined on the user's PC.
        SLCO Requirements Average GAP
        Total GAP




                                                                                        Page 27 of 169
SALT LAKE COUNTY                                                                  INSTRUCTIONS                                               RATING LEGEND
Functional Requirements Matrix                                                                                     SUP   Supported as delivered "out-of-the-box"
                                                                     Complete the worksheet by placing an X in           Supported via modifications (screen configurations, reports, GUI
                                                                        the most appropriate column for each       MOD
                                                                                                                         tailoring, etc)
                                                                       criterion. The X's should represent the
                                                                        current state of a particular product or   3RD   Supported via a third party solution
                                                                    service. (More than one response to a single   CST   Supported via customization (changes to source code)
                                                                         requirement will be treated as a non
                                                                                       response)
                                                                                                                   FUT   Will be supported in a future release
                                                                                                                   NS    Not supported


       GENERAL LEDGER MANAGEMENT                                               RATING RESPONSE                                    ADDITIONAL COMMENTS
                                                                     SUP      MOD       3RD      CST      FUT      NS                                                              Resp
 GL     System Setup Section
        The system should provide for sufficient accounting
        code elements to code and classify transactions (i.e.:
 GL1                                                                                                                                                                                NS
        fund, organization, department, division, object code,
        object code summary, projects/activities,etc.)
        The system should allow for the setup of a hierarchical
        account structure to allow for grouping or rollup of cost
 GL2                                                                                                                                                                                NS
        centers and accounts (chart of accounts) for G/L
        reporting and on-line inquiry.
        The system should provide the ability to define the types
        of accounts that can be used in conjunction with any
 GL3    given cost center. For example, a cost center can be                                                                                                                        NS
        restricted so that it can only be paired with revenue and
        expense accounts (and not asset/liability accounts).
        The system should provide the ability to define the
        subsystems in which a specific account can be used.
        For example, the Office Supplies account can be used
 GL4                                                                                                                                                                                NS
        within Purchasing, Accounts Payable, and the General
        Ledger, but it cannot be used within Accounts
        Receivable.




                                                                                              Page 28 of 169
         The system should provide the ability to assign a
GL5                                                                                       NS
         responsible person to each cost center.
         The system should allow administrator control over
         account code terminology. In other words, the system
GL6      should allow the user to establish their own                                     NS
         group/element/dimension names for cost centers and
         object codes.
         The system should allow for the creation of shortcut
         account numbers in order to facilitate data entry. A
GL7                                                                                       NS
         short series of numbers can be entered instead of the
         fully qualified account.
         The system should allow for the setup of user defined
GL8
         month-end posting restrictions to:
GL8    1 Allow each month to be defined as open or closed.                                NS
         Define the number of days in which users can still post
         back to the prior month. The system should have the
         capability to define this by subsystem. For example,
GL8    2                                                                                  NS
         after the 10th day of the month, AP cannot post back to
         the prior month and after the 15th day of the month, no
         GL transactions can be booked to the prior month.

           Allow administrators the ability to override blocks so they
GL8    3                                                                                  NS
           can post back to previous months, if necessary.

           The system should provide the ability to define the
           number of reporting periods within a fiscal year. This
GL9        would allow for the separation of unique periods (13th,                        NS
           14th, etc.) for balance forward entries, audit required
           adjustments, and other special closing entries.
           The system should allow for the setup of multiple seed
           numbers for journals. This would allow different
GL10       numbering conventions to be used for different types of                        NS
           journal entries, which would facilitate reporting and
           inquiring based on these groups.




                                                                         Page 29 of 169
       The system should provide the ability to set up multiple
GL11                                                                                   NS
       ledgers to accommodate different legal entities.
       The system should provide the ability to maintain
GL12                                                                                   NS
       multiple charts of accounts for different legal entities.
       System Setup Average GAP
       General Operating Requirements Section
       The General Ledger system should be integrated to
       financial, procurement, work order and payroll
GL13                                                                                   NS
       subsystems in order to provide centralized, real-time
       information to all users.
       The system should allow processing in the current
GL14   period, future periods, previous periods, and even                              NS
       previous years (with the proper security access).
       The system should provide for the automation of most
GL15   intrafund and interfund clearing entries based on                               NS
       defined rules to ensure that funds stay in balance.
       The system should provide the ability to associate each
GL16   transaction with a user name/user number, job number,                           NS
       entry date and time
       The system should be able to maintain a history of all
GL17   changes made to accounts and cost centers (not only                             NS
       the latest change)
       The system should provide the ability to block the
       deletion of accounts that have associated
GL18                                                                                   NS
       history/transactions. (These accounts should be
       inactivated, not deleted).
       The system should provide the ability to re-open
GL19                                                                                   NS
       inactivated accounts.
       The system should have the ability to run a utility to
       change old accounts to new accounts, including the
GL20   update of all historical transactions. The ability to                           NS
       inquire and/or view all historical transactions should still
       be available.




                                                                      Page 30 of 169
           The system should allow the user to view the future
           impact to the organizational structure before making any
GL21                                                                                   NS
           actual change that would impact it (on-screen or by
           report option)
           The system should have built-in safeguards to ensure
GL22       subsidiary accounts are always in balance to G/L control                    NS
           accounts.
           The system should provide for automated monthly and
GL23                                                                                   NS
           year end closing entries.
           The system should provide authorized users the ability
           to reverse transactions, provided that there is an audit
GL24                                                                                   NS
           trail. The system should retain the data within the
           batch/journal so it can be reposted, if necessary.
           The system should provide the ability to copy accounts
GL25                                                                                   NS
           to facilitate the entry of similar records.
           The system should provide for an unlimited number of
GL26                                                                                   NS
           data entry lines (dr/cr's) on a journal entry.
           The system should provide for recurring journal entry
           templates which can be used to create a journal entry
GL27                                                                                   NS
           with the same accounts and debit and credit
           transactions.
           The system should have the ability to automatically
GL28       produce a journal entry based upon user defined rules
           and calculations:
           For allocation of indirect costs, fringe costs, space
GL28   1                                                                               NS
           costs, or other.
           For pooled investment interest allocation based on
GL28   2   average daily cash balance or other chart of accounts                       NS
           criteria.
           That are automatically triggered upon the completion of
GL28   3                                                                               NS
           another transaction within the system.
GL28   4   With the ability to support multiple step allocations.                      NS
           That allow users to review and make adjustments to the
GL28   5                                                                               NS
           resulting journal entry prior to posting.




                                                                      Page 31 of 169
       The system should automatically generate accrual
GL29   reversal entries for posting to the next accounting period                                         NS
       or to a user defined period.
       The system should provide the ability to warn users of
       errors on-line before posting (account code, budget
GL30                                                                                                      NS
       allowance, duplicate journal entry number, dr/cr's do not
       balance, etc)
       The system should provide a free form text field on
GL31   journal entries that allows for ample space to include a                                           NS
       several sentence description.
       The system should provide the ability to calculate and
       post balance forward entries to a new year. The
GL32                                                                                                      NS
       balances should be automatically updated as additional
       adjustments are made to the open (prior) year.
       The system should provide the ability to
GL33   upload/download general ledger transactions                                                        NS
       (integration with desktop applications)
       The system should provide a work order module that
       integrates with GL, Projects/Activity, Inventory, Fixed
GL34   Assets, Payroll, Billing, etc. It must be flexible enough                                          NS
       to interface with the Fleet Management and Fuel
       Management systems.
       The system should provide the ability to link images and
GL35                                                                                 Currently use Sire   NS
       source documents to journal entries.
       The system should provide the ability to route journal
GL36                                                                                 Currently use Sire   NS
       entries for approval based on user defined rules.
       General Operating Requirements Average GAP
       Inquiry and Reporting Requirements Section
       The system should provide the ability to support trial or
GL37   pre-closes with the ability to generate supporting                                                 NS
       financial reports.
       The system should provide the ability to close books
GL38   and prepare complete financial statements for any                                                  NS
       month-end, quarter-end, and/or year-end.




                                                                    Page 32 of 169
       The system should provide the ability to perform
GL39   consolidation and eliminations necessary to prepare                            Allow government wide journal entries   NS
       entity-wide financial statements
       The system should be able to maintain an unlimited
GL40   history of transactions and balances that can be                                                                       NS
       reported or inquired on.
       The system should allow inquiries on prior fiscal year
GL41                                                                                                                          NS
       data in summary or detail form.
       The system should allow reports to be generated based
GL42                                                                                                                          NS
       on any user defined selection criteria.
       They system should provide the ability to report
GL43   variances between actual and forecasted cash                                                                           NS
       balances.
       The system should provide the ability to drill down to
GL44                                                                                                                          NS
       detail transactions on screen or from within reports.
       The system should allow users to print/view a proof
GL45                                                                                                                          NS
       report to verify entries before posting
       The system should provide the ability to run
GL46   reports/inquiries with the option of including unposted                                                                NS
       transactions.
       The system should have the ability to report for any
GL47   selected time period (monthly, quarterly, multi-year, prior                                                            NS
       year, etc.) that is defined by the user.
       The system should provide the ability to meet GAAP,
GL48   GAAFR/GFOA, GASB (including GASB 34) and FASB                                                                          NS
       reporting requirements.
       The system should include standard reports to meet the
GL49   needs of proprietary funds. (i.e. operating statement,                                                                 NS
       statement of cash flows, statement of net assets, etc.)
       The system should allow for the development of
       customized reports to meet the client's specific reporting
GL50                                                                                                                          NS
       requirements, such as for the CAFR, financial
       statements and State Controller's Report.




                                                                     Page 33 of 169
       The system should provide the ability to record object
       code and debt service principal to facilitate reporting the
GL51                                                                                  NS
       debt at both the fund level and government wide
       financial statements according to GASB 34.

       The system should allow for the creation of comparison
GL52   reports in order to compare one month's balances to                            NS
       another or to compare one year's balances to another.
       The system should allow for reports to be run by
GL53   department, regardless of whether the activity resides in                      NS
       multiple funds
       The system should provide the ability to produce
GL54   graphical representations within reports, including                            NS
       charts, line charts, pie charts and Gantt charts.
       Inquiry and Reporting Average GAP
       Bank Reconciliation Section
       The system should provide a bank reconciliation module
GL55                                                                                  NS
       to automate the import of transactions from the bank.
       The system should provide for automatic matching of
       bank transactions with general ledger transactions
GL56                                                                                  NS
       based on configurable matching rules for more precise
       automatic reconciliation.
       The system should allow manual matching in order to
       enable a user to resolve unreconciled transactions for
GL57                                                                                  NS
       unique situations and override automatic reconciliation
       matching results.
       The system should provide the ability to manually enter
GL58   checks, deposits, etc. (This would typically be used to                        NS
       load data before go live)
       The system should allow the user to re-run
GL59   reconciliations from prior months for corrections or to                        NS
       include auditor adjustments for prior years.
       The system should allow for the assignment of statuses
GL60                                                                                  NS
       to classify the progress of bank reconciliations.




                                                                     Page 34 of 169
       The system should allow for the entry of
GL61   notes/comments in association with unreconciled                             NS
       transactions.
       The system should allow for date sensitive reporting.
       For example, a check issued in January 2011 but not
GL62   cleared until April 2011 should show as outstanding                         NS
       when running January, February and March reports,
       even if the current month is May 2011.
       The system should track check activity dates, such as
GL63   issue date, void date, reversal date, cleared date, stop                    NS
       payment date, escheat date, etc.
       They system should provide the ability to account for
GL64   multiple restricted and unrestricted bank and investment                    NS
       accounts.
       They system should provide the ability to record bank
GL65   information for multiple banks and accounts (i.e.                           NS
       contact, mailing address, e-mail, account number).
       Bank Reconciliation Average GAP
       SLCO Requirements Section
       The system should provide for the differentiation
       between a "soft-close" and a "hard close" based on cost
GL66                                                                               NS
       center/department/fund. The hard close should prevent
       users from posting to previously closed months .
       The system should provide the capability to associate
GL67   new cost center numbers with historic cost center                           NS
       numbers.
       The system should provide the ability to assign a
GL68                                                                               NS
       responsible person to each cost center
       The system should provide the ability to create, delete,
GL69                                                                               NS
       and inactivate cost centers and object codes.
GL70   The system should provide cost accounting functionality                     NS




                                                                  Page 35 of 169
       The system should provide the ability to correct errors
       after the posting process has been completed. The
GL71                                                                                NS
       system must maintain an audit trail for these
       corrections/changes.
       The system should provide the ability to perform screen
GL72                                                                                NS
       prints on request
       The system should be able to create and post
GL73   transactions for subsequent accounting periods before                        NS
       the current accounting period is closed
       The system should provide easy correction of data entry
GL74                                                                                NS
       errors before posting
       The system should provide general instructions on how
GL75                                                                                NS
       to reconcile subsystems to the General Ledger.
       The system should provide the ability to identify the
GL76   unique chart of accounts that was valid during any                           NS
       particular year.
       The system should allow the definition of open periods
GL77                                                                                NS
       in order to control closed periods.
       The system should provide at least 25 accounting code
       elements that can be used to classify transactions (i.e.:
GL78                                                                                NS
       fund, organization, department, object code summary,
       projects/activities,etc.)
       The system should allow for the setup of at least 99,999
       number of funds and other accounting codes of varying
GL79   lengths. (The system should provide an ample length                          NS
       for each accounting structure element/code.).
       Alphanumeric codes should be able to be setup.
       The system should allow accounting elements to be
       setup in a hierarchical scheme. For example, the
GL80                                                                                NS
       system should allow for at least 6 hierarchal elements
       for each chart of account element.
       The system should allow users to obtain a current on-
GL81   line balance on any balance sheet or fund balance                            NS
       account. (similuated close)




                                                                   Page 36 of 169
       The system should be able to support cash, budgetary,
GL82                                                                                  NS
       modified accrual and full accrual accounting.
       The system should allow for user defined levels of cash
GL83                                                                                  NS
       management control.
       The system should provide the ability to enter entries
       (either through the GL subsystem or through the
GL84                                                                                  NS
       encumbrance subsystem) to update the encumbrance
       database directly.
       The system should provide the ability to record capital
       assets in order to facilitate reporting on assets at the
GL85                                                                                  NS
       fund level and book/report on assets on the government-
       wide financial statements according to GASB 34.

       The system should provide the ability to record object
       code and debt service principal to facilitate reporting the
GL86                                                                                  NS
       debt at both the fund level and government wide
       financial statements according to GASB 34.
       The system should track check activity dates, such as
GL87   issue date, void date, reversal date, cleared date, stop                       NS
       payment date, escheat date, etc.
       The system should allow for decentralized entry of
GL88                                                                                  NS
       journal entries.
       The system should allow for additional data to be
GL89   entered into journal entries such as vendor codes,                             NS
       contract numbers etc. and other user defined data.
       The system should be able to import and export journal
GL90                                                                                  NS
       entries from Excel, XML etc
       SLCO Requirements Average GAP
       Total GAP




                                                                     Page 37 of 169
SALT LAKE COUNTY                                                                    INSTRUCTIONS                                               RATING LEGEND
Functional Requirements Matrix                                                                                       SUP   Supported as delivered "out-of-the-box"
                                                                       Complete the worksheet by placing an X in           Supported via modifications (screen configurations, reports, GUI
                                                                          the most appropriate column for each       MOD
                                                                                                                           tailoring, etc)
                                                                         criterion. The X's should represent the
                                                                          current state of a particular product or   3RD   Supported via a third party solution
                                                                      service. (More than one response to a single   CST   Supported via customization (changes to source code)
                                                                           requirement will be treated as a non
                                                                                         response)
                                                                                                                     FUT   Will be supported in a future release
                                                                                                                     NS    Not supported


               PROJECT/ACTIVITY                                                  RATING RESPONSE                                    ADDITIONAL COMMENTS
                                                                       SUP      MOD       3RD      CST      FUT      NS                                                              Resp
 PJ    General Operating Requirements Section
       The system should be fully integrated with the General
 PJ1   Ledger, Purchasing, Grants, Accounts Payable, Work                                                                                                                             NS
       Order, Accounts Receivable/Billing and Payroll modules.
       The system should provide the ability to maintain
 PJ2   payment history by funding source throughout the                                                                                                                               NS
       project life cycle.
       The system should provide the ability to define project
 PJ3   start and close dates. The dates should be able to be                                                                                                                          NS
       changed or left blank if unknown.
       The system should provide the ability to prevent
 PJ4   transactions from being posted to a project when the                                                                                                                           NS
       project is inactive.
       The system should allow access to data in the current
       period, previous periods, future periods, and even
 PJ5                                                                                                                                                                                  NS
       previous years to facilitate reporting and inquiry (with the
       proper security access).
       The system should allow users to set up projects in a
       hierarchical structure which includes the definition of
 PJ6                                                                                                                                                                                  NS
       different project sub-levels (i.e.: project, sub-project,
       work breakdown structure, etc.)


                                                                                                Page 38 of 169
       The system should be able to track and report on
PJ7    project related performance measures, services, and                             NS
       accomplishments.
       The system should be able to track and report on all
PJ8    (multiple) funding sources and/or contracts for each                            NS
       project.
       The system should be able to track and report on all
PJ9    (multiple) projects that are related to a single funding                        NS
       source.
       The system should provide the ability to tie-in project
PJ10   information on construction activities to the Capital                           NS
       Improvement Plan.
       The system should provide the ability to apply changes
PJ11                                                                                   NS
       to unit costs and estimates during the life of the project.
       The system should provide the ability to record and
       maintain an original budget, budget changes, and a
PJ12                                                                                   NS
       revised budget for each project account at each level in
       the project hierarchy structure.
       The system should provide the ability to track staff labor
       data related to projects (e.g. salary, fringe, other direct,
PJ13                                                                                   NS
       premium time, bill rate, billable time, non- billable time,
       multipliers, etc.).
       The system should provide the ability to receive
PJ14   employee time sheet information (from Payroll) by grant                         NS
       or task (type of work) and hours worked.
       The system should provide the ability to track various
PJ15   material items (e.g. charge back rate, multipliers, bill                        NS
       rate, etc.).
       The system should provide the ability to track labor,
PJ16                                                                                   NS
       equipment, and material productivity analysis.
       The system should be able to report the financial status
PJ17                                                                                   NS
       of projects, including all direct costs and allocations.
       The system should accommodate the transfer of funds
PJ18                                                                                   NS
       between projects.




                                                                      Page 39 of 169
       The system should provide a way to prevent inactivation
PJ19   of a project account for which funds are encumbered                              NS
       until the project is closed out.
       The system should provide the ability to develop
       forecasts based on the actual project cost/schedule and
PJ20                                                                                    NS
       generate progress trend analysis reports for quantities,
       amounts, etc.
       The system should provide project management
       capabilities that facilitate workload projections and the
PJ21                                                                                    NS
       allocation of resources, such as the ability to view future
       estimates of work (i.e.: 90-day look ahead).

       The system should provide the ability to define project
PJ22                                                                                    NS
       activity by contractor, consultant and accounting string.

       The system should have the ability to provide a user
PJ23                                                                                    NS
       defined alert if a project related permit is about to expire.
       The system should be able to flag/warn users when
       actual costs against a particular project budget line item
PJ24                                                                                    NS
       are approaching the budget limit. The timing of the
       warning should be user definable.
       The system should provide the ability to support backlog
PJ25   analysis (i.e.: the balance of the project dollar value                          NS
       against the remaining work yet to be completed.)
       The system should allow users to view expenses that
PJ26                                                                                    NS
       have been encumbered but not yet billed.
       The system should allow users to view paid and unpaid
PJ27                                                                                    NS
       invoices.
       The system should provide the ability to allocate
       expenses by fund number, account number, cost
PJ28                                                                                    NS
       center, project number, etc. (including indirect cost
       overhead)
       The system should provide the ability to develop fully
PJ29   burdened labor rates that are related to a specific                              NS
       project before they are allocated.



                                                                       Page 40 of 169
       The system should provide multi-year project budget
PJ30                                                                               NS
       capabilities
       The system should provide the ability to set up default
       mapping rules (for example: the user enters the project
PJ31                                                                               NS
       number and the system automatically defaults to the
       associated GL account coding.)
       The system should be able to interface with other
       Project Management applications, such as Microsoft
PJ32   Project, Expedition, Primavera, etc. (Vendors: please                       NS
       address whether your system has been interfaced with
       Microsoft Project in the past).
       The system should be able to interface with systems like
       MAXIMO (work order system). (Vendors: Please
PJ33                                                                               NS
       indicate whether your system has been interfaced to
       MAXIMO previously.)
       The system should provide the ability to generate
PJ34                                                                               NS
       balance sheet information at the project level.
       The system should provide the ability to process
PJ35                                                                               NS
       inception to date reports/inquiries.
       The system should provide the ability to appropriate
PJ36                                                                               NS
       funds at the project level
       The system should provide the ability to close projects
PJ37   to fixed assets periodically or at the completion of the                    NS
       project or when the asset is substantially complete.
       General Requirements Average GAP
       SLCO Requirements Section
       The system should automatically generate the next
PJ38                                                                               NS
       project number
       The system should have a way to exclude project
PJ39   numbers from all the reports if they have been flagged                      NS
       as "inactive".
       The system should provide the ability to group projects
PJ40   at different levels in order to facilitate reporting and                    NS
       inquiry.




                                                                  Page 41 of 169
       The system should allow for recording other attributes to
PJ41   a project, including demographics, location and other                        NS
       user defined fields.
       The system should maintain appropriate data to
PJ42                                                                                NS
       interface with GIS.
       SLCO Requirements Average GAP
       Total GAP




                                                                   Page 42 of 169
SALT LAKE COUNTY                                                                 INSTRUCTIONS                                               RATING LEGEND
Functional Requirements Matrix                                                                                    SUP   Supported as delivered "out-of-the-box"
                                                                    Complete the worksheet by placing an X in           Supported via modifications (screen configurations, reports, GUI
                                                                       the most appropriate column for each       MOD
                                                                                                                        tailoring, etc)
                                                                      criterion. The X's should represent the
                                                                       current state of a particular product or   3RD   Supported via a third party solution
                                                                   service. (More than one response to a single   CST   Supported via customization (changes to source code)
                                                                        requirement will be treated as a non
                                                                                      response)
                                                                                                                  FUT   Will be supported in a future release
                                                                                                                  NS    Not supported


            GRANTS ACCOUNTING                                                 RATING RESPONSE                                    ADDITIONAL COMMENTS
                                                                    SUP      MOD       3RD      CST      FUT      NS                                                              Resp
 GA    General Operating Requirements Section
       The system should integrate with Project Accounting,
       General Ledger, Budget, Accounts Receivable,
GA1                                                                                                                                                                                NS
       Purchasing, Billing, Accounts Payable, Payroll, Fixed
       Assets and Cash Receipts.
       The system should provide the ability to distribute grant
GA2                                                                                                                                                                                NS
       applications to the review board for electronic approval.
       The system should provide the ability to support grant
GA3    fiscal year closing independent of the fiscal year of the                                                                                                                   NS
       organization
       The system should provide the ability to inactivate
       accounts upon closure of a grant while maintaining all
       historical activity associated with the grant. The
GA4    accounts should not allow posting beyond the inactive                                                                                                                       NS
       date. (The inactive date may differ from the end date in
       order to allow additional time for closing entries to be
       posted).
       The system should provide the ability to bring forward
GA5                                                                                                                                                                                NS
       fiscal year end balances for multi-year grants.




                                                                                             Page 43 of 169
           The system should provide the ability to produce AP
GA6                                                                                      NS
           vouchers for payments to sub recipients
           The system should provide the ability to produce
           automated notifications based on expenditures,
GA7        encumbrances, and commitments based on user-                                  NS
           defined criteria (e.g., match exhausted, 90%
           expended, etc).
           The system should provide the ability to create a tickler
           file notice of dates for performance reviews, submission
GA8                                                                                      NS
           of reports, etc.and flag/report exceptions to events that
           are not accomplished on time.
           For projects that are funded by multiple grants, the
GA9        system should provide user-defined prioritization for the                     NS
           utilization of funds.
           The system should provide the ability to transfer
GA10                                                                                     NS
           expenditure amounts between phases.
           The system should enable multiple contract types per
GA11       phase. (for example, types may include professional                           NS
           services, construction, construction management, etc)
         The system should allow for the transfer of excess
GA12                                                                                     NS
         phase/project funds back to the funding agency.
         The system should provide the ability to capture eligible
GA13
         and ineligible costs by:
GA13   1 Task/Activity                                                                   NS
GA13   2 Program                                                                         NS
GA13   3 Other user-defined tracking                                                     NS
         The system should have the ability to perform
GA14
         automated allocations including:
           The system should provide the ability to allocate indirect
GA14   1                                                                                 NS
           salaries and fringe benefits to the applicable grants.
           The system should provide the ability to apply more than
GA14   2                                                                                 NS
           one indirect cost allocation per grant.




                                                                        Page 44 of 169
         The system should provide the ability to automatically
         create accounting entries at user-defined intervals for
GA14   3                                                                                NS
         the recognition of indirect cost recoveries or matching
         fund information.
           The system should provide the ability to maintain grants
GA15                                                                                    NS
           that affect multiple departments/programs and/or funds.
           The system should allow for multiple grants/funding
GA16                                                                                    NS
           sources for a single program.
           The system should provide the ability to receive
GA17       employee time sheet information (from Payroll) by grant                      NS
           or task (type of work) and hours worked.
           The system should automatically adjust grant
GA18                                                                                    NS
           expenditures accordingly for any Payroll adjustments.

           The system should provide the ability to copy existing
GA19                                                                                    NS
           grants to establish templates for new grants.
           The system should provide the ability to calculate the
GA20
           timing of draw downs based on:
GA20   1   Level of expenditures                                                        NS
GA20   2   Grant requirements                                                           NS
GA20   3    User-Defined criteria                                                       NS
           The system should provide the ability to record project
GA21                                                                                    NS
           performance information.
           The system should provide the ability to allow authorized
           managers to access, inquire, report and reconcile the
GA22
           status of grants and all other funding sources on the
           following information:
GA22   1   Drawdowns                                                                    NS
GA22   2   Obligations                                                                  NS
GA22   3   Encumbrances                                                                 NS
GA22   4   Expenditures                                                                 NS
           The system should provide the ability to track the
GA23
           following information for each grant related activity:
GA23   1   Grant number                                                                 NS
GA23   2   Account code                                                                 NS



                                                                       Page 45 of 169
GA23 3 CFDA number                                                                   NS
GA23 4 Funding agency                                                                NS
GA23 5 Name of program                                                               NS
GA23 6 Type of funding agency (federal, state, local, etc.)                          NS
GA23 7 Award amount                                                                  NS
GA23 8 PO number                                                                     NS
GA23 9 Vendor name                                                                   NS
GA23 10 Invoice number                                                               NS
GA23 11 Check number                                                                 NS
        The system should be able to track and manage the
GA24
        following:
GA24 1 Grants in progress                                                            NS
GA24 2 Report due dates                                                              NS
GA24 3 Grant eligibility                                                             NS
GA24 4 Grant proposal                                                                NS
GA24 5 Multiple grant approval phases                                                NS
GA24 6 Reimbursements                                                                NS
GA24 7 Sub recipient contracts                                                       NS
GA24 8 Grant ending date                                                             NS
GA24 9 In-kind transactions                                                          NS
GA24 10 Application date                                                             NS
GA24 11 Encumbrances                                                                 NS
GA24 12 Percent match                                                                NS
GA24 13 Monetary versus in-kind contributions                                        NS
GA24 14 Specific accounts of matching funds                                          NS
GA24 15 Status of matched funds                                                      NS
        The system should allow for the attachment of images
GA25                                                                                 NS
        or source documents to grant records.
        The system should provide the ability to record grant
GA26    contracts with sub recipient requirements to specific                        NS
        grants and/or sub grants.
        General Operating Requirements Average GAP
        Communication with Funding Agencies
        Requirements Section
          The system should provide the ability to electronically
GA27                                                                                 NS
          submit grant applications to external funding sources




                                                                    Page 46 of 169
           The system should provide the ability to automate the
           preparation of billing statements and other associated
GA28       documents to any of the federal and/or local units,                          NS
           regardless of the billing arrangements and participation
           agreements (e.g., project reimbursement)
           The system should provide the ability to send project
GA29
           billing information electronically to:
GA29   1   Federal grantors                                                             NS
GA29   2   State grantors                                                               NS
GA29   3   Local Offices                                                                NS
GA29   4   Other                                                                        NS
           The system should provide the ability to accept grant
GA30       reimbursements from wire transfers received from                             NS
           grantor agencies.
           The system should provide the ability to electronically
GA31       transmit grant progress reports based on user defined                        NS
           intervals.
           Communication with Funding Agencies
           Requirements Average GAP
           System Setup Requirements Section
           The system should provide the ability to establish and
GA32                                                                                    NS
           adjust budgets for each grant or project.
           The system should provide the ability to set-up
           grants/projects by phase or other sublevel to enable
GA33                                                                                    NS
           tracking by participating departments, divisions or any
           other user defined organization units.
           The system should provide the ability to track
GA34                                                                                    NS
           MBE/WBE/DBE requirements and related compliances.

           The system should allow for the establishment of
           allowed costs for each grant based on activity or other
GA35       user defined parameter. The system should then                               NS
           automatically disallow unauthorized costs either in total
           or partial, along with reason for disallowance.




                                                                       Page 47 of 169
           The system should provide the ability to apply new
GA36                                                                                      NS
           reimbursement rules to a grant.
           System Setup Requirements Average GAP
           Reporting Requirements Section
           The system should provide the ability to track and report
GA37       current performance against past performance and/or                            NS
           established goals.
           The system should provide the ability to roll-up grants to
GA38       higher levels, such as grantor agency or CFDA number                           NS
           for internal and external reporting.
           The system should be able to report the following
           information over any user defined reporting period (state
GA39       reporting period, federal reporting period, grant year,                        NS
           fiscal year, inception to date, breakdowns by period,
           etc.)
GA39   1   Expenditures                                                                   NS
GA39   2   Revenues                                                                       NS
GA39   3   Encumbrances                                                                   NS
GA39   4   Billings                                                                       NS
GA39   5   Payments                                                                       NS
GA39   6   Balances                                                                       NS
           The system should be able to generate standard federal
GA40                                                                                      NS
           reports (including The Single Audit Report).
           The system should be able to generate the Schedule of
GA41       Federal Financial Assistance Award (Total federal                              NS
           expenditures with corresponding CFDA #).
           The system should provide the ability to generate a
GA42       grant transaction history report (reflecting ALL activity                      NS
           for each grant).
           The system should provide the ability to generate
GA43       program history reports or inquiries, showing funds                            NS
           budgeted and expended by a date range.
           The system should provide the ability to generate the
GA44       following reports for individual grants, as well as for all
           grants:
GA44   1   Trial balance                                                                  NS
GA44   2   Year end and interim financial statements                                      NS



                                                                         Page 48 of 169
         The system should provide the ability to create the
GA45                                                                                  NS
         Quarterly Expenditure Reports for Federal Grants
         Reporting Requirements Average GAP
         SLCO Requirements Section
         The system should provide the ability to apply budgetary
         restraints (revenue and/or expenditures) which have
GA46                                                                                  NS
         been either established by the legislature or
         administrative directive.
         The system should provide the ability to compare
GA47                                                                                  NS
         current costs to budgeted costs.
         The system should provide the ability to maintain
GA48     transaction listing of all budget changes including date                     NS
         and source.
         The system should provide the ability to modify line item
GA49                                                                                  NS
         amounts within user-defined parameters.
         The system should provide the ability for analyses and
GA50     forecasting of expenditures/revenues based on most                           NS
         recent fiscal activities, or user-defined time periods.
         The system should allow the recording of revenues to
GA51
         one or more phases by:
GA51   1 Percentage of billings                                                       NS
GA51   2 Percentage of participating dollars                                          NS
GA51   3 User defined option                                                          NS
         The system should provide the ability to archive closed
GA52     grants/projects with no activity beyond a user defined                       NS
         time interval.
         The system should provide the ability to modify grant
GA53                                                                                  NS
         data prior to carryover.
         The system should provide the ability to reference grant
GA54                                                                                  NS
         authorizing resolutions.
         The system should provide the ability to establish
         appropriate approval processes for grant fund
GA55     commitment through the requisition process with not-to-                      NS
         exceed approved budget levels by
         department/Project/PO.




                                                                     Page 49 of 169
       The system should provide the ability to record grant
       encumbrances and subsequent payments against
GA56                                                                                 NS
       existing encumbrance so that available funding
       calculations can be generated.
       The system should be able to record expenditure by
GA57                                                                                 NS
       phase.
       The system should provide the ability to track grant
GA58   terms and balances from starting date to completion of                        NS
       audit and/or user-defined completion date.
       The system should provide the ability to input costs for a
GA59                                                                                 NS
       project submitted by sub recipients
       The system should integrate with the Accounts
GA60   Receivable module including edits to prevent double                           NS
       billing transactions.
       The system should allow users to re-open previously
GA61                                                                                 NS
       closed grants.
       The system should provide the ability to review online
GA62                                                                                 NS
       summary of all financial information by grant.
       The system should be able to generate reports showing
GA63                                                                                 NS
       grantor status and updates.
GA64   The system should provide grant titles in all reports.                        NS
       The system should provide the ability to denote if grants
GA65                                                                                 NS
       are for multiple years.
       The system should provide the ability to consolidate
GA66   grant, budget, and grant expense information on a                             NS
       project and department basis.
       The system should provide the ability to provide cost
       accounting information to calculate IDC rates and
GA67                                                                                 NS
       provide internal service billings between supporting
       departments and the grant/project.
       The system should automatically generate the next
GA68                                                                                 NS
       grant number
       The system should provide the ability to exclude grant
GA69   numbers from all the reports if they have been flagged                        NS
       as "inactive".




                                                                    Page 50 of 169
       The system should provide the ability to set up default
       mapping rules (for example: the user enters the grant
GA70                                                                              NS
       number and the system would automatically default to
       the associated GL account coding.)
       The system should allow for multiple revenue sources
GA71                                                                              NS
       for a single grant.
       The system should provide the ability to track the DUNN
GA72                                                                              NS
       number for each grant related activity.
       SLCO Requirements Average GAP
       Total GAP




                                                                 Page 51 of 169
SALT LAKE COUNTY                                                                 INSTRUCTIONS                                               RATING LEGEND
Functional Requirements Matrix                                                                                    SUP   Supported as delivered "out-of-the-box"
                                                                    Complete the worksheet by placing an X in           Supported via modifications (screen configurations, reports, GUI
                                                                       the most appropriate column for each       MOD
                                                                                                                        tailoring, etc)
                                                                      criterion. The X's should represent the
                                                                       current state of a particular product or   3RD   Supported via a third party solution
                                                                   service. (More than one response to a single   CST   Supported via customization (changes to source code)
                                                                        requirement will be treated as a non
                                                                                      response)
                                                                                                                  FUT   Will be supported in a future release
                                                                                                                  NS    Not supported


         PURCHASING MANAGEMENT                                                RATING RESPONSE                                    ADDITIONAL COMMENTS
                                                                    SUP      MOD       3RD      CST      FUT      NS                                                              Resp
 PR      General Operating Requirements Section
         The system should integrate with the General Ledger,
         Accounts Payable, Encumbrance, Inventory, Project
 PR1                                                                                                                                                                               NS
         Ledger, Fixed Assets, Contracts, and possibly the
         Grants module.
         The system should have the ability to perform real-time
 PR2                                                                                                                                                                               NS
         budget checking during the creating of a requisition.
         The system should have the ability to perform real-time
 PR3     budget checking during the creating of a purchase                                                                                                                         NS
         order.
         The system should prevent the assignment of a
 PR4     purchase order number before the purchase requisition                                                                                                                     NS
         has been approved.
         The system should have the ability to establish the
 PR5
         following for blanket purchase orders:
         A not-to-exceed amount on the entire blanket purchase
 PR5   1                                                                                                                                                                           NS
         order
         A not-to-exceed amount on each release/requisition
 PR5   2                                                                                                                                                                           NS
         against a blanket order (per occurance)
 PR5   3 An expiration date                                                                                                                                                        NS




                                                                                             Page 52 of 169
       The system should allow for the attachment of images
PR6    or source documents to the purchase order. (either as                       NS
       an attached image or a URL)
       The system should have the ability to automatically
PR7    encumber funds during the requisition process. (pre-                        NS
       encumbrance)
       The system should have the ability to automatically
PR8                                                                                NS
       encumber funds during the purchase order process.
       The system should provide the ability to automatically
       adjust encumbrance balances when a change order or
PR9                                                                                NS
       other adjustment affects account coding or line
       amounts.
       The system should provide full encumbrance
       capabilities. For blanket purchase orders, the system
PR10                                                                               NS
       should allow the users to encumber releases against the
       blanket
       The system should provide the ability to close unused
PR11   encumbrances easily and adjust the budget balances                          NS
       accordingly .
       The system should provide different options for carrying
       over open encumbrances at year end. One example is
PR12   for the organization to create another budget version in                    NS
       the ensuing year that is separate and apart from the
       Operating Budget.
       The system should provide an on-screen display of the
PR13                                                                               NS
       running PR/PO total as line items are entered.
       The system should be able to generate a list of vendors
PR14   based on commodity codes. (first five digits of NIGP                        NS
       codes)
       The system should provide the ability to combine
PR15                                                                               NS
       several requisitions into one purchase order
       The system should have the ability to automatically
PR16   notify the Purchasing Department of approved                                NS
       requisitions that are ready to be processed.
       The system should have the ability to track buyer
PR17   workload and be able to display outstanding requisitions                    NS
       by buyer.



                                                                  Page 53 of 169
       The system should provide the ability to create
       notes/extended descriptions at the line item level with
PR18   word wrap capabilities. Formatting should be carried                          NS
       over when copy/paste used from standard word
       processing or spreadsheet software
       The system should allow for the creation of notes
       (pertaining to the PO as a whole) to document any
       pertinent conversations between the buyer and the
       vendor or any other pertinent conversations. This note
       section should be time stamped and should have
PR19                                                                                 NS
       security features. The notes should have the option of
       being labeled as internal or external (to print on the PO)
       User should be able to print part, all, or none of the
       attached notes, and all users should have the ability to
       search the notes
       The system should have the ability to generate single or
PR20                                                                                 NS
       multi-page purchase orders
       The system should allow numerous line items to be
PR21   charged to a single account and a single line item to be                      NS
       charged to multiple accounts.
       The system should provide for the creation of multiple
       seed numbers to enable different numbering
       conventions to be used during the creation of purchase
PR22                                                                                 NS
       requisitions and purchase orders. The seed number
       system should disallow multiple uses of the same
       number, for example NA1143C and NA1143G.
       The system should allow authorized users to cancel
PR23                                                                                 NS
       purchase orders
       The system should provide the ability to update and
       change the PO with appropriate security. (even after a
PR24   partial payment has been made) This option should                             NS
       only be available in current years, and all changes
       should be tracked




                                                                    Page 54 of 169
       The system should be able to track an audit trail of all
       changes to a purchase order including the user, date,
PR25                                                                                  NS
       time and what the value was before the change and
       after the change.
       The system should automatically close a purchase order
PR26   and all associated encumbrances when a final payment                           NS
       is issued by authorized Accounts Payable users.
       The system should provide a simple order request
       webform that simplifies entry for decentralized
PR27                                                                                  NS
       departments. The request should automatically create a
       purchase requisition in the system.
       The system should be able to track freight charges and
PR28                                                                                  NS
       to define freight routing options.
       The system should allow the creator of the requisition to
PR29   edit the requisition document up until the point it has                        NS
       received any approvals.
       The system should allow for approval overrides so that
PR30   authorized users can print the purchase order                                  NS
       immediately.
       The system should be able to show the status of
       purchase requisitions/purchase orders to reflect whether
PR31                                                                                  NS
       the document has been approved, printed, received,
       and/or paid.
       The system should maintain an audit trail of all approval
       activities related to a requisition. This includes the
       approver's name, the date of activity, whether the
PR32                                                                                  NS
       approver made changes to the requisition, and whether
       the approver rejected, approved or forwarded the
       requisition.
       The system should be able to report on the number of
       outstanding requisitions and purchase orders. This
PR33                                                                                  NS
       report should be able to be sorted via any standard
       criteria; division, department, creator, buyer, vendor, etc




                                                                     Page 55 of 169
       The system should have the ability to automatically
PR34   update the fixed asset or controlled asset module when                      NS
       payment information is entered.
       The system should have the ability to interface with bar
PR35                                                                               NS
       coding inventory systems.
       The system should provide an unlimited number of line
PR36                                                                               NS
       items for each Requisition and Purchase Order
       The system should track the flow of information for the
PR37   entire life cycle of procurement. (i.e.: requisition-to-                    NS
       payment.)
       The system should have the ability to import
       procurement card information from the procurement
PR38                                                                               NS
       card provider. The imported information should be
       searchable
       The system should provide the ability to electronically
PR39                                                                               NS
       transmit purchase orders to vendors.
       The system should have the capability to link the
PR40   requisition to a work order system (by work order                           NS
       number).
       The system should have the capability to link the
PR41                                                                               NS
       requisition to a Fleet Management System.
       General Operating Requirements Average GAP
       Vendor Related Requirements Section
       The system should allow for the maintenance of multiple
PR42                                                                               NS
       addresses for each vendor.
       The system should allow vendor "numbers" to be setup
PR43                                                                               NS
       as alphanumeric.
       The system should have the ability to create a "to be
PR44   determined" vendor for purchase requests where the                          NS
       initiator does not know the vendor to be selected.
       Users should have access to the vendor file while in the
       Requisition screen, allowing them the ability to look up
PR45   vendor information such as address, fax, email, and                         NS
       phone number. Personal identifiers must be kept
       confidential




                                                                  Page 56 of 169
       The system should have the ability to record vendor
       responses to bids and create a Purchase Order if the
PR46   quote is awarded to the vendor. The system should                               NS
       allow a historical report to research a specifc vendors'
       bid/ result history
       The system should provide the ability to track why a
PR47                                                                                   NS
       vendor was not selected (high price, inferior quality, etc.)
       The system should provide designation codes to identify
PR48   characteristics for a vendor (such as bad quality vendor,                       NS
       DBE, MBE, WBE, etc.)
       The system should allow authorized users to select
       active vendors after a user specified period of inactivity
PR49   and change the status to inactive. This should be able                          NS
       to be performed as a mass update with the ability to run
       a trial run.
       The system should allow a change of address history
PR50                                                                                   NS
       report
       The system should provide the ability to automatically
       merge two vendors and update all related activity for
PR51   and associated history for the merged vendor (based on                          NS
       user security). A complete audit trail should be
       maintained for this action.
       The system should have the capability to load the most
       current United States Postal Service zip code table to
       the database. The system should automatically fill in
PR52   City Name, State and country based upon the zip code                            NS
       entered. If a user manually enters a the city, state,
       country, the system should verify the entry for accuracy
       against the zip code table.
       Vendor Related Requirements Average GAP
       Vendor Self Service Section
       The system should provide online vendor self-service
PR53   abilities with an easy-to-use, secure online process with
       the following capabilities:




                                                                      Page 57 of 169
           Ability for vendors to update/maintain contact
PR53   1                                                                              NS
           information and inquire on invoices and payment status.
         Provide an easy-to-use way for vendors to select and
PR53   2                                                                              NS
         assign their commodity codes during registration.
         Provide on-line notification of forgotten user ID's and
PR53   3                                                                              NS
         passwords to vendors.
           Provide the ability for vendors to attach/submit
PR53   4                                                                              NS
           documents online (such as W-9 forms, invoices, etc.)
         Provide the ability for vendors to enter their
PR53   5                                                                              NS
         banking/ACH information on-line.
PR53   6 Automatic notification of payment to the vendor.                             NS
         Allow for the customization of on-line help screens for
PR53   7                                                                              NS
         vendor registration.
           Provide vendors the ability to download Client provided
PR53   8                                                                              NS
           forms and bid specifications over the internet.
         The system should generate an automated notification
         to the ordering department when the receiving
PR54                                                                                  NS
         department enters returns or backordered items into the
         system.
         Provide the ability to place self-service updates in a
PR55     holding file for approval and post updates once                              NS
         approved.
         Allow customization of the on-line vendor registration
PR56                                                                                  NS
         screens/process.
         The system should accommodate a vendor view of
PR57
         invoice status including:
PR57   1 Payment status. (user defined)                                               NS
PR57   2 Payment amount.                                                              NS
         Check number and issue date if check has been issued,
PR57   3                                                                              NS
         or EFT confirmation information.
         Vendor Self Service Average GAP
         Receiving Related Requirements Section




                                                                     Page 58 of 169
       The system should allow for either centralized or
PR58   decentralized (end-user) processing of receipts for                           NS
       goods and services.
       The system should provide the ability to maintain
       historical information of receiving, including receiver
PR59                                                                                 NS
       name, date of receipt, and quantities received, returned,
       damaged, etc
       The system should prevent AP from making a payment
PR60   on an invoice if receiving has not taken place for the                        NS
       invoiced items.
       The system should provide the ability to track the
PR61                                                                                 NS
       anticipated delivery date and the actual receiving date
       The system should provide real time purchasing reports
PR62   showing original goods requested versus actual goods                          NS
       received.
       The system should provide a Vendor Shipping
       Performance Report that includes due dates for
PR63                                                                                 NS
       delivery, actual dates of delivery, accuracy of shipments,
       etc.
       Receiving Related Requirements Average GAP
       Reporting Requirements Section
       The system should track purchase releases and
PR64   payments issued against blanket orders in order to                            NS
       report on the remaining amount.
       The system should have a standard report to reconcile
PR65                                                                                 NS
       purchase order totals to encumbrance totals

       The system should allow for the setup of a commodity
PR66                                                                                 NS
       database that can sort by class or description.
       The system should allow the design of customized
       forms, including Request for Quote, Purchase Request
PR67                                                                                 NS
       Purchase Order, Sole Source, and Emergency
       Purchase.




                                                                    Page 59 of 169
           The system should provide the capability for users to
           inquire and report on where a requisition is in the
           approval process and how long it has been waiting for
PR68                                                                                  NS
           approval from that approver. (System should take into
           account standard non-work days, such as weekends
           and holiday)
           The system should be able to report on vendor history
PR69                                                                                  NS
           and provide activity analysis
           The system should provide complete reporting and
           inquiry of purchase orders with order, receipt and
PR70       payment information. (Basis of such reporting should be                    NS
           user defined, such as vendor, division, department,
           object code, req creator, etc.)
           The system should be able to generate reports on stale
PR71                                                                                  NS
           dated requisitions and purchase orders.
           The system should be able to report and inquire on
PR72
           purchasing activities by:
PR72   1   vendor name and ID                                                         NS
           account number or partial account number, such as
PR72   2                                                                              NS
           object or activity
PR72   3   buyer                                                                      NS
PR72   4   date                                                                       NS
PR72   5   initiator/creator                                                          NS
PR72   6   ordering department                                                        NS
PR72   7   purchase order number                                                      NS
PR72   8   commodity                                                                  NS
           Reporting Requirements Average GAP
           SLCO Requirements Section
           The system should provide warnings to prevent
           duplicate requisition and purchase order numbers. The
PR73       seed number system should be able to disallow multiple                     NS
           uses of the same number, for example NA1143C and
           NA1143G.
           The system should display an error message when an
           inactive or erroneous cost center, account number,
PR74                                                                                  NS
           vendor ID or other field is populated with incorrect
           information.



                                                                     Page 60 of 169
       The system should have the ability to override system
PR75   generated purchase requisition and purchase order                            NS
       create dates.
       The system should automatically populate the "entered
PR76   by" when the data entry staff logs on to the system to                       NS
       enter a new PR.
       The system should have the ability to generate bid
PR77   tabulations, store bid prices, and quantify bid data for                     NS
       historic comparison purposes.
       The system should have the ability to track items that
PR78                                                                                NS
       are currently out for bid.
       The system should have the ability to provide savings
PR79                                                                                NS
       breakdowns on bids and quotes.
       The system should provide a tracking system that can
PR80   target bidders' performance, including vendors who                           NS
       consistently do not bid.
       The system should provide commodity selection by
PR81                                                                                NS
       commodity number or by name.
       The system should have the ability to split a requisition
PR82                                                                                NS
       into multiple purchase orders
       The system should automatically calculate the extended
PR83                                                                                NS
       price (units x unit cost).
       The system should track the name and of the requisition
PR84                                                                                NS
       initiator
       The system should provide for the automatic
PR85                                                                                NS
       assignment of purchase order number.
       The system should have the ability to manually enter
PR86                                                                                NS
       purchase order numbers.
       The system should have the ability to override purchase
PR87                                                                                NS
       order numbers.
       The system should track discounts offered by vendor
PR88   with automatic notification as items are requisitioned                       NS
       from those vendors.
       The system should allow buyers to override either user-
PR89                                                                                NS
       specified or system generated vendors and prices.




                                                                   Page 61 of 169
           The system should provide a field for the delivery
PR90                                                                                     NS
           location on a purchase order.
           The system should prevent receiving until purchase
PR91       orders have been completed and printed by the                                 NS
           Purchasing Department
           The system should provide for on-screen inquiries of
PR92                                                                                     NS
           requisition/purchase order information.
           The system should provide on-line access to open bids,
PR93       bid tabs, award tabs, preferred vendors, contract terms,                      NS
           etc
           The system should enable departments to perform on-
PR94       line inquiries to check the status of quotes, requisitions                    NS
           and purchase orders
PR95       The system should run year to date reports for vendors                        NS
           At a minimum, detailed transaction reports should
PR96
           include the following:
PR96 1      cost center number and description                                           NS
PR96 2      vendor number and name                                                       NS
PR96 3      account number and description                                               NS
PR96 4      check number                                                                 NS
PR96 5      purchase order/contract number                                               NS
PR96 6      requisition number                                                           NS
PR96 7      status                                                                       NS
PR96 8      check date                                                                   NS
PR96 9      invoice number                                                               NS
PR96 10     invoice date                                                                 NS
PR96 11     paid amount                                                                  NS
           The system should provide an encumbrance report with
PR97       flexible selection criteria. At a minimum, the users
           should be able to select by:
PR97   1    date range (not just end date)                                               NS
PR97   2    vendor name                                                                  NS
PR97   3    vendor ID                                                                    NS
PR97   4    requisition number                                                           NS
PR97   5    purchase order/contract/blanket number                                       NS
PR97   6    dollar amount                                                                NS



                                                                        Page 62 of 169
PR97    7 status (purchasing stage)                                                    NS
PR97    8 buyer name with phone extension                                              NS
PR97    9 cost center/department                                                       NS
          The system should allow individuals (based on security)
PR98                                                                                   NS
          to update "remit to" address when necessary.
          The system should provide the ability to print the DBA
PR99      name on the purchase order, not just the name of the                         NS
          individual.
PR100     The system should provide e-procurement capabilities.                        NS

          The system should have the ability to send (hard copy or
PR101                                                                                  NS
          electronic format) quote solicitation letters to vendors

          The system should provide the ability to attach
PR102     management reports that provide information regarding                        NS
          how vendors were rated across numerous RFQ's.

          The system should provide the ability to identify vendors
PR103                                                                                  NS
          who have won bids and the activity for those bids.
          The system should maintain an easy-to-use master
PR104     vendor file, including vendor information and types of                       NS
          commodity/service they can bid on.
          The system should provide the ability to set up preferred
          vendors for specific products and have the system
PR105                                                                                  NS
          display or populate the fields along with the pricing
          information.
          The system should allow multiple users to view the
PR106                                                                                  NS
          same vendor simultaneously.
PR107     The system should provide receiving reports                                  NS
          The system should provide the ability for (authorized)
PR108     users to process simple, routine purchases without                           NS
          involving a buyer
          The system should allow vendors to submit their bids on-
PR109                                                                                  NS
          line




                                                                      Page 63 of 169
        The system should enable the user of NIGP commodity
        codes. Use first five digits of NIGP codes and NIGP
PR110   database should be searchable by any term or by                               NS
        common synonym. For example: pesticide, bug spray,
        insect control, etc.
        The system should provide the ability to post/release
PR111                                                                                 NS
        bids on-line and include attachment documents/images.
        The system should have the ability to create solictiations
PR112   such as RFB's, RFC's, RFP's, RFQ's, PO's, Contracts,                          NS
        and Blanket Orders.
        The system should allow (authorized) users to change a
PR113                                                                                 NS
        vendor number/id.
        The system should have the ability to include both
PR114   encumbered and non-encumbered line items on the                               NS
        same PO
        SLCO Requirements Average GAP
        Total GAP

        5250
        2625




                                                                     Page 64 of 169
SALT LAKE COUNTY                                                                INSTRUCTIONS                                               RATING LEGEND
Functional Requirements Matrix                                                                                   SUP   Supported as delivered "out-of-the-box"
                                                                   Complete the worksheet by placing an X in           Supported via modifications (screen configurations, reports, GUI
                                                                      the most appropriate column for each       MOD
                                                                                                                       tailoring, etc)
                                                                     criterion. The X's should represent the
                                                                      current state of a particular product or   3RD   Supported via a third party solution
                                                                  service. (More than one response to a single   CST   Supported via customization (changes to source code)
                                                                       requirement will be treated as a non
                                                                                     response)
                                                                                                                 FUT   Will be supported in a future release
                                                                                                                 NS    Not supported


           BUDGET MANAGEMENT                                                 RATING RESPONSE                                    ADDITIONAL COMMENTS
                                                                   SUP      MOD       3RD      CST      FUT      NS                                                              Resp
 BM    General Operating Requirements Section
       The system should integrate with Human Resources
       (Position Control), Payroll, General Ledger, Purchasing,
BM1                                                                                                                                                                               NS
       Grant Management, Project Accounting and other
       applicable subsystems.
       The system should provide the ability to keep multiple
BM2                                                                                                                                                                               NS
       budget years open at the same time.
       The system should allow for inquiry and reporting on
BM3    budget data for any number of past, present, and future                                                                                                                    NS
       years.
       The system should provide the ability to make mass
BM4                                                                                                                                                                               NS
       adjustments to multiple budget line items at once.
       The system should provide the ability to make dollar and
BM5    percentage adjustments by budget line item or line item                                                                                                                    NS
       group and sustain audit trails for all changes..
       The system should provide the ability to allocate
BM6    overhead and administration costs to departments, cost                                                                                                                     NS
       centers, programs, sub-program, etc.
       The system should allow for the transfer of funds
BM7                                                                                                                                                                               NS
       between budgeted line items.




                                                                                            Page 65 of 169
           The system should be able to assign unique identifiers
BM8                                                                                     NS
           for budget transfers.
           The system should allow the same employee to be
BM9                                                                                     NS
           budgeted to multiple account codes
           The system should allow users to view current year- to-
BM10       date or a user defined range of actual hours by                              NS
           employee as a basis to prepare the upcoming budget.
         The system should allow for budget based projections,
BM11
         including:
         The ability to compute "what if" scenarios using user
BM11   1                                                                                NS
         defined calculations.
         The ability to perform a variety of revenue, expenditure,
BM11   2 and fund balance forecasting including the ability to                          NS
         perform fee analysis.
         Allow forecasts to be calculated in terms of percentage
BM11   3 increases or decreases (either globally or for specific                        NS
         departments, funding sources or other units).

           Allow salary and benefits projections based on user
BM11   4                                                                                NS
           defined parameters (fixed cost, percentage, lump sum).

           The system should provide users the ability to enter
BM12                                                                                    NS
           budget requests (modifications, transfers,etc.) on-line.
           The system should support a linear budget process
BM13       (data segregation by stage, ability to multipost data                        NS
           across budget stages, security control by stage).
           The system should provide the ability to create, maintain
BM14                                                                                    NS
           and compare multiple budget versions
           The system should allow users to download or upload
BM15                                                                                    NS
           budgets from desk-top applications
           The system should allow budgets to be copied forward
BM16                                                                                    NS
           from the current budget.
           The system should allow budgets to be copied forward
BM17                                                                                    NS
           from the last 12 months actual.




                                                                       Page 66 of 169
           The system should provide a mechanism for lapsing the
           operating budget at year-end while allowing CIP for the
BM18                                                                                      NS
           same year and other continuing budget amounts to roll
           forward.
           The system should provide the ability to automatically
BM19       identify accounts that meet the criteria for being carried                     NS
           forward to the next fiscal period.
           The system should provide the ability to tie performance
BM20       data to any level of detail (e.g.: organization, program or                    NS
           division rollup).
           The system should provide the ability to track original
BM21                                                                                      NS
           and amended budgeted amounts by line item.
           General Operating Requirements Average GAP
           Budget Reporting Requirements Section
           The system should allow users to view the detail
BM22       charges of actual spending or encumbrance amounts                              NS
           against the budget.
           The system should provide the ability to create the final
BM23                                                                                      NS
           budget document in its finished form.
           The system should provide a report that lists information
BM24       for employees including position and hourly rate by                            NS
           account number with flexible subtotaling capabilities.
           The system should provide a complete encumbrance
BM25                                                                                      NS
           transaction history report.
           The system should provide standard and customized
BM26       budget reports. At a minimum, the standard reporting
           should provide the ability to:
           Run reports based on date range (user defined, fiscal
BM26   1                                                                                  NS
           year, etc)
           Develop exception reports or criteria-driven reports (e.g.
BM26   2                                                                                  NS
           accounts that are 75% expended at mid-year).
BM26   3   Drill down to the lowest level.                                                NS
BM26   4   Drill down to a supporting scanned document.                                   NS




                                                                         Page 67 of 169
         Run variance reports to compare actual expenditures
BM26   5 and encumbered amounts against the respective                                    NS
         budgets for at least a five year period.
         Develop other customized management and budget
BM26   6                                                                                  NS
         reports based any budget data field.
           Develop statistical budget information to allow research
BM26   7                                                                                  NS
           and analysis (including performance measurements).
BM26   8 Include charts and other graphical information.                                  NS
         Compare prior year to current year budget to actual
BM26   9                                                                                  NS
         comparisons
         Budget Reporting Requirements Average GAP
         Budget Devaelopment & Preparation Requirements
         Section
         The system should provide a flexible way of preparing
         budget details that is not restricted to the attributes of
BM27     the chart of accounts. (The ability to budget at lower or                        NS
         more detailed levels than the chart of accounts allows
         for)
           The system should provide the ability to budget related
BM28                                                                                      NS
           revenues and expenditures at the program level.
           The system should provide the ability to develop multi-
BM29       year and inception to date project budgets according to                        NS
           user-defined parameters.
           The system should provide the ability to budget by
           position. It should have the ability to handle approved
           agreements by bargaining unit and estimated increases,
BM30                                                                                      NS
           salary and step pay plans. The system should provide
           the ability to view different job classifications and their
           corresponding pay ranges and steps.
           The system should be able to track salary commitments
BM31                                                                                      NS
           and payroll expenditures by position.




                                                                         Page 68 of 169
         The system should provide the ability to automatically
         calculate an hourly rate by the number of estimated
BM32                                                                                 NS
         annual hours in order to produce a budget for each
         employee.
         The system should provide the ability to accommodate
BM33                                                                                 NS
         project contingency line items in budgets.
         The system should provide Performance-based
BM34                                                                                 NS
         Budgeting.
         The system should allow users the ability to create a
BM35     budget "worksheet" to facilitate the budget preparation                     NS
         process.
         The system should provide the ability to develop
BM36                                                                                 NS
         monthly and quarterly budgets.
         The system should provide on-line budget preparation
BM37     capabilities to all departments based on user defined                       NS
         rules.
         The system should provide the ability to maintain
         narrative information such as goals and objectives,
BM38     justifications, and performance criteria within the                         NS
         department. Justifications should be able to be
         maintained at the lowest level of budget line item.
         The system should provide the ability to electronically
BM39     route the following while maintaining a complete audit
         trail:
         Budgets for approval. The approver should be able to
BM39   1                                                                             NS
         make changes to the budget.
BM39   2 Proposed budgetary transfers/changes.                                       NS
         Budget Development & Preparation Requirements
         Average GAP
         Budget Setup and Controls Requirements Section
         The system should provide the ability to setup and apply
BM40     budgetary controls at any level of the account structure                    NS
         (by line item), as established in the chart of accounts.




                                                                    Page 69 of 169
       The system should provide the ability to summarize
       budgets based on account attributes (groupings) that
BM41                                                                                 NS
       are built into the account structure in the General Ledger
       and Project Ledger.
       The system should accommodate multi-year (inception
BM42                                                                                 NS
       to date) budget controls.
       The system should provide the ability to set spending
BM43   controls or establish a spending plan related to available                    NS
       funds for expenditures.
       They system should provide the ability to perform
       budget checking at all transaction points, including pre-
BM44                                                                                 NS
       encumbrance, purchase order, invoice, and check
       generation.
       The system should allow for the designation of whether
       a warning or a block will occur when a user attempts to
       enter a transaction that exceeds the available funds in
BM45                                                                                 NS
       the budget. This should be available for each stage of
       budget checking (requisition, purchase order, invoice,
       check),
       The system should allow authorized users the ability to
       establish a tolerance percentage or any other user
BM46                                                                                 NS
       defined constraint before the over-budget condition is
       blocked or warned.
       The system should allow for a contact person or
BM47   "responsible person" assigned to each cost                                    NS
       center/department.
       The system should allow for the definition of security
       that restricts the access, creation and/or approval of
BM48                                                                                 NS
       specific budgets to authorized users. Security should be
       provided at the functional and database level.
       Budget Setup and Controls Requirements Average
       GAP
       SLCO Requirements Section
       The system should provide pull-down lists and lookup
BM49                                                                                 NS
       features within data fields




                                                                    Page 70 of 169
       The system should allow for the analysis of subsequent
BM50   proposals and changes without affecting current                           NS
       budgets.
       The system should provide Activity Based Budgeting
BM51                                                                             NS
       (ABB).
       The system should allow authorized users see which
BM52                                                                             NS
       budgets have been approved.
       The system should be able to assign temporary cost
BM53   center numbers and be able to delete them if not                          NS
       approved.
       The system should provide the ability to check for
BM54   unauthorized charges against budgeted line items on a                     NS
       timely basis.
       Ability to budget for capital asset purchases from
BM55                                                                             NS
       balance sheet accounts and have budgetary controls.
       SLCO Requirements Average GAP
       Total GAP




                                                                Page 71 of 169
SALT LAKE COUNTY                                                                     INSTRUCTIONS                                               RATING LEGEND
Functional Requirements Matrix                                                                                        SUP   Supported as delivered "out-of-the-box"
                                                                        Complete the worksheet by placing an X in           Supported via modifications (screen configurations, reports, GUI
                                                                           the most appropriate column for each       MOD
                                                                                                                            tailoring, etc)
                                                                          criterion. The X's should represent the
                                                                           current state of a particular product or   3RD   Supported via a third party solution
                                                                       service. (More than one response to a single   CST   Supported via customization (changes to source code)
                                                                            requirement will be treated as a non
                                                                                          response)
                                                                                                                      FUT   Will be supported in a future release
                                                                                                                      NS    Not supported


       ACCOUNTS PAYABLE MANAGEMENT                                                RATING RESPONSE                                    ADDITIONAL COMMENTS
                                                                        SUP      MOD       3RD      CST      FUT      NS                                                              Resp
 AP      General Operating Requirements Section
         The system should integrate with the Purchasing
         module, General Ledger, Encumbrance, Inventory,
 AP1                                                                                                                                                                                   NS
         Project Ledger, Fixed Assets, Contracts, and the Grants
         module.
         The system should provide the option for 3 way
 AP2     matching of purchase orders, receiving documents and                                                                                                                          NS
         invoices
         The AP system should automatically post entries to the
 AP3     General Ledger, including expense distribution, cash                                                                                                                          NS
         distribution, discounts earned, retainage, sales tax, etc.)

         The system should be able to track use taxes and
 AP4                                                                                                                                                                                   NS
         automatically generate the entries to book the liability
         The system should have the capability to prevent
 AP5     unauthorized users from modifying invoice data once                                                                                                                           NS
         the invoice has been approved and released.
         The system should have the ability to prevent the entry
 AP6     of an invoice that would cause the cumulative invoiced                                                                                                                        NS
         amount to exceed the contract or purchase order.



                                                                                                 Page 72 of 169
          The system should have the following capabilities
AP7
          related to vendor returns:
          The system should maintain credit memo balances for
AP7   1                                                                               NS
          vendor(s) in order to offset future invoices.
          The system should have the ability to apply a credit
AP7   2                                                                               NS
          memo to more than one vendor invoice
          The system should prevent payments to vendors with
AP7   3                                                                               NS
          credit or zero balances
          The system should have the following 1099 related
AP8
          capabilities:
          The system should track 1099 vendors and keep a
AP8   1                                                                               NS
          history of all 1099 qualifying payments.
          The system should have the capability to generate 1099
AP8   2   IRS reports on standard forms and also to transmit 1099                     NS
          information electronically
          The system should allow for the addition of manually
AP8   3                                                                               NS
          added 1099's.
          The system should include mandated 1099 updates with
AP8   4                                                                               NS
          annual maintenance releases.
          The system should provide the ability to keep track of
AP8   5   IRS notices for missing or incorrect tax ID numbers for                     NS
          individual vendors.
          The system should provide the ability to indicate that a
          vendor is 1099 but then allow the user to exclude
AP8   6                                                                               NS
          individual payments from the 1099 transactions for that
          vendor.
          The system should provide the ability to generate
AP8   7                                                                               NS
          amended 1099s.
          The system should provide the ability to automatically
AP8   8                                                                               NS
          adjust 1099 balances when payments are cancelled.
        The system should comply with IRS Regulations where
        withholdings from individual vendors are required
AP8   9                                                                               NS
        according to the regulations. (3% percent withholding
        reuirement)
        The system should allow payments against multiple
AP9                                                                                   NS
        invoices on one check



                                                                     Page 73 of 169
       The system should allow the user to request separate
AP10   checks when multiple invoices are being processed for                                                                                NS
       the same vendor.
       The system should support multiple payment types
AP11   (e.g., system generated checks, manual checks, wire                          The current system does not support procurement cards   NS
       transfers, procurement cards, e-commerce, etc.)
       The system should update encumbrance records once
AP12   an invoice is paid. (In order to move the amount from                                                                                NS
       encumbered to actual).
       The system should provide the ability to pay both
AP13   encumbered and non-encumbered items on the same                                                                                      NS
       check.
       The system should allow for the processing of stop
AP14                                                                                                                                        NS
       payments.
AP15   The system should be able to void a range of checks.                                                                                 NS
       The system should allow users to void all stale dated
AP16   checks that were dated on or before a user defined                                                                                   NS
       date.
       The system should provide the ability to void a check
AP17   and facilitate the re-processing of a new check for the                                                                              NS
       same invoice(s).
       The system should allow invoices that are not tied to a
AP18   purchase order to be entered into the system. (as long                                                                               NS
       as the purchase does not exceed budgets)
       The system should allow multiple partial payments
       against a purchase order or a contract until the total
AP19                                                                                                                                        NS
       amount is reached. (Not restricted to an item, service or
       unit on a partial payment)
       The system should allow users to select from different
AP20                                                                                                                                        NS
       bank accounts for disbursements
       The system should allow authorized users to withhold
AP21                                                                                                                                        NS
       payments to a vendor even though the invoice is due
       Users should be allowed to enter a payment document
AP22                                                                                                                                        NS
       even if payments are being held



                                                                   Page 74 of 169
       The system should have the ability to suspend and/or
AP23   restart payment for specified vendors, contracts or work                     NS
       orders based on a user defined duration.

       The system should provide the ability to automatically
AP24   calculate discounts when the check payment date is the                       NS
       same as, or prior to, the discount due date.
       The system should provide the ability to override the
AP25                                                                                NS
       defaulted vendor discount.
       The system should provide a field to indicate the
AP26   distribution of the check. It should enable the user to                      NS
       indicate the specific pick-up location of the check.
       The system should provide the capability to sort and
AP27   print checks based on user-defined selection criteria.                       NS
       (including the pick-up location)
       The system should provide the ability to reverse an
       invoice distribution/posting with the proper security and
AP28                                                                                NS
       automatically reverse the General Ledger and AP
       postings.
       The system should be capable of interfacing to a third
AP29                                                                                NS
       party check writing software.
       The system should amortize existing pre-payments by
AP30   automatically generating invoices to distribute the                          NS
       payments to the proper periods.
       The system should come with a time and expense
AP31   functionality for the tracking of travel advances and                        NS
       travel expense reports.
       The system should have an automatic interface with
       banking institution(s) to allow for electronic ACH
AP32                                                                                NS
       payments and other digital functions (positive pay, stop
       payments, voids, etc).
       The system should have the ability to electronically
AP33   notify vendors of pending ACH payments and/or when                           NS
       payments have been made to their accounts.




                                                                   Page 75 of 169
       The system should provide the ability to copy
AP34   invoices/payment records The copied document should                          NS
       allow editing/modification.
       The system should provide a functionality for recurring
       invoices where the user can define the repetitive invoice
       and then the system will automatically generate an
AP35                                                                                NS
       invoice based on the specifications defined in the
       template. (frequency, amount, account, vendor, invoice
       numbering convention, etc.)
       The system should have the ability to automatically re-
AP36                                                                                NS
       open an invoice upon check voiding
       The system should provide the ability to reverse an
AP37   electronic payment and create a new electronic payment                       NS
       without entering additional data.
       The system should have controls to block or warn users
AP38   when invoices exceed the budget, encumbrances or                             NS
       when using invalid accounts
       The system should provide an efficient process to
AP39   facilitate the payment of immediate checks that need to                      NS
       be processed before the regular check processing date.
       The system should enable interfaces of invoice
       information (from another application). The system
AP40                                                                                NS
       should automatically generate invoice records for
       payment based on the uploaded information.
       The system should provide multiple payment selection
       criteria (i.e.: by due date, by vendor, invoice
AP41   category/group, by invoice number, by account number,                        NS
       by department number, etc.) in order to allow the user to
       pay based on various factors.
       The system should provide the ability to de-select an
AP42   invoice for payment (after a group of invoices has been                      NS
       selected for payment).




                                                                   Page 76 of 169
       The system should provide the option to automatically
AP43   split freight or shipping charges among split accounts                        NS
       within an invoice
       The system should allow the user to distribute a line
AP44                                                                                 NS
       item to multiple account numbers.
       For telephone, utility or similar bills, the system should
       provide the ability for users to set up distribution codes
AP45                                                                                 NS
       for the allocation of the invoiced amounts to various
       departments.
       The system should provide visibility to the PO while in
       invoice data entry mode. If the invoice is associated
       with a PO, then the user should be able to view the
AP46   purchase order line items and indicate the lines and                          NS
       amounts they would like to pay. This information would
       then automatically come forward into the invoice in order
       to reduce the need for duplicate data entry.
       The system should be able to route invoices for
AP47                                                                                 NS
       approval based on the account or dollar amount.
       The system should reference the contract number on
AP48                                                                                 NS
       the invoice screen (if applicable).
       The system should have the ability to group checks
       based on the dollar amount so that checks can be
AP49                                                                                 NS
       sorted and printed based on these groups for the proper
       signature requirements.
       General Operating Average GAP
       System Setup Requirements Section
       The system should automatically calculate the payment
       due date based on user-defined criteria for each vendor
AP50   (for example, 30 days from the receipt date of an                             NS
       invoice). The user should be able to over-ride the
       system produced date.
       The system should provide for the following fields on
       each payment document: Scheduled Payment Date;
AP51                                                                                 NS
       Invoice Number; Invoice Line; Invoice Date; Tracking
       Date; and Invoice Receipt Date.




                                                                    Page 77 of 169
         The system should allow for user-defined aging criteria
AP52                                                                                  NS
         for reporting.
         The system should allow for the setup of an
         overpayment threshold whereby invoices that are
AP53
         greater than the original PO/encumbrance by an
         established amount can be paid without delay:
         The system should have the ability to establish a
AP53   1                                                                              NS
         percentage threshold for overpayments.
         The system should have the ability to establish a dollar
AP53   2                                                                              NS
         threshold.
         The system should allow users to set up discount and
AP54                                                                                  NS
         payment terms for each vendor.
         The system should allow the customization of checks
         with fields such as the invoice number(s), invoice line
AP55     item(s), invoice amount(s), discounts taken, vendor                          NS
         name, vendor number, purchase order number and/or
         any other AP data field.
         System Setup Average GAP
         Reporting Requirements Section
         The system should be able to report on vendor payment
AP56     records for current period, year-to-date, prior years and                    NS
         also by date range.
         The system should provide a Vendor Analysis Report
AP57     that shows various breakdowns of activities (quantity,                       NS
         product line, type) by vendor.
         The system should provide the ability to view and report
AP58     on invoices waiting for payment by fund, department,                         NS
         vendor, due date, etc.
         The system should provide the option to print invoice
AP59     line items on the check stub in detail or summary                            NS
         format.
         The system should allow the printing of check details on
AP60                                                                                  NS
         successive check stubs if there is an overflow condition.
         The system should be able to print checks on blank
AP61     check stock (the system should print the system                              NS
         generated check number on the check).



                                                                     Page 78 of 169
       The system should provide standard and customized
       reports. Standard reports should, at a minimum, include
       Cash Disbursements Journal, Open Payables Listing,
       Accounts Payable Aging Report, Outstanding Invoice
AP62   Listing, Cash Requirements Report, Check Register,                           NS
       Outstanding Checks, Cleared Checks, Check
       Reconciliation Report, Vendor List, Void and Stale
       Dated Report, ACH/Wire Report, and Inactive Vendor
       List. (Have client identify others that they need)
       The system should generate reports that identify gaps in
AP63                                                                                NS
       the check sequence
       Reporting Requirements Average GAP
       SLCO Requirements Section
       The system should provide control totals during
AP64                                                                                NS
       Accounts Payable batch processing
       The system should generate unique AP batch numbers
AP65                                                                                NS
       or other unique identifiers
       The system should provide the ability to set up inter-
AP66                                                                                NS
       fund payable entries
       The system should be able to track taxes that have
AP67   been billed by the vendor, but that the Client is exempt                     NS
       from.
       The system should calculate tax rebates at the time of
AP68                                                                                NS
       invoice entry.
       The system should support debit/credit memos and
AP69   automatically post the appropriate entries to the General                    NS
       Ledger.
       The system should prevent duplicate invoices from
AP70                                                                                NS
       being entered.
       The system should allow users to view duplicate
AP71   invoices when the user is flagged that they are                              NS
       attempting to enter a duplicate invoice.
       The system should provide the capability for AP users to
AP72   schedule check runs (user can define when and how                            NS
       often checks are processed)




                                                                   Page 79 of 169
       The system should provide a check register of manually
AP73                                                                                                                                        NS
       prepared checks.
       The system should be able to flag checks such as:
       negative checks and zero checks. (Negative and zero
AP74                                                                                                                                        NS
       checks should not be printed nor checks less than a
       designated amount)
       The system should provide the ability to assign payment
AP75   to a different accounting year and budget year per                                                                                   NS
       governmental accounting requirements.
       The system should provide the ability to change the
       vendor on existing contracts. (For cases where the
AP76                                                                                                                                        NS
       vendor changes name or is bought by another
       company)
       The system should provide the ability to link historical
       vendor codes/numbers related to a newer vendor
AP77                                                                                                                                        NS
       code/number for the same vendor for analysis and
       reporting purposes.
       The system should provide one single summary screen,
       which indicates: contract or purchase order number,
AP78                                                                                                                                        NS
       vendor, item, current amount being paid, accounting info
       and previous payment info.
       The system should provide electronic invoicing (or work
       with a 3rd party vendor that can provide electronic
       invoicing), which is the process of receiving invoices
       from vendors either in an electronic format to begin with,                    Please indicate whether your software provides this
AP79   or converting them to electronic form after receipt of the                    feature or whether you would be working with a 3rd     NS
       paper invoice. The electronic invoice would be                                party vendor. (Please identify the 3rd party vendor)
       formatted to fit the payable system such that the invoice
       data can be used to automatically create a payment
       document in the system without human intervention.
       The system should provide imaging to scan paper
AP80   invoices and payment records for storage and retrieval                                                                               NS
       purposes.
       The system should provide separate fields to identify
AP81   freight and discounts separtely on the invoice data entry                                                                            NS
       screen.



                                                                    Page 80 of 169
       The system should provide for an unlimited or user
AP82                                                                               NS
       defined field size for invoice numbers.
       The system should allow the user to enter multiple
       invoice numbers (as one query) for which the system
AP83                                                                               NS
       will check to see any of them are duplicate invoice
       numbers.
       The system should allow for a check to be issued for a
AP84                                                                               NS
       single item.
       The system should allow users to void checks from a
AP85                                                                               NS
       previous year (with proper security).
       The system should have the ability to issue manual
AP86                                                                               NS
       warrants.
       The system should provide the ability to undo an invoice
AP87                                                                               NS
       distribution/posting with the proper security.
       The system should provide provide a flow chart of how it
AP88                                                                               NS
       has been setup and how the modules interact.
       The system should only require one User ID for users to
AP89                                                                               NS
       complete all transactions.
       The system should have the ability to use multiple
AP90                                                                               NS
       different ACH protocals.
       SLCO Requirements Average GAP
       Total GAP




                                                                  Page 81 of 169
SALT LAKE COUNTY                                                                  INSTRUCTIONS                                               RATING LEGEND
Functional Requirements Matrix                                                                                     SUP   Supported as delivered "out-of-the-box"
                                                                     Complete the worksheet by placing an X in           Supported via modifications (screen configurations, reports, GUI
                                                                        the most appropriate column for each       MOD
                                                                                                                         tailoring, etc)
                                                                       criterion. The X's should represent the
                                                                        current state of a particular product or   3RD   Supported via a third party solution
                                                                    service. (More than one response to a single   CST   Supported via customization (changes to source code)
                                                                         requirement will be treated as a non
                                                                                       response)
                                                                                                                   FUT   Will be supported in a future release
                                                                                                                   NS    Not supported


  ACCOUNTS RECEIVABLE MANAGEMENT                                               RATING RESPONSE                                    ADDITIONAL COMMENTS
                                                                     SUP      MOD       3RD      CST      FUT      NS                                                              Resp
 AR    General Operating Requirements Section
       The system should have integrated AR and Cash
 AR1                                                                                                                                                                                NS
       Receipts subsystems that provides real time information
       The system should provide the ability to categorize
 AR2                                                                                                                                                                                NS
       receivables by sales/receivable type.
       The system should maintain state sales tax information
 AR3   to facilitate automatic calculation of sales taxes on each                                                                                                                   NS
       invoice
       The system should provide the ability to generate tickler
 AR4   messages for automatic display on specific dates for                                                                                                                         NS
       follow-up with a customer.
       General Operating Requirements Average GAP
       Statements/Invoices Requirements Section
       The system should provide the ability to re-print
 AR5                                                                                                                                                                                NS
       customer invoices and billing statements.
 AR6   The system should provide electronic billing capabilities                                                                                                                    NS
       The system should be capable of creating user-defined
 AR7                                                                                                                                                                                NS
       forms for invoices and billing statements.




                                                                                              Page 82 of 169
       The system should be able to generate customer
       statements showing beginning balance, charges during
AR8                                                                                  NS
       the month, credits during the month, aging and ending
       balance.
AR9    The system should be able to bill partial invoices                            NS
       The system should support tear-off remittance advices
AR10                                                                                 NS
       that the customer can return with the payment

       The system should allow users to print invoices and/or
AR11   statements in any user defined criteria (i.e. by customer                     NS
       number, customer name, zip code, payment status, etc)
       The system should provide the ability to include
AR12                                                                                 NS
       informational messages on invoices/statements
       The system should allow users to suppress statements
AR13                                                                                 NS
       with zero and credit balance.
       The system should provide the ability to print mailing
AR14                                                                                 NS
       labels
       Statements/Invoices Requirements Average GAP
       Customer Requirements Section
       The system should provide a customer database with
AR15   the ability to assign a different class code for each type                    NS
       of customer.
       The system should provide the ability to assign multiple
AR16                                                                                 NS
       class codes to a customer.
       The system should provide different options to treat one-
AR17                                                                                 NS
       time customers.
       The system should provide the ability to maintain
       customer correspondence and internal notes/comments
AR18                                                                                 NS
       (for example: Customer has paid with NSF checks in
       the past, etc. )
       The system should provide the ability to tie a customer
AR19   code to some sort of geobase of street addresses for                          NS
       business license billing.
       The system should provide the ability to reference
AR20   business license number and other user defined                                NS
       elements to the customer information.



                                                                    Page 83 of 169
           The customer database should provide the ability to
AR21                                                                                      NS
           maintain insurance information.
           Customer Requirements Average GAP
           Billing Requirements Section
           The system should provide the ability to process
AR22       installment billings and perform aging according to the                        NS
           installment terms
           The system must be able to accommodate internal
AR23                                                                                      NS
           service billings.
           The system should provide the ability to set up recurring
AR24       billing based on contract specifications (i.e.: begin date,                    NS
           end date, insurance information, frequency, amount)
         The system should provide a user defined grace period,
AR25                                                                                      NS
         allowing customers to pay prior period rates.
         The system should provide the ability to bill by type of
AR26                                                                                      NS
         charge and/or type of customer.
         The system should provide the ability to suspend billing
AR27                                                                                      NS
         on items disputed by the customer.
AR28     Delinquencies:
         The system should be able to generate delinquency
AR28   1                                                                                  NS
         letters to customers
           The system should provide the ability to review past due
AR28   2                                                                                  NS
           customer accounts on-line by authorized personnel
           The system should provide the ability to assess interest,
AR28   3                                                                                  NS
           late charges and penalties.
AR28   4   The system should be able to waive Late Fees.                                  NS
AR28   5   The system should be able to waive NSF Fees.                                   NS
           The system should be able to waive Interest or Finance
AR28   6                                                                                  NS
           Charges.
           The system should provide the ability to produce a
AR28   7   report of accounts to write off based on user defined                          NS
           criteria.
           The system should provide the ability to track accounts
AR28   8                                                                                  NS
           sent to collection agencies.




                                                                         Page 84 of 169
         The system should provide the ability to track dollars of
AR28   9 delinquent accounts collected, collection cases and                            NS
         results of collection efforts.
AR29     Aging:
         The system should be able to support extended
AR29   1 payment terms and adjust the aging to reflect the new                          NS
         term
         The system should provide the ability to review
AR29   2 customer aging and other statistics (such as last                              NS
         payment date, etc.) on-line by authorized personnel
         The system should allow users to define aging
AR29   3                                                                                NS
         categories (e.g., current, 30,60,90 days)
AR30     Prepayments/Overpayments:
         The system should be able to produce customer refund
AR30   1 checks by automatically creating an AP invoice record                          NS
         based on the AR refund information.
AR30   2 The system should allow for prepayments by customers                           NS
           The system should allow users to enter credit memos to
AR30   3                                                                                NS
           update Accounts Receivable.
           Billing Requirements Average GAP
           SLCO Requirements Section
           The system should provide the ability to
AR31                                                                                    NS
           activate/deactivate customers on request
           The system should be able to maintain daily/monthly
AR32                                                                                    NS
           Accounts Receivable control totals with supporting detail
           The system should provide for automated inter-
AR33                                                                                    NS
           department charge backs
           The system should be able to generate a General
AR34       Ledger Distribution Report that summarizes the posting                       NS
           to specific Accounts Receivable and revenue accounts.
           The system should be able to generate warning when
AR35                                                                                    NS
           duplicate Invoice numbers are used.
AR36       The system should maintain a master customer file.                           NS




                                                                       Page 85 of 169
       The system should allow authorized users to create
       "dummy" cost centers and/or account number so that
AR37   the cash receipt can get posted to temporary accounts.                      NS
       The temporary accounts should be analyzed and then
       posted to the proper account.
       The system should provide the ability to automatically
AR38                                                                               NS
       assign unique credit memo numbers
       The system should provide the ability to print debit and
AR39                                                                               NS
       credit memos on request
       The system should allow for user-defined delinquency
AR40                                                                               NS
       notices
       The system should provide online customer and billing
AR41   data/status (such as invoice information, adjustments                       NS
       and payments by customers, etc. ).
       The system should be able to interface to various POS
AR42                                                                               NS
       systems.
       The system should provide the ability to track work
AR43                                                                               NS
       performed but not yet billed out to customers.
       The system should provide the ability to schedule the
AR44                                                                               NS
       printing of invoices (based on user defined parameters)
       The system should provide control totals during batch
       processing. The system should generate an error
AR45                                                                               NS
       message when the control amount differs from the
       amount entered.
       The system should allow invoices to be coded to split
AR46                                                                               NS
       accounts (multiple funds, object codes, etc.)
       The system should allow the customization of invoices
       and billing statements with fields such as the invoice
AR47   number(s), line item(s), invoice amount(s), account                         NS
       numbers, vendor name, vendor number, invoice/billing
       date, amount paid to date, etc.
       The system should be able to generate collection
AR48                                                                               NS
       notices.




                                                                  Page 86 of 169
       The system should be able to generate dunning letters
AR49                                                                               NS
       based on a user-defined progressive sequence.

       The system should allow invoice dates to be defined,
AR50                                                                               NS
       such as late payment date, delinquent billing date, etc.
       The system should have automatic interface with
AR51   banking institution(s) to allow for electronic payment                      NS
       receipt.
       The system should provide standard and customized
       reports. Standard reports should, at a minimum, include
AR52   Aging Report, Overdue Accounts, Collection Reports,                         NS
       Deposit Listings, Cash Receipts Listing, Activity by
       Customer, Outstanding Invoice Listing, Custom
       The system should provide the ability to decentralize AR
AR53   with appropriate security to provide agencies access                        NS
       and functionality as needed.
       The system should provide the ability to barcode
AR54   invoices and cash receipts to automate the posting of                       NS
       transactions.
       The system should provide the ability to attach Excel,
AR55   Word, and PDF documents to invoice and provider                             NS
       records.
AR56   The system should provide workflow capabilities                             NS
AR57   the system should provide imaging capabilities                              NS
       SLCO Requirements Average GAP
       Total GAP




                                                                  Page 87 of 169
SALT LAKE COUNTY                                                                    INSTRUCTIONS                                               RATING LEGEND
Functional Requirements Matrix                                                                                       SUP   Supported as delivered "out-of-the-box"
                                                                       Complete the worksheet by placing an X in           Supported via modifications (screen configurations, reports, GUI
                                                                          the most appropriate column for each       MOD
                                                                                                                           tailoring, etc)
                                                                         criterion. The X's should represent the
                                                                          current state of a particular product or   3RD   Supported via a third party solution
                                                                      service. (More than one response to a single   CST   Supported via customization (changes to source code)
                                                                           requirement will be treated as a non
                                                                                         response)
                                                                                                                     FUT   Will be supported in a future release
                                                                                                                     NS    Not supported


                     CASH RECEIPTS                                               RATING RESPONSE                                    ADDITIONAL COMMENTS
                                                                       SUP      MOD       3RD      CST      FUT      NS                                                              Resp
 CR       General Operating Requirements Section
          The system should allow for the collection of cash
CR1       payments for both general receipts and for receipts on                                                                                                                      NS
          receivables.
          The system should allow for multi-line descriptions to be
CR2                                                                                                                                                                                   NS
          entered on each receipt.
          The system should allow for the tracking of receipts by
CR3       various types (types should be user definable, but can                                                                                                                      NS
          define the type of revenue).
          The system should allow for the tracking of receipts by
CR4       input operator and by date. Detailed information should                                                                                                                     NS
          be available.
          The system should provide the ability to track multiple
CR5
          receipt types including:
CR5   1   Cash                                                                                                                                                                        NS
CR5   2   Check                                                                                                                                                                       NS
CR5   3   Money Order                                                                                                                                                                 NS
CR5   4   Credit Cards                                                                                                                                                                NS
CR5   5   Direct Deposits                                                                                                                                                             NS
          Other (auto-pay, lockbox, online payment, online
CR5   6                                                                                                                                                                               NS
          banking, etc.)




                                                                                                Page 88 of 169
         During cash receipting, the system should allow the
CR6      online lookup of customer numbers based on a full or                        NS
         partial name entry.
         During cash receipting, the system should allow the
CR7                                                                                  NS
         online lookup of account name and numbers.
         For each line of a cash receipt, the system should allow
CR8      for the entry of the project, grant, work order, and/or                     NS
         task number for notation or posting to those systems.
         The system should provide for a daily and monthly cash
         receipts journal report showing all transactions. The
CR9                                                                                  NS
         reports should be able to provide a summary by
         category and date range.
         The system should provide the ability for cash to be
CR10                                                                                 NS
         deposited into multiple bank accounts.
         The system should be able to interface to various POS
CR11     systems by specific revenue accounts and type of                            NS
         receipt (cash, check, credit card, debit card, etc.)
         The system should allow the same check to apply to
CR12                                                                                 NS
         multiple open items
         The system should allow partial payments to be applied
CR13                                                                                 NS
         to specific invoice line items.
         The system should allow partial payments to be applied
CR14     in a predetermined hierarchy instead of just applying                       NS
         payments to the earliest open receivable item.
         The system should provide the ability to process non-
CR15     sufficient funds checks with correct posting to the                         NS
         General Ledger
         General Requirements Average GAP
         Reporting Section
         The system should provide a daily or monthly edit report
CR16
         showing cash receipts sorted at a minimum by:
CR16   1 Receipts By Operator                                                        NS
CR16   2 General Ledger Distribution                                                 NS



                                                                    Page 89 of 169
CR16   3   Date                                                                         NS
CR16   4   Receipt by Location                                                          NS
CR16   5   Receipts By Type                                                             NS
CR16   6   Receipts By Bank                                                             NS
CR16   7   Receipts By Processing Source (i.e.: PayPal, etc.)                           NS
CR16   8   Entry Sequence                                                               NS
           The system should allow for printing of fund and
CR17                                                                                    NS
           account information on cash receipts.
           The system should provide the ability to print receipts
CR18                                                                                    NS
           immediately after customer payments are entered.

           The system should allow cash receipts to be printed in
CR19                                                                                    NS
           batch (by type) or to be converted to PDF to be mailed.
           Reporting Average GAP
           SLCO Requirements Section
           The system should provide the ability to print a cash
CR20                                                                                    NS
           receipts edit listing.
           The system should allow the cashier to defined
CR21                                                                                    NS
           shortened revenue codes in place of full account codes
           The system should provide the ability to track and report
CR22       on cash receipts by credit card company (American                            NS
           Express, Visa, etc.)
           The system should facilitate ACH cash receipting on a
CR23       centralized and decentralized basis to multiple bank                         NS
           accounts, if necessary.
           The system should allow for payments to be processed
CR24       through a variety of payment methods including in-                           NS
           person payments and on-line payments.
           The system should be able to group cash receipts into
CR25                                                                                    NS
           one deposit entry based on user-defined periods (daily)
           The system should allow users to modify cash receipts
CR26       that have been previously entered (but not posted) in the                    NS
           system.




                                                                       Page 90 of 169
       The system should allow the ability to re-print cash
CR27                                                                             NS
       receipts.
       The system should provide for robust reporting and BI
CR28                                                                             NS
       capabilities
       The system should provide the ability to assign unique
CR29                                                                             NS
       cash receipt numbers.
       General Requirements Average GAP
       Total GAP




                                                                Page 91 of 169
SALT LAKE COUNTY                                                                   INSTRUCTIONS                                               RATING LEGEND
Functional Requirements Matrix                                                                                      SUP   Supported as delivered "out-of-the-box"
                                                                      Complete the worksheet by placing an X in           Supported via modifications (screen configurations, reports, GUI
                                                                         the most appropriate column for each       MOD
                                                                                                                          tailoring, etc)
                                                                        criterion. The X's should represent the
                                                                         current state of a particular product or   3RD   Supported via a third party solution
                                                                     service. (More than one response to a single   CST   Supported via customization (changes to source code)
                                                                          requirement will be treated as a non
                                                                                        response)
                                                                                                                    FUT   Will be supported in a future release
                                                                                                                    NS    Not supported


                   FIXED ASSETS                                                 RATING RESPONSE                                    ADDITIONAL COMMENTS
                                                                      SUP      MOD       3RD      CST      FUT      NS                                                              Resp
 FA    General Operating Requirements Section
       The system should integrate with the General Ledger,
 FA1   Accounts Payable, Purchasing, and Work Order                                                                                                                                  NS
       modules.
       The system should have the ability to automatically
       populate the useful life based on the asset classification.
 FA2                                                                                                                                                                                 NS
       The user should be able to exclude or override a
       classification
       The system should provide the capability to assign
 FA3   primary classes to assets. (for reporting and inquiry) For                                                                                                                    NS
       example, building, vehicles, equipment, etc.
       The system should provide the capability to assign
       secondary or tertiary classes to assets. (for sorting and
 FA4   inquiry) For example, office equipment could represent                                                                                                                        NS
       a secondary class and fax machine, copier, and printer
       could represent tertiary classes.
       The system should allow for improvement adjustments
       to an asset to increase the value and/or extend the
 FA5   useful life, while maintaining the original asset                                                                                                                             NS
       information intact. It should track the history of
       improvements to an asset.




                                                                                               Page 92 of 169
           The system should allow for the automatic creation of
           fixed assets based on account number & dollar
FA6        threshold. Information from Purchasing and Accounts                         NS
           Payable can be automatically brought over to the Fixed
           Assets database.
           The system should allow for the creation of detailed
FA7        retirement records in relation to an asset, including                       NS
           sales price, disposal date, method of sale, etc.
           The system should provide the ability to track an asset
FA8        that was purchased from more than one cost center                           NS
           (charge code)
           The system should be able to expedite the process of
           transfers and disposals through automated processing.
           For example, an electronic transfer form could be
           established whereby as soon as the asset number is
           entered, the remaining data fields are populated from
FA9
           the Fixed Asset database. Using automated tools, this
           form is then sent to the receiving department for their
           acceptance of the transfer and then to Accounting to
           ensure the proper entries are made within the Fixed
           Assets system. The system should:
         Accommodate the creation of user-defined electronic
FA9    1                                                                               NS
         forms.
         Automatically populate data fields on the form from
FA9    2                                                                               NS
         existing asset information.
         Allow electronic forms to be routed for electronic
FA9    3                                                                               NS
         approvals.
           The system should have the ability to track the transfer
FA10                                                                                   NS
           of assets and all associated location/transfer history
           The system should have the ability to provide for the
FA11       automatic creation of entries to the General ledger for                     NS
           transfer and disposition transactions.
           The system should have the ability to maintain detailed
FA12                                                                                   NS
           vehicle records for insurance purposes.




                                                                      Page 93 of 169
       The system should have the ability to maintain cost,
FA13                                                                                NS
       insurance, and replacement values for property.
       The system should have the ability to maintain detailed
FA14                                                                                NS
       warranty records.
       The system should allow for CIP classification to accrue
FA15   costs while the asset is still under construction, but                       NS
       exclude it from depreciation
       The system should provide the ability to link related
FA16                                                                                NS
       assets together
       The system should provide the ability to track
       information related to the asset purchase, such as
       contract number, purchase order number, funding
FA17                                                                                NS
       source, grant information, bid number, check number,
       invoice number, vendor, item description, GL account,
       etc.
       The system should provide capabilities to automatically
FA18   create multiple fixed asset records based on a purchase                      NS
       of multiple quantities.
       The system should provide the ability to record donated
FA19   assets and other non cash assets for reporting on the                        NS
       cash flow statement
       The system should provide sufficient fields to track
       location information, such as building, department,
FA20                                                                                NS
       room, room description, address, phone, GPS number,
       etc.
       The system should provide the capability to assign a
FA21   responsible person or role, such as a custodian, to a                        NS
       fixed asset.
       The system should provide a "notes" section to allow
FA22                                                                                NS
       free form text entry
       The system should allow the attachment of an image(s)
FA23   to each asset; such as a picture of the asset, title                         NS
       documents, surveys, invoices, warranty certificates, etc.
       The system should provide barcode capability with
FA24                                                                                NS
       physical inventory input




                                                                   Page 94 of 169
       The system should provide users the ability to copy
FA25                                                                                    NS
       asset information from another, pre-existing asset.
       The system should provide the ability to assign fixed
FA26   asset numbers based on a 'seed' number so that                                   NS
       numbers will not be skipped or duplicated.
       The system should allow for the creation of an electronic
       form that will be automatically sent to the responsible
       asset custodian upon receipt of the asset. The form will
FA27   require the custodian to complete information regarding                          NS
       the asset, including serial number, model number,
       location, etc. Once completed, the information will
       automatically update the asset record.
       The system should provide the ability to set up security
       in order to restrict users to read or write access based
FA28                                                                                    NS
       on their location/department, or other user defined
       criteria.
       The system should provide the ability to track controlled
FA29   (non-capital) assets. These assets should be able to be                          NS
       uniquely identified so that they do not depreciate.
       The system should provide the ability to track employee-
FA30   issued controlled asset items for internal control                               NS
       purposes.
       The system should provide the ability to distinguish fixed
FA31   assets in government funds, proprietary funds and                                NS
       government wide for GASB reporting purposes.
       The system should have the capability to retain the fixed
       asset number (that was automatically assigned by the
FA32   system) within the A/P or the G/L subsystems. This                               NS
       would facilitate users in identifying fixed asset
       assignments based on expenditure activity reports.
       The system should provide the ability to make mass
       changes to an unlimited number of asset records based
FA33                                                                                    NS
       on a single request/single screen entry with full audit trail
       of changes made.



                                                                       Page 95 of 169
       The system should have the ability to interface to work
FA34   order, asset management, fleet management, and other                           NS
       systems.
       General Operating Average GAP
       Depreciation Section
       The system should have the ability to adjust
       depreciation accordingly if a valid adjustment is made to
FA35                                                                                  NS
       the cost/useful life of an asset. (with full audit trail of
       changes made).
       The system should provide for the automated
FA36   calculation of depreciation and posting of entries to the                      NS
       General Ledger
       The system should have the ability to selectively post
FA37   depreciation based on asset category, account, status,                         NS
       or other field.
       The system should have the option to depreciate on a
FA38   variety of methods (straight line, sum of years digits,                        NS
       double declining balance, etc.)
       The system should provide for depreciation
FA39   comparisons, such as Last Year Amount, Year to Date                            NS
       Amount, Last Depr Amount, etc.)
       The system should allow a choice for fixed assets to
FA40   begin depreciation based on either the acquisition date                        NS
       or the in-service date.
       The system should allow depreciation to be calculated
FA41                                                                                  NS
       on a monthly, quarterly, or annual basis.
       The system should have the ability to allocate
       depreciation expense to the
FA42                                                                                  NS
       functions/programs/activities on the Statement of
       Activities consistent with GASB 34.
       Depreciation Requirements Average GAP
       SLCO Requirements Section
       The system should allow both automatic and manual
FA43                                                                                  NS
       entry creation of an asset into the system
       The system should provide the ability to track multiple
FA44                                                                                  NS
       funding sources related to one asset




                                                                     Page 96 of 169
       The system should provide the ability to print standard
       reports and create customized reports. (standard
FA45                                                                                                            NS
       reports should include depreciation and inventory
       reports by class/category, cost center, etc.)
       The system should provide miscellaneous fields for user
FA46                                                                                                            NS
       defined information
       The system should provide separate fields for Serial
FA47                                                                                                            NS
       Number, Manufacturer, other identifying marks
       The system allows for multiple serial numbers to be
FA48                                                                                                            NS
       recorded for the same asset.
       The system should provide the ability to
FA49   upload/download information (integration with desktop                                                    NS
       applications)
       The system should integrate with receiving so that
FA50   Property Management will know when an asset has                                                          NS
       been received and is ready for tagging.
FA51   Ability to assign, manage and print Tag Numbers                            Currently use a third party   NS
FA52   Interface with GIS                                                                                       NS
       Ability to distinguish between true additions and
FA53   disposals compared to internal adjustments, for                                                          NS
       example CIP transfers or asset number corrections.
       SLCO Requirements Average GAP
       Total GAP




                                                                 Page 97 of 169
SALT LAKE COUNTY                                                                  INSTRUCTIONS                                               RATING LEGEND
Functional Requirements Matrix                                                                                     SUP   Supported as delivered "out-of-the-box"
                                                                     Complete the worksheet by placing an X in           Supported via modifications (screen configurations, reports, GUI
                                                                        the most appropriate column for each       MOD
                                                                                                                         tailoring, etc)
                                                                       criterion. The X's should represent the
                                                                        current state of a particular product or   3RD   Supported via a third party solution
                                                                    service. (More than one response to a single   CST   Supported via customization (changes to source code)
                                                                         requirement will be treated as a non
                                                                                       response)
                                                                                                                   FUT   Will be supported in a future release
                                                                                                                   NS    Not supported


        CONTRACTS MANAGEMENT                                                   RATING RESPONSE                                    ADDITIONAL COMMENTS
                                                                     SUP      MOD       3RD      CST      FUT      NS                                                              Resp
 CM    General Operating Requirements Section
       The system should integrate in real time to Purchasing,
CM1    Budget, Bid/Quote, Accounts Payable and other                                                                                                                                NS
       applicable subsystems.
       The system should track vendor's insurance information
CM2    with insurance requirements, coverage amounts, types                                                                                                                         NS
       of coverage, and expiration dates.
       The system should have the ability to provide a user
CM3    defined alert if a contractor's insurance is about to                                                                                                                        NS
       expire.
       The system should provide warning or a block when a
CM4    contract is about to expire based on user defined                                                                                                                            NS
       criteria.
       The system should allow for electronic insurance
CM5                                                                                                                                                                                 NS
       renewal notices to be sent to contractors.
       The system should provide reason codes and/or
CM6                                                                                                                                                                                 NS
       remarks for missed milestone dates.
       The system should provide the ability to track and report
CM7    on contract data, including receiving statistics, warranty                                                                                                                   NS
       claims.
       The system should have the ability to manage and track
CM8                                                                                                                                                                                 NS
       grant related revenue contracts.


                                                                                              Page 98 of 169
           The system should provide a consistent contract data
           entry screen whether the contract is a revenue contract,
CM9                                                                                        NS
           encumbered contract, or expensed (unencumbered)
           contract with the ability to define multiple line items.
           The system should provide an "Authorization to Start"
CM10       field for consultant contracts if one is provided or default                    NS
           to the current date.
           The system should be able to create and generate
           letters or emails based on user-defined templates. For
           example, to create award letters to successful bidders
CM11       as well as letters for contractors/vendors who were not                         NS
           selected. (Other letters may include "Authorization to
           Start", "Renewal Notices", "Notice to Proceed",
           "Contractor's Affidavit", other legal documents, etc.)
           The system should provide multiple contract approval
CM12       routes to track all stages of the contract approval                             NS
           process based on contract type.
           The system should allow for concurrent approvals on a
CM13                                                                                       NS
           contract.
           The system should be able to maintain a list of required
CM14       legal documents in relation to a contract. (ie: bonds,                          NS
           certificates, licensing)
           The system should allow for the creation of a single year
CM15                                                                                       NS
           or a multi-year contract.
           The system should maintain a library of standard and
CM16       acceptable legal/ performance bond                                              NS
           documents/samples.
CM17       The system should provide the ability to track:
CM17   1   Advertised date                                                                 NS
CM17   2   Bid opening date                                                                NS
CM17   3   Mayor date                                                                      NS
CM17   4   Notice of award date                                                            NS
CM17   5   Notice to proceed date                                                          NS
CM17   6   Notice of completion date                                                       NS
CM17   7   Final payment date                                                              NS



                                                                          Page 99 of 169
            User defined warranty due date triggered by another
CM17 8                                                                                      NS
            date
CM17    9   Contract termination date                                                       NS
CM17   10   Modification to contract date(s)                                                NS
CM17   11   Original estimated amount                                                       NS
CM17   12   Award amount                                                                    NS
CM17   13   Change order/amendment amounts even if negative)                                NS
CM17   14   Number of days for completion                                                   NS
CM17   15   Days added/deleted via change orders                                            NS
CM17   16   Retention Amounts/percentage                                                    NS
CM17   17   Notes field                                                                     NS
            The system should have the ability to send out
CM18        reminders to process retention and associated interest                          NS
            payouts.
            The system should provide the ability to track
CM19                                                                                        NS
            MBE/WBE/DBE requirements and related compliances.
            The system should provide the ability to verify
CM20        participation and payments to sub-contractors by the                            NS
            prime contractor.
            The system should provide the ability to track
CM21        contractor's compliance with prevailing wage                                    NS
            regulations.
            The system should provide the ability to assign
            quantities to tasks/subtasks with user-defined units of
CM22                                                                                        NS
            measure and unit costs (for example: engineers'
            estimates)
            The system should provide a text field in order to list any
CM23        possible exceptions or qualifications by bid or bid item.                       NS
            (alternate bid items)
            The system should allow users to develop contract
CM24                                                                                        NS
            related notes, messages and comments.
            The system should allow users to enter and update
CM25        monthly construction progress in order to determine the                         NS
            amount of the current month progress payment.




                                                                          Page 100 of 169
       The system should allow authorized personnel to select
       a successful bidder from the list of bid responses and to
CM26                                                                                  NS
       record a comment for cases where the low bidder was
       not selected.
       The system should provide the ability to produce bid and
CM27                                                                                  NS
       RFP documents.
       The system should allow a bid award to automatically
       turn into a contract after the necessary approval and
CM28   review processes have been completed. The system                               NS
       should allow the capability to generate multiple
       numbered contracts from the bid document.
       The system should be able to interface to contract
       administration software. (Vendors: Please indicate the
CM29   contract administrator software packages that your                             NS
       system has successfully interfaced to in the past - in the
       comments section).
       The system should provide the ability to establish
CM30   retainage based on a percentage and/or a dollar                                NS
       amount.
       The system should allow for a user defined multi-level
       retainage structure for calculation of progress payment
CM31                                                                                  NS
       (payment request) based on criteria of percentage
       completed or total amount paid to a contractor.
       The system should provide the ability for an authorized
CM32   user to override a retainage amount at invoice entry.                          NS
       (with proper security/authority)
       The system should provide the ability for an authorized
       user to release retainage at the contract and project
CM33                                                                                  NS
       level (lump sum release or percentage release) in a
       single or multiple transactions.
       The system should allow for separate retainage
CM34                                                                                  NS
       percentage for change orders (contract modifications).




                                                                    Page 101 of 169
       The system should provide the ability to route the
       contract modifications (change orders) to all required
CM35                                                                                  NS
       parties for approval and then record the status of the
       modification.
       The system should provide the ability to track the
       contract amount, payments and the contract balance for
CM36                                                                                  NS
       the original contract as well as all the amendments. The
       information should also be available in summary format
       The system should provide the ability to track numerous
CM37                                                                                  NS
       contract modifications.
       The system should be able to create and process
CM38                                                                                  NS
       change orders with multiple budget years
       The system should provide the ability to identify contract
       modifications either as a quantity change, a scope
CM39                                                                                  NS
       change or a combination. (with an explanation for the
       change)
       The system should provide the ability to calculate the
CM40   number of change orders by reason code for a specific                          NS
       contract and project.
       The system should maintain a single
CM41   bidder/contractor/vendor database with unique                                  NS
       identifiers.
       The system should provide the ability to track different
CM42   types of licenses and specialties held by                                      NS
       bidder/contractor/vendor.
       The system should provide the ability to close partially
       fulfilled contracts with proper authorization. The closing
CM43                                                                                  NS
       transaction must automatically update the
       encumbrances and budget.
       The system should be able to prevent a contract from
CM44   being closed if all required closing activities have not                       NS
       been achieved.
       The system should provide the ability to close out a
       contract through user-defined criteria (i.e.: upon the
CM45                                                                                  NS
       issuance of final payment, etc.) and release the
       remaining encumbrance.



                                                                    Page 102 of 169
       The system should enable users to view and report on
CM46                                                                                                                                        NS
       current and past contracts by year.
       The system should enable users to view and report on
       contracts by fund, account, grant(s), division, object,
CM47                                                                                                                                        NS
       activity, project, program manager, Mayor priority,
       and/or department.
       The system should enable users to view and report on
CM48   contracts by project manager, inspector, and other                                                                                   NS
       responsible party.
       The system should have the ability to include both
CM49   encumbered and non-encumbered line items on the                                                                                      NS
       same contract.
       The system should allow users to view contract history
CM50   on a single screen, including each project order (work                                                                               NS
       order, amendment and change order.
                                                                                     User should be able to choose this option when enter
       The system should have the ability to automatically
CM51                                                                                 the requisition, or be able for it to be automatic     NS
       create a contract record from a purchase requisition.
                                                                                     depending on user setup
       The system should provide the ability to track the
CM52   amount of money spent on American Disabilities Acts                                                                                  NS
       (ADA) related improvements for each contract.
       The system should provide a self service web-based
       capability, allowing contractors to view the results of a
CM53                                                                                                                                        NS
       particular bid. The amount of information displayed on
       the web should be user-defined.
       The system should provide the ability for contractors to
CM54                                                                                                                                        NS
       submit bids electronically.
       The system should provide the ability to track warranty
CM55                                                                                                                                        NS
       claims.
       The system should provide the ability to track stop
CM56                                                                                                                                        NS
       notices
       The system should provide the ability to track liquidated
CM57                                                                                                                                        NS
       damages
       The system should provide the ability to attach multiple
CM58                                                                                                                                        NS
       contracts to the same project (flip file.)




                                                                   Page 103 of 169
         The system should allow funds to be encumbered using
CM59     a future date. (ie: funds related to future years on multi-                     NS
         year contracts)
         The system should provide the ability to track materials
CM60                                                                                     NS
         on-hand payments (the material portion of a bid item).
         General Requirements Average GAP
         SLCO Requirements Section
         The system should have the capability to track
CM61                                                                                     NS
         insurance requirements, including:
CM62 1   Insurance expiration dates                                                      NS
         The ability to send out automatic e-mail or letter
CM62 2                                                                                   NS
         notifications of upcoming insurance expirations.
         The ability to provide notice that submitted insurance
CM62 3   coverage amounts and types are in or out of compliance                          NS
         with contract requirements.
         The ability to generate reports of insurance deficiencies
CM62 4                                                                                   NS
         and policy expirations.
         The system should provide the ability to log requests
CM62     and amounts for proposed contract modifications by                              NS
         project code as well as by bid line items.
         The system should provide warning when modified
CM63                                                                                     NS
         contract amount exceeds available funds.
         The system should provide the ability to modify and
CM64     monitor stated and revised contract amounts                                     NS
         (amendments) or scope.
         The system should provide the ability to track numerous
CM65                                                                                     NS
         modification numbers.
         The system should provide the ability to prioritize
CM66                                                                                     NS
         contract amendment actions.
         The system should provide the ability to track the length
         of time required to make a contract change (from
CM67                                                                                     NS
         submittal of proposed contract modification to approval
         by legal or other parties).
         The system should provide the ability to look up
CM68     information by contractor, project name/number and                              NS
         contract number.



                                                                       Page 104 of 169
       The system should allow changes to the contract
CM69                                                                             NS
       process, to include change orders and modifications
       The system should provide the ability to change the
CM70   vendor on an existing contract with proper                                NS
       authorization..
       The system should be able to flow chart all the steps
       that are required or optional to the system to aid in
CM71                                                                             NS
       process improvement and identify conflicts when
       process changes are suggested
       SLCO Requirements Average GAP
       Total GAP




                                                               Page 105 of 169
SALT LAKE COUNTY                                                                        INSTRUCTIONS                                               RATING LEGEND
Functional Requirements Matrix                                                                                           SUP   Supported as delivered "out-of-the-box"
                                                                           Complete the worksheet by placing an X in           Supported via modifications (screen configurations, reports, GUI
                                                                              the most appropriate column for each       MOD
                                                                                                                               tailoring, etc)
                                                                             criterion. The X's should represent the
                                                                              current state of a particular product or   3RD   Supported via a third party solution
                                                                             service. (More than one response to a       CST   Supported via customization (changes to source code)
                                                                           single requirement will be treated as a non
                                                                                             response)                   FUT   Will be supported in a future release
                                                                                                                         NS    Not supported


                  APPLICANT TRACKING                                                 RATING RESPONSE                                    ADDITIONAL COMMENTS
                                                                            SUP     MOD       3RD      CST      FUT      NS                                                              Resp
 AT         General Operating Requirements Section
            The system should provide the ability to integrate
 AT1                                                                                                                                                                                      NS
            seamlessly with other HR applications.
            The system should provide the ability to interface with a
 AT2        web-based application and to download data from this                                                                                                                          NS
            application directly into the Applicant Tracking Module.
            The system should provide the ability to retain applicant
 AT3        information for those applicants not selected for future                                                                                                                      NS
            consideration.
            The system should provide the ability to support the
            management and tracking of each applicant and/or
 AT4        candidate through the recruiting and application process
            by tracking, at a minimum, the following data item
            attributes for each applicant/candidate:
 AT4   1    Position number.                                                                                                                                                              NS
 AT4   2    Requisition number.                                                                                                                                                           NS
 AT4   3    Job title for which applicant applied.                                                                                                                                        NS
 AT4   4    Social security number of applicant.                                                                                                                                          NS
 AT4   5    Name - First, MI, Last, Jr. etc.                                                                                                                                              NS
 AT4   6    Date application was submitted.                                                                                                                                               NS
 AT4   7    Internal or external recruitment.                                                                                                                                             NS
 AT4   8    Posting expiration dates.                                                                                                                                                     NS
 AT4   9    Cost of recruitment.                                                                                                                                                          NS
 AT4   10   Referral source.                                                                                                                                                              NS
 AT4   11   Qualified/Non-qualified.                                                                                                                                                      NS
 AT4   12   Current and historical records of employment.                                                                                                                                 NS
            Current and historical records of any disciplinary,
 AT4   13   dismissal actions or failed background checks with                                                                                                                            NS
            warning for reason dismissed or terminated.
 AT4   14   Testing requirements.                                                                                                                                                         NS
 AT4   15 Applicant/Candidate's schedule of tests, interviews, etc.                                                                                                                       NS
            Applicant/Candidate's position in user-defined
 AT4   16                                                                                                                                                                                 NS
            qualification steps.
 AT4   17   Current testing/scoring results.                                                                                                                                              NS
 AT4   18   Historical test scores and banked scores.                                                                                                                                     NS
 AT4   19   Interview results/scoring/comments per interviewer.                                                                                                                           NS
 AT4   20   Interview history.                                                                                                                                                            NS
 AT4   21   Reference checks and results.                                                                                                                                                 NS
 AT4   22   Fingerprint record, if applicable.                                                                                                                                            NS
 AT4   23   Criminal Background Check                                                                                                                                                     NS
            Education verification (transcripts, required
 AT4   24                                                                                                                                                                                 NS
            coursework).
 AT4   25   Credential verification.                                                                                                                                                      NS
 AT4   26   License verification.                                                                                                                                                         NS
 AT4   27   Certifications                                                                                                                                                                NS
 AT4   28   Languages and Proficiency                                                                                                                                                     NS
 AT4   29   Veterans status.                                                                                                                                                              NS
 AT4   30   Eligibility to work in the U.S..                                                                                                                                              NS
 AT4   31   Response to job offer, if extended..                                                                                                                                          NS
 AT4   32   User defined rejection reason codes.                                                                                                                                          NS
 AT4   33   User defined comments field.                                                                                                                                                  NS
 AT4   33    Scoring results based on user-defined criteria.                                                                                                                              NS
            The system should provide the ability to track user
            defined special skills and/or competencies of applicants
 AT5                                                                                                                                                                                      NS
            so specialized skills can be targeted in the recruitment
            process.
            The system should provide the ability to create job
 AT6                                                                                                                                                                                      NS
            listings which are e-mailed to a specific distribution list.
            The system should provide the ability to generate
            appropriate correspondence (e.g., letters, e-mails) to
 AT7        qualified/ non-qualified and applicants based on status                                                                                                                       NS
            in the application process, using industry standard office
            products.
            The system should provide the ability to assign a user
            defined expiration date to applicant data, an eligibility
 AT8                                                                                                                                                                                      NS
            list and/or an applicant on an eligibility list (e.g.,
            continuous filing list).




                                                                                           Page 106 of 169
           The system should provide the ability to merge eligibility
AT9                                                                                       NS
           lists and/or criteria.
           The system should provide the ability to attach
AT10       electronic documents in Word, .PDF or any other format                         NS
           to the applicant record.
           The system should have the ability to automatically
AT11       include previous applicants who are eligible for new                           NS
           openings in hiring evaluations.
           The system should have the ability to automatically
AT12       include current employees who are eligible for new                             NS
           openings in hiring evaluations.
           The system should provide the ability to warn the user
AT13       and prevent the entry of a duplicate SSN or applicant                          NS
           number.
           The system should provide the ability to allow rehired
           employees to use their previous employee ID based on
AT14       the organization's defined criteria and identify the                           NS
           applicant as a former employee using their former
           number.
           The system should have the ability to generate warnings
AT15       and errors when trying to rehire employees terminated                          NS
           or disqualified for cause.
           The system should provide the ability for the hiring
AT16       manager to do online searches for applicants and view                          NS
           the applications and scanned documents.
           The system should provide the ability to suppress the
AT17       viewing of applicants who have not provided all required                       NS
           documentation and information.
           The system should provide the ability to ensure
AT18       adequate security of all confidential information and                          NS
           systems.
           The system should provide the ablility to establish pre-
AT19       screening hurdles to exclude unqualified candidates in                         NS
           advance of the detailed analysis process.
         The system should provide a resume parser to extract
AT20     information from uploaded resumes and automatically                              NS
         update applicant profiles.
         The system should provide a self-service module where
AT21     applicants can complete and view the status of their                             NS
         application(s).
         The system should provide the ability to provide an
AT22     online employment application available via a Web form                           NS
         on the Intranet or the Internet sites.
         The system should provide the ability for applicants to
         log into their online application to make changes to their
AT23                                                                                      NS
         profile information or to apply for a different position
         without creating an entirely new profile.
         The system should provide the ability to print and post
AT24     customized job announcements in HTML format to the                               NS
         internet.
         The system should provide the ability to allow an
AT25     applicant to view the results of their test/exam scores                          NS
         online through an Internet portal.
         The system should provide the ability to allow managers
AT26                                                                                      NS
         to schedule applicant interviews on-line.
         The system should provide automated workflow
         functionality to manage required actions and
AT27                                                                                      NS
         notifications (eg, scheduling of and notification of results
         for pre-employment testing).
         The system should provide the ability to provide tracking
         of and management of test scheduling for applicants
         where tests are required including online schedule of
AT28                                                                                      NS
         exams by applicants with access to an exam calendar
         and the ability to register and schedule themselves for
         exams or tests.
         The system should provide the ability to generate test
AT29     invitations to specifically identified                                           NS
         applicants/candidates.
         The system should provide the ability to analyze test
AT30                                                                                      NS
         score data within the system.
         The system should provide robust reporting functionality
         for the management and tracking of each
AT31
         applicant/candidate through the recruiting and
         application process:
         The system should provide for the reporting on
AT31   1 applications received and grouped by user defined                                NS
         criteria (e.g.position number, job title, department)
         The system should provide for the reporting on
AT31   2                                                                                  NS
         applicants tested (e.g., written, practical, oral).
           The system should provide for the reporting on
AT31   3                                                                                  NS
           applicants passed/failed (e.g., written, practical, oral).
         The system should provide for the reporting on
AT31   4                                                                                  NS
         applicants interviewed.




                                                                        Page 107 of 169
            The system should provide for reporting on the number
            of eligible applicants qualified/certified for hire in each
AT31    5   stage of the process (e.g., meeting minimum                                     NS
            requirements, passing tests, successful in the
            assessment process).
            The system should provide for the reporting on
AT31    6   applicants medically examined, drug tested and/or                               NS
            background checked.
            The system should provide for the reporting on
AT31    7                                                                                   NS
            applicant(s) selected for interviews.
            The system should provide for the reporting on
AT31    8                                                                                   NS
            applicants to whom job offers have been extended.
            The system should provide for the reporting on the
            status of selected applicants per position number or job
AT31    9                                                                                   NS
            title and related attributes (e.g., background checks,
            budget constraints).
            The system should provide for the creation of
AT31 10     notification lists for qualified/non-qualified candidates                       NS
            and/or applicants.
        The system should provide for user defined analytical
        reports to analyze, sort, select and report on candidates
AT31 11 using specific attributes such as education, experience,                            NS
        skills, references, past performance, test results, work
        location preference, veterans status, etc.
        The system should provide for reporting on activity per
        position number including number of applicants, status
AT31 12                                                                                     NS
        of applicants, average length to hire, qualifications,
        credentials, etc.
        The system should provide for reporting for EEO reports
AT31 13 on applicants (tracking of race, sex, position applied,                             NS
        etc.).
        The system should provide for the creation of candidate
        lists in a variety of sort orders including, but not limited
AT31 14 to job title, skill mix, position/requisition number,                               NS
        application date order, alphabetical name order, zip
        code or city order, etc.
            The system should provide for the creation of a vacancy
            requisition report documenting vacant positions with
AT31 15                                                                                     NS
            recruitments to fill as well as vacant positions that have
            no current recruitment in progress.
            General Requirements Average GAP
            SLCO Requirements Section
            The system should provide the ability to track applicants
            by occupational category and job groups through the
AT32        entire personnel process according to the requirements
            for EEO reporting including, but not limited to the
            following information:
AT32 1       EEO Classification                                                             NS
AT32 2       Advertising                                                                    NS
AT32 3       Recruitment                                                                    NS
AT32 4       Selection                                                                      NS
AT32 5       Placement                                                                      NS
AT32 6       Compensation                                                                   NS
AT32 7       Transfers                                                                      NS
AT32 8       Promotions                                                                     NS
AT32 9       Discipline                                                                     NS
AT32 10      Separation                                                                     NS
            The system should provide the ability to transfer
            applicant data directly from the Applicant Tracking
AT33                                                                                        NS
            Module into the Personnel Administration Module for a
            new hire to prevent duplicate data entry.
            The system should provide the ability to notify an
            applicant if additional documentation is needed to
AT34                                                                                        NS
            complete the evaluation process (e.g., degrees,
            certifications).
            The system should provide the ability to upload job
AT35                                                                                        NS
            listings to the Internet or the Intranet.
            The system should provide the ability to archive
AT36        applicant and/or candidate data after the position closing                      NS
            date for a specified time period.
            The system should provide the ability to designate the
AT37        applicant as successful in testing automatically after test                     NS
            results are entered.
            The system should provide the ability to provide access
            to real-time and/or archived interactive data in multiple
AT38        areas for viewing on screen or in reports on screen prior                       NS
            to printing and/or other interaction with all the
            applicant/candidate data.
            The system should provide the ability to generate
AT39        customized notices using Microsoft standard products                            NS
            as an editor.




                                                                          Page 108 of 169
       The system should provide the ability to revise and
       update any table driven attributes through a user friendly
AT40   interface such as class codes, exam locations,                                 NS
       department/division numbers and/or titles without
       complete re-creation of the table.
       The system should provide the ability for HR or a
AT41   Manager to enter job related or interview related                              NS
       comments about applicants and/or candidates.
       The system should provide the ability to run multiple
AT42                                                                                  NS
       batch processes for printing and scanning.
       The system should provide the ability to customize job
AT43                                                                                  NS
       postings by adding detailed specifics to each opening.

       The system should provide the ability to generate paper,
AT44                                                                                  NS
       e-mail and Web posting notices of positions to be filled.
       The system should provide the ability for applicants to
AT45   apply for two or more positions at once using one                              NS
       application.
       The system should provide the ability to allow Human
AT46   Resources and/or Applicants to reactivate an expired                           NS
       application.
       The system should provide the ability to allow Human
AT47   Resources and/or Applicants to deactivate an                                   NS
       application.
       The system should provide the ability to change
AT48                                                                                  NS
       expiration dates on lists based on user defined criteria.
       The system should provide the ability to produce an
AT49                                                                                  NS
       individual applicant profile.
       The system should provide the ability to track all
AT50                                                                                  NS
       applicant history under one master record.
        The system should provide for the creation of a detailed
       report of number of people hired by job class, class
AT51                                                                                  NS
       code, subject area, department, fiscal year, calendar
       year, month, year, etc.
       SLCO Requirements Average GAP
       Total GAP




                                                                    Page 109 of 169
SALT LAKE COUNTY                                                                INSTRUCTIONS                                               RATING LEGEND
Functional Requirements Matrix                                                                                   SUP   Supported as delivered "out-of-the-box"
                                                                   Complete the worksheet by placing an X in           Supported via modifications (screen configurations, reports, GUI
                                                                      the most appropriate column for each       MOD
                                                                                                                       tailoring, etc)
                                                                     criterion. The X's should represent the
                                                                      current state of a particular product or   3RD   Supported via a third party solution
                                                                     service. (More than one response to a       CST   Supported via customization (changes to source code)
                                                                   single requirement will be treated as a non
                                                                                     response)                   FUT   Will be supported in a future release
                                                                                                                 NS    Not supported


            LEAVE MANAGEMENT                                                 RATING RESPONSE                                    ADDITIONAL COMMENTS
                                                                    SUP     MOD       3RD      CST      FUT      NS                                                              Resp
 LM    General Operating Requirements Section
       The system should provide the ability to integrate time
       and attendance activity fully with the Leave
       Management System based on user defined
LM1    transactions. Leave Management should also integrate                                                                                                                       NS
       with all other modules within the HR suite such as
       Payroll, Benefits, Personnel Administration, Training,
       etc.
       The system should provide the ability to track any type
       of leave/absence (i.e., vacation, sick time, comp time,
       FMLA, State Leave Statute, Administrative, Jury Duty,
LM2    Disability, Military, Workers Compensation, Personal,                                                                                                                      NS
       Unpaid etc.), by accrued hours, accrual rate, accrual
       frequency, hours used, and balance based on user
       defined criteria.
       The system should provide the ability to define
LM3    parameters, carryover amounts, ceilings, etc. for                                                                                                                          NS
       leave/absence plans.
       The system should provide automated retroactive
LM4    vacation accruals based on user defined criteria (eg,                                                                                                                      NS
       class, compensation, etc.).
       The system should provide the ability to allow managers
                                                                                                                       SLCO Note: Some employees have access if on
       and/or supervisors to view leave data online relevant to
                                                                                                                       electronic timecards and some do not who are not on
       their scope of authority including individual employee
LM5                                                                                                                    electronic timecards. Viewing by employees is              NS
       leave/absence accrual, leave/absence taken data
                                                                                                                       available, but systems used in various areas are
       (leave/absence types include sick, vacation, holiday,
                                                                                                                       different.
       PTO), etc.
       The system should provide the ability for an employee
                                                                                                                       SLCO Note: County has a policy where an employee
       to "donate" leave hours to another employee according
LM6                                                                                                                    can donate hours to a "sick bank" as well as an            NS
       to any organizational policy of Employee Assistance and
                                                                                                                       employee.
       Goodwill.
       The system should provide the ability to track any
       required documentation and/or approval forms for a
LM7                                                                                                                                                                               NS
       leave/absence (e.g., FMLA documentation, Doctor’s
       Certificate of Authorization, etc.)
       The system should provide the ability to adjust leave
       accruals, time taken, balances etc. with appropriate
LM8                                                                                                                                                                               NS
       security. This includes the abilty to make retroactive
       adjustments.
       The system should provide the ability to create user
       defined leave/absence accrual structures based on
LM9                                                                                                                                                                               NS
       employee attributes (eg, years of service, job
       assignment, bargaining unit, etc.).
       The system should provide the capability to earn
LM10   leave/absence accruals during a paid absence based                                                                                                                         NS
       on user defined criteria.
       The system should provide a warning flag when
LM11   recorded absence hours are greater than the normal                                                                                                                         NS
       work hours for a specific work day or pay cycle.
       The system should provide an editing and review
LM12   method prior to the processing of leave transactions                                                                                                                       NS
       through the Payroll System.
       The system should provide the ability to track historical
       data per employee on each leave plan - such as type of
LM13   leave, leave start date, leave ending date, estimated                                                                                                                      NS
       return to work date and date paperwork received for
       approval.
       The system should provide the ability to establish and
       track rules surrounding an employee's return to work to
LM14   ensure requirements such as a physician's release to                                                                                                                       NS
       work, training, certification, and safety are addressed
       and confirmed prior to the employee's first day at work.
       The system should provide the ability to accommodate
LM15   vacation buy back and sell programs (i.e. leave                                                                                                                            NS
       conversion) based on user defined criteria.
       The system should provide the ability to track paid and
LM16   unpaid leaves of every kind including accrual based and                                                                                                                    NS
       government required.




                                                                                   Page 110 of 169
           The system should provide the ability to move an
           employee automatically to a new accrual rate due to
LM17                                                                                      NS
           anniversary date, eligibility change or policy rule
           change.
           The system should provide the ability to stop the use of
LM18       leave hours not yet earned if the organization's policy                        NS
           does not allow negative leave balances.
           The system should provide the ability to bank
LM19       compensatory time based on employee eligibility rules                          NS
           similar to a leave plan.
           The system should provide the ability to generate letters
LM20                                                                                      NS
           and forms using standard office tools.
           The system should provide the ability to prorate leave
LM21                                                                                      NS
           accruals for part-time employees.
           The system should provide the ability to report
LM22
           attendance data including but not limited to absence by:
LM22   1employee.                                                                         NS
LM22   2department.                                                                       NS
LM22   3work location.                                                                    NS
LM22   4job code.                                                                         NS
LM22   5supervisor.                                                                       NS
LM22   6project code.                                                                     NS
LM22   7date                                                                              NS
LM22   8type (illness, vacation, jury duty, etc.)                                         NS
LM22   9frequency.                                                                        NS
        leave/absence status (medical, non-medical, disabled,
LM22 10                                                                                   NS
        comp time, etc.
LM23       The system should not allow negative leave balances.                           NS
           The system should provide the ability to accurately
           maintain leave information for employees moving
LM24                                                                                      NS
           between employee eligibility statuses, bargaining units,
           uniform and non-uniform classifications, etc.
           The system should provide the ability to calculate
LM25       cashout value for accrued leave based on user defined                          NS
           rules.
           The system should provide the ability to calculate the
           dollar value of accrued leave based on user defined
LM26                                                                                      NS
           rules, for purposes of recording leave liabilities in the
           General Ledger.
           The system should provide the ability to enter
           employees' upcoming absences (vacation, scheduled
LM27                                                                                      NS
           sick leave, comp day, PTO, etc.) and allow the
           Supervisor to inquire who will be off in the future.
           General Requirements Average GAP
           SLCO Requirements Section
           The system should provide the ability to track eligibility
LM28       and qualifications for each type of leave/absence based                        NS
           on user defined criteria.
           The system should provide the ability to produce a
LM29       benefit eligibility list upon request for employees hired                      NS
           during a selected time period.
           The system should provide the ability to accrue sick
LM30                                                                                      NS
           leave based on user defined criteria.
           The system should provide the ability to manage
LM31       different groups of employees with different eligibility                       NS
           rules and different accrual/earning rates.
           They system should provide the ability to integrate any
           time and attendance system into the payroll processing
LM32                                                                                      NS
           with full integration and notification to Leave
           Management of user defined transactions..
           The system should provide the ability to warn
           employees, Supervisors, or Managers when the
LM33                                                                                      NS
           employee attempts to use more leave hours than are
           currently available.
           The system should provide the ability to create e-mail
LM34       notices or form letters for automated mailings regarding
           user defined events including, but not limited to:
LM34   1    - Expiring leave.                                                             NS
LM34   2    - Leave without pay letters.                                                  NS
LM34   3    - Family leave letters (FMLA).                                                NS
LM34   4    - Open enrollment.                                                            NS
           The system should provide the ability to notify Leave
           Management, the employee's Supervisor and/or
           Manager and any other personnel deemed necessary
LM35                                                                                      NS
           upon the approaching expiration of a type of
           leave/absence status (e.g., FMLA, expiration of a
           temporary position).
           The system should provide the ability to track
           concurrent leave/absence statuses (e.g., maternity
LM36                                                                                      NS
           leave/absence with illness leave/absence) based on
           differing rules.




                                                                        Page 111 of 169
        The system should provide the ability to perform fiscal
       year end updates on employee records based on
LM37                                                                                   NS
       defined criteria (i.e., years of service, vacation earning
       factor, bargaining unit, employee group, seniority, etc.).
       The system should provide the ability to create a
       leave/absence profile based on user-defined criteria for
LM38                                                                                   NS
       a department, a date range, an employee, a Supervisor,
       or other user defined parameters.
       The system should provide the ability to track leave that
LM39                                                                                   NS
       is advanced to the employee.
       The system should provide the ability to separate leave
       earned and taken into separate calendar years based
LM40                                                                                   NS
       on payroll and timekeeping data specific to the date of
       use.
       The system should provide the ability to automatically fill
       in dates in a range for vacation or leave. For example,
       the user would enter a start date and an end date and
LM41                                                                                   NS
       the system would fill in the days in between provided the
       absence code is the same and the days are
       consecutive.
       The system should provide the ability to allow certain
       corrections, such as accruals, time entry, etc. to the
LM42                                                                                   NS
       history of leave taken as well as corrections to the
       current parameters such as accrual rate and balance.

       The system should provide a field in which to indicate
       an employee's leave status for reporting purposes. At a
LM43   minimum, the system must have the ability to enter and                          NS
       save history for multiple leaves taken by an employee
       such as type of leave, leave start day, etc.
       The system should provide a way to track membership
       in the catastrophic leave bank, as well as the donation
       of catastrophic hours required to join. The system
LM44                                                                                   NS
       should be able to flag an employee as "accepted" into
       the bank or "denied" entry into the bank based on
       security definition.
       The system should provide the ability to track forfeited
LM45   short-term leave (for instance, leave exceeding the                             NS
       maximum.
       The system should provide the ability to accrue the
LM46                                                                                   NS
       earning of sick leave bonuses.
       System should track and automatically re-pay sick
LM47   advance with accruals when employee has returned to                             NS
       work
       System should only allow employee to enter leave if it's
LM48                                                                                   NS
       been pre-approved based on user criteria.
       SLCO Requirements Average GAP
       Total GAP




                                                                     Page 112 of 169
SALT LAKE COUNTY                                                                     INSTRUCTIONS                                               RATING LEGEND
Functional Requirements Matrix                                                                                        SUP   Supported as delivered "out-of-the-box"
                                                                        Complete the worksheet by placing an X in           Supported via modifications (screen configurations, reports, GUI
                                                                           the most appropriate column for each       MOD
                                                                                                                            tailoring, etc)
                                                                          criterion. The X's should represent the
                                                                           current state of a particular product or   3RD   Supported via a third party solution
                                                                       service. (More than one response to a single   CST   Supported via customization (changes to source code)
                                                                            requirement will be treated as a non
                                                                                          response)
                                                                                                                      FUT   Will be supported in a future release
                                                                                                                      NS    Not supported


                         PERSONNEL                                                RATING RESPONSE                                    ADDITIONAL COMMENTS
                                                                        SUP      MOD       3RD      CST      FUT      NS                                                              Resp
 PA         General Operating Requirements Section
            The system should provide seamless integration with
            other modules within the vendor's suite such as Payroll,
 PA1                                                                                                                                                                                   NS
            Leave Management, and Benefits to automatically
            update systems.
            The system should provide the ability to maintain the
 PA2
            following individual employee data, at a minimum:
 PA2    1   Date of hire.                                                                                                                                                              NS
 PA2    2   Date of rehire.                                                                                                                                                            NS
 PA2    3   First name.                                                                                                                                                                NS
 PA2    4   Middle initial.                                                                                                                                                            NS
 PA2    5   Last name.                                                                                                                                                                 NS
 PA2    6   Former last name.                                                                                                                                                          NS
 PA2    7   Social Security Number (SSN).                                                                                                                                              NS
 PA2    8   Employee Number                                                                                                                                                            NS
 PA2    9   Date of birth.                                                                                                                                                             NS
 PA2   10   Gender.                                                                                                                                                                    NS
 PA2   11   Primary address.                                                                                                                                                           NS
 PA2   12   Secondary address.                                                                                                                                                         NS
 PA2   13   Mailing address.                                                                                                                                                           NS
 PA2   14   Primary phone number.                                                                                                                                                      NS
 PA2   15   Mobile phone number.                                                                                                                                                       NS


                                                                                                 Page 113 of 169
PA2   16   Emergency contact information.                                              NS
PA2   17   Employee Status.                                                            NS
PA2   18   FLSA status (Exempt vs. Non-Exempt).                                        NS
PA2   19   Education                                                                   NS
PA2   20   Current job title.                                                          NS
PA2   21   Current assigned position.                                                  NS
PA2   22   Current assigned FTE value.                                                 NS
PA2   23   Current work schedule.                                                      NS
PA2   24   Current rate of pay.                                                        NS
PA2   25   Current Supervisor or Manager.                                              NS
PA2   26   Current department.                                                         NS
           Current union/bargaining unit/employee association
PA2   27                                                                               NS
           affiliation.
PA2   28   Length of service from date of hire.                                        NS
PA2   29   Uniform/Non-uniform designation.                                            NS
PA2   30   Sworn/Un-sworn designation.                                                 NS
PA2   31 Licensure/Certifications, ID number, and expiration date.                     NS
PA2   32   Languages and proficiency                                                   NS
PA2   33   Special skills and competencies                                             NS
PA2   34   Testing performed and results.                                              NS
PA2   35   Training completed and results.                                             NS
PA2   36   Background check schedule.                                                  NS
           Background check results within user defined history
PA2   37                                                                               NS
           parameters.
PA2   38   Out of state residences.                                                    NS
PA2   39   Performance evaluation schedule.                                            NS
PA2   40   Next performance evaluation date.                                           NS
PA2   41   Performance evaluation score/information.                                   NS
PA2   42   Special assignments.                                                        NS
PA2   43   Disciplinary actions.                                                       NS
           History of disciplinary actions within user defined
PA2   44                                                                               NS
           parameters.
PA2   45   Reported work related injuries.                                             NS
PA2   46   H1B Visa Status.                                                            NS
           Driver's License Number and expiration date if required
PA2   47                                                                               NS
           by position.



                                                                     Page 114 of 169
PA2   48 User-defined reason codes for employee separation.                             NS
PA2   49 Length of time in position(s) and organizational unit(s).                      NS
           User-defined text or date fields and codes for specific
PA2   50                                                                                NS
           employee attributes as needed.
PA2   51   Employee badge number (separate from ID number)                              NS
           Emergency Management information such as special
PA2   52   skills and competencies (which may or may not be job-                        NS
           related).
PA2   53   leave benefits entitlement code                                              NS
PA2   54   benefits enrolment code (for health/dental)                                  NS
           service recognition date (for 10/20/xx year service
PA2   55                                                                                NS
           awards
            - Seniority status and/or ranking based on user defined
PA2   56                                                                                NS
           criteria per employee group.
            - Seniority credit based on user defined criteria per
PA2   57                                                                                NS
           employee group.
PA2   58    - Pre-defined reason codes for employee separation.                         NS
            - All related data to positions occupied other than
PA2   59                                                                                NS
           primary position of employee.
           The system should maintain transactional history for all
PA3        current and former employees - from hire to separation -                     NS
           for management and reporting purposes.
           The system should provide the ability to rehire an
           employee by accessing the deactivated record and
PA4                                                                                     NS
           uploading current data without re-entering the
           employee's information or creating a new hire record.
           The system should provide the ability to allow rehired
           employees to use their previous employee ID based on
PA5        the organization's defined criteria and identify the                         NS
           applicant as a former employee using their former
           number.
           The system should provide for the organization to
           implement Employee Self Service (via an internet portal
PA6        or the organization's intranet) to allow employees to                        NS
           update information such as addresses, phone numbers,
           etc. online.



                                                                      Page 115 of 169
       The system should provide the ability to create
PA7    paperless workflows for personnel transactions and                             NS
       authorizations.
       The system should provide the ability to support
       automated tracking of Management's goals for
PA8                                                                                   NS
       themselves, their teams, their departments, and their
       projects.
       The system should provide the ability to create
PA9    performance evaluations based on a position's current                          NS
       job description and user defined criteria.
       The system should provide the ability to flag employees
PA10   under a Supervisor or Manager's responsibility who                             NS
       have an approaching performance evaluation.
       The system should provide the ability to escalate past
PA11   due performance evaluations to the next level of                               NS
       authority for review.
       The system should provide the ability to update salary
PA12   amounts for each classification via mass pay changes                           NS
       or compensation adjustments
       The system should alert the designated authorities if an
       employee's required licensure or certificate will expire
PA13                                                                                  NS
       within a user defined parameter such as 30 days, 90
       days, etc.
       The system should provide the ability for an employee to
PA14   be assigned to multiple positions simultaneously with                          NS
       one position designated as primary.
       The system should provide the ability to manage
       alternate pay rates in addition to the employee's
PA15   assigned rate of pay for work within a specific function                       NS
       or role that is in addition to the primary or secondary
       position.
       The system should provide the ability to base benefit
PA16   eligibility on a calculated, separate FTE value other than                     NS
       the actual position FTE value.




                                                                    Page 116 of 169
       The system should provide the ability to flag and notify
       Human Resources if an employee's inactive status (e.g.,
PA17                                                                                  NS
       leave status) has exceeded a user-determined amount
       of time.
       The system should provide the ability to indicate a
PA18                                                                                  NS
       reason code and description for personnel actions.
       The system should provide the ability to interface with
PA19   current and historical payroll data allowing authorized                        NS
       users to perform inquiries/reporting.
       The system should provide the ability to cross reference
       an employee's functional abilities and/or medical
PA20   limitations with the requirement of a specific position to                     NS
       prevent an employee from being assigned outside their
       capabilities.
       The system should provide the ability to enter multiple
PA21                                                                                  NS
       personnel actions per employee per payroll cycle.
       The system should provide the ability to enter personnel
PA22                                                                                  NS
       transactions with a future effective date.
       The system should provide the ability to apply a warning
PA23   to a user who enters a personnel transaction with an                           NS
       effective date that is retroactive.
       The system should provide the ability to generate a
PA24   warning on a personnel action for a salary increase that                       NS
       is outside of the allowable range.
       The system should provide the ability to view pending
PA25   personnel transactions based on their status in an                             NS
       automated workflow/approval process.
       The system should date and time stamp each personnel
       transaction when it is created and each time there is an
PA26                                                                                  NS
       action related to the transaction
       (approval/rejection/comments, etc.)
       The system should provide the ability to assign assets to
       an individual employee such as a computer, keys,
PA27   weapon, vehicle, etc. and notify the appropriate                               NS
       authorities upon the processing of any leave or term
       related actions.



                                                                    Page 117 of 169
          The system should provide the ability to record a photo
PA28                                                                                    NS
          of the employee in the employee's online record.
          The system should provide the ability to record
PA29                                                                                    NS
          ID/security badges assigned to an employee.
          The system should provide the ability to interface
PA30                                                                                    NS
          ID/security badges with any timekeeping system.
          The system should provide automatic assignment of
PA31      bargaining units based on job classes or job codes with                       NS
          override capability.
          The system should provide the ability to automatically
PA32      calculate a salary change by entering a percentage or                         NS
          dollar amount change.
          The system should provide the ability to perform salary
PA33                                                                                    NS
          "what-if" modeling.
          The system should provide a user defined
PA34      compensation table to accommodate multiple salary                             NS
          structures.
          The system should allow users to track multiple user
          defined breaks in service, for example breaks resulting
PA35                                                                                    NS
          from a legal settlement, reduction in hours, lay-off, or
          disciplinary action.
          The system should provide the ability to track data
PA36      attributes specific to a job code or position number that
          include, but are not limited to, the following:
PA36 1    Salary range.                                                                 NS
PA36 2    Fair Labor Standards Act (FLSA) status.                                       NS
PA36 3    Workers compensation code.                                                    NS
PA36 4    Diversity information.                                                        NS
PA36 5    Employee type/bargaining unit/employee association                            NS
PA36 6    Licenses, certificates and registration requirements.                         NS
PA36 7    Degree/education requirements.                                                NS
PA36 8    Minimum qualifications/requirements.                                          NS
PA36 9    Management and supervisory level.                                             NS
PA36 10   Physical parameters.                                                          NS
          Americans with Disabilities Act (ADA) by
PA36 11                                                                                 NS
          classification/essential functions.



                                                                      Page 118 of 169
            Status (active, inactive, pending, budgeted, approved
PA36 12                                                                                     NS
            but not budgeted, etc.)
PA36 13 Classification (with title) for Pay Equity/EEO reporting.                           NS
PA36   14   Funding source for position, i.e. grant, internal, etc.                         NS
PA36   15   Name of funding source and ID# if applicable.                                   NS
PA36   16   Length of time funding is awarded.                                              NS
PA36   17    - Record of job classification code(s).                                        NS
PA36   18    - Number of budgeted FTEs per budget year.                                     NS
PA36   19    - Number of current FTEs filled/vacant.                                        NS
PA36   20    - Location of current FTEs filled/vacant.                                      NS
            The system should be able to create mailing lists for use
PA37        in communication to groups of employees with common                             NS
            user defined criteria.
            The system should provide the capability to report on
PA38        work related injuries including employee name, work                             NS
            location, job code, department, Supervisor, etc.
            The system should provide checklists for employee hire
            and termination processes to ensure all steps are
PA39                                                                                        NS
            completed (checklist should include policy and
            agreement documents).
            The system should provide a disciplinary action report in
PA40        a pre-defined and/or user-defined format with user                              NS
            defined variables.
            The system should provide a report of vacancies and
PA41        hires by class and department within a user defined date                        NS
            range.
            The system should provide a report of current
PA42                                                                                        NS
            employees on leave..
            The system should provide a report documenting
            frequency of absenteeism or tardiness by employee, by
PA43                                                                                        NS
            department, by manager or by user defined parameters
            for a specified time range.
            The system should provide the ability to create a labor
            distribution report which identifies labor in hours,
PA44                                                                                        NS
            overtime, position, department, date, time of day or shift,
            etc.



                                                                          Page 119 of 169
       The system should provide the ability to create a
PA45   Probation Status Report at the organizational and                             NS
       individual employee level.
       The system should provide the ability to create an
PA46                                                                                 NS
       anniversary date report by department, month/year, etc.
       The system should provide the ability to create a New
PA47                                                                                 NS
       Hire Report with user defined data attributes.
       The system should provide the ability to create a
PA48                                                                                 NS
       Termination Report with user defined data attributes.
       The system should provide the ability to create a Job
PA49                                                                                 NS
       Class Report.
       The system should provide the ability to create an
PA50                                                                                 NS
       Average Salary Report by class, bargaining unit, etc.
       The system should provide the ability to create a report
PA51                                                                                 NS
       for tuition reimbursement usage.
       The system should provide the ability to create tickler
PA52   notifications for time-dependent events such as                               NS
       forthcoming service awards, etc.
       The system shall provide the ability to create a turnover
       rate report by gender, age, appointment to class, date,
PA53                                                                                 NS
       disciplinary release, promotion, race, classification,
       probation release, transfer and/or resignation, etc.
       The system should provide the ability to generate
PA54   reports based on "what if" modeling for use during                            NS
       bargaining unit negotiations.
       The system should provide the ability to generate
       reports based on a position control number and all data
PA55                                                                                 NS
       related to that position from various tables and
       employee files.
       The system should provide code structures that are
PA56   easily identifiable to ease in report creation and                            NS
       recognition.




                                                                   Page 120 of 169
       The system should provide a robust user-configurable
       security structure -- including attribute-level security -- to
PA57                                                                                      NS
       protect senstive employee data (eg, SSN, medical
       status, address, discipline information, etc) at all times.

       The system should provide a mechanism to track the
PA58   reclassifications of job codes and/or position codes and                           NS
       their history for a user defined period of time.

       Ths system should provide the ability to attach scanned
PA59   documents/images to an employee's master, including                                NS
       photos, resumes, both current and historical, etc.
       The system should provide the ability to track
PA60   employees by occupational category and job groups                                  NS
       according to user-defined criteria.
       General Requirements Average GAP
       SLCO Requirements Section
        - Seniority status and/or ranking based on user defined
PA61                                                                                      NS
       criteria per employee group.
        - Seniority credit based on user defined criteria per
PA62                                                                                      NS
       employee group.
PA63    - Pre-defined reason codes for employee separation.                               NS
        - All related data to positions occupied other than
PA64                                                                                      NS
       primary position of employee.
       The system should provide the ability to access and
PA65                                                                                      NS
       report on employees' transactional history.
       The system should provide the ability to manually assign
PA66   or automatically generate an employee/applicant/retiree                            NS
       number.
       The system should provide the ability to configure
PA67   manager self service tools via the organization's Intranet                         NS
       or via an Internet portal.
       The system should provide the ability to create
PA68   evaluations forms and process forms electronically with                            NS
       full update to the employee's HR and Payroll records.




                                                                        Page 121 of 169
       The system should provide the ability to allow for on-line
PA69                                                                                  NS
       employment verification via an Internet portal.
       The system should provide the ability to consolidate
       multiple positions within one EIN assigned to one
PA70   employee to calculate eligibility and base the level of                        NS
       benefits, leave accrual, premium costs, retirement
       benefits, etc.
       The system should provide the ability to consolidate
       multiple positions within multiple EINs assigned to one
PA71   employee to calculate eligibility and base level of                            NS
       benefits, leave accrual, premium costs, retirement
       benefits, etc.
       The system should provide the ability to perform mass
       changes by user-defined criteria, including but not
PA72                                                                                  NS
       limited to, bargaining unit, class code, etc. and update
       the employee record or appropriate databases.
       The system should provide the ability to establish a
PA73                                                                                  NS
       standard rounding method.
       The system should stamp each personnel transaction
       with the source of the action and the source of any user
PA74                                                                                  NS
       processing the action through an automated workflow
       process.
       The system should provide the ability to escalate any
       personnel transaction to the appropriate next level if the
PA75                                                                                  NS
       assigned processing time period expires at its current
       point in an automated workflow process.
       The system should provide the ability to notify the
       appropriate authorities of assets assigned to an
PA76                                                                                  NS
       employee upon the processing of any leave or term
       related actions.
       The system should provide the ability to build automated
PA77   salary increases based on user defined criteria (e.g.,                         NS
       union, department).




                                                                    Page 122 of 169
       The system should provide the ability to record
PA78   disciplinary actions by employee and to track the                             NS
       employee's progress through any probationary process.

       The system should provide the ability to perform a mass
       change on compensation structures for all employees
PA79   within a user defined group and/or a selected group of                        NS
       employees. This change should update Budget, Position
       Control and the General Ledger.
       The system should provide the ability to create salary
PA80                                                                                 NS
       schedules tied to specific positions.
       Ths system should provide data validation tables to
PA81                                                                                 NS
       ensure data entry accuracy
       The system should provide the capability to override
PA82   specific position attributes at the employee record level                     NS
       with appropriate authorization.
       The system should provide security authorization levels
PA83   for users based on roles and responsibilities and to                          NS
       detail of screens and/or individual fields.
PA84   The system should provide point-in-time reporting.                            NS
PA85   The system should be able to produce mailing labels.                          NS
       The system should provide the ability to create e-mail
PA86   notices or form letters for automated mailings regarding                      NS
       user defined events.
       The system should provide robust reporting capabilities
PA87   to support the management of employees and provide                            NS
       decision support data as needed.
       The system should provide turnover reporting by
PA88                                                                                 NS
       budgeted class, including temporary employees.
       The system should provide user defined reporting by
PA89                                                                                 NS
       position.




                                                                   Page 123 of 169
       The system should provide the ability to track
       employees in all possible states of employment status:
PA90   recruitment, hiring, assigned positions, paid leaves,                         NS
       unpaid leaves, separated, barred (prevented from being
       hired or rehired), absences, etc.
       The system should provide the ability to create an
       employee history report (date hired, date of increases,
PA91                                                                                 NS
       promotions, hourly rates, date of evaluations,
       department changes, etc.).
       The system should provide the ability to report using
PA92   data from all positions - primary and otherwise - for all                     NS
       employees.
       The system should provide the ability to allow
PA93   employees with authorization to access limited reports                        NS
       via the web or their desktop computer.
       The system should provide the ability to create reports
PA94   on position related data with a variety of user chosen                        NS
       parameters.
       The system should provide detailed recap and summary
PA95                                                                                 NS
       reports for EEO reporting.
       The system should provide the ability to create all
PA96                                                                                 NS
       required state and federal reports.
       The system should provide the ability to create a COLA
PA97   History Report by bargaining unit, COLA, effective date,                      NS
       etc.
       The system should provide robust ad hoc reporting tools
PA98                                                                                 NS
       that easily access any employee data field.
       The system should provide the ability to scan
       documents, photos, resumes - both current and
PA99                                                                                 NS
       historical, create an index and attached to the
       employee's electronic record.
       SLCO Requirements Average GAP
       Total GAP




                                                                   Page 124 of 169
SALT LAKE COUNTY                                                                     INSTRUCTIONS                                               RATING LEGEND
Functional Requirements Matrix                                                                                        SUP   Supported as delivered "out-of-the-box"
                                                                        Complete the worksheet by placing an X in           Supported via modifications (screen configurations, reports, GUI
                                                                           the most appropriate column for each       MOD
                                                                                                                            tailoring, etc)
                                                                          criterion. The X's should represent the
                                                                           current state of a particular product or   3RD   Supported via a third party solution
                                                                          service. (More than one response to a       CST   Supported via customization (changes to source code)
                                                                        single requirement will be treated as a non
                                                                                          response)                   FUT   Will be supported in a future release
                                                                                                                      NS    Not supported


                          BENEFITS                                                RATING RESPONSE                                    ADDITIONAL COMMENTS
                                                                         SUP     MOD       3RD      CST      FUT      NS                                                              Resp
 BN        General Operating Requirements Section
           The system should provide the ability to seamlessly
BN1        integrate with other modules within the vendor's                                                                                                                            NS
           HR/Payroll suite.
           The system should provide the structure to designate
           the following data item attributes related to the
BN2
           Organization's employee benefit programs including, but
           not limited to:
BN2   1    Fiscal year.                                                                                                                                                                NS
BN2   2    Budget cycle.                                                                                                                                                               NS
BN2   3    Benefit plans requiring COBRA management.                                                                                                                                   NS
BN2   4    General ledger accounts related to a benefit plan.                                                                                                                          NS
           Payroll frequency specific to each benefit plan's
BN2   5                                                                                                                                                                                NS
           deduction schedule.
BN2   6    Definition of employee salary for benefit calculations.                                                                                                                     NS
           Definition of employee groups for benefit eligibility
BN2   7                                                                                                                                                                                NS
           calculations.
BN2   8    Tax designations for benefit plans impacting W-2s.                                                                                                                          NS
           Annual limitations on benefit plan deductions (401k,
BN2   9                                                                                                                                                                                NS
           403b, 457, spending accounts, etc.)
BN2   10   Vendor identification for each benefit plan.                                                                                                                                NS
BN2   11   Default options for specific benefit plans.                                                                                                                                 NS
BN2   12   Budgeted expense per benefit type per budget year.                                                                                                                          NS
           Budgeted expense per benefit type per benefit plan
BN2   13                                                                                                                                                                               NS
           year.
BN2   14    - Benefit plans covering dependents.                                                                                                                                       NS
BN2   15    - Benefit plans covering retirees.                                                                                                                                         NS
BN2   16    - Benefit plans covering retiree beneficiaries.                                                                                                                            NS
            - Pre-tax designation if benefit plan deductions are non-                                                       Employee makes an election to have benefits taxable or
BN2   17                                                                                                                                                                               NS
           taxable.                                                                                                         nontaxable.
BN2   18    - Definition of rounding rule for calculations.                                                                                                                            NS
            - Employee statuses eligible for benefit plan
BN2   19                                                                                                                                                                               NS
           participation.
           The system should provide the structure to designate
BN3        the following data item attributes related to each
           employee benefit program including, but not limited to:
BN3   1    Plan type.                                                                                                                                                                  NS
BN3   2    Plan name.                                                                                                                                                                  NS
BN3   3    Plan vendor.                                                                                                                                                                NS
BN3   4    Vendor policy identification.                                                                                                                                               NS
BN3   5    Plan beginning date.                                                                                                                                                        NS
BN3   6    Plan ending date.                                                                                                                                                           NS
BN3   7    Coverage type (options, salary based, default, etc.)                                                                                                                        NS
           Contribution type (flat, table driven, salary based, age
BN3   8                                                                                                                                                                                NS
           graded, etc.)
BN3   9    Employee elgibility rules.                                                                                                                                                  NS
BN3   10   Employee waiting period rules.                                                                                                                                              NS
BN3   11   Dependent eligibility rules.                                                                                                                                                NS
BN3   12   Dependent waiting period rules.                                                                                                                                             NS
BN3   13   Evidence of insurability rules for life/STD/LTD plans.                                                                                                                      NS
BN3   14   Premium waiver rules for life/STD/LTD plans.                                                                                                                                NS
BN3   15   Employee contribution schedule.                                                                                                                                             NS
           Covered participants (employees, dependents, retirees,
BN3   16                                                                                                                                                                               NS
           former employees, beneficiaries, etc.)
BN3   17   Vesting schedule, if applicable.                                                                                                                                            NS
BN3   18   Retirement Tier(s)                                                                                                                                                          NS
BN3   19   Coverage termination rules.                                                                                                                                                 NS
BN3   20   Deduction codes.                                                                                                                                                            NS
BN3   21   Tax designation for W-2 handling, if applicable.                                                                                                                            NS
BN3   22   Initial enrollment options.                                                                                                                                                 NS
BN3   23   Effective date of initial enrollment                                                                                                                                        NS
BN3   24   Re-enrollment/reinstatement rules and options.                                                                                                                              NS
BN3   25   Effective date of re-enrollment                                                                                                                                             NS
BN3   26   Coverage options.                                                                                                                                                           NS
BN3   27   Coverage defaults.                                                                                                                                                          NS
BN3   28   Premiums per eligible employee group.                                                                                                                                       NS
BN3   29   Premium cost sharing between employer/employee.                                                                                                                             NS
           Personnel actions impacting benefit plan coverage (hire,
BN3   30                                                                                                                                                                               NS
           transfer, change of status, etc.)




                                                                                        Page 125 of 169
BN3    31 Termination rules.                                                                                                     NS
BN3    32 Flexible Spending Account notices.                                                                                     NS
BN3    33 - Eligible employee groups.                                                                                            NS
           - General ledger accounts related to
BN3    34                                                                                                                        NS
          employee/employer contribution schedule.
BN3    35 - Deduction frequency schedule.                                                                                        NS
BN3    36 - Deduction arrears accumulator.                                                                                       NS
           The system should provide the ability to assign benefit
BN4        plan codes, deduction codes, and related premiums                                                                     NS
           based on employee groups and employee status.
           The system should have the ability to produce form
BN5                                                                                                                              NS
           letters using Microsoft mail merge.
           The system should provide mass change updates for
BN6                                                                                                                              NS
           current and retroactive benefit adjustments.
           The system should provide the ability to prorate benefits
BN7                                                                                                                              NS
           for part-time employees based on user defined criteria.
           The system should provide the ability to calculate
BN8        benefit deduction and employer contribution amounts
           using various methods, including:
BN8    1   flat amount                                                                      Currently 401K 457 requires % only   NS
BN8    2   percentage of wages                                                                                                   NS
BN8    3   age graded                                                                                                            NS
BN8    4   user-defined table of rates                                                                                           NS
BN8    5   client-specific formulas                                                                                              NS
BN8    6   table-driven limits and maximums.                                                                                     NS
           The system should provide the ability to define and track
BN9                                                                                                                              NS
           multiple defined contribution benefit plans.
           The system should have the ability to track vesting and
BN10                                                                                                                             NS
           breaks in service as defined by each benefit plan.
           The system should provide the ability to manage
           retroactive adjustments to employee data based on
BN11                                                                                                                             NS
           retroactive changes to contribution levels, calculation of
           benefits, etc.
           The system should provide the ability to report on
           budgeted vs. actual costs based on user defined criteria
BN12                                                                                                                             NS
           by benefit plan, by plan year, by budget year, including
           employer and employee costs, etc.
           The system should provide the ability to project, report,
           and faciliate the analysis of the cost impact to changes
BN13                                                                                                                             NS
           in benefits, accruals, allowances, etc. for current
           employees, retirees, and all covered participants.
           The system should provide the ability to establish
BN14                                                                                                                             NS
           multiple vendors per plan.
           The system should provide the ability to maintain
           dependent and/or beneficiary information including but
BN15                                                                                                                             NS
           not limited to relationship, date of birth, address, and
           phone.
           The system should provide the ability to track survivor
BN16                                                                                                                             NS
           coverage.
           The system should automatically disenroll an
BN17       employee/retiree from a previous plan when a                                                                          NS
           change/new enrollment of same plan type occurs.
           The system should automatically generate notices to
           departments/functions when an employee is terminating
BN18       or has been on leave with monies due to the                                                                           NS
           organization for loans, tuition reimbursement, or
           benefits.
           The system should provide the ability to print benefits
BN19       statements as needed or on a user defined frequency                                                                   NS
           basis.
           The system should provide the ability to process
BN20       grandfathered eligibility and participation in pension plan                                                           NS
           or other benefit.
           The system should provide the ability to refund benefits
BN21                                                                                                                             NS
           premiums to employees.
           The system should provide the ability to track, bill and
BN22                                                                                                                             NS
           collect benefits costs from employees on leave.
           The system should provide the ability to make current
           cost of living adjustments (COLA) based on user
BN23       defined criteria, including but not limited to, individual,                                                           NS
           group or all retirement plan accounts if payments are
           administered internally.
           The system should provide the ability to generate
           electronic files to vendors for benefit plan billing reports
BN24
           whether invoiced or self billed including, but not limited
           to, the following:
BN24   1   Employee name.                                                                                                        NS
BN24   2   Employee social security number                                                                                       NS
BN24   3   Employee date of birth..                                                                                              NS
BN24   4   Employee address.                                                                                                     NS
BN24   5   Employee coverage election.                                                                                           NS




                                                                          Page 126 of 169
BN24   6Effective date of employee coverage.                                              NS
BN24   7Covered dependents, if applicable for benefit plan.                               NS
BN24   8Covered dependents' names.                                                        NS
BN24   9Relationship of covered dependents.                                               NS
BN24    Covered dependents dates of birth.
       10                                                                                 NS
BN24    Covered dependents social security numbers.
       11                                                                                 NS
BN24    Eligibility status of dependent(s).
       12                                                                                 NS
BN24    Effective date of each covered dependent's coverage.
       13                                                                                 NS
        Covered dependents' address if different from
BN24 14                                                                                   NS
        employee.
BN24 15 Covered dependents other coverage.                                                NS
BN24 16 Covered dependents primary and secondary coverage.                                NS
BN24 17 Covered Retirees participants                                                     NS
BN24 18 Covered COBRA participants                                                        NS
        The system should provide self-service enrollment for
BN25                                                                                      NS
        organization-approved benefit plans.
        System should provide the ability to view information
BN26
        online including, but not limited to, the following:
BN26 1 Employee benefits communication.                                                   NS
BN26 2 Employee benefits elections.                                                       NS
BN26 3 Employee benefits summary plan descriptions.                                       NS
BN26 4 Employee benefits enrollment history.                                              NS
BN26 5 Employee benefit providers' link.                                                  NS
        Employee gross pay, deduction and net pay information
BN26 6                                                                                    NS
        for each pay period.
BN26 7 - Employee leave balance information.                                              NS
BN26 8 - Employee time record history.                                                    NS
        The system should provide the option for self-service
BN27                                                                                      NS
        access to pension fund data for participants.
        The system should provide the ability to define and track
BN28                                                                                      NS
        multiple defined benefit pension plans.
        The system should track employee contributions for
BN29                                                                                      NS
        various retirement plans.
        The system should provide the ability to
BN30    add/modify/delete pension systems, codes, options, and                            NS
        rates and their effective dates.
        The system should provide the ability to generate
BN31    advance notices to employees and dependants who are                               NS
        eligible for Medicare.
        The system should provide the ability to generate form
BN32    letters for retirement plan administration based on                               NS
        various triggers (e.g. date of birth, age).
            The system should provide the ability to track periods of
BN33        non-paid service, based on user defined criteria, for                         NS
            purposes of subtracting from pension service.
            The system should provide the ability to calculate and
BN34        print pension benefit projections for current employees                       NS
            and current pension participants.
            The system should provide the ability to track user
BN35        defined "creditable service" for each retirement plan                         NS
            benefit calculation.
            The system should provide the ability to enter pension
BN36        plan enrollment information and set rates by individual                       NS
            enrollee as well as globally by plan.
            The system should have the ability to track deferred
BN37                                                                                      NS
            retirement benefit plans through the benefit plan set up.

            The system should provide the ability to automatically
            configure and re-configure employee pension
BN38        information (eg, pension plan code and deduction                              NS
            amount) for new hires, re-hires, and transfer between
            retirement plans as needed based on plan rules.

            The system should provide the ability to track and
            maintain benefit information and changes in status for
BN39
            retired employees, surviving spouse and dependents
            that includes, but is not limited to, the following:
BN39   1 Retirement date                                                                  NS
BN39   2 Date of death                                                                    NS
BN39   3 Type of retirement (e.g service, early, disability)                              NS
          Name, social security number, address, telephone
BN39   4 number, and date of birth of beneficiaries both primary                          NS
          and contingent
BN39   5 Dependent coverage eligibility and expiration dates                              NS
BN39   6 Life insurance amount                                                            NS
BN39   7 Base pay                                                                         NS
BN39   8 Last day paid updated from payroll system                                        NS
BN39   9 Last day worked tied to leave status                                             NS
BN39   10 Retire/ rehire status                                                           NS
          Medical coverage provider eligibility and expiration
BN39   11                                                                                 NS
          dates
BN39   12 Medical coverage                                                                NS




                                                                        Page 127 of 169
BN39 13 Remarks                                                                                                                              NS
        The system should provide the ability to process,
                                                                                           Currently outsourcing COBRA, but would like the
BN40    maintain, bill and collect premiums for COBRA benefits
                                                                                           capability if included with the program
        including, but not limited to, the following:
BN40 1 Qualifying event.                                                                                                                     NS
BN40 2 Length of COBRA eligibility.                                                                                                          NS
BN40 3 Expiration dates.                                                                                                                     NS
BN40 4 Covered participants.                                                                                                                 NS
BN40 5 Elected coverage.                                                                                                                     NS
BN40 6 Premium cost.                                                                                                                         NS
BN40 7 Notification and response dates.                                                                                                      NS
BN40 8 Payment history.                                                                                                                      NS
        The system should provide automated notification to
BN41                                                                                                                                         NS
        COBRA enrollees when coverage is going to expire.
        The system should provide the ability to generate a
BN42                                                                                                                                         NS
        "Newly Enrolled/Change Report."
        The system should provide participant reports, including
        but not limited to, enrollment, dependent names and
BN43    relationships, department name, pay group, social                                                                                    NS
        security number, etc. that can be generated by
        individual or group.
        The system should provide the ability to generate
BN44    insurance billing reports including, but not limited to, the
        following:
BN44 1 type of coverage,                                                                                                                     NS
BN44 2 class code,                                                                                                                           NS
BN44 3 employee name                                                                                                                         NS
BN44 4 amount                                                                                                                                NS
BN44 5 number of insured,                                                                                                                    NS
           The system should provide the ability to calculate the
BN45       premium for life and disability insurance each month                                                                              NS
           based on age, coverage level, salary and waiting period.
           General Requirements Average GAP
           SLCO Requirements Section
           The system should provide the ability to create a
BN46       disability retirement report by name, SSN, department,                                                                            NS
           month/year, bargaining unit, etc.
           The system should provide the ability to define benefit
BN47                                                                                                                                         NS
           options and associated costs.
           The system should provide Social Security Number
           (SSN) and EIN on all benefit screens for employee,
BN48                                                                                                                                         NS
           beneficiary or dependent. Only authorized personnel
           may have visibility to the SSN and EIN.
           The system should provide a master screen including
           name, address, phone number, date of birth, date of
BN49       hire, status date, employee identification number, SSN,                                                                           NS
           plan enrollment, etc., with additional screens for plan
           enrollments.
           The system should automatically calculate balance due
BN50       from employee/retiree and create an arrears amount                                                                                NS
           when payroll deduction is less than full amount due.
           The system should not allow a rehired employee to be
BN51                                                                                                                                         NS
           automatically enrolled in old benefits.
           The system should automatically verify benefits status
BN52                                                                                                                                         NS
           based on employee status and eligibility rules.

           The system should provide the ability for an employee
BN53       to have an employee status for benefits eligibility that is                                                                       NS
           different from their position oriented employee status.

           The system should provide the ability to enroll
BN54                                                                                                                                         NS
           employees in multiple plans with one point of data entry.
           The system should "pend" online request for changes or
BN55       updates if participant is required to submit                                                                                      NS
           proof/documentation.
           The system should provide electronic enrollment
BN56                                                                                                                                         NS
           process with user defined frequencies.
           The system should provide automated notice when
BN57       employee / retiree /term / beneficiary becomes                                                                                    NS
           Medicare eligible.
           The system should provide automated benefits letter
           with options based on employee status changes,
BN58                                                                                                                                         NS
           including but not limited to, job data and family status
           changes.
           The system should provide the ability to calculate
BN59       benefit deduction amounts based on user defined table                                                                             NS
           of rates, formulas, and eligibility/coverage rules.
           The system should provide automated benefits letter
           with options based on employee status changes,
BN60                                                                                                                                         NS
           including but not limited to, job data and family status
           changes.




                                                                         Page 128 of 169
       The system should provide the ability to calculate
BN61   benefit deduction amounts based on user defined table                                                             NS
       of rates, formulas, and eligibility/coverage rules.
       The system should provide integration between
BN62                                                                                                                     NS
       accounts receivable and benefits billing.
BN63   The system should provide benefit eligibility tracking.                                                           NS
       The system should provide the ability to track
BN64   employee’s coverage and coverage level based on                                                                   NS
       class and bargaining unit.
       The system should provide the ability to track
BN65   beneficiaries (e.g., for life insurance, final paycheck,                                                          NS
       retirement contributions).
       The system should provide the ability to track COBRA
BN66   eligibility based on Federally defined criteria with the                                                          NS
       ability to enhance but not reduce.
       The system should provide the ability to create
       automated feeds to vendors to process updates to
BN67                                                                                                                     NS
       benefit plan eligibility and billing on a weekly, biweekly,
       monthly, quarterly, or annual basis.
       The system should provide the ability to include all
       covered individuals in any automated vendor feed
BN68   including, but not limited to, employees, employees'                                                              NS
       dependents, retirees, retirees' dependents, COBRA,
       COBRA beneficiaries, employees on leave, etc.
       The system should provide archiving of files for non-
BN69                                                                                   if included with overall system   NS
       responsive COBRA eligible employees.
       The system should provide the ability to set COBRA
BN70   termination dates by individual enrollee (e.g., greater                         if included with overall system   NS
       than 18, 29, or 36 months).
       The system should provide the ability to create online
BN71   benefits information and enrollment options for the                                                               NS
       organization.
       The system should provide the ability to capture
       information on eligible participants who do not normally
BN72                                                                                                                     NS
       reside in the HR database (e.g., retirees, retiree
       beneficiaries).
       The system should provide the ability to create
       notifications regarding benefits to all levels of
BN73                                                                                                                     NS
       participants (COBRA, retirees, etc.) in hard copy and
       electronic format.
       The system should provide the ability to automate
BN74   reconciliation of enrollment information with benefit                                                             NS
       providers.
       The system should provide the ability to have benefit
BN75                                                                                                                     NS
       premiums paid in full or part by the Organization.
       The system should provide the ability to bill and collect
BN76                                                                                                                     NS
       retiree payments for benefit coverage.
       The system should provide the ability to track monthly
BN77                                                                                                                     NS
       retirement payments if applicable for the Organization.
       The system should provide the ability to track pension
BN78                                                                                                                     NS
       plan table history.
       The system should provide the ability to process
BN79                                                                                                                     NS
       retirement plan eligibility based on employee groups.
       The system should provide the optional ability to
BN80                                                                                                                     NS
       perform individual pension calculations.
       The system should provide the optional ability to
       perform group pension calculations for a user defined
BN81                                                                                                                     NS
       group (e.g., based on union, uniform vs. non-uniform,
       department, etc.).
       The system should provide the ability to specify which
BN82                                                                                                                     NS
       pay types are pensionable.
       The system should provide the option to manage retiree
BN83   payment from retirement plans via the payroll/benefits                                                            NS
       modules.
       The system should determine retiree benefit deduction
BN84   frequency and amounts based on retiree pay frequency,                                                             NS
       if retiree pay is managed through the system.
       The system should provide the ability to have applicable
BN85   retirement plan contributions calculated and deducted                                                             NS
       through the payroll system.
       The system should provide the ability to track retirement
BN86                                                                                                                     NS
       benefit cost by plan and by employee.
       The system should provide the ability to track retirement
BN87                                                                                                                     NS
       plan communications with employees and retirees.
       The system should provide the ability to make
       adjustments, with the proper security, to employee
BN88                                                                                                                     NS
       retirement payment amounts and balances, if
       administered through the system.
       The system should provide the ability to suspend and
BN89                                                                                                                     NS
       reinstate retirement plan benefits.




                                                                     Page 129 of 169
        The system should provide the ability to calculate the
        employee's average salary for benefit computation
BN90    purposes based on user defined criteria, including but                           NS
        not limited to, employee pay, base pay, shift differential,
        specified overtime hours, over a defined time period.

        The system should provide the ability track and query
BN91    the following, but not limited to, name, identification                          NS
        number and social security number of participant.
        The system should provide the ability to track an
BN92    employee's salary history (e.g.,, date of hire) when                             NS
        identification number changes.
        The system should provide the ability to track
BN93    employees not eligible to participate in the pension                             NS
        system.
        The system should provide the ability to generate a list
BN94                                                                                     NS
        of retirees and benefit information.
        The system should provide the ability to extract and
BN95    report benefit information and changes in status into a                          NS
        form letter for retiree/beneficiary correspondence.
        The system should track monthly, quarterly and year-to-
BN96                                                                                     NS
        date employee salary and deduction history.
        The system should provide the ability to define and track
BN97                                                                                     NS
        multiple defined benefit pension plans.
        The system should provide the ability to define defined
BN98    benefit and defined contribution eligibility rules on an                         NS
        organizational and benefit plan level.
        The system should provide the ability to configure and
        change employee and employer contribution rates for
BN99    both current and retroactive calculations (e.g.,                                 NS
        calculation of benefits, eligibility rules, retirement plan,
        retirement plan eligibility date etc.)
        The system should provide the ability for the system to
        update an employee's retirement plan eligibility based
BN100                                                                                    NS
        on plan rules and the personnel actions processed on
        the employee's record.
        The system should provide all employees and retirees
        with annual benefit statements, including but not limited
BN101                                                                                    NS
        to, designated beneficiary information and benefits that
        are available to beneficiaries.
        The system should provide the ability to generate
BN102   reporting on a pay period, monthly, quarterly, and                               NS
        annual basis.
        The system should provide a report of terminated
BN103   employees with the reason for termination, date of                               NS
        termination, and benefits code.
        The system should provide the ability to automatically
BN104   identify retirees that are subject to the 1099 reporting                         NS
        requirement.
        The system should provide the ability to report or
BN105   transmit taxable income to the Accounts Payable                                  NS
        Department for 1099 reporting.
        The system should provide the ability to track
BN106   employees by hire date, insurance plan, gender,                                  NS
        department, and bargaining unit, etc.
        The system should provide the ability to manage
        pension eligibility rules and affect an employee's record
BN107                                                                                    NS
        automatically when an employee's job information and
        assignment change.
        The system should provide the ability to generate a Pay
BN108                                                                                    NS
        Period Insurance Report.
        The system should provide the ability to generate an
BN109                                                                                    NS
        Enrollment Report.
        The system should provide the ability to adjust the value
BN110                                                                                    NS
        of the benefits based on retiree elections.
        The system should provide the ability to create an
        electronic feed between the County and insurance
BN111                                                                                    NS
        carriers in a file format that is 834 compliant for HIPAA
        regulations.
        The system should provide the ability to track deferred
BN112                                                                                    NS
        retirement option plans.
        SLCO Requirements Average GAP
        Total GAP




                                                                       Page 130 of 169
SALT LAKE COUNTY                                                                 INSTRUCTIONS                                               RATING LEGEND
Functional Requirements Matrix                                                                                    SUP   Supported as delivered "out-of-the-box"
                                                                    Complete the worksheet by placing an X in           Supported via modifications (screen configurations, reports, GUI
                                                                       the most appropriate column for each       MOD
                                                                                                                        tailoring, etc)
                                                                      criterion. The X's should represent the
                                                                       current state of a particular product or   3RD   Supported via a third party solution
                                                                      service. (More than one response to a       CST   Supported via customization (changes to source code)
                                                                    single requirement will be treated as a non
                                                                                      response)                   FUT   Will be supported in a future release
                                                                                                                  NS    Not supported


                      TRAINING                                                RATING RESPONSE                                    ADDITIONAL COMMENTS
                                                                     SUP     MOD       3RD      CST      FUT      NS                                                              Resp
 TR    General Operating Requirements Section
       The Training module should be fully integrated with
TR1                                                                                                                                                                                NS
       other integrated HR modules.
       The system should provide the ability to interface with
TR2    the training system from the Emergency Management                                                                                                                           NS
       Institute (EMI) for NIMS, FEMA and ICS courses.
       The system should provide the ability to interface with
TR3    the State wide Commission on Peace Officers                                                                                                                                 NS
       Standards and Training (POST).
       The system should provide the ability to track all
       required and optional training, licenses, certifications,
TR4                                                                                                                                                                                NS
       skills, etc., per employee, by topic and job title,
       department.
       The system should provide the ability to track the history
TR5                                                                                                                                                                                NS
       of all training/licensing related activity by department.
       The system should provide the ability to track the last
TR6    activity date and next required action date per employee                                                                                                                    NS
       and per training and licensing requirement.
       The system should track training activities for all types
       of workforce, including full time employees, part time
TR7                                                                                                                                                                                NS
       employees, seasonal workers, interns, temporary
       workers, contractors and volunteers.
       The system should provide the ability to track an
TR8    employee's progress toward completion of certifications,                                                                                                                    NS
       degrees or development (career) path.
       The system should provide the ability to track multiple
TR9    types of tests, along with a pass/fail status and a test                                                                                                                    NS
       score for employees.
       The system should provide the ability to maintain an
TR10   education plan, including recommended course and                                                                                                                            NS
       curriculum by position and/or employee.
       The system should provide the ability to track internally
TR11   sponsored and vendor sponsored training all in one                                                                                                                          NS
       system.
       The system should be able to track multiple or split day
TR12                                                                                                                                                                               NS
       training classes.
       The system should provide the ability to cap or limit the
TR13                                                                                                                                                                               NS
       number of people who can take a class.
       The system should provide the ability to track classroom
TR14   activity for employees who have completed a class, no                                                                                                                       NS
       shows, cancellations, etc.
       The system should enable user defined security in order
       to allow limited access to decentralized departments so
TR15                                                                                                                                                                               NS
       they can only read, write and update to their own
       employee records.
       The system should provide an interface with position
TR16   requirements in order to match requirements to                                                                                                                              NS
       employee profiles.
       The system should provide the ability to monitor training
       effectiveness by obtaining feedback from class
       participants and supervisors. The system should be
TR17                                                                                                                                                                               NS
       able to automatically send a follow up form a certain
       amount of days (as defined by the supervisor) after
       completion of the designated training
       The system should provide the ability to define a training
TR18   schedule based upon the employee's professional                                                                                                                             NS
       development path.
       The system should provide the ability to schedule
TR19                                                                                                                                                                               NS
       training by job title and employee.
       The system should provide a consolidated organization-
       wide training schedule with different view capabilities,
TR20                                                                                                                                                                               NS
       including a calendar, list format. The schedule should
       be able to be viewed by topic, time frame, etc.
       The system should provide the ability for users to
TR21                                                                                                                                                                               NS
       reserve available training facilities.




                                                                                    Page 131 of 169
           The system should provide the ability to survey
TR22       employees to assess the interest level in a particular                         NS
           course.
           The system should provide the ability to track training
TR23                                                                                      NS
           costs by participant, department, program, class, etc.
           The system should allow the HR department to charge
TR24       departments, cancel fees, split charges or charge other                        NS
           agencies for training when appropriate.
           The system should provide the ability to track the
TR25       certificates and training that an individual has received                      NS
           prior to becoming an employee.
           The system should provide a variety of multi-media
           training, such as webinar, video training, PowerPoint
TR26                                                                                      NS
           slides, etc. and allow employees to access the training
           from their work station.
           The system should provide the ability to attach scanned
TR27       certificates, transcripts and other documents to                               NS
           employee training records.
           If a internally sponsored class is attended by outside
           parties (for example, employees from nearby cities,
TR28                                                                                      NS
           schools, etc.), the system should trigger a billing notice
           to Accounts Receivable.
           The system should allows users to enter "wish list"
           courses and notify HR of the need. The system should
TR29                                                                                      NS
           automatically notify the user when the class/training is
           made available.
           The system should provide user defined fields for
TR30                                                                                      NS
           tracking client specific training information.
           The system should provide the ability for electronic
TR31                                                                                      NS
           registration.
           The system should provide for the automated
TR32       integration of registration information to the employee's                      NS
           calendar via Outlook.
           For external courses (offered by a third party), the
TR33       system should provide web links to pre-approved                                NS
           training sites for registration.
           If an employee registers for a training class provided by
TR34       an outside vendor, the system should electronically                            NS
           send class registration costs and other details to AP.
           If an employee uses the self enrollment feature, the
TR35                                                                                      NS
           system should provide a confirmation notification.
           Once registration information is entered into the system,
TR36       the data should automatically flow into the Training                           NS
           module without the need for duplicate entry.
           The system should provide the ability for users with
TR37       appropriate security access to view enrollment data by                         NS
           employee and by course.
           The system should provide the ability to generate
           reports for individuals, departments, and divisions with
TR38                                                                                      NS
           individual training history for employees and user
           defined group statistics.
           The system should provide the ability to issue and print
TR39       in-house certificates for those employees who are in (or                       NS
           who successfully completed) a course.
           The system should provide the ability to inquire and
TR40       report on the employees that have not taken a required                         NS
           class.
           The system should provide the following reporting
TR41
           capabilities:
           Easy to use standard and ad-hoc report writing
TR41   1                                                                                  NS
           capabilities.
           The system should provide for a Compliance Year End
TR41   2                                                                                  NS
           Review Report.
           All reports should have the ability to be run by a user
TR41   3                                                                                  NS
           defined date range.
           Reporting should be decentralized based on security
TR41   4   profiles allowing each decentralized group to only view                        NS
           their own data.
           The system should be able to track the degrees or
TR42       certificates an employee has completed through the                             NS
           Tuition Reimbursement program
           The system should enable the integration of training
TR43       reimbursement payment requests with Accounts                                   NS
           Payable
           The system should enable the tracking of individual use
TR44                                                                                      NS
           of Tuition Reimbursement in a fiscal year.
           For tuition reimbursements, the system should provide
TR45
           the ability to track the employee's:
TR45   1   Participation level                                                            NS
TR45   2   Amount of money budgeted                                                       NS
TR45   3   Amount of money spent                                                          NS
TR45   4   School attended                                                                NS
TR45   5   Goals achieved                                                                 NS




                                                                        Page 132 of 169
TR45   6 Degree(s) earned                                                               NS
         If an employee terminates prior to finishing up courses
         taken through the Tuition Reimbursement Program, the
TR46                                                                                    NS
         system should trigger a notification to HR for partial
         recoupment of the reimbursement.
         The system should provide the ability to provide
TR47     automated reminder notices of internally scheduled                             NS
         training courses.
          The system should have the ability to generate an
TR48      automatic notification when a class reaches maximum                           NS
          capacity and has a wait list of a user defined number.
          The system should provide electronic training approval
TR49                                                                                    NS
          routing based on user defined routing paths.
          The electronic workflow tools should also include an
          auto-escalation process. For example, if an employee
          has a required training or does not show up for a class,
TR50      the system should automatically alert his/her immediate                       NS
          supervisor. If the supervisor does not deal with the
          issue, then the process should escalate up to the next
          level.
          The system should provide for automated notification
TR51      when certifications, contracts and licenses, etc. are                         NS
          about to expire.
          The system should provide employee self service
TR52      access to allow employees to review their individual                          NS
          training and licensing information on file.
          The system should provide the ability to notify a
TR53      supervisor when training for one of their employees is                        NS
          due within a user defined period of time.
          The system should provide the ability to develop and
TR54      maintain comprehensive course development data (i.e.:
          course catalogue), including, but not limited to:
TR54 1    Course Title                                                                  NS
TR54 2    Course Dates and Times                                                        NS
TR54 3    Course ID number/code number                                                  NS
TR54 4    Course description                                                            NS
TR54 5    Course capacity                                                               NS
TR54 6    Course category                                                               NS
TR54 7    Course learning objective                                                     NS
TR54 8    Course duration                                                               NS
TR54 9    Course prerequisite                                                           NS
TR54 10   Facility requirements                                                         NS
TR54 11   Equipment requirements                                                        NS
TR54 12   Training material requirements                                                NS
          The system should provide the ability to create
          transcripts of employee development activity for use by
TR55                                                                                    NS
          the employee and the supervisor. The transcripts should
          be accessible electronically.
          General Requirements Average GAP
          SLCO Requirements Section
          The system should provide the ability to track employee
TR56                                                                                    NS
          skills
          The system should provide a report of all training for
TR57                                                                                    NS
          one employee.
          The system has the ability to review current training and
          certifications of employees and recommendation of
TR58                                                                                    NS
          employee training plans that relate to their specific
          position or job function.
          The system should provide the ability to notify
          supervisor when employee completes the training;
TR59      automatically send a follow up form to the supervisor 90                      NS
          days after completion of designated training to assess
          the impact of the training on performance.
          The system should provide the capability to set up a link
          between the software and the curriculum if training
          requires certification by another agency such as IAFC,
TR60                                                                                    NS
          NFPA, DOD, CESPP, EMS, DOJ, PHTLS, ACLS,
          American Heart Association, FAA, OSHA, NIOSH, FBI,
          ATF, etc.
          The system should provide users the ability to track the
TR61      history of performance in certain classes (what                               NS
          percentage passed/failed) and instructors
          The system should provide an electronic calendar
          capability which can be updated from Human
TR62                                                                                    NS
          Resources and accessible to employees via a Web
          portal.
          The system should provide for an employee to enroll in
          training posted to the electronic calendar via a Web
TR63                                                                                    NS
          portal allowing on line enrollment and update of the
          calendar.




                                                                      Page 133 of 169
       The system should provide the ability for Human
       Resources or Department Heads to enroll employees
TR64   within their scope of responsibility in training sessions                     NS
       either through the HR module or through the use of
       Outlook.
       SLCO Requirements Average GAP
       Total GAP




                                                                   Page 134 of 169
SALT LAKE COUNTY                                                                        INSTRUCTIONS                                               RATING LEGEND
Functional Requirements Matrix                                                                                           SUP   Supported as delivered "out-of-the-box"
                                                                           Complete the worksheet by placing an X in           Supported via modifications (screen configurations, reports, GUI
                                                                              the most appropriate column for each       MOD
                                                                                                                               tailoring, etc)
                                                                             criterion. The X's should represent the
                                                                              current state of a particular product or   3RD   Supported via a third party solution
                                                                             service. (More than one response to a       CST   Supported via customization (changes to source code)
                                                                           single requirement will be treated as a non
                                                                                             response)                   FUT   Will be supported in a future release
                                                                                                                         NS    Not supported


                  POSITION CONTROL                                                   RATING RESPONSE                                    ADDITIONAL COMMENTS
                                                                            SUP     MOD       3RD      CST      FUT      NS                                                              Resp
 PC        General Operating Requirements Section
           The system should provide tracking of the following data
PC1        attributes related to each position. At a minimum, the
           system should include:
PC1   1    Location                                                                                                                                                                       NS
PC1   2    Job classification                                                                                                                                                             NS
PC1   3    History of Job/Position classification                                                                                                                                         NS
PC1   4    Current position title                                                                                                                                                         NS
PC1   5    History of position titles.                                                                                                                                                    NS
PC1   6    Exempt vs. Non-Exempt.                                                                                                                                                         NS
PC1   7    History of exempt vs. non-exempt.                                                                                                                                              NS
           Multiple employee grouping fields (Dept, Division,
PC1   8                                                                                                                                                                                   NS
           Group, Unit, Sub-unit)
PC1   9    History of employee groups.                                                                                                                                                    NS
PC1   10   Current job code.                                                                                                                                                              NS
PC1   11   History of job codes.                                                                                                                                                          NS
PC1   12   Position description                                                                                                                                                           NS
PC1   13   History of position description.                                                                                                                                               NS
PC1   14   Position status                                                                                                                                                                NS
PC1   15   Number of employees in same position                                                                                                                                           NS
PC1   16   Job skills                                                                                                                                                                     NS
PC1   17   Training requirements                                                                                                                                                          NS
PC1   18   Educational requirements.                                                                                                                                                      NS
PC1   19   Licenses, certificates and registration requirements                                                                                                                           NS
PC1   20   Testing requirements,                                                                                                                                                          NS
PC1   21   Grade Level                                                                                                                                                                    NS
PC1   22   History of grade level.                                                                                                                                                        NS
PC1   23   Minimum requirements                                                                                                                                                           NS
PC1   24   Management and supervisory level                                                                                                                                               NS
PC1   25   Physical parameters/Physical Demands Analysis                                                                                                                                  NS
           American Disabilities Act (ADA) by
PC1   26                                                                                                                                                                                  NS
           classification/essential functions
PC1   27 Classification (with title) for Pay Equity/EEO Reporting.                                                                                                                        NS
PC1   28   Workers compensation/WSIB code                                                                                                                                                 NS
PC1   29   Diversity information                                                                                                                                                          NS
PC1   30   Employee type/Employee Association                                                                                                                                             NS
PC1   31   Union/Collective Bargaining Unit                                                                                                                                               NS
PC1   32   Sub-union                                                                                                                                                                      NS
PC1   33   FICA Status                                                                                                                                                                    NS
PC1   34   Civil Service Status                                                                                                                                                           NS
           User comment section for each change to position
PC1   35                                                                                                                                                                                  NS
           structure.
PC1   36   Date created                                                                                                                                                                   NS
           Date and time stamp of each change to position
PC1   37                                                                                                                                                                                  NS
           structure.
PC1   38   Expiration date                                                                                                                                                                NS
PC1   39   Position review dates/ frequency code                                                                                                                                          NS
PC1   40   Budgeted beginning/end dates                                                                                                                                                   NS
PC1   41   Budgeted/un-budgeted status                                                                                                                                                    NS
PC1   42   Funding source for position, i.e. grant, internal, etc.                                                                                                                        NS
PC1   43   Name of funding source and ID# if applicable.                                                                                                                                  NS
           History of funding source for position, i.e. grant, internal,
PC1   44                                                                                                                                                                                  NS
           etc.
PC1   45   History of pay schedules and steps.                                                                                                                                            NS
           Organizational codes (such as department, division,
PC1   46                                                                                                                                                                                  NS
           cost center, etc.)
PC1   47   Pay schedule and step                                                                                                                                                          NS
           Miscellaneous user-defined fields for unspecified client-
PC1   48                                                                                                                                                                                  NS
           specific tracking.
PC1   49    - Number of FTEs/hours per position                                                                                                                                           NS
PC1   50    - History of FTEs assigned per budget year.                                                                                                                                   NS
PC1   51    - Number of current FTEs filled/vacant.                                                                                                                                       NS
PC1   52    - Location of current FTEs filled/vacant.                                                                                                                                     NS
PC1   54    - History of length of time funding is awarded.                                                                                                                               NS
           The system should provide the ability to designate the
PC2        number of authorized positions by department and                                                                                                                               NS
           classification code.
           The system should provide the ability to assign multiple
PC3                                                                                                                                                                                       NS
           employees to a single position.




                                                                                           Page 135 of 169
       The system should provide the ability for employees to
PC4    be assigned to and paid from multiple positions in                               NS
       different funds, organizational units, classes, status, etc.
       The system should provide the ability to track position
       history for each position including date created, date
PC5                                                                                     NS
       authorized, funding history, budgeted positions by year,
       etc.
       The system should provide the ability to designate a
       position as "on hold" or "pending" with an explanatory
PC6                                                                                     NS
       comment, for example, a position that is pending full
       budget approval.
       The system should provide a standardized job
PC7                                                                                     NS
       description format.
       The system should provide decentralized job description
       maintenance (with appropriate security authorization
PC8                                                                                     NS
       structure) with automated workflow for approval through
       HR.
       The system should provide the ability to forecast payroll
       costs over various "what if" scenarios for analysis and
PC9    budgeting purposes by applying user defined criteria                             NS
       such as percentage change in earnings, change in
       FTEs, leaves of absence, payroll factors, etc.

       The system should provide the ability to establish and
PC10                                                                                    NS
       maintain a unique position identifier for each position.
       The system should provide the ability to track user
PC11   defined reasons for increased salaries or grades related                         NS
       to a position.
       The system should provide the ability to change funding
       sources associated with positions with full integration
PC12                                                                                    NS
       and update of related employee records upon
       processing of the change.
       The system should provide the ability to change position
       characteristics associated with positions with full
PC13                                                                                    NS
       integration and update of related employee records
       upon processing of the change.
       The system should provide the ability to log and report
PC14                                                                                    NS
       on progress of position fulfillment efforts.
       The system should provide the ability to prevent an
       employee from being processed without a valid position
PC15                                                                                    NS
       control number (with the ability to override this control
       feature given the appropriate authorization).
       The system should provide the ability to use an
       alternative "fast track" approach to fulfilling a position,
PC16                                                                                    NS
       (i.e. an override transaction, a pending status, etc. with
       appropriate authorization).
       The system should provide the ability to value budgeted
       positions in different ways (e.g., by dollar amount, by full
PC17   time equivalent (FTE), by Annual Person Unit, by                                 NS
       Hours) and within different periods (Month, Calendar
       Year, Fiscal Year.)
       The system should provide the ability to track variances
PC18   between budgeted and actual costs by position, by                                NS
       business entity, by department, by FTEs, etc.
       The system should provide edits to prevent action on a
PC19                                                                                    NS
       position which is not authorized and budgeted.
       The system should provide the ability to create salary
PC20                                                                                    NS
       schedules that are tied to specific positions.
       The system should provide the ability to track and report
       on filled and vacant positions by position number,
PC21   budgeted vs. non-budgeted, pending, department, date                             NS
       range, union affiliation, or other user defined
       parameters.
       The system should provide the ability to prioritize the
PC22                                                                                    NS
       use of funding from multiple sources for a position.
       The system should provide the ability to perform mass
       changes by user-defined criteria, including but not
PC23                                                                                    NS
       limited to, bargaining unit, class code, etc. and update
       the employee record or appropriate databases.
       The system should provide the ability to support
PC24   budgeting in annual, multi-year or user defined                                  NS
       increments.
       The system should provide the functionality to establish
PC25   a baseline position budget, process changes that occur                           NS
       during the year and create a new baseline if needed.

       The system should provide automated workflow tools to
PC26                                                                                    NS
       facilitate the request and approval process for positions.




                                                                      Page 136 of 169
       The system should provide the ability to create a
       position with automatic promotions based on specific
PC27   user defined criteria such as requirements based on a                          NS
       union agreement or Memorandum of Understanding
       (MOU).
       The system should link or integrate with the base
PC28                                                                                  NS
       financial system's position budgeting information.
       The system should have the ability to designate a Job or
PC29   Position as critical for Emergency Management                                  NS
       purposes.
       General Operating Requirements Average GAP
       Reporting Requirements Section
       The system should allow for reporting on positions
PC30                                                                                  NS
       underfilled per their assigned FTE per budget year
       The system should allow for reporting on history of
PC31                                                                                  NS
       FTEs assigned per budget year.
       The system should allow for reporting on the number of
PC32                                                                                  NS
       employees in same position
       The system should be able to report on the history of
PC33                                                                                  NS
       location of current FTEs filled/vacant per position.
       The system should be able to track and report on
PC34                                                                                  NS
       diversity information in relation to a position.
       The system should be able to track and report on the
PC35                                                                                  NS
       number of current FTEs filled/vacant.
       The system should be able to track and report the
PC36                                                                                  NS
       location of current FTEs filled/vacant.
       The system should be able to report on the number of
PC37                                                                                  NS
       budgeted FTEs per budget year.
       Reporting Requirements Average GAP
       SLCO Requirements Section
       The system should provide the ability to assign an
PC38                                                                                  NS
       employee to multiple positions.
       The system should provide the ability to track history of
       authorized or unauthorized positions separate from
PC39   incumbents with totals by user-defined criteria, including                     NS
       but not limited to, fund code, department, project
       number, location, etc.
       The system should provide online job descriptions
       including job duties, educational and skills requirements,
PC40   experience requirements, credentialing/licenses/permits                        NS
       requirements, physical parameters, EEO classification,
       union affiliation(s) etc.
       The system should be able to report on the follow
       elements which are not part of the job descriptino.
       educational and skills requirements, experience
PC41                                                                                  NS
       requirements, credentialing/licenses/permits
       requirements, physical parameters, EEO classification,
       union affiliation(s) etc.
       The system should provide position control at the
PC42                                                                                  NS
       department level with inquiry and print capability.
       The system should provide the ability to reclassify
PC43   positions without extensive rebuilding of table driven                         NS
       attributes.
       The system should provide the ability to identify
PC44                                                                                  NS
       positions that may be "fast tracked."
       The system should provide the ability to assign various
PC45   statuses to a position (e.g., active, inactive, on hold,                       NS
       proposed, etc.)
       The system should provide the ability to create and
PC46   maintain position definitions/classifications with rules                       NS
       and salary ranges/tables.
       The system should provide the ability to open and close
PC47                                                                                  NS
       a position for recruitment.
       The system should interface with the applicant tracking
PC48   system and auto update changes to position from the                            NS
       PC system to the ATS.
       The system should provide the ability to revise and
       update any table driven attributes through a user friendly
PC49   interface such as position numbers, number of FTEs                             NS
       approved per position, department/division numbers
       and/or titles without complete re-creation of the table.
       The system should provide the ability to create a set of
PC50                                                                                  NS
       standard reports related to position control.
       The system should provide the ability to create ad hoc
PC51                                                                                  NS
       reports based on user defined criteria.
       The system should provide the ability to charge the
PC52   funding source for a position based on effective dates                         NS
       (e.g., grant funded positions).
       The system should provide the ability to assign correct
PC53   level of benefits, retirement, etc. to employees with                          NS
       multiple positions.




                                                                    Page 137 of 169
       The system should provide the ability to link historical
       records as job codes or positions codes change and
PC54                                                                                NS
       create links within an employee’s job code/position code
       history.
       SLCO Requirements Average GAP
       Total GAP




                                                                  Page 138 of 169
SALT LAKE COUNTY                                                                      INSTRUCTIONS                                               RATING LEGEND
Functional Requirements Matrix                                                                                         SUP   Supported as delivered "out-of-the-box"
                                                                         Complete the worksheet by placing an X in           Supported via modifications (screen configurations, reports, GUI
                                                                            the most appropriate column for each       MOD
                                                                                                                             tailoring, etc)
                                                                           criterion. The X's should represent the
                                                                            current state of a particular product or   3RD   Supported via a third party solution
                                                                        service. (More than one response to a single   CST   Supported via customization (changes to source code)
                                                                             requirement will be treated as a non
                                                                                           response)
                                                                                                                       FUT   Will be supported in a future release
                                                                                                                       NS    Not supported


                           PAYROLL                                                 RATING RESPONSE                                    ADDITIONAL COMMENTS
                                                                         SUP      MOD       3RD      CST      FUT      NS                                                              Resp
 PY        General Operating Requirements Section
           The system should provide the ability to interface payroll
           information to and from Human Resources,
 PY1       Timekeeping, Leave Management, Benefits                                                                                                                                      NS
           Administration, General Ledger, Grants/Projects and
           other financial modules.
           The system should provide the ability to interface with
           the Accounts Payable module to create payment to
 PY2       specified vendors or agencies for deductions taken from                                                                                                                      NS
           employees' payroll checks each pay cycle or at a user
           defined frequency.
           The system should track an unlimited number of
 PY3
           earnings/pay codes, including but not limited to:
 PY3   1   Regular                                                                                                                                                                      NS
 PY3   2   Overtime                                                                                                                                                                     NS
 PY3   3   Double Time                                                                                                                                                                  NS
 PY3   4   Bonuses                                                                                                                                                                      NS
 PY3   5   Premium Pay                                                                                                                                                                  NS
 PY3   6   Vacation                                                                                                                                                                     NS
 PY3   7   Holiday                                                                                                                                                                      NS
 PY3   8   Shift Differentials                                                                                                                                                          NS
 PY3   9   Function Pay                                                                                                                                                                 NS


                                                                                                  Page 139 of 169
PY3   10   Sick Pay                                                                     NS
PY3   11   Personal Days                                                                NS
PY3   12   Comp Time                                                                    NS
PY3   13   Meals and Lodging Reimbursement                                              NS
PY3   14   Auto and Mileage Reimbursement                                               NS
PY3   15   Relocation Reimbursement                                                     NS
PY3   16   Employee Association Dues                                                    NS
PY3   17   Uniform Allowance                                                            NS
PY3   18   Longevity                                                                    NS
PY3   19   Garnishments                                                                 NS
PY3   20   Retroactive Adjustment                                                       NS
PY3   21   Miscellaneous Expense reimbursement                                          NS
PY3   22   User Defined Earnings                                                        NS
PY3   23   Bond Calculation                                                             NS
PY3   24   Charity Tracking                                                             NS
           The system should provide the ability to create multiple
           definitions of pay cycles and pay periods including but
PY4                                                                                     NS
           not limited to weekly, biweekly, semi-monthly, monthly,
           27-day cycle, etc.
           The system should provide the ability to group
           employees by common attributes within any
PY5                                                                                     NS
           organizational unit without having to set up multiple
           employee records for each unit.
           The system should provide the ability to pay an
PY6        employee at more than one pay rate within a single pay                       NS
           period.
           The system should provide the ability to pay
PY7        reimbursements through payroll (e.g., mileage, tuition                       NS
           subsidies, etc.).
           The system should provide the ability to calculate
PY8                                                                                     NS
           Workers Compensation gross pay and leave.
           The system should provide the ability to make
PY9        adjustments to W-4 data such as taxable earnings,                            NS
           deductions, etc.




                                                                      Page 140 of 169
       The system should provide the ability to allocate an
       employee's earnings and benefits to more than one
PY10   organizational unit, job code,or project code and to track                     NS
       the labor distribution throughout the relevant General
       Ledger accounts based on percentages or time entries.
       The system should provide the ability to default basic
PY11   pay and deduction codes for new hires based on user                            NS
       defined employee groups and parameters.
       The system should provide the ability to restrict the use
       of pay and deductions codes based on user defined
PY12                                                                                  NS
       criteria linking codes to specific employee groups,
       payroll groups, or bargaining units.
       The system should provide the ability to link deduction
PY13                                                                                  NS
       codes to specific payroll cycles and frequency cycles.
       The system should provide the ability to default earning
       and deduction codes from the earning and deduction
PY14                                                                                  NS
       master based on, but not limited to, the payroll
       organizational unit or group.
       The system should provide the ability to locate and
PY15   display employee data based on SSN, employee                                   NS
       identifier and/or name.
       The system should provide the ability to locate and
PY16   display employee information using partial values (eg, a                       NS
       portion of a name) or wild card values.
       The system should provide the ability to make mass
       changes to earnings, deductions, and rate amounts by
PY17                                                                                  NS
       bargaining unit, employee group or any other defined
       criteria.
       The system should provide the ability to calculate tax
       witholding based on a percentage, flat amount, or
PY18   percentage plus flat amount and/or interface with tax                          NS
       software to ensure updated tax tables are used at all
       times for employer/employee tax deductions.




                                                                    Page 141 of 169
       The system should provide the ability to perform pay
PY19                                                                                  NS
       period, month end, quarter end, and year end accruals.
       The system should have the ability to calculate an
       amount needed for accruing compensated absences,
PY20                                                                                  NS
       including but not limited to, FICA and Medicare in
       accordance with GASB requirements.
       The system should provide edit and validation codes
PY21                                                                                  NS
       that are both system and user defined.
       The system should provide the ability to create user
PY22   defined and/or multiple formulas for complex earning                           NS
       and deduction codes.
       The system should provide the automated calculation of
PY23                                                                                  NS
       shift differential based on rules for employee groups.

       The system should provide the ability to create and track
       employee deductions per employee/retiree for benefit
PY24   payments deducted from the employee's paycheck                                 NS
       including, but not limited to, insurance plans, retirement
       plans, voluntary plans, non-voluntary plans, etc.
       The system should calculate all types of current
PY25                                                                                  NS
       garnishments or garnishments in arrears.
       The system should provide the ability to store and print
       information (plaintiff’s address, employee name, SSN,
PY26                                                                                  NS
       date paid and amount paid) needed for answering court
       orders.
       The system should provide the ability to calculate
PY27   interest due on garnishments, by court order, based on                         NS
       a dollar amount and/or percentage.
       The system should provide the ability to impose user-
PY28                                                                                  NS
       defined cap for earnings and deductions.
       The system should provide the ability to develop user-
PY29   defined effective dates, anniversary dates, and                                NS
       expiration dates for earnings and deductions.




                                                                    Page 142 of 169
       The system should provide the ability to calculate
PY30   vacation and sick leave accruals on partial pay periods                        NS
       for both hourly and salaried employees.
       The system should provide the ability to pay employees
PY31   for authorized hours from multiple assignments up to a                         NS
       user-defined limit.
       The system should provide the ability to perform
PY32   retroactive pay adjustments by individual, bargaining                          NS
       unit, and any other user defined criteria.
       The system should provide the ability to calculate
PY33   retroactive pay for a special alternate pay rate as                            NS
       needed based on user defined criteria.
       The system should provide the ability for self service
       calculation of employee paycheck amount through a
PY34                                                                                  NS
       "what if" modeler allowing changes to deductions, pay
       rates, withholding allowances, etc.
       The system should provide the ability to establish a final
PY35   cutoff flag for terminated employees to prevent further                        NS
       timesheet processing and check printing.
       The system should provide the ability to pay an
PY36   automobile allowance at different rates per employee at                        NS
       user-defined frequencies.
       The system should provide the ability to void/reverse
       checks including cancellation of a payroll direct deposit
PY37                                                                                  NS
       (with audit trail and accompanying adjustments to
       General Ledger)
       The system should provide the ability to take deductions
PY38   and apply special earnings outside of the regular pay                          NS
       cycle (e.g., special pay).
       The system should provide the ability to produce and/or
PY39   allow direct deposit payments to be made to multiple                           NS
       banks or payees for each employee.
       The system should provide the ability to automatically
PY40   adjust liability values in the General Ledger as a result                      NS
       of adjustments to the accrual balances or pay rates.




                                                                    Page 143 of 169
           The system should provide the ability to adjust
PY41       retirement contributions as a result of retroactive pay                        NS
           adjustments and/or changes in retirement systems.
           The system should provide the ability to select and print
PY42                                                                                      NS
           payroll checks by user defined groups.
           The system should provide the ability to eliminate the
           processing and distribution of check stubs by allowing
PY43       payment information to be accessible, viewable, and                            NS
           printable to authorized users and employees via an on-
           line portal.
           The system should provide the ability to void an entire
PY44       payroll and re-run it if significant errors are discovered                     NS
           after the payroll has been run and posted.
           The system should provide the ability to calculate
           contributions and set maximums on deductions related
PY45                                                                                      NS
           to benefit plans, retirement plans and any other user
           defined deductions code.
           The system should provide the ability to designate an
PY46       employee, a group, a division, or a company as exempt                          NS
           from FICA tax and reporting.
           The system should provide the ability to track employee
PY47                                                                                      NS
           paid benefits for an employee on a non-paid status.
           The system should provide for pro-rated calculations for
PY48                                                                                      NS
           mid-period hires, rate changes, and terminations.
           The system should provide support for automatic and
PY49       manual wage adjustments, in accordance with federal
           and/or state/provincial requirements in regards to:
PY49   1   Garnishment                                                                    NS
PY49   2   Child Support                                                                  NS
PY49   3   Federal and local levies                                                       NS
PY49   4   Bankruptcies                                                                   NS
PY49   5   Other wage assignment computations                                             NS
PY49   6   Any combination of the above                                                   NS
           The pay stub provided by the system should, at a
PY50
           minimum, include the following:



                                                                        Page 144 of 169
PY50   1 Social Security Number                                                         NS
PY50   2 Employee Number.                                                               NS
PY50   3 Organizational unit number (dept, division, project, etc.)                     NS
PY50   4   Employee name.                                                               NS
PY50   5   Pay period begin/end dates.                                                  NS
PY50   6   Issue date.                                                                  NS
PY50   7   Pay rate per earnings code.                                                  NS
PY50   8 Message field for general or employee specific notes.                          NS
PY50 9 Gross earnings.                                                                  NS
PY50 10 Adjusted taxable earnings.                                                      NS
PY50 11 Medicare earnings.                                                              NS
        All earning and deduction types adequately itemized on
PY50 12                                                                                 NS
        each stub and defined by taxability status.
PY50 13 Withholding status.                                                             NS
PY50 14 Current and Year to Date Totals.                                                NS
PY50 15 Federal Income tax.                                                             NS
PY50 16 FICA/Social Security tax.                                                       NS
        Employer contribution/employee contribution amount for
PY50 17                                                                                 NS
        any user defined deduction code.
PY50 18 State tax                                                                       NS
PY50 19 Direct deposit (multiple accounts)                                              NS
PY50 20 Medicare tax.                                                                   NS
PY50 21 Vacation hours balance                                                          NS
PY50 22 Sick leave hours balance                                                        NS
PY50 23 Other leave hours balances                                                      NS
PY50 24 Other deductions and amounts                                                    NS
PY50 25 Total deductions                                                                NS
PY50 26 Net pay                                                                         NS
PY50 27 - Group insurance.                                                              NS
PY50 28 - Taxable/non-taxable earnings                                                  NS
PY50 29 - Workers’ comp (injury leave)                                                  NS
PY50 30 - Direct deposit portion                                                        NS
PY50 31 - Dates of service                                                              NS
PY50 32 - Location of service                                                           NS




                                                                      Page 145 of 169
           The system should provide all mandated governmental
PY51                                                                                      NS
           reports.
           The system should provide the ability to inquire or run
           reports on earnings balances based on a variety of time
PY52       periods, including but not limited to pay period, monthly,                     NS
           quarterly, year-to-date, fiscal year-to-date, and
           employee service-to-date.
            The system should have the ability to provide
PY53       garnishment reports, including but not limited to the
           following:
           Garnishment report of employees after each payroll run
PY53   1   who have active garnishment on their payroll record and                        NS
           have been garnished.
           Garnishment insufficient fund report after each payroll
           run to identify employees who have active garnishment
PY53   2                                                                                  NS
           on their payroll record but did not earn enough to be
           garnished.
           Garnishment warrant report (issued to creditors) drawn
PY53   3                                                                                  NS
           from garnished employees.
           Garnishment report after each payroll run of employees
PY53   4                                                                                  NS
           whose garnishment has been satisfied.
         Garnishment report after each payroll run to identify
         employees who have active garnishment on their payroll
PY53   5                                                                                  NS
         record but the employee has a termination pending or
         termination action processed within that payroll cycle.
         The system should provide the ability to produce reports
PY54
         including, but not limited to:
         Payroll register per organizational unit per standard
PY54   1                                                                                  NS
         and/or supplemental payroll cycle.
         Deduction registers per deduction per standard and/or
PY54   2                                                                                  NS
         supplemental payroll cycle.
         Labor distribution by General Ledger code, by
PY54   3 organizational unit or any other user defined parameters                         NS
         per standard and/or supplemental payroll cycle.
PY54   4 Overtime and compensatory time accruals by period                                NS



                                                                        Page 146 of 169
         FMLA, stand-by hours, extended leave, safety leave,
         awarded hours, excused absence, unexcused absence,
PY54   5                                                                                NS
         suspension, worker's compensation and non-pay
         activities including the reason and description.
         Planned and actual absentee time and the related costs,
PY54   6                                                                                NS
         including costs of associated fringe benefits.
         Employee vacation schedules reflecting approved
PY54   7                                                                                NS
         requests.
          - Tax register per standard and/or supplemental Payroll
PY54   8                                                                                NS
         cycle.
         The system should provide the ability to create
         deduction overrides for one time adjustments or
PY55     transactions which are temporary. (For example, the                            NS
         need to change the direct deposit to savings only for
         one check.)
         General Requirements Average GAP
         SLCO Requirements Section
         The system should provide the ability to calculate
         earnings per employee based on employee pay
         attributes, taxes based on tax tables as mandated by
PY56                                                                                    NS
         Federal and State requirements, and deduct expense
         deductions assigned to the employee arriving at a net
         pay check value.
         The system should provide a hierachical code structure
         within the organization (i.e. Company, EIN, Business
PY57                                                                                    NS
         Unit, Division, Department, Employee Groups,
         Employees
         The system should provide the ability for General
PY58     Ledger and Project Ledger distribution based upon                              NS
         timesheet data.
         The system should provide the ability to allocate salary
         and benefits expense, including retirement benefits, to
PY59                                                                                    NS
         more than one distribution level within the organizational
         account structure.




                                                                      Page 147 of 169
       The system should provide ability to set a default
PY60   number of hours for hourly employees and alter the                             NS
       number of hours worked on an exception basis.
       The system should provide the ability to utilize different
PY61                                                                                  NS
       GL account codes to record vacation pay, sick pay, etc.
       The system should provide the ability to automatically
PY62   update employee records with each payroll cycle and                            NS
       each adjustment cycle.
       The system should provide the ability to process and
       update employee records based on personnel
PY63                                                                                  NS
       transactions entered through Human Resources or
       satellite payroll offices.
       The system should provide the ability to automatically
       generate payroll posting entries to the General Ledger
PY64                                                                                  NS
       and validate General Ledger account codes against the
       chart of accounts before processing posting.

       The system should maintain historical payroll detail for a
PY65                                                                                  NS
       user defined time period within the master database.
       The system should provide access to recent payroll data
PY66   for each employee via online access for a user defined                         NS
       period of time.
       The system should provide ad hoc query capability
PY67   accessible to employees on line to inquire on history                          NS
       based on user defined criteria.
       The system should be FLSA compliant (e.g., regular
PY68                                                                                  NS
       rate calculations, required reports, archives).
       The system should provide the ability to deduct
       designated deductions pre-tax and apply the correct
PY69                                                                                  NS
       taxing calculations to the employee's adjusted gross
       income.
       The system should post payroll accruals to the
PY70   applicable expenditure/expense accounts and to the                             NS
       accrued payroll account.




                                                                    Page 148 of 169
       The system should have the ability for users with the
       appropriate authority to drill-down to payment details to
PY71                                                                                 NS
       view labor distribution, expense allocation, etc. in the
       General Ledger.
       The system should provide the ability to define codes for
       - but not limited to - checks and automatic deposit,
PY72                                                                                 NS
       automatic deposit only, multiple automatic deposits,
       check only, etc.
       The system should provide the ability to establish user-
       defined parameters for deductions and earnings codes
PY73                                                                                 NS
       for taxing and withholding purposes. (based on straight
       pay as well as a percentage.)
       The system should provide the ability to calculate the
PY74   payout of an eligible leave balance based on user                             NS
       defined criteria and initiated by a personnel action.
       The system should calculate all types of employee
PY75   garnishments (e.g., effective date, limit, establish                          NS
       priority).
       The system should automatically update accruals for
PY76   vacation, sick leave, etc. based on user defined plan                         NS
       rules and employee groups.
       The system should have the ability to calculate
PY77                                                                                 NS
       supplemental payrolls.
       The system should provide the ability to pay at a higher
PY78   or lower step for any period of hours, calendar days, pay                     NS
       periods, or until a specified date.
       The system should provide the ability to have payroll
PY79   adjustments reflected in correct pay period through a                         NS
       reporting mechanism or user initiated functionality.
       The system should provide the ability to calculate
       benefits based on a "benefit eligible FTE value" and/or a
PY80                                                                                 NS
       "position FTE value" and to prorate benefits based on
       either or both of these FTE definitions.
       The system should provide the ability to automatically
PY81   reverse a check/automatic payroll deposit with an audit                       NS
       trail.




                                                                   Page 149 of 169
       The system should provide the ability to generate
PY82   supplemental checks with immediate update of year-to-                           NS
       date payroll information.
       The system should provide the ability to allow
PY83   supplemental payroll checks with appropriate                                    NS
       deductions reported in the regular pay cycle.
       The system should provide the ability to review and
       modify pending payroll transactions prior to final
PY84                                                                                   NS
       processing of each standard or supplemental payroll
       cycle.
       The system should provide the ability to correct errors
PY85   and reprocess exceptions online prior to printing checks                        NS
       and/or automatic payroll deposits.
       The system should provide the ability to view manual
PY86                                                                                   NS
       checks online immediately after they are generated.
       The system should provide the ability to automatically
PY87   adjust all accrual balances (e.g., illness, vacation)                           NS
       resulting from benefit adjustments.
       The system should provide the ability to process
PY88                                                                                   NS
       catastrophic leave donations to other employees.
       The system should provide the ability to produce W-2
PY89                                                                                   NS
       Forms at the end of each calendar year.
       The system should provide the ability to print fiscal year-
PY90   to-date total per employee by any attribute in the                              NS
       account code structure.
       The system should provide ability to establish a limit on
PY91   the dollar amount of an individual payment (e.g., net                           NS
       pay).
       The system should have the ability to process a
PY92   deceased employee's payments in accordance with                                 NS
       Internal Revenue Service requirements.
       The system should have the ability to perform calendar
       year end updates on employee records based on
PY93                                                                                   NS
       defined criteria (e.g., year-to-date gross earnings, social
       security and Medicare taxes).




                                                                     Page 150 of 169
        The system should have the ability to set up appropriate
PY94                                                                                 NS
        approval and audit trail procedures for all interfaces.
        The system should provide the ability to enter time in
PY95                                                                                 NS
        future pay periods.
        The system should provide comments fields associated
PY96    with time entry data (e.g., user can provide narrative                       NS
        reason for overtime).
        The system should provide the ability to enter and
        process non-hourly/wage reimbursements, including but
PY97    not limited to mileage and other non-taxable                                 NS
        reimbursements, etc. with payments to the employee
        through Payroll.
        The system should provide electronic signature
PY98                                                                                 NS
        features.
        The system should provide the ability to create
PY99    automated workflows for payroll and time and                                 NS
        attendance processing.
        The system should have the ability to keep track of work
PY100                                                                                NS
        hours when an employee works several different shifts.
        The system should provide the ability to track, validate
PY101   and reconcile actual hours worked by work schedule by                        NS
        position, classification and employee.
PY102   The system should allow time entry by shift.                                 NS
        The system should provide tracking of comp time with
PY103                                                                                NS
        different rules for different groups of employees.
        The system should provide the ability to assign
PY104   employee hours to capital improvement projects, special                      NS
        projects and grant number.
        The system should provide the ability to trigger shift
PY105                                                                                NS
        differentials based on user defined criteria.
        The system should provide work history accessible to
PY106                                                                                NS
        departments for on-line viewing of hours worked.




                                                                   Page 151 of 169
        The system should provide the ability for users to view
        online administrative time balances and history at time-
PY107                                                                                NS
        entry (e.g., pop-up display of leave history and time
        bank balances).
        The system should validate employee sick time, leave,
        and other time bank balances at time entry and
PY108                                                                                NS
        generate warnings and/or prohibitions for time usage
        exceeding balances.
        The system should provide the ability for rapid data
PY109                                                                                NS
        entry across days and across employees.
        The system should provide the ability to enter time
PY110                                                                                NS
        adjustments for prior pay periods.
        The system should provide the ability to generate and
PY111   print manual payroll checks for immediate payment                            NS
        outside the normal processing cycle.
        The system should provide the ability to create user
        defined pay classes, pay codes and maintain a variety of
        employee earnings codes including standard earnings
PY112                                                                                NS
        such as regular, overtime, shift codes, double time,
        taxable and non-taxlabe earnings codes, state or federal
        mandated earnings, and user defined earnings codes.

        The system should provide the ability to create user
        defined deduction classes, deduction codes and
        maintain a variety of employee payroll deductions,
PY113                                                                                NS
        including standard deductions for tax purposes as well
        as pre-tax deductions, state mandated deductions,
        benefit deductions, and user defined deductions.
         The system should have the ability to post direct
        deposit/checks remittance advice to a secured website
PY114                                                                                NS
        where employees can view and print their own
        information.
        The system should provide the ability to process hours
        and time worked based on multiple positions, pay rates,
PY115                                                                                NS
        and function pays during each standard and/or
        supplemental payroll cycle.



                                                                   Page 152 of 169
          The system should provide the ability to designate
PY116     employees as exempt or non-exempt and to process                              NS
          their pay appropriately according to FLSA regulations.
          The system should provide the ability to pay inactive
          employees, but should provide a warning at the point of
PY117                                                                                   NS
          data entry and on an edit report during payroll
          processing.
          The system should provide the ability to view timesheets
PY118     related to each pay period and historically for a user                        NS
          defined period of time.
          The system should provide the ability to build user
          defined earnings accumulators which will accumulate
PY119     specific earnings codes into cumulative totals                                NS
          throughout the year for purposes of pension, 401k,
          403b, etc.
          The system should provide the ability to cancel a check
          by check number and have totals automatically reverse
PY120                                                                                   NS
          from the employee pay history, the leave system and
          General Ledger.
          The system should provide the ability to check for
PY121                                                                                   NS
          duplicate and/or incorrect social security numbers.
          The system should provide the ability to pay overtime at
PY122     time and one half, straight time or double time based on                      NS
          user defined criteria and FLSA regulations.

          The system should provide the ability to distribute
PY123     employer contributions to different cost centers, project                     NS
          codes, and any other user defined allocation needs.
          The system should provide the ability to enter payroll
          overrides and adjustments for one-time dollar hour
PY124     adjustments and other miscellaneous transactions
          affecting an employee’s check including, but not limited
          to, the following:
PY124 1 - Withholding both additional and specific deductions.                          NS




                                                                      Page 153 of 169
PY124 2 - Withholding both additional and specific tax amounts.                      NS
PY124 3 - Stop generation of an employee's check.                                    NS
        The system should provide the ability to enter time at
PY125   decentralized locations by the following methods,
        including but not limited to:
PY125 1 - By timekeeper                                                              NS
PY125 2 - By employee                                                                NS
PY125 3 - Intranet                                                                   NS
PY125 4 - Web browser (Internet)                                                     NS
PY125 5 - File transfers                                                             NS
        The system should provide the ability to audit, modify,
        and approve timekeeping data and adjustments prior to
PY126                                                                                NS
        final processing of a standard or supplemental payroll
        cycle.
        The system should provide the ability to establish a
        default configuration that limits the menus available to
PY127                                                                                NS
        the employee for inputting time to only those items
        relevant to that employee.
        The system should allow entry of time by exception only
PY128                                                                                NS
        and positive entry capabilities.
        The system should provide the ability to adjust
        exception hours based on user defined criteria (i.e.,
PY129                                                                                NS
        classification, physical location, bargaining unit, work
        year, etc.).
        The system should allow multiple units of time entry and
PY130   processing, including but not limited to hours and                           NS
        minutes and hours and decimals.
        The system should provide the ability to enter, process
        and track non-hourly/wage reimbursements, including
PY131   but not limited to mileage and other non-taxable                             NS
        reimbursements, etc. System should allow the ability to
        generate an AR entry.
        The system should provide the ability to generate
PY132   Accounts Receivable entries based on non-hourly/wage                         NS
        reimbursements.




                                                                   Page 154 of 169
        The system should provide reports of all changes to
PY133                                                                                 NS
        employee's pay, deductions, taxes, etc.
        The system should provide reports of all changes to
PY134                                                                                 NS
        employer's deduction and taxes, etc.
        The system should provide reports on FLSA
PY135                                                                                 NS
        calculations.
        The system should provide reports of tax payments by
PY136                                                                                 NS
        employee.
        The system should provide the ability for exception
PY137                                                                                 NS
        reports for leave balance.
        The system should provide reports of retirement
PY138                                                                                 NS
        deductions by employee.
        The system should provide the ability to identify, enter
        and report, with appropriate security, those hours
PY139   charged to any fund, department and organization for                          NS
        positions that do not exist or are not authorized in
        position control.
        The system should provide time collection data
PY140                                                                                 NS
        reporting at any user defined level.
        The system should provide the ability to track and report
PY141                                                                                 NS
        absence history from time and attendance records.

        The system should provide the ability to calculate the
        overtime based on a variety of schedules including 7
PY142                                                                                 NS
        days, 14 days, 21 days, 24 days, and 28 days cycles
        with defined number of hours assigned to those cycles.
        Ability to pro-rate taxes on lump sum earnings within
        the payroll to spread vacation/sick payouts taxability
PY143                                                                                 NS
        across year vs pay period to reduce amount of taxes
        withheld
PY144   Ability to withhold taxes on bonuses at appropriate rate                      NS
        Ability to validate address compliance with USPS
PY145                                                                                 NS
        standard
        SLCO Requirements Average GAP
        Total GAP



                                                                    Page 155 of 169
SALT LAKE COUNTY                                                                       INSTRUCTIONS
Functional Requirements Matrix
                                                                          Complete the worksheet by placing an X in
                                                                             the most appropriate column for each
                                                                            criterion. The X's should represent the
                                                                             current state of a particular product or
                                                                         service. (More than one response to a single
                                                                              requirement will be treated as a non
                                                                                            response)




                        TIMEKEEPING                                                 RATING RESPONSE
                                                                          SUP      MOD       3RD      CST      FUT
 TK         General Operating Requirements Section
            The system should provide the ability to define work and
 TK1
            leave hours by user defined criteria.
            The system should provide the ability to enter time at
 TK2        centralized or decentralized locations by the following
            methods, including but not limited to:
 TK2   1    By timekeeper
 TK2   2    By employee
 TK2   3    Electronic time card
 TK2   4    Intranet
 TK2   5    Kiosk
 TK2   6    Internet
 TK2   7    Touchscreen
 TK2   8    Personal digital assistant (PDA)
            Interfaces with other systems (inbound and outbound,
 TK2   9
            real time)
 TK2   10    - Batch (inbound)
 TK2   11    - Online (with keyboard "shortcut" keys)
 TK2   12    - Web browser (Internet)
 TK2   13    - Interactive voice response (IVR)
 TK2   14    - File transfers
 TK2   15    - Biometrics
            The system should allow multiple units of time entry and
 TK3
            processing, including but not limited to:
 TK3   1    Hours and minutes
 TK3   2    Hours and decimals
            The system should provide the ability to access time
            entered including, but not limited to: daily, weekly,
 TK4
            biweekly, quadri-weekly (every four weeks) and/or
            monthly basis.
            The system should provide the ability to charge or
            allocate labor, i.e. time, against multiple types of fund,
 TK5
            job, department, project, etc. codes as defined in the
            chart of accounts.
            The system should provide the ability to enter worked
 TK6
            time or leave hours in future pay periods.
       The system should provide the ability to organize a
       group of employees within divisions into work areas
TK7    and/or work teams and select (via pop-up display etc.)
       groups or individuals to facilitate time keeper data entry
       and/or approval of multiple time entry.
       The system should provide electronic signature
TK8
       features.
       The system should have the ability to keep track of work
TK9
       hours when an employee works several different shifts.
       The system should provide the ability to track, validate
TK10   and reconcile actual hours worked by work schedule by
       position, classification and employee.
TK11   The system should allow time entry by shift.
       The system should provide tracking of compensatory
TK12   time per rules by bargaining unit, department, or other
       employee grouping.
       The system should provide the ability for employees to
       take leave hours in the period they accrue the hours
TK13
       (e.g., an employee can take four hours during the period
       in which he accrues the four hours).
       The system should automatically check that an
       employee is authorized to work on a project and that the
TK14
       number of hours charged is authorized for that
       employee on the project.
       The system should provide the ability to limit (assign
TK15   maximums) the amount of leave employees can accrue
       for each individual leave type.
       The system should provide the ability to vary the number
TK16
       of regular/default hours by position.
       The system should provide the ability to enter time
TK17   adjustments for prior pay periods based on user defined
       security.
       The system should display leave balances on paystubs
TK18
       and reports.
       The system should have the ability to display real-time
       balances, including leave which has been posted but not
TK19
       yet paid in the payroll system. The user should have
       access to this data when entering their timecard
       The system should enable automatic draws from other
TK20   leave balances when a balance has been exceeded
       based on user-defined criteria.
       General Requirements Average GAP
       Approval Requirements Section
       The system should provide the ability to enter timesheet
TK21
       approvals at decentralized locations.
       The system should provide workflow for exception-
       based review and approval, changes to history and
TK22
       schedules, etc. and provide review status and workflow
       audit trail information.
       The system should flag time entered falling outside of
TK23   normal work schedules for management
       review/approval.
           The system should provide the ability to workflow the
TK24
           approval of time entry to supervisors.
           The system should provide the ability for a supervisor to
TK25       certify an employee has completed the requirements for
           supplemental pay.
           The system should provide the ability to assign various
           approval rights to specific users/management including
TK26
           but not limited to approval of overtime, working out of
           shift, etc.
           The system should support multi-level, real-time
TK27       updates and approvals for automatic calculation and
           tracking of overtime and shift differentials payments
           The system should display a warning message when
TK28       the user is entering overtime hours that are restricted or
           require additional approvals.
           The system should have the ability to revise submitted
TK29
           timecards or delete them with the appropriate security.
           Approval Requirements Average GAP
           Scheduling Requirements Section
           The system should provide the ability to define and track
TK30       work schedules at multiple levels, including but not
           limited to the following:
TK30   1   Employee
TK30   2   Position
TK30   3   Other Classification
TK30   4   Work Group
TK30   5   Division
TK30   6   Department
TK30   7   Location
           The system should enable the user to generate daily,
           weekly, bi-weekly, 28-day cycles and future schedules
TK31       automatically, allow for manual overrides on an
           exception-basis and provide for effective calendar
           dating.
           The system should provide the ability to define multiple
TK32       shifts including, but not limited to, starting and ending
           times, breaks and lunch periods, etc.
           The system should provide the ability to assign
           employees to hours, shifts, positions, departments, etc.
TK33       outside of their normal schedule and accumulate and
           track all associated time and related data without
           affecting the employees normal schedule.
           The system should provide comments fields to provide
TK34
           reason for changes in schedules.
           The system should provide the ability to define and
TK35       assign employees to an unlimited number of labor cost
           codes.
           The system should determine staffing shortages based
TK36
           upon current and future schedules.
           The system should accommodate authorized schedules
TK37
           of any number of hours up to a specified limit.
           Scheduling Requirements Average GAP
         Reporting Requirements Section
         The system should provide the ability to produce reports
TK38
         including, but not limited to:
TK38   1 Overtime and compensatory time accruals by period
         FMLA, stand-by hours, extended leave, safety leave,
         awarded hours, excused dock, dock, suspension,
TK38   2
         worker's compensation and non-pay activities including
         the reason and description
         Planned and actual absentee time and the related costs,
TK38   3
         including costs of associated fringe benefits
           Absence by employee, fund, department, organization,
TK38   4
           shift and reason by pay period and cumulative
           Employee vacation schedules reflecting approved
TK38   5
           requests
           The system should provide time collection data
TK39
           reporting at any user defined level.
           The system should provide the ability to print the daily
TK40       detail of time reported for the current pay period both by
           employee number and employee name sequences.

           The system should provide the ability to support time
TK41
           reporting of employees to assist with cost accounting.
           Reporting Requirements Average GAP
           SLCO Requirements Section
           The system should allow entry of time by exception only
TK42
           and positive entry capabilities.
           The system should provide the ability to adjust
           exception hours based on user defined criteria (i.e.,
TK43
           classification, physical location, bargaining unit, work
           year, etc.).
           The system should provide the ability to enter time on a
TK44       daily, weekly, biweekly, quadri-weekly (every four
           weeks), and/or monthly basis.
           The system should provide the ability to identify, enter
           and report, with appropriate security, those hours
TK45       charged to any fund, department and organization for
           positions that do not exist or are not authorized in
           position control.
           The system should provide the ability to define common
           allowances, including but not limited to: meal allowance
TK46       associated with positions, work schedules, etc. and
           recommend appropriate allowances to the user based
           on data entered during time-entry (regul
           The system should provide the ability to enter, process
           and track non-hourly/wage reimbursements, including
TK47
           but not limited to mileage and other non-taxable
           reimbursements, etc.
           The system should provide the ability to enter and
           process non-hourly/wage reimbursements, including but
TK48       not limited to mileage and other non-taxable
           reimbursements, etc. through Accounts Payable, with
           payments to the employee through Payroll.
           The system should provide the ability to create default
           timesheet activities for individuals or groups of users to
TK49
           facilitate time entry based on user-defined needs and
           criteria (e.g., 4/40, 9/80 work schedules).

           The system should accumulate, process, and track all
           associated time-related data for employees working in
TK50       multiple positions, multiple shifts, multiple locations,
           multiple work schedules, multiple calendars etc.,
           including but not limited to the following:
TK50   1   - Work hours
TK50   2   - Overtime
TK50   3   - Compensatory Time-off
TK50   4   - Accruals
TK50   5    - Benefits
TK50   6    - Fair Labor Standards Act (FLSA)
TK50   7    - Filler Time
           The system should provide the fund information
           integrated with time entry (e.g., ability to charge partial
TK51
           hours worked by employees to grants - charge 2 of 8
           hours to a grant).
           The system should provide the ability to track clock time
TK52
           for some employees and elapsed time for others.
           The system should provide the ability to trigger shift
TK53       differentials based on clock time reported by an
           employee (check in time).
           The system should provide work history accessible to
TK54
           departments for on-line viewing of hours worked.
           The system should provide the ability to record hours
           worked and hours payable as two different amounts
TK55
           (ability to apply unpaid hours to service requirements for
           leave calculations).
           The system should automatically update accruals for,
TK56       including but not limited to, vacation, sick leave, comp
           time, paid non-working days, etc.
           The system should provide the ability to accommodate
TK57       frequent and on-the-spot staff changes and provide an
           accessible permanent staffing record.
           The system should provide Family Medical Leave Act
TK58       (FMLA) tracking, including Intermittent Family Care
           tracking.
           The system should provide the ability for rapid data
TK59
           entry across days and across employees.
           The system should validate, upon entry, the accrual
TK60
           hours, project, work schedule, etc.
           The system should support a schedule that can be
           specified that will automatically capture holiday pay to
TK61
           eligible employees and recognize when employees are
           not eligible.
           The system should track work years that reflect the
           various work schedules of the district, site, track, or/and
TK62
           of individuals (e.g., schedules refer to the number of
           months of work and/or work years).
TK63       The system should allow work schedule modifications.
           The system should define and track work schedules by
TK64       days, hours and minutes (e.g. job sharing which may be
           tracked at the site).
           The system should provide ability to assign multiple
TK65
           work schedules to an individual.
           The system should provide online validation of all time
           entered with rules, pay policies, schedules, etc. and
TK66       generate warnings and/or restrictions/prohibitions when
           time entry data is in violation of policies, including but
           not limited to the following:
TK66   1 - Overtime
TK66   2 - Shift differential
TK66   3 - Special shift and benefit rules
         The system should provide the ability to create user
TK67
         defined electronic time sheet approval.
         The system should accommodate entry of authorization
TK68
         number of person approving overtime.
           The system should provide the ability to automatically
TK69
           recalculate regular hours as leave hours are recorded.
           The system should support multi-level, real-time
TK70       updates and approvals for the following but not limited
           to:
TK70   1    - Employee absences
TK70   2    - Start and stop work times
TK70   3    - Total time expended per assignment/appointment
            - Provide the ability to review and modify pending
TK70   4
           payroll transactions
            - Automatically calculate and track overtime and double
TK70   5
           time payments
           The system should provide the ability to adjust
TK71
           exceptions based on user defined criteria.
           The system should have the ability to edit all timesheet
TK72
           entries based on security rules.
           The system should provide a validation and verification
TK73       control identifying the work-flow status of the approval
           process.
           The system should provide the ability to edit all
TK74       timesheet entries based on user-defined eligibility
           criteria.
           The system should provide an audit trail of all edits and
TK75
           approvals.
           The system should provide the ability to track and
TK76       maintain work schedules by position, classification of
           employee and work location.
           The system should provide the ability to define and
           apply multiple organization specific rules to schedules
TK77
           and pay policies, including but not limited to the
           following:
TK77   1    - Time banks
TK77   2    - Overtime
TK77   3    - Compensatory time-off
TK77   4    - Shift differential
TK77   5    - Special shift rules
           The system should provide work history reports for
TK78       subpoena responses including dates worked, breaks,
           assignments, etc.
           The system should provide reports of active employees
TK79
           with no hours entered.
           The system should provide the ability to track and report
TK80
           absence history from time and attendance records.
           The system should provide the ability to track and report
TK81       employees who submit fraudulent data or perform
           fraudulent actions at work.
           The system should provide the ability to print
           adjustments including but not limited to by program
TK82
           code, single employee, multiple employees by pay
           period and cumulative.
           The system should provide reporting capability for both
TK83       daily detail and summary by type of time code, e.g., OT
           reported both in current pay period and cumulative.
           The system should provide the ability to automatically
TK84       update (negative or positive) benefit balances based on
           prior pay period adjustments.
           SLCO Requirements Average GAP
           Total GAP
                                  RATING LEGEND
        SUP   Supported as delivered "out-of-the-box"
              Supported via modifications (screen configurations, reports, GUI
        MOD
              tailoring, etc)
        3RD   Supported via a third party solution
        CST   Supported via customization (changes to source code)
        FUT   Will be supported in a future release
        NS    Not supported


PONSE                  ADDITIONAL COMMENTS
        NS                                                              Resp

                                                                         NS




                                                                         NS
                                                                         NS
                                                                         NS
                                                                         NS
                                                                         NS
                                                                         NS
                                                                         NS
                                                                         NS
                                                                         NS
                                                                         NS
                                                                         NS
                                                                         NS
                                                                         NS
                                                                         NS
                                                                         NS


                                                                         NS
                                                                         NS


                                                                         NS



                                                                         NS


                                                                         NS
NS



NS


NS


NS

NS

NS



NS



NS



NS


NS


NS


NS



NS



NS




NS


NS



NS
NS


NS



NS



NS


NS


NS




NS
NS
NS
NS
NS
NS
NS


NS



NS




NS



NS


NS


NS


NS
NS


NS


NS


NS


NS

NS


NS



NS




NS


NS



NS



NS




NS




NS




NS
NS




NS
NS
NS
NS
NS
NS
NS


NS



NS


NS


NS


NS



NS



NS



NS


NS

NS


NS
NS


NS


NS


NS




NS
NS
NS
NS

NS


NS




NS
NS
NS
NS

NS

NS

NS


NS


NS


NS


NS
NS
NS
NS
NS
NS

NS


NS


NS


NS



NS



NS



NS

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:30
posted:5/16/2012
language:English
pages:169
fanzhongqing fanzhongqing http://
About