Hi Irshad,
1) general advice on id's
If the exact values of id's are somehting you care about, why exactly? If you have certain expectations/functional uses for a piece of information in an entity, you should add that piece of information as an attribute on top of your id, you should not overload you id with any other meaning than simply to uniquely identify one row. (typical example would be if you plan on using the id for showing the options in a specific order in your UI, don't, that's what an order attribute is for.)
2) specific advice on static entity id's
Don't have them on auto generate. This can cause all kinds of problems if you work across several environments, as you have no guarantee that they will get same id in all environments. This is problematic for moving (test) data between environments, but even simply for troubleshooting etc. it can be very confusing. If you do this, than as a side effect, you yourself have full control over which record gets which id attributed.
Dorine