Server : Apache System : Linux profile 3.10.0-1160.88.1.el7.x86_64 #1 SMP Tue Mar 7 15:41:52 UTC 2023 x86_64 User : apache ( 48) PHP Version : 8.0.28 Disable Function : NONE Directory :  /var/www/html/mmishra/erp-19-12-2019/includes/

Upload File : current_dir [ Writeable ] document_root [ Writeable ]

<?php

$erpDesign = "
<center>
<h1>Enterprise Resource Planning (ERP)</h1>
<h4>Design, Development and Deployment Plan</h4>
<h5>( Technical Perspective Draft #1 )</h5>
</center>

<br>
<h3>Title</h3>
We may start with targeting system for IIITA Resource Planning (IRP). Once it is functional we may scale up to a system for Institute Resource Planning (IRP).
If desired, we may further scale up to a system for Enterprise Resource Planning (ERP).

<br>
<h3>Objective</h3>
Automation of processes to achieve less-paper working environment, quick decision making and effective resource planning at the institute. To achieve this we need to develop following sub systems under ERP.
<ol>
<li>Data Capturing and Storing System (DCS)
<li>Transaction Processing System (TPS)
<li>Management Information System (MIS)
<li>Knowledge Support System (KSS)
<li>Decision Support System (DSS)
<li>Enterprise/Institute Resource Planning (E/IRP)
</ol>

<h3>Major Milestones</h3>
<ol>
<li>Design (one time exercise)</li>
<li>Development (one time but spiral exercise)</li>
<li>Deployment (one time trial and run exercise)</li>
<li>User training (initial and on demand exercise)</li>
<li>Operation (regular exercise for next 10 years)</li>
<li>Maintenance (occasional exercise for next 10 years)</li>
</ol>

<h3>Present Situation</h3>
No significant use of software solution currently, except below partial few in use at different sections/departments
<ul>
<li>Library</li>
<li>Health Care</li>
<li>Store Inventory</li>
<li>Electricity Metering & Billing</li>
<li>Admission, Registration, Course Selection, Grading etc.</li>
<li>Online Applications, Fee Submission etc.</li>
<li>Help Desk</li>
<li>Tally</li>
</ul>

<h3>Development Till Now</h3>
Mostly developed in house except Tally<br>
Open source technology except Library (Microsoft technology)<br>
Cover only data capturing and storing, transaction processing, information system, online access over campus LAN<br>

<h3>ERP Targets</h3>
To develop and deploy 
<ul>
<li>Knowledge Support System (KSS)</li>
<li>Decision Support System (DSS)</li>
<li>Institute Resource Planning (IRP)</li>
</ul>
<br>
This will start with 
<ul>
<li>Automation of routine activities</li>
<li>Less paper environment</li>
<li>Realtime system led communication (alert, messaging, feedback)</li>
</ul>

<br>
<h3>ERP Layout</h3>
<img src='images/erp-layout.png' width='70%' height='600'>
<br>
Records of employees, students and agency staff are maintained in the Central Database thru their respective application software. 
This enables central authentication system for all the application software. 
However, all application software maintains a private local database at their end with read only access to other applications for information sharing. 
A central backup server maintains a copy of all databases at a central location which for updation of records synchronizes itself with original databases periodically using incremental backup mechanism.

<br>
<h3>ERP Segments</h3>
<b>Academic</b>
<dir>
Admission, Assessment, Awards, Alumni, Research
</dir>
<b>Administrative</b>
<dir>
Establishment, Store, Purchase, Account, Finance, Estate
</dir>
<b>Services</b>
<dir>
Library, Maintenance, Hostels, Mess, Transport, Guest House, Health Care, Sports
</dir>
<br>
<img src='images/erp-main-panel.png' width='70%' height='600'>

<br>
<h3>Challenges</h3>
<b>Non-technical</b>
<dir>
Developers team<br>
User involvement<br>
Procedures and policies (standardization, optimization)
</dir>
<b>Technical</b>
<dir>
System Requirement Specification (SRS)<br>
Architectural design (3 tier, thin client, networked, online etc.)<br>
Database Management System (DBMS)<br>
Programming framework (language, model etc.)
</dir>

<h3>SRS Documents</h3>
We need to work on following documents for each module to be developed under ERP.
<ul>
<li>Process flow diagram (PFD)</li>
<li>Data flow diagram (DFD)</li>
<li>Entity relationship diagram (ERD)</li>
<li>Use cases</li>
<li>Exception handling</li>
<li>Test cases</li>
<li>Report formats</li>
</ul>
<br>
<h3>Major Concerns</h3>
Below are the few major concerns related to design of ERP and its deployment plan.
<ul>
<li><b>Security model</b> 
	<dir>
		Authentication<br>
		Authorization)
	</dir>
