My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Item 26 - Agreement with Allied Network Solutions, Inc. for Adobe Software and Subscription
Clerk
>
Agenda Packets / Staff Reports
>
City Council (2004 - Present)
>
2025
>
01/21/2025 Regular & Special SA
>
Item 26 - Agreement with Allied Network Solutions, Inc. for Adobe Software and Subscription
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/27/2025 5:03:20 PM
Creation date
1/21/2025 2:16:24 PM
Metadata
Fields
Template:
City Clerk
Doc Type
Agenda Packet
Agency
Information Technology
Item #
26
Date
1/21/2025
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
762
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
SOLICITATION # CH16012 <br />reduces false positives and keeps analysts and customers focused on real, actionable incidents. <br />In addition, Alert Logic's security research team continuously monitors threat data and tunes the <br />Expert System to respond to the most current threats. <br />SAP <br />Ariba <br />Within our solution, specific logging takes place that is viewable by the <br />customer administrator or their designee. Audit logs produced through use of <br />the solution are considered customer data and are maintained within the <br />customer's instance of the database. These logs are retained so long as the <br />customer has an active contract with us. <br />As a user control consideration, customers are responsible for monitoring the <br />proper entry of data to the solution and reviewing reports generated by the <br />system. <br />Fieldglass <br />Fieldglass has a comprehensive set of performance monitoring tools in place. <br />Some tools are built in the application and some are external. <br />The Fieldglass application captures every page hit and the time it takes to <br />respond. It captures the server response time and the client rendering time <br />separately. The average page times are available to be seen by privileged <br />users through the application. The user can drill down to the hour or minute or <br />a single request for analysis. The information can be displayed by time range <br />for all users, by company, or even for an individual user. <br />Orion Network Monitoring watches more than 1,000 different points of interest <br />on the production infrastructure. These monitors include, but are not limited to, <br />the following: CPU, Memory, I/0, Capacity and Synthetic Transactions. These <br />monitors along with our custom application performance monitors are used to <br />produce and comply with customer SLA requirements. <br />Fieldglass also uses Splunk Enterprise Security for event/audit log collection <br />and correlation. Events and logs are retained online for 90 days and offline for <br />two years. <br />Alerts are generated and reviewed as they occur. <br />Hanna <br />SAP HEC uses Solution Manager for monitoring the infrastructure end to end. <br />Hybris <br />SAP Hybris offers continuous 24/7 systems monitoring in -place, which <br />automatically notifies you, SAP Hybris support and optionally your designated <br />implementation partner in the event of any monitored system problem. Tools <br />used for monitoring include HP Sitescope and Nagios. This service ensures <br />quick response times to emergency problems. Standard monitors are in place <br />for basic site availability. Customer can utilize additional 3rd party monitoring <br />services should it wish to add additional monitoring. Upon request, monthly or <br />quarterly reviews are offered to review performance over the period. When a <br />system problem occurs, in addition to monitor alerts sent to the customer, <br />SAP Hybris support may send emails to a designated customer notification <br />email address to provide status, updates or further detailed information. In <br />addition, a support ticket would be created which would include such <br />information. <br />SuccessFactors <br />The application logs the following for every transaction: Event/transaction <br />Time, Transaction ID, Event/transaction Type, Event/transaction Status <br />(Result of the event; if failure, includes reason), Object Attributes (Describes <br />the object affected by the event), Originator User ID (ID of the user who <br />initiated the event or action), Subject ID, Process User ID, Account Number, <br />Transaction Specific Elements. <br />The application audits changes to the major components. Examples of this are <br />goal auditing and document auditing. The audit trail includes who made the <br />change, the date of the change and the ability to see the data as it existed at <br />carahsoft 175 carahsoft <br />
The URL can be used to link to this page
Your browser does not support the video tag.