Specifically, from my long understanding that happened after talking to your employees, positive, negative, pretty much everything has come from here. So in that case, what I couldn't identify is their current workload. So everyone is busy. I have identified that. Everyone is very busy. But the current workload, what they are busy with, to identify that thing, we need to spend a little more time with each person. But before I do that, go into an investigation, before that I will also talk with your Javed sir. Before I start, I mean, in-detail conversation. But roughly what I have presented is that none of them are free. Everyone is working. Okay. So now, what I need to do from Arif bhai, since Javed sir has specifically given me some instructions. So if I share those instructions with you all, then maybe we can close this more easily. So the first instruction is operational cost minimization. So now, the way everyone is busy, in that case, how we will do operational cost minimization, we need to identify that. That actually, how we can do this, what do you call it, execute it. So in that case, what we need to do, which I saw after talking, is that, number one, your current developments that are there, although I have heard from Javed sir that pretty much all of them have been paused, that no development will happen for now. So I don't know if you all have been able to implement that in your workflow yet, that's number one. Number two is, some projects, which projects you need to work on continuously, for example the SD module or if you need to work continuously on any other module, identifying that. Besides that, if we want to reduce the project cost or reduce something else, reduce the running cost, that's not possible. So what I need to do now, specifically I need this thing from Arif bhai, is for example, if we talk about the SD module, or if any other module of yours is currently in the development way, to start a disciplined documentation for each one. That is, how much work you have done in the SD module, how much work is left, how many days it will take you to do that work, what manpower will be needed for that, and what budget will be needed. I need these three things. Now if you think that the other modules are not finished yet or that will also have continuous development, then you should also say that. Since Javed sir has said to keep it on pause for now, then why haven't you paused it or for what reason, I mean, why this needs to be continued, needs to be developed continuously, you need to give us an explanation for that as well. So, first thing, the module you are working on, what state is it in, what percentage of work is finished, what percentage of work is left, a timeline for doing that, manpower and budget. Manpower will come based on the timeline, budget will come based on the manpower. Now, if you continuously develop all the modules, you will have to do a task like this for each one. Then what can we do? We can do things like the SD module. In the SD module, let's say we need five people for manpower. Or if any other module...

