Get documents about "Area Stage 1 FI Cal Non Functional Requirements Technical T Requiremen
Document Sample
Area # Stage 1 - FI$Cal Non-Functional Requirements
Technical (T) Requirements
Software Solution
General Application Design
T 1.0 The Proposed Solution shall be a secure, web-based COTS application.
T 2.0 The Proposed Solution shall use a multi-tiered architecture (e.g., Presentation, Business, and Database).
T 3.0 The Proposed Solution shall utilize an ANSI compliant Structured Query Language (SQL).
T 4.0 The Proposed Solution shall conform to W3C Internet standards.
The Proposed Solution shall meet Technical System Requirements of the Core Financial System Requirements, published by the Office of
Federal Financial Management (OFFM-NO-0106, January 2006) and subsequent updates, if any.
T 10.0
Refer to http://www.whitehouse.gov/omb/financial/ffs/012306_Core_Requirements.pdf. Only technical components of this document are required to be met. References to
names and policies of federal government agencies in the above document are excluded.
The Proposed Solution shall provide complete support for multi-currency capabilities including conversion and translation with Generally
T 11.0
Accepted Accounting Principles (GAAP).
The Proposed Solution shall support built-in integration capabilities among all the components of the ERP suite as needed in the
Functional Requirements section of this RFP.
T 12.0
Refer to Section VI, Non-Functional and Functional Requirements” and “Appendix D-01 - Appendix D-23, Functional Requirements Response Matrices”.
T 23.0 The Proposed Solution shall provide the ability to automatically reconcile data between all components of the ERP suite.
The Proposed Solution shall provide the ability to prevent transactions that would introduce a data discrepancy between application
T 24.0
components of the ERP suite.
The Proposed Solution shall have the ability to authenticate electronically signed documents using digital signatures and electronic
T 25.0
signatures in compliance with Civil Code Section 1633, Government Code Section 16.5, and Secretary of State Regulations.
Workflow
The Proposed Solution shall include workflow features that assign tasks (e.g., create, review, copy (all or selected portions), reject,
T 29.0
approve, update, cancel, and close, applicable documents) to staff based on defined business rules.
The Proposed Solution shall include workflow features that routes work to the next person in a workflow (e.g., based on process outcomes
T 30.0
or trigger dates).
T 31.0 The Proposed Solution shall include workflow features that balances workload based on user and work unit queues.
The Proposed Solution shall include workflow features that provide a mechanism for workflow routing to be chosen by the authorized user.
T 32.0
The Proposed Solution shall include workflow features that provide a mechanism for both parallel and serial steps and for looping of steps
T 33.0
until a condition is met in the workflow.
The Proposed Solution shall include workflow features for workflow routing that supports notification either by e-mail (push) or online
T 34.0
automated/on-demand queries (pull) or other mechanism by user for work that is in the user's queue.
The Proposed Solution shall include workflow features which enforces workflow rules (with task checklists) to ensure that processes are
T 35.0
completed correctly.
Area # Stage 1 - FI$Cal Non-Functional Requirements
The Proposed Solution shall include workflow rules that are configurable and that can be updated easily by authorized users to take effect
T 36.0
either immediately or by scheduled time or event.
The Proposed Solution shall generate reports and alerts of pending and/or overdue work to improve management and staff accountability,
T 37.0
based on user-defined criteria.
The Proposed Solution shall provide for tracking that includes, at a minimum, logging of user entries, what areas the user accessed,
T 38.0
logging of task status, contact history, issues, workflow changes, and overrides.
The Proposed Solution shall provide automatic notification (to internal and external users) based on status of a workflow item, date, event,
T 39.0
and user role (e.g., 30-day notification letter), or by user-defined criteria.
T 40.0 The Proposed Solution shall provide escalation features to ensure timely response to inquiries or problems.
The Proposed Solution shall notify users in a particular workflow to handle activities that cannot be automated, through a notification or
T 41.0 alert that contains all supporting information needed to make a selection from a pre-defined (e.g., drop-down list) menu of activities.
The Proposed Solution shall support collaborative work activities to allow multiple users to work on the same information (e.g., document,
T 42.0
data, record) with the capability to track and merge who has made changes.
The Proposed Solution shall allow an authorized user to create, archive, remove, or modify workflow activities, or set up new relationships
T 43.0
among activities with the ability to maintain, view, and print an audit trail/history of all changes made.
T 44.0 The Proposed Solution shall allow an authorized user to override defined approval rules with the ability to audit changes made.
T 45.0 The Proposed Solution shall provide the ability to archive completed work of workflow processes.
T 46.0 The Proposed Solution shall include the ability to apply start and end dates to workflow approvers and their proxies.
The Proposed Solution shall include the ability to define multiple levels of document approvals based on State-defined and/or user-defined
T 47.0
criteria (e.g., dollar amounts, types of items purchased and document types).
The Proposed Solution shall include the ability to define multiple approval levels to an individual user based on State-defined and/or user-
T 48.0
defined criteria.
The Proposed Solution shall provide the ability to prevent an individual user from applying more than one level of approval to the same
T 49.0
document to conform to the principle of separation of duties.
The Proposed Solution shall provide the ability for workflow calendaring including the ability to generate date-based process exception
T 50.0
reports and alerts (e.g., notify an accounts payable office when invoices are held over 30 days with no matching receiving report).
The Proposed Solution shall provide the ability to capture approval actions by transaction, including the time, date and approving party.
T 51.0
The Proposed Solution shall provide a Graphical User Interface (GUI) business process workflow modeling capability with the ability to
T 53.0
create, update, delete, print, export, import and save.
The Proposed Solution shall provide the ability to generate auditable records of changes made to the workflow approval routing design.
T 54.0
The Proposed Solution shall allow associated documents (including individual emails, PDFs., and other document file types) to be
T 55.0 imported, stored, and linked (e.g., associates the indexed documents with any additional actions, activities, or events pertaining to that
document allowing for multiple associations).
The Proposed Solution shall provide the ability to facilitate document management requirements to comply with the Sarbanes-Oxley Law.
T 56.0
Area # Stage 1 - FI$Cal Non-Functional Requirements
T 57.0 The Proposed Solution shall provide access to help procedures and tips for using the content/document management function.
T 58.0 The Proposed Solution shall provide the ability to search based on keywords (e.g., metadata) and phrases.
The Proposed Solution shall provide the ability to electronically image, scan, index and store file reference materials delivered in hard copy
T 59.0
format (e.g., a signed contract, bill of lading, vendor invoices) while maintaining system performance.
The Proposed Solution shall provide the ability to identify the presence of associated stored/linked documents and provide the ability to
T 60.0
view them.
The Proposed Solution shall provide the ability to correct, modify, adjust or reverse transactions (e.g., based on user-authority, workflow,
T 61.0
audit history and thresholds).
The Proposed Solution shall have the ability to perform certain actions (e.g., approve, reject, cancel, close, or print) one at a time,
T 62.0
simultaneously, or in batch mode based on user-defined criteria.
T 63.0 The Proposed Solution shall allow a user to generate alerts and prompts (e.g., one time, persistent) based on user-defined criteria.
The Proposed Solution shall provide the ability to generate user alerts based on user-defined triggering events (e.g., thresholds) using the
T 64.0
State's existing e-mail system.
The Proposed Solution shall have the ability to create, retrieve, update, and archive data (e.g., requisitions, solicitations, purchase
T 65.0
documents, project documents, receiving log) based on user-defined criteria.
The Proposed Solution shall provide the ability to maintain, view, and print an audit trail/history of all activity for a transaction (e.g., edits to
T 66.0 purchase documents), based on user-defined criteria (e.g., identification of operator, what was changed, time, date).
T 434.0 The Proposed Solution shall provide the ability to notify user, retrieve, and add comments regarding electronic images.
T 435.0 The Proposed Solution shall provide the ability to scan and capture (i.e., OCR) electronic images.
Technical Architecture
Presentation Architecture
The Proposed Solution browser based access shall not require the installation of components above the proposed minimum level of
T 87.0
system requirements.
The Proposed Solution shall provide a common graphical user interface which includes, but is not limited to:
• Pull-down menus
• Spell checking
• Ability to find, replace, and go-to within a transaction
• Keyboard equivalent for all menu options
• Use of a mouse for all commands
T 99.0 • Scrollable list boxes
• Cursor selection of items in scrollable list boxes
• Multiple windows that may be open simultaneously
• Windows that can be minimized and maximized
• Built-in charting on all standard inquiries
• Drop-down menu list of open windows
• Ability to print windows or entire screens in a “user friendly” print format
• Print preview of each transaction
Area # Stage 1 - FI$Cal Non-Functional Requirements
The Proposed Solution shall provide an online help facility which includes, but is not limited to:
• Window level help
• Field level help
• Error message help
T 100.0
• Context sensitive help
• Windows hypertext help
• Indexed help
• Definable coaches, wizards, or tutors
The Proposed Solution shall have word processing capabilities for entering narratives (e.g., creation, input, editing, formatting of
T 101.0
documents, spell check).
Application Configuration Components
The Proposed Solution shall provide the ability to store and update validation data (e.g., list boxes, combo boxes, radio buttons and check
T 102.0
boxes).
Data Entry Support
T 110.0 The Proposed Solution shall provide a method of manual online/offline data entry.
The Proposed Solution shall provide a method of manual online/offline data entry, including but not limited to, copy and paste capabilities.
T 111.0
The Proposed Solution shall have the ability to associate (i.e., attach/link) data (e.g., metadata, documents and other information) to a user-
T 113.0 designated item (e.g., solicitation or purchase document) and have the data remain associated with the user-designated item regardless of
activity (e.g., revisions, submission for approval, or export of user-designated item).
Database Architecture
T 125.0 The Proposed Solution shall provide the ability to generate an Entity Relationship Diagram (ERD) on demand.
The Proposed Solution shall provide the ability to maintain internal database consistency at all times. In the event of a system failure the
Proposed Solution must have the ability to:
• Back out incompletely processed transactions
T 126.0 • Restore the system to its last consistent state before the failure occurred
• Re-apply all incomplete transactions previously submitted by the user
• Validate internal database consistency to ensure duplicate postings are avoided
• Report any data or transactions that failed to process completely
The Proposed Solution shall provide the ability to configure the number of times an incomplete transaction is re-applied in the event of
T 127.0
system failure.
Interface Architecture
T 143.0 The Proposed Solution shall support integrated functionality within an application/module and between applications/modules.
The Proposed Solution shall provide the ability to implement permanent and interim data interfaces between FI$Cal and other agency and
T 144.0
external entity systems, including data mapping, record layout (e.g., fixed record layout, XML) transformation.
Area # Stage 1 - FI$Cal Non-Functional Requirements
The Proposed Solution shall have the ability to communicate with other agency and external entity systems using various mechanisms,
including at a minimum:
• Publish/subscribe
T 145.0
• Request/reply
• Synchronous
• Asynchronous
The Proposed Solution shall provide the ability to interface with industry standard document imaging technologies, including functionality to
T 148.0
view those documents as attachments within the system, and to define where the link to the document is triggered.
T 149.0 The Proposed Solution shall provide the ability to integrate with third-party Enterprise Architecture Integration (EAI) software.
The Proposed Solution's Enterprise Architecture Integration (EAI) software shall provide the ability to implement metadata management
T 150.0
features such as semantic integration, metadata sharing, and synchronization.
The Proposed Solution's Enterprise Architecture Integration (EAI) software shall provide the ability to synchronize data between systems in
T 151.0
real time, batch mode, or in near real time (such that the latency experienced by users is minimal).
T 152.0 The Proposed Solution shall provide the ability to define business rules that drive the data synchronization process.
The Proposed Solution's Enterprise Architecture Integration (EAI) software shall provide the ability to perform data transformation functions
T 153.0
such as cleansing, validation, auditing, and semantic, structural or format reconciliation.
The Proposed Solution shall provide the ability to centrally manage the Enterprise Architecture Integration (EAI) software components.
T 154.0
The Proposed Solution shall provide ability to implement a transaction management strategy between FI$Cal and other agency and
T 155.0 external entity systems to not only ensure transaction integrity and logical completion and consistency, but also to provide transaction roll-
back.
The Proposed Solution shall provide the ability to orchestrate fully formed business process flows (e.g., sending, receiving, and data
T 156.0
confirmation) between FI$Cal and other agency and external entity systems.
The Proposed Solution shall provide the ability to receive and distribute data records of appropriate type and format based on
T 161.0
characteristics of the destination systems.
T 162.0 The Proposed Solution shall provide the ability to synchronize data in near real-time.
The Proposed Solution shall provide the ability to handle errors and exceptions that may occur as part of integration and interface
T 163.0
operations.
The Proposed Solution shall log individual errors in the interface communication log indicating at a minimum, the date and time of the
T 164.0 transmission, the transmission file name, the record that failed, the type of error/failure and the problem (e.g., data element or invalid
message header) that caused the error.
The Proposed Solution shall provide the ability to define and implement standardized interfaces to external systems based on Service
T 165.0
Oriented Architecture (SOA) principles.
T 166.0 The Proposed Solution shall provide the ability to track the status of transaction processing that occurs over an interface.
The Proposed Solution shall store and attempt to re-transmit the appropriate data to all appropriate target destinations in the event of a
T 167.0
transmission failure, until an acknowledgement is received.
The Proposed Solution shall provide the ability to queue transactions retaining data that is currently undeliverable until the connection to
T 168.0
the target system can be re-established.
T 169.0 The Proposed Solution shall provide the ability to configure the allowed number of re-transmits.
Area # Stage 1 - FI$Cal Non-Functional Requirements
The Proposed Solution shall perform sequencing of interface transactions so that the data for a particular interface is transmitted and
T 170.0
received in the same order in which it was sent, particularly in the event of re-transmissions.
The Proposed Solution shall provide interface monitoring and scheduling functionality that allows interface processes to be scheduled,
T 171.0
tracked, started and stopped.
The Proposed Solution shall retain appropriate messages/data when an interface transaction fails so that the transaction can be
T 172.0
reprocessed once the error has been resolved without the necessity to reprocess the entire message or dataset.
The Proposed Solution shall store and report statistical information on interface executions, volume of data, number of records, number
T 173.0
and type of errors. This statistical information must be reported in a user-readable format.
The Proposed Solution shall record, in an interface communication log, information on interface data transmissions such that data can be
tracked from the destination system, through the interface, back to the source system. The log shall include entries for start and end date,
T 174.0
time of transmissions, the type of transmission, the transmission file name/data, and indicate success or failure of the transmission.
The Proposed Solution shall provide the ability to provide specific controls (e.g., header and trailer records with total number of
T 175.0
transactions and total dollar amounts, hash totals and check digits) to ensure accurate data transfers.
T 176.0 The Proposed Solution shall provide the ability to validate inbound and outbound interface transactions.
The Proposed Solution shall provide the ability for the proposed Enterprise Architecture Integration (EAI) software to track the propagation
T 177.0
of errors with complete audit trails.
The Proposed Solution shall provide the ability for Enterprise Architecture Integration (EAI) transaction errors to be uniquely numbered and
T 178.0
to include a clear definition of the error.
The Proposed Solution shall provide the ability to notify the appropriate staff if there is a transmission failure. The notification must be
T 179.0
configurable for each interface (e.g., who to notify, how many failures trigger a notification and method of notification).
The Proposed Solution shall provide the ability to handle Enterprise Architecture Integration (EAI) errors differently based on high level
T 180.0
classifications of error categories (such as programming errors or resource errors).
The Proposed Solution shall provide the ability to generate electronic responses to source agency systems including unique identifiers
T 181.0
(e.g., hash, sequence number) for each Enterprise Architecture Integration (EAI) transaction successfully processed.
The Proposed Solution shall provide the ability to generate electronic responses to source agency systems including unique identifiers
T 182.0 (e.g., hash, sequence number) for each Enterprise Architecture Integration (EAI) transaction rejected including details of rejected
transaction such as a clear and succinct description of the reason for rejection.
T 183.0 The Proposed Solution shall provide Enterprise Architecture Integration (EAI) the ability that does not rely on proprietary protocols.
The Proposed Solution shall provide Enterprise Architecture Integration (EAI) the ability to support a number of standards, data formats
T 184.0
and transaction protocols.
T 185.0 The Proposed Solution shall provide the ability for application exit points for interfacing with external systems.
The Proposed Solution shall provide Enterprise Architecture Integration (EAI) the ability that provides a choice of batch, real-time or near
T 186.0
real-time modes of operation.
The Proposed Solution shall provide Enterprise Architecture Integration (EAI) the ability that leverages network level protocols to ensure
T 187.0
secure and reliable delivery of data.
The Proposed Solution shall provide Enterprise Architecture Integration (EAI) the ability to ensure that application messages are
T 188.0
acknowledged and sequenced.
Area # Stage 1 - FI$Cal Non-Functional Requirements
The Proposed Solution shall provide Enterprise Architecture Integration (EAI) the ability to automatically recover from infrastructure or
T 189.0
application failures.
T 190.0 The Proposed Solution shall provide Enterprise Architecture Integration (EAI) the ability to automatically correct common errors.
The Proposed Solution shall provide Enterprise Architecture Integration (EAI) the ability to enable application services that perform specific
T 191.0
functions, do not overlap in functionality and only operate on specific data.
The Proposed Solution Enterprise Architecture Integration (EAI) architecture shall ensure that modifications to underlying system
T 192.0
applications do not necessitate revisions to EAI services.
The Proposed Solution shall provide Enterprise Architecture Integration (EAI) the ability to allow application services to be reused by a
T 193.0
number of business processes.
The Proposed Solution shall provide Enterprise Architecture Integration (EAI) the ability to combine application services to form new
T 194.0
business processes.
The Proposed Solution shall provide Enterprise Architecture Integration (EAI) the ability for applications to register and locate services.
T 195.0
The Proposed Solution shall provide Enterprise Architecture Integration (EAI) the ability that allows application services to be implemented
T 196.0
with predefined quality of service levels that may vary depending on the function or process involved.
The Proposed Solution shall provide the ability to interface with the State's existing IT environments.
T 197.0
See Section III Current Environment
The Proposed Solution shall provide the ability to utilize the SCO HRMS data for Budget Development and Administration, Position
T 201.0
Control, and Accounting (e.g., General Ledger, Program Cost Allocation, Projects, Grants).
The Proposed Solution shall allow data (e.g., text, graphics) to be received, sent, or input in whole, part, or as part of a page when
T 202.0 performing various activities (e.g., create solicitations, purchase documents, receive bids from vendors in electronic or paper format).
Business Intelligence/Data Warehouse
General
T 206.0 The Proposed Solution shall provide a web-based portal single point of entry to Business Intelligence and Data Warehouse (BI/DW).
The Proposed Solution shall provide a searchable, comprehensive, online data dictionary describing all data elements in the entire data
T 207.0
warehouse.
The Proposed Solution shall provide a data dictionary which includes a listing of indexed and summary fields by table, including both short
T 208.0
and long field descriptions.
The Proposed Solution shall provide and maintain, in the data dictionary, a history of changes to individual data element (e.g. data length,
T 209.0
format, descriptions).
T 211.0 The Proposed Solution shall provide detailed descriptions for any metadata codes, data definitions and reference data.
The Proposed Solution Business Intelligence and Data Warehouse (BI/DW) components shall be implemented and deployed in the
T 214.0
production environment with no impact to the performance of any production system.
The Proposed Solution shall have the ability to incorporate new data, forms, and documents into workflows, processes and tasks.
T 215.0
T 216.0 The Proposed Solution shall have the ability to print data in a format representative of current forms and documents.
Area # Stage 1 - FI$Cal Non-Functional Requirements
Analysis and Reporting
T 224.0 The Proposed Solution shall enable report selection and generation screens from within the Proposed Solution.
The Proposed Solution shall provide the ability to generate reports from several database instances (e.g., Production, Public
T 225.0
Access/Reporting, Data Warehouse).
The Proposed Solution shall provide basic report creation without requiring technical staff or expertise to create and publish reports within
T 226.0
the Proposed Solution.
T 227.0 The Proposed Solution shall provide standard reporting (with and without input parameters).
T 228.0 The Proposed Solution shall provide ad-hoc reporting (with and without input parameters).
The Proposed Solution shall provide the ability to produce standard and ad-hoc reports/queries, save the results and share the
T 229.0
reports/queries with others.
The Proposed Solution shall print items (e.g., reports) at the users' office location as a default, but may print to any configured user-defined
T 230.0
printer.
T 231.0 The Proposed Solution shall ensure that reports maintain formatting independent of printing.
The Proposed Solution shall generate a confidentiality statement in the header and footer area of any report containing sensitive,
T 232.0
confidential or personal data.
T 233.0 The Proposed Solution shall provide the ability to apply role-based controls on user reporting capability based on roles/rules.
The Proposed Solution shall have the ability to export reports, query results and data files using multiple formats. Specified formats can
T 234.0 include online display, printed report (e.g., Portable Document Format (PDF), MS Word, OpenDocument format (ODF), Excel, ASCII or
delimited text file).
The Proposed Solution shall provide the ability to retain formatting when "exporting " information to and "importing" information from
T 235.0 external applications (e.g., Portable Document Format (PDF), MS Word, OpenDocument format (ODF), Excel, ASCII or delimited text file).
T 236.0 The Proposed Solution shall provide the ability for Report Management to set access controls on data.
The Proposed Solution shall provide the ability for Report Management to set system resources for generating a report (e.g., priority, CPU
T 237.0
usage).
The Proposed Solution shall provide the ability to merge and export data and text from various sources and data/file formats (e.g., ASCII
T 238.0 comma delimited, MS-Word, OpenDocument and MS-Excel) to create complex reports in publishable electronic formats (e.g., State
budget).
The Proposed Solution shall provide the ability to publish data to the State internal or external website with minimal manual "hands on"
T 239.0
intervention and processing.
T 240.0 The Proposed Solution shall provide a list of all standard reports/queries listed by business process.
T 241.0 The Proposed Solution shall provide the ability to preview (e.g., a result, form, report) before printing.
The Proposed Solution shall provide the ability to perform historical data reporting either from the operational database or from an archival
T 242.0
database based on user-defined parameters.
The Proposed Solution shall allow public/non-public access to reports and queries according to defined data warehouse access roles and
T 243.0
privileges
The Proposed Solution shall provide the ability to re-sort or re-group data returned from a query, without requiring a new query to be
T 245.0
executed.
Area # Stage 1 - FI$Cal Non-Functional Requirements
The Proposed Solution shall warn the user when the user submits a complex query or report which may require several hours to process,
T 246.0
allowing the user to proceed, modify or cancel the query/report in response to the warning.
T 247.0 The Proposed Solution shall allow for cancellation of a query at any time after submission but prior to completion.
The Proposed Solution's error notification shall include a meaningful reason including configurable options (e.g., date, time) of occurrence.
T 248.0
T 249.0 The Proposed Solution shall send notification when query has been stopped prior to completion.
The Proposed Solution shall have the ability to provide trend analysis of current, historical, and archive data across data warehouse(s).
T 250.0
T 251.0 The Proposed Solution shall provide the ability to drill down from standard report results to access data at a more detailed level.
T 252.0 The Proposed Solution shall provide the ability to select from multiple predefined report types and formats.
T 253.0 The Proposed Solution shall provide support for regular expressions (e.g., wildcards) in queries.
T 254.0 The Proposed Solution shall allow for ad hoc reports/queries to be exported (e.g., Word, Access, Excel, XML and PDF).
The Proposed Solution shall provide the ability to run reports automatically on a user-defined schedule (e.g. daily, weekly, monthly and
T 255.0
yearly).
T 256.0 The Proposed Solution shall provide the ability to run reports on an on-demand basis.
The Proposed Solution shall provide menu-driven graphical report generation capabilities including:
• Page formatting features
• Drag and drop positioning
T 257.0 • Multi-level sorting and sub-totaling
• Page numbering
• Widow and orphan control
• Pivot and cross tabulations
The Proposed Solution shall provide the ability to query both production, archived and historical data specified by user defined criteria(e.g.,
T 258.0 by purchase document number, by specific vendor, state fiscal year, federal fiscal year, calendar year, month/year, quarter/year, date
range and year-to-date).
T 259.0 The Proposed Solution shall provide the ability to attach/link the query and selection criteria to reports.
T 260.0 The Proposed Solution shall provide the ability to sort and aggregate data by substrings of field values.
The Proposed Solution shall allow calculation and comparison of report data by any element or combination of elements in the database.
T 261.0
The Proposed Solution shall provide the ability to display the code value (e.g., cost code, account code) and brief description (e.g., contract
T 262.0
type, coding structure) of any data field used in a query or report.
The Proposed Solution shall provide the ability to filter (e.g., by specific vendor, buyer, or program in an organization) when generating a
T 263.0
report.
T 264.0 The Proposed Solution shall provide the ability to include derived fields in queries and reports.
T 265.0 The Proposed Solution shall provide the ability to create normative comparisons.
T 266.0 The Proposed Solution shall provide the ability to reconcile summary level query results with detail data.
Area # Stage 1 - FI$Cal Non-Functional Requirements
The Proposed Solution shall provide menu-driven report editing capabilities, including but not limited to:
• The ability to select for multiple unduplicated counts in the same report
• The ability to apply aggregate functions (e.g., sum, average, minimum and maximum)
T 267.0 • The ability to perform multi-level sorts in ascending and descending order
• The ability to generate summary reports that hide report details
• The ability to generate detailed reports with summary information
The Proposed Solution shall provide the ability to print (e.g. reports, text, tables, data maps, charts, /graphs, requisitions, solicitations,
T 268.0 purchase documents, labels, user created lists such as a bid list, log of waivers, justifications, certifications, requests, project documents,
and receiving log), based on user-defined criteria.
The Proposed Solution shall provide the ability to save data in reports and support distribution to other users (e.g., fax, PDA and email
T 269.0
attachment).
The Proposed Solution shall provide the ability to save the query structure, selection criteria and report formatting for single and multiple
T 270.0
users and by multiple agencies.
The Proposed Solution shall provide the ability to save reports in multiple formats (e.g., .rtf, .txt, .CSV, .xls, .gif, .jpg, HTML, PDF and
T 271.0
ASCII).
The Proposed Solution shall have the ability to preclude directing data (e.g., documents, reports, and query results) directly to a printer
T 272.0
(e.g., the query results must be viewed by the end user prior to printing).
T 273.0 The Proposed Solution shall provide the ability to permanently delete user-defined reports and user-defined queries.
The Proposed Solution shall provide the ability to display data in multi-color graphical charts (e.g., Bar, Area, Line, Pie and Column) and
T 274.0
provide a complete listing of the graphs and charts supported by the application.
The Proposed Solution shall provide the ability to display at least four data dimensions in table or graph format (e.g., payee, time period,
T 275.0
amount and transaction type).
T 276.0 The Proposed Solution shall provide the ability to drill down to multiple levels from within a graph, table or query results.
T 277.0 The Proposed Solution shall provide the ability to resize any graph.
T 278.0 The Proposed Solution shall allow simultaneous scaling across multiple graphs.
T 279.0 The Proposed Solution shall allow graphs to be displayed in a three-dimensional view.
T 280.0 The Proposed Solution shall provide the ability to customize graph axis scales and point of origin.
T 281.0 The Proposed Solution shall provide the ability to label all data sets and subsets displayed on graphs.
T 282.0 The Proposed Solution shall provide the ability to customize the colors and fill patterns for each data series on a graph.
T 283.0 The Proposed Solution shall provide the ability to display descriptions of all metadata in graphs.
The Proposed Solution shall provide the ability to customize report text/font (e.g. multiple font selection, font size, font style and text
T 284.0
alignment).
T 285.0 The Proposed Solution shall provide the ability to add standard and custom watermarks to reports.
T 286.0 The Proposed Solution shall provide the ability to draw custom borders around sections of report text.
T 287.0 The Proposed Solution shall provide the ability to remove report headers and footers during export of query results.
Area # Stage 1 - FI$Cal Non-Functional Requirements
The Proposed Solution shall provide the ability to add remarks or comments within a report and to save and print the comments with the
T 288.0
report.
T 289.0 The Proposed Solution shall provide the ability to audit exports of report data or modifications to report definitions.
The Proposed Solution shall provide the ability to generate and distribute reports based on events, process milestones, pre-defined data
T 290.0
thresholds or user defined criteria.
T 291.0 The Proposed Solution shall provide the ability to create various reports and “what if” analysis based on user defined criteria.
The Proposed Solution shall provide the ability to conduct what-if analysis using current, historic, and forecasted data across multiple
T 292.0 tables (e.g., customers, buyers, suppliers, items, time spans, requisitions, solicitations, product shipments, delivery, and workflow
bottlenecks) either from the operational database or from an archival database based on user-defined criteria.
The Proposed Solution shall provide the ability to choose collation sequences and quantities for standard reports, financial statements and
T 293.0
transmittal letters.
T 294.0 The Proposed Solution shall provide the ability to create, format and update transmittal letters and cover sheets.
T 295.0 The Proposed Solution shall provide the ability to create, format and update a table-of-contents.
T 296.0 The Proposed Solution shall have the ability perform data anomaly and deviation analysis based on user-defined criteria.
The Proposed Solution shall have the ability to select approval data (e.g., printed name, signature, title, date) based upon user defined
T 297.0
criteria (e.g., no identification, one or more individuals identified).
Scorecard/Dashboard (Metrics)
The Proposed Solution shall provide statistical functions (e.g. sum, average, mean, variance, standard deviation, minimum/maximum and
T 300.0
range of values).
The Proposed Solution shall provide statistical functions allowing queries across data dimensions for all fields in the database (e.g.,
T 301.0
compare first quarters over a period of years).
T 302.0 The Proposed Solution shall provide statistical functions allowing queries of summary and detail data.
The Proposed Solution shall provide statistical functions generating modeling and statistical data through a menu-driven Graphical User
T 303.0
Interface (GUI) without the need for manually entered syntax.
The Proposed Solution shall provide the ability to specify statistical counting methods, including unique (unduplicated) counts for multiple
T 304.0
fields.
T 305.0 The Proposed Solution shall provide the ability to filter out duplicates in a single query.
The Proposed Solution shall provide desktop Graphical User Interface (GUI) interfaces (dashboard) that are easy to understand and
T 306.0
navigate in addition to traditional reporting and online presentation.
Data Warehouse
The Proposed Solution's data warehouse shall accept data feeds based on user defined criteria (e.g., hourly, daily, weekly, monthly and on
T 309.0
demand).
The Proposed Solution's data warehouse shall accept multiple feeds from the same or different sources based on user defined criteria
T 310.0
(e.g. daily, weekly, monthly and on demand).
The Proposed Solution's data warehouse shall allow importing of data to the database with no interruption to availability or perceived
T 311.0
degradation to performance.
T 312.0 The Proposed Solution's data warehouse must allow authorized users to release or delete data which failed to be imported or had errors.
Area # Stage 1 - FI$Cal Non-Functional Requirements
T 313.0 The Proposed Solution's data warehouse shall identify errors in received data transmissions.
T 314.0 The Proposed Solution's data warehouse shall support validation and verification of the data to be imported into the data warehouse.
T 315.0 The Proposed Solution's data warehouse shall allow for a distributed approach to data access using data marts.
The Proposed Solution's data warehouse shall allow data sharing between FI$Cal and other agency and external entity systems data
T 316.0
warehouses and data marts.
T 321.0 The Proposed Solution shall provide the ability integrate with data modeling tools to facilitate data warehouse design.
The Proposed Solution shall provide the ability to integrate with modeling tools to assess the impact of prospective changes to the data
T 322.0
warehouse design.
The Proposed Solution shall provide the ability to perform data transformations such as cleansing, validation, auditing, and semantic,
T 323.0
structural or format reconciliation.
The Proposed Solution shall provide the ability to implement metadata management features such as semantic integration, metadata
T 324.0
sharing and synchronization.
T 325.0 The Proposed Solution shall provide the ability to move data in batch or real-time mode.
The Proposed Solution shall provide the ability to deploy performance and capacity scaling strategies such as parallel processing,
T 326.0
distributed processing, partitioning and caching.
Systems Administration
System Administration
T 327.0 The Proposed Solution shall conform to industry standard Information Technology Infrastructure Library (ITIL) Practices.
T 335.0 The Proposed Solution shall allow authorized users to maintain tables, parameters, values, codes, sort or selection criteria, etc.
T 336.0 The Proposed Solution shall allow authorized users to create and define new fields.
The Proposed Solution shall provide the ability to suppress fields and data elements, both standard and user-defined, when displaying on-
T 337.0
screen, printing, and producing reports.
Business Continuity & Disaster Recovery
The Proposed Solution shall be capable of restoring the State's ability to issue warrants within four (4) hours of any disruption in service.
T 355.0
The Proposed Solution shall provide within four (4) hours of any disruption in service the ability for the State to validate a payment voucher
T 356.0
for proper appropriation authority and sufficient cash in the appropriate account to issue warrants.
The Proposed Solution shall provide the State the ability to provide information on the status of the State's cash balances and cash
T 357.0
requirements within four (4) hours of any disruption in service.
The Proposed Solution shall provide the State the ability to provide information to banks on the status of the State's cash balances and
T 358.0
cash requirements within four (4) hours of any disruption in service.
The Proposed Solution shall provide the State the ability to prepare the detailed information for the Governor’s Budget, which by law must
T 359.0
be submitted, to the Legislature by January 10th, within four (4) hours of any disruption in service.
The Proposed Solution shall provide the State the ability to record actions taken by the Legislature during hearings and to provide updates
T 360.0
on the State's General Fund condition or the condition of other funds within four (4) hours of any disruption in service.
The Proposed Solution shall provide the State the ability to finalize the State Budget based upon Legislative actions and the Governor's
T 361.0
veto process within four (4) hours of any disruption in service.
Area # Stage 1 - FI$Cal Non-Functional Requirements
The Proposed Solution shall provide the State the ability to communicate the approved expenditure authority contained within the enacted
T 362.0
State Budget within four (4) hours of any disruption in service.
The Proposed Solution shall provide the State the ability to coordinate with professional engineering organizations and California
T 363.0 Emergency Management Agency (CalEMA) in recruiting, orienting, and training volunteer structural engineers within several business days
of any disruption in service.
The Proposed Solution shall provide the State the ability to enter into contracts and procure goods and services to meet emergency
T 364.0
response activities of the State within four (4) hours of any disruption in service.
The Proposed Solution shall provide State departments the ability to continue critical business processes, including disbursement, budget
T 365.0 development and publication, and determining the State's cash balance at an acceptable level despite a disruption of business functions
within four (4) hours of any disruption in service.
The Proposed Solution shall provide the State the ability to process payment vouchers and electronic tape claims within four (4) hours of
T 371.0
any disruption in service.
The Proposed Solution shall provide the State the ability to process "date specific" payment vouchers and electronic tape claims (e.g.,
T 372.0 retirement payments, Apportionments and Legislative Payroll) to issue payment on dates mandated by State law within four (4) hours of
any disruption of service.
The Proposed Solution shall provide the State the ability to produce the Comprehensive Annual Financial Report to be included in State
T 373.0 bond offering documents, including the Preliminary Official Statements and Official Statements, within one (1) day of any disruption of
service.
System Performance
System Performance Metrics
The Proposed Solution shall provide the ability to report metrics (e.g., transactions per second, workflow processes and concurrent users).
T 388.0
T 395.0 The Proposed Solution shall complete 95% of online transactions within 1.5 seconds.
The Contractor shall be responsible for the development and documentation on all available query processing performance benchmark
T 397.0 reports and analysis for the Proposed Solution. The Contractor will be expected to include this as part of the document titled "System
Performance Metrics".
T 398.0 The Proposed Solution shall complete 90% of predefined report/queries in less than thirty (30) seconds from submission.
T 399.0 The Proposed Solution shall complete 95% of standard reports within five (5) minutes.
T 400.0 The Proposed Solution have the ability to execute reports in a synchronous or asynchronous manner.
T 401.0 The Proposed Solution shall support a database retention as defined in Appendix I-01 Data Conversion and Retention.
T 402.0 The Proposed Solution shall allow for a minimum of 5000 concurrent users (approximately 30% of potential users).
T 403.0 The Proposed Solution shall allow for a minimum of 500 concurrent transactions.
Implementation (I) Requirements
Standards and Policies
The Proposed Solution shall meet all internal control requirements of the Federal General Accounting Office (GAO), the Federal Office of
I 8.0
Management and Budget (OMB), and the American Institute of Certified Public Accountants (AICPA).
Area # Stage 1 - FI$Cal Non-Functional Requirements
The Proposed Solution shall meet the applicable requirements outlined by the Federal General Accounting Office (GAO), the Federal
I 9.0 Office of Management and Budget (OMB), and the Code of Federal Regulations Title 32 Part 33 as related to accounting requirements for
Federal funds.
The Proposed Solution shall meet the applicable requirements of the Governmental Accounting Standards Board (GASB), and the
I 10.0
Financial Accounting Standards Board (FASB).
The Proposed Solution shall provide the ability to meet the reporting requirements of the Federal Census Bureau's annual survey of State
I 11.0
Government Finances for statistical estimates of State's revenue expenditures, debt and assets.
I 13.0 The Proposed Solution shall provide the ability to meet the public message standards.
The Proposed Solution shall be implemented so that the roles and responsibilities of the "Control Agencies" will remain the same as before
I 15.0
the implementation of the FI$Cal system unless a change is approved by the agency involved (See Control Agency Matrix).
The Proposed Solution shall provide the ability to meet California Uniform Codes Manual (UCM) requirements, as administered by the
I 16.0 Department of Finance (DOF). The State intends to modify the UCM in alignment with the COA Strategy, the FI$Cal Vision and Strategy,
and best practices.
The Proposed Solution shall provide the ability to meet California State Administrative Manual (SAM) requirements. The State intends to
I 17.0
modify the SAM in alignment with the FI$Cal Vision and Strategy, and to adopt best practices.
The Proposed Solution shall provide the ability to meet all Federal and State mandated requirements. The State intends to modify State
I 18.0
mandates in alignment with the FI$Cal Vision and Strategy, and to adopt best practices.
The Proposed Solution shall provide the ability to maintain the confidentiality and privacy of extremely sensitive, specific data, for reasons
I 19.0 identified by the State including specific payments (e.g., car payables, gas payables, and contract payables) submitted by law enforcement
agencies.
The Proposed Solution shall meet the applicable requirements of the Generally Accepted Auditing Standards (GAAS) so auditors can
I 662.0 minimize the probability of missing material information including the general standards, standards of fieldwork, and standards of reporting.
Data Conversion and Retention
Data Retention, Archiving & Historical Reporting
The Proposed Solution shall store supporting documentation related to data, retaining the linkages as defined by State defined criteria.
I 263.0
The Proposed Solution shall provide the ability to flag historical data to remain immediately available until designated for archive based on
I 270.0
user-defined criteria (e.g., business rules and State policy).
The Proposed Solution shall provide a mechanism for automatically and manually purging data (e.g., duplicate data and erroneous data)
I 274.0
based on State defined criteria (e.g., business rules and State policy).
Interfaces
Interface Management
The Proposed Solution shall have the ability to route an interface transaction based on the data source, data structure, content of data,
I 314.0 business rule, and any combination of these elements.
System and Program Documentation
Online Help Documentation
Area # Stage 1 - FI$Cal Non-Functional Requirements
The Proposed Solution shall provide Online Help for technical (e.g., System Administrators) and end-users which supports multiple levels
I 535.0
of expertise.
Security (S) Requirements
General Security
The Proposed Solution shall comply with the latest published referenced security practices, standards, and regulations when mentioned
S 5.0
within these security requirements.
S 6.0 The Proposed Solution shall utilize International Organization of Standardization (ISO) 27002 best practices.
S 7.0 The Proposed Solution shall comply with the Federal Information Security Management Act (FISMA).
S 8.0 The Proposed Solution shall comply with National Institute of Standards and Technology (NIST) SP 800-53 at the moderate level.
S 9.0 The Proposed Solution shall comply with Internal Revenue Service (IRS) 1075.
The Proposed Solution shall comply with the latest Payment Card Industry (PCI) Security Standards Council data security standards
S 10.0
published at the time of contract award.
S 11.0 The Proposed Solution shall comply with the Health Insurance Portability and Accountability Act (HIPAA).
S 12.0 The Proposed Solution shall comply with National Automated Clearing House Association (NACHA) requirements.
The Proposed Solution shall employ host intrusion detection (HID) and a host-based intrusion prevention system (HIPS). The HID process
S 13.0 service will be expected to monitor events and log files from operating systems, and related processes and provide notification of events,
while HIPS will be expected to use deep packet analysis to control and prevent unauthorized access.
The Proposed Solution shall display a State, legally approved, system use notification message before granting system access. The
Proposed Solution shall inform potential users: (i) that the user is accessing a State Government information system; (ii) that system usage
S 14.0 may be monitored, recorded, and subject to audit; (iii) that unauthorized use of the system is prohibited and subject to criminal and civil
penalties; and (iv) that use of the system indicates consent to monitoring and recording. The Contractor shall ensure that the notification
message remains on the screen until the user takes explicit actions to log on to the Proposed Solution.
The Proposed Solution shall appropriately label information, based on classification and business requirements, in output, regardless of the
S 15.0
medium, and in transmission.
The Proposed Solution shall physically and logically separate user interface services (e.g., public web pages) from information storage and
S 16.0
management services (e.g., database management).
The Proposed Solution shall identify and handle error conditions in an expeditious manner without providing information that could be
S 17.0
negatively exploited.
The Proposed Solution shall generate error messages providing timely and useful information without revealing potentially harmful,
S 18.0
confidential, or sensitive information that could be used by adversaries.
The Proposed Solution shall ensure confidential or sensitive information (e.g., account numbers, social security numbers, and credit card
S 19.0
numbers) are not listed in error logs or any associated administrative messages.
The Proposed Solution shall verify information for accuracy, completeness, validity, and authenticity. Verifications of accuracy,
completeness, validity, and authenticity of information shall be accomplished as close to the point of origin as possible. The Contractor will
ensure that rules for checking the valid syntax of system inputs (e.g., character set, length, numerical range, acceptable values) are in
S 23.0
place to verify that inputs match specified definitions for format and content. Inputs passed to interpreters shall be prescreened to prevent
the content from being unintentionally interpreted as commands. The extent to which the information system is able to check the accuracy,
completeness, validity, and authenticity of information is guided by business requirements.
Encryption
Area # Stage 1 - FI$Cal Non-Functional Requirements
S 31.0 The Proposed Solution shall ensure confidential or sensitive data shall be encrypted during transport.
The Proposed Solution shall employ and manage cryptographic keys using automated mechanisms with supporting procedures or manual
procedures when cryptography is required by business need or requirement.
S 32.0
See National Institute of Standards and Technology (NIST) Special Publication 800-56 and 800-57.
Cryptography utilized by the Proposed Solution shall comply with FIPS 140-2 (as amended) and validation certificates issued by the
S 33.0
National Institute of Standards and Technology (NIST) Cryptographic Module Validation Program.
Remote Access
S 38.0 The Proposed Solution shall authorize, monitor, and control all methods of remote access to the Proposed Solution.
The Proposed Solution shall restrict access provided through remote connections (e.g., limiting dial-up access based upon source of
S 39.0
request).
The Proposed Solution shall protect against unauthorized connections or subversion of authorized connections (e.g., using virtual private
S 40.0
network technology).
Security Administration
The Proposed Solution shall provide the ability to access Proposed Solution products for administrative purposes through an encrypted
S 46.0
session.
The Proposed Solution shall isolate security functions from non-security functions.
S 47.0
See National Institute of Standards and Technology (NIST) SP 800-53 for further guidelines on Security Function Isolation.
Authorization
The Proposed Solution shall manage access accounts, including establishing, activating, modifying, reviewing, disabling, and removing
S 48.0 accounts. Access Account management includes the identification of account types (i.e., individual, group, and system), establishment of
conditions for group membership, and assignment of associated authorizations based on business needs.
The Proposed Solution shall enforce assigned authorizations for controlling the flow of information within and between interconnected
S 49.0
systems in accordance with business needs.
S 50.0 The Proposed Solution shall enforce separation of duties through assigned access authorizations.
The Proposed Solution shall enforce the most restrictive set of rights/privileges or accesses needed by users (or processes acting on
S 51.0
behalf of users) for the performance of specified tasks based on business requirements.
S 52.0 The Proposed Solution shall allow for the ability to enforce a configurable limit of consecutive invalid access attempts by a user.
The Proposed Solution shall ensure the system automatically locks an account when the maximum number of unsuccessful access
S 53.0
attempts is exceeded.
The Proposed Solution shall allow the ability for password self service reset (i.e., after lockout) after authentication of user by challenge
S 54.0
response processes or equivalent.
S 55.0 The Proposed Solution shall allow for the ability for a password to automatically reset after a configurable amount of time.
The Proposed Solution shall prevent further access to the system by initiating a session lock after a configurable amount of time of
S 56.0 inactivity. The session lock shall remain in effect until the user reestablishes access using appropriate identification and authentication
procedures.
The Proposed Solution shall automatically terminate a remote session after a maximum of fifteen (15) minutes of inactivity and have the
S 57.0
ability to be configured for a different time frame.
Area # Stage 1 - FI$Cal Non-Functional Requirements
Authentication
S 58.0 The Proposed Solution shall uniquely identify and authenticate users (or processes acting on behalf of users).
The Proposed Solution shall support multiple authentication methodologies including but not limited to strong passwords, tokens,
S 59.0 biometrics, or in the case of multifactor authentication, some combination thereof for each activity conducted based on business identity
assurance requirements.
The Proposed Solution shall ensure authentication methodologies are utilized to confirm user identity conforms to National Institute of
S 60.0
Standards and Technology (NIST) Special Publication 800-63 and to any other assurance levels determined by the State.
The Proposed Solution shall identify and authenticate specific devices before establishing a connection for non-public users using an
S 61.0 organizational authentication solution (e.g., IEEE 802.1x and Extensible Authentication Protocol (EAP) or a Radius server with EAP-
Transport Layer Security (TLS) authentication) to identify and authenticate devices on local and/or wide area networks.
The Proposed Solution shall obscure feedback of authentication information during the authentication process to protect the information
S 62.0
from possible exploitation/use by unauthorized individuals.
Auditing
The Proposed Solution shall provide the capability and sufficient capacity to record all events that occur within all layers of the Proposed
Solution (e.g., operating system, application, network, and middleware and database) The required events will include at a minimum any
attempt to log on (successful or unsuccessful), the log-on ID, date and time of each log-on attempt, date and time of each log-off, the
S 63.0
devices used, and the function(s) performed once logged on (e.g., the applications that the user successfully or unsuccessfully attempted
to invoke), data files opened and closed, specific actions, such as reading, editing, and deleting records or fields, and printing reports or
other media creations (i.e., exporting information to another media such as printer, and CD).
The Proposed Solution shall allocate sufficient audit record storage capacity to configure auditing that will reduce the likelihood of such
S 64.0
capacity being exceeded.
The Proposed Solution shall provide a real-time alert to appropriate FI$Cal personnel with the ability to stop transaction processing in the
S 65.0
event of an audit processing failure.
S 66.0 The Proposed Solution shall provide an audit report generation capability based on business needs and requirements.
S 67.0 The Proposed Solution shall provide time stamps normalized with Coordinate Universal Time (UTC).
S 68.0 The Proposed Solution shall protect audit information and audit tools from unauthorized access, creation, modification, and deletion.
The Proposed Solution shall, based on business need, provide the capability to determine whether a given individual initiated a particular
S 69.0 action(s). Examples of particular actions taken by individuals include creating information, sending a message, approving information (e.g.,
indicating concurrence or signing a contract), and receiving a message.
Network Security
S 74.0 The Proposed Solution shall protect against or limit the effects of a denial of service attack.
The Proposed Solution shall protect the confidentiality and integrity of transmitted information.
S 76.0
See National Institute of Standards and Technology (NIST) Special Publications 800-52, 800-77 and 800-81.
The Proposed Solution shall terminate a network connection at the end of a session or after thirty (30) minutes of inactivity providing an
S 77.0
administrator the ability to configure termination for an alternate time frame.
OCIO (O) Requirements
SOA - General
Area # Stage 1 - FI$Cal Non-Functional Requirements
O 1.0 The Proposed Solution shall conform to Web Services Definition Language (WSDL).
The Proposed Solution shall adhere to web service standards defined by the Organization for the Advancement of Structured Information
O 2.0
Standards (OASIS).
O 3.0 The Proposed Solution shall adhere to web service standards defined by the World Wide Web Consortium (W3C).
The Proposed Solution shall have the ability to communicate between FI$Cal's Web Service(s) and external systems using the Enterprise
O 4.0
Service Bus (ESB) provided by the Department of Technology Services (DTS).
The Proposed Solution shall have the ability to use Universal Description Discovery and Integration (UDDI) to discover web services
O 6.0
advertised by other entities.
O 7.0 The Proposed Solution shall have the ability to advertise available web service(s).
The Proposed Solution shall have the ability to provide an identity credential to publish or modify a service in the DTS OASIS Universal
O 8.0
Description Discovery and Integration (UDDI) registry.
The Proposed Solution shall have the ability to define access restrictions to services published to the DTS OASIS Universal Description
O 9.0
Discovery and Integration (UDDI) registry.
SOA - Web Services Design and Composition
The Proposed Solution shall have the ability to use Web Services Business Process Execution Language (BPEL) to specify business
O 11.0
process behavior based on Web Services.
Identity Management - Authentication
O 12.0 The Proposed Solution shall conform to OCIO’s Federated Identity Management Standard Compliance Component.
Identity Management - Web Services Security
The Proposed Solution shall secure all web services communication between FI$Cal and other agencies adhering to the WS-I Basic
O 15.0
Security Profile.
O 16.0 The Proposed Solution shall encrypt all confidential, sensitive, or personal data transmitted using web services.
