The data collection component provides secure electronic delivery of reports (UTRs, STRs, CTRs and EFTRs from reporting entities using (SSL 512 bit encryption). It allows the FIU to create (register) reporting entities in the system and then provides functionality for reporting entities to create and/or change contact details, to upload reports and to perform data entry. Reports are either submitted offline (through XML data exchange such as e-mail attachment, CD, HD etc.), online (through direct upload of XML data messages) or through filling in and submitting online forms on the FIU's secure website (goAML Web). Report formats are defined within the collection component. If reports are submitted to the FIU on paper these can be manually entered by the FIU.
Additional data, other than mandated reports, requested by the FIU (bank statements, account opening details etc.) can also be submitted online or through offline media.
goAML Web: The goAML Web application provides a secure web based interface between the FIU and its reporting institutions for the electronic upload of reports and other information. The principal purpose of the goAML WEB is to provide an online platform for communication between the FIU and its reporting entities and for the submission of reports by those entities to the FIU by automated XML file upload, filling out the online report forms or sending XML files as attachments by secure e-mail. The communication function can be used to provide information to reporting entities either individually or on a collective basis; it can also provide links to other, related, websites, and a "contact us" link for general communication if required. The FIU can largely customize goAML web to its own corporate requirements.
The reporting interface provides the facility to report multi party transactions using the web based forms provided. The is a particularly important feature for reporting entities such as dealers in high value goods who tend to report single sided transactions even where there are a number of parties to the transaction.
The goAML Web also facilitates the Request for additional Information (Additional Information Report [AIR]). Upon receipt of an STR or other report an FIU will often want further information, particularly transaction histories, from the reporting institutions. This feature enables the automation of that process. Upon request the reporting institution can compile the information in XML format as it would with reports and transmit it electronically to the FIU. The requested data is uploaded to the goAML database and is immediately available to analysts.
This component automatically checks incoming electronic data for completeness and accuracy (compliance with XML schema). This process takes place in a staging area outside the main system environment (the DMZ). If incoming data is correct and complete it is transferred to the main database, if it is not it is returned to the reporting entity for correction. This process can also be completed manually within the FIU by allowing FIU personnel to view selected reports or all reports submitted by reporting entities and manually accepting or rejecting them. An XML rules editor allows the creation of rules to accept or reject individual transactions within a report after XML validation.
"Syntax" - normal validation/check against schema
"Symantix" defined by user - checks transactions for pre-defined conditions such as non alphabetical characters in names, age of transactor etc.
The rules editor allows for flexibility in checking transactions details as well as the more rigid check against the schema. This tool allows the extraction of faulty transactions from a report and sends just those transactions back to the reporting institution for correction or enquiry. The rest of the report is validated. All of this activity is recorded by goAML which gives the compliance staff of the FIU continuous and detailed information about who is reporting (and who isn't) what they are reporting, what is the standard of the reports etc. A variety of "compliance" reports relating directly to the reporting practices and standards of reporting entities as a whole, by business type, by geographical location, or as individuals etc. can be produced from this data. All data of this type can also be charted to add visual weight to reports produced.
Subject unification is a facility that is available following report and business rule validation. It allows non destructive subject promotion and demotion, meaning that database objects can be merged where it is found that multiple entries relate to the same object. Conversely, an object can be separated into multiple objects where it is found that the original object has been incorrectly entered as a unique identity. Merging of objects can be done automatically according to user defined rules. The original data always remains and all activities are logged.
Virtual object: Where there is doubt as to whether two or more database entries such as persons or entities relate to the same identity this feature allows analysts to create a database object (a virtual object) based on the assumption that two or more separate identities recorded in the system are the same but without merging those identities.
The Ad hoc queries and matching component allows users to enter requests for matches on a wide variety of criteria such as name, address, country, account number, identification document number or type, etc. There are a number of search options. Some are specific to the preferred search criteria and full details or parts thereof can be entered.
There is also a quick finder option which essentially allows the user to Google© the entire database. After the query is submitted the system returns a list of all entities matching the requested criteria and links them, where links exist.
Data Matching module: Features an importer that can input data from external sources on persons, accounts and entities in any format and match this data against the FIU's report database. The data matching process can be run on an ad hoc basis or as a scheduled task at regular intervals. When run as a scheduled task, the matching process can automatically create analytical case proposals.
This component allows statistical reports to be automatically generated or ad hoc statistics to be obtained from the system to prepare reports on all activities carried out within the goAML application. Many different types of reports can be produced. These include a variety of "compliance" type reports that track the numbers, types, values etc. of the various mandated reports collected by the FIU as well as identifying the reporting entities by type, name, address etc. In addition the FIU can analyse and report on its own activities for internal management purposes or for more general consumption. The reports produced by this component of goAML can contain either general or very specific statistics of the FIU's performance overall or in specific areas of activity. These reports are of considerable assistance in compiling the FIU's annual report, in reporting to Parliament, responsible Ministers or Heads of Departments or for identifying gaps or weaknesses in the FIU's performance that require addressing by adding extra resources, changes to work practices etc.
This component is very feature rich and covers the contents of all reports submitted to the FIU and any other data held within the FIU's database. If their roles and security clearances permit, analysts can access the entire data set for in-depth analysis at both the tactical and strategic levels. goAML provides a wide variety of analytical tools and views that allow analysts to look at data from numerous different angles.
All of these tools such as sorting, filtering, and pivoting are integrated into this component of goAML allowing analysts to reveal patterns, anomalies, key variables, relationships etc. using just the one application. Trends and patterns of financial transactions of persons and entities, occupational types, geographical regions etc. can be analysed.
Tactical analysis on specific targets can be carried out utilising the full content of the database as well as more general strategic analysis again utilising all data contained in the database. The strategic analysis function provides a wide range of options including analysis pivoting on top players, in terms of account or transaction activity, primary account holder, event timelines, signatories, account activity, transaction type, occupation etc.
Virtual object: This feature allows analysts to create a database object based on an assumption that two or more separate identities recorded in the system are the same. It also enables the grouping together of identities under one object to create social network structures such as family associations, gang associations etc.
Whenever new information that relates to a member of a virtual object or if a query is run against an identity included in a virtual object, all information relating to that virtual object will be retrieved.
This new feature allows analysts, either individually or collectively, to design profiles or queries to run against part, or the whole of the FIU's data holdings. Using this tool, an analyst can create, save and share their own queries of the data based on any database object and according to their individual requirements. It looks and feels like a filter builder in Excel and offers an almost limitless range of questions that can be put to the data set. These can range from the very simple and general to highly detailed enquiries aimed at extracting very specific information from data holdings. Profile matches can be run as a "one off" enquiry, saved for reuse as and when required or set to run against the data holdings on a scheduled basis.
This is a powerful new tool that provides analysts, particularly strategic analysts, with a highly flexible means by which they can run queries and scenarios against the FIU's data holdings.
The rule based analysis component of goAML is structured into three parts. The rules engine, the rules editor and the alert manager. The rules engine continuously scans the data in the goAML database looking for data that matches certain circumstances (rules) that have been deemed by the FIU as worthy of specific attention. The rules can consist of virtually any set of facts or circumstances such as a particular pattern of transactions by a particular account type, occupation type etc., a change in transaction frequency in a certain type of account or commencement of cash deposits by a certain occupational type etc. There is no limit to the number and type of rules that can be applied. The rules editor is a user interface that allows rules to be written and submitted to the rules engine by anyone in the FIU authorized to do so. Rules can be formulated by imposing conditions on standard intelligence objects such as persons, entities, accounts etc. in the much the same way as filters can be formulated in Excel and other analytical programmes. The user does not need to be able to write computer code, and the FIU can customize the submission and authorization process to suit its particular situation and work preferences. The alert manager is the process by which alerts triggered by the rules engine are managed and prioritized.
The workflow management system provides the ability for FIU management to set and maintain system driven sequenced steps in the process of information management based on the FIU's standard operating procedures. This includes the receipt and processing of reports and other information, the analysis process from beginning to end, the management of information dissemination and any feedback processes. This component effectively drives the work of the FIU as it relates to receipt and management of information and the development and dissemination of intelligence. The Workflow System is fully customizable so that the workflow process can be set precisely to the needs and processes of the user FIU. Whilst the Workflow System is programmed to follow a set step by step process it is flexible enough to be overridden when particular circumstances, such as the urgency of a particular matter, dictate that the normal workflow process should not be followed.
Multiple business process workflows: The workflow system allows for multiple workflows to reflect the different standard operating procedures applied to different aspects of an FIU's business. The system allows completely separate workflow processes to be applied to different tasks and activities. For example, a workflow can be applied to the initial analysis of reports; if a report is escalated to a case proposal a different workflow process then commences. If the matter is escalated further another workflow process commences and drives the task through to its conclusion. Each workflow is configurable to the individual requirements of the user FIU.
The workflow system can graphically illustrate the workflow process by producing a diagram depicting the workflow steps. The diagram is automatically amended as the workflow process itself is amended.
A range of reports that give management statistical information or a snapshot of current tasks proceeding through the workflow stages can be produced by the system.
This component is a management tool that allows managers and supervisors to allocate tasks with or without pre-set time limits and to then monitor and track the progress of that task or tasks as they progress through the workflow cycle. Whenever a new task is assigned or an existing task re-assigned or becomes due the person responsible for the task is advised in the goAML system itself and also notified by e-mail. The system also provides alerts to supervisors and managers when tasks are due or overdue or if tasks have been re-assigned, terminated or if the standard workflow has been overridden for any reason. This component also provides management with valuable statistical information that measures the performance of the workflow process itself and of the various FIU personnel working within it.
The document management component allows the capture of documents through electronic transfer and/or scanning and optical recognition. Documents can be recorded and filed according to a wide variety of document characteristics. When a new document enters the system it is not simply recorded as an image, the actual text in the document is lifted from it and filed in the database in the same way as any other entered data. The practical implication of this is that the entire content of the document is searchable and retrievable. The entire document can be retrieved at any time by clicking on links to it which appear in various lookup screens or by searching for key words or phrases known to be contained in the document. A general text search will retrieve all documents containing that text or text that looks or sounds substantially similar to the questioned text.
Case Proposals: This component is the first step in the escalation process applied in the course of the internal intelligence cycle of the FIU. Once an analyst has compiled all initial information, analyzed it and a decision has been made that a matter under enquiry, whether originating from mandated reports or other sources, is worthy of further and closer attention he/she can create a case proposal within the goAML system. Moving data into the file automatically creates links within the file to all other data related to the original data. For example, the analyst moves a name into the case proposal, all data within the goAML database related to that name such as addresses, accounts, known transactions, linked associates, etc. is automatically moved into the case proposal as well.
All further work on this matter is now handled within the case proposal and any new data added is automatically linked to the data already in the case proposal and any other associated data in the database. The practical implication of this is that the system itself adds most of the substance to the case proposal. Others within the FIU can access and contribute to the case proposal as it develops and its progress can be monitored throughout by supervisors or management. At any point the analyst can edit the case proposal to suit the particular matter under enquiry. This automated case building process can save many hours of analysts' time.
Case proposals can also be automatically generated from the automated data matching process.
The usual next step in the analytical process is escalation from a case proposal to a case file although the case proposal step can be omitted in favour of escalating the matter directly from analysis to a case file.
The entire case file, or selected parts of it, can be disseminated as an intelligence package to law enforcement or other authorities.
goAML provides a variety of options whereby the FIU can request and collect data from any external source. The range of options can vary from the very high tech to a letter delivered by post or by hand.
At one end of the spectrum goAML can be configured so that an analyst or other authorized person in the FIU can perform a completely online query of external databases to look for information associated with the persons, entities etc. that the FIU is interested in. This can be virtually any type of database hosted by any type of agency and can include criminal history records, vehicle registrations, company registrars, etc.
The system can be configured to cluster such enquiries so that when the details of the person or entity enquired about are entered all the databases to which the FIU has access can be queried simultaneously.
Because of the diversity and numbers of databases and agencies that could be involved in this type of online query facility this functionality has to be individually built for each installation. That build is not included in the routine goAML cost structure.
If this level of automation is not possible then requests for information can be transmitted in a less automated fashion. A standard request form can be configured in goAML and then populated by an analyst or other authorized person with data directly from the case or report the analyst is working on.
The request can be addressed from a pre-formatted list of agencies or organizations the FIU regularly queries or can be addressed manually in a "one-off" situation. Multiple requests can be simply produced using the same set of data but addressed to different agencies or organizations. These requests can then be sent as e-mail attachments, faxes or printed and posted or hand delivered. Whichever method is used, goAML provides the full functionality to produce and transmit the enquiry, there is no need for any other system. Again this saves much valuable analyst time.
The charting and diagramming tool is fully integrated into goAML and when activated by the analyst runs continuously and charts all analysis processes undertaken by the analyst. It is designed specifically for FIU use to chart transactional flows and to show the connections of the parties to the transactions (persons, entities, accounts etc.) to the transactions themselves and to other connected persons, addresses, phone numbers etc.
The analyst can manually switch between the charting tool and table data views or, if using two screens, can view both simultaneously. The staged drill-down function of the charting tool can actually drive the tactical analysis process by accessing data directly from the database and drawing flows, links and associations automatically.
Alternatively the analyst can use the tool to expand the chart and show flows and links one step at a time originating from accounts, persons, addresses, phone numbers or any other available object.
If the analyst simply wants to draw a chart without reference to the database this facility is also provided. The analyst can manually compile charts for individual cases by using the diagram options and icons available under this component.
Charts compiled in goAML are fully compatible with i2 Analyst Notebook© so if the FIU includes charts in its intelligence packages and the receiving agency is using i2 Analyst Notebook© the chart from the FIU can be loaded to i2 Analyst Notebook© in the receiving agency and the chart further developed in the course of that agency's enquiries or investigations.
The intelligence report writer tool is a fully integrated component that usually forms the final stage in the analytical process and provides a template and process for preparing the final intelligence package for dissemination to the FIU's end user agencies. The report can be customized to the FIU's specific requirements in terms of appearance and content and, like the intelligence file development component, can be populated entirely with data contained in the goAML system. The report itself is broken into a number of components, including an executive summary, intelligence hypothesis, main report body, conclusions etc. and the person(s) preparing it can, by simply checking or unchecking boxes, include or exclude any information already uploaded to it when it is created. Documents, charts etc. can be attached and the report itself and all associated data can be disseminated in XML format or the report body can be printed or communicated as an e-mail attachment whilst the associated data can be converted to Excel workbooks and disseminated in that format. The report writer tool allows any type of report format to be created in the application and stored in the database including connectivity to other data sources.