Okay. Regarding this, I'll just... Regarding this, I already had a... with you. No, I am not muted. Can you hear me now? Yes, I can hear you now. Yes. Okay. Another call came in between. Oh okay, okay. I, I already shared a file with you, ZARP Issues and Solutions, there are around over 150 issues there. which are currently in 'in progress' status, some are in 'not started' status. In fact, the thing you are asking for, the whole thing is right here. What pending tasks are there for the SD module, what pending tasks are there for the MM module, what pending tasks are there for the FICO module, what pending tasks are there for the PP module, everything is in that list, within that list. Maybe the estimation for all the tasks is not given there. What you are saying, timeline and manpower. This total estimation... we have already identified the tasks. Whenever we have work, we identify it here. Okay. I am in that documentation of yours. That documentation, thank you. I am in that one. But what we need to do here is, instead of all the tasks being one cluster, if we separate the cluster. Okay? Cluster one, cluster two, cluster three, cluster four, cluster five. I think you all work in five domains. So if we cluster it and say SD, this work has been done, this work is pending. And we need to map it with the plan that you have. At what stage you will lock the SD module in version one. Okay? Why? Because if we don't lock these features, we can't stop it. We will get old, our beards and mustaches will turn white, we will die, but this will not stop. We have to lock version one. That version one, this is the feature list. With this feature list, these things have been done, these things have not been done. Then we need to do it in proportion to that: timeline, manpower, budget. Absolutely specific. Then, for example, you are doing HRM. In a similar way. How much has been done, how much needs to be done, what features we will add, manpower, timeline, manpower, budget. For each of them, if we don't do it this way, then we won't be able to minimize this operational cost. For example, what I have identified here now is that everyone is a developer. Okay, they are different types of developers, database developers, app developers, frontend developers, this developer, that developer. When the application is finished, specifically, companies eliminate all the developers. Why do they eliminate them? Because there is no development work. What kind of work is it? It's maintenance work or fixing work, maintenance work. For that, I need one or two people or four, five, or ten people, depending on the project depth, that would be enough. What are the other staff needed for? My main... my other staff are needed for technical support, this, that, etc. Then that needs to be grown. So now, if your project finishes or if the project doesn't finish, in which space is it safe to lock it. I am saying, in which space it is safe to lock, we need to identify that and lock it. If we want to develop something, we can definitely develop it, but in a pattern. So that these manual things that are happening now, I see that you are doing a lot of manual work. If you don't stop these tasks, you will never be able to finish this project. Okay? And what we are thinking further now is that we need to bring in earnings. Now, this identification of ours, it needs to be done right now. Now, let's say, we, I mean, I and Russ will propose that this work can be done, this work can be done, that work can be done. But the decision will be made by, Javed sir or those who are at your senior level. But we need to show them the way, that if you, if we do this, then this result will come, if we do this, this result will come. So in fact, it might not be possible for us to reduce operational costs from here. Okay? But we can't say this now. The management also doesn't know how it's possible. If we don't show it, then they will have to be shown and told that yes, you want to do this or you are saying to do this. After doing the total assessment, we have found these things. Now you decide what we would do. Okay? So for this reason, I now have a developer of yours who works with database and frontend. So I have already spoken with him. that we need to do the mapping. Mapping your database with your total application. And until that is done, we cannot further develop it either. Okay? We need to review this database. that if we actually convert the database to another version, to make the total solution safe, how we will do that. Because one version has to be kept safe. Why does it have to be kept? From Oracle, so that we can go online then and there. So that there is no loss to our business, no loss to the investment. We need to do that. So all in all, our next week is very crucial. Within this next week, if you say that I will sit with you or if you add someone to me, like any project manager or someone, or even if you sit with me and we identify that, we, module one, this thing has been done, this thing has not been done, this thing needs to be done. Module two and the budgets. You don't have to do anything. If the details are separated for me, timeline, budget, manpower, I can do these myself. That's not a problem either. And if you work with me or if someone else from your team works with me, then that will be helpful for me as well.

So I think that the things I wanted to say are more or less clear. I will send an email after this meeting about what our next course of action will be. So do you have any questions, Rasel bhai or Arif bhai.

And Rasel bhai is probably going on holiday between the 16th and 22nd of December. So what we should do is that Rasel bhai, Rasel bhai is going on the 16th, if we can identify this before the 16th, then it's better for us. Because I have to talk with Javed sir as well, and I won't be able to talk to him until I understand whether it's actually possible or impossible to reduce the operational cost that I was told about. So the 16th is still a long way off.

From my side, now, in this ZARP Issues and Solutions, the pending tasks that we have, the pending tasks that are there, which we are doing, to differentiate those module-wise plus give an estimated timeline with manpower, right?

Yes, and then the budget. If the timeline and manpower are set, the budget will follow. Okay. Here in my sheet, if I divide this same sheet into four parts for you. Basically, it's divided into four parts, but that won't work. I have four tabs, look, SD, PP, FICO, MM, I have divided them into four parts. Is it just the pending tasks that are here? The issue description is there. What I need here, the pending task is there, which is pending, that's fine. What I need here is what you originally thought, what the SD module would actually be. Along with that, you probably designed the database. Right? What you have thought for version one. We need to do a mapping of that. Why will we do the mapping? Because mapping is needed to lock it. That I, this version... No, I'm not really clear on this mapping. What does mapping actually mean, an entity against each feature?

The mapping is, let's say you will bring a feature. Right? For example, in ZARP's SD module, a complete version's thing, that in the complete version, let's say there are 100 features. Yes? With these 100 features, version 0.1 will be locked. Among these features, among the 100 features, maybe you have done thirty, and seventy are left. Now, you have done thirty, from there the seventy that are left, one thing is an error, which you have already developed, the error needs to be solved, that is different. And developing a new one is different. Error, you have to give a timeline, a timeframe for the error, that in this ZARP, we have these errors. To develop this, we will need X amount of days, X amount of employees, X amount of money. That was the error part. Second is ZARP 0.1, we are locking it with these features. To further develop these features, in a similar way, timeline, people, money.