</li>
<li>Availability and Accessibility (24x7)</li>
<li>Concurrency load during peak hours</li>
<li>Scalability (not very serious in our case)</li>
<li>Maintainability (very important as the developed ERP will be used for years to come)</li>
<li>Backup and Restore</li>
</ul>

<h3>ERP Design</h3>
<b>Architectural design</b>
<dir>
	3-Segmented modules
	<dir>
		Academic modules<br>
		Administrative modules<br>
		Services modules
	</dir>
	3-Tier client/server architecture<br>
	Thin client user interface (Browser)
</dir>
MySQL as application independent backend database<br>
PHP/Python programming language without any framework<br>
Open source platform<br>

<h3>Security Model</h3>
To ensure a fairly secure ERP system in place, its design should include following features
<ul>
<li>Central authentication of user (LDAP)</li>
<li>Encrypted web access (HTTPS)</li>
<li>Digital signature, OTP verified login on servers</li>
<li>Referential navigation on private servers</li>
<li>Access control list (ACL) on central server</li>
<li>Activity logging on central server</li>
<li>Session tracking (sign in, sign out, idle locking)</li>
<li>Moderated database operations</li>
<li>Acknowledge alerts for critical data changes</li>
</ul>

<h3>Accessibility Model</h3>
Following accessibility model is followed in proposed design of ERP:
<ul>
<li>Online web application on top of central database (containg public domain records) with public access over campus network (central server)</li>
<li>Online web application on top of local database with private data over every departmental network (private server)</li>
<li>Synchronization of database of central server by private server (push)</li>
<li>Departments write data into departmental private servers (push to central server for public access)</li>
<li>Public write data into central server (pulling by private servers for departmental consumption)</li>
<li>Departmental private servers host official data to be accessed within department only</li>
<li>Central server hosts copies of departmental data that are to be consumed in public domain</li>
<li>Backup server stores copies of departmental server (outward write) and central databases</li>  
</ul>

<h3>User Authentication</h3>
Design include following user athentication model:
<ul>
<li>Central server authenticates users through LDAP server</li>
<li>Departmental servers authenticate users through the same LDAP</li>
<li>User activity logs are created on private as well as central server</li>
<li>Sessions of authenticated users are created on private/central servers</li>
</ul>

<h3>User Group Roles</h3>
Users to be classified into following groups and roles<br>
<dir>
	<b>Super users</b>
	<dir>
		Director and his Secretariate<br>
		Registrar and his Secretariate<br>
		Technical support In-charge (who need to work on design and business logic layer)<br>
	</dir>
	<b>Power users</b> (with privileged access to information stored in departmental databases)
	<dir>
		Dean<br>
		HoD<br>
		In-charges<br>
		Wardens<br>
		Officers<br>
		Doctors	etc.
	</dir>
	<b>Operators</b> (with restricted access to departmental data of their table)
	<dir>
		Support staff (data entry assistants)
	</dir>
	<b>Users</b> (with limited access to their personal data and interaction with ERP system)
	<dir>
		Employees<br>
		Students
	</dir>
	<b>Guests</b> (public access to general purpose information)
	<dir>
		Alumni<br>
		Parent of Students<br>
		Visitors and Vendors<br>
		Public at large
	</dir>
