Manhattan Active® SCI (Supply Chain Intelligence) is a powerful reporting and analytics tool designed to support operational decision-making within the Manhattan Active® solution ecosystem. It allows users to generate ad-hoc reports, create interactive dashboards, and set up alerting mechanisms to monitor key performance indicators. With SCI, businesses can analyze large datasets and gain insights through human-readable reports, helping to streamline supply chain processes. However, its usage is optimized for analytical purposes. For real-time decision making, utilize the dashboards built into the Manhattan Active solution. For data integration and migration, utilize tools like Manhattan Integration Framework and Manhattan ProActive.
This is the multi-page printable view of this section. Click here to print.
Manhattan Active® Supply Chain Intelligence
Manhattan Active® Supply Chain Intelligence
1 - Manhattan Active SCI Status
Track and monitor the usage of SCI across Manhattan Active® products
Overview
The Manhattan Active SCI Status tracks and monitors the usage of SCI across Manhattan Active® products. It intends to continuously monitor and inform users to take proactive actions for interactive and scheduled reports, performance and configuration-related issues, and long-running reports that signal a potential risk of crashing and avoid downtime.
You can access it by navigating to Team Content > SCI Audit Reports > System Activity > Manhattan Active SCI Status.
Manhattan Active SCI Status contains the date filter which you can use to reflect data accordingly. The following table explains the sections it includes. Some sections comprise links to detailed reports that you can view for more insights and analysis.
Report Prompt
The following table explains the fields on the prompt page of this report:
| Prompt Field | Description |
|---|---|
| Select Date | The default value for this filter is ‘Last 24 Hr’, and you can also select a date from the last 15 days. |
| Report Type | You can select the report type that fetches values from ‘Report reportservice’, ‘ReportView reportservice’, or ‘Exploration queryservice’. |
| Type | You can run the report for Standard and Unsaved reports. |
Report Sections
The following table describes the sections in the Manhattan Active SCI Status report and their color coding parameters:
| Section Name | Description | Color Code for Visualization |
|---|---|---|
| Reports in 24Hrs | This visualization includes two metrics for Interactive and Scheduled reports to capture the number of reports users execute in the SCI instance. Detailed Report: You can access the drill-down or detailed report for interactive and scheduled reports by clicking the links on the numbers. This page provides the report name, timestamp, username, package, execution status, execution time in seconds, and issues. You can also filter the drill-down reports by report name and/or username. | Note: The Interactive and Scheduled report metrics do not have any threshold defined. |
| Failed Reports | This visualization indicates the percentage of reports that failed to generate for the date you select. Detailed Report: This section also contains a link to the drill-down or detailed report that includes the report name, timestamp, username, package, report type, execution time in seconds, issues, error details, and KB link. You can also filter the drill-down reports by report name and/or username. | Green : less than 2% ,Yellow : between 2 and 3% ,Red : greater than or equal to 3% |
| Long Running Reports | This section provides the number of reports that ran for more than two minutes for Interactive and 30 minutes for schedule. Depending upon the data availability, this report displays either a Green check or a bar visualization for a report type as shown in the image. Detailed Report: To access the drill-down or detailed report for interactive and scheduled reports, | Color Codes for Interactive Reports :Green : greater than or equal to 0 but less than or equal to 2,Yellow : greater than or equal to 2 but less than or equal to 5,Red : greater than 5,Maximum: 8.Color Codes for Scheduled Reports:Green : less than or equal to 30,Yellow : greater than or equal to 31 but less than or equal to 60,Red : greater than 60, Maximum: 90 |
| Max Runtime Minutes Per Hour | This section provides the highest execution time in minutes per hour for a day and the time interval when it is at its maximum. | Note: The report metrics do not have any threshold defined. |
| Ad hoc Reports | This section provides a count of all ad hoc or unsaved reports users execute. Detailed Report: You can access the drill-down or detailed report by clicking the links on the number. This page provides the report name, timestamp, username, package, execution status, report type, and execution time in seconds. You can also filter the drill-down reports by report name and/or username. | Green : less than or equal to 2,Yellow : greater than or equal to 2 but less than or equal to 5,Red : greater than 5 |
| Operational Documents | This section highlights the number of operational documents that users execute. Examples of these documents are packing lists, bills of lading, and others. | Red : greater than 0 |
| Multiple Users Same Report | This section provides the number of reports that multiple users execute in an hour of a day. Detailed Report: You can access the drill-down or detailed report by clicking the links on the number. This page provides the report name, timestamp, username, package, execution status, report type, and execution time in seconds. | Green : greater than or equal to 0 but less than or equal to 5,Yellow : greater than or equal to 5 but less than or equal to 10,Red : greater than 10 |
Report Types
The following table summarizes the standard IBM Cognos report types used in Operational SCI and their category in the Manhattan Active SCI Report:
| IBM Cognos Service Type | Report Type | Metric Category/Usage in Manhattan Active SCI Status Report |
|---|---|---|
| Exploration queryservice | Dashboards/Story | Not considered in the MA Active status report |
| Exploration queryservice | Unsaved Report | Adhoc |
| Report reportservice | Unsaved Report | Interactive / Adhoc |
| Report reportservice | Standard Report | Interactive |
| Report batchreportservice | Standard Report | Scheduled |
| ReportView batchreportservice | Standard Report | Scheduled |
| Report promptforward reportservice | Unsaved Report | Not considered in the MA Active status report |
| Report promptforward reportservice | Standard Report | Not considered in the MA Active status report |
Manhattan Active SCI Status
Drill-down report for reports in 24Hrs
Drill-down report for long-running reports
Drill-down report for failed reports
Drill-down report for multiple users same report
Drill-down report for ad hoc reports
1.1 - Troubleshooting Guidelines
Recommended guidelines for Manhattan Active Status Reports
Overview
This document outlines best practices for managing long-running reports, addressing report failures, and efficiently utilizing ad-hoc reporting in SCI. Adhering to these guidelines will help maintain optimal system performance.
Long-Running Reports
A long-running report takes more time than expected to execute.
General Guidelines to avoid long-running reports (interactive and scheduled)
- Understand user requirements: Focus on key metrics/KPIs to avoid unnecessary data, minimizing processing time.
- Limit data retrieval:
- Implement filtering options to restrict the volume of data processed and displayed.
- Enable users to select specific time periods and other necessary prompts before running the report.
- Use summary reports: Instead of detailed reports, create summary reports that provide high-level insights without processing more data.
- Break down complex reports: If a report is complex, consider splitting it into smaller, more manageable reports/sections based on the use case.
- Optimize data sources: After applying the other recommendations and if the report is still slow, connect with MA services to verify the indexes.
Scheduled Reports
- Schedule during off-peak hours: Whenever possible, schedule long-running reports during off-peak hours when system usage is lower. Also, pay attention to the frequency of scheduling.
Failed Reports
Follow the recommendations below to minimize the failures.
Review error messages: Verify the error message and resolve the issue if the failure is self-explanatory.
Attempt to re-run the report: If the failure was possibly a one-time issue, try executing the report again after a brief wait.
Verify data sources: Ensure all required data sources are accessible from the Cognos admin console.
Check report logic: Review any filters, calculations, and joins for potential issues that may cause failures.
Document the failure: Keep a record of the failure, including error codes and any relevant details of the resolution, for future reference.
Ad-Hoc Reports
Ad-hoc reports are generated on a need basis to meet specific business requirements quickly. They allow users to analyze data flexibly and dynamically.
- Leverage existing reports: Before creating a new ad-hoc report, check if an existing report can be adjusted to meet the business needs.
- Limit data scope: Focus on specific datasets relevant to the use case to improve performance and reduce execution time.
- Understand the purpose: Clearly define what is needed from the ad-hoc report to avoid unnecessary complexity.
- Avoid excessive runs: Be mindful of the number of ad-hoc report executions within a short timeframe, as it may affect overall system performance.
- Utilize report parameters: Use prompts effectively to customize reports without creating multiple versions of the same report.
Operational Documents
Operational documents are reports that offer insights into the performance, status, and tracking of various supply chain operations. SCI should not be used for creating or running operational document reports, such as Bills of Lading, Packing Slips, Worksheets, or Manifests.
Multiple Users Running the Same Report
Follow the below recommendations:
- Schedule reports: Encourage users to schedule reports to avoid simultaneous, on-demand generation.
- Use prompts and filters: Implement dynamic prompts and filters to tailor reports to individual user needs.
- Consolidate and standardize reports: Minimize redundancy and ensure that users are running the latest versions of reports.
- Leverage report bursting: Use bursting to generate personalized reports and distribute them automatically.
2 - SCI Limits and Guidelines
Rate Limits and Guidelines for Usage for Supply Chain Intelligence (SCI) with Manhattan Active® Solutions
The use of Manhattan Active® SCI (Operational SCI) is limited to the Manhattan Active® solution and its directly related systems. To help ensure optimal performance, default limits have been set as follows:
Default Limits
| Description | Limit |
|---|---|
| Runtime Limits | |
| Maximum runtime for batch/scheduled reports | 30 minutes |
| Maximum runtime for interactive reports | 5 minutes |
| Rows Retrieval | |
| Maximum number of retrieved rows per query | 100,000 |
| Content Retention | |
| Number of report output versions | 1 |
| Number of report history occurrences | 5 |
| Content Removal | |
| Retention period for report output | 7 days |
| Retention period for report history | 7 days |
Additionally, the following guidelines are recommended to maintain optimal performance:
1) SCI datasets should not be refreshed more than every 15 minutes.
2) No more than 25 reports should be run concurrently.
3) CSV table extracts should not be used.
4) Raw Data Movement Limitation: Extraction of large amounts of raw data, for example a CSV or Excel file to feed a data warehouse, is not supported in Manhattan Active® SCI. This immense movement of data affects the performance of conventional reporting use cases. Manhattan Active® SCI is intended only for analytics through the production of human-readable reports and dashboards.
5) Real-Time Mission-Critical Reports are not Supported: Reports are generated using a read-only replica of the production database. While the replication is typically near real-time, there may be occasional replication delays. Reports will always reflect what is currently in the read-replica, but because of occasional delays, may not reflect the current production data and therefore may not be appropriate for reports requiring real-time information. Real-time production reports are available within the Manhattan Active solution and utilize the real-time production database.
Some examples of mission-critical reports, forms, and labels are:
- Shipping labels and documents such as packing lists and bills of lading
- Trucks expecting an SCI report before transporting orders
- Floor-level employees waiting for SCI reports before beginning their operations
- Receiving worksheet to initiate the receiving process
- Printing of packing lists and dispatching of orders (shipments stopping due to the dependency on these reports)
- Assembly line operations halted due to the dependency on the SCI report
6) My Content Folder Limitation: Manhattan Active® SCI offers two folders, namely, Team Content and My Content, for developing reports and dashboards. The use of the My Content folder is generally not supported. After any Manhattan Active® SCI upgrade, the content and ownership of items saved in the My Content folder are not retained. It must not be used as a reliable location to save any reporting object. Items in the My Content Folder must be moved to the Team Content folder.
7) Access Control: Admin-level access to Manhattan Active® SCI is exclusively limited to Manhattan Services and Operations teams to manage Manhattan Active® SCI deployments. Customers are prohibited from accessing the system with admin privileges.
Capacity
Manhattan Active® SCI capacity is measured in runtime minutes per hour. The SCI capacity is based on the licensed subscription tier as follows:
| Size | User Tier | FUM Tier | Order Tier | Runtime Minutes/Hr |
|---|---|---|---|---|
| Tier 1 | 25 - 450 | 25M - 75M | 250K - 750K | Up to 150 |
| Tier 2 | 500 - 900 | 100M - 500M | 1M - 9M | Up to 300 |
| Tier 3 | 1000 - 1900 | 500M - 2B | 10M - 45M | Up to 500 |
| Tier 4 | 2000+ | 2B+ | 50M+ | Up to 1500 |
Runtime minutes per hour refers to the time spent running all reports within a single hour. For example, if 75 reports are run in an hour, and each report runs in two minutes, then the runtime minutes per hour would be 150.
Performance and Health Dashboard
To help identify and resolve performance issues, Manhattan Active® SCI includes a Performance and Health Dashboard. This dashboard includes the current runtime minutes per hour, listings of long running reports, total interactive and scheduled reports, and much more.