No, if you could just clarify the database mapping. Okay, database mapping is, when we do software development, when we do knowledge engineering, we first prepare the feature list. That I have 500 features here within the application. And these 500 features are in different sections, as you have divided them, FICO, SD, this, that. So after this division, my tables are ready. Okay? The mapping is, matching my original application with my database table, to see how much I have developed and how much I haven't. And what we do is, the original database that we develop, we don't touch that. Why don't we touch it? The reason is, touching one table means my entire business information, my entire thinking gets ruined. Because it's relational data... I mean, we do it with a relational database if any changes are needed. But the normal one is wireframing it, doing this, doing that. And when we make changes, this relational database we are using, which module it will attach to, what changes it will make after attaching, each one works as a specific card, like add, edit, delete, it works like this. So which table it will go to, which query it will run, how it will control that table by running the query and how it will produce the result, that is done with a relational database. So that there is less manual intervention in my original application.

Because... this thing is not really ready for us and doing this is a very time-consuming matter. This is... I mean... if you, if you divide it for me module-wise like this, first is, what have you done? The features. For example, if you first list the total list of features. That I have a list of 500 features here. Out of the list of 500 features, I have finished 200 features. Among the 200 features, I have bugs. Which is your bug fixing thing. And the remaining features haven't been developed yet. Then what I will do, I am taking a copy of the entire application's database from you. I can get that mapping done or I can do it. That won't be a problem. That actually... so you need a complete feature list now, basically. A complete feature list is needed, from there, what you have finished is needed. You have already given here what bugs there are. And future development, I mean, for everything you do, along with the things that are pending, if there are pending bugs in the feature list, then how many days it will take you, how many manpower will be needed, how much budget you will need for this. If you are to develop a new feature, I will have to do it in a similar way.

In this invoice number... the mapping, I am already creating an endpoint for that. I am creating an endpoint, I will share that. But after having a meeting with Javed sir, I will tell you those things when he gives permission. Not before that. So that maybe your 30 GB, 300 GB space or those things, to safely do it, to analyze it. Because I won't touch your current system. Okay. Okay? Just taking a copy and saving it in a different version, working on the database plus other things. Okay, is the plan to move the database to a different database? If we want to do AI, and if we don't have a registered version, if it's not a registered version of Oracle, then many problems will arise in the future. And it's risky. Why is it risky? Because if Oracle wants, they can change their business policy at any time. As soon as the business policy changes, if they don't provide support, if they stop it, then all the investment that we have made in the last six or seven years will go to waste. So for this reason, it is safe to convert and keep the database in another version. No, we already have... Rasel bhai, can you give an update regarding the licensing?

Okay, I don't know if Rasel bhai has spoken recently. But from what I know, I have spoken. So to get the licensing, you have to invest a lot of money here. Javed sir, until he understands, he doesn't want to do that. But Rasel bhai can give an update. Rasel bhai?

No, no, it's the same. Yours is the same thing. We just talked a few days ago. The same thing.

Now, for example, we will have to invest one crore taka here for the database, honestly speaking. And every month they have running costs if we want to take the licensed version. So in that case, it will be a huge expense, and the Chairman sir will think about whether he will actually do it or not. But we won't say whether you should do it or not. We will just say this is the situation, if you don't do this, then this kind of problem will happen. But as we know that if we save this version in another version and change our thinking, then it is possible for us to migrate. But you will continue running what you are running now. We won't touch that. What we will do, if we want to build our AI features, we will need a version of the database. Why? Because otherwise we won't get full accessibility. You will take the metadata storage to some other database. Yes, I mean, the total, total, your frontend, which is in React or Vue.js, which you have done. We will not change your architecture. We will just, for example, the database is now in, say, Oracle, it might go to some other big data. But the structure, everything will remain the same. Just the database screen will change. And when we go to different versions or different countries in the future, will everyone use Oracle? No. Some might want a different kind of database schema. So that our, for example, the people will remain the same, the uniform will change, for example. We will just change the hard drive like a hard drive based on customer requirements. But the total thing, the system, everything will remain the same. There will be no changes to that. Because that is not possible.

