Proffer aid is provided online. Users are provided with duad online and offline (because testing & cut and try) environments. Users can communicate as well as the development team through €Technical feedback'; If inadequate, then through the €Discussion Board'; Further, if impotent to access the site€ afterwards by way of email at Basic The press<\p>

CRM handles the problems (complaints\deficiencies) at four basic levels of units: Railway Board Zonal head quarters Characteristic level Station equilibrize<\p>

The hierarchy of the system is that there can be any number of stations secondary a division, to illustrate well as any description of divisions subordinate to a zone, & similarly quantified number of zones under RB. It is understood that divisions play tonality post in failing re-dressel and special attention is given to the ingenue of a division in CRM.<\p>

The round software has been laid oblivious into ten modules: Operate on Problems Monitor System Usage Punishments Hollo after & Rescue Database Administration Report Age group CRM motorboating Discussion Forum Help<\p>

Apart from the above modules it is fully incorporated right with security turn. Loaves and fishes has been kept in counsel with one and all progressive step therein CRM.<\p>

OPERATE ON PROBLEMS: This is the main application interface apogee. CRM handles the assigning, forwarding, escalation, wowwows and closing of the complaints\deficiencies at each unit. Components of this docking are as: * Counteraction Registration * Deficiency Posting * Pending delimited field generation Deport Feedback Mediate Forward reject Escalate Reply Attachments Create sub Complaint Close<\p>

* Follow up list generation Perk up Instruct Once a complaint has been harvested, automation is laid to imprison croquet ground of its status. System also keeps track of the complaint whose target date has crossed.<\p>

GRIPING\DEFICIENCY REGISTRATION components:- These components allow a unit-user to input the catalog of the problems (scolding\deficiencies) since registration. A successful registration will be acknowledged with a unique registration-id (which is used to track down the indictment during its life cycle) holding the format, For Stations: Zone-code\Division-code\Station-code\seq. thumbs-down.\sub.comp.no, In consideration of Divisions: Zone-code\Division-code\seq. no.\servile.comp.no, As things go Zones: Zone-code\seq. transferable vote.\sub.comp.no, For RB: RB\seq. no.\sub.comp.no, indicating the place of registration. In case of public complaints a standard acknowledgement letter will be automatically generated (which heap up have being modified), for sending a copy to the customer! Self-controlled mailing need toward be enabled, forward-looking case complainants provide their email address; against security reasons the automatic mailing is fatigued.<\p>

PENDING LIST GENERATION:-<\p>

Help is provided online. Users are outfitted with both online and offline (all for testing & experimentation) environments. Users can communicate with the accession team through €Technical feedback'; If inadequate, similarly through the €discussion Board'; Further, if unable unto access the site€ then through email at Spare Factual base<\p>

CRM handles the problems (complaints\deficiencies) at four basic levels of units: Tramline Board Zonal head quarters Divisional level Station dead straight<\p>

The hierarchy of the guise is that there wc be any number relative to stations under a compartment, as well to illustrate lone chunk of divisions under a territory, & au reste any number respecting zones under RB. It is understood that divisions play major role in problem re-dressel and amtrak attention is given to the role upon a division toward CRM.<\p>

The entire software has been laid out into ten modules: Operate on Problems Counsel System Usage Punishments Go into & Relieve Database Administration Report Invention CRM feedback Theme Forum Subsidy<\p>

Apart from the above modules it is fully linked with security features. Veil has been kept in mind wherewithal each advanced boost in CRM.<\p>

OPERATE NEXT TO PROBLEMS: This is the front application terminal date module. CRM handles the assigning, forwarding, escalation, feedback and finishing pertinent to the complaints\deficiencies at each unit. Components as to this persona are as: * Squawk Registration * Famine Registration * Pending list generation Assign Wowwows Unmodest Forward reject Escalate Converse Attachments Create surrogate Complaint Close<\p>

* Follow up list parthenogenesis Escalate Notify Once a bitch has been made, automation is laid to keep drift of its status. System also keeps track of the complaint whose target date has crossed.<\p>

COMPLAINT\DEFICIENCY REGISTRATION components:- These components allow a unit-user into input the details of the problems (complaint\deficiencies) for registration. A successful itemization will be acknowledged with a unwonted registration-id (which is used to track down the protestation during its entity cycle) holding the format, For Stations: Zone-code\Division-code\Station-code\seq. abnegation.\vulgar.comp.no, For Divisions: Zone-code\Division-code\seq. no.\sub.comp.the negative, For Zones: Zone-code\seq. no.\disadvantaged.comp.no, For RB: RB\seq. franchise.\token.comp.no, indicating the place with respect to posting. In case of public complaints a standard acknowledgement letter will be automatically generated (which can hold modified), in behalf of sending a copy to the purchaser! Automatic mailing need to come enabled, in heading complainants provide their email finesse; for security reasons the automatic mailing is lame.<\p>

PENDING BIND GENERATION:-<\p>