Sie sind auf Seite 1von 153

Management Information System 1

MANAGEMENT INFORMATION SYSTEM (MIS),

NATIONAL PHYSICAL LABORATORY

SUBMITTED BY
Gopal Krishna
Registration No. 415025
DATE OF SUBMISSION: 30th March 2007

Under the guidance of Mr. Ashu Krishna


Submitted in partial fulfillment of the requirements for qualifying DOEACC B Level

Center of Development of Advanced Computing (CDAC),

B-30, Sector-62, Noida (U.P)


Management Information System 2

TABLE OF CONTENTS
1. Acknowledgement
2. Certificate of the Project Guide
3. Synopsis of the Project
4. Organizational Profile
4.1 About the organization…………………………1
4.2 CDAC - an overview…………………………...2
4.2.1 Executive Summary
4.2.2 CDAC- Vision
4.2.3 Mission Statement
4.2.4 Intellectual Resources
4.3 Strengths and Track Record………………3
4.4 History and achievements………………………………
4.5 Latest achievements……………………….7
4.6 Organizational Structure…………………….………8

5. Problem Formulation
5.1 About the Client……………………11
5.1.1 Introduction to “National Physical Laboratory”
5.1.2 Indian Patent Office
5.2 System Objective………………………….12
5.3 System Purpose……………………………………………13
5.4 System Context…………………………….……13
5.5 Need Recognition……………………….…………15
5.5.1 Accommodation………….……………16
5.5.2 Leaves………………………………………………….17
5.5.3 Employee Details (Personal and Service Details)
5.5.4 Pension………………………………………………18

6. System Study
6.1 Introduction……………………………………………20
6.2 Study of the Existing System (Manual)……………….20
6.3 Study of the Proposed System (Computerized)…………….21
6.4 Feasibility Study……………………………………………22
6.4.1 Why is it important? ………………………………2
6.4.2 Economic Feasibility………………………………….23
6.4.3 Technical Feasibility………………………………….23
6.4.4 Operational Feasibility…………………………..24
6.5 Cost and benefit analysis………………………………….25
6.5.1 Payback analysis…………………………26
6.5.2 Cost estimation……………………………………27
6.5.2.1 Function point………………………….27
6.5.2.2 COCOMO……………………….28

7. System Planning
7.1 Project Plan……………………………………30
Management Information System 3

7.2 Project Methodology…………………………………………0


7.3 Team Structure………………………………….31
7.4 Quality Assurance Plan……………………32
7.5 Project Monitoring System……………………………32
7.5.1 PERT………………………………………..33
7.5.2 GANTT……………………………………….35
7.6 Risk Management Plan……………………………6

8. System Analysis
8.1 Process Flow Analysis
8.1.1 Accommodation
a. Work Flow
b. Data Flow Diagram (DFD)
c. Entity Relationship Diagrams (ERD)
8.1.2 Leaves
a. Work Flow
b. Data Flow Diagram (DFD)
c. Entity Relationship Diagrams (ERD)
8.1.3 Employee Details (Personal and Service)
a. Work Flow
b. Data Flow Diagram (DFD)
c. Entity Relationship Diagrams (ERD)
8.1.4 Pension
a. Work Flow
b. Data Flow Diagram (DFD)
c. Entity Relationship Diagrams (ERD)

9. System Design
9.1 Table Structure……………………………………..58
9.2 User Interface (Form Design)………………………70
9.3 Report Design……………………………………………95
9.4 Hardware and Software Specification…………………….99
10. System Testing
10.1 Introduction………………………………………109
10.2 Unit Testing…………………………110
10.3 Integration Testing………………………….115
10.4 System Testing…………………………………….115
10.5 Acceptance Testing………………………………….116

11. System Constraints and Security


11.1 System Constraints……………………………………121
11.2 System Security………………………………………22
11.3 Suggested Enhancements…………………………….122

Bibliography…………………………………………………………..124
Management Information System 4

ACKNOWLEDGEMENT

It gives me immense pleasure to acknowledge my deep sense of gratitude to


CDAC, Noida for having accommodated me in their esteemed organization for
training and providing me with an opportunity to enlighten myself from the rich,
varied experience and distinct work culture of its management and staff at various
levels. Indeed, this opportunity has allowed me to work in real life situations
encompassing various functions and has gone a long way into furthering my
competency and professional skills.

I express my sincere gratitude to the Project Coordinator for Mr. Naveen Jain for
providing the opportunity to do my Project work at CDAC.

My sincere thanks are due to Mr. Varun Jain, System Administrator, CDAC for
providing me with all the facilities needed.

I am extremely thankful to Project Manager Mr. Paras Nath Barwal for having
provided me a challenging opportunity to work on this Information System and
guiding me through tough times during my training period.

I am fully inclined to express my sincere gratitude to our Center Manager


Mr. Navneet Jain and Faculty of DOEACC ‘B’ level, CDAC, Noida (B-30, Sector-
62, Noida) for valuable suggestions & help during the desertion period.

My special thanks to my Project Guide Mr. Ashu Krishna for her immense help,
guidance and ready-to-help attitude.

I take pleasure in expressing thanks to all my friends who very kindly evinced their
keen interest, helpfulness and encouragement at all the time endeavors as
hitherto.

Date :
Place : Noida Gopal Krishna
Management Information System 5

Certificate Of The Project Guide

1. Name & address of the student : Gopal Krishna

2. Registration No : 415025

3. Name of Accredited Center : CDAC, Noida


B-30, Sector-62, Noida

4. Title of Project: : Management Information System


(MIS) , National Physical Laboratory

1. 5. Name & address of the guide : Mr. Ashu Krishna


F-104, Rail Vihar, Sector - III
Vasundhara
Ghaziabad, (UP)
India

6. Qualification of the guide : M.C.A.

7. Working experience of Guide (in years) : 7+

Signature of the student Signature of the Guide

Date: ....................... Date: ...........................


Management Information System 6

3. Project Synopsis
Management Information System 7

Synopsis Report
On
Personnel Information System

Indian Patent Office

Government of India

Submitted By:
Devyani Sharma
B Level - sixth semester
Registration # 266592

Date of Submission:
October 15, 2008

Under the guidance of:


Mrs. Priti Razdan

In Partial Fulfillment of
B Level Course
From DOEACC Society
Session: 2004-2005

CENTRE FOR DEVELOPMENT OF ADVANCED


Management Information System 8

Table of Contents

1. Introduction 9
1.1 Objective 9
1.2 System Purpose 9
1.3 System Scope 9
2. Resume of the Project Guide 11
3.System Description 16
3.1 System Context 16
3.1.1 Accommodation
3.1.2 Leaves
3.1.3 Employee Details
4. Process Analysis 19
4.1 Accommodation 19
- Data Flow Diagram
4.2 Leaves 20
- Data Flow Diagram
4.3 Employee Details 21
- Data Flow Diagram
5. Referenced Documents 23
Management Information System 9

Introduction

Objective
The objective of the system is to:
• Enhance the use of technology as a cost-effective support to the NPL (National
Physical Laboratory) mission.
• Provide an infrastructure for the sharing of information and computer
applications throughout the organization.
• Support the operational, tactical and strategic information needs of NPL.

• Provide an infrastructure for sharing of information between the employees of


NPL.

System Purpose

The current document serves as a System Requirements Specification (SRS) for


Computerization of Management Information System for NPL, an integral part of
CSIR under Government of India.
National Physical Laboratory, our client, desires a computerized system to carry out
various functions of the organization. The functions such as Administrative work;
Accounts, etc are time consuming and human intensive.
With a view to reduce the above chances of errors and providing the staff a
technologically enabled and capable system, NPL has embarked on a trail-blazing
approach to automate the above system to the level that minimizes human
intervention and maximizes end-user satisfaction.

System scope

• Recording the employee details e.g. Name, Address, Educational Qualification,


Present Posting, present Salary details.
• Recording of Leave details e.g. From Date, to Date, type and current leave
balance, CL/RH handling at different levels.
• Recording the Training details e.g. Course Name, Name of organization.
Management Information System 10

• Recording the details of Advance e.g. Advance Type, Advance Amount, date of
Advance, Number of Installments, Installment Amount.
• Recording the details of Promotion e.g. New post, new basic, Promotion date.
• Capture of Transfer Details e.g. New Place of Posting, Transfer Date, Order
number etc.
Management Information System 11

Resume of the Project Guide

Priti Razdan
Name and Address: 314 Gobind Apartments
Vasundhara Enclave, New Delhi
India
Pin: 110096
Phone: +91-11-22618362
Mobile: 9811669318
E-Mail: priti_razdan@yahoo.com

Education B.E (Electronics) from Poona University


Passing out Year: 1994
Advanced Diploma in computing from Center for Development of
Advanced Computing (C-DAC) New Delhi Aug 1996 – Jan 1997

Work Experience About 7 Years


Currently Working in Center for Development of Advanced Computing (C-DAC) New Delhi
Since February- 1997 as Member Technical Staff
Domain o Relational Databases and Related applications in
o Client Server Architecture
o N-tier Architecture.
Languages o C
o C++
o Java
o PL/SQL
o ANSI SQL
Programming Skills o Structured Programming Concepts
o Object Oriented Programming Concepts
o Event Driven Programming Concepts.
S/W Engg. and Quality o Software Development Life Cycle
Assurance. o System Analysis and Design
o Entity Relationship Modeling
o Data Flow Diagramming
o CMM Level – 3 standards implementation.
Database Skills o Database Normalization
o Database Design and Implementation
OS o MS-Windows
o UNIX
o SOLARIS
o DOS
Platforms o Intel Pentium Series
o Sun Ultra Sparc Series.
Management Information System 12

Development and o Developer 2000


CASE Tools o VB – 6.0
o JDK – 1.2
o Designer 2000
o Toad
o PL/SQL Developer
o Oracle Enterprise Manager

RELEVANT PROJECT SUMMARY

Crystallization of HIS as libraries and implementation of HL-7 Standards


OS To be OS independent
Platform To be Platform Independent
Database Oracle 8i and MS SQL Server 2000
Languages/Tools PL/SQL, ANSI SQL
Duration Dec 2003 – Till date
Team Size 1
Description The objective of this exercise was to:
o Redesign the already done HIS projects as a set of library
routines so that fast implementation and customization is
possible.
o HL – 7 Messaging standards was also to be incorporated into
the software.
o Use XML as an interface with the database.
My Role Core Member
Role Summary o Redesign of all the modules of HIS with minimum inter-
dependence so that one module can be implemented
independently if necessary.
o Implementation of HL-7 messaging standards so that the
software can be interlinked to any other HIS or PACS as and
when necessary.
o Provide the libraries in both Oracle and MS SQL Server
Databases independent of Platform or OS.
o Implement HIS using any front-end tool.

Intranet Based Software Solutions For Central Water Commission


OS (Back End/Front Windows 2000/Windows 2000
End)
Platform Intel Pentium IV
Database Microsoft SQL Server 2000
Languages Java, JSP, TSQL
Application Server Jrun, IIS Web Server
Duration Jul 2002 – May 2003

Description The objective is to develop an Intranet Based integrated solutions, from


scratch according to the requirements of The Central Water
Commission, Delhi having about 2500 employees on its rolls. The
software has the following modules:
o Personal Information System
o Financial Management System
o Parliamentary query System
o Library Information System etc
Management Information System 13

My Role System Analysis, Design and Development for the Financial


Management System.
Role Summary o Initial discussions, and Preliminary Study.
o Study and preparation of Design Documents
o Design of Database and Data Normalizations.
o Design and Coding of Back End procedures and functions.
o Coding of
o Employee Masters module
o Parliamentary Query module
o Work Allocation and supervision of team of programmers.

Intranet Based Software Solutions For Indian Patent Office


OS Windows 2000/Linux
Platform Intel Pentium IV
Database Oracle 9i
Languages Java, JSP, SQL, PL/SQL
Application Server Web Sphere
Duration Jul 2002 – May 2003

Description The objective is to develop an Intranet Based integrated solutions, from


scratch according to the requirements of The Indian Patent Office,
Kolkata having about 900 employees on its rolls. The software has the
following modules:
Personal Information System
Financial Management System
Budget System
Library Information System etc.

My Role Team Leader, System Analysis, Design and Development for the
Personnel Information System.

Role Summary o Initial discussions, and Preliminary Study.


o Study and preparation of Design Documents
o Design of Database and Data Normalizations.
o Design and Coding of Employee Masters & leave module.
o Work Allocation and supervision of team of programmers.

Intranet based Hospital Information System


OS Windows 2000/Windows 2000
Platform Intel Pentium IV
Database Oracle 8i
Web Server Apache Web Server
Duration Dec 2000 – Sep 2001
Team Size 5
Description The objective of this exercise was to redesign the already done HIS
projects as a browser based solution.

My Role Team Leader


Role Summary Implement HIS using Java based front-end tool.
Work Allocation and supervision of team of programmers.
Management Information System 14

Hospital Information System for Guru Tegh Bahadur Hospital New Delhi
OS Windows NT/Windows 95
Platform Intel Pentium III
Database Oracle 8i
Languages/Tools PL/SQL, Developer 2000, Designer 2000
Duration Feb 2000 - Nov 2000
Team Size 8

Description The objective was to develop the HIS from scratch according to the
requirements of a General Govt. Hospital. GTBH Delhi is a 900-bed
Govt. Hospital, which sees about 3000 patients in its OPD daily. The
project was implemented with a server and 30 Nodes. The software
had the following modules:
Registration
Investigation,
Central Admission
Casualty Management.
Medical Records
My Role Team Member/Database Administrator

Role Summary Preliminary Study and Technical Proposal.


Initial System Study and Database Design.
Coding of Back end procedures and functions.
Coding of the masters and Investigation modules.

Hospital Information System (HIS) for Sanjay Gandhi Postgraduate Institute of


Medical Sciences, Lucknow
OS (Back End/Front Solaris 2.8/Windows 95
End)
Platform Sun E450 on Sun Cluster 2.0/Intel Pentium
Database Oracle 9i
Languages/Tools PL/SQL, Developer 2000, Designer 2000
Duration Jan 1998 - Jan 2000
Team Size 8

Description SGPGI, Lucknow is a 600-bed super specialty hospital. The system


had a Sun Server with a 300 Node network on a fiber-optic backbone.
The objective of the project was installation of server, design of
network and design and development of 14 modules of application
software to eliminate delays faced by patient and streamline the
working of the hospital.

My Role Team Member

Role Summary Design and Development of OPD, Investigation, Operation theatre


& Central Sterile Stores Department module
Design and Development of Role based security features.

Quick Start Program (QSP) for Bangalore Water Supply and Sewerage Board,
Bangalore.
OS Windows NT/Windows 95
Platform Microsoft
Database MS-Access 1.1.
Management Information System 15

Languages/Tools Visual Basic 4.0


Duration Feb 1997 - Dec 1997
Team Size 3
Description This application has five basic parts:
Geographic Information System, Water Resource Management,
Project Management, Personal Information Management &Accounting
and MIS reporting.
My Role Team Member
Role Summary Design and Development of Water resources Management System,
Personal Information System and Project Management module.