Okay, so now if I summarize a bit, that for each of our modules, the completed feature list and the upcoming planned feature list, these two lists have to be given to you. Those that are already completed and released, and those that are in progress but we haven't released yet. Those with a timeline.

Yes, with the timeline. Because if we don't do this, for example, even if we want to develop further now, our proper, we will develop it in a way that we have, what do you call it, accountability, that yes, we are this, Okay, this total list, this total list, in the database that was shared with you, there is a table called ADM_Features. The full list is right there, in the ADM_Features table.

No, that's not a problem. What I want is for you to kindly divide it. Because if you divide it, what will happen, the things you haven't done, those things will come in a section, like the SD module, these things have been done, these things have errors, these things need to be done in the future. That's how I want it. Okay, okay. Do you have any specific template that I should provide it in? No, no, not any template. In the ZARP Development Issues and Solutions template, if you add four or five tabs there, and after adding the tabs, if you individually identify each one and give it to me, that will be fine, no problem. Okay, okay, okay. Because you have already done these tasks, so it will be easy for me to analyze and make further decisions.

And if you have any query, you can knock me anytime, no problem. Rasel bhai, do you have any suggestions in this regard? No, it's okay. I don't have any suggestions for now. We will talk if needed. Okay, no problem. Okay, okay. Alright then, I will send an email to you both, with Javed sir in CC, about the things we discussed and to bring our results in line with that. And that's it. Okay, okay. Okay then, Rasel bhai, Arif bhai, so this, I'll just, last thing, how many days will it take for us to get this? I want that, Rasel bhai is leaving on the 16th, before that, if I can just check the time, kindly give me a second. So if we can finalize it by Sunday, then on Monday the 15th, I will talk to Javed sir about this whole matter before Rasel bhai leaves. I mean, on Monday... I can provide the completed feature list by Monday. The ones that are completed. The ones that are in progress and not started, it's not possible to give that by Monday. Because these are not in an organized way. Fully. Then by when can we finalize this? I need a specific date on which I will receive this.

You have to give me until next Thursday. Okay, Thursday is... Okay, then that's fine. So when you, I will sit with Javed sir in the meantime, no problem. You don't have to be there. So when you come on the 22nd, then if he gives it to me on the 18th, I can prepare a review by the 22nd, Insha'Allah. No problem. So on the 23rd or 24th, we can talk to Javed sir about this whole matter. Okay, no problem. If you need me, text or call me on WhatsApp, I will be available online, hopefully. Okay, that's fine. Then Rasel bhai, you do it by the 18th and give the feature list by the 15th so I can understand what the 100% feature list for each is. That we will lock it there, and in proportion to that, we have been told to pause development for now, so we are pausing it. Our development will start again after all this. Because we will finish this. The company wants to finalize this. So since the company wants to finalize it, but we will finalize it after we have thoroughly prepared what we have done, then we will move forward again. Okay? So in that case, what I said, whether it's possible to reduce our budget, we will understand based on this.

Okay, alright then Rasel bhai and Arif bhai, thank you. Then the call we had on Saturday, the call on Saturday, should we still keep that on the calendar? To talk to you? If something is needed, or should I delete it.

I don't think it's necessary. If needed, we will talk one-on-one because the list I will prepare, it will be fine if I just talk to you one-on-one. Okay then, Rasel bhai and Arif bhai, thank you for your cooperation. I will send an email regarding the whole conversation we had, then we will talk again next week, Insha'Allah. Okay? Sure. Okay. Thank you. Assalamu Alaikum (Peace be upon you).