CIP4 TSC

1
Welcome to the Montreal MIS Tutorial
2
MIS Tutorial

• What is an MIS
• What is the MIS role in JDF
• Introduction Gray Boxes
• MIS Requirements
• Job Costing

3
CIP4 Reference Model
4
CIP4 Reference Model

• Product Definition / Intent
• Communication betweenprint customer and printer
• Fully Intent-Based
• Today mostly non-JDF
• JDF used for job definitionin Quotes and Orders
• PrintTalk used for definitionof the business
  transaction
• CIP4 Product Definition WG

5
CIP4 Reference Model

• Process Definition
• MIS managedenvironment
• MIS created initialjob (ID and Ticket)
• PurelyProcess-Based
• MIS creates Processnodes or Gray Boxes
• Production Managerexpands Gray Boxesto Process
  nodes
• JMF used for feedback

6
What is an MIS

• Software TLAs
• MIS Management Information System
• ERP Enterprise Resource Planning
• MES Manufacturing Execution System
• The MIS role in JDF is all of the above
• Print MIS Systems
• Specific for Print
• Also provides information to management -)

7
What is the MIS

• MIS is (possibly) the wrong term
• MIS is a Role not always a single system
• Main tasks
• Created Quotations to customers
• Handles Customer Order Entry
• Creates Production Jobs and Job Tickets
• Does Production Scheduling
• Handles Material Logistics (stock and purchasing)
• Does Job Tracking and Job Costing
• Includes Invoicing (Billing) and Accounting

8
MIS and JDF/JMF
9
Before MIS

• Everything was manual
• Paper job tickets passed around
• Information about production written on paper
• At job completion, papers were filed
• .

10
Before JDF

• MIS manages / tracks information about jobs
• Paper job tickets still passed around
• Information about production written on paper
• Option to have shop floor data collection
  terminals for capturing costing information in
  real-time
• At job completion, papers are filed
• Data captured by shop floor data collection
  stored / managed by MIS
• Much information managed / tracked by production
  systems still hidden from MIS
• .

MIS
SFDC
SFDC
SFDC
SFDC
11
MIS With JDF

• MIS passes data it knows to JDF-enabled
  production systems or integration system
• JDF-enabled production systems can add more data
  to the JDF ticket
• Production parameters
• Costing data
• General notes
• JDF ticket passed back to MIS
• Bridges the islands of information that used to
  exist
• .

12
MIS vs. Integration System

• 2 Strategies of Workflow Implementation
• MIS as the leading system
• MIS controls individual devices directly
• Production Integration System as the leading
  system
• MIS passes control of individual devices to an
  integration system
• Integration system controls individual devices
• Products are generally either
• an MIS that adds features of Production Control
• A Production Control System that adds features of
  an MIS

13
MIS and JDF

• MIS gets customer view of job (Intent)
• MIS converts Intent to Process by doing job
  planning, estimating and scheduling

14
MIS and JDF

• MIS creates the initial JDF ticket (Process)
• MIS submits JDF ticket to production
• MIS receives JMF for job tracking

15
MIS and JDF

• MIS receives JDF back after completion
• MIS submits JDF to next production step

16
Introduction to Gray Boxes
17
Intent to Process conversion

• Customers view of job is description of what
  to produce not how to produce
• MIS needs to convert the what (Intent) into the
  the how (Process)
• For some Processes MIS can create full Process
  definition (all Resources)
• For many other Processes MIS does not have enough
  technical detail / knowledge
• Solution Gray Boxes

18
Gray Boxes

• For many Processes the MIS does not know
• The exact Processes required
• The exact order of the Processes
• The parameters of all Processes
• Examples
• Pre-Press Screening angles, Trapping params
• Result MIS cannot create valid JDF

19
Gray Boxes

• Solution (in simple words)
• The MIS writes in the JDF what it knows The
  Gray Box
• The production system add what it needs
  Expanding the Gray Box
• By operator input or applying defaults
• The production system informs the MIS what it has
  done
• Using JMF Signals of type NewJDF

20
Gray Box - Example

• Example from Pre-Press

21
Gray Box - Example
22
Gray Box - Example
23

• MIS Requirements

24
MIS and JDF/JMF

• JDF
• Replacement for Paper job ticket
• JMF and Audits
• Replacement for Shop floor data collection

25
Shop floor data collection

• Staff time and attendance
• Complete record of staff time (9 to 5)
• Job costing
• Complete record of actual production cost
• Work in progress (WIP)
• Complete record of cost of jobs in production
• Equipment utilisation statistics
• Complete record of machine time
• Production and Non-Productive

26
JMF vs. Audits

• Audits are only available for jobs
• Productive time
• JMF can be used for job related time
• Productive time
• Up to JDF 1.3 Audits are the only accurate
  source of job costing data
• The reason for JDF snapshots up to JMF 1.3
• From JDF 1.4 Reliable JMF Channels
• JMF only way to record non-job related time
• Non-Productive time

27
Work In Progress

• Value of actual costs on jobs in production
• Like value of stock in warehouse
• Calculated on Daily, Weekly, Monthly basis
• Is used to calculate companys profitability
• Used by accountants and auditors
• Must be very accurate
• close enough ! good enough
• The reason for Audit snapshots in JMF 1.3 and
  Reliable JMF Channels in JMF 1.4

28
MIS / Production Interaction

• BaseMIS-ICS Level 1 (Job Tickets Only)
• Job submission
• Returned JDF with Simple Audits
• BaseMIS-ICS Level 2 (adds Job Tracking)
• JMF Status Signals (fire and forget)
• Full Audits in JDF Snapshots and Returned JDF
• BaseMIS-ICS Level 3 (adds Job Costing)
• JDF 1.3 JDF Snapshots in JMF Signals
• JDF 1.4 (proposed) Reliable JMF Channels

29
JMF Signals
30
JMF Signals

• Status Signals
• Report Device and Job Status
• Used for Job Tracking
• Used for Job Costing (hours component)
• Resource Signals
• Report Resource Comsumption / Production
• Used for job Costing (material component)
• Used for Job Tracking (Plates been made?)
• Events / Notifications
• Report special events and milestones
• Used for Errors, Job Completion reporting,
  Archieving, etc

31
JMF Status Signals

• Create JMF when
• Device is switched on
• Every status change (begin of new phase)
• Idle -gt Setup -gt Running -gt Cleanup -gt Idle
• Every change of Shift and/or Operator
• A heart beat for long running jobs
• RepeatTime in Query / Subscription
• (Just before) Device is switched off

32
JMF Status Signals

• JDF snapshot (1)
• Up to JDF 1.3 JMF Signals a fire and forget
  and therefore unreliable
• There is no guarantee that all Signals arrive at
  MIS
• WIP must be accurate, therefore MIS must get
  complete job costing information
• In JDF 1.3 JDF snapshot is only available
  mechanism to get accurate costs for jobs that
  have not yet been returned to MIS

33
JMF Status Signals

• JDF snapshot (2)
• Must contain
• Process node that is executing (not complete JDF
  if non-spawned JDF was received)
• Complete AuditPool including Audit for this
  JobPhase

34
JMF Reliable Signals

• JMF Reliable Signals
• From JDF 1.4 JMF Signal channels can be made
  Reliable
• To guarantee that all Signals will arrive at MIS
• Signals must be acknowledged by receiver
• Signals must be repeated if not acknowledged
• From JDF 1.4 JMF can be used to get accurate
  costs for jobs that have not yet been returned to
  MIS

35
JMF Status Signal
36
JMF Resource Signals

• Create JMF when
• A Resource is (partly) consumed
• Media
• Paper, Plates
• UsageCounters
• A Resource is (partly) produced
• ExposedMedia
• Plates
• Preview
• Component

37
JMF Resource Signals
38
Thank You