Other Activities:
1. Complete System and Requirement Analysis for University Grants Commission
(May – Jun 2001)
2. Complete System Analysis, Study and Design of Database Solution for Lok Nayak Hospital
Delhi (Oct – Nov 2003)

I hereby declare that all the information provided above is true to the best of my
knowledge

Priti Razdan
Date:
Management Information System 16

System Description

2.1 System Context

Centre for Development of Advanced Computing, C-DAC, Noida has undertaken the
project of providing total IT solution for NPL. It is intended to serve the requirements
of the staff members of NPL and to provide adequate and quick services to the
associated clients of NPL.

The total IT solution for NPL focuses on computerizing process of Management


Information System, Technical Information highway, Budget management, Financial
Management System, Intranet Main Page Development, Administrative Features &
Work Flow Features and Library Management System. This Synopsis report focuses
on the proposed system for Management Information System.

The system is envisaged as a three-tier solution to fulfill the objectives of centralized


database server, business logic and multi-location clients on Intranet and Internet.
The three-tier software architecture is a versatile, request/ response based and
object oriented infrastructure that is intended to improve usability, flexibility,
interoperability, and scalability as compared to centralized, mainframe and time
sharing computing.
The Management Information System comprises of the following sub modules:
 Accommodation
 Leaves
 Employee details
We now concentrate on each separately.

2.1.1 Accommodation

• Accommodation Section receives notification from the Directorate of Estate


of any available accommodations.
Management Information System 17

• Accommodation Section informs the employees of the concerned


directorates to obtain the form from the Directorate of Estate depending on
the category of the quarter to be applied.
• Accommodation section indicates the code on each and every form and also
prepares the abstract report to be sent to the Directorate of estates.
• The acceptance form, which is filled by the employee after getting verified by
the concerned establishment section, is sent to accommodation section.
Accommodation section puts the endorsement number and sends the form to
the directorate of Estates.
• Request for change of allotted accommodation is also done by
accommodation section.
2.1.2 Leaves
• The leave balance has to be examined before sanctioning the leave.
• Leave has to be integrated with the other departments like Pay and Account
office, which will calculate the salary accordingly.
• Reports like how many people took leave within a particular period require a
lot of processing in the current system.

2.1.3 Employee details


• Compiling personal details about employees e.g. knowledge of a specific
foreign language, employee’s mother tongue or state of domicile is
cumbersome.
• At the time of review, gathering information about the employees with
membership of Professional bodies (subject wise experts, academic
qualifications) is time consuming.
• Preparing a list of Employee of age group 50-55, due for retirement (Grade
wise, Across the board) is very time consuming.
• Lengthy manual efforts required to time Information about the total period of
ex-Cadre assignment can be calculated.
• Foreign assignment period based queries can be retrieved from the
database.
• Keeping Track of deputation details like period of deputation, borrowing
organization, absorption date, designation and place of posting is difficult.
Management Information System 18

Process Analysis

An analysis of the user requirements specification and other information led us to


present the following needs of the module, to provide solution for above issues.
 Online submission of various Inter Office forms for all kinds of functions, which
are currently, being done using manual forms.
 Integration of working of Accommodation, Account, Pay and so on.

3.1 Accommodation:

 Put the circular about the accommodation availability from Directorate of


estates online for various directorates to refer.
 Allowing provision for online application of the quarters for the employees.
 Provision for online change request of the quarters for the employees.
 Generating statistical reports indicating the quarter requests for each
quarter category in a given time period.
 Putting online information for the employees who have been allotted an
accommodation and who have accepted the same.

Data Flow Diagram


Management Information System 19

Accomodation
Request Personnel
Quarter
Allotment
Employee Information Details
Finance
System

Accommodation Module Context Level Diagram

3.2 Leaves

 Sending online request for Leave.


 Online sanctioning of the leave by the controlling officer.
 Sending the leave application to the concerned section for issuing the
sanction.
 Updating the leave account as per the sanction order.
 Cancellation/Additions to the previous leave request.
 Submitting an online departure report to the controlling officer before going
on leave and likewise submitting an online arrival report to the controlling
officer.

Data Flow Diagram

Leave
Personnel
Request Sanction
Employee Information Order
Employee
System

Leave Module Context Level Diagram


Management Information System 20

3.3 Employee Details (Personal & Service related)

• Storing employee’s Employment summary details.


• Storing personal details about employees e.g. knowledge of a specific
foreign language, employee’s mother tongue or state of domicile, retirement
date etc.
• Storing qualification and specialization related details of the employee like
membership of Professional bodies.
• Storing employees Posting details.
• Storing ex-Cadre, foreign assignment details of employees.
• Storing deputation details like period of deputation, borrowing organization,
absorption date, designation and place of posting.
• Storing employee promotion / increment due dates.
• Provision for searching of Employee details.

Data Flow Diagram

Details
Personnel
Utilized
Employee Information
Authorized
System Users

Employee Details Module Context Level Diagram


Management Information System 21

Referenced Documents

The following documents were referenced:


1. System Requirements Specification (SRS) Ver 1.0
2. System Requirements Specification (SRS) Ver 1.1
3. An Integrated Approach to Software Engineering – By Pankaj Jalote
4. System Analysis and Design – By Elias M. Awad
5. Concepts of Software Engineering – By Roger Pressman
Management Information System 22

4. Organizational Profile
Management Information System 23

4.1 ABOUT THE ORGANIZATION

• Initiation

• Started in March 1988,by Government of India.


• Scientific Society, under the Department of Information Technology, under
Ministry of Communications and Information Technology.

• Objectives

Design and Development of massive Parallel Super Computing Technology.

• CDAC Strengths

• Total Solution Through Emerging Technologies.


• Turnkey Solutions to key sectors such as:
• Real Time Systems (Water, Power).
• Telecom.
• Health Care, and
• Finance.

• Need for Advanced Computing Solutions

• Today’s business is managing information.


• Information is:
• Complex
• Large
• Volatile
• Information Should Be:
• Complete
• Accurate
• Available

Aim of computerization is to achieve the business objectives through information


management.
Management Information System 24

4.2 CDAC - AN OVERVIEW

4.2.1 Executive Summary

Established in March 1988, as a Scientific Society of the Department of Information


Technology (formerly Department of Electronics), under Ministry of Communications and
Information Technology, Government of India, The Centre For Development of
Advanced Computing (CDAC), is primarily an R& D institution involved in the design,
development and deployment of Advanced Information Technology (IT) products and
solutions. CDAC’s operations are mission oriented and driven by its mission objectives.

In the decade since inception, CDAC has developed a range of high-performance parallel
computing products, popularly known as the PARAM series of computers.

Asia's most powerful computer, after Japan, the PARAM 10000, with its cumulative peak
computing power of 100 Giga-Floating-Point-Operations per Second (GFLOPS) is housed
at the National PARAM Supercomputing Facility (NPSF) at CDAC in Pune.

Our expertise also extends to a number of other related areas. These include, Indian
Language support for information technology products through CDAC’s GIST technology
and human resource generation in the key sectors of IT through Advanced Computer
Training School. CDAC has also been offering advanced IT solutions in various sectors
such as power, telecom, health, banking and finance and to the government.

In a little over a decade since inception, CDAC has developed a range of high
performance parallel computers, known as the PARAM series of supercomputers. The
latest in the series is the PARAM Anant, which is a low-cost supercomputing solution
based on CDAC’s unique Open Frame architecture for scalable and high-performance
computing that incorporates the well-known Cluster of Workstations (COW) and Massively
Parallel Processing (MPP) concepts. PARAM Anant is based on, off the shelf, low-cost,
commodity processors & networks but provides a similar environment & features available
with the more comprehensive & powerful PARAM 10000.
Management Information System 25

Presently, more than 50 installations of various PARAM systems exist in India & abroad.
Recognizing the fact that it would not be possible for all academic, research facilities and
other users in the country to have full-scaled PARAM systems, CDAC has set up a
National PARAM Supercomputing Facility (NPSF) at Pune. The facility houses the most
powerful supercomputer built in the country, PARAM 10000 and facilitates researchers and
other supercomputer users to use the same for their work. In addition to utilizing the
system in-house, the PARAM may be accessed over wide area network.

CDAC’s expertise also extends to other related areas of Information Technology and
includes pioneering work undertaken in the field of multilingual & multimedia technologies,
education and training and developing IT based solutions in areas like Financial Modelling,
Network & Internet Security, Real Time Systems, e-Governance, Geomatics, Digital
Library & Artificial Intelligence.

CDAC evolved the Graphics and Intelligence Based Script Technology (GIST), with a view
to extend the benefits of Information Technology to the vast and diversified multilingual
population of India. Use of the GIST range of products has lead to the proliferation of the
use of computers and their application in all major Indian languages Countrywide.

Some of the multilingual software products include LEAP office, GIST shell toolkit, GIST
SDK, GIST Mail, iPlugin, ISM2000 Language learning software LILA and Machine aided
translation MANTRA tools are other products based on Artificial Intelligence.

CDAC has undertaken a number of development projects in the area of Electronics and
Information Technology, which have been assigned and sponsored by the Department of
Information Technology, Department of Official Language (DOL), Department of Science
and Technology (DST) and the Department of Scientific and Industrial Research (DSIR).

As part of its business activities, CDAC has executed projects, which are broadly
categorized in the areas of:
• High Performance Computing
• Internet and Networking
Management Information System 26

• E-Governance
• Geomatics
• Banking and Finance
• Power
• Telecom
• Medical Informatics & Healthcare
• Real Time System

CDAC’s website at www.cdacindia.com provides a window into the developments and


activities at CDAC. It also includes free downloadable versions of multilingual and
multimedia software.

CDAC has offices at Pune (HQ), Noida, Bangalore, Hyderabad, Calcutta and Chennai with
employees’ strength of around 1800, more than 60% of these are in technical areas of
development, sales and support functions.

The Pune Center has the National PARAM Supercomputing Facility, PARAM Hardware,
Networking, Application Development Team, Language Technology Team, Financial / Data
ware housing Team, Advanced Computing Training School Team, Defence Application
Group. The Pune Center is the Headquarters of CDAC, with the Executive Director &
Director’s office.

The Bangalore Center is headed by a Director with the major groups of E-Governance,
Systems Software Development (SSDG), Real Time Systems (RTSG), Business Division
(BD), Advanced Computing Training School (ACTS) and GIST Group. The Organization
chart is given in the following page.

The Noida Center is headed by ED with NLP group, the Business Division, the ACTS
(Advanced Computing Training School), GIS and R&D and Software Development Team.
Management Information System 27

CDAC established a new Center at Hyderabad beginning 1999, to participate more


effectively in the on-going Information Technology revolution in the State of Andhra
Pradesh.

The Chennai, Calcutta & Thiruvananthapuram Center has ACTS (Advanced Computing
Training School), Data Warehousing Group, GIST (Graphics and Intelligence Based Script
Technology), and a Software Development Team.

4.2.2 CDAC Vision

To emerge as the premier R&D Institution for the design, development and
deployment of world class IT solutions for economic and human advancement.

4.2.3 Mission Statement

To carve out a niche in the global arena of advanced Information Technology and enhance
our brand image.

To continue to create and deploy the finest talent in our quest for further expanding the
frontiers of High Performance Computing and Communication Technologies and its
applications.

To achieve rapid and effective spread of knowledge by overcoming language barriers


using Natural Language oriented computing and Multimedia Technologies.

To share our vast reservoir of experience for education and knowledge enrichment in the
field of Information Technology.

To utilize the intellectual property thus generated, bring benefits of Information Technology
to Society, by converting it into an exciting business opportunity and establishing a self-
sustaining and wealth creating operation.

4.2.4 Intellectual Resources


Management Information System 28

CDAC’s team of professional and skilled personnel is its valuable asset. Its manpower has
virtually remained constant throughout the year despite rapid growth in projects. Of the
557 members, 210 are deployed on mission related projects of CDAC, 145 on business
related operations and 62 members are engaged in sponsored projects & remaining in
administrative & Human Resource Development activities.

Compared to the trends in the Indian IT industry for attrition, the CDAC’s attrition rate is
around 10%, well below the current industry rate. CDAC’s ability to retain talent stems
from initiation of employee friendly policies, unique work culture and exciting learning
opportunities at the cutting edge of technology.

Being a high technology development center of excellence CDAC has a blend of qualified
and experienced management and technical teams.

The management of CDAC is under the overall direction of the Executive Director ED.
Shri. S. Ramakrishnan, ED reports to the Governing Council chaired by Minister of
Communications & Information Technology & consisting of eminent persons in their fields
appointed by the Government of India. For the management of CDAC, a Project Board
chaired by the ED, consists of the Directors at Bangalore and Pune and the Registrar who
is the Secretary to this Board. Programme Coordinators (PC) who have long experience in
their fields and have held positions of esteem among their peers heads the various
technology groups. The PCs are formed into task force, led by an expert for a particular
task among the PCs. PCs are also co-opted into the Project Board as required.

Mr. R. K. Verma heads the CDAC Noida center, under which the two separate, group
Training, Research & Development and Business Development works He has more than
25 years experience in the Information Technology Industry, HMS and E-Governance
activities at Noida Centre. He has provided detailed computing solutions for various
sectors in the Industry, which includes fault tolerant redundant systems and wide area
networks and total solutions including hardware, network and application software. He is
coordinating various projects and collaborative efforts with Health Sector, e-Governance in
various Government Departments, Department of Information Technology, under Ministry
of Communications and Information Technology, and other institutions.
Management Information System 29

Mr. Naveen Kumar Jain, who has more than 12 years experience in the Information
Technology Industry, manages the R&D and Training activities at Noida Center.

4.3 Strength and Track Record

CDAC’s HPCC-Networking (High Performance Computing & Communications) group, for


providing Networking solutions, is involved in designing and implementing Enterprise-wide
networks for Telecom, Healthcare, Education, Finance and other core sectors. A brief
profile of CDAC’s earlier experience is given below:

SOME OF THE PROJECTS SUCCESSFULLY IMPLEMENTED BY CDAC

S. No. Name of the Organization Description

1 Pune University Enterprise wide CDAC has designed and implemented a state-
Networking, Pune of-the-art network for Pune University, over
Fiber optic (7.5 Kms. of Fiber) FDDI Backbone
networks. All the departments of the University
are connected to each other through this
network.

2 Department of Post, Ministry of CDAC has designed and implemented a state-


Communication, Govt. of India. of-the-art network for Department of Post, All
New Delhi the departments of the DOP are connected to
each other through this network. The network
also connects the New Delhi office to the
North East Office in Assam and Meghalaya
with WAN connectivity. The network connects
more then 200 nodes at all the places.

3 Power System Monitoring - CDAC has implemented a state-of-the-art


NRLDC, Delhi, SCADA Real Time System project based on
ERLDC, Calcutta, distributed computing over Dual Ethernet
PSEB, Patiala LANs at these Load Dispatch Centres. Special
data concentrators developed by CDAC are in
operation to integrate data arriving from
multiple vendor equipment with different
protocols over DOT, PLCC and VSATs. Fault
tolerant servers and LANs have been
implemented for this critical application.

