1 / 36

Welcome to the Heidelberg MIS Tutorial

Welcome to the Heidelberg MIS Tutorial. MIS Tutorial. What is an MIS Gray Boxes MIS Requirements Job Costing. Creative Professional. Prepress Manager(s). Prepress. Customer. Limited Process. Extended MIS. Production Scheduling. Print Buyer. Prepress. Negotiation & Quote. Product

sakura
Download Presentation

Welcome to the Heidelberg MIS Tutorial

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Welcome to the Heidelberg MIS Tutorial

  2. MIS Tutorial • What is an MIS • Gray Boxes • MIS Requirements • Job Costing

  3. CreativeProfessional PrepressManager(s) Prepress Customer LimitedProcess ExtendedMIS ProductionScheduling PrintBuyer Prepress Negotiation & Quote Product Description LimitedProcess CustomerService Rep Sales Rep PressManager(s) Press CreateJDF Intent Base MIS ProductDescription (with ranges) Estimating &Order Entry LimitedProcess Print ShopManager ProductDescription (Actual values) Press CreateDocument PrepressOperator PostpressManager(s) Postpress PressOperator Job Creation Print Shop Management Postpress PostpressOperator Customer Facility Print Shop CIP4 Reference Model

  4. CreativeProfessional PrepressManager(s) Prepress Customer LimitedProcess ExtendedMIS ProductionScheduling PrintBuyer Prepress Negotiation & Quote Product Description LimitedProcess CustomerService Rep Sales Rep PressManager(s) Press CreateJDF Intent Base MIS ProductDescription (with ranges) Estimating &Order Entry LimitedProcess Print ShopManager ProductDescription (Actual values) Press CreateDocument PrepressOperator PostpressManager(s) Postpress PressOperator Job Creation Print Shop Management Postpress PostpressOperator Customer Facility Print Shop 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. CreativeProfessional PrepressManager(s) Prepress Customer LimitedProcess ExtendedMIS ProductionScheduling PrintBuyer Prepress Negotiation & Quote Product Description LimitedProcess CustomerService Rep Sales Rep PressManager(s) Press CreateJDF Intent Base MIS ProductDescription (with ranges) Estimating &Order Entry LimitedProcess Print ShopManager ProductDescription (Actual values) Press CreateDocument PrepressOperator PostpressManager(s) Postpress PressOperator Job Creation Print Shop Management Postpress PostpressOperator Customer Facility Print Shop CIP4 Reference Model • Process Definition • MIS managedenvironment • MIS created initialjob (ID and Ticket) • Should be purely“Process-Based” • MIS creates “Process”nodes 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 • … • Print MIS systems are all of the above • Specific for Print • Also provides information to management

  7. What is an 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. MIS and JDF • MIS gets customer view of job (Intent) • MIS converts Intent to Process by doing job planning, estimating and scheduling • MIS creates the initial JDF ticket (Process) • MIS submits JDF ticket to production • MIS receives JMF for job tracking • MIS receives JDF back after completion • MIS submits JDF to next step in production

  10. Intent to Process conversion • Customer’s 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 nothave enough technical detail / knowledge • Solution: Gray Boxes

  11. 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

  12. 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

  13. Gray Box - Life Cycle MIS Uses GB as legoblocks Fill in (limited) parameters it knows Gray box expander Expands the gray boxes to sequences of real processes • Filling in missing parameters • from default values • by Operator Calls external programs with UI to add some parameters (e.g. RunList, Imposition) Prepress Processes Executes the processes Reports back status

  14. Gray Box • How to detect s Gray Box • From JDF 1.3 - 3.1.4.1 Use of the Types attribute in ProcessGroup nodes - Gray Boxes: • ProcessGroup nodes may contain an optional Types attribute that allows a controller (e.g. an MIS system) to define a set of processes that must be executed without defining the exact structure or grouping of these processes into individual JDF nodes. ProcessGroup nodes that contain a Types attribute are commonly referred to as Gray Boxes.

  15. Gray Box • A Gray Box is a JDF Process Group with: • JDF/@Category=“...” • JDF/@Types=“...” • Either a real Types list of a special token from JDF 1.2 Table 3-4

  16. Gray Box • JDF/@Category • JDF 1.2 table 3-4 @Category says: • This allows processors to identify the general purpose of a node without parsing the Types field. For instance a RIP for final output and RIP for proof process may have identical Types attribute values but will have Category = “ProofRIPing” or Category = “RIPing” respectively.

  17. Gray Box • @Types • JDF 1.2 table 3-4 @Types says: • The [following] special tokens are defined to allow a JDF-enabled MIS or workflow system to roughly specify finishing, proofing, and RIPing without knowing the details of the respective combined processes. Use these special tokens only for a ProcessGroup and not for a Combined Process.

  18. Gray Box - Example • Example from Pre-Press

  19. MIS Requirements

  20. MIS and JDF/JMF • JDF = Replacement for “Paper job ticket” • JMF and Audits = Replacement for “Shop floor data collection” • Shop floor data collection • Staff time and attendance • Job costing • Work in progress (WIP) • Equipment utilisation statistics

  21. 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

  22. JMF vs. Audits • Audits are only available for jobs • = Productive time • JMF can be used for job related time • = Productive time • Audits are the only accurate source of data • The reason for JDF snapshots in JMF • JMF only way to record non-job related time • = Non-Productive time

  23. 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 company’s profitability • Used by accountants and auditors • Must be very accurate • close enough != good enough • The reason for Audit snapshots in JMF!

  24. MIS / Production Interaction • Base+MIS-ICS Level 1 (Job Tickets Only) • Job submission • Returned JDF with Audits • Base+MIS-ICS Level 2 (adds Job Tracking) • JMF Status Signals / JDF Snapshots • Base+MIS-ICS Level 3 (adds Job Costing) • Full Audits in JDF Snapshots and Returned JDF • More detailed Status Signals

  25. MIS / Production Interaction • Not in ICS yet • Change order submission • Scheduling of jobs • On going work in MIS Working Group • Please join working group meetings • Here in Heidelberg: • Wed 26-Jan 9:00 - 12:00, Thu 27-Jan 14:00 - 16:00 • Webex: 2nd and 4th Thursday 16:30 CET

  26. JMF Status Signals • Complete record of device time • Create JMF when: • Device is switched on • Every status change (begin of new phase) • Idle [-> Setup] -> Running [-> Cleanup] -> 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

  27. JMF Status Signals • JMF - Base-ICS Table 20 • Each JMF Status Signal has a JMF “container” <JMF ID=“…” Version =“1.2” SenderID=“your_sender_controller/device_id” xmlns=“http://www.CIP4.org/JDFSchema_1_1” xmlns:xsi=“http://www.w3.org/2001/XML-Schema-instance” TimeStamp=“yyyy-mm-dd hh:mm:ssZ”> • “TimeStamp” is UTC date and time of message • Each <JMF> “container” MUST have 1 or more <Signal> nodes (from the same SenderID)

  28. JMF Status Signals • Signal - MIS-ICS Table 29 • Data Collection uses Status Signals <Signal ID=“…” refID=“…” Type=“Status” xsi:type=“SignalStatus” Time=“yyyy-mm-dd hh:mm:ssZ”> • “refID” is ID of Query that triggered Signal • “xsi:type” allows XML Validation of message • “Time” is UTC date and time of event • Each <Signal> MUST contain 1 or more <DeviceInfo> nodes

  29. JMF Status Signals • DeviceInfo - MIS-ICS Table 30 • One DeviceInfo per Device that is reporting <DeviceInfo DeviceOperationMode=“Productive” DeviceStatus=“Running” StatusDetails=“Good” ProductionCounter=“nnn” Speed=“nnn” TotalProductionCounter=“nnn”> • Indicates the status of the Device • Quantity fields only for quantity aware devices

  30. JMF Status Signals • DeviceInfo - MIS-ICS Table 30 • Each <DeviceInfo> contains: • 1 <Device> node (MUST) • 1 or more <Employee> nodes (conditional MUST) • 0 or more <JobPhase> nodes (conditional MUST)

  31. JMF Status Signals • Device - MIS-ICS Table 31 • Identifies the device <Device DeviceID=“….”/> • “DeviceID” MUST be unique in the print shop’s workflow (across all workflow systems in pre-press, press and post press)

  32. JMF Status Signals • Employee - MIS-ICS Table 32 • Identifies the device operator(s) <Employee PersonalID=“…” Roles=“Operator”/> <Employee PersonalID=“…” Roles=“Assistant”/> • “PersonalID” is the staff code / employee number • “Roles” specifies the task of the operator • “Operator” - Main device operator • “Assistant” - Extra staff assisting the Operator

  33. JMF Status Signals • JobPhase - MIS-ICS Table 33 • Identifies the job(s) in the queue of the device <JobPhase JobID=“…” JobPartID=“…” Status=“InProgress” StatusDetails=“Good” StartTime=“…” PhaseStartTime=“…” TotalAmount=“…” Amount=“nnn” Waste=“…” PhaseAmount=“nnn” PhaseWaste=“…”> • Quantity fields only for quantity aware devices • Each <JobPhase> can contain <JDF> snapshot

  34. JMF Status Signals • JDF snapshot (1) • 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 • JDF snapshot is only available mechanism to get accurate costs for jobs that have not yet been returned to MIS

  35. 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”

  36. Thank You

More Related