Our company has been using database login and is considering moving to Windows login (due to lack of password policy in NAV and it is required by Internal Audit).
The estimation for this change is > 40 man days for 10 countries. We thought it is a bit too much.
Is this reasonable?
0
Comments
1. how many users?
2. how many databases
3. how many companies in each database
4. how many roles?
5...
6...
ERP Consultant (not just Navision) & Navision challenger
As idiot says, you need to provide more information, but assuming that one country = one database, and 4 days per database, that sounds excessive. Though that does depend how much travel time is involved for the 10 countries, I would assume that the largest part of the project will be traveling to each country.
Do you have remote access so that this can be done from one location.
The additional details:
- 1 databse each county, so 10 databases in total
- the number of users are different for each country. The one with the most users are about 165, while the least is only 3 users. In total, there are about 330 users.
- each database have about 2 companies on average
So, isn't the estimate of > 40 days a bit excessive?
If you are using SQL then yes, an additional configuration will be required at SQL, in case if that is your requirement.
Even if you would manually type this in, 40 days is outrageous. Do they have a team of 6 people on this or something?
RIS Plus, LLC
It sounds very excesive, but then maybe it depends on the hourly rate. Remember that in the end what matters is the job cost, and some people use the formula
where others work on the formula
Assuming everything you said is correct, i.e. that the Roles and users are already created and tested in DB logins, and you just want to change to Windows logins, then yes this is ridiculous, but we can only say that because we don't know all the facts. Maybe your partner knows something that we don't.
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
So the consultants said that the only way to have password policy in NAV is to change our login method to Windows login. We asked for the estimation of effort for this change, and they quoted us > 40 days.
I doubt our management will go ahead with this change since it is going to be so expensive (they said "> 40 man days", which means that it may be more). But then, it is an audit issue that we have to address. I'm thinking of another alternative, i.e. customizing password policy function in NAV for db login rather than moving everyone to Windows.
Anyone sees any possible problem with such approach?
I would not recommend changing native password functinality, that for sure is the wrong thing to do. I think the alternative is to get a second quote from another company.
There is nothing stopping you from shopping around, you can buy services where ever you want.
RIS Plus, LLC
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
Thanks all NAV gurus here who took the time to enlighten me on this.
RIS Plus, LLC
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
Hmm, now i do recall there seems to be a mention of something about coding. Probably that's why -- there are quite a number of re-coding to do for this change.
Now the estimation seems more reasonable... i'll find out more from the consultants.
Thanks, guys.
RIS Plus, LLC