4 Pune NET (Library Net) This Network is implemented for connecting


Management Information System 30

the various libraries around Pune city, with the


main University library as part of the Pune
NET project.

5 Personnel Management The Personnel Management Information


Information System for Indian System designed for Indian Railways caters to
Railways the various Personnel Management tasks. It
consists of 17 (Seventeen) modules namely
Recruitment, Training, Service Record, Pay
Fixation, Increment, Seniority, Reservation,
Transfer, Promotion, Casual Labour,
Qualifying Service, D & AR, Court Cases,
MPP, Pass, MIS, Policy. The application has
been successfully implemented in Delhi
Division of Northern Railway. The use of PMIS
has given the Indian Railways the benefits of
Automatic Updation of Relevant Records,
Automatic Linking of Different Events,
Reduced Processing Time, Increased
Productivity, Automatic Error Detection, Built in
Accountability and Responsibility for Different
Levels and ability to generate reports from
Anywhere on the Rail net.

6 Civil Engineering Management CEMIS is a MIS package for monitoring and


Information System for Indian maintaining Tracks and bridges related activity
Railways of Indian railways.It consists of various
modules like:

• Track- Track renewal, Monitoring by


Machine, Maintenance by Machine,
Accidents, Deep Screening, CRS
Enquiries, Rail Weld Fractures, USFD,
Ballast Supply Insertion Patrolling, Caution
Order and Traffic Block, MTS Engg.
Control, Inventory management.
 Bridges- Rehabilitation of distressed
bridges, Strengthening of bridge approach,
Elimination of bridge timbers, Speed
Restriction on bridges.

The system has a complete three-tier


architecture with distributed databases. Each
server is linked to different other servers
through Rail net. The key function of this
project is storing, managing & transferring the
data from server to server (placed at remote
distances) at three different levels through Rail
net using D2K Utility. The other features are
Management Information System 31

multilevel security, Encrypting and Decrypting


Data, audit trials maintenance.

7 Integrated Transaction Accounting In the initial two phases of the project, an


System for Indian Railways Integrated Transaction Accounting System
was developed & successfully implemented at
the Northern Railway Headquarters and
Seven divisions at Lucknow, Ambala, Firozpur,
Allahabad, Bikaner, Moradabad and Jodhpur.
Encouraged by the success, a further order
has been awarded by the Railway for
implementing the ITAS at Seven workshops of
the Northern Railways at- Jodhpur, Jagadhri,
Lucknow–Alambagh & Charbagh, Bikaner,
Ghaziabad, Amritsar.
The project has been completed. It is
expected that the system will be in
implemented in all the Zonal Railways.

8 Financial Accounting Package for HSCC is a PSU taking up Turnkey Projects for
Hospital Services Consultancy setting up big hospitals across the country.
Corporation The scope of the project include development
of the following modules for an integrated
financial and pay roll systems :

• Financial Accounting
• Voucher Entry System
• Day Books
• General Ledger
• Trial Balance
• Balance Sheet
• Profit & Loss Account
• Cost Center Reports
• Payroll
• Income Tax
• MIS
The system has been developed &
implemented.

9 Library Automation & Campus-wide This Campus Wide Networking of


Network at Shantiniketan, Calcutta Shantiniketan campus is implemented over 13
Kms. Diameter FDDI ring connecting 250
nodes.

10 Mahatma Phule Krishi Vidyapeeth, The network of Mahatma Phule Krishi


Management Information System 32

Rahuri Vidyapeeth at Rahuri is implemented over


Fiber Optic (2.5 Kms. Of fiber) network. All the
departments of the University are connected
to other through this network. This network is
in turn connected to zonal stations, viz. Plain
Zone, Pune; Scarcity zone, Solapur, Sub-
montane Zone, Kolhapur and Western Ghat
zone, Igatpuri network.

11 Software Technology Park, ATM backbone network is implemented at


Bangalore STPI, Bangalore. Currently 500 nodes are
connected to this network.

12 Software Technology Park, Noida At STPI, Noida CDAC is implementing ATM


backbone to provide service to its clients over
high-speed ATM network. Currently 100 nodes
are planned to get the connectivity.

13 Punjab University, Chandigarh CDAC has implemented the one of the largest
ATM installation at Punjab University,
Chandigarh. ATM is installed as the campus
backbone and the departments are connected
over Ethernet and fast Ethernet. Currently
1200 nodes are connected over ATM.

14 Raman Research institute, CDAC has implemented high-speed ATM


Bangalore backbone at RRI, Bangalore to give
connectivity to 500 nodes.

15 University of Mysore, Mysore Recently CDAC has implemented high speed


ATM backbone for computerization of Mysore
University. Currently 100 nodes are
connected. It is planned to connect 500 nodes
over all the departments in the University in
near future.

16 Human Resource Management This project has been implemented in the


System for Indian Tourism ITDC Head Quarter, Human Resource
Development Corporation (ITDC) Development division.

17 Human Resource Management HSCC is a PSU taking up Turnkey Projects for


System for Hospital Services setting up big hospitals across the country.
Consultancy Corporation The scope of the project include development
of the following modules for an integrated
Management Information System 33

HRMS System with Leave Module:


• Recruitment
• Manpower Planning
• Employee Details
• Seniority
• Probation
• Transfer and Deputation
• Increments
• Annual Confidential Reports
• Leaves
• Promotion
• Emoluments and Entitlements
• Disciplinary Details
• Property Returns
• Training
• Medical Reimbursement
• Advances
• Roster Maintenance
• MIS Reports

18 Sales & Inventory Management ITDC owns different types of shops like Duty
System (ISMS) for India Tourism Free, Tax Free, Tax Paid etc at all over India.
Development Corporation (ITDC) Most of the shops are located at
International Airports. There are some
Warehouses located in major cities to store
imported and local items sold through these
shops. Sales data would be captured from
these shops and data would be replicated at
head office periodically. The scope of the
project include development of the following
modules
• Sales
Direct sale
Item Master
Details of counters at each
location
Daily Reports
MIS / Exception Reports
• Material Management (Inventory)
Indent received from Shops
Receiving of items (capturing all
the data from custom authority)
Provision for wastage, shortage
and breakage
Stock Update
Issuing of Items
GB note
Reports
MIS
Management Information System 34

• Purchase
Analysis and approval of the
indent
Supplier Master
Quotation from the supplier
Comparison and analysis of prices
Performa invoice
Letter Of Credit for imported items
Purchase order
Bill of Entry
Report
MIS / Exception Reports

19 Loan Accounting & Management This project is being developed for the 5
Information System for Ministry of Apex corporation under the mentioned
Social Justice and Empowerment ministry namely NMDFC, NSFDC, NHFDC,
NBCFDC, NSKFDC and are involved in the
uplifting of the persons belonging to the
corresponding classes and under DPL. This
project take care of all the steps followed in
the procedures of loan like submitting
proposals, appraisal and sanctioning,
disbursements and recovery, repayment
schedule generation, recovery and utilization
appropriation etc.

4.4 History and Achievements

CDAC is India’s initiative in Advanced Computing. CDAC’s mission is to deliver state-of-art


open high performance computer in the desktop to tear flops range embodying
architecture scaleable parallel emergent industry-standard RISC processor,
interconnection networks, I/Os, network connectivity and programming; and graphics and
visualization environments. In fulfillment of this goal, CDAC has advented the Open Frame
Architecture for High-Performance Computing and Communication, which has been
realized in its celebrated PARAM 9000 series high performance computers.

The application development program covers scientific and engineering, real time and
business application and is addressed to such areas as weather forecasting,
computational fluid dynamic, heat transfer, finite element modeling, launch vehicle
dynamics simulation, seismic data processing, reservoir modeling, remote sensing,
medical imaging, computational chemistry, molecular dynamic, biotechnology and also
Management Information System 35

emerging area like parallel databases, data warehousing and mining, video-on-demand
and virtual reality. Several production quality software from independent software vendors
are being parallelized and ported on PARAM series high-performance computers. A
National PARAM Supercomputing Facility (NPSF) has been created to provide nation-wide
access to CDAC’s PARAM series supercomputers.

CDAC’s Language technology mission complements its high-performance computing and


communication initiative to create a framework for the co-existence of all the living
languages of the world with diverse scripts on standard computer allowing script
independent universal software to become a reality. CDAC has innovated its trail-blazing
Graphics and Intelligence based Script Technology (GIST). The GIST technology is being
extended to include multilingual and multimedia computing.

CDAC is continuously creating valued advanced computing technology products solution


and services for mass as well as mission-critical applications. The advanced computing
technology solutions for education and research, power, telecom, healthcare, finance,
transport and other sectors are being developed and have received wide recognition.
CDAC’s esteemed Advanced Computing Training School (ACTS) leverages CDAC’s
unique expertise and high-performance computing infrastructure to prepare intellectual
resources for the growing Information Technology industry. Coupled with its newly created
commercial arm and has formed a “Virtual Cooperation” which today represents the
Critical Mass in Advanced Computing to address the needs of the 90’s and beyond. The
most valued assets of CDAC are its 300 strong young, dynamic and committed team of
engineers and scientists managers and facilitation service providers. Its advanced
computing infrastructure for EDA and S/W development, LAN and WAN connectivity and
most importantly, its open, creativity and initiative nurturing, vibrant work culture.

The government of India launched the Center For Development Of Advanced Computing
(CDAC) in 1998 as India’s national initiative for the development of core technologies in
the area of high-performance computing. With a budget of Rs 37.5 crores spread over 3-
Years, CDAC’s first mission was to develop and deliver parallel computer with a peak
performance rating of 1000 Mega Flops. This mission was both challenging and path-
breaking, coming as it did the time negotiation on the import delivery of CRAY super
computer for weather forecasting had themselves run into rough weather. At this time
Management Information System 36

India’s development efforts at computing were characterized by high dependence in the


import of critical component, with indigenous technology being largely limited to the
assembly of 386 based PCs.

CDAC to its credits to accomplished its mission on time, within budget and despite
resource constraints, to deliver PARAM 8000, it’s associated system software and over 30
application kennels. PARAM 8000 synonymous with “The Supreme” and “Parallel
Machine” was the first of a series of parallel supercomputer developed by CDAC. CDAC
has since progressed to develop a range of modular system with varying processing
powers from tens of Mega Flops to a few Giga Flops to suit the computing requirements of
a variety of users from low budget academic institution to high compute intensive
application. A comprehensive software development environment PARAS – was made
available to the application developers. The performance of these machines is comparable
to machine of a similar class available in Europe. After completion of the first mission,
CDAC enhanced the PARAM 8000 to incorporate the latest ‘Vector Engine’ - Intel’s i860
processor. This model was known as the PARAM – 8600. over 30 PARAM 8000 and 8600
have been deployed in the field mainly for education and research in the areas of Weather
Forecasting, FD, FEM. Remote Sensing, Launch Vehicle Dynamic Simulation, Oil
Reservoir Modeling, Computational Chemistry, Molecular Dynamics and Biotechnology.
CDAC is now embarking upon the design and development of a Grand Challenge Tera
Flops Supercomputer. This will help India retain its eminent position in the select league of
Supercomputing nations. CDAC purposed its Second Mission with the following
objectives. To design, develop and deliver a general purpose, massively parallel
Supercomputer with the following features:
• Architecture with a peak performance scaleable in the Tera Flops range and
proportionate aggregate main memory and secondary storage.
• Advanced parallel programming environment covering operating systems, parallel file
systems, compilers, and parallel processing tools and libraries.
• Connectivity to standard hosts, graphics and multi-media workstations and networking
capabilities for Supercomputing environments.
• System architecture targeted at scientific and engineering, real time and business
applications.
• To demonstrate applications of the targeted Supercomputer in collaboration with the
end users/independent software vendors in select areas.
Management Information System 37

• To commercial nationally and internationally the spin-offs and complimentary products


such as the VLSI ’s accelerators, high performance computing and communication
products, parallel disk arrays, compilers and parallel processing tools, parallel libraries
and applications.

4.5 Latest Achievement

CDAC’s Terascale Supercomputing Facility (CTSF) which houses the next generation high
performance scalable supercomputing cluster - PARAM Padma, currently with a peak
computing power of one Teraflop was dedicated to the nation by Shri. Arun Shourie,
Minister for Disinvestment and Communications & Information Technology, Govt. of India,
at the CDAC Knowledge Park on April 1, 2003 on the eve of CDAC's Sixteenth Foundation
Day. The hardware environment of PARAM Padma is powered by Compute Nodes based
on the state-of-the-art Power4 RISC processors, using Copper and SOI technology, in
Symmetric Multiprocessor (SMP) configurations. The PARAM Padma is powered by
CDAC's flexible and scalable HPCC software environment. The Storage System of
PARAM Padma has been designed to provide a primary storage of 5 Terabytes scalable to
22 Terabytes. The network centric storage architecture, based on state-of-the-art Storage
Area Network (SAN) technologies, ensures high performance, scalable and reliable
storage. The Secondary backup storage subsystem is scalable from 10 Terabytes to 100
Terabytes. It implements a Hierarchical Storage Management (HSM) technology to
optimize the demand on primary storage and effectively utilize the secondary storage. The
PARAM Padma system is also accessible by users from remote locations.

4.6 Organizational Structure

CDAC has witnessed a major merger with ER&DCI, NOIDA, NCST, Mumbai and CEDTI,
Mohali, societies under the Department of Information Technology, as an effort to meet the
aggressive R&D goals while doggedly pursuing a vision centered around the people.

The current merger of DIT societies has catapulted CDAC's existing human resource from
737 to 1846. Suddenly a vast pool of highly skilled people with domain expertise covering
a wide canvas of high-end technology and applied R&D areas has come together with
Management Information System 38

working culture diversity. This intellectual property has a mandate to shape CDAC into a
premier R&D Center of excellence of international repute working in advanced electronics
and information technologies. This is a challenging but realizable call and the
management of CDAC has been mandated to carry out activities the HR due diligence and
organizational mapping, while addressing issues related to staffing, employee relations
and workforce restructuring. The integration would involve assessing the degree of cultural
and functional integration required to help the larger CDAC achieve its strategic ambitions.
CDAC has offices at Pune (HQ), Delhi, Mohali, Mumbai , Kolkata , Bangalore, Hyderabad,
Thiruvanathapuram and Chennai with employees’ strength of around 60% of these are in
technical areas of development, sales and support functions.

The Pune Centre has the National PARAM Supercomputing Facility, PARAM Hardware,
Networking, Application Development Team, Language Technology Team, Financial / Data
ware housing Team, Advanced Computing Training School Team, Defence Application
Group. The Pune Centre is the Headquarters of CDAC, with the Executive Director &
Director’s office.

The Bangalore Centre is headed by a Director with the major groups of E-Governance,
Systems Software Development (SSDG), Real Time Systems (RTSG), Business Division
(BD), Advanced Computing Training School (ACTS) and GIST Group. The Organization
chart is given in the following page.

The Noida Centre has the MIT liaison group, the Business Division and R&D and Software
Development Team.

CDAC is all set to open up an office in California, USA in near future.


Management Information System 39

5. Problem Formulation
Management Information System 40

5.1 About the Client

5.1.1 Introduction to “Patent”

In less than five decades since independence, there has been significant change in the
economic scene in the country mainly due to rapid increase in industrial and R&D
activities. By and large the industrial infrastructure has now reached a stage of
technological maturity and it is possible to set up plants based on indigenous technological
capabilities in almost all industries, with only marginal inputs of foreign assistance.
However, the quest for new technologies by Indian industries has been ever increasing in
the country with a view to become a global player in the international market. As a result
“Patent” has assumed a great importance in recent time. Since its basic function – to
promote innovation – is an essential component of economic growth and social evolution.
Patent is not just an incentive to invest in the innovation process per se, but is also
increasingly important for trade and industry worldwide. For developing and industrializing
countries in particular, patent is an essential component of the framework they need in
order to attract foreign investment and faster technology transfer.

5.1.2 Indian Patent Office

The Patent Office, under the Ministry of Commerce & Industry, Department of Industrial
Policy & Promotion, has been established to administer the various provisions of the
Patents Law relating to the grant of Patents & The Designs Law, relating to the registration
of Industrial Designs.

The Patent office and its branch offices are established to administer various provisions
relating the grant of patent and maintenance of Register of patents under the Act. The
Head Office of Patent Office is located at Calcutta and branch offices are located at
Management Information System 41

Mumbai, Delhi & Chennai. The Patent Office is under the charge of Controller General of
Patents, Designs & Trade Marks who is the Controller of Patents for the purpose of the
Act. The Central Government has power to specify for the purpose of facilitating the
registration of Patents, the establishment of Head Office and branch offices at the places it
may think fit.

5.2 System Objective

The module undertaken serves for computerization of personnel information system for
NPL, an integral part of the project named “National Physical Laboratory”.

The objective of this module is to:

• Enhance the use of technology as a cost-effective support to the NPL mission.

• Provide an infrastructure for the sharing of information and computer


applications throughout the organization.
• Support the operational, tactical and strategic information needs of NPL.

• Provide an infrastructure for sharing of information between the employees of


NPL.
• Provision for automatic calculation of retirement age, salaries, incentives will also
be available.
• Provide the provision of building various types of reports according to ones
authorization. Similarly a member will be able to build the report on his own
status. Later on if the organization finds it feasible, it can widen the scope by
combining it’s own intranet with the intranet of other organization.

The module will act as an infrastructure for sharing the information through this
application. Any employee sitting at his own seat and branch can acquire information on
personal as well as the service related details such as inquiring about the first
appointment, qualification, transfer, promotion, deputation, family member, dependents
details and so on. A member or an employee can also query about his own status, his pay
scale, increment, promotion, retirement, etc. The system being on intranet will be
accessible to everyone; hence the system also proposes to provide the security measures
Management Information System 42

of the sort where an employee is able to check or query about his own status and not of
anybody else. Master entries like assigning designation ids, grades, etc will be accessible
to only certain authorized people.

Hence, in nutshell the overall objective of this module is to provide the staff a
technologically enabled and capable system and to automate the system to the level that
minimizes human intervention and maximizes end-user satisfaction.

5.3 System Purpose

National Physical Laboratory, our client, desires a computerized system to carry out
various functions of the organization. The functions such as Administrative work, Accounts,
etc are time consuming and human intensive.

With a view to reduce the above chances of errors and providing the staff a technologically
enabled and capable system, NPL has embarked on a trail-blazing approach to automate
the above system to the level that minimizes human intervention and maximizes end-user
satisfaction.

5.4 System Context

Centre for Development of Advanced Computing, CDAC, New Delhi has undertaken the
project of providing total IT solution for NPL. It is intended to serve the requirements of the
staff members of NPL and to provide adequate and quick services to the associated
clients of NPL.

The total IT solution for NPL focuses on computerizing process of Management


Information System, Budget management, Financial Management System, Intranet Main
Page Development, Administrative Features & Work Flow Features and Library
Management System. This Project report focuses on Management Information System.
Management Information System 43

The system is envisaged as a three-tier solution to fulfill the objectives of centralized


database server, business logic and multi-location clients on Intranet and Internet. The
three-tier software architecture is a versatile, request/ response based and object oriented
infrastructure that is intended to improve usability, flexibility, interoperability, and scalability
as compared to centralized, mainframe and time sharing computing.

Fig. 3 Tier architecture of NPL project

5.5 Need Recognition

a. Accommodation

• Accommodation Section receives notification from the Directorate of Estate of any


available accommodations.
Management Information System 44

• Accommodation Section informs the employees of the concerned directorates to


obtain the form from the Directorate of Estate depending on the category of the
quarter to be applied.
• Accommodation section indicates the code on each and every form and also
prepares the abstract report to be sent to the Directorate of estates.
• The acceptance form, which is filled by the employee after getting verified by the
concerned establishment section, is sent to the accommodation section. It puts the
endorsement number and sends the form to the directorate of Estates.
• Request for change of allotted accommodation is also done by accommodation
section.

b. Leaves

• The leave balance has to be examined before sanctioning the leave.


• Leave has to be integrated with the other departments like Pay and Account office,
which will calculate the salary accordingly.
• Reports like how many people took leave within a particular period require a lot of
processing in the current system.

c. Employee Details (Personal & Service related)

• Compiling personal details about employees e.g. knowledge of a specific foreign


language, employee’s mother tongue or state of domicile is cumbersome.
• At the time of review, gathering information about the employees with membership
of Professional bodies (subject wise experts, academic qualifications) is time
consuming.
• Preparing a list of Employee of age group 50-55, due for retirement (Grade wise,
Across the board) is very time consuming.
• Difficulty in tracking employees with the longest stay as regards to the current
posting.
• Lengthy manual efforts required to time Information about the total period of ex-
Cadre assignment (Both totality and frequency) can be calculated.
• Foreign assignment period based queries can be retrieved from the database.
• Lot of efforts required in preparing Seniority list, Civil list of SC/ST officers and
officers within a particular age group.
Management Information System 45

• Keeping Track of deputation details like period of deputation, borrowing


organization, absorption date, designation and place of posting is difficult.

6. System Study
Management Information System 46

6.1 Introduction

System study is a vast field through which a system analyst puts his thoughts and
searches of the best solution to the problem. The objective of study phase is to answer the
questions: Exactly what the system? What the System must do? During the system study,
the analyst attempts to develop a complete functional understanding of the proposed
system on a document. The document identifies a number of functions or processes that
must be performed by the system. The system analyst studies these functions in detail
during the analysis phase. The study phase should include the following steps:

• Study of existing system, the basic inputs available and outputs desired.
• The splitting of the available inputs into database files to reduce redundancy and
increasing consistency.
• Give the ideas of essential fields (if any).
• Idea of implementation code etc.

Since the evolution of computers, computer based information system has greatly
increased the quality and performance of the organizations. The possibility of mistakes in
record management has lowered down to zero. By analyzing the existing system in a well
– defined manner, analyst can reduce the burden of handling a large amount of data and
can facilitate planner and decision makers in taking decision and planning in an
appropriate time.
Management Information System 47

6.2 Study of the Existing System (Manual)

The Management Information System (MIS) of NPL is presently working manually and is
proposed to be automated. The major bottlenecks faced in the manual operations of MIs
are:

• The organization has to maintain records of thousands of employees, which


becomes cumbersome
• The process of entering the details of an employee, modifying it, deleting is
repeated time and again
• A unique & consistence user classification scheme is not followed in current
system
• User authentication is a tedious job and is time consuming
• It is not easy to locate information about a particular employee on the shelves
when it is required for some purpose, as shelf arrangement is not fixed.
• The calculation of an employee’s pay scale, salary, increment, etc is done
manually
• Application for allotment of accommodation as well request for change of
accommodation has to be made manually.
• Monitoring of leaves, checking of leave balance, etc is done manually, which is a
tedious process
• Lack of updated human resources information for effective planning and decision-
making
• Serious budgetary problems as processing of resignations, appointments and
promotions takes a long time
Management Information System 48

• Lack of information leading to inaccurate resource allocations in regions, districts


and schools
• Lack of means for viewing employee’s retirement related information such as the
retirement age, amount of pension, pension status and so on
• Budget allocation on salaries made very difficult owing to lack of accurate
information
• Lack of current statistical information on human resources
• There is s no provision for the generation of various reports such as leave reports
and so on for administrative purposes as well as user’s personal awareness
• There is time delay in reporting

6.3 Study of the Proposed System (Computerized)

The aim of the proposed system is to automate the Personnel Information System
functioning where the employees at all the levels at large are facilitated maximum. Making
the system computerized would make transactions faster, more accurate, quick retrieval of
information and large storage of data. The capabilities of the proposed system are as
under:

• Maintains large data pertaining to personal as well as service related information


etc.
• Well-designed screens requiring entry of minimum possible data.
• Allows managing, both, online and manual ordering process.
• Provides interface to enter relevant data.
• Checks for duplication of data.
• Reentry of data is not required for ordering additional copies.
• Maintains employees details like their personal details, their qualification, work
experience, salary, awards, incentives, leave, resignation, termination, tour etc.
• Classifies the entire organization into different levels, different units based on
departments and designations.
• Keeps track of the joining date and the resigning date of the employees, which aids
the company in deciding the number of vacant posts.
Management Information System 49

• Provides salary details of the employees as and when required by the top-level
management of the company.
• Maintain dates of when the employees were provided appraisals.
• Helps the top-level management to decide the date of promotion of the employees
as per their performance.
• Generates important reports for top-level management about performances of the
employees
• Maintains and updates records of existing and past employees; categorizes them
on the basis of their unit, departments, designations, etc.
• Various reports of employees as desired can be generated through this application.
• Export of reports in various formats such as RTF, HTML, Excel, Lotus, Word
Document, etc.
• Emailing of generated reports from the application itself
• Menu-Driven Programs which are user friendly and easy to use
• Reduces paperwork in the organization
• Proper generation of reports in PDF format as well as HTML format.
• Error detection.
• Generating required reports as and when required.
• Query.

6.4 Feasibility Study

The feasibility study documents the analysis of a business problem, including the
determination of whether it can be solved effectively. The operational (will it work?),
economical (costs and benefits) and technical (can it be built?) aspects are part of the
study. Results of the study determine whether the solution should be implemented.
A feasibility study is conducted to select the best system that meets the performance
requirements. This entails an identification description, an evaluation of candidate
systems, and the selection of the best system for the job. Three key considerations are
involved in the feasibility analysis: economic, technical, and operational. Computerizing
Personnel operations will involve new costs that can be justified by saving one/two full-
Management Information System 50

time staff and substantially improving member service and overall performance. Also gives
exact stock verifications needed from time to time.

6.4.1 Why is this important?

Management must make a crucial decision during the early stages of an information
technology (IT) investment: whether to seek resources to support full-scale development
and implementation, or to suspend activities due to a lack of clear benefits (tangible,
intangible, or both), and/or unacceptable risks. The feasibility study offers a structured,
modular process for gathering the information needed support stakeholders in making this
crucial decision and to support decision packages submitted to the administration. The
Information Services Board (ISB) requires that feasibility studies be conducted for projects
rated as Level 3 according to the Severity and Risk Matrices.

6.4.2 Economic Feasibility


Economic analysis is most frequently used method used for evaluating the effectiveness of
a candidate system. Also known as Cost/Benefit Analysis determines whether the adoption
of a system can be cost justified. To access this system:

1) Software:
1.1) Database: Postgresql, which is readily available and is the most
commonly used database.
1.2) Operating System: Linux, which is very easily available and has great
security features along with large no. of user support.
1.3) Web Server: Apache Tomcat, which is very easy to maintain.
1.4) Client Software: J2EE which is Java Platform and again easily
available on Internet and other software markets.
2) Hardware requirements are Pentium machine with 2x36GB Hard Disk, 2GB
RAM which are quite economical for a huge Personnel system for NPL.

6.4.3 Technical Feasibility

The system is proposed to be using Java 2 Enterprise Edition (J2EE) environment, which
has great power for sophisticated, robust applications like PIS. The Java Servlet API and
Java Server Pages (JSP) bring the full power of Java to the Web server, with database
Management Information System 51

connectivity, network access, and multithreaded operations, and a different process


model. Servlets and JSP pages operate from a single instance that remains in memory
and uses multiple threads to service requests simultaneously.

The web application model previously was client-side Java in the form of applets which led
to considerable incompatibilities between browsers, lengthy downloads over slow
modems, security limitations etc. Server-side Java had grown since then as it had none of
the browser inconsistencies since browser is not required to host a Java virtual machine.
The browser only has to render HTML. JSP proved to be a successful server-side
technology and an excellent base for Web applications.

JSP pages provide the major advantages as:

1) They have better performance and scalability than CGI scripts.


2) No special client set-up is required.
3) They have built-in support for HTTP sessions, which makes application
programming possible.
4) They have full access to Java technology-network awareness, threads, and
database connectivity –without the limitations of client-side applets.
5) They are automatically recompiled when necessary.
6) Since JSP pages are HTML-like, they have greater compatibility with web
development tools.

6.4.4 Operational Feasibility

Operational feasibility determines how much effort will go into educating, selling, and
training the user staff on the proposed system.

As such the proposed system is going to make the work of PIS staff easier so the problem
of resistance to change would not arise. Instead the monotonous tasks for the day would
be automated, proper tracking of information would be there, proper stock verification can
be made, periodic overdue notices would be possible automatically, re-entry of data not
needed, duplication of data would be checked and many more such features are
incorporated which make the life of data entry operator and other PIS staff easy. Since PIS
Management Information System 52

staff of National Physical Laboratory already has the domain knowledge so effort required
for user training would be minimal.
Management Information System 53

COST BENEFIT ANALYSIS

DEVELOPMENT COST

• System Analysis & Requirement Determination

16 Days (80 Hrs. @ 200/Hr.)……………………………………Rs.16000.00

• System Design

12 Days (85 Hrs. @ 200/Hr.)……………………………………Rs.17000.00

• Development & Implementation

100 Days (500 Hrs. @ 200/Hr.)……………………………...….Rs.100000.00

Total Development Cost…………………………………....…...Rs.133000.00

PROJECTED ANNUAL OPERATING COST

• Computer, Electricity, Printer & Maintenance………...…Rs. 200000.00

SYSTEM BENEFITS

1.Tangible benefits (per year)

• Reduction in paper work……………………….…….…. Rs. 10000.00

2. Intangible benefits (per year)

• Relief from additional staff………………………………Rs.36000.00

• Increase in efficiency……………………………………Rs.10000.00

Total System Benefits…………………………………Rs.56000.00


Management Information System 54

PAYABLE ANALYSIS FOR CANDIDATE SYSTEM

Cash Flow Yr. – 0 Yr. – 1 Yr. – 2 Yr. – 3 Yr. – 4 Yr. – 5


Description (Rs.) (Rs.) (Rs.) (Rs.) (Rs.) (Rs.)
• Development Cost 133000.0

• Operating Cost
50000 75000 120000 150000 180000 200000
• Benefits derived
from the new
system 0 10000.0 80000.0 200000 230000 260000
Net Cost
(Cost – Benefits) 183000.0 65000 40000.0 50000 50000 60000.0

200000 1.83

100000
0.65
0.60
0.50 0.50
50000
0.40

PAYBACK PERIOD OCCURS FROM THE 1st YEAR ITSELF AFTER THE SYSTEM
BEGINS OPERATING.

COST ESTIMATION
1. Function point estimation

Predefined data used for estimation: -

Measurement Count Simple Average Complex


parameter weighting weighting weighting factor
factor factor
No. of inputs 3 4 6
No. of outputs 4 5 7
No. of inquiries 3 4 6
Management Information System 55

No. of files 7 10 15
No, of external 5 7 10
interface

Environmental Complexity: -

0 1 2 3 4 5

Influence Incidental Moderately Average Significant Essential


effective
Functional Point Estimation for the system
(On the basis of weighting factors predefined)

Measurement Opt. Likely Pess Estm. Simple Avg Complex FP


Parameter count
No. of user 20 30 40 30 4 120
inputs
No. of user 12 15 20 11 7 77
outputs
No. of inquiries 13 16 21 12 3 36
No. of files 10 15 20 18 15 270
No. of external 0 1 2 2 5 10
files.
TOTAL COUNT 513

OTHER 14 CHARACTERISTICS EVALUATION


(On the basis of environmental complexity predefined)

1. Backup and recovery 4


2. Data communication 3
3. Distributed processing 3
4. Performance critical 4
5. Existing operation environment 3
6. Online data entry 4
7. Input transaction over multiple screen 0
8. Master files updated online 5
9. Information domain values 2
10. Internal processing complex 4
Management Information System 56

11. Code designed for reuse 4


12. Conversion/ installation in design 2
13. Multiple installation 5
14. Application designed for change 5
51

FP (estimated)
=513*[(0.65+0.01*51)]
=513*(0.06+0.51)
=513*(1.16)
=595.

2. COCOMO (COnstructive COst MOdel)

Predefined data used for estimation of effort through


INTERMEDIATE COCOMO: -

Software project a b
Organic 3.2 1.05
Semi – detached 3.0 1.12
Embedded 2.8 1.20

Effort Adjustment Factor.

Very low Low Nominal High Very high


0.75 0.88 1.00 1.15 1.40

Initial Effort (E)=aKLOC

Effort is estimated on the basis of Intermediate COCOMO model and is semi-detached


type software.
Where a=3.0, b=1.12
On an avg. there are 1000 LOC per file and there are 100-200 files.

Therefore on avg. KLOC=150

Initial effort
1.12
E=3.0(150)
=4.72
Management Information System 57

EFFORT ADJUSTMENT FACTOR (EAF)


(On the basis of predefined EAF)

1. Product Attribute

• Required reliability 1.15


• Database size 0.88
• Product complexity 1.00

2. Computer attributes

• Execution time constraint 0.88


• Main storage constraint 0.75
• Virtual machine volatility 0.75
• Computer turnaround time 0.75

3. Personnel attributes

• Analyst capability 1.15


• Application experience 1.00
• Programmer capability 1.15
• Virtual machine experience 0.88
• Program language 0.88

4. Project attributes

• Modern programming practices 1.15


• Use of software tools 1.15
• Development schedule 1.00

14.47

EAF = 14.47/14 = 1.033

Final effort = E * EAF


= 4.72*1.033
= 4.88 = 5 person months
Management Information System 58

7. System Planning
Management Information System 59

7.1 Project Plan

The plan will be prepared and released after review. Once released the plan will be base-
lined. Any changes to the plan will follow change management procedure. This plan is
updated on regular basis whenever there is any:
• Change in the process.
• Change based on review.
• Change based on any rescheduling activities like change in schedule, effort, change in
deliverables due to customer request, actions initiated to bring the project under the
quantitative goals specified etc.

The change to Project Management Plan (PMP) will be authorized by the Project Leader /
Project Manager. PM will authorize the release of PMP. These changes will also be
disseminated to all the team members during periodical team meetings.

7.2 Project Methodology

The project follows the organization standard life cycle model :

1. Conduct system study through Functional Specifications and meetings with the client.
2. Arrive at Architecture and Database Design.
3. Code the programs and do a unit testing.
4. Conduct System Testing.
5. Conduct final inspection and release the product to the user.
6. Conduct User Training.
7. Conduct Acceptance Testing.
8. Get User Sign-Off.
Management Information System 60

7.3 Team Structure

S.No. Name Role Responsibility


1 Paras Nath Project Manager - Interaction with client.
Barwal - Supervision of project.
- Ensuring the timely of availability
of the resources for smooth
functioning of project.
2 Ashu Krishna Project Leader - Ensuring timely completion of
work, ensuring availability of
resources.
- Making plan along with the PM,
tracking the plan, coding etc.
3 Gopal Krishna Project Trainee - Design, Coding, testing,
documentation & implementation.
- Looking after the day to day
working of the entire PIS.

7.4 Quality Assurance Plans

The Software Quality Assurance Plans (SQAP) specifies the tasks that need to be
undertaken at different times in the life cycle to improve the system quality and
how they are to be managed.

The project is to adhere to SEI – CMMI level 5 – quality capability model


throughout its life cycle. For the same following procedures are being followed :

• Timesheet Maintenance: Each team member is supposed to log all the details
for the weekly activities at the end of the week and the collated data is also
being maintained by means of an excel sheet which gives an idea about the
actual hours spent in each of the activities within the project.
• Schedule Plan: In order to complete the project within the time limit proposed, a
schedule plan is being maintained as per which all individual activities are being
assigned to each of the team members. Ideally, Timesheet activities must
match with the scheduled activities.
Management Information System 61

• Screen Estimation: A separate word document along with an excel sheet is


being maintained to calculate the actual effort for each module and these
calculations have been made after function point analysis has been done.
• Functional Specifications Document : The FS for the project is client specific. It
has been prepared and maintained by the client.
• SCM Plan : Software Configuration Management Plan is maintained which
identifies the configurable items along with other relevant information pertaining
to them.
• Quality Assurance Plan : This plan defines the quality processes being followed
and quality measures to implement these processes. It is carried on by
conducting Verification and Validation at various phases of the life cycle and
through inspections and reviews at regular intervals.

7.5 Project Monitoring System

For monitoring the progress of the system the activity chart used is shown below:
The project starts with the preliminary study of the PIS which involves looking into
the functions of all the employee related activities. Once this is done System
Requirement Study is conducted and the details of each sub process or sub
module is collected and all the formats used and referred are also taken into
consideration. A model, which incorporates the interaction between various sub
processes of PIS, is prepared. Database design, which includes Tables, Data
Dictionary, is finalized along with the architecture of the system, which includes
ERD, DFD (Context Level and Fist Level) and screen shots. Once the architecture
and database is frozen coding for the application starts. After all the functionality
has been coded the application developed is tested with includes unit testing and
integration testing. Application is tested thoroughly before implementation starts.
Application is implemented and any changes required are incorporated.

PERT CHART

ACTIVITY DESCRIPTION DURATION PREDECESSOR


(days)
A Planning of the functionality. 6 --------
B Defining and understanding the 15 --------
problem.
C Analyzing hardware requirements. 5 B
Management Information System 62

D Analyzing software requirements 5 B


E Deciding upon the platform to be 2 B
used
F Analyzing alternative for decided 2 E
platform
G Analyzing alternative for decided 1 D
software.
H Analyzing alternative for hardware. 1 C
I Technical feasibility 2 F, G, H
J Operational feasibility 2 F, G, H
K Economical feasibility 2 F, G, H
L System design 20 I
M System development. 90 L
N Testing 5 M
O Implementation 30 N
Management Information System 63

CHART

A-6
2
1
4
C-5 H-1
0
B-15

D-5 5 G-1
3

F-2
E-2 6 I-2 7 K-2

J-1

9
L-20 10 8

0 0
0
-30

M-90 N
-5
14
12 13
11

CRITICAL PATH------1-2-3-6-7-10-11-12-13-14 (157 days)


&
1-2-3-6-7-8-9-10-11-12-13-14 (157 days)
Management Information System 64

GANTT CHART

TASKS

150

Implementation

User Manual 35

Testing
50

Coding
300

Database design
50

Analysis &
feasibility study 80

100 200 300 400 500 600 700

No of hours No of hours
Management Information System 65

7.6 Risk Management Plan

Risk Item Probabilit Impact Risk Mitigation Approach


y Exposure
Non-availability of .6 .7 4.2 - Training has been
Skilled Human provided at the beginning
Resources by STG for Java, JSP
and Microsoft for MS-
SQL Server .
Lack of Hardware .4 .7 2.8 - NPL has been asked to
Resources procure some of the H/W
like Bar Code Printer and
Scanner.
Staff Turnover .45 .8 3.6 - Every module is looked
after by minimum 2
members so that in case
a person leaves the other
person is aware about the
processes.
Unknown Technology .6 .6 3.6 - Training has been
provided at the beginning
by STG for Java, JSP
and Microsoft for MS-
SQL Server.
Frequently changing .7 .9 6.3 - Change requisition
User Requirements forms are given to the
users so that at later
stage the user can be
informed the cost impact
of the same.
Management Information System 66

8. System Analysis

8.1 Process Flow Analysis

8.1.1 Accommodation
a. Work Flow

 Put the circular about the accommodation availability from


Directorate of estates online for various directorates to refer.
 Allowing provision for online application of the quarters for the
employees.
 Provision for online change request of the quarters for the
employees.
 Generating statistical reports indicating the quarter requests for each
quarter category in a given time period.
Management Information System 67

 Putting online information for the employees who have been allotted
an accommodation and who have accepted the same.
 Putting online information for the employees who have requested a
change in the accommodation.
b. Data Flow Diagram

Accomodation
Request Personnel
Quarter
Allotment
Employee Information Details
Finance
System

Accommodation Module Context Level Diagram

DFD Level 1 Accommodation

c. Entity Relationship Diagram


Management Information System 68

8.1.2 Leaves
a. Work Flow

 Sending online request for Leave.


 Online sanctioning of the leave by the controlling officer.
 Sending the leave application to the concerned Establishment
section for issuing the sanction.
 Updating the leave account as per the sanction order.
 Cancellation/Additions to the previous leave request.
Management Information System 69

 Submitting an online departure report to the controlling officer before


going on leave and likewise submitting an online arrival report to the
controlling officer.

b. Data Flow Diagram

Leave
Personnel
Request Sanction
Employee Information Order
Employee
System

Leave Module Context Level Diagram

DFD Level 1 Leave


Management Information System 70

c. Entity Relationship Diagram


Management Information System 71

8.1.3 Employee Details (Personal & Service related)


a. Work Flow
• Storing employee’s Employment summary details.
• Storing personal details about employees e.g. knowledge of a specific
foreign language, employee’s mother tongue or state of domicile, retirement
date etc.
• Storing qualification and specialization related details of the employee like
membership of Professional bodies (subject wise experts, academic
qualifications).
• Storing employees Posting details.
• Storing ex-Cadre, foreign assignment details of employees.
• Storing deputation details like period of deputation, borrowing organization,
absorption date, designation and place of posting.
• Storing employee promotion / increment due dates.
• Provision for searching of Employee details.

b. Data Flow Diagram

Details
Personnel
Utilized
Employee Information
Authorized
System Users/
Directorate
s

Employee Details Module Context Level Diagram


Management Information System 72

DFD Level 1 Employee Details

c. Entity Relationship Diagram


Management Information System 73
Management Information System 74

9. System Design
Management Information System 75

9.1 Table Structures

MASTERS

1.MAS_TAB_DESIGNATION
Primary Key: DESIGNATION_NAME

COLUMN NAME DATA TYPE NULLABLE DESCRIPTION


DESIGNATION_NAME VARCHAR2(150) N designation name
OBSOLETE CHAR(1) Y
OBSOLETE_DATE DATE Y date at which data is
deleted
LEVELOFPARTICIPATION NUMBER(10) Y
DESIGID NUMBER(19) N desig id

2.MAS_TAB_STATION
Primary Key: STATION_NAME

COLUMN NAME DATA TYPE NULLABLE DESCRIPTION


STATION_ID NUMBER(10) N Station id
STATION_NAME VARCHAR2(100) N Station name
OBS_DATE DATE Y Obsolete date

3.MAS_TAB_CONFIG
Primary Key: KEYWORD,K_VALUE

COLUMN NAME DATA TYPE NULLABLE DESCRIPTION


KEYWORD VARCHAR2(70) N Keyword
K_VALUE VARCHAR2(200) N Value corresponding to the
keyword
SEQ_NUM NUMBER Y Sequence number
OBS_DATE DATE Y Obsolete date

4.MAS_TAB_COMMUTATION_PENSION
Primary Key: AGE_NEXT_BDAY

COLUMN NAME DATA TYPE NULLABLE DESCRIPTION


AGE_NEXT_BDAY NUMBER(10) N Age next birthday
COMMUTATION_VALUE VARCHAR2(5) N Commutation value

5.MAS_TAB_HOLIDAY
Primary Key: HOLIDAY_DAY, HOLIDAY_DATE

COLUMN NAME DATA TYPE NULLABLE DESCRIPTION


Management Information System 76

SEQUENCE NUMBER(10) N Sequence number


HOLIDAY_DAY CHAR(10) N Day
HOLIDAY_DATE DATE N Date
OCCASSION CHAR(50) N Occasion
DELDATE DATE Y Obsolete date
STATUS CHAR(1) Y

6.MAS_TAB_PAYLEVELS
Primary Key: PAYFIXATION_SEQ

COLUMN NAME DATA TYPE NULLABLE DESCRIPTION


PAYFIXATION_SEQ NUMBER(10) N Sequence number
INCREMENT_LEVELS NUMBER(10) N Number of slabs in a
payscale
PAY_ID VARCHAR2(10) N Pay id

7.MAS_TAB_PAYFIXATION
Primary Key: PAY_SEQ, LEVEL_SEQ
Foreign Key: PAY_SEQ references MAS_TAB_PAYLEVELS (PAYFIXATION_SEQ)

COLUMN NAME DATA TYPE NULLABLE DESCRIPTION


PAY_SEQ NUMBER(10) N Pay seq referring
payfixation_seq in
mas_tab_paylevels
LEVEL_SEQ NUMBER(10) N Sequence number of
each level in
corresponding pay scale
F_BASIC_PAY NUMBER(10) N Starting pay of the
payscale
INCREMENT_LEVEL NUMBER(10) N Increment amount
E_BASIC_PAY NUMBER(10) N Ending pay of the
payscale

8.MAS_TAB_GRADE
Primary Key: GRADE_NAME

COLUMN DATA TYPE NULLABLE DESCRIPTION


NAME
GRADE_ID VARCHAR2(50) N Grade id
GRADE_NAME VARCHAR2(50) N Grade name
OBS_DATE DATE Y Obsolete date
ENTER_BY VARCHAR2(50) Y Enter by whom
ENTER_DATE DATE Y Data entered on which date
Management Information System 77

9.MAS_TAB_INDIAN_STATES
Primary Key: STATE_NAME

COLUMN NAME DATA TYPE NULLABLE DESCRIPTION


STATE_ID NUMBER N State id
STATE_NAME VARCHAR2(100) N State name
OBS_DATE DATE Y Obsolete date

EMPLOYEE PERSONAL DETAILS


10.TBL_EMPLOYEE_DETAILS
Primary Key: EMPLOYEE_NUMBER

COLUMN NAME DATA TYPE NULLABLE DESCRIPTION


EMPLOYEE_NUMBER VARCHAR2(20) N Employee id
FIRST_NAME VARCHAR2(64) N First name
MIDDLE_NAME VARCHAR2(64) Y Middle name
LAST_NAME VARCHAR2(64) Y Last name
SEX CHAR(1) N Gender
MARITAL_STATUS CHAR(1) N Marital status
FATHER_NAME VARCHAR2(128) N Father name
RES_LOCALITY VARCHAR2(50) Y Residing locality
RES_STREET VARCHAR2(50) Y Residing street
RES_CITY VARCHAR2(50) N Residing city
RES_DIST VARCHAR2(50) Y Residing district
RES_PINCODE NUMBER(18) N Residing pin code
RES_STATE VARCHAR2(50) N Residing state
OFFICE_NUMBER VARCHAR2(100) Y Office telephone
number
BIRTH_DATE DATE N Date of birth
BIRTH_PLACE VARCHAR2(50) Y Birth place
HOMETOWN_DECLARE CHAR(1) Y Flag corresponding to
home town declaration
HOME_TOWN VARCHAR2(64) Y Home town
HOME_DISTRICT VARCHAR2(64) Y Home town district
PERM_LOCALITY VARCHAR2(50) Y Permanent address
locality
PERM_STREET VARCHAR2(50) Y Permanent address
street
PERM_CITY VARCHAR2(50) N Permanent address
city
PERM_DIST VARCHAR2(50) Y Permanent address
district
Management Information System 78

PERM_PINCODE NUMBER(18) Y Permanent address pin


code
PERM_STATE VARCHAR2(50) Y Permanent address
state
NATIONALITY VARCHAR2(64) N Nationality
RELIGION VARCHAR2(64) N Religion
MOTHER_TONGUE VARCHAR2(64) N Mother tongue
SC_ST_OBC VARCHAR2(32) N Category
DATE_RETIREMENT DATE N Retirement date
PAN_NO VARCHAR2(32) Y Pan number
OBS_DATE DATE Y Obsolete date
REMARKS VARCHAR2(2000) Y Remarks if any
STATUS VARCHAR2(50) Y Whether transferred,
promoted, appointed,
deputed
PERMANENT_TEMPORA CHAR(1) Y Flag
RY
DESIGNATION VARCHAR2(100) Y Current designation
DIRECTORATE NUMBER(10) Y Current office id
LANGUAGES_KNOWN VARCHAR2(100) Languages known
FOREIGN_LANGUAGES VARCHAR2(100) Y
_KNOWN
MOBILE_NUMBER VARCHAR2(50) Y Mobile number
CURRENT_BASIC FLOAT Y Current basic pay
BASIC_EFF_DATE DATE Y Effective date of
current basic pay
CURRENT_PAYSCALE VARCHAR2(32) Y Current payscale
PAYSCALE_EFF_DATE DATE Y Effective date of
current payscale
GRADE VARCHAR2(32) Y Current grade
#CURRENT_OFFICE VARCHAR2(200) Y Current office
POSTING_STATION VARCHAR2(50) Y Current posting station
SOURCE_OF_SALARY VARCHAR2(50) Y
POSTING_STATION_DAT DATE Y Effective date of
E current posting station
GRADE_DATE DATE Y Effective date of
current grade
DIRECTORATE_DATE DATE Y Effective date of
current office
DESIGNATION_DATE DATE Y Effective date of
current designation
STATUS_DATE DATE Y Effective date of
current sttaus
ACCOUNTNUMBER VARCHAR2(30) Y Bank account number
GROUP_INSURANCE CHAR(1) Y
Management Information System 79

YEAR_OF_SUBSCRIPTI NUMBER(10) Y
ON
BLOOD_GROUP VARCHAR2(3) Y Blood group
EMAIL_ID VARCHAR2(30) Y Email id
RESIDENCE_NUMBER VARCHAR2(30) Y Telephone number of
residence
HOME_STATE VARCHAR2(30) Y Home town state
PHYSICALLY_HANDICAP CHAR(10) Y Whether physically
PED handicapped
FATHER_OCCUPATION VARCHAR2(120) Y Occupation of father
FAMILY_INCOME FLOAT Y Family income
SERVICE_AT_JOINING VARCHAR2(30) Y Designation when
joined the service
ALLOTMENT_YEAR NUMBER(10) Y
SPOUSE_NAME VARCHAR2(30) Y Spouse name
SPOUSE_NATIONALITY VARCHAR2(30) Y Spouse nationality
ROSTER_POINT VARCHAR2(50) Y Roster number
TYPE_DETAILS VARCHAR2(50) Y Typing details
SHORTHAND_DETAILS VARCHAR2(50) Y Shorthand details
*PRESENT_STATUS VARCHAR2(50) Y
RECRUIT VARCHAR2(20) Y Whether recrited direct
or promotee
MOTHER_NAME VARCHAR2(100) Y Mother;s name
I_MARK VARCHAR2(50) Y Identifying mark
ENTER_BY VARCHAR2(100) Y Data Enter by whom
ENTER_DATE DATE Y Date at which entered
RES_HNO VARCHAR2(20) Y Residing house
number
WEIGHT FLOAT Y Weight
HEIGHT VARCHAR2(5) Y Height
PERM_HNO VARCHAR2(15) Y Permanent address
house number

DATE_NEXT_INCREMEN DATE Y Date of next increment


T

11.TBL_FAMILY_DETAILS
Primary Key: EMPLOYEE_NUMBER references TBL_EMPLOYEE_DETAILS
(EMPLOYEE_NUMBER)

COLUMN NAME DATA TYPE NULLABLE DESCRIPTION


EMPLOYEE_NUMBER VARCHAR2(20) N Employee number
MEMBER_SEQ NUMBER(10) N Sequence number
MEMBER_NAME VARCHAR2(64) Y Name of the family
member
Management Information System 80

RELATION VARCHAR2(64) Y Relation with the


employee
BIRTH_DATE DATE Y Member’s Date of birth
PROFESSION VARCHAR2(64) Y Member’s Profession
REMARKS VARCHAR2(128) Y remarks
MEMBER_MARRIED CHAR(1) Y Whether member
married
*DEPENDENT CHAR(1) Y Whether member
dependent on you
OBS_DATE DATE Y Obsolete date
ENTER_BY VARCHAR2(100) Y Entered by whom
ENTER_DATE DATE Y Data entered on which
date
MEMBER_MARRIED CHAR(1) Y Whether member is
married or not

12.TBL_DEPENDENT_DETAILS
Primary Key: EMPLOYEE_NUMBER references
Tbl_employee_details(employee_number)

COLUMN NAME DATA TYPE NULLABLE DESCRIPTION


EMPLOYEE_NUMBER VARCHAR2(20) N Employee id
MEMBER_SEQ NUMBER(10) N Sequence number
MEMBER_NAME VARCHAR2(64) Y Name of the dependent
RELATION VARCHAR2(64) Y Relation to the
employee
BIRTH_DATE DATE Y Date of birth
PROFESSION VARCHAR2(64) Y Profession
REMARKS VARCHAR2(128) Y Remarks
MEMBER_MARRIED CHAR(10) Y Whether dependent
married or not
OBS_DATE DATE Y Obsolete date
ENTER_BY VARCHAR2(100) Y Data entered by whom

13.TBL_MEMBER_DETAILS
Primary Key: EMPLOYEE_NUMBER refrences
Tbl_employee_details(employee_number)

COLUMN NAME DATA TYPE NULLABLE DESCRIPTION


EMPLOYEE_NUMBER VARCHAR2(20) N Employee id
MEMBERSHIP_SEQ NUMBER(10) N Sequence of
membership to the
professional body
PROF_BODY VARCHAR2(128) Y Name of the
Management Information System 81

professional body
MEMBER_NO VARCHAR2(64) Y Membership number
SUBJECT VARCHAR2(128) Y Subject on which
professional body
works
REMARKS VARCHAR2(256) Y Remarks
OBS_DATE DATE Y Obsolete date
ENTER_BY VARCHAR2(100) Y Enter by

14.TBL_NOMINEE_DETAILS
Primary Key: EMPLOYEE_NUMBER refrences
Tbl_employee_details(employee_number)

COLUMN NAME DATA TYPE NULLABLE DESCRIPTION


EMPLOYEE_NUMBER VARCHAR2(20) N Employee number
NOMINEE_SEQ NUMBER(10) N Sequence number
NOMINEE_FOR VARCHAR2(32) Y Nomination for i.e
gpf,pension etc
NOMINEE_NAME VARCHAR2(32) Y Nominee name
NOMINEE_FRACTION VARCHAR2(32) Y Fraction
corresponding to
nominee
NOMINEE_RELATIONSHIP VARCHAR2(32) Y Relationship with
the nominee
NOMINEE_REMARKS VARCHAR2(32) Y Remarks
OBS_DATE DATE Y Obsolete date
ENTER_BY VARCHAR2(100) Y Data Enter by
whom

15.TBL_QUALIFICATION_DETAILS
Primary Key: EMPLOYEE_NUMBER refrences
Tbl_employee_details (employee_number)

COLUMN NAME DATA TYPE NULLABLE DESCRIPTION


EMPLOYEE_NUMBER VARCHAR2(20) N Employee id
QUALIFICATION_SEQ NUMBER(10) N Sequence number
QUALIFICATION VARCHAR2(64) Y Qualification
PASSING_YEAR NUMBER(10) Y Year of passing
STATUS VARCHAR2(64) Y Degree/diploma/certifi
cate course
GRADE VARCHAR2(32) Y %/grade acquired
INSTITUTE_NAME VARCHAR2(64) Y Name of the institute
BOARD_UNIVERSITY VARCHAR2(64) Y University/board
DISCIPLINE VARCHAR2(64) Y Discipline
OBS_DATE DATE Y Obsolete date
Management Information System 82

ENTER_BY VARCHAR2(100) Y Data entered by


whom

EMPLOYEE SERVICE DETAILS

16. TBL_FIRST_ORDER
Primary Key: EMPLOYEE_NUMBER
Foreign Key: EMPLOYEE_NUMBER references
TBL_EMPLOYEE_DETAILS(EMPLOYEE_NUMBER)

COLUMN NAME DATA TYPE NULLABLE DESCRIPTION


EMPLOYEE_NUMBER VARCHAR2(20) N Employee id
ORDER_NUMBER VARCHAR2(32) Y Order number
ORDER_DATE DATE N Date of issuing of order
APPROVING_AUTHORITY VARCHAR2(200) Y Approving authority
RECRUITMENT_MODE VARCHAR2(200) N Mode of recruitment
CESE VARCHAR2(50) Y Whether recruited
through CESE /interview/
examination
CESE_YEAR Varchar2(50) Y Year/batch/rank
DESIGNATION VARCHAR2(200) N Designation
TEMPORARY_PERMANENT VARCHAR2(50) N Flag
APP_AGAINST_RESERVATION CHAR(1) N Whether appointed
against reservation
JOINING_DATE DATE N Date of joining
JOINING_BEFORE_NOON CHAR(1) N Whether joined before
noon or after noon
#OFFICE_NAME VARCHAR2(200) Y
DIRECTORATE NUMBER(10) Y Office id
PER_ORDER_NO VARCHAR2(32) Y Order number
corresponding to
permanency
PER_ORDER_DATE DATE Y Order date
PER_ISSUING_AUTHORITY VARCHAR2(200) Y issuing authority
PER_EFFECTIVE_DATE DATE Y Effective date
PER_REMARKS VARCHAR2(2000) Y Remarks
OBS_DATE DATE Y Obsolete date
POSTING_STATION VARCHAR2(400) Y Posting station
@NON_PLAN VARCHAR2(20) Y Under plan project or
non plan project
PER_CONFIRM_POST VARCHAR2(100) Y Post at which
permanency is confirmed
GRADE VARCHAR2(50) Y Grade
RELIEVING_PRESENT_DATE DATE Y Relieving date of this
Management Information System 83

office

17. TBL_PAYFIXATION_DETAILS
Primary Key: EMPLOYEE_NUMBER, PAYFIXATION_SEQNO
Foreign Key: EMPLOYEE_NUMBER references TBL_EMPLOYEE_DETAILS

COLUMN NAME DATA TYPE NULLABLE DESCRIPTION


EMPLOYEE_NUMBER VARCHAR2(20) N Employee number
PAYFIXATION_SEQNO NUMBER(10) N Sequence number
ORDER_NUMBER VARCHAR2(32) Y Order number
ORDER_DATE DATE Y Order date
EFFECTIVE_DATE DATE N Effective date
NEW_PAYSCALE VARCHAR2(32) N New payscale
NEW_BASIC FLOAT(126) N New basic
corresponding to the
payscale
DATE_OF_FIXATION DATE Y
PAY_THEREON FLOAT(126) Y
AUTHORITY VARCHAR2(32) Y
REMARKS CHAR(2000) Y
PAY_FIXATION_DETAILS VARCHAR2(100) Y Reason behind
payfixation
OBS_DATE DATE Y Obsolete date
RETROSPECTION_DATE DATE Y
ENTER_BY VARCHAR2(100) Y Data entered by
whom
ENTER_DATE DATE Y Date at which data is
entered
PERSONAL_PAY VARCHAR2(50) Y Personal pay if any

18.TBL_INCREMENT_DETAILS
Primary Key: EMPLOYEE_NUMBER, INCREMENT_SEQUENCE_NO
Foreign Key: EMPLOYEE_NUMBER references TBL_EMPLOYEE_DETAILS

COLUMN NAME DATA TYPE NULLABLE DESCRIPTION


EMPLOYEE_NUMBER VARCHAR2(20) N EMPLOYEE ID
INCREMENT_SEQUENCE_NO NUMBER(10) N Sequence number
INCREMENT_TYPE VARCHAR2(64) N Reason bhind
increment
NEW_BASIC FLOAT(126) N New basic
CURRENT_SCALE VARCHAR2(32) N Current payscale in
which increment is
given
EFFECTIVE_DATE DATE N Effective date of
increment
Management Information System 84

REMARKS VARCHAR2(2000) Y Remarks if any


OBS_DATE DATE Y Obsolete date

19. TBL_TRANSFER_PROMOTION
Primary Key: EMPLOYEE_NUMBER, TRANSFER_PROMOTION_SEQ
Foreign Key: EMPLOYEE_NUMBER references TBL_EMPLOYEE_DETAILS

COLUMN NAME DATA TYPE NULLABLE DESCRIPTION


