Filter
Top Products
such as an order, a shipping document, or an invoice.
Information flows can use various media, such as FAX
machines, telephones, or electronic mail, which can be
represented on the LOVCs by icons. See also
data
flow
,
material flow
, and
control flow
.
information system. See
system
.
input container. In FlowMark: storage for data used
as an input for activities, processes, or blocks. See
also
output container
.
inquiry management bus. On the ALOVC, a
continuum of repetitive and unpredictable processes for
enabling customers to request information on anything
about the company, its products and services, or a past
service encounter (for example, an inquiry about a
proposal, a contract, or an order). See also
bus
and
change management bus
.
internal interface. An interface between two internal
business functions, departments, or jobs where a
dependency exists or a transfer takes place.
issue. A matter at dispute that needs to be discussed
and resolved.
J
JLOVC. See
job line of visibility chart
.
job. The physical implementation of business
processes, as expressed through manual activities and
interfaces with customers, systems, and internal or
external organizations. A series of one or more
activities in a department that are performed by one
employee. A job is represented by the JLOVC and can
be part of a PLOVC. Examples of a job: marketing
representative or customer service representative.
job line of visibility chart (JLOVC). A physical
modeling and blueprinting technique that shows the
effectiveness and efficiency
of one particular job. Using
the JLOVC, you focus on
how
an individual job is or will
be implemented, and
who
is or will be executing the
manual activities. It also shows the relationship of each
activity to customer activities, systems, and internal or
external organizations. See also
line of visibility chart
.
L
LAN. Local area network.
line of business (LOB). A family of products or
services, having common characteristics.
line of visibility (LOV). On an LOVC, the line
between your customer and internal processes or
activities where all points of contact (service
encounters) are shown. See also
service encounter
.
line of visibility chart (LOVC). The graphical
representation of all aspects of your business processes
that are required to provide your customer with a
specific product or service. It shows all points of
contact with your customer. The LOVC is implemented
in four different types of charts:
ALOVC. See
architecture line of visibility chart
.
LLOVC. See
logical line of visibility chart
.
PLOVC. See
physical line of visibility chart
.
JLOVC. See
job line of visibility chart
.
Line of Visibility Engineering Methodology
(LOVEM). See
IBM LOVEM
.
Line of Visibility Enterprise Modeling (LOVEM). See
IBM LOVEM
.
LLOVC. See
logical line of visibility chart
.
load balancing. Attempting to ensure that each
worker gets the same amount of work to perform. Can
be automated or manual.
LOB. See
line of business
.
location. A physical place where activities are
performed or where information or materials are stored.
logical. The abstract or generic nature of business
processes or data before any physical constraints are
applied. Logical defines
what
process or data is
required, not
how
it is implemented. See also
unconstrained
.
logical line of visibility chart (LLOVC). A logical
modeling or blueprinting technique that shows the
effectiveness
of the process path that you are studying.
Using this technique, you focus on
what
needs to be
done, not
how
it is done. See also
line of visibility
chart
.
logical model or blueprint. The depiction of the
effectiveness of a process:
doing the right thing
. See
also
logical, model
, and
blueprint
.
logical-to-physical transformation. The translation of
a logical process into its physical implementation
components, such as manual activities or systems
functions. See also
logical transformation list
.
logical transformation list (LTL). A technique for
transforming logical processes into physical
implementation scenarios. For example, a logical
process can be transformed into any number of manual
activities, any number of systems functions, or both.
42 FlowMark V2.3 Design Guidelines