</dir>
<h3>User Interface</h3>
Following interface design is considered in the ERP:
<ul>
<li>Single sign-on user interface to all users except guests</li>
<li>Interface comprises with access links of all the desired applications/operations/functionalities as per user role and ACL</li>
<li>User can track his/her sessions, activities</li>
<li>Interface automatically changes with change in role of user</li>
<li>Interface prompts information pertaining to user for desired actions</li>
<li>Interface provides required formats, reports etc. as per role of user</li>
<li>Interface does not change with change in role, just content of interface changes according to role and ACL of a particular user</li>
<li>Interface tracks IP address of user's computer for timestamped logs for each and every activity performed by user across sessions</li>
</ul>

<h3>Data Validation</h3>
<b>3 Layer data validation model is good for data validity and integrity</b><br>
<ul>
<li>Client side data validation at the time of data entry will be done using HTML form inbuilt features and JavaScript</li>
<li>Process level data validation will be done by application</li>
<li>Backend data validation will be done by database server</li>
</ul>
HTML forms to be treated as data views or templates<br>

<h3>Programming Language</h3>
<b>Initially</b>
<dir>
	Academic modules can be coded in Python<br>
	Administrative modules can be coded in PHP<br>
	Services modules can be coded in either Python or PHP (any)
</dir>
<b>This approach will highlight power of each language</b><br>
At later stage all modules can be coded in both Python and PHP to achieve two versions of IRP<br>

<h3>Coding Standard</h3>
Standard coding practices to be followed for<br>
Proper indentation of code<br>
Desired level of comments in code<br>
<b>Standard variable naming for</b>
<ul>
<li>Constants</li>
<li>Temporary variables</li>
<li>Form variables</li>
<li>Program variables</li>
<li>Function name</li>
<li>Array name</li>  
<li>Database table and field name</li>
</ul>

<h3>Object Orientation</h3>
For efficient coding we have to work on following in a modular approach:
<ul>
<li>Objects in all modules to be identified</li>
<li>Accordingly classes to be defined with properties and methods</li>
<li>Constructor to be used for object initialization</li>
<li>Data handling must be encapsulated withing class definition</li>
<li>Processes handle data through object methods</li>
<li>Class files to be created for each module</li>
<li>Class files to be called from within the main program of each module</li>
<li>Proper naming and path must be followed for class files</li>
<li>Classes to be treated as data model</li>
</ul>

<h3>Library Files</h3>
Since modular system uses common functionalities across various modules, ERP design includes Library files that contain common function such as
<ul>
<li>Database connectivity</li>
<li>User account handling</li>
<li>User authentication via LDAP</li>
<li>User session handling</li>
<li>Log generation</li>
<li>Auto messaging (SMS) / auto mailing (Email)</li>
<li>Application configuration and setting</li>
</ul>
Library files to be called from within the main program of each module <br>

<h3>Look & Feel</h3>
In order to get a professional look and feel of developed ERP, design includes:
<ul>
<li>Cascading Style Sheets (CSS) is used for uniform look & feel of user interface and reports across the applications</li>
<li>Theme based user interface, banner, icons, navigation menu, links, forms, media files etc. is across the applications</li>
<li>Customization of look & feel is incorporated via configuration and setting of a particular applications</li>
</ul>

<h3>Database</h3>
Initially ERP design is based on MySQL database at the backend with following configuration:
<ul>
<li>MySQL with phpMyAdmin interface</li>
<li>Auto and programatic synchronization of all databases</li>
<li>Application wise separate database</li>
<li>Standard table and field naming convention to follow</li>
<li>Normalized design with primary and foreign keys</li>
<li>Inbuilt features to be used where ever possible</li>
<li>Triggers to be used for backend data handling</li>
<li>Auto time stamping of record creation as well as record modification</li>
<li>Moderated deletion of record in master/transaction tables</li>
</ul>

<h3>Deployment Plan</h3>
Following approach may be considered for deployment of ERP at campus network:
<ul>
<li>URL “https://erp.iiita.ac.in” may be used to access institute ERP</li>
<li>All applications can have second level URL as below
	<ul>
	<li>https://erp.iiita.ac.in/academic</li>
	<li>https://erp.iiita.ac.in/establishment</li>
	<li>https://erp.iiita.ac.in/store</li>
	<li>https://erp.iiita.ac.in/library etc.</li>
	</ul>
</li>
<li>Central server may be kept at server room under N & M Committee</li>
<li>Departmental servers may be kept at each department</li>
<li>Server that hosts various services may be kept at server room</li>
<li>ERP & A team to support users via remote access to their servers</li>
</ul>

