The PI Batch Database
Architecture is tightly integrated
with the PI Server Architecture. It was introduced
in PI Server Version 3.3 and
it is considered part of the Module Database
structure that we have in the PI Server.
And the PI Batch Database allows us to
gather and archive
real-time data in time
frames, and we have defined
certain parameters in the PI Batch Database. For example,
the Campaign, Batch, Unit Batch
and Sub-Batch layers. Although, as we will
see a little bit later in the class, our current Batch
generator will only use Batch,
Unit Bath, and Sub-Batch. We,
we have not implemented the Campaign layer
of the PI Batch Database. There's also something called
the Transfer Record Database as well,
and it is currently not implemented in our
Batch Generator Interface. It may be used by
other applications. We give you a nice
graphical configuration tool with the PI System
Management Tools, and so, you can use our
tools to view the data or you can
develop your own. We provide complete read-write access
to the Batch Database using our PI SDK.
This is a diagram that you will see
throughout this course, and it's just
here to illustrate how tightly woven all of the systems
are, all of the Architectures are with one
another in the PI Batch Database
with regard to the PI System. And you can see here
that this piece is representing our PI
Archive. This supplies all Process Values,
and it's actually where we store the Event
Frame information. The PIBatch
Database stores batch records, so
the PI Archive stores specific
information about each batch, whereas the PIBatch Database
stores the record itself.
This diagram represents the
PIBatch Database from an Architectural
or hierarchical standpoint. At
the top, we have the PICampaign level.
The PICampaign is made up of one or more PI
Batches. A PI Batch is constructed
of one or more PIUnitBatch
Structures.
And the PIUnitBatch can be made up of one
or more sub-batches. Sub-batches can, in turn,
have other sub-batches. Let's
take at look at each one of these in our -- in sequence.
The PICampaign is the highest level
in the BatchDatabase hierarchy. It's the name
of a campaign. Usually, it's the
product that's being made, and it has a
specific start and end time.
We have the PIBatch which is
the second level of the PIBatchDatabase
hierarchy. And the PIBatch
contains the names of products and
batches. It usually references some sort of recipe.
And normally a batch,
PIBatch, will have a specific start and end time. Sometimes
these might be considered lots.
And there's some other data that we store along with that.
The PIUnitBatch is actually the
Unit or Units that
are actually producing the materials. Whereas the PIBatch
level was a lot or run of
a product, the UnitBatch is actually where the
production is taking place. And it's usually
contains the name of the Unit and the batch, UnitBatch ID.
Occasionally, we, we would include the
product or the recipe name and, of course,
start and end times. And then,
the Golden Batch Rule which says
only one UnitBatch may be active in a Unit
over any given time period. That's the PIBatach
Golden Rule. We realize
there are some production processes where
a single Unit might be running multiple
batches at one time. However, the
PIBatch Database cannot accommodate that particular
structure. Only one UnitBatch may be active in
a Unit at a -- at one time.
Finally, we get to the SubBatch
level usually where
some step, or some operation or phase,
is taking place within a UnitBatch.
And, the SubBatches, they are optional.
Again, they are usually operations or phases.
And they will have Start and EndTimes
that are within the Start and EndTime
of the UnitBatch. And, SubBatches can
themselves have collections of
SubBatches. So, the hierarchy is very rich.