Workspace 04

Technology and Enterprise Architecture

Workspace objective

Assess the current technology and enterprise architecture

This workspace documents the applications, infrastructure, interfaces, automation, reporting, data environment and technology constraints supporting the current risk, lending and investment processes.

Technology and Enterprise Architecture

0%

0 of 16 answeredNot started
1

List core banking applications, lending platforms, workflow systems, document systems, spreadsheets, databases and supporting tools.

2

Describe the functions supported, primary users, products covered and where each application fits within the process.

3

Identify business owners, application owners, infrastructure teams, vendors and support arrangements.

4

Describe whether the environment is centralised, distributed, service-based, application-led, batch-oriented or dependent on manual file movement.

5

Include on-premise infrastructure, private cloud, public cloud, data centres, operating systems, databases and network dependencies.

6

Identify APIs, middleware, database links, file transfers, email, spreadsheets, manual uploads, batch interfaces and direct system connections.

7

Consider credit bureaus, identity providers, payment platforms, fraud services, regulatory platforms, data providers and partners.

8

Identify re-keying, copy-and-paste activities, spreadsheet uploads, email attachments, document transfers and reconciliation work.

9

Include workflow automation, rules engines, robotic process automation, scheduled jobs, alerts, decision engines and document processing.

10

Describe reporting tools, dashboards, spreadsheets, data extracts, report ownership, refresh frequency and manual preparation.

11

Identify source systems, operational databases, data warehouses, document repositories, shared drives and local spreadsheets.

12

Consider access controls, segregation of duties, audit trails, backups, monitoring, disaster recovery and change controls.

13

Include slow processing, system downtime, batch delays, storage limits, network constraints and peak-volume issues.

14

Consider legacy systems, limited integration, duplicate data, poor visibility, unsupported applications, manual workarounds and vendor dependencies.

15

Identify confirmed or proposed projects that may affect scope, architecture, integration or delivery sequencing.

16

Include logical diagrams, physical diagrams, data-flow diagrams, system catalogues, interface specifications and support documents.

Loading saved responses...

Dashboard
Why this information matters

AI and automation solutions must fit securely within FCMB’s existing enterprise environment. Understanding the current applications, infrastructure and interfaces reveals integration effort, architectural constraints, operational dependencies and technology risks.

Completion guidance
  • Document the environment as it operates today.
  • Include formally supported systems and unofficial tools used by staff.
  • Record manual interfaces and spreadsheet-based workarounds.
  • Identify external dependencies and vendor-managed services.
  • Reference available architecture, application and interface documents.
Information captured
  • Application landscape
  • Application purpose and ownership
  • Architecture and infrastructure
  • Internal and external interfaces
  • Manual data movement
  • Automation capabilities
  • Reporting environment
  • Data storage
  • Technology controls
  • Performance and capacity limitations
  • Technology challenges
  • Planned technology changes
  • Architecture documentation