<br> 
<h3>Deployment Design</h3>
<img src='images/erp-deployment.png' width='70%' height='600'>

<center><h5>( Functional Perspective Draft #1 )</h5></center>


<h3 align='left'>Task List</h3>

The following major tasks are required to be accomplished by ERP system under academic, adminstrative and service modules.


<h3>Academic Modules</h3>

<table width='50%'>
<tr><th><i class='fa fa-university'></i> DEPARTMENTS</th></tr>
<tr><td>
	Departmental administrative (faculty leave, student leave) and academic activities (course structuring, syllabus,
	course allocation, time table, experts lectures, projects), monitoring 	
</td></tr>
	
<tr><th><i class='fa fa-graduation-cap'></i> AAA</th></tr>
<tr><td>
	Student profile, course structure, syllabus, project list, academic calendar, section details, course allocation, 
	class time table, exam time table, loboratory details, class attendance, student leave application,
	student leave status, fee status, grading and academic performance reports
</td></tr>

<tr><th><i class='fa fa-building'></i> COW</th></tr>
<tr><td>
	Hostel details, fee chart, mess menu and rates, occupancy status, vacancy status, warden office activities, 
	inventory, maintenance
</td></tr>

<tr><th><i class='fa fa-book'></i> LIBRARY</th></tr>
<tr><td>
	Catalogues, loan status, overdue status, overdue fine, loan history, advance booking, waiting queue, 
	inventory, maintenance
</td></tr>

<tr><th><i class='fa fa-handshake-o'></i> ALUMNI</th></tr>
<tr><td>
	Alumni registration, social networking, alumni list, alumni meets
</td></tr>
</table>

<h3>Administrative Modules</h3>

<table width='50%'>
<tr><th><i class='fa fa-id-badge'></i> ESTABLISHMENT</th></tr>
<tr><td>
	Employee service book, leave processing, leave status, LTC processing, transfer/posting
</td></tr>

<tr><th><i class='fa fa-cart-plus'></i> STORE PURCHASE</th></tr>
<tr><td>
	Indent processing, material receipt, material distribution, dues status
</td></tr>

<tr><th><i class='fa fa-inr'></i> ACCOUNTS</td></tr>
<tr><td>
	Fee structure, fee status, fee submission, advances, dues, salary slip, bill processing, ledger maintenance,
	loan processing and recovery, settlements, boucher posting, balance sheet, audit reports
</td></tr>

<tr><th><i class='fa fa-bed'></i> VISITOR HOSTEL</th></tr>
<tr><td>
	Room rent chart, mess charges, booking request, booking status, occupancy status, vacancy status,
	inventory, accounting
</td></tr>

<tr><th><i class='fa fa-home'></i> ESTATE</th></tr>
<tr><td>
	Accommodation units, office units, allotment, occupancy list, vacancy list, furniture inventory, maintenance
</td></tr>
</table>
	
<h3>Service Modules</h3>

<table width='50%'>
<tr><th><i class='fa fa-ambulance'></i> HEALTH CENTER</th></tr>
<tr><td>
	Patient registration, prescription, medication, admission, discharge, tests, pharmacy store inventory, 
	medical receipts, doctor schedule, staff duty chart, ambulance runup, equipment inventory
</td></tr>

<tr><th><i class='fa fa-bus'></i> TRANSPORT</th></tr>
<tr><td>
	Vehicle/driver/helper lists, routine schedules, school list, school timings, school schedules,
	requisition processing, transport billing, inventory, runnibg/maintenance/refilling logs
</td></tr>

<tr><th><i class='fa fa-sitemap'></i> NETWORK MAINTENANCE</th></tr>
<tr><td>
	Password reset request, inventory, maintenance
</td></tr>

<tr><th><i class='fa fa-cog'></i> GENERAL MAINTENANCE</th></tr>
<tr><td>
	Accommodation units, office units, allotment, occupancy list, vacancy list, furniture inventory, maintenance
</td></tr>

<tr><th><i class='fa fa-thumbs-down'></i> HELP DESK</th></tr>
<tr><td>
	Ticket submission, monitoring, downloads, telephone directory etc.
</td></tr>
</table>



<br>
<br>
<h3>ERP Modules</h3>
ERP package consists of several modules. Each module focuses on one area of business processes, such as academic or establishment. 
The core modules of system are identified as:
<ol>
<li>Academic
	<ul>
	<li>Registration/reregistration</li>
	<li>Course allotment</li>
	<li>Time-table</li>
	<li>Attendance</li>
	<li>Examination</li>
	<li>Certification</li>
	<li>Placements</li>
	</ul>
</li>
<li>Establishment
	<ul>
	<li>Service book</li>
	<li>Leave register</li>
	</ul>
</li>
<li>Estate
	<ul>
	<li>Asset management</li>
	<li>Allotment</li>
	<li>Housekeeping maintenance</li>
	</ul>
</li>
<li>Store and Purchase
	<ul>
	<li>Tender processing</li>
	<li>Order processing</li>
	<li>Stock book entry</li>
	<li>Material management</li>
	<li>Utilization status</li>
	</ul>
</li>
<li>Finance and Accounting
	<ul>
	<li>Salary processing</li>
	<li>Payment processing</li>
	<li>Expenditure</li>
	<li>Budgeting</li>
	</ul>
</li>
<li>Student Affairs
	<ul>
	<li>Alumnae</li>
	<li>Technical activities</li>
	<li>Sports activities</li>
	<li>Cultural activities</li>
	</ul>
</li>
<li>Library
	<ul>
	<li>Acquisition</li>
	<li>Cataloging</li>
	<li>Circulation</li>
	<li>Housekeeping maintenance</li>
	</ul>
</li>
<li>Technical Department
	<ul>
	<li>Hardware</li>
	<li>Software</li>
	<li>Network services</li>
	<li>Maintenance</li>
	</ul>
</li>
<li>Works Department
	<ul>
	<li>Electrical/Civil maintenance</li>
	<li>Sanitary/Plumbing maintenance</li>
	<li>Stock book and utilization </li>
	</ul>
</li>
<li>Project Management
	<ul>
	<li>Project status</li>
	<li>Fund utilization</li>
	</ul>
</li>
<li>Security
	<ul>
	<li>Engagement</li>
	<li>Deployment</li>
	<li>Attendance</li>
	<li>Wages</li>
	</ul>
</li>
<li>Guest House
	<ul>
	<li>Visitor In/out</li>
	<li>Earning/expenditure</li>
	<li>Stock status</li>
	</ul>
</li>
<li>Health Center
	<ul>
	<li>Medication</li>
	<li>Medical procurement</li>
	</ul>
</li>
<li>Hostels
	<ul>
	<li>Allotment</li>
	<li>Stock status</li>
	<li>Mess management</li>
	</ul>
</li>
<li>Horticulture
	<ul>
	<li>Nursery stock</li>
	<li>Gardener attendance</li>
	<li>Wages</li>
	</ul>
</li>
<li>Alumni
	<ul>
	<li>Registration</li>
	<li>Communication</li>
	<li>Involvement</li>
	</ul>
</li>
<li>Pensioner
	<ul>
	<li>Registration</li>
	<li>Redressal</li>
	</ul>
</li>
</ol>
<br>
Above modules are preliminary and will be reviewed by automation team time to time in the development process for a better design of solution. 
This ERP to be an integrated system of network based distributed database applications under direct control of respective user departments. 
ERP & Automation Department ensures functional support to user departments, safety and security of databases on servers as well as uptime of applications over campus LAN.

<br>
<h3>AAA Process Flow</h3>
<img src='images/aaa-processflow1.jpg' width='80%' height='600'>

<br>
<h3>Accounts & Finance DFD</h3>
<img src='images/erp-ipay.png' width='70%' height='600'>

<br>
<h3>Inventory Management System</h3>
<img src='images/erp-istore.png' width='70%' height='600'>

<br>
<h3>Health Center System</h3>
<img src='images/erp-icure.png' width='70%' height='600'>

<br>
<h3>Transport System</h3>
<img src='images/erp-iport.png' width='70%' height='600'>

<br><br>Continue...
";

?>