Processing of transactions results in certain documents. These documents may be
classified into any of the following types:
(a) Informational Documents:
These documents just inform that something has taken place or is taking place. For
example, a sale confirms that the order has been received from the customer and has been
verified.
(b).Action Oriented Documents:
These documents need to be acted upon. For example, a purchase order initiates a
purchase. Similarly a production order instructs the production department to start production
of the products mentioned in the production order.
(c). Investigational Documents:
These are generated on an exceptional basis. For example, whenever operations are not
conforming to the range of deviations permitted, the variations are tracked and analyzed. A
report is generated to enable the control point to take corrective action.
The reports or outputs generated by the TPS can also be classified into the following
categories:
(a). Pre-planned Reports:
Formats of these reports are pre-designed. These reports are frequently generated to meet
information requirements of planning and control of actions. Most of these reports are periodic
in nature like daily report, weekly report, monthly report etc. for example, weekly sales analysis
report submitted to the sales manager helps him to know whether the sales targets for the week
were met or not. If the targets were not met, the reasons for failure to meet the targets are also
analyzed and mentioned in the report. This enables a manager to take corrective action.
(b). Pre-planned Enquiries:
For the smooth an deficient functioning of any business, a lot of status information will
be needed. For example, if a sale order comes from a customer, the sales clerk needs some status
information about the stock of that particular inventory item, pending orders, credit limits in case
of credit transaction etc. before he confirms the order. Most of this type of status information
needs can be met through built-in query facility.
(c). Ad-hoc Reports and inquiry Responses:
These reports and inquiries are infrequent or are not anticipated. They are needed to take
some non-routine decisions or actions. For example, at the time of wage negotiation with its
workers, if a firm is considering to offer a new incentive scheme, the personnel manager / the
finance manager may want to know the implications of this decision in terms of financial
obligations. This information need cannot be anticipated in advance. Hence, such unique
information needs have to be met by ad-hoc reports and enquiry facility.
(d) User Machine Dialogue results:
For interactive decision making like in DSS, the decision maker has to enter into a
dialogue with the system to generate more useful information. The results are interactively
generated and displayed on the screen.
classified into any of the following types:
(a) Informational Documents:
These documents just inform that something has taken place or is taking place. For
example, a sale confirms that the order has been received from the customer and has been
verified.
(b).Action Oriented Documents:
These documents need to be acted upon. For example, a purchase order initiates a
purchase. Similarly a production order instructs the production department to start production
of the products mentioned in the production order.
(c). Investigational Documents:
These are generated on an exceptional basis. For example, whenever operations are not
conforming to the range of deviations permitted, the variations are tracked and analyzed. A
report is generated to enable the control point to take corrective action.
The reports or outputs generated by the TPS can also be classified into the following
categories:
(a). Pre-planned Reports:
Formats of these reports are pre-designed. These reports are frequently generated to meet
information requirements of planning and control of actions. Most of these reports are periodic
in nature like daily report, weekly report, monthly report etc. for example, weekly sales analysis
report submitted to the sales manager helps him to know whether the sales targets for the week
were met or not. If the targets were not met, the reasons for failure to meet the targets are also
analyzed and mentioned in the report. This enables a manager to take corrective action.
(b). Pre-planned Enquiries:
For the smooth an deficient functioning of any business, a lot of status information will
be needed. For example, if a sale order comes from a customer, the sales clerk needs some status
information about the stock of that particular inventory item, pending orders, credit limits in case
of credit transaction etc. before he confirms the order. Most of this type of status information
needs can be met through built-in query facility.
(c). Ad-hoc Reports and inquiry Responses:
These reports and inquiries are infrequent or are not anticipated. They are needed to take
some non-routine decisions or actions. For example, at the time of wage negotiation with its
workers, if a firm is considering to offer a new incentive scheme, the personnel manager / the
finance manager may want to know the implications of this decision in terms of financial
obligations. This information need cannot be anticipated in advance. Hence, such unique
information needs have to be met by ad-hoc reports and enquiry facility.
(d) User Machine Dialogue results:
For interactive decision making like in DSS, the decision maker has to enter into a
dialogue with the system to generate more useful information. The results are interactively
generated and displayed on the screen.
No comments:
Post a Comment