21
PROSE vs. PROSE vs. PROSE PROSE What it was Why it didn’t catch on What we did about it Why it will work Who’s committed to using it

PROSE vs. PROSE What it was Why it didn’t catch on What we did about it Why it will work Who’s committed to using it

Embed Size (px)

Citation preview

Page 1: PROSE vs. PROSE What it was Why it didn’t catch on What we did about it Why it will work Who’s committed to using it

PROSE vs. PROSEPROSE vs. PROSE

What it was

Why it didn’t catch on

What we did about it

Why it will work

Who’s committed to using it

Page 2: PROSE vs. PROSE What it was Why it didn’t catch on What we did about it Why it will work Who’s committed to using it

What PROSE Was: What PROSE Was: 1990 - 20001990 - 2000 Computerized production order Industry Standard, IdeAlliance endorsed Supported by contributors– Meredith, Reader’s Digest, more...– RRD– Quad– Quebecor– Perry/Judds

Page 3: PROSE vs. PROSE What it was Why it didn’t catch on What we did about it Why it will work Who’s committed to using it

...What PROSE Was...What PROSE WasEDI Format– Electronic Data Interchange

Directly supported by Prograph– Toolbox–Magpro

Available to all vendors– Impoze, Managing Editor, Proteus

Page 4: PROSE vs. PROSE What it was Why it didn’t catch on What we did about it Why it will work Who’s committed to using it

Why Didn’t It Catch On?Why Didn’t It Catch On?

Ahead of its time?Required significant changes to

workflowNot broad enough to cover all

monthlies, weeklies, SIPs“Frozen,” not easily modifiedNo formalized testingNon-Database Format

Page 5: PROSE vs. PROSE What it was Why it didn’t catch on What we did about it Why it will work Who’s committed to using it

Where Where DidDid it Work? it Work?

Custom Time Inc. DevelopmentConsiderable modifications to

languageProprietary Trading-Partner

deploymentResult is successful EDI but not

easily adaptable to others

Page 6: PROSE vs. PROSE What it was Why it didn’t catch on What we did about it Why it will work Who’s committed to using it

What Did it Look Like?What Did it Look Like?

It wasn’t pretty

Page 7: PROSE vs. PROSE What it was Why it didn’t catch on What we did about it Why it will work Who’s committed to using it

What We Did About It:What We Did About It:2000-20012000-2001Private effort to Redo Language– RRD, Quad, Meredith, Queb, others

Methods and Goals– Rewrite in XML– Test across variety of titles

Release to IdeAlliance for potential adoption

Page 8: PROSE vs. PROSE What it was Why it didn’t catch on What we did about it Why it will work Who’s committed to using it

...What We Did About It:...What We Did About It:20022002Presented to IdeAlliance Members– Review, suggestions, changes

Modified, Improved based on suggestions

February 2003 Rollout– New format appears stable and powerful

Page 9: PROSE vs. PROSE What it was Why it didn’t catch on What we did about it Why it will work Who’s committed to using it

What it Looks Like NowWhat it Looks Like Now

Lipstick on a pig? Or a silk purse...

Page 10: PROSE vs. PROSE What it was Why it didn’t catch on What we did about it Why it will work Who’s committed to using it

Testing Testing

Created live, complex magazine filesFile integrity is built in to XML– (if it’s legible, it’s structured)

Included postal data, edition data, paper, weight, etc.

Thumbs up, ready to roll

Page 11: PROSE vs. PROSE What it was Why it didn’t catch on What we did about it Why it will work Who’s committed to using it

Transition: Transition: Historical AbilityHistorical Ability

Converter written and testedConverts XML to PROSE 1.2Compatible with Prograph Toolbox

Page 12: PROSE vs. PROSE What it was Why it didn’t catch on What we did about it Why it will work Who’s committed to using it

Benefits: PublishersBenefits: Publishers

Error reduction– No re-keyboarding at plant

Later closingClosed-loop production dataNo more bushel-basket instructionsCoordination among vendors

Page 13: PROSE vs. PROSE What it was Why it didn’t catch on What we did about it Why it will work Who’s committed to using it

Risks: PublishersRisks: Publishers

Publishers often rely on vendors to fix messes

Data must be completeErrors might obviously be your own

fault

Page 14: PROSE vs. PROSE What it was Why it didn’t catch on What we did about it Why it will work Who’s committed to using it

Benefits: PrintersBenefits: Printers

Reallocate time spent re-keying dataFewer mistakes, opportunities for

make-goodsIntegrated, digital workflowUniformity among customers

Page 15: PROSE vs. PROSE What it was Why it didn’t catch on What we did about it Why it will work Who’s committed to using it

Risks: PrintersRisks: Printers

Very few risksPrinters are accustomed to digital

workflows

Page 16: PROSE vs. PROSE What it was Why it didn’t catch on What we did about it Why it will work Who’s committed to using it

The Big Picture: The Big Picture: PROSE XML Interface to...PROSE XML Interface to...

CDS, EDS, TCS, etc.USPSWholesalersImage ManagementAd Sales DatabasePrinter’s job control system

Page 17: PROSE vs. PROSE What it was Why it didn’t catch on What we did about it Why it will work Who’s committed to using it

What to Do NextWhat to Do Next

Prepare to Digitize Production– Get rid of the pencils

Cross-Departmental Involvement– Electronic production data involves all

departmentsEat Change for Breakfast– Automation of this magnitude will

change your entire operation

Page 18: PROSE vs. PROSE What it was Why it didn’t catch on What we did about it Why it will work Who’s committed to using it

Who’s Going First? Pubs...Who’s Going First? Pubs...

Meredith– Participated in PROSE development

since 1989 and isn’t giving up nowGruner + Jahr– Coordinating and automating all

production data– First postal-certified staff members for

PAGE integration

Page 19: PROSE vs. PROSE What it was Why it didn’t catch on What we did about it Why it will work Who’s committed to using it

Who’s Going First? Printers...Who’s Going First? Printers...

RRD building DIMs system around XML including PROSE

Quad plans to request PROSE from customers to feed job control

Brown, Perry/Judds, Quebecor all moving toward XML

Page 20: PROSE vs. PROSE What it was Why it didn’t catch on What we did about it Why it will work Who’s committed to using it

R.O.I.?R.O.I.?

Standards create R.O.I.Cycle time reductionMore Productivity (use your

imagination)Closed-loop production data for all

parties

Page 21: PROSE vs. PROSE What it was Why it didn’t catch on What we did about it Why it will work Who’s committed to using it

PROSE XMLPROSE XML

It’s ready. Let’s rock.It’s ready. Let’s rock.