The Configuration Menu is used to configure the static data (contracts, markets, users, etc.).
From this screen, you can configure how LISA matches the trades with orders. An order can only be matched with a trade if they have the same values in the following fields:
These fields are called the matching criteria. You can refine the matching in LISA by adding additional criteria. You can also define to which markets and contracts the new matching criteria apply.
To manage one or several matching criteria, go on Configuration Menu Clearing Matching Criteria following window will be displayed:
This window is divided in two parts: a vertical Action Panel and a horizontal list of the matching criteria already defined. The user can perform six different actions from the Action Panel:
Add a matching criteria.
Edit a matching criteria.
Delete a matching criteria.
Export a file
Printthe matching criteria.
Refreshthe list.
To add a new Matching Criteria, follow these steps:
Click on the [ Add] button located in the Action Panel.
A new window appears - Add New Matching Criteria.
Field | Example | Comment |
Market/Contract Criteria : used to filter to which market and Contract this matching criteria will be applied | ||
Market | % | The LISA market name or wildcard (%) to which the matching logic will be applied. |
Contract | % | The LISA Contract name or wildcard (%) to which the matching logic will be applied. |
Strong Matching Criteria: These are basic value where fields that are checked must be equal on both order and trade | ||
Clear Info 1 Clear Info 2 Contract Version Environment Give in member Market trader Order number Order Type |
Checkbox = true | By enabling any of these radio buttons, this will be added to the criteria to which an order and trade must have the same value in the corresponding field. Therefore, for example, if Clear info1 is checked, both the order and the trade value must have the same value to match the order and trade. |
Matching Rules: This section allows you to setup custom rules based on just the trade or just the order values. | ||
Add | Add a new custom matching value. | |
Edit | Edit/Update the selected rule from the grid. | |
Delete | Delete the selected rule from the grid. | |
Import Settings From [Import] | Allows a user to import the matching rules from another market already setup in LISA. |
Select which exchange and instrument you want to add new matching criteria.
Note If you select the
wildcard &, then the matching criteria will apply on every market and/or every contract.
Select as many Strong Matching Criteria as required.
Note You can
also de-select all if you define your
own matching rules. An order and a trade will be matched together only if they have the same value for the
selected strong matching criteria. If you define no matching rules, the Matching Engine will base its matching
only on the Strong Matching Criteria selected. If there is more than one trade which fits the matching
criteria, then the Matching Engine will pick the trade having the closest volume to the order’s one.
Click Add to save the new Matching Criteria. It is now added, and it will be taken in consideration by the Matching Engine module.
Note There is a possibility to import the settings from existing matching criteria. To do so, select the existing matching criteria in the drop-down list located at the bottom of the window and then click on the [Import] button. Once imported, you can modify the matching criteria settings as required.
To add one or more matching rules, follow the steps below:
Add New Matching Rule
Field Name | Comment |
---|---|
Priority |
Defines the priority of how the matching rule will be applied between orders and trades. Note: The Priority box defines the level of priority for the matching rule being created. Lower the level higher the priority. The Priority of level 1 is the highest priority. |
Case is insensitive | Defines if the matching order and trade field should be case sensitive when applying the rule against these rules. |
Match Values with Wildcards |
To match both the contents of the trade and order field. If these fields are equal, the lines will be matched. If the content of either field contains the same values these lines will match. e.g. Trade Field = XXXX and Order Field = ZXXXXZ these lines will match. |
Match equal Values |
Adds the ability to match two values without taking into account the following special characters: colon (,) , slash(\), forward slash (/) and dash (-) Example: Order: ABC:DEF Trade: ABCDEF The new matching rule, saying match if same value without special char, will allow to match ABC:DEF with ABCDEF as without the special char those values are identical. |
Values Starts/Contains/Ends |
Defines if one of the fields is the prefix or contains or is trailing characters of the matching field. Starts Example: Starts With XXX Trade Field = XXXYYY and Order Field = XXXZZZ Contains Example: Contains XXX Trade Field =ZZXXXZZ and Order Field =YXXXY Ends Example: Ends With XXX Trade Field=ZZZXXX and Order Field =YYYYXXX |
Trade Fixed Value | Define the selected Trade Field which contains a specific value. Any Trade that has this value and matches on core matching criteria with an order will be matched. The use of wild cards use is possible. |
Order Fixed Value | Define the selected Order Field which contains a specific value. Any Trade that has this value and matches on core matching criteria with an order will be matched. The use of wild cards use is possible |
Apply Strong Matching Criteria | This forces the strong Matching criteria to be the matching criteria selected independent on other rules. It is recommended you set the priority to 1. |
List of Values |
You can select this rule if you want to match the order to a trade according to a list of possible values in given fields. To do so, you need first to select on which fields you want to enter a list of possible values. Note: If you want the real character and not the wildcard, enclose the character into brackets (for example: test[#] will search for the exact value test#) * or % : Any characters ? : Any single character # : Any single digit (0-9) ! : Reverse the result (i.e. NOT clause) |
Ignore Price On Matching (IPOM) | The MTE will ignore the price as a matching criteria. This is useful for the allocation of APS trades where the user sends a file in to allocate an APS group where they may not know the exact average price. |
Full Matching Only (FM) | The matching engine will match orders only if those and their corresponding trades can be fully matched. |
Trade Field | The trade field that the matching criteria will be run against. Note that you can also use the Trade ID for a matching rule |
Order Field | The order field that the matching criteria will be run against. |
The LISA Risk function aims to protect against automatic acceptance of irregular position primarily for Give-in but can also include in- house accounts.
This Risk window is divided in two parts: a vertical Action Panel and a horizontal list of the risks already defined. The user can perform eight different actions from the Action Panel:
Should you wish to protect against give-ins and/or house accounts being accepted beyond an agreed exposure you can do this with the following levels of control.
Control levels by:
“*”: Treat as individual (Please see below example)
If “*” is selected in the exchange, account or contract field the limit will be treated as an individual criteria. Hence, per exchange, per account or per contract respectively.
“%”: Treat as amalgamated (Please see below example)
If “%” is selected in the exchange, account or contract field, please treat as amalgamated criteria for that field, resulting in combined across all exchanges, all accounts and across all contracts.
Management criteria as a mixture:
Position Types:
Clearing Mode:
In order to determine what rule to apply if multiple are eligible, the system will allocate points depending on the rule settings.
Note The rule with the lowest score will take precedence.
The following logic is used to calculate the score:
Property | Score |
---|---|
Kill Switch (i.e. Block Account,GI/GU, Contract) | +512 |
real market (not star market) | +256 |
either a Clearing Only or ExecutionOnly rule | +128 |
actual account (not star/percent) | +64 |
account group | +32 |
actual contract (not star/percent) | +16 |
Call or Put contracts | +8 |
Futures or Options contract: +4 | +4 |
GiveIn member | +2 |
GiveUp member | +1 |
Final score = 1024 - score calculated above
Note All scores are between 1 and 1024
To add a new risk limit, carry out the following steps:
Field | Values | Comments |
---|---|---|
Rule Name | Text | Name of your rule |
Trades | Clearing Only (GI) Execution Only (GU) Execution + Clearing |
Defines the trade type that this risk parameter will be applied to. |
Accept Risk | Only if position is flat Only on these sides: Buy Only Sell Only Decrease Only |
Defines the type of risk calculation that will be applied through this risk parameter. Only if position is flat: If the position is flat (buy/sell), then this risk restriction can be acknowledged. Buy Only: The Risk admin can accept the risk position if the execution is a buy Sell only: The Risk admin can accept the risk position if the execution is a sell. Decrease Only: The Risk admin can accept the position risk if it is reducing the current calculated Risk. |
[Market / Contract] | ||
Market | Select a Market for which one will apply the new Risk. |
|
Contract | Futures Options Call Put |
Select a Contract you have several possibilities for the contract. Select a specific contract in the list and then the new Risk defined will appear only for this contract. Enter “%” in the contract text box. It means you want to apply the new Risk for all the Contracts. Enter “%” in the contract text box and select the “Future” radio button. Then the new Risk defined will appear only for all the Future contracts. Enter “%” in the contract text box and select the “Option” radio button. Then the new Risk defined will appear only for all the Option contracts. Enter “%” in the contract text box and select the “Call” radio button. Then the new Risk defined will appear only for all the Call Options contracts. Enter “%” in the contract text box and select the “Put” radio button. Then the new Risk defined will appear only forall the Put Options contracts. |
Aggregation on | Expiry Strike |
You can either aggregate the new Risk by the Expiry or by the Strike price: By Expiry: the limits will be applied only for the tickets having the same expiry. Example: There is a risk defined for the market M1, contract code C1 and account A1. Its gross position is set to 120. There is one Buy ticket for the market M1, contract code C1, account A1, expiry Sep09 and a Volume set to 50. There is one Sell ticket for the market M1, contract code C1, account A1, expiry Sep10 and a Volume set to 100. The risk alert should appear because the gross position for these two tickets is 150. But if you aggregate by Expiry, then no risk alert would appear because the expiry of the two tickets is different and then they would be processed separately. By Strike: the limits will be applied only for the tickets having the same Strike price. |
[Parties] | ||
Account | Select an Account on which you will apply the new Risk. Please note. the account name is based on the Lisa [Account Name] — [Member] — [Contract Type] —[Contract] as defined in the Account static. |
|
Account Group | Select an Account Group on which you will apply the new Risk. |
|
Give In Member | ||
[Position Values] | ||
Net Position | Net Position defines the limit of the volume Buy — Sell. |
|
Gross Position | Gross Position defines the limit of the volume Buy + Sell. |
|
Max Clip Size | Clip Size defines the maximum volume that a trader can buy or sell for a specific ticket. |
To delete a Risk, follow these steps:
To define the universal risk parameters, follow these steps:
Option | Comment |
---|---|
Clearing | |
Short Option protection | To raise a risk warning for all Sell options, enable this option. This protects against the risk of delivery of the contract. All other risk settings are ignored, and a warning is raised |
Refuse clearing if no limit defined | To raise a risk warning when there are no risk limits set for a particular order account. |
Exclude give in from ourselves | ExcludeGive-ins from risk checks if the give-in member and the member are the same. |
Limits | |
Move all limits | In the event of a large market movement, you have the option to move all the risk limits by a defined percentage. The number is the defined percentage increasing or decreasing of the defined limit. |
Members excluded from risk | |
Drop Down | You have the possibility to exclude one or several members from all defined risk limits suppressing any
risk warnings for this member. To add a new member to exclude: Select a member from the drop-down list and click on the [Add] button. The selected member will appear in the list under. To remove a member: Select it in the list and click on the [Remove] button. |
Accept Risk Password | |
Change Password | Enabling this will force a password change if you populate the old password field correctly. |
Old password | Enter the current password. The default risk password is xxxxxx. This must be changed to ensure your level of security. |
New Password | Enter a password that is appropriate for your risk management team to use. |
Rewrite the password | Re-enter the new password again. |
To export the Risk details in a Text File or in a CSV File, follow these steps:
Note You can export all the Risks by replacing the step 2 by: [ File Export]>[All Lines] .
To email the Risk details, the following actions have to be made in this specific order:
Note You can email all the Risks by replacing the step 3 by: [ Email]>[All Lines] .
To print the Risk details or to see a 'Print Preview' before starting to print; follow these steps:
Choose one of these options
Note To refresh the list of the Risk window, you just need to click on the button Refresh .
This feature allows for complete clearing suspension on select accounts.
This feature allows for suspension of all Give-In acceptance for selected brokers.
This feature allows for the suspension of all GiveUps to selected brokers.
Enhancement in LISA in order to manage regulatory subject or client contract scope. The current LISA risk setup doesn't allow to define rule with Group of contract / Account or Account Groups. Rules setup to block the clearing Account contract /Account group and Member.
Order/trades blocked following a regulatory rule will end up in a new clear status : Regulatory Warning
User with the permission Accept Regulatory will be able to accept the regulatory rule by doing the action Accept Regulatory and entering a pre-defined password (setup under Regulatory parameters).
Select Parameters to setup the Regulatory passwords.
Rule | Description |
---|---|
Rule Name | This name will be displayed on the Lisa FrontEnd whenever a clearing is blocked following a Regulatory rule |
Clearing Only (GI) | Limit rule to GiveIn only |
Execution Only (GU) | Limit rule to Giveup only |
Execution + Clearing | No limit to Rule being applied to all trades |
Contract | Limit rule to specific contract |
Contract Group | Limit rule to Specific contract group |
Contract Type | All Contracts: Futures: Limit rule to Future only Option Call/Put: Limit rule to Options only |
Give In Member |
Member: Limit rule to a specific member Member Group: Limit rule to a member group |
Account | Limit rule to a specific account |
Account Group | Limit rule to a specific account group |
This feature limits which accounts are available for allocation depending on the execution account (Market Account).
This is to limit user error on allocations.
This affects both TeoV3 and LISA. The desired end effect is:
TeoV3 trader would only see a subset of accounts on his account list when allocating a specific trade (or in the split screen etc). Any attempt at allocation to an account not in the list would be refused.
LISA user would only see a subset of accounts on his account list when allocating a specific trade (or in the split
screen, F2 etc). Any attempt at allocation to an account not in the list would be refused.This feature does not put limits on ACR rules, Allocation split, automatic matching or orders entered via file import (including TeoV3 since the limitation should have already been done in TeoV3).
This method is best used for adding a single limitation, however using the bulk import table might be a better and
faster.From the LISA Menu follow these steps
Field | Description |
---|---|
Trade Exec Account | The Market account that the broker executed onto the exchange. This is usually found the Market Account field of the trade.Wildcards (*) can be used. e.g. marketacc* |
Market | The market that is relevant for this limitation. Wildcards (*) can be used e.g. * |
Member | The member that is relevant for this limitation.Wildcards (*) can be used e.g. * |
Account | TheLisa Account that the Exec Account is limited too. Wildcards (*) can be used.e.g. POV_* |
Free Text 1 | Free text information |
Free text 2 | Free text information |
Free Text 3 | Free text information |
Free text 4 | Free text information |
Free Text 5 | Free text information |
Note This will not take effect unless the LISA user in question has the ALS enabled under there user login for each member and market under the Member Tab on the Login setup.
Note This functionality requires a feature license. Please contact your ATEO sales representative should you want to use this feature. The module LISAAllocationSplit is a required component with this feature. The goal of this module is to automatically split and allocate trades between different customers dependent on the setup done in the LISA Frontend.
The Allocation Split window will keep an update of allocation done, to take account of these values before a new split is done.
This window is divided in two parts: a vertical Action Panel and a horizontal list of the allocation split, already defined. The user can perform seven different actions from the Action Panel:
To add a new allocation split, follow these steps:
Field | Values | Comments |
---|---|---|
General Section | ||
Name | |
A unique name the split allocation. |
Description | Useful text to help other users understand the purpose of this split. | |
Market | The orders that the markets. | |
Member | ||
Trigger Frequency | Interval Fixed Hours |
Interval means that you have to enter an interval in seconds to define time between two run of allocation
split. Fixed hours means that you have to enter the time in the day you want the allocation split to be perform. Format is HH:mm (for several times, separate par a dash). |
Reset Frequency | Define when the module will reset data regarding the previous allocation split for the calculated of volume and price. | |
Disabled | Checked/unchecked | Check « Disabled » box if the allocation split is not used anymore. |
Percentage Split | Checked/unchecked | When checked, it enables allocation split based on percentage. |
Volume Split | Checked/unchecked | When checked, it enables allocation split based on volume. |
Algo Section: Note not all algos are visible but are based on Volume or Percentage split selection. | ||
Trades | Will take all trades and split them based on the percentage defined. | |
Trades Split Exact | Will only start to split the trades based on the percentage only if the remainder is less than 4 decimal places. | |
Orders | Will take all trades and split them based on the percentage defined. | |
Wellington | Checked |
When this option is activated, then a specific algorithm will be applied on Wellington Orders rather than the default split behavior. When all orders are matched, this algorithm will split all the allocations onto the different accounts that are on the allocations, so each account gets the closest average price as possible. All the orders will then be updated, rematches properly with the different trades to get the result that have been calculated. |
Wellington / Details | Will do the calculation based on the above specification, however, the resulting positions will be done on one account at a time, rather than on the volume. | |
Trades Split when a multiple of the total volume | Checked | Visible when setting a volume split. TheLAS is only triggered if the total volume of all available trades equals or is a multiple of the total volume of the split. |
Criteria Section | ||
Field |
Example: Field ExecBroker in Lisa, Value=Broker1 FieldMarket Trader in Lisa, Value Trader1 Those filters mean that only trades which have Exec_Broker=Broker1 andMarket Trader=Trader1 will be selected by the module for allocation split. The following wildcard characters can also be used: % or * means any characters (including zero character). ? means any single character. # means any single digit (0-9). ! means the NOT clause (e.g. !ABC means every values exceptABC). , means the OR clause (e.g. ABC,DEF means only values ABC orDEF). !() means the NOT clause applicable globally on several OR clauses(e.g. !(ABC,DEF) means every value except ABC and DEF). |
|
Allocation Section | ||
% (percentage) |
If the split is by percentage, Enter aPercentage* and a corresponding account. The following Algos can be applied: Trades Trades Split Exact Orders Wellington Wellington / Detail (the algo split will be done as per the account, but the result split per the different order generated.) |
|
Volume | If the split is by volume, Enter a volume* and a corresponding account. | |
Account | When user starts entering an account,a list of account available will be displayed. The total must be 100%. |
Note The fields followed by an * are mandatory to add a new Allocation Split.
In LISA, you can have Allocation Split Report to display all splits and average price calculated.
This window is divided in three parts: a vertical hierarchy on the list, a tool bar on the top and a main screen to display information.
Note The top part of the screen is a current view. The user will find the latest state of all splits applied on various trades.
The bottom part of the screen is an historical view, displaying a summary of for each time a split calculation had been applied.
To display historical data:
This is a licensed feature used to setup the running of EOD Exports. You need to add the registration code for activating it, the registration code is setup at Configuration > System > Registration Code. Once the right Registration Code is setup, proceed to Configuration → Security → User (or Profile), Clearing Tab and grant permissions as desired (View and/or Add/Edit/delete) on the “Back Office Exports” entry.
To access Back Office Export, go to Configuration -> Clearing -> Back Office Exports. This screen will display two tabs:
This tab allows you to declare the different Instance name available.
Note This entry needs to match the instance name defined in the ini file of the Export.
This tab allows you to setup the EOD export job.
Field | Values | Comments |
---|---|---|
Instance | String | Instance name of the R&N instance. |
Time Zone | Time zone | The desired time zone of the EOD job. |
Execution Time | Time |
Execution time for the EOD job in HH:MM:SS format(in the time zone defined above). Time entered in HH24:MI:SS format. |
Market List | String | Write a list of markets to export, the entries should be separated by a comma/semi-colon.(Must be filled) |
Default Account | Account to export uncleared trades to. (Must be filled) | |
Where Clause | SQL where clause applied to the export. | |
Last Run Date | Last date the EOD export job was run (not editable). |
Notes
To import orders that come from sources other than LISA, you need to set up a job that the Order Input Transfer module will run.
To access the Order Input Transfer configuration window, go to the menu [Configuration]>[Clearing]>[Order Input Transfer].
The Order Input Transfer window opens:
Follow these steps to add a new Order Input Transfer job:
Field | Values | Comments |
---|---|---|
[Parameters] | ||
Source | Text |
Defines the value that this job will look for in the ori_source (Source Field) field. |
Market | % | You can define a specific market that this job will process or just use the wild card %. |
Contracts | Text | Specifies the contract that this job will process. This can be for all contract if the wildcard is used, or a list separated by comma (,) |
Excluded Contracts | Text | Specify a list of contracts that this job should not process. Lists can be specified by a comma(,). |
Time Intervals | Int | A numeric value defined in seconds that the job will check if there are any new records to process. |
Active | Binary | Defines if this job should be activated and run at the interval period defined. |
Can update orders | Binary | Defines if the job will allow processed orders to be updated if new updates are sent to the input module. This is useful should you have a feed that can allow for deletion of orders being sent. |
[Options] | ||
Default Behavior | Binary | The module itself has settings that can be defined in the ini file. Should you wish to override these settings you can specify this job specific function below. By enabling this feature, you will use the default settings defined on the module. |
Allow deletion for LME | Binary | Should this job handle LME orders,this function will allow for the delete action to be permissible and delete any previously submitted orders. |
Allow Delete on Give Up Pending | Binary | Should this feature be enabled if an order is in a clearing status of Give-Up pending this job will allow for the deletion of the order in this state. |
Allow Delete on Non Give Up Cleared | Binary | Should this feature be enabled, if an order is in a cleared status that was not a Give-Up, the delete action will be permissible. |
Do Not Allow Duplicate Insert | Binary | This will check any new order processed is unique so as not to insert duplicate records. |
Do Not Allow Duplicate Insert CaseSensitive | Binary | Default value is unchecked. If checked, then force case sensitiveness on ord_ori_ref when checking for duplicate insert. |
Handle Full Update | Binary | This allows for an update record to update all order details. |
On_ref2 In Ord_on_ref | Binary | These fields define the uniqueness of the record that is being processed. Please speak to your TAM should you wish to use it. |
On_ref2 In Ord_on_ref With Sub_ref | Binary | These fields define the uniqueness of the record that is being processed. Please speak to your TAM should you wish to use it. |
Do not Fail delete when not found | Binary | Option to suppress Failed Orders being raised if the message is regarding a Delete for an order which no longer exists in LISA. |
Allow Delete On Cleared Give Up On Virtual Member | Binary | Option allows deletion of cleared giveup orders on virtual market |
The Order Input Transfer module (OIT) will use the information you have set up on this screen to perform the order imports into LISA.
To edit an Order Input Transfer, follow these steps:
To delete an Order Input Transfer, follow these steps :
The Trade Input Transfer works in the exact same way as the Order Input Transfer except that it applies to trades instead of orders. The Trade Input Transfer module (TIT) will use the information you have setup on this screen to perform the trade imports into LISA. Please review the parameter table below that is specific to Trades.
Please refer to Order Input Transfer for more information.
Field | Values | Comments |
---|---|---|
[Parameters] | ||
Source | Text |
Defines the value that this job will look for in the tri_source (Source Field) field. |
Market | % | You can define a specific market that this job will process or just use the wild card %. |
Contracts | Text | Specific the contract that this job will process specifically. This can be for all contract if the wildcard is used, or a list separated by comma (,). |
Excluded Contracts | Text | Specify a list of contracts that this job should not process. Lists can be specified by a comma(,). |
Time Intervals | Int | A numeric value defined in seconds that the job will check if there are any new records to process. |
Active | Binary | Defines if this job should be activated and run at the interval period defined. |
Can update Trades | Binary | Defines if the job will allow processed trades to be updated if new updates are sent to the input module. This is useful should you have a feed that can allow for deletion of trades being sent. |
[Options] | ||
Default Behavior | Binary | The module itself has settings that can be defined in the ini file. Should you wish to override these settings you can specify this job specific function below. By enabling this feature, you will use the default settings defined on the module. |
Do Not Allow Duplicate Insert | Binary | This will check any new order processed is unique so as not to insert duplicate records. |
Force Clear Member From Member Setup | Binary | |
Insert Unknown Contracts and Members | Binary | If the contract or member on the inbound feed does not exists, the member and contract will automatically be created. If not enabled, a warning will be raised requiring the member/contract to be created manually from the failed trade window. Please note permission will still need to be setup for the new member for users to view the new trades. |
Ignore Side on Delete | Binary | If checked, then any inbound trade with delete action will delete regardless of its side. So,the buy/sell indicator will not be considered when replacing the trade inLisa. |
PriceStrikeConversionEnabled | Binary | If checked, the 8/32/64 price/strike conversion and price/strike multi will be applied when processing a trade. |
Auto Clear Rules (ACR) are used to perform automated operations on trades as soon as they arrive in the LISA Front End. In particular, Auto Clear Rules can automatically:
To access the Auto Clear Rule configuration window:
Note You can filter the existing Auto Clear Rules by clicking on a market name on the horizontal tab bar. By clicking on a market name, the list will display only the Auto Clear Rules defined for this specific market. You can further filter by Member. When a Market filter is selected, the Member panel will update to show only the members of the selected Market.
Note The Member Tab will only appear if the option to show the members panel is selected in section Members. This can be configured under the menu [User]>[Appearance]>[Filters] and select the member tab.
To see the different actions a user can perform with the Action Panel (Delete, Export, Email, etc.), refer to General Screen Layout.
Note There is a virtual column (Calculated Score) that shows the calculated priority value for that rule. This value is used to determine the order the rules to be applied where multiple rules are applicable, i.e. the higher the score, the higher the priority it has. Below is an overview of how the score is computed.
There are two priority scores computed for every ACR:
Score 1 specificity criteria
Criteria | Score |
Global rules | -300 000 |
Ignore ACR / Do nothing | +200 000 |
Do not process trade | +100 000 |
Market is not star/percent | +20 000 |
Account is directly specified instead of using account pattern | +10 000 |
Contract is not start/percent |
|
Contract is star/percent |
|
Executing Member is not star/percent | +500 |
GiveIn Member is not star/percent | +400 |
For every other trade filter fields |
|
Follow these steps to add a new Auto Clear Rule:
Note Please review the Patterns, Wildcards and Lists of Values for details on the wild card parameters. You can use a comma separator (,) to add multiple conditional values to a number of text fields. To match a wildcard character, enclose it in brackets: e.g. [%] or [!]
Field | Req. | Comment |
---|---|---|
[Auto Clear Rule] | ||
Name | Y | Name of Auto Clear Rule. |
Description | Allows any user defined description of the ACR being set. | |
Disabled | Check the box Disabled if you don’t want to activate the new Auto Clear Rule. | |
Regular | This is the default setup which only applies to the specified ACR created | |
Global | When selected, it flags the ACR as Global which in turn allows definition of Advanced Rules to be applied across all ACRS identified by the set trade filters. | |
User Retry Only | When selected, the ACR will not be triggered by the Gateways nor the Trade Input Transfer. It will only be triggered through Lisa FrontEnd using the “Retry ACR” action. | |
Delayed | This allows the delay of the ACR processing by a number of configurable minutes as set in the Min text box, to allow a trade to match with an order first. | |
Min | This a text box allows a maximum input of three digits to set the period/time (in minutes) of delay once the Delay checkbox is ticked. | |
[Filter Options] | ||
Case is insensitive | If enabled, all the trade field filter criteria will not be case sensitive. This means the filter parameter can be entered in uppercase, however, despite the trade value being in lower case, the ACR will be applied. | |
Apply to Current and Future Clearing Dates Only | The ACR will not trigger is the clearing date of the trade is previous to current system date. | |
[Trade Filter] | ||
Market | Y | Select a market from the dropdown list for which the Auto Clear Rule will be applied. |
Exec & Give-in | Auto Clear Rules will be applied to both regular and Give-In trades. | |
Only Exec | Auto Clear Rules will only be applied to regular trades. | |
Only GiveIn | Auto Clear Rules will only be applied to Give-In trades. | |
Only GiveUp | Auto Clear Rules will only be applied to Give-Up trades. Used to create an Order based on the trade for a giveup down outside Lisa environment. | |
Ex/Ass/Pos | Auto Clear Rules will only be applied to Exercise, Assignment or Position trades. | |
Executing member | Y | The Auto Clear Rule will be executed only if the trades have been executed by this member. |
GiveIn Member | A Give-In Member must only be selected if the Only Give-In option has been selected. The Auto Clear Rule
will be executed only if the trades have been given up by this member. |
|
Contract Type | Enter a value and the Auto Clear Rule will only apply to the trades which have the same values in their corresponding fields or add a pattern to match multiple values at the same time. The pattern syntax is the same as the one used in the LISA filters (cf. Section 3.4.2.6 Patterns, Wildcards and Lists of Values p 28 ) | |
Contract |
|
|
Expiry | default value = % = no filter on the expiry. Expected format is yyyymm, yyyymm00 or yyyymmdd |
|
Trader | Enter Value or Wildcards. | |
Exchange Trader key | Enter Value or Wildcards. | |
Exec Broker | Enter Value or Wildcards. | |
Environment | Enter Value or Wildcards. | |
Exec Fee | Enter Value or Wildcards. | |
Give Up Member | Select the appropriate Give up member from the drop-down list. The field also supports use of wild cards. The ACR will be triggered only on trades with the selected Giveup Member. | |
Clear Info 1 | Enter Value or Wildcards. | |
Clear Info 2 | Enter Value or Wildcards. | |
Clear Info 3 | Enter Value or Wildcards. | |
Clear Info 4 | Enter Value or Wildcards. | |
Clear Info 5 | Enter Value or Wildcards. | |
Clear Info 6 | Enter Value or Wildcards. | |
Clear Info 7 | Enter Value or Wildcards. | |
Clear Info 8 | Enter Value or Wildcards. | |
Clear info 9 | Enter Value or Wildcards. | |
Account Type (CTI) | Enter Value or Wildcards. | |
Open / Close | The wildcard ‘%’ for the Auto Clear Rule to apply to all trades regardless the Open/Close
status. The values “O” for “Opened” or “C” for “Closed”. The Auto Clear Rule will only be executed if the trades have the Open/Close status as the one selected. |
|
Market Status | Enter the Market status or a wildcard. When the Market status is specified then the rule will be applied to the trades matching the status. | |
Market Sub Status | Enter the Market sub status or wildcard. When the Market sub status is specified then the rule will be applied to the trades matching the sub status. | |
Venue | Enter Value or Wildcards. | |
Order Environment | Enter Value or Wildcards. | |
Type | Enter Value or Wildcards. | |
Sub Type | Enter Value or Wildcards. | |
Type 2 | Enter Value or Wildcards. | |
Order Type | Enter Value or Wildcards. | |
Free 1 | Enter Value or Wildcards. | |
Free 2 | Enter Value or Wildcards. | |
Free 3 | Enter Value or Wildcards. | |
Free 4 | Enter Value or Wildcards. | |
Free 5 | Enter Value or Wildcards. | |
Free 6 | Enter Value or Wildcards. | |
Free 7 | Enter Value or Wildcards. | |
Free 8 | Enter Value or Wildcards. | |
Free 9 | Enter Value or Wildcards. | |
Market Text 1 | Enter Value or Wildcards. | |
Market Text 2 | Enter Value or Wildcards. | |
Market Text 3 | Enter Value or Wildcards. | |
Market Text 4 | Enter Value or Wildcards. | |
Market Text 5 | Enter Value or Wildcards. | |
Market Text 6 | Enter Value or Wildcards. | |
Market Text 7 | Enter Value or Wildcards. | |
Market Text 8 | Enter Value or Wildcards. | |
Market Text 9 | Enter Value or Wildcards. | |
Exercise Style | Enter Value or Wildcards. | |
Settl Method | Enter Value or Wildcards. | |
Contract Frequency | Enter Value or Wildcards. | |
Contract Id | Enter Value or Wildcards. | |
Contract Mnemonic | Enter Value or Wildcards. | |
Contract Date | Enter Value or Wildcards. | |
Flex Contract | Enter Value or Wildcards. | |
[Actions] | ||
Generate Order and send instruction to market | if LISA receives a trade with all the parameters defined in the new Auto Clear Rule, an order will be automatically generated for this trade and the clearing request will be sent to the market. | |
Generate Order and wait before sending instruction to market | if LISA receives a trade with all the parameters defined in the new Auto Clear Rule, an order will be automatically generated for this trade but no clearing request will be sent to the market. Instead, the trade’s clearing status will be set to “Wait”. | |
Generate Order and Auto validate | If LISA receives a trade with all the parameters defined in the new Auto Clear Rule, an order will be automatically generated for this trade and marked as cleared without sending a clearing request to the market. | |
Mark trade as matched and cleared | if LISA receives a trade with all the parameters defined in the new Auto Clear Rule, the trade will be automatically marked as matched and cleared without creating an order. | |
Mark trade as cleared: | if LISA receives a trade with all the parameters defined in the new Auto Clear Rule, the trade will be automatically marked as cleared without creating an order | |
Mark as GiveUp | This will move the trade to the clearing house Give-up system. Note: This is only for the CME Group and ICE trades. |
|
Mark as APS | This will move the trade to the average pricing system on the relevant market. The Group ID will be created based on the Mark As APS Options settings where selecting the Default Behavior will create the ID normally or using the Order Number or Market Trader value selection. Note: This is applicable to CME, ICE, Eurex (User Retry Only), OM, ME, MEFF Note: It's possible to retry Mark as APS auto clear rules for all protocols except OCC. |
|
Mark as APS NVAP | When ticked, the Clear info9 is populated with "NVAP" so the exchange gateway knows this is an NVAP
group/allocation. The Group ID will be created based on the Mark As APS Options settings where selecting the Default Behavior will create the ID normally or using the Order Number or Market Trader value selection. Note: Only applicable to CME. |
|
Reject GiveIn | This feature allows you to reject a givein trade that was executed on a clearing house that supports this option. This feature is only available for trades with mode=Exec & Givein or Only GiveIn. | |
Ignore ACR / Do nothing | When checked, the trade will be processed normally as if no rules were triggered. An ACR with this option does not require an account to be configured and Override Clearing Information. |
|
Do Not Process Trade | This will filter out the trade so that it doesn’t appear in the Lisa system. | |
Post Clearing | If Trade which are visible (Internal Status < none & Clear Status in Uncleared, Given Taken,
Cleared, Give-up Pending only) Check for a Post Clearing ACR matching the radio selection in the following order : Only Exec = no in/out member Only GU = Trade without member Only GI = Trade within member Exec + GI + GU : no filter If rule is found LISA will create the order with a new Source ACRPC, copy the Clear Status from the trade. If trade is Uncleared or Given Taken, then mark the order and trade as Cleared. |
|
[Account] | ||
Account | Select an Account. If the Auto Clear Rule matches on all criteria set up in the filter, the trade is auto-cleared and the account value is allocated to the trade. | |
Use Pattern | ||
[Override Clearing Information] | ||
Override | ||
[Advanced Rules] Time Period (Allows for the ability to override the time in which the ACR is active or inactive) |
||
Time Zone | Select the Appropriate time zone in which the active or inactive period apply. When empty, the time zone to be applied to will be the system time zone | |
Active Period | A list of time period separated by a semi colon when the ACR is active. When left blank then the ACR
will be active at all times. Format is hh:mm-hh:mm;hh:mm-hh:mm;... (.e.g : 08:00-18:00) |
|
Inactive Period | A list of time period separated by a semi colon when the ACR is inactive. When left blank then the ACR
will have no inactive period. Format is hh:mm-hh:mm;hh:mm-hh:mm;... (.e.g : 08:00-18:00) NOTE: This is the superior condition. The system first checks the inactive period and applies it before considering the active period. Example, If Active=08:00-18:00 and Inactive=16:00-16:10 then no ACR will be applied between 16:00-16:10 |
The values of the fields Clear Info 1 to Clear Info 9 depend on the market selected. Find below a small chart describing the field values on some common markets.
Corresponding Value | ||||
---|---|---|---|---|
Market | Account Type | Clear Info 1 | Clear Info 2 | Clear Info 3 |
Eurex | Account Type | Executing Account | Text | MiOrdNo |
ME | Account Type | Executing Account | Sub Account | Hedge Spec Code |
CME/COT | Account Type | Executing Account | Origin Code | Clear Info 3 |
Other | Account Type | Executing Account | Clear Info 2 | Clear Info 3 |
The Run Now option basically allows you to run an ACR on all applicable unmatched trades in the following scenarios:
A pop-up window will appear with the below options.
CTI Auto Management is used to automate the handling of CME group trades of the CTI Account Type as soon as they reach the LISA Front End. It works very similarly to the AutoClearRule.
Alternative to manually inserting one CTI at a time is to use the Bulk Import option.
To create a new CTI Auto Management Rule, follow these steps:
Field Name | Comment | |
---|---|---|
[CTI Rule Name] | ||
Name Pattern | A unique name for the clearing pattern. | |
Description | A simple description. | |
Disabled | The clearing pattern is not used when this is checked. | |
[Account Filter] | ||
Market | The Market of the account. | |
Member | The Member associated with this account. | |
CTI Rule Type | A CTI Rule can be one of two types:
|
|
Account | The LISA Account to be associated with this new CTI Rule. | |
[Trade Filters] | ||
Options |
|
|
Exchange Trade Key | Defines the exchange login used to execute the trade. This may be a wildcard (%) or a
market
specific trader login. This value is normally in the Lisa field Trader. |
|
Exec Broker | The execution broker reference that this CTI should be assigned to. | |
Executing Account | The market account that the position was executed. | |
Order Type | The market appropriate order type for that the execution. If this value matches the CTI will be applied to the order. | |
[CTI Result] | ||
CTI | Defines the CTI value to apply should the above trade filters match the trade. |
Clicking the Bulk Import will open a grid window from which static can be imported. There are a few button options at the bottom right of the window.
Create: Only add new records to static data that don't exist. If import line matches existing static data record it will be failed.
Update: Update existing static data record with import line. If import line doesn't match an existing static data record it will be failed.
Merge: Update existing static data record with import line, where a match is found, else add a new static data record.
An update only happens if something has changed. In mode Update & Merge, if no change is detected, the results to "No change detected. Action skipped" is consider as the record being a success.
To edit a CTI Auto Management Rule, follow these steps:
To delete a CTI Auto Management Rule, follow these steps:
Used as a form of a translation from the Reference value that can be entered via the Order Input transfer or manually that is translated into the market defined User ID.
Clearing settings allows the user to setup specific clearing actions.
This window offers the following settings:
Allow Give-Up from non-Give-Up Account: This option is checked by default. It allows users to be able to add a Give-Up member on a non-Give-Up account on trade/order split screens(Alt+A/Alt+Z screens).
This window offers the following settings:
This window offers the following settings:
Force users to enter Volatility value when entering TRADED OPTIONS & TAPO trades: When this setting is enabled, users will not be allowed to submit Traded Options or TAPO's with an empty Volatility column value on LME only.
Enable Auto GIVE-UP EXECUTOR UNA Submissions: the GUE UNA workflow for accounts having the flag GUE
UNA enabled.
Order Input : Ignore UserTrader from Account: This option is unchecked by default. If checked, in the LME Input Order : when the user selects an account, do not put the value of Account.UserTrader into ExecutionDecisionUser.
This window offers the following settings:
Validate Pit Entry: When checked, CME Pit trade entries will undergo validation check before being submitted:
Basic Fields validations include:Account Field must be valid.
Ordernumber - force user to enter a value.
Origin - 1 or 2
CTI - 1-4
CTR field must be populated.
CTR Specific Behavior
When leaving the Ordernumber field - if the Account/Firm/Trader entered match an existing Pit Account/ Member/UserTrader then the CTR field is populated with the Ordernumber field value prefixed with an "X"
else CTR code will be entered manually.
To change the password of a LISA user, you must perform these steps:
Note Your new LISA password is setup only if the last two passwords entered are the same. You will have to use this new password from now on to log in to LISA.
You can configure the rights of a LISA user and/or the rights of a system user connected to LISA Clearing Engine by going to the sub-menu User
You can create a new login policy associated with a LISA user. It will define the rules applied to the login (expiry, maximum failed login attempts, etc.).
You can create a profile to define user access rights. If the profile has access to only some specific market or it has only few rights on LISA; the user with this profile will have only the rights defined for the profile. A user with several profiles will have access to the highest rights defined in the different profiles.
Field | Description |
Type | Only one type supported: Request Server |
Login | Lisa User login for this module to subscript to Lisa server events |
Name | Proxy name that is user friendly |
Description | Description free |
URL | The URL above must match one of the prefixes setup on the LisaProxyServer.ini under [Module
Settings]>Prefixes For Https, URL must match the certificate DNSName you are using. |
You can also add a user to a Trader group. Users can only see the trades his Trader group is configured to see.
Static Data Sub-menu
This menu allows a LISA's user to configure all LISA's static data such as:
The static data are generally dependent on one another:
You start by creating the markets that you want to handle in LISA.Then you have to add the contracts, members and account types to these markets.
Then you need to setup the LISA accounts and Auto Clear Rules. You can also include accounts in Account Groups
The Source Menu lets you define from where the orders/trades originate.
The Transco Menu lets you add Transcos to apply specific conversions on the data received in LISA.
The Alert Menu lets you create your own alerts, displayed at the bottom of the LISA main window.
In order to access the Account configuration window, go to [Configuration Menu] > [Static Data] > [Account].
The Account window opens:
This window is divided into three parts:
You can filter the existing accounts by clicking on a market name on the horizontal tab bar. By clicking on a market name, the list will display only the accounts defined for this specific market.
To see the different actions users can perform with the Action Panel (Delete, Export, Email, etc.), refer to General Screen Layout
Follow these steps to add a new Account:
Field Name | Comment | |
[Account] | ||
Name | A unique name for the account | |
Description | A summary of the account | |
Disabled | The account is not used when this is checked. | |
Account Setup | ||
Market | The Market of the account. | |
Member | The member associated with this account. | |
Contract Type | The Type of contract assigned to this account. | |
Contract | The contract assigned to this account. | |
[Clearing Information] | ||
Account Type | The type of account. Check the Open box if the account is to be an open account. |
|
Give Up Member | The account can be a Give-Up account. This means that as soon as an order is created with this
account, the trade will be given up to a member already defined. Check theGive Up Member box and select the Member Code in the dropdown list. |
|
Clear Info 1 - 9 | Depending on the market these fields have different meaning. | |
Group / Split | ||
Group List | If you want to assign the new account to an Account Group, select the account groups in the drop-down list. | |
Options | ||
Wait/Match | If you check the box Wait/Match, when a trade is allocated to this new account, an order will be created but not matched to the trade.The order status will be set to Wait. | |
Wait/Clear | If you check the box Wait/Clear, when a trade is allocated to this new account, an order will be
created and matched to the trade, but no clearing request will be sent to the market. The order status will be
set to Wait. You can define the wait timer before the order is released for processing by choosing from the options on the Wait/Clear timer. |
|
WAIT/Clear Timer | For this option to work,Wait/Clear needs to be checked. None: Do as normal match order and send clearing Default: wait based on the Matching engine configuration period. 5Min: Wait 5 minutes before moving to cleared. 15Min: Wait 15 minutes after matching before moving to cleared. Time: Allows you to set a specific time you want the orders released after allocation. |
|
Auto Clear | If you check the box Auto Clear, when a trade is allocated to this new account, an order will be created, matched to the trade and both the trade and the order will be cleared without having a clearing request sent to the market. | |
Internal AVG | If checked, the trades cleared on this new account will be copied by theLisa Internal Average
Price (LIAP) module into a virtual market called APSMKT(by default). On the OM markets, the market account is copied onto the clear info1 from the APSMKT trade Note:this market name is configurable. |
|
GUE UNA | ||
Pit | If checked, this account added to the drop-down list on the Submit CME Trade window. | |
User Trader | ||
User Trader | Enter a trader name in the User Trader Field, or leave it blank,or select from a dropdown list of the available User Traders if selection is enforced Under [Configuration]>[Clearing]>[Settings]> Account Tab | |
Free Text Information | ||
Free Text 1 - 9 | These are open fields that may be used to specify any internal data that is needed. | |
Fee Information | ||
Exec Fee Ref | An internal business reference relating to the fee for execution charged to client. | |
Clear Fee Ref | An internal business reference relating to the fee for clearing to be charged to the client. | |
Other Fee 1 | A free reference field relating to any changes associated with this account. | |
Other Fee 2 | A free reference field relating to any changes associated with this account. | |
Other Fee 3 | A free reference field relating to any changes associated with this account. | |
Back Office Information | ||
Back Office 1 | A field for passing information to back-office system. | |
Back Office 2 | A field for passing information to back-office system. | |
Back Office 3 | A field for passing information to back-office system. | |
Back Office 4 | A field for passing information to back-office system. | |
Back Office 5 | A field for passing information to back-office system. | |
Back Office 6 | A field for passing information to back-office system. | |
Back Office 7 | A field for passing information to back-office system. | |
Back Office 8 | A field for passing information to back-office system. | |
Back Office 9 | A field for passing information to back-office system. |
This feature is to allow a client to setup just one account within LISA and to declare somewhere else the clearing detail for each market (Example: on EUREX use A1, on ICE use N...).
Field Name | Comment | ||
[Clearing Pattern] | |||
Clearing Pattern | A unique name for the clearing pattern. | ||
Disabled | The clearing pattern is not used when this is checked. | ||
Account Setup | |||
Market | The Market of the account. | ||
Member | The member associated with this account. | ||
Contract Type | The Type of contract assigned to this account. | ||
Contract | The contract assigned to this account. | ||
[Clearing Information] | |||
Account Type | The type of account. Check the Open box if the account is to be an open account. |
||
Give Up Member | The account can be a Give-Up account. This means that as soon as an order is created with this
account, the trade will be given up to a member already defined. Check the Give Up Member box and select the Member Code in the dropdown list. |
||
Clear Info 1 - 9 | Depending on the market these fields have different meaning. | ||
Group / Split | |||
Group List | If you want to assign the new account to an Account Group, select the account groups in the drop-down list. | ||
Options | |||
Wait/Match | If you check the box Wait/Match, when a trade is allocated to this new account, an order will be created but not matched to the trade. The order status will be set to Wait. | ||
Wait/Clear | If you check the box Wait/Clear, when a trade is allocated to this new account, an order will be created and matched to the trade, but no clearing request will be sent to the market. The order status will be set to Wait. | ||
Auto Clear | If you check the box Auto Clear, when a trade is allocated to this new account, an order will be created, matched to the trade and both the trade and the order will be cleared without having a clearing request sent to the market. | ||
Internal AVG | If checked, the trades cleared on this new account will be copied by the Lisa Internal Average
Price (LIAP) module into a virtual market called APSMKT (by default). On the OM markets, the market account is copied onto the clear info1 from the APSMKT trade Note:this market name is configurable. |
||
GUE UNA | |||
Pit | If checked, this account added to the drop-down list on the Submit CME Trade window. | ||
User Trader | |||
User Trader | Enter a trader name in the User Trader Text box. | ||
Free Text Information | |||
Free Text 1 - 5 | These are open fields that may be used to specify any internal data that is needed. | ||
Fee Information | |||
Exec Fee Ref | An internal business reference relating to the fee for execution charged to client. | ||
Clear Fee Ref | An internal business reference relating to the fee for clearing to be charged to the client. | ||
Other Fee 1 | A free reference field relating to any changes associated with this account. | ||
Other Fee 2 | A free reference field relating to any changes associated with this account. | ||
Other Fee 3 | A free reference field relating to any changes associated with this account. | ||
Back Office Information | |||
Back Office 1 | A field for passing information to back-office system. | ||
Back Office 2 | A field for passing information to back-office system. | ||
Back Office 3 | A field for passing information to back-office system. | ||
Back Office 4 | A field for passing information to back-office system. | ||
Back Office 5 | A field for passing information to back-office system. | ||
Back Office 6 | A field for passing information to back-office system. | ||
Back Office 7 | A field for passing information to back-office system. | ||
Back Office 8 | A field for passing information to back-office system. | ||
Back Office 9 | A field for passing information to back-office system. |
Clicking the Bulk Import will open a grid window from which static can be imported. There are a few button options at the bottom right of the window.
Create : Only add new records to static data that don't exist. If import line matches existing static data record it will be failed.
Update : Update existing static data record with import line. If import line doesn't match an existing static data record it will be failed.
Merge :Update existing static data record with import line, where a match is found, else add a new static data record.
An update only happens if something has changed. In mode Update & Merge, if no change is detected, the results to "No change detected. Action skipped" is consider as the record being a success.
An Account Group is useful to gather several existing accounts. It can be used, for example, to filter out on the Account Recap window.
In order to access the Account Group configuration window, go to [Configuration] Menu > [Static Data] > [Account Group].
The Account Group window opens.
This window is divided into two parts:
To see the different actions users can perform with the Action Panel (Delete, Export, Email, etc.), refer to General Screen Layout
Follow these steps to add a new Account Group:
Note The fields followed by an * are mandatory.
This window allows for general market account type on the various clearing houses. There is also the ability to define the Clearing patten type base on a wildcard known as Market *. For the Clearing pattern to become available there must be a market that has been defined in the Market static as *.
Adding an account type requires the follows
Field | Description |
[Account Type] | |
Market | The market to which the account type will apply. |
Type | Type code that is accepted by the clearing house. For CME Accounts, AUTOT account type will copy the account type value from the trade to the order if no CTI Auto Management rules are setup. |
House |
If this is to be defined as a house account. |
Description | Free field to explain the purpose of the record. |
[Clearing Pattern] for this to be enabled the market * must exist in Lisa | |
Clearing Pattern | A unique name for the reference of the type in theClearing pattern definition window. |
Description | Free field to explain the purpose of the record. |
Clicking the Bulk Import will open a grid window from which static can be imported. There are a few button options at the bottom right of the window.
An update only happens if something has changed. In mode Update & Merge, if no change is detected, the results to "No
change detected. Action skipped" is consider as the record being a success.This window contains a list of User Traders to be selected from a drop-down list when creating or editing an Account. To make the list available for selection from a drop-down menu, one must go to [Configuration] > [Clearing] > [Settings]: Account tab and check the setting Enforce User Trader to be selected from a list.
In order to access the Account User Trader configuration window, follow these steps:
To see the different actions user can perform with the Action Panel (Delete, Export, Email, etc.), refer to General Screen Layout.
Follow these steps to add a new Account User Trader:
The Alert screen, you can setup Alerts that will be raised in the Alert panel located at the bottom of the LISA Front End main screen. They can be configured to appear at specific times or according to a custom schedule.
For example, alerts can be useful to remind users that a market is going to close soon.
In order to access the Alert configuration window, follow these steps:
To see the different actions user can perform with the Action Panel (Delete, Export, Email, etc.), refer to General Screen Layout
Follow these steps to add a new Alert:
For the Monthly option, a day offset can be applied to the rule. This will raise the alert the specified days before (negative value) or after the set day.
Please review the section in this guide.
In order to access the Contract configuration window, go to [Configuration] Menu > [Static Data] > [Contract].
The Contract window opens.
This window is divided into three parts:
In this window, you can:
Follow these steps to add a new Contract:
The following four different price bases are available:
Note The fields followed by an * are mandatory.
A Contract Group is used to group contracts.
In order to access the Contract Group configuration window, go to [Configuration] Menu > [Static Data] > [Contract Group]
The Contract Group window opens.
This window is divided into two parts:
You can create as many contract groups as you want. To see the different actions users can perform with the Action Panel (Delete, Export, Email, etc.), refer to General Screen Layout .
Follow these steps to add a new Contract Group:
In order to access the Market configuration window, go to [Configuration] Menu > [Static Data] > [Market].
The Market window opens.
This window is divided into two parts:
To see the different actions user can perform with the Action Panel (Delete, Export, Email, etc.), refer to General Screen Layout
Note The fields followed by an * are mandatory.
In order to access the Member configuration window, go to [Configuration] Menu > [Static Data] > [Member].
The Member window opens.
This window is divided into three parts:
You can filter the existing members by clicking on a market name on the horizontal tab bar. By clicking on a market name, the list will display only the members defined for this specific market.
To see the different actions user can perform with the Action Panel (Delete, Export, Email, etc.), refer to General Screen Layout.
Follow these steps to add a new Member:
Please note that if you check this box, the new member will be considered as a Clearer member of the market.
Connectivity
Options
Matching
Force trades status to Uncleared instead of Unmatched. Provides the ability to define it at a member level rather than at the global system setting:
Free Info
Fill in any free text information relating to this member.
Member Groups
Use this to assign member groups to the member being created.
Note The fields followed by an * are mandatory.
In order to access the Source configuration window, go to [Configuration] Menu > [Static Data] > [Member Group].
Field Name | Description |
Member Group Information | |
Name | A unique name for the member group. |
Description | A useful description to explain the member group. |
Include Members | |
What is the purpose of this member group? | Regular: Allocation: |
Market | Market name for this member group. |
Member | Only one member per market can be selected. |
In order to access the Source configuration window, go to [Configuration] Menu > [Static Data] > [Source].
The Source window opens.
This window is divided into two parts:
In order to see the different actions user can perform with the Action Panel (Delete, Export, Email, etc.), refer to General Screen Layout.
Follow these steps to add a Source:
Note The fields followed by an * are mandatory.
To access the Transco configuration window, go to [Configuration] Menu > [Static Data] > [Transco].
The Transco window opens.
This window is divided into three parts:
As soon as you create a new Transco type, a new Tab will appear on the horizontal bar of the window. The Tab name will be formatted as follow: Application Name/Type Name. If you click on one of the tabs, the list will be filtered to display only the transcos defined for this pair.
To see the different actions users can perform with the Action Panel (Delete, Export, Email, etc.), refer to General Screen Layout.
For more information on the creation of Transcos, refer to the documentation “LISA Order Input - Transco Setup.pdf”.
This form allows of the setup of user friendly Trade Types and spread indicators in two LISA frontend virtual columns
Using this form you will be able to setup market specific trade variables that will calculate the trade type and relevant spread indicator. Wildcards are permitted in all fields.
The from fields are basically all based on the trade data. The result will be displayed in the virtual columns described above.
The fields:
This form allows for the setup quickly for various users and also to create market and members for a number of user logins in one go rather than from the profile or login setup.
The System Sub menu provides details on various system objects and Object versions. Namely, the database components version and core LISA objects.
Object Versioning: Will show you a table that provides information on the version of all the components running in your LISA environment.
Options: Provides you with options to change support contact information and version control.
Registration Code: Provides the provision of activating different licensed features by entering and storing the License codes.
System Object: Provides away to edit many of the LISA UI form fields renames and other
For support purposes, you can see the list of LISA database objects and their version.
The Option tab allows for two options:
Provides the provision of activating different licensed features by entering and storing the License codes under Configuration > System > Registration Code. This should be done with guidance from your Technical Account Manager.
The System Object allows for the Adding/Editing/Deleting of various market data mapping to normalized LISA fields. It also has the added feature of defining a windows downtime period.
You can edit the mapping of Clearing info for various Markets as follows:
To Add ClearInfo, you must perform these steps:
To Edit ClearInfo you must perform these steps:
To Delete ClearInfo you must perform these steps:
To Add Transcos you must perform these steps:
Note The Optional box defines the mappings requirement in the mapping.
To Edit Transcos you must perform these steps:
To Delete Transcos, you must perform these steps:
Allows for the adding of the free text fields to the Add Order (Alt+A) window. You can display (checked) or hide (unchecked) the following Free Text1-5 fields.
Accessed via the Menu [Configuration]>[System]>[System Object] tab UI.
This feature allows for the disabling of all LISA modules while the environment goes through maintenance. This has benefits should you wish to suspend LISA during market roll period that is not immediately after midnight of the core server module.
During this period, no users or modules will be able to connect to LISA. This is useful for running a LISAArchiver during this downtime period. The downtime period is populated in the Server Time field. Once you apply the time settings the “Your Local Time” field will be populated with the time appropriate to your timezone.
Possible formats:
Here you can specify the field name mapping for the Back Info and static free fields that are used to send information to the BackOffice System. The fields are reflected in the Account and Member static window.
To Add/Edit/Delete BackInfo follow these steps:
This allows for the renaming of the order free text fields for passing information internally normally between the Front office and Back-office systems.
To Add/Edit/Delete Frees follow these steps: