This document presents an overview of the system, the design considerations leading

to the system architecture, describes the system architecture itself, and finally
details
the system design
The end user system will initially need to present a user interface where they can
select the factory they are working at, the checkpoint they are inspecting at, and
the type
of car being inspected. This information is stored on the server alongside the
defect data
that the user inputs later.
The end user system will initially need to present a user interface where they can
select the factory they are working at, the checkpoint they are inspecting at, and
the type
of car being inspected. This information is stored on the server alongside the
defect data
that the user inputs later.
Second, another menu will allow users to indicate the location, severity, and type
of defects. This menu will display a wireframe for the selected model of car, that
allows
users to place the defect in the appropriate location on the vehicle.
Lastly, end users will be able to run three types of reports over previously stored
defect data. The first type of report is a QA report, which summarizes vehicle
inspections
over a specific time range, which is chosen by the user when running the report. It
contains all the data stored for the defects over that period, the total number of
cars
inspected, and the defects per unit. It also contains several tables that show an
aggregated
car diagram with locations of all recorded defects, and a pie chart that displays
the ratios
of all defect types over this period.
The end user system will initially need to present a user interface where they can
select the factory they are working at, the checkpoint they are inspecting at, and
the type
of car being inspected. This information is stored on the server alongside the
defect data
that the user inputs later.
Second, another menu will allow users to indicate the location, severity, and type
of defects. This menu will display a wireframe for the selected model of car, that
allows
users to place the defect in the appropriate location on the vehicle.
Lastly, end users will be able to run three types of reports over previously stored
defect data. The first type of report is a QA report, which summarizes vehicle
inspections
over a specific time range, which is chosen by the user when running the report. It
contains all the data stored for the defects over that period, the total number of
cars
inspected, and the defects per unit. It also contains several tables that show an
aggregated
car diagram with locations of all recorded defects, and a pie chart that displays
the ratios
of all defect types over this period.
The second report is a Summary of Analysis report, which is a numeric summary
of defects over a given period that were entered by a specific analyst. The user
running
the report is able to specify the date range to run the report on. This report
contains the
shift the analyst was on, the check point being inspected, and a summary of the
number
of defects, number of units, and number of defects per unit.

The second report is a Summary of Analysis report, which is a numeric summary

of defects over a given period that were entered by a specific analyst. The user
running
the report is able to specify the date range to run the report on. This report
contains the
shift the analyst was on, the check point being inspected, and a summary of the
number
of defects, number of units, and number of defects per unit.

Second, another menu will allow users to indicate the location, severity, and type
of defects. This menu will display a wireframe for the selected model of car, that
allows
users to place the defect in the appropriate location on the vehicle.
Lastly, end users will be able to run three types of reports over previously stored
defect data. The first type of report is a QA report, which summarizes vehicle
inspections
over a specific time range, which is chosen by the user when running the report. It
contains all the data stored for the defects over that period, the total number of
cars
inspected, and the defects per unit. It also contains several tables that show an
aggregated
car diagram with locations of all recorded defects, and a pie chart that displays
the ratios
of all defect types over this period.
The second report is a Summary of Analysis report, which is a numeric summary
of defects over a given period that were entered by a specific analyst. The user
running
the report is able to specify the date range to run the report on. This report
contains the
shift the analyst was on, the check point being inspected, and a summary of the
number
of defects, number of units, and number of defects per unit.

This document presents an overview of the system, the design considerations leading
to the system architecture, describes the system architecture itself, and finally
details
the system design
Considering the need for continuity and to rein in the losses of the utilities,
need was felt to continue
the initiative of APDRP in 11th plan as well. On review of the status and benefits
achieved of APDRP,
it was felt that to have sustainable distribution business, it is essential to give
impetus to IT enabling of
the sector on an integrated platform. The IT platform shall assist in capturing and
validating the
energy and revenue model to gather in a transparent manner with accuracy.
Considering the difficulties of domain expertise in IT area of the utilities and
the experiences the
utilities had, it was considered necessary to prepare SRS template, which shall
provide the IT
infrastructure for drawing the baseline data while addressing the need of IT back
bone in the area of
distribution business process to capture the benefits of the investments on
sustainable basis.
2 INTENT OF SPECIFICATION
2.1 This specification intends to cover the following activities, services and
works in respect of
successful set up of IT infrastructure for collection of baseline data for energy
and revenue of
the identified scheme areas (town) and setting up of customer care center in the
towns along
with supply, installation, testing and commissioning of all necessary hardware,
software and
managing the facilities created under the scope of work for a period of 5 years
after successful
completion of acceptance test of hardware and software. Detailed scope of work
under this
package is listed at clause 3.0.
This document presents an overview of the system, the design considerations leading
to the system architecture, describes the system architecture itself, and finally
details
the system design
Considering the need for continuity and to rein in the losses of the utilities,
need was felt to continue
the initiative of APDRP in 11th plan as well. On review of the status and benefits
achieved of APDRP,
it was felt that to have sustainable distribution business, it is essential to give
impetus to IT enabling of
the sector on an integrated platform. The IT platform shall assist in capturing and
validating the
energy and revenue model to gather in a transparent manner with accuracy.
Considering the difficulties of domain expertise in IT area of the utilities and
the experiences the
utilities had, it was considered necessary to prepare SRS template, which shall
provide the IT
infrastructure for drawing the baseline data while addressing the need of IT back
bone in the area of
distribution business process to capture the benefits of the investments on
sustainable basis.
2 INTENT OF SPECIFICATION
2.1 This specification intends to cover the following activities, services and
works in respect of
successful set up of IT infrastructure for collection of baseline data for energy
and revenue of
the identified scheme areas (town) and setting up of customer care center in the
towns along
with supply, installation, testing and commissioning of all necessary hardware,
software and
managing the facilities created under the scope of work for a period of 5 years
after successful
completion of acceptance test of hardware and software. Detailed scope of work
under this
package is listed at clause 3.0.
This document presents an overview of the system, the design considerations leading
to the system architecture, describes the system architecture itself, and finally
details
the system design
This document presents an overview of the system, the design considerations leading
to the system architecture, describes the system architecture itself, and finally
details
the system design
This document presents an overview of the system, the design considerations leading
to the system architecture, describes the system architecture itself, and finally
details
the system design
This document presents an overview of the system, the design considerations leading
to the system architecture, describes the system architecture itself, and finally
details
the system design
This document presents an overview of the system, the design considerations leading
to the system architecture, describes the system architecture itself, and finally
details
the system design
This document presents an overview of the system, the design considerations leading
to the system architecture, describes the system architecture itself, and finally
details
the system design
This document presents an overview of the system, the design considerations leading
to the system architecture, describes the system architecture itself, and finally
details
the system design
Considering the need for continuity and to rein in the losses of the utilities,
need was felt to continue
the initiative of APDRP in 11th plan as well. On review of the status and benefits
achieved of APDRP,
it was felt that to have sustainable distribution business, it is essential to give
impetus to IT enabling of
the sector on an integrated platform. The IT platform shall assist in capturing and
validating the
energy and revenue model to gather in a transparent manner with accuracy.
Considering the difficulties of domain expertise in IT area of the utilities and
the experiences the
utilities had, it was considered necessary to prepare SRS template, which shall
provide the IT
infrastructure for drawing the baseline data while addressing the need of IT back
bone in the area of
distribution business process to capture the benefits of the investments on
sustainable basis.
2 INTENT OF SPECIFICATION
2.1 This specification intends to cover the following activities, services and
works in respect of
successful set up of IT infrastructure for collection of baseline data for energy
and revenue of
the identified scheme areas (town) and setting up of customer care center in the
towns along
with supply, installation, testing and commissioning of all necessary hardware,
software and
managing the facilities created under the scope of work for a period of 5 years
after successful
completion of acceptance test of hardware and software. Detailed scope of work
under this
package is listed at clause 3.0.
This document presents an overview of the system, the design considerations leading
to the system architecture, describes the system architecture itself, and finally
details
the system design
This document presents an overview of the system, the design considerations leading
to the system architecture, describes the system architecture itself, and finally
details
the system design
This document presents an overview of the system, the design considerations leading
to the system architecture, describes the system architecture itself, and finally
details
the system design
This document presents an overview of the system, the design considerations leading
to the system architecture, describes the system architecture itself, and finally
details
the system design
This document presents an overview of the system, the design considerations leading
to the system architecture, describes the system architecture itself, and finally
details
the system design