EMPLOYEE_NUMBER VARCHAR2(20) N EMPLOYEE ID
TRANSFER_PROMOTION_SEQ NUMBER(10) N Sequence
number
ORDER_NUMBER VARCHAR2(12) Y Order number
ORDER_DATE DATE Y Order date
TRANSFER CHAR(1) Y Whether
transferred
PROMOTION CHAR(1) Y Whether
promoted
OLD_OFFICE_LOCATION VARCHAR2(400) N Old office location
NEW_OFFICE_LOCATION VARCHAR2(400) N New office
location
ACCEPTED CHAR(1) N Whether
transfer/promotion
accepted by the
employee
RELIEVING_DATE DATE N Relieving date
JOINING_DATE DATE N Joining date
JOINING_NOON CHAR(1) N Whether Joined
before noon
NEW_DESIGNATION VARCHAR2(100) N New designation
NEW_DIRECTORATE NUMBER(10) N New office
NEW_GRADE VARCHAR2(100 N New grade
REPORTING_OFFICER_DESIGNATION VARCHAR2(100) Y
REMARKS VARCHAR2(2000) Y Remarks
ISSUING_AUTHORITY VARCHARs2(200) Y Issuing authority
OBS_DATE DATE Y Obsolete date
PUBLIC_INTEREST CHAR(10) Y Whether
transfer/promotion
took place in
public interest
OWN_INTEREST CHAR(10) Y Whether
transfer/promotion
took place in self
interest
NEW_PAYSCALE VARCHAR2(50) Y New payscale
#OLD_OFFICE VARCHAR2(50) Y
Management Information System 85

#NEW_OFFICE VARCHAR2(50) Y
RELIEVING_PRESENT_DATE DATE Y Date on which
employee relieved
from the present
office
NON_PLAN VARCHAR2(10) Y Whether in plan
project or nonplan

20. TBL_DEPUTATION_DETAILS
Primary Key: EMPLOYEE_NUMBER, DEPUTATION_SEQNO
Foreign Key: EMPLOYEE_NUMBER references TBL_EMPLOYEE_DETAILS

COLUMN NAME DATA TYPE NULLABLE DESCRIPTION


EMPLOYEE_NUMBER VARCHAR2(20) N EMPLOYEE ID
DEPUTATION_SEQNO NUMBER(10) N Sequence
number
DEPUTATION_IN_OUT CHAR(3) N Deputed in or
out
FOREIGN_ASSIGNMENT CHAR(1) N Whether
deputed on
foreign
assignment
SOURCE_OF_SALARY VARCHAR2(200) Y Source of salary
PREV_ORGANIZATION_NAME VARCHAR2(200) N Present
organization
PREV_OFFICE VARCHAR2(100) Y Present office id
PREV_POSTING_PLACE VARCHAR2(200) N Present posting
station
PREV_GRADE VARCHAR2(20) N Present grade in
the office
PREV_POST VARCHAR2(200) N Present
designation
PREV_PAY FLOAT(126) Y Present basic
pay
PREV_SCALE VARCHAR2(32) N Present
payscale
RELIEVING_DATE DATE N Relieving date of
present office
RELIEVING_BEFORE_NOON CHAR(1) Y Whether
Relieved before
noon
NEW_ORGANIZATION VARCHAR2(200) N New
Management Information System 86

organization
NEW_PLACE VARCHAR2(200) N New posting
station
NEW_GRADE VARCHAR2(20) N New grade
NEW_POST VARCHAR2(200) N New designation
NEW_PAY FLOAT(126) N New basic pay
JOINING_DATE DATE N Joining date of
new office
JOINING_BEFORE_NOON CHAR(1) Y Whether joined
before noon.
ORDER_NUMBER VARCHAR2(32) Y Order number
ORDER_DATE DATE Y Order date
ISSUING_AUTHORITY VARCHAR2(200) Y Issuing authority
OBS_DATE DATE Y Obsolete date
NEW_SCALE VARCHAR2(32) New payscale
RESIDING_ADDRESS VARCHAR2(2000) Y
RELIEVING_PRESENT_DATE DATE Y Relieving date of
new office
ENTER_BY VARCHAR2(100) Y Data entered by
whom
ENTER_DATE DATE Y Date on which
data is entered

21.TBL_SUSPENSION_RESUMPTION
Primary Key: EMPLOYEE_NUMBER

COLUMN NAME DATA TYPE NULLABLE DESCRIPTION


EMPLOYEE_NUMBER VARCHAR2(20) N Employee Number
ORDER_SEQNO NUMBER(10) Y Sequence number
ORDER_DATE DATE N Order date
ISSUING_AUTHORITY VARCHAR2(50) Y Issuing authority
EFFECTIVE_DATE DATE N Effective date
ORDER_DETAILS VARCHAR2(2000) N Reason behind
suspension/resumpti
on
REMARKS VARCHAR2(2000) Y Remarks if any
SUSPENSION_RESUMPTION CHAR(1) N Whether suspended
or resumed
OBS_DATE DATE N Obsolete date
ORDER_NUMBER VARCHAR2(32) N Order number
PENALTY FLOAT(126) N Penalty

LEAVES
Management Information System 87

21.TBL_LEAVE_DETAILS
Primary Key: EMPLOYEE_NUMBER , LEAVE_SEQ_NO
Foreign Key: TYPE_OF_LEAVE references TBL_LEAVE_MASTER

COLUMN NAME DATA TYPE NULLABLE DESCRIPTION


EMPLOYEE_NUMBER VARCHAR2(20) N Employee number
APP_SEQ_NO NUMBER(10) N Application sequence
number
LEAVE_SEQ_NO NUMBER(10) N Leave seq number in
particular appl seq
TYPE_OF_LEAVE VARCHAR2(10) N Nature of leave taken
FROM_DATE DATE N From date
TO_DATE DATE N To date
INDIV_TOT NUMBER(10) N Total no of days
corres to a particular
leave type
REASON_FOR_LEAVE VARCHAR2(100) N Reason for leave
MED_ATTACH CHAR(10) Y Whether medical
certificate attached or
not
FROM_DATE_FN CHAR(10) Y Whether leave taken
from after noon or
before noon
CONT CHAR(10) Y Whether approved by
controlling officer
SANCT CHAR(10) Y Whether particular
leave approved by
sanctioning authority
TO_DATE_FN CHAR(10) Y Whether joined after
noon or before noon
ADDRESS_ON_LEAVE VARCHAR2(100) N Address during leave
PREFIX_DATES VARCHAR2(50) Y Dates prefixed to the
leave taken which
are holidays
SUFFIX_DATES VARCHAR2(50) Y Dates suffixed to the
leave taken which
are holidays
SFX_DAYS_NO NUMBER(18) Y Total number of prefix
dates
PFX_DAYS_NO NUMBER(18) Y Total number of suffix
dates
DATE_LAST_LEAVE DATE Y Date at which last
leave was over
NATURE_LAST_LEAVE VARCHAR2(50) Y Type of leave of last
leave taken
AVAIL_LTC CHAR(10) Y Whether availing
Management Information System 88

LTC during present


leave
BLOCK_FIN_YEAR VARCHAR2(100) Y Years which are
blocked for LTC
SANCTIONING_AUTHORIT VARCHAR2(100) Y Remarks of
Y Sanctioning authority
SANCTIONING_DATE DATE Y Date on which leave
is sanctioned
ADD_CHARGE_GIVEN CHAR(10) Y Whether Additional
charge given
ADDITIONAL_CHARGE_TO CHAR(100) Y Additional charge
given to whom
OFFICE_ORDER_NO VARCHAR2(50) Y Order no at which
leave is granted
DATE_OF_JOINDEP DATE Y Date of
joining/departure
office before/after
leave
JOINDEP_AN_FN CHAR(10) Y Whether
joined/departed
before noon or after
noon
JOINDEP_FORWARDED VARCHAR2(100) Y
REMARKS VARCHAR2(200) Y Remarks of user if
any
OBS_DATE DATE Y Obsolete date
TOTAL_DAYS FLOAT(126) Y Total days
REMARKS_CONTROL_OFF VARCHAR2(150) Y Remarks of the
ICER controlling officer
ENTER_BY VARCHAR2(100) Y Data entered by
whom
ENTER_DATE DATE Y Data entered at
which date
STATUS VARCHAR2(5) Y
TO_CANCEL VARCHAR2(1) Y
JOINING_DATE DATE Y
DEPARTURE_DATE DATE Y
JN_DP_CO VARCHAR2(5) Y

22.TBL_LEAVE_MASTER
Primary Key: EMPLOYEE_NUMBER , LEAVE_TYPE
Foreign Key: EMPLOYEE_NUMBER references TBL_EMPLOYEE_DETAILS
Management Information System 89

COLUMN NAME DATA TYPE NULLABLE DESCRIPTION


EMPLOYEE_NUMBER VARCHAR2(20) N Employee number
EL FLOAT(126) Y No of earned leaves
CL FLOAT(126) Y No of casual leaves
RH FLOAT(126) Y No. of restricted
holidays
HPL FLOAT(126) Y No. of half pay leaves
DATE_UPDATED DATE Y Date on which record
has been updated
OBS_DATE DATE Y Obsolete date
ENTER_BY VARCHAR2(100) Y Data entered by whom
ENTER_DATE DATE Y Date on which data is
entered

ACCOMODATION

23.TBL_ACCOMODATION_REQUEST
Primary Key: EMPLOYEE_NUMBER, REQUEST_NO
Foreign Key: EMPLOYEE_NUMBER references TBL_EMPLOYEE_DETAILS

COLUMN NAME DATA TYPE


NULLABLE DESCRIPTION
EMPLOYEE_NUMBER VARCHAR2(20)
N Employee number
REQUEST_NO NUMBER(10)
N Accommodation
request no
DATE_OF_APPLICATION DATE Y Date of application
QUARTER_REQUESTED VARCHAR2(50) N Type of Quarter
requested
POOL_TYPE VARCHAR2(50) N Type of pool
ENDORSEMENT_NUMBER VARCHAR2(10) Y
DOOR_NO VARCHAR2(50) Y No .of house that
is being allotted
STREET_LOCALITY VARCHAR2(100) Y Locality of the
house
CITY VARCHAR2(100) Y City of the house
STATE VARCHAR2(50) Y State of the house
ZIP VARCHAR2(50) Y Pincode
ACCEPTED CHAR(10) Y Whether accepted
by the employee
ALLOTEMENT_CATEGORY CHAR(10) Y Category of
allotment
SECTOR VARCHAR2(50) Y Sector
Management Information System 90

BLOCK VARCHAR2(50) Y Block


OBS_DATE DATE Y Obsolete date
DATE_OF_POSSESSION DATE Y Date of
possession of
house
ENTER_BY VARCHAR2(100) Y Data entered by
whom
ENTER_DATE DATE Y Date on which
data is entered
FLOOR VARCHAR2(50) Y Floor

24.TBL_CHANGE_REQUEST
Primary Key: EMPLOYEE_NUMBER, CHANGE_SEQ_NO
Foreign Key: EMPLOYEE_NUMBER references TBL_EMPLOYEE_DETAIL :
Request_Number refrences tbl_accomodation_request(request_no)

COLUMN NAME DATA TYPE NULLABLE DESCRIPTION


EMPLOYEE_NUMBER VARCHAR2(20) N Employee number
REQUEST_NUMBER NUMBER(10) N Request number
CHOICE_NUMBER NUMBER(10) N Choice number within a
particular request
number
FLOOR_REQUESTED VARCHAR2(50) Y Floor requested
STREET_REQUESTED VARCHAR2(100) Y Street requested
LAYOUT_PLAN VARCHAR2(100) Y Layout plan
ENTER_BY VARCHAR2(100) Y Data entered by whom
ENTER_DATE DATE Y Date on which data is
entered

PENSION

25.TBL_PENSION_DETAILS
Primary Key :EMPLOYEE_NUMBER
Foreign Key: EMPLOYEE_NUMBER references TBL_EMPLOYEE_DETAILS

COLUMN NAME DATA TYPE NULL DESCRIPTION


ABLE
EMPLOYEE_NUMBER VARCHAR2(2 N Employee ID
0)
Management Information System 91

QUAL_YEAR FLOAT(126) Y Total number of years


of qualifying service of
the employee
QUAL_MONTH FLOAT(126) Y number of months of
qualifying service of
the employee
QUAL_DATE FLOAT(126) Y number of days of
qualifying service of
the employee
AVG_EMOLUMENTS_PENSIO FLOAT(126) Y Avg Emoluments
N given as part of
pension
PENSION_ADMISSIBLE FLOAT(126) Y Total pension
admissible
GRATUITY_EMOLUMENTS_D FLOAT(126) Y Emoluments for
UE gratuity
RETIRE_GRATUITY_ADMISSI FLOAT(126) Y Retirement gratuity
BLE admissible
FAMILY_PENSION_EMOLUME FLOAT(126) Y Emoluments for family
NTS_DUE pension
FAMILY_PENSION_ADMISSIB FLOAT(126) Y Family pension
LE admissible
ORDINARY_PENSION_AMOU FLOAT(126) Y Ordinary family
NT_DUE pension
ENHANCE_PENSION_AMOUN FLOAT(126) Y Enhanced family
T_DUE pension
DATE_OF_PENSION_APPLIC DATE Y
ATION
STATUS VARCHAR2(5 Y Whether pension
0) status is cleared or not
OBS_DATE DATE Y Obsolete date
PENSION_COMMUTE FLOAT(126) Y % of pension to be
commuted
COMMUTE_VALUE FLOAT(126) Y Amount of pension
commuted
RESIDUAL_PEN FLOAT(126) Y Residual pension after
commutation
ENTER_BY VARCHAR2(1 Y Entered by whom
00)
ENTER_DATE DATE Y Entered on which date

26.TBL_PENSION_LINK
Primary Key: EMPLOYEE_NUMBER & seq_no
Foreign Key: employee_number references tbl_pension_details
(employee_number)
Management Information System 92

COLUMN NAME DATA TYPE NULLABLE DESCRIPTION


EMPLOYEE_NUMBER VARCHAR2(20) N Employee
number
SEQ_NO NUMBER(10) N Sequence
number
FROM_DATE DATE Y From date
TO_DATE DATE Y To date
RUPEES FLOAT(126) Y Total pension
amt
ENTER_BY VARCHAR2(100) Y Data entered by
whom
ENTER_DATE DATE Y Date on which
data is entered

9.2 User Interface Design

1. Login screen
Management Information System 93

2. Main Menu
Management Information System 94

3. MASTERS

3.1 Menu for Master


Management Information System 95

3.2.1 Designation Master Main Page


Management Information System 96

3.2.2 Designation Master View All Page


Management Information System 97

3.2.3 Designation Master Update Page


Management Information System 98

3.3.1 Station Master Main Page


Management Information System 99

3.3.2 Station Master View All Page


Management Information System 100

3.4.1 Config Master Main Page


Management Information System 101

3.5.1 Pension Commutation Main Page


Management Information System 102

3.6.1 Holiday Master Update Page


Management Information System 103

3.7.1 Pay fixation Master


Management Information System 104

3.8.1 Grade Master Main Page


Management Information System 105

4. ACCOMMODATION

4.1 Accommodation Request Form


Management Information System 106

4.2 Accommodation Request Query Page


Management Information System 107

4.3 Accommodation Acceptance form


Management Information System 108

4.4 Accommodation Acceptance Query


Management Information System 109

4.5 Accommodation Change Request Form


Management Information System 110

4.6 Accommodation Abstract Report First Page


Management Information System 111

4.7 Accommodation Abstract Report


Management Information System 112

LEAVES

5.1 CL/RH Leave Application Form


Management Information System 113

5.2 Leave Application Form


Management Information System 114

5.3 Joining Departure Report


Management Information System 115

5.4 Controlling Officer (CO) Leave Approval Form


Management Information System 116

5.5 Sanctioning Officer (SO) Query Page


Management Information System 117

5.6 Sanctioning Officer (SO) Approval Form


Management Information System 118

5.7 Leave Report Main Page


Management Information System 119

EMPLOYEE DETAILS (Personal and Service related)

6.1 Employee Personal Details


Management Information System 120

6.2 Employee Personal Query Page


Management Information System 121

6.3 Family Member Details Page


Management Information System 122

6.4 Dependent Details


Management Information System 123

6.5 Professional Experience Details


Management Information System 124

6.6 Nominee Details


Management Information System 125

6.7 Qualification Details


Management Information System 126

6.8 Employee First Appointment Details


Management Information System 127

6.9 Employee Biodata Menu Page


Management Information System 128

6.10 Employee Biodata


Management Information System 129

6.11 Employee Increment Details


Management Information System 130

6.12 Employee Transfer Details


Management Information System 131

6.13 Employee Suspension Details


Management Information System 132

6.14 Employee Resumption Details


Management Information System 133

6.15 Employee Tenure Details


Management Information System 134

6.16 Employee Tenure Details Menu


Management Information System 135

6.17 Employee Permanency Details


Management Information System 136

6.18 General Query Page


Management Information System 137

9.3 Report Design

1. Family Members Report


Management Information System 138

9.4 Hardware and Software Specifications

9.4.1 Hardware Specification

Java 2.0 is an object-oriented programming language that runs on IBM-PC and


compatible microcomputer systems. Windows is a graphical system and, like all
such system requires a lot of processor power and memory if it is to operate
efficiently. Generally, a large hard disk space is needed for Windows applications
that are normally very hungry for disk space. A realistic hardware platform for
proposed system is:

Server Configuration
Processor Pentium.
Management Information System 139

RAM 64MB.
Hard Disk 200MB (disk requirement depends on various installation
options).
Monitor VGA Color Monitor.
Network Server should be on network
Internet Access

Client Configuration
Processor Pentium.
RAM Min 32MB (64MB recommended).
Hard Disk 200MB (disk requirement depends on various installation
options).
Monitor VGA Color Monitor.
Network System should be on network

9.4.2 SOFTWARE SPECIFICATION


I.E. 5.5 is required at the client machine.
Software used in the development of the system are:
• JSP 2.0 is used to develop this system as Front-end.
• Microsoft SQL Server 2000 as Back-end.
• Apache Tomcat 4.0 as web server.
• Windows 2000 (professional) as platform.
• Web authoring tool – Macromedia Dreamweaver Ultradev 4.0,
Adobe Photoshop 6.0.
Management Information System 140

10. System Testing


Management Information System 141

10.1 Introduction

Testing for “Personnel Information System” is done with the intent of checking the
application for errors or defects to rectify them before the implementation. No
matter how good the programming is, bugs usually creep in. There could be logical
errors, erroneous assumptions made while coding, failing in understanding the
exact requirements etc. Testing for this software is done to rectify all those errors.

Testing Objectives
There is a common misconception that software testing is an activity to improve
the correctness of software. The reality however is that testing should be viewed
more as a destructive process than a constructive process of software
development.

“The objective of testing is not to show the absence of defects, but to show
their presence.” Hence, any structured testing activity has to comply this
underlying objective.

Testing for “Personnel Information System” is done with the following objectives in
mind:
• To discover yet undiscovered errors.
• To determine whether all user requirements are being met.
• To find out whether all design specifications are being met.
• To ensure that code compiles without error.
• To ensure that there are no memory leak.
• To find out that there are no dead code areas i.e. the code that never gets
executes.
• To ensure that maximum errors are discovered at this stage to minimize the
debugging effort & cost.
• To ensure that the software produced is of high quality.

Types of Testing
Testing for PIS is done in the following order :
1. Unit Testing
2. Integration Testing
3. System Testing
4. Acceptance Testing

10.2 Unit Testing


Unit Testing is a dynamic method for verification where code is executed with some
test cases and then results are evaluated. To perform unit testing, Unit Test Cases
are designed to uncover maximum errors.
The following figure describes the unit tests carried at different steps of coding.
Different test cases are use to uncover different kinds of errors and bugs. Each test
had its own significance in Unit Testing.
Management Information System 142

Coding for Database


Connectivity with
Oracle

Coding of JSP

Various Test Cases:


• Interface
Checkpoints
• Local Data Structure
• Independent Paths

Oracle Connection through

Total no. of Structure of

Data in Tables Results in form of

Figure for Unit Testing of PIS


Management Information System 143

These inputs are mainly as follows:


• Interface Checkpoints
• Local Data Structure
• Independent Paths
• Boundary Conditions
• Error Handling Paths

All these tests are very useful to understand and uncover the errors.

1. Interface Checkpoints - It is performed to check the information flow across the


input and output of the module to be tested. Various tests performed are: -
1. The no. of input parameters should be equal to output parameters.
2. Correct number and type of arguments should be passed to the stored
procedures.
3. Global Variable definitions are consistent across modules.

It is tested that data that is entered should be retrieved properly. Records were
entered and saved in the database and then are carried out to ensure that proper
records are retrieved and at proper places.

Errors Generated: Some errors were generated at the time of retrieval of records.

2. Logical Data Structure – It is a common source by which large no. of errors can
be generated. It may be:
1. Incorrect database name.
2. Improper or inconsistent typing.
3. Incorrect variable names (names not according to coding standards)
4. Invalid table name or default value – a number value is given in place or
character value. Therefore, the data structure cannot directly recognize the
table name.
5. Inconsistent data type for table field in Oracle.
6. Impact of global data on module is also tested.

Errors Generated: The accuracy of the data must be checked with checking points
so that if user inputs incorrect data then the user must be informed.

3. Independent Paths – Selective testing of execution paths is very important


in unit testing. Various test cases are developed to test the control flow,
computations and comparisons. Basis Path Testing and loop testing is done
to uncover errors in which various values are selected to determine the
control flow.

Errors Generated: No errors are generated in testing the control flow.

4. Boundary Conditions – To see behavior of module at minimum and


maximum values this test is very helpful. Various tests performed are:
Management Information System 144

1. By providing input to JSP pages, the values more than the upper limit.
For example, by inputting a large number of characters in the Text field.
2. Another way to uncover the errors is providing the blank spaces in the
field.

Errors Generated: By proving the values that are more than the upper limit,
Overflow occurs where client side validations are not used. Otherwise, validations
are used to validate the input.

5. Error Handling Paths – During the test case, potential errors must be
handled. These errors should be carefully managed because they do not tell
much about themselves. Error description does not provide enough amount
of information to assist errors. Errors messages are coded in JSP pages
only. The most common errors that usually creep in are in form of database
errors. Appropriate messages are provided as and when errors occur.

Errors Generated: Error description is sometimes unintelligible i.e. they do not


speak about what they are. It is very difficult to understand them. Otherwise, good
description is provided about the nature of errors.

Result of Unit Testing

The result of unit testing phase is the sum-up of all the errors generated during
various test cases.
The unit testing is performed using various test logs for various modules and errors
are reported therein.
Format of test logs are as shown below:

Test Log

Test Case ID: IPO 01:01


Revision History
Sr. Revision Sections Reason for Revision Changed Approve
No. No. Affected By d by

Test description: Personnel Information System


Management Information System 145

Unit Test
The entire Personnel Information System is to be tested
on verification of the smallest unit of the software;
important control paths are tested to uncover errors within
the boundary of the module.
Function to be tested:

Environment: Java

Test Setup: Network facility for accessing the database.


MS word

Test Execution
♦ Inserting Data From Details (*.jsp)
Sr. Test Procedure Expected Results Actual Developer's
No Results Comments
1 Field/Column Validations
to be followed

2 Field/Column Validations
to be followed

Summary
Total test procedures passed
Total test procedures failed
No. of Major defects
No. of Minor defects

Actual Results:
Pass / Failed

♦ Querying and Updating Data From Details (*.jsp)

Sr. Test Procedure Expected Results Actual Developer's


No Results Comments
1 Field/Column validations
other than that in
Management Information System 146

insertion form for a


process.

Summary
Total test procedures passed
Total test procedures failed
No. of Major defects
No. of Minor defects

Actual Results:
Pass / Failed

♦ Querying and Deleting Data Form Details (*.jsp)

Sr. Test Procedure Expected Results Actual Developer's


No Results Comments
1 Field/Column validations
other than that in
insertion form for a
process.

Summary
Total test procedures passed
Total test procedures failed
No. of Major defects
No. of Minor defects

Actual Results:
Pass / Failed
Management Information System 147

10.3 Integration Testing

The PIS consists of many modules. All these modules are tested unit-wise before
conducting integration testing. Each module takes input from other module and
provides output to another module. The goal here is to test interfaces between the
modules.

To conduct the integration testing, it is necessary to realize that each of the


modules consists of series of separate screens. The Top – Down Approach is
being followed to conduct the integration testing on PIS. To do this all modules are
integrated by moving through control hierarchy. Modules are integrated in a depth-
first manner. This is because some modules (screens) provide the input to other
modules (screens).

During testing, the data is inputted in some screens of some module and are
tested for the retrieval of data from other modules/screens.

Moreover, modules are also tested for the links they provide to other modules
(screens).

Result of Integration Testing


Data is appropriately reflected in one module that is entered in some other module.
Some of the links are not working properly.

10.4 System Testing

System Testing is done to test the whole software and the goal is to see if the
software meets the requirements. This is essentially a validation activity.

Stress Testing is also done at this level to confront programs with abnormal
situations. For Stress Testing of PIS, Stress Test cases are designed through
which abnormal conditions are applied for software’s execution.

Some test cases on which PIS is tested are: -


1. A large number of users (about 25) are asked to work on a single page entering
data at a very high rate to test how input functions respond.
2. Retrieving data from a database by many users to test how database will
respond.
3. Seizing very large amount of available memory by enlarging the number of
customers in the database.

Result of System Testing


The complete software complies with the requirement specifications and no such
errors are generated.
Management Information System 148

No such errors are generated during stress testing. The speed of the application
and time duration gets affected by seizing large amount of memory available in the
system.

10.4 Acceptance Testing

Acceptance testing is performed with realistic data of the client to demonstrate that
the software is performing satisfactorily. Testing here focuses on the external
behavior of the system.
PIS was tested on the client side in presence of the all the staff.

Result of Acceptance Testing


PIS was accepted satisfactorily by all the employees.
Management Information System 149

11. System Constraints


4. Organizational Profile
Management Information System 150

11.1 System Constraints

• Network Connectivity
Since the system being proposed is solely dependent on the availability and
connectivity of the network, a fast Ethernet network is required. To connect
the administration block to the main server Fiber Optic cabling is required.

• Trained Manpower Skills


Data entry being the main purpose of the system, even though required
validations and checks will be provided at the front end, trained manpower
is required to minimize the chances of errors.

• Hardware resources
Properly configured robust system needs to be configured depending upon
the needs of the hospital, since most of the activities are held only during
office hours, it would be necessary for the hardware resource to be fully
functional at least in those hours.

• Security
Provide an operating system level and application level authentication and
validation.

• Compatibility of data formats


Architecture that is necessary and proposed for the data is based upon
open J2EE standard, therefore all interfaces with in and without the system
have necessarily to be complied with the above standards. This can help to
a large extent in future transactions; both inter department and intra
department. The solution will also be scalable if one opts for open Software
Standards incorporating platform independence, J2EE compliance and
secure transactions.

• Proper policies and regulations


Proper policies and regulation should be formed since this activity of
General Hospital coordinates between various departments.

11.2 SYSTEM SECURITY

The system is of utmost importance and should cover the following aspects:

• Administrative
o Roles and responsibilities should be clearly defined for system
related work, like backup operators, power users, Replicator
etc.
• Operational
Management Information System 151

o The system should also be able to grant and revoke privileges


with regards to the data access being given to different users.
o User classes should be defined in order to specify restrictions
on viewing, modifying and updating of the data.
• Network
o As the data traveling on the network will be confidential proper
security mechanism should be in place to ensure the credibility
and authenticity of the data.

11.3 Suggested Enhancements

The advent of e-governance has brought a need of increased efficiency and


scalability. But this step has brought an explosion of data, as the different
Departments of the Government gather more and more details. Today this
information has become key to the ability to operate and compete – and that in
turn, has made the storage and management of data a vital issue.

To achieve this, the Department needs enterprise applications and other software
over an Internet Protocol Ethernet based network. Such architecture will essentially
keep data safe and readily available. Also such architecture will need to be flexible
and scalable in storage, to keep capacity in step with the changing needs of
technology.

“The art of progress is to preserve order amid change and to preserve change
amid order.” The Department needs to move its operations to the Web. The answer
is a portal –
A web page that integrates data from other sources. Using portals will enable the
different offices of the Department to perform their daily tasks using a centralized
place.

To implement a web-based application architecture, which links all the offices of


the Department with the Head Office, a Server is needed. It serves as a central
unit that performs the critical storage and management of vast data.

The offices would need machines that are linked with the servers. The local (node)
machines will serve as the functional units, where the majority of the processing
takes place, and also serve as entry points for crucial data.

Besides this hardware infrastructure, the Department needs to employ a


Parliamentary Query software program.

By computerizing the Personnel Information System , we keep aside all the


papers, cards and the registers used to maintain records about the employees,
and can give an interactive way of arranging, managing and handling the large
volumes of data.
Management Information System 152

The flow of documents on paper will be drastically reduced and will be faster as
well. After all the Directorates under each coordination wing are computerized, the
director or any person at the top level can get information regarding any activity of
these programs.

BIBLIOGRAPHY

S. No. Author(s) Title Publisher


1. Patrick Naughton,The Complete Reference Tata McGraw Hill
Herbert Schildt Java 2.0
2. Phil Hanna The Complete Reference Tata McGraw Hill
Java 2.0
3. Various Professional JSP Wrox
4. Various Professional Java Server Wrox
Programming
5. Richard Waymire, SQL Server 2000: In 21 Techmedia
Rick Sawtell days

6. Danny Goodman JavaScript Bible IDG Books India


Management Information System 153

Referenced Sites

• www.java.sun.com
• www.javascript.internet.com
• www.microsoft.com
• www.werbach.com
• www.google.com

Das könnte Ihnen auch gefallen