FIS Data Navigator Modernization Guide

FIS Data Navigator collects transaction data from various source systems within the FIS Enterprise Payments platform. It then routes this data to appropriate processing systems for further action.

Data Navigator allows bank personnel to monitor transactions as they move through the FIS payment processing system. This provides visibility into transaction status and potential issues.

Data Navigator integrates with various source systems, including core banking platforms, payment gateways, and fraud detection systems. It also integrates with downstream processing systems for settlement and reconciliation.

The system uses message queues (MQ) and other messaging protocols to ensure reliable data delivery between components. Specific protocols may include IBM MQ, JMS, or proprietary FIS protocols.

While specific commands vary, common operations include transaction lookup by ID, filtering transactions by criteria (e.g., amount, date), and viewing transaction details. Configuration files define routing rules and data transformations.

Data Navigator likely exposes APIs for transaction inquiry and reporting. These APIs could be RESTful or SOAP-based. Specific endpoint patterns and method names would be defined in the API documentation.

The system architecture includes components such as the Data Collector, Routing Engine, and Monitoring Console. These components communicate via message queues and potentially direct database connections.

Data Navigator likely uses a relational database (e.g., Oracle, DB2) to store transaction data and configuration information. Specific database requirements would be outlined in the system documentation.

By providing real-time transaction visibility, Data Navigator enables faster issue resolution and improved customer service. It also supports compliance efforts by providing an audit trail of transaction activity.

Data Navigator helps reduce operational costs by automating transaction monitoring and reducing the need for manual reconciliation. It also improves efficiency by streamlining data routing and processing.

The system provides a centralized view of transaction data, enabling better decision-making and improved risk management. This allows banks to identify and address potential problems more quickly.

Data Navigator supports authentication methods such as LDAP, SAML 2.0, and X.509 certificates. Specific authentication requirements would be configured within the system.

The system uses a role-based access control (RBAC) model to manage user permissions. This allows administrators to assign specific roles to users, granting them access to certain functions and data.

Data Navigator uses encryption to protect sensitive data both in transit and at rest. Specific encryption algorithms and key management practices would be documented in the system's security documentation.

The system provides audit logging capabilities to track user activity and system events. These logs can be used to monitor security and compliance.

Data Navigator provides administrative interfaces such as a web console and potentially a command-line interface (CLI). These interfaces are used to configure the system, manage users, and monitor performance.

User management is handled through the administrative interface, allowing administrators to create, modify, and delete user accounts. User roles and permissions are also managed through this interface.

Key configuration parameters include routing rules, data transformation settings, and security configurations. These parameters are typically stored in configuration files or a database.

Data Navigator provides monitoring and logging capabilities to track system performance and identify potential issues. Logs can be viewed through the administrative interface or exported for analysis.