MétaCan
Menu
Back to cohort
Record W3159678997 · doi:10.18280/mmep.080203

A Multi-Objective Risk Return Trade off Models for Banks: Fuzzy Programming Approach

2021· article· en· W3159678997 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

venuePublished in a venue whose home country is Canada.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueMathematical Modelling and Engineering Problems · 2021
Typearticle
Languageen
FieldEngineering
TopicOptimization and Mathematical Programming
Canadian institutionsnot available
FundersUniversity of KalyaniDepartment of Science and Technology, Ministry of Science and Technology, India
KeywordsLiquidity riskMarket liquidityBusinessInterest rate riskFuzzy logicLiquidity crisisInterest rateEconomicsActuarial scienceComputer scienceFinance

Abstract

fetched live from OpenAlex

The main focus of banking sector is on the risk management. Asset liability management (ALM) is one of the key processes to manage the risks. The objective of this paper is to develop a multi-objective asset liability optimization model for banks with the maximization of market value of equity and minimization of duration gap as the objective function. Several liquidity ratios, concept of duration and convexity are considered to manage the risk properly. Interest rate risk and liquidity risk are two major considerations in both the regulation and management of a bank. As we know that, with the fluctuation of the market interest rate, the market value of assets and liabilities of a bank changes and that affects a change in owner’s equity. In order to overcome such type of situation here we will use the concept of duration and convexity to manage the interest rate risk. In case of liquidity risk the shortage of liquidity may also put that bank in risk and simultaneously it is very crucial to manage the cash flow properly. So here we will use some major liquidity ratios to manage the liquidity risk. We will take the help of fuzzy programming technique to solve our model properly. A numerical example is given to illustrate our model by considering a hypothetical bank balance sheet. Also we will compare the result obtained by fuzzy technique with result obtained by a non fuzzy based technique.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.209
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.029
GPT teacher head0.218
Teacher spread0.189 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it