ATTACHMENT_1_APM_RFI_06202019.pdf

13 May, 2019 HRC Application Performance Monitoring Project Requirements Specification Matrix (RSM)

Stakeholder Requirement Number:

Functional Requirement

Number:

Technical Requirement Number: Objective/Outcome

Business Requirement 1.0.0.0 Functional Requirement

FR 1.1.0.0

Analytic Dashboards & Content

Technical Requirement

TR 1.1.1.0

Solution shall allow all visualizations, dashboards, configuration, analysis, collaboration, etc. within a single, browser-based user interface that is controlled by role-based access.

TR 1.1.2.0 Solution shall have a community of fully-supported extensions and/or integrations which can ingest metrics from third-party components, such as F5 load balancer, VMware hypervisor, etc. The metrics ingested shall follow the same baseline/trending approach as metrics collected by native agents.

Technical Requirement

TR 1.1.3.0

Solution shall automatically draw application topology maps in runtime that use the auto-discovered Business Transactions to trace application flow.

Technical Requirement

TR 1.1.3.1

Solution shall develop the service dependency mapping that directly maps to the APMS -->ADDM-->Playbooks-->SPECTRUM-->Vendor Aplication

Technical Requirement

TR 1.1.3.2

Solution should apply modeling from service dependency mapping that directly maps to the APMS -->ADDM-->Playbooks-->SPECTRUM-->Vendor Aplication to the single pane of glass.

TR 1.1.4.0 Soliton shall provide the ability to visualize, perform complex queries, both drag-and-drop and query-language based, math functions and graphing of metrics into dashboards and reports

TR 1.1.5.0 Solution shall provide the ability to define log file patterns for ingest of various complex log file types, from multiple disparate sources, using grok patterns or drag-and-drop UI and based on field format of supplied example log file contents

Functional Requirement

FR 1.2.0.0

Application Availability/Responsiveness Monitoring

Comments

Log File Configuration

Requirement Descripton

Single pane of glass for metric visualizarion and analysis

Single pane of glass integration with additional components

Visualization and Mapping

Visualization and Mapping

Visualization and Mapping

Backend Configuration Interface

Description: HRC Enterprise Network Application Performance Monitoring

Application Monitoring Monitoring (APM) is a critical part of systems management and ensuring network stability and maintenance which is necessary to ensure continuity of customer services, enhanced customer experiences and effective and efficient stewardship of the information systems required to support personnel information for the Human Resources Enterprise Network serving the Army Human Resources Command, the Army Recruiting Command and the Army Cadet Command.

Requirement Descripton

TR 1.3.1.00

TR 1.2.2.0 Solution shall provide automatic detection of entry points of running applications having the following component types: Servlet, Struts, SOAP/REST web services, Spring Beans, EJB, JMS, Java Objects, Binary Remoting, ASP.NET, WCF, .NET Class/Method, Message Queues, PHP Web/CLI/MVC, Drupal, Wordpress, Apache HTTP Server

TR 1.2.3.0 Solution shall ensure deep granularity of running application code, including framework as well as custom code, to be included in transaction snapshot call graphs out-of-the-box, without requiring additional configurations post-install and without disruptive performance impact.

TR 1.2.3.1 Solution shall , deconflict existing modeling and monitoring, to reduce & remove dependency on other "APM Like" tools. For example: Zabbix, SCOM.

TR 1.2.4.0 Solution shall provide synthetic private agents enabling the ability to monitor internal websites or services that are not accessible outside the network boundaries, and allows the synthetic metrics to be displayed and compared to real-user experience metrics

TR 1.2.5.0 Solution shall provide browser performance and timings on applications with full HTTP page loads as well as AJAX calls, IFrames, Virtual Pages and Single-Page Applications and collect the following: Sessions, Page & AJAX request performance (unique and aggregated) [@TODO: add additional]

TR 1.2.6.0 Solution shall display end user experience of individual clicks, including each phase of the page load lifecycle, as well as Session capture to enable ‘User Journey’ reporting across multiple browser requests [@TODO: add additional]

TR 1.2.7.0 Solution shall provide ability to trigger Alerting (notifications) and Remediation (scripts, workflows, ITSM integration, etc.) off the dynamic baselines for any metric being collected.

TR 1.2.7.1 Solution shall provide for systems management, alerting and proactive/reactive notifications

TR 1.2.8.0 Solution shall fully correlate individual transactions with single or double click within the same UI: Browser or Mobile session into middle-tier application runtime transaction into database health as well as infrastructure health for all instrumented components

