Mattec PMC - Revision history

Paulreed: /* Resources */

2011-03-07T02:42:32Z

Resources

← Older revision		Revision as of 21:42, 6 March 2011
Line 25:		Line 25:

	===Resources===		===Resources===
	[[File:mattec.~~ppt~~]]		[[File:mattec.pdf]]
	*Back to [[Waddington North America]]		*Back to [[Waddington North America]]

Paulreed at 02:36, 7 March 2011

2011-03-07T02:36:07Z

← Older revision		Revision as of 21:36, 6 March 2011
Line 22:		Line 22:
	*But machine cycle doesn’t account defects or a misfiring of the resin in to mold so counts needed to be verified and adjusted in Mattec before the export to IFS. (called a shift related export in powerpoint presentation which can be provided		*But machine cycle doesn’t account defects or a misfiring of the resin in to mold so counts needed to be verified and adjusted in Mattec before the export to IFS. (called a shift related export in powerpoint presentation which can be provided

	*IFS consultants good. More or less on time and on budget		*IFS consultants good. More or less on time and on budget.

			===Resources===
			[[File:mattec.ppt]]
	*Back to [[Waddington North America]]		*Back to [[Waddington North America]]

Paulreed at 01:13, 2 March 2011

2011-03-02T01:13:35Z

← Older revision		Revision as of 20:13, 1 March 2011
Line 3:		Line 3:
	Mattec was first implemented at the [[CIND]] prior to 2002 but was never developed and fell out of use. It received a new lease of live when a significant investment was made to reimplement the product in CIND and LANC. At CHLM the decision was made to continue to the Production Process MES system for the foreseeble future.		Mattec was first implemented at the [[CIND]] prior to 2002 but was never developed and fell out of use. It received a new lease of live when a significant investment was made to reimplement the product in CIND and LANC. At CHLM the decision was made to continue to the Production Process MES system for the foreseeble future.

	Objective: 1 calculation of machine efficiencies/ scrap reprting/ earned hours /scrap & scheduled and unscheduled downtime reporting. Shop Floor Machine Loading (not possible to do in IFS given our routing set up. A product can run on one or multiple machines and mold sizes		==Objective: ==
	Vendor selection. We run Production Process and old disused version of Mattec - These are primarily focused on the Plastics industry		*1 calculation of machine efficiencies/ scrap reprting/ earned hours /scrap & scheduled and unscheduled downtime reporting. Shop Floor Machine Loading (not possible to do in IFS given our routing set up. A product can run on one or multiple machines and mold sizes
			*Vendor selection. We run Production Process and old disused version of Mattec - These are primarily focused on the Plastics industry

	So install Mattec and interface Upload IFS Shop Orders/Parts/Routings/Tools(Mold Cavities) to Mattec. Download Production receipts		*So install Mattec and interface Upload IFS Shop Orders/Parts/Routings/Tools(Mold Cavities) to Mattec. Download Production receipts

	2. Overview - (Non IFS) Install server on the network wire the MIU's to the MES hardware - to count machine cycles - takes a while to set up test and get stable and maintain connectivity especially with heavy machinery		*Overview - (Non IFS) Install server on the network wire the MIU's to the MES hardware - to count machine cycles - takes a while to set up test and get stable and maintain connectivity especially with heavy machinery
	3. Overview IFS - Wanted to do the transactions via XML through the ES but Mattec would only accept ASCII. We also wanted to do this cheaply as it was only a once a day transaction (First quote from IFS was $40K)		*Overview IFS - Wanted to do the transactions via XML through the ES but Mattec would only accept ASCII. We also wanted to do this cheaply as it was only a once a day transaction (First quote from IFS was $40K)
	a. Had IFS write SQL statements to extract the data to a file that was then sent to the Mattec server via a custom event once a day. Some logic to prevent overwriting file before upload to IFS		*a)Had IFS write SQL statements to extract the data to a file that was then sent to the Mattec server via a custom event once a day. Some logic to prevent overwriting file before upload to IFS
	b. For the import treated the Mattec server as a kind of bar-code reader transaction and convert the ASCII file in to XML into ES and then IFS		*b). For the import treated the Mattec server as a kind of bar-code reader transaction and convert the ASCII file in to XML into ES and then IFS
	c. Purchased Bar-Code connector and two BIZApi's (Shop Order receipt/Production schedule receipt		*c. Purchased Bar-Code connector and two BIZApi's (Shop Order receipt/Production schedule receipt
	d. Avoided any customization of Mattec system which provided a lot more control of the solution		*d. Avoided any customization of Mattec system which provided a lot more control of the solution
	e. Used Crystal reports to develop the reports via ODBC driver		*e. Used Crystal reports to develop the reports via ODBC driver

	Outcome		===Outcome===
	4 months to install and interface MES to IFS at one site. New site going live this summer		*4 months to install and interface MES to IFS at one site. New site going live this summer
	Upload to Mattec works well		*Upload to Mattec works well. Download is problematic operationally. We report cases so Cases = machine cycles X mold cavity/Parts per box
	Download is problematic operationally. We report cases so Cases = machine cycles X mold cavity/Parts per box		*But machine cycle doesn’t account defects or a misfiring of the resin in to mold so counts needed to be verified and adjusted in Mattec before the export to IFS. (called a shift related export in powerpoint presentation which can be provided
	But machine cycle doesn’t account defects or a misfiring of the resin in to mold so counts needed to be verified and adjusted in Mattec before the export to IFS. (called a shift related export in powerpoint presentation which can be provided

	IFS consultants good. More or less on time and on budget		*IFS consultants good. More or less on time and on budget

	*Back to [[Waddington North America]]		*Back to [[Waddington North America]]

Paulreed at 01:11, 2 March 2011

2011-03-02T01:11:02Z

← Older revision		Revision as of 20:11, 1 March 2011
Line 2:		Line 2:

	Mattec was first implemented at the [[CIND]] prior to 2002 but was never developed and fell out of use. It received a new lease of live when a significant investment was made to reimplement the product in CIND and LANC. At CHLM the decision was made to continue to the Production Process MES system for the foreseeble future.		Mattec was first implemented at the [[CIND]] prior to 2002 but was never developed and fell out of use. It received a new lease of live when a significant investment was made to reimplement the product in CIND and LANC. At CHLM the decision was made to continue to the Production Process MES system for the foreseeble future.

			Objective: 1 calculation of machine efficiencies/ scrap reprting/ earned hours /scrap & scheduled and unscheduled downtime reporting. Shop Floor Machine Loading (not possible to do in IFS given our routing set up. A product can run on one or multiple machines and mold sizes
			Vendor selection. We run Production Process and old disused version of Mattec - These are primarily focused on the Plastics industry

			So install Mattec and interface Upload IFS Shop Orders/Parts/Routings/Tools(Mold Cavities) to Mattec. Download Production receipts

			2. Overview - (Non IFS) Install server on the network wire the MIU's to the MES hardware - to count machine cycles - takes a while to set up test and get stable and maintain connectivity especially with heavy machinery
			3. Overview IFS - Wanted to do the transactions via XML through the ES but Mattec would only accept ASCII. We also wanted to do this cheaply as it was only a once a day transaction (First quote from IFS was $40K)
			a. Had IFS write SQL statements to extract the data to a file that was then sent to the Mattec server via a custom event once a day. Some logic to prevent overwriting file before upload to IFS
			b. For the import treated the Mattec server as a kind of bar-code reader transaction and convert the ASCII file in to XML into ES and then IFS
			c. Purchased Bar-Code connector and two BIZApi's (Shop Order receipt/Production schedule receipt
			d. Avoided any customization of Mattec system which provided a lot more control of the solution
			e. Used Crystal reports to develop the reports via ODBC driver

			Outcome
			4 months to install and interface MES to IFS at one site. New site going live this summer
			Upload to Mattec works well
			Download is problematic operationally. We report cases so Cases = machine cycles X mold cavity/Parts per box
			But machine cycle doesn’t account defects or a misfiring of the resin in to mold so counts needed to be verified and adjusted in Mattec before the export to IFS. (called a shift related export in powerpoint presentation which can be provided

			IFS consultants good. More or less on time and on budget

	*Back to [[Waddington North America]]		*Back to [[Waddington North America]]

Paulreed at 20:59, 8 February 2011

2011-02-08T20:59:29Z

← Older revision		Revision as of 15:59, 8 February 2011
Line 2:		Line 2:

	Mattec was first implemented at the [[CIND]] prior to 2002 but was never developed and fell out of use. It received a new lease of live when a significant investment was made to reimplement the product in CIND and LANC. At CHLM the decision was made to continue to the Production Process MES system for the foreseeble future.		Mattec was first implemented at the [[CIND]] prior to 2002 but was never developed and fell out of use. It received a new lease of live when a significant investment was made to reimplement the product in CIND and LANC. At CHLM the decision was made to continue to the Production Process MES system for the foreseeble future.

			*Back to [[Waddington North America]]

	[[Category:WNA]]		[[Category:WNA]]
	[[Category:2009]]		[[Category:2009]]
	[[category:Application]]		[[category:Application]]

Paulreed: moved Mattec to Mattec PMC

2011-02-08T20:58:54Z

moved Mattec to Mattec PMC

← Older revision	Revision as of 15:58, 8 February 2011
(No difference)

Paulreed: Created page with "Mattec is a shop floor machine monitoring system primarily for the plastics industry.Each injection molder or themo-molding machine is hooked up to the Mattec Server via a MIU. T..."

2011-02-08T20:57:00Z

Created page with "Mattec is a shop floor machine monitoring system primarily for the plastics industry.Each injection molder or themo-molding machine is hooked up to the Mattec Server via a MIU. T..."

New page

Mattec is a shop floor machine monitoring system primarily for the plastics industry.Each injection molder or themo-molding machine is hooked up to the Mattec Server via a MIU. The Mattec client provides an interface screen that allows the loading of shop floor orders and the counting of machine cycles that equates to the number of products manufactured.

Mattec was first implemented at the [[CIND]] prior to 2002 but was never developed and fell out of use. It received a new lease of live when a significant investment was made to reimplement the product in CIND and LANC. At CHLM the decision was made to continue to the Production Process MES system for the foreseeble future.

[[Category:WNA]]
[[Category:2009]]
[[category:Application]]