Granular monitoring and defined actionable remediation without impact

Internal Website and Service Monitoring

Browser Collection Metrics

Provide automated entry point detection

Granular monitoring and defined actionable remediation without impact

Browser and Mobile Correlation with Backing Infrastructure

User Experience Collection Metrics

Alerting and Remediation Triggering

Alerting and Remediation Triggering

TR 1.2.9.0 Solution shall provide ability to dynamically collect method parameters, HTTP header and session values, browser cookie values and other data points across every transaction within the running application without requiring code changes to the application itself. Solution shall also provide an ability to similarly disable this feature if required.

TR 1.2.10.0 Solution shall provide Response Time, Throughput, Error Rates.

TR 1.2.11.0 Solution shall report most time consuming transactions.

TR 1.2.12.0 Solution shall include ability to provide data for thread dump analysis

TR 1.2.13.0 Solution shall include ability to provide cross application Tracing

TR 1.2.14.0 Solution shall provide Xray Sessions.

TR 1.2.15.0 Solution shall provide Services Mapping.

TR 1.2.16.0 Solution shall provide deployment analysis history comparisons.

TR 1.2.17.0 Solution shall provide application histograms.

TR 1.2.18.0 Solution shall provide performance reporting of external services.

TR 1.2.19.0 Solution shall provide transaction metric traces.

TR 1.2.20.0 Solution shall provide access to performance data API.

TR 1.2.21.0 Solution shall track Key Business Transactions.

TR 1.2.22.0 Solution shall provide JVM Performance Analyzer.

TR 1.2.23.0 Solution shall provide Baseline Performance.

Browser and Mobile Collection

Response Time, Throughput, Error Rates

Xray Sessions

Services Map

Deployment Analysis History Comparison

Application Histograms

Performance of External Services

Transaction Metric Traces

Most Time Consuming Transactions

Thread Profile

Cross application Tracing

Access to Performance Data API

Track Key Business Transactions

JVM Performance Analyzer

Baseline Performance

TR 1.2.24.0 Solution shall provide Auto Discovery and Mapping.

TR 1.2.25.0 Solution shall provide Application Debugging.

TR 1.2.26.0

Total Transaction Response Time (Sec)

Time from client Hello to fin/ack or rst on the given transaction

Solution shall provide a total transacton Response time from client Hello to fin/ack or rst on the given transactionmeeting or exceeding industry standard of 0.5 sec.

Client-side Transaction Time (sec) Time taken by the client to respond to server request Solution shall provide a Client-side Transaction Time taken by the client to respond to server request meeting or exceeding industry standard of 0.25 sec.

Tier 3 (App server to DB server) Response Time (sec

Time it takes the back end server to respond to application server (Syn to fin/ack) rs

Solution shall provide aTier 3 (App server to DB server) Response Time meeting or exceeding industry standard of 0.25 sec.

Client Response Time (sec) Total client response time, screen draw, processing, etc.

Solution shall provide a total transacton Response time it takes the back end server to respond to application server (Syn to fin/ack) rs meeting or exceeding industry standard of 0.5 sec.

Response Time (sec Time for server to process request and respond to user transaction

Solution shall provide a Client Response Time for server to process request and respond to user transaction meeting or exceeding industry standard of

0.5 sec.

CPU Utilization (%) CPU utilization on all cores Solution shall provide a CPU Utilization on all cores meeting or execceding industry standard of 70%.

CPU Size Quantity Number of Cores Solution shall identify projected quantity of cores required.

RAM Utilization (%) RAM usage and pagination Solution shall provide a RAMusage and pagination Utilization meeting or execceding industry standard of 70%.

TR 1.2.27.0 Solution should have implementation services with ability to work with third party vendor products.

TR 1.2.28.0

JMX/PMI Java Management Extensions (JMX) Mbeans

Solution should have ability to implement JMX/PMI.

TR 1.2.29.0

Byte Code Bytecode_OOP(Object Oriented Programming)

Solution should have ability to implement Byte Code.

TR 1.2.30.0 Solution should perform auto discovery and deep instrumentation of application code.

Detect and measure response time of all app components activity initiated by a single user request

Implementation Services/ ability to work with 3rd party products

Auto discovery and deep instrumentation of application code

Auto Discovery and Mapping

Application Debugging

Functional Requirement

FR 1.3.0.0

End User/Synthetic Transaction Monitoring

Comments

TR 1.3.1.0 Solution shall separate the real issues from the noise by learning the application's normal behavior as a set of dynamic baselines, and then responding based on abnormalities or movement away from the normal baseline, in order to reduce the time spent on defining health conditions as well as the time spent maintaining those rules as the application changes over time. The solution shall automatically maintain baselines for all metrics collected, and the baselines shall be dynamic in nature to reflect the true performance of the application over time. Alerting (notifications) and Remediation (scripts, workflows, ITSM integration, etc.) shall be driven off the baselines to enable proactive issue identification & resolution.

TR 1.3.2.0 Solution shall provide browser performance and timings on applications with full HTTP page loads as well as AJAX calls, IFrames, Virtual Pages and Single-Page Applications and collect the following: Sessions, Page & AJAX request performance (unique and aggregated) [@TODO: add additional]

TR 1.3.3.0 Solution shall provide ability to dynamically collect method parameters, HTTP header and session values, browser cookie values and other data points across every transaction within the running application without requiring code changes to the application itself. Solution shall also provide an ability to similarly disable this feature if required.

TR 1.3.4.0 Solution shall fully correlate individual transactions with single or double click within the same UI: Browser or Mobile session into middle-tier application runtime transaction into database health as well as infrastructure health for all instrumented components

TR 1.3.5.0 Solution shall provide ability to dynamically collect method parameters, HTTP header and session values, browser cookie values and other data points across every transaction within the running application without requiring code changes to the application itself. Solution shall also provide an ability to similarly disable this feature if required.

TR 1.3.6.0 Solution provides a scalable continuous 24x7x365 synthetic-user capability that can be used internally as well as having the capability of being deployed globally to test, report, alert and alarm regarding access, application availability and proper functionality, process and dependent service provider availability and performance

TR 1.3.7.0 Solution shall notify via email and generate log file that non-availability or error has occurred.

Requirement Descripton

Use baselines/trends to drive behavior; collect the appropriate data and alert/remediate on issues only as needed

Browser and Mobile Collection

Alert Policies

Availability and Error Monitoring

Browser Collection Metrics

Mobile Device Collection Metrics

Browser and Mobile Correlation with Backing Infrastructure

TR 1.3.8.0 Solution shall notify via email and generate log file that client-side error has occurred.

TR 1.3.9.0 Solution shall notify via email and generate log file that synthetic transactions error has occurred.

TR 1.3.10.0 Solution shall notify via email and generate log file that mobile application error has occurred.

TR 1.3.11.0 Solution shall provide session replay ability to replay a User's journey to include users's view (browser or screen output), user input (keyboard and mouse inputs) and logs of network events or console logs.

TR 1.3.12.0 Solution shall provide a Total Transacton Response time meeting or exceeding industry standard of 0.5 sec.

Functional Requirement

FR 1.4.0.0

Supported User Databases Comments

TR 1.4.1.0 The solution shall fully support the required database components, including the ability to view historically the following: sessions, wait states, slow queries, locks, tablespace, execution plans, etc. The solution shall fully correlate transactions from the middle-tier into the database for deep, end-to-end root cause analysis.

TR 1.4.2.0 The solution shall fully support the required database components, including the ability to view historically the following: sessions, wait states, slow queries, locks, tablespace, execution plans, etc. The solution shall fully correlate transactions from the middle-tier into the database for deep, end-to-end root cause analysis.

TR 1.4.3.0 The solution shall fully support the required database components, including the ability to view historically the following: sessions, wait states, slow queries, locks, tablespace, execution plans, etc. The solution shall fully correlate transactions from the middle-tier into the database for deep, end-to-end root cause analysis.

TR 1.4.4.0 The solution shall fully support the required database components, including the ability to view historically the following: sessions, wait states, slow queries, locks, tablespace, execution plans, etc. The solution shall fully correlate transactions from the middle-tier into the database for deep, end-to-end root cause analysis.

TR 1.4.5.0 The solution shall fully support the required database components, including the ability to view historically the following: sessions, wait states, slow queries, locks, tablespace, execution plans, etc. The solution shall fully correlate transactions from the middle-tier into the database for deep, end-to-end root cause analysis.

Session replay

Monitor response time of app to end user

Requirement Descripton

Real User Monitoring

Synthetic Monitoring

Mobile Application Monitoring

Sybase

Oracle

MS SQL

MySQL

DB2

TR 1.4.6.0 The solution shall fully support the required database components, including the ability to view historically the following: sessions, wait states, slow queries, locks, tablespace, execution plans, etc. The solution shall fully correlate transactions from the middle-tier into the database for deep, end-to-end root cause analysis.

TR 1.4.7.0 The solution shall fully support the required database components, including the ability to view historically the following: sessions, wait states, slow queries, locks, tablespace, execution plans, etc. The solution shall fully correlate transactions from the middle-tier into the database for deep, end-to-end root cause analysis.

TR 1.4.8.0 Solution should at minimum collect the following metrics on each database being monitored: sessions, wait states, slow queries, locks, tablespace, execution plans [@TODO: add additional]

TR 1.4.9.0 Solution should at minimum collect the following metrics on each database being monitored: sessions, wait states, slow queries, locks, tablespace, execution plans [@TODO: add additional]

TR 1.4.10.0 Solution should at minimum collect the following metrics on each database being monitored: sessions, wait states, slow queries, locks, tablespace, execution plans [@TODO: add additional]

TR 1.4.11.0 Solution should at minimum collect the following metrics on each database being monitored: sessions, wait states, slow queries, locks, tablespace, execution plans [@TODO: add additional]

TR 1.4.12.0 Solution should at minimum collect the following metrics on each database being monitored: sessions, wait states, slow queries, locks, tablespace, execution plans [@TODO: add additional]

TR 1.4.13.0 Solution should provide searcha and filter capabilities for selected database metrics.

Functional Requirement

FR 1.5.0.0

Misc IT Requirements (HRC) Comments

TR 1.5.1.0 Solution should have ability to create custom agent checks.

TR 1.5.2.0 Solution should have ability to monitor Citrix XenApp and XenDesktop.

TR 1.5.3.0 Solution should have ability to monitor Vmware.

TR 1.5.4.0 Solution should Supports Service Oriented Architecture (SOA).

Mongo / No-SQL Databases

Database Collection Metrics

Time Spent in DB calls

DB Call Response Times

PostgreSQL

Requirement Descripton

Ability to create custom agent checks

Ability to monitor Citrix XenApp and XenDesktop

SQL Query Analysis

Slow Query Reporting

Search and Filter capabilities

Ability to monitor Vmware

Supports Service Oriented Architecture (SOA)

TR 1.5.5.0 Solution shall meets Common Operating Environment (COE) - operating system is Microsoft Windows Server or Red Hat Enterprise LINUX (RHEL).

TR 1.5.6.0 Solution should have Software Developer Kit (SDK) - required for customizations.

TR 1.5.7.0 Solution shall not require thin client to operate.

TR 1.5.8.0 Solution should deliver scheduled reports via email (proactive detection and alerts).

TR 1.5.9.0 Solution should perform direct discovery - renders summary data only - no data replication (security).

TR 1.5.10.0 Solution should allow administrative limitations to be set on access to data tables, elements (limit scope of data access to minimize impact to database).

TR 1.5.11.0 Solution should have no data update capability/or has ability to admin disable update capability.

TR 1.5.12.0 A variety of application runtime technologies are currently utilized or may be utilized in the future including: Java, .NET, relational/SQL and NoSQL databases, Android and iOS applications, web browsers, Apache, PHP, Node.js, C/C++, Python, Windows, Linux and Unix servers etc., COTS suites such as Oracle EBusiness Suite and PeopleSoft, etc. The solution shall fully support all required technology runtime environments. [@TODO:Add full list of COTS/GOTS here.]

TR 1.5.13.0 Solution shall be fully implemented and "always on" in production in order to get complete, relevant metrics on the health of US Army’s applications 24x7. Also, the end users of these applications shall not experience any additional delay or performance degradation due to the solution being turned on at all times. The solution shall maintain a very low overhead of network bandwidth, less than 10 megabits/second for a large-scale deployment (1000+ agents).

TR 1.5.14.0 Solution shall support complete root cause analysis by capturing deep, code-level granularity even during times of high application load, in order to ensure complete visibility during times when issues occur. The solution shall not reduce granularity of performance data captured during these high-workload periods. Granted, shall it be required to disable the solution for the purpose of retaining 100% resources for use by the respective application or supporting systems, the solution shall provide the means to be disabled nondisruptive with respect to the monitored application or any other environment for that matter.

Software Developer Kit (SDK) - required for customizations

Does not require thin client to operate

Ability to deliver scheduled reports via email (proactive detection and alerts)

Meets Common Operating Environment (COE) - operating system is Microsoft Windows Server or Red Hat Enterprise LINUX (RHEL)

Heterogeneous middleware technology support

Little to no impact on production performance

Application metrics collected shall not be limited during times of heavy application workload

Direct discovery - Renders summary data only - no data replication (security)

Allows administrative limitations to be set on access to data tables, elements (limit scope of data access to minimize impact to database)

No data update capability/or has ability to admin disable update capability

TR 1.5.15.0 Solution shall define monitoring or actioning rules to be driven by a baseline-set or manually-set thresholds.

TR 1.5.16.0 Solution shall provide Windows, Linux, AIX, and Solaris [@TODO:Add additional] infrastructure visibility covering the following metrics: CPU & Memory utilization, Network Throughput, Disk Usage & I/O, running processes

TR 1.5.17.0 Solution shall provide NetApp, Hitachi, HPE 3PAR, and other leading storage system visibility and correlation.

TR 1.5.18.0 Solution shall provide integrated network visibility implemented as a OS node-based agent and which delivers the following metrics: throughput, latency, TCP loss, errors, Performance Impacting Events (PIE), which indicates performance issues one node, both nodes and/or the network between the two nodes being monitored

TR 1.5.20.0 Solution shall provide remote data collector that uses protocols such as ssh, wmi, https, jmx, snmp, and REST APIs

Functional Requirement

FR 1.6.0.0

Cloud Deployment Comments

TR 1.6.1.0 Solution shall support cloud deployment as well as on premises data sources

TR 1.6.1.1

Data Transfer In (by selected period of time)

Solution shall support data transfer in for Cloud deployment as well as on premises data.

TR 1.6.1.2

Data Transfer out (by selected period of time)

Solution shall support data transfer out for Cloud deployment as well as on premises data.

TR 1.6.1.3

Number of Unique

Solution shall support number of unique for Cloud deployment as well as on premises data.

TR 1.6.1.4

Users Peak Time

Solution shall support users peak time for Cloud deployment as well as on premises data.

TR 1.6.1.5

Concurrent Users

Solution shall support concurrent users for Cloud deployment as well as on premises data.

TR 1.6.1.6

Page views (by selected period of time)

Solution shall support page views for Cloud deployment as well as on premises data.

TR 1.6.1.7

Data read/writes

Solution shall support data read/writes for Cloud deployment as well as on premises data.

TR 1.6.1.8

CPU size, Quantity

Solution shall support CPU size, Quantity for Cloud deployment as well as on premises data.

Network System Visibility and Compatibility

Ability to monitor hyper converged infrastructures

Requirement Descripton

Prevent unnecessary data collection and alert storms

Infrastructure System Visibility and Compatibility

Storage System Visibility and Compatibility

Supports Cloud deployment as well as on premises data sources

TR 1.6.1.9

Number of Cores

Solution shall support Number of cores for Cloud deployment as well as on premises data.

TR 1.6.1.10

Peak CPU utilization

Solution shall support data Peak CPU utilization for Cloud deployment as well as on premises data.

TR 1.6.1.11

Total RAM Peak

Solution shall support total RAM peak for Cloud deployment as well as on premises data.

TR 1.6.1.12

RAM utilization (%)

Solution shall support RAM utilization (%) for Cloud deployment as well as on premises data.

TR 1.6.1.13

Execution time

Solution shall support Execution time for Cloud deployment as well as on premises data.

TR 1.6.1.14

Query performance

Solution shall support Query performance for Cloud deployment as well as on premises data.

TR 1.6.1.15

Observed storage on-premise (capacity and current occupancy)

Solution shall support observed storage on-premise for Cloud deployment as well as on premises data.

TR 1.6.1.16

Storage durability

Solution shall support Storage durability for Cloud deployment as well as on premises data.

TR 1.6.2.0

Disk Input/Output Operations per Second (IOPS) and bandwidth

Solution shall support disk input/output for Cloud deployment as well as on premises data.

TR 1.6.3.0 Solution should support self-service elasticity for Cloud deployment as well as on premises data.

TR 1.6.4.0 Solution should support monitoring of containers for Cloud deployment as well as on premises data.

Grafana or Elasticsearch search integration with Prometheus Endpoint

Managed cloud metrics platform with Prometheus standard for monitoring Kubernetes.

Solution should provide a managed cloud metric platform capable integration for Kubernets monitoring and management.

Functional Requirement

FR 1.7.0.0

System Access/Security Comments

TR 1.7.1.0 Solution shall support Enterprise User Management without customization (i.e. LDAP).

TR 1.7.2.0 Solution shall ensure all agent-controller traffic traverses using the SSL/TLS encrypted protocol to secure HTTPS ports, without requiring decryption of traffic at any point in the platform. Solution shall also support pre-TLS SSL communications to support legacy application components. [@TODO:List any specifics needed here]

Self-service elasticity

Supports monitoring of containers (i.e. Docker)

Requirement Descripton

Supports Enterprise User Management without customization, i.e. LDAP

Completely secure & encrypted, using well-known ports & protocols throughout platform

TR 1.7.3.0 Solution shall provide a means to export active system logs to a syslog server for recording events and health of the solution system itself.

TR 1.7.4.0 Solution shall allow all visualizations, dashboards, configuration, analysis, collaboration, etc. within a single, browser-based user interface that is controlled by role-based access and can be integrated with existing

Functional Requirement

FR 1.8.0.0

Concurrency/Scalability Comments

TR 1.8.1.0 Solution shall provide multiple methods for integrating with ticketing and/or issue management systems, such as BMC Remedy, JIRA, etc. The methods shall include automated emails/SMS, HTTP/HTTPS (current required TLS level) request templates, ability to run custom scripts on remote hosts, etc.

TR 1.8.2.0 Solution shall enhance agile workflows and provide multiple methods for integrating with CI/CD, configuration & release management systems, such as Jenkins, Chef, Puppet, Git, SVN, etc., in order to enable true agility and feedback loops within a DevOps environment.

TR 1.8.3.0 Solution shall be able to scale quickly and easily to support many custom applications, with the ability to grow that footprint as necessary. The solution shall have the ability to scale to thousands of agents for a single Controller platform, without any need for intervening collectors or additional aggregators lying in between agents and Controller.

Functional Requirement

FR 1.9.0.0

License Pricing Agreement Comments

TR 1.9.1.0 Solution shall be available at enterprise licensing models.

TR 1.9.2.0 Solution shall be available costing at per user licensing models.

TR 1.9.3.0 Solution shall be available costing at per server/CPU licensing models.

TR 1.9.4.0 Solution shall be available at user token licensing models.

Functional Requirement

FR 1.10.0.0

Misc Other Comments

TR 1.0.1.0 Solution shall be capable of achieving a Certificate of Networthines (CoN) on the HRC networks.

Backend Management System

Requirement Descripton

Out-of-the-box integration with IT ticketing/issue management systems

Non-repudiation and System Configuration Change and Event Logging

Enterprise licensing

Per user licensing

Per server/CPU licensing

Out-of-the-box integration with DevOps toolchain

Highly scalable without an unreasonable number of additional hardware requirements

Requirement Descripton

User Token licensing

Requirement Descripton

Certificate of Networthines (CoN)

TR 1.0.2.0 Solution shall be listed on the Unified Capabilities Approved Product List

(UCAPL).

TR 1.0.3.0 Solution shall be available from the Computer Hardware Enterprise Software and Solutions (CHESS).

TR 1.0.4.0 Solution shall be FedRamp Compliant at the required levels.

Functional Requirement

FR 1.11.0.0

Importing/Exporting Comments

TR 1.11.1.0 Solution shall be directly exportable to MS Office (version 2013) out of the box.

TR 1.11.2.0 Solution shall be directly exportable to TXT out of the box.

TR 1.11.3.0 Solution shall be directly exportable to CVS out of the box.

TR 1.11.4.0 Solution shall be directly exportable to PDF out of the box.

Functional Requirement

FR 1.12.0.0

Training/Maintainability/ Vendor Stability

Comments

TR 1.12.1.0 Solution shall include available vendor maintenance support.

TR 1.12.2.0 Solution shall include available training.

TR 1.12.4.0 Solution shall include available customer support.

TR 1.12.5.0 Solution shall include vendor on-line documentation / tutorials.

TR 1.12.6.0 Solution shall include available on-line Communities.

TR 1.12.9.0 Solution shallminimal installation effort and minimal on-going maintenance impacts.

Unified Capabilities Approved Product List (UCAPL)

Computer Hardware Enterprise Software and Solutions (CHESS)

FedRamp Compliance

Exportable to CSV

Exportable to PDF

Requirement Descripton

Requirement Descripton

Exportable to MS Office (version 2013)

Exportable to TXT

Vendor On-line Documentation / Tutorials

Vendor On-line User Communities

Minimal installation effort, minimal ongoing maintenance impact

Maintenance Support available

Training available

Customer Support available

ATTCH 1