Implementation Plan for XML Support for Riordan Mfg



Implementation Plan for Adding

XML Support to Riordan Manufacturing's Operations

Service Request SR-rm-020

1

Learning Team A

WEB/431: XML

University of Phoenix

February 25, 2009

Abstract

This paper proposes an implementation process model for integrating eXtensible Markup Language (XML) into Riordan Manfacturing's operations. This paper describes the XML characteristics for defining the Data Type Definition (DTD) to be used with XML in the inter-organizational exchange of information between Brooks Chemical Supply, Huffman Trucking, and Bickford Organic Juices. Team A also discusses the process of defining DTD(s) and producing the XML documents by providing a high-level information flow diagram that displays the basic exchange of information between the above-mentioned organizations and demonstrates how XML can be incorporated the process.

Executive Summary

Riordan Manufacturing is a Fortune 1000 enterprise that employs 550 people throughout its facilities in California, Georgia, Michigan, and China. Riordan is an industry leader in the field of plastic injection molding and its products include plastic bottles, fans, heart valves, medical stents, and custom plastic parts. Riordan’s major customers include automotive parts and aircraft manufacturers, the Department of Defense, beverage makers and bottlers, and appliance manufacturers.

This implementation plan was developed in response to a request made by Maria Trinh, in Service Request SR-rm-020 to devise a detailed plan to use XML in tracking orders and shipments of raw materials and finished products throughout Riordan's supply chain. Adding affordable, efficient, and reliable XML support to the databases of Riordan Manufacturing, Brooks Chemical Supply, Bickford Organic Juices, and Huffman Trucking will allow Riordan to track shipments and orders. This implementation plan will enable Riordan’s management and its stakeholders to make a determination as to how to best accomplish these goals.

Objectives of XML Implementation

The objectives in implementing XML into Riordan's order processing operations include directly applying the order processing forms to an Internet-based environment, adding the capability of cross-platform functionality, providing for easy development for future growth and easy-to-read documents that are clearly understood, quick production of new and expanded documents, and the capability to support widely-used software applications. With the implementation of XML, DTDs or schemas can be designed in order to develop a standard in the order processing documents across Riordan, Bickford Organic Juices, Brooks Chemical, and Huffman Trucking. Below is a high-level information flow diagram that provides a visual representation of the ordering process across these organizations.

[pic]

Figure 1. High-Level Information Flow Diagram

Supported Functionality

HTML

Although ideally every device and computer supports XML, it can be difficult if not impossible to display all the information required with plain XML. For those devices that cannot support XML, it will be necessary to provide backwards compatibility for these legacy browsers for at least a few years. The benefit of using HTML is the ability to port the XML functionality with little overhead to devices like cell phones and PDA’s. This allows shipments to be tracked without complicated equipment, reducing operating costs. An example of this is FedEx, allowing customers to track packages and see who signed for them using Bluetooth enabled PowerPads (Carter, R., 10/1/2007.) Rather than developing unique application for small devices, HTML allows users to work with technology that is already available and ready for use. Separating the content from the presentation is an extremely effective technique that improves the content and the appearance of a document because it allows the database administrators, programmers, and designers to work more independently of one another. Several technologies are available that can help leverage this functionality. 



allows XML and database applications to be developed in a host of languages like Visual Basic or C#. The unique part of the development process is automatically detects the type of browser that is requesting the data and tailors that data to a format that the browser understands. needs to be hosted by Microsoft software primarily, so it runs on Windows Server 2000, Windows Server 2003, XP Professional and Vista, which should be fine because the main San Jose office supports Windows Servers. In addition, .NET itself has many aspects to combine XML technology with data integration both with databases and communications with external systems. XML functionality is supported for a database in the format of a "typed dataset" this is an object in memory that is generated from an XSD. It allows the application easily to parse and create XML from that format and store or retrieve it from the database. For communications built into the technology is SOAP, a communication protocol standardized with XML. Program class objects can be serialized (broken down into a transmittable or storable format) with built in technology such as SOAP for sending information, or by writing custom formats with built in program objects such as XMLTextWriter or XMLDocument. The technology also provides many ways to consume XML documents with multiple ways to read and parse data, validate them with XSD, or even transform them with XSLT. 

XSLT

XSLT is a method of transferring or transforming an XML file to another XML file, or an HTML file so the user can read the file. Although XSLT can be run from the client side, a great many browsers do not completely support the specification, and it may be impossible for small devices to process. A solution to this dilemma is running the XSLT on the server side. This is possible through the apache software foundation, with added functionality supported by Java. This allows XML to be viewed effortlessly on a variety of small devices.

Design of the Data

The simplicity of XML can be deceiving, in the past companies jumped right into designing DTDs without putting a great deal of thought into the actual design. Many of these companies needed to go back to the drawing board and start the design process again because the data models initially design were not robust enough to accommodate the changing business. Riordan is a prime example of a company that changes extensively over time so a proper design needs to be created with this in mind.

  XML is a relatively new technology, so little information is available to reference on how to create a good working model. Although much experience can be gained through the relational model and concepts such as object oriented programming, the modeling process is mostly theoretical, and grappling with XML data model can be difficult for both programmers and database designers. A way to get past this is to do research and see if current models are already being designed and implemented; the and xml. websites, for example, provide information for various industries.

Three major categories of data design exist (Birbeck, M., 2004):

• Information modeling – understanding the information that will be carried in documents: its structure and meaning

• Document design – how the information model is translated into XML documents

• Creating Schemas – which allow the user to record document design so that processing applications and other users can work with the schema.

Information Modeling

Information modeling is a process of determining what information interactions need to occur in order to complete a task. Modeling is not a description of a database but a basis for the development of a database. This step is completely technology independent and could describe a process that is done on paper, over the phone, or in XML. There are several ways to model data: IDEF1X, Entity-Relationship (ER) (Chen) Diagramming, or Information Engineering (IE), for example.

Document design

In this step schema creation can be started while observing the importance of creating sample documents of the data that was modeled in the last step based on what the function of the document is. Is the document going to be used for sending messages? Is it used for an archive or is it being entered into a database? These are questions that should be asked so a functional document design can be created. Critical consideration must also be given to the fact that many documents will be limited by the same schemas.

Creating Schemas

Schemas are a way of defining quality control for the data that is going to be passed in and out of the system. They are what define the difference between a good document and bad document. This can serve 2 purposes, to serve as a structure that defines the company, and define the structure of a document so that it meets at least the minimum requirements for its purpose. Having too many constraints can cause problems down the road if the model is too rigid to facilitate change, as mentioned earlier.

Description of Process Logic

In order to properly develop an XML solution for Riordan’s order and shipment tracking system, the relationships and flow of data within the process must be identified and analyzed. The focal point of process logic in this project is, for the sake of analysis, Riordan’s Albany Georgia beverage and container plant. For the purposes of this review, Team A assumes that Albany order processing and shipment tracking is handled onsite via their Manufacturing Resource Planning (MRP II) system. Team A also assumes that this analysis will exclude process logic between Riordan’s San Jose headquarters and the Albany site.

Resource and production planning for the manufacture of plastic bottles for Bickford Organic Juices is assumed based upon a “pull” demand system. In other words, all plastic bottle production for Bickford is initiated by Bickford, Riordan does not inventory bottles to fill Bickford orders. By agreement with Riordan, Bickford has committed to participate in the plan to incorporate a comprehensive order and shipment tracking system. Therefore, process logic for a Bickford bottle order begins with order creation at the Bickford plant. Through the use of XML and attached document type definition, order creation conforms to a predefined data structure that ensures accuracy and compatibility with Riordan’s order handling system. Once the order is transmitted by Bickford and received by Riordan, order conformance to data design requirements is validated by receipt processing within the MRP II system.

The validated order then generates two new process flows. The first is an order confirmation document which is designed by data type definition to be compatible with Bickford’s order creation system. The second process flow is a query to Riordan’s plastic pellet inventory database. The inventory query is generated in the form of a production order with conditional formatting. Once the inventory query is resolved, one of two new process flows begins.

If the pellet inventory is insufficient to produce the bottles ordered, then an order is automatically generated to Brooks Chemical for the required pellets. Once again, by agreement with Riordan, Brooks is participating in the comprehensive order and shipment tracking system that Riordan has initiated. To comply with the requirements of Books’ ordering system, the Riordan generated pellet order will be XML-based with data typing to ensure that order is complete and coherent. Once the order from Riordan is validated, a data type validated order confirmation is transmitted back to Riordan. Concurrent with order confirmation to Riordan, a shipping service request is generated and transmitted to Huffman trucking.

Huffman Trucking schedules the shipment of pellets from Brooks to Riordan and generates a manifest that is transmitted to Brooks and Riordan. Once again, all documents exchanged by Brooks, Huffman, Riordan, and Bickford are validated XML documents that ensure compatibility with the recipient data processing systems as well as completeness and accuracy. The manifest transmission to Brooks is forwarded to Riordan and held in a suspense key at Brooks for confirmation of shipment receipt from Riordan.

Upon receipt of the pellet shipment Riordan generates receipt notices to Brooks and internally to the order processing system. The order processing system now releases the bottle production order through the inventory control system which resolves the pellet inventory query and forwards the production order to the shop floor so that production can begin. Upon production fulfillment of the Bickford order a shipment request is generated to Huffman trucking and simultaneously, Riordan’s order processing and production scheduling system is updated via a production complete notice. Within the process flow of the production completion notice Riordan auto generates a notice to Bickford advising them of the status of their order.

Huffman Trucking schedules bottle pickup from Riordan and delivery to Bickford based upon the notification auto generated by Riordan. A validated XML manifest document is generated and transmitted to Bickford and Riordan advising them of the shipment details. The manifest document is held in suspense at Huffman pending confirmation of receipt from Bickford and completed when confirmation is received.

Bickford bottle receipt triggers the final information process flows of this order transaction. Order receipt confirmation is transmitted to Riordan and Huffman. Both Riordan and Huffman process the order receipt information and close out their respective production and shipping orders. Riordan’s completed production record process also generates a shipment complete notice that is transmitted to Bickford along with billing information.

As stated at the outset of this section, all information flow between Riordan, Bickford, Brooks, and Huffman is based upon careful design and validation of the documents that are transmitted between the companies. By controlling the data that is exchanged and validating the documents upon receipt, Riordan realizes the goal of an order and shipment tracking system that is accurate and current at all times.

See Appendix A: DTD Documents for DTD documents, Appendix B: XML Documents, and Appendix C: Cascading Style Sheets for the proposed XML documents. Two sets have been created to provide a choice between in the Web layout, and Figure 1 and Figure 2 are screen captures of the two available designs.

[pic]

Figure 1. Riordan Manufacturing Order Information screen option 1.

Figure 2. Riordan Manufacturing Order Information screen option 2.

Conclusion

XML is increasingly becoming a standard in data exchange between and within organizations. Many organizations and departments can be involved in setting XML-related standards and because existing DTDs can be incorporated, developing XML support will allow for future growth and adaptation across Riordan Manufacturing as well as across organizations that Riordan does business with as well. By using the system outlined in this paper, processing and tracking incoming and outgoing orders can be seamless across departments and platforms internal to Riordan Manufacturing as well as compatible with external organizations such as Bickford Organic Juices and Brooks Chemical Supply to include the transport of orders via Huffman Trucking.

References

Apollo Group, Inc. (2004). Information regarding Riordan Manufacturing. Retrieved Febuary 25, 2009, from University of Phoenix Virtual Organizations Portal:

Apollo Group, Inc. (2006). Riordan Manufacturing. Information Technology – San Jose, Ca.. Retrieved February 19, 2009. WEB/431 - XML.

/aapd/CIST/VOP/Business/Riordan/IT/RioITNetwork002.htm

Birbeck, M. (2004) Professional XML (2nd ed. Chapter 14) APress. New York

Carter, R. (10/1/2007.) Delivering Innovation. (Vol. 21 Issue 1, p44-44, 1/4p) CIO. Retrieved February 24, 2009 from EBSCOHost.

 

Meloan, S. (April 2001) The Jakarta Taglibs Project-- Part I. Retrieved February 25, 2009 from

Appendices

Appendix A: DTD Documents

Orders.dtd

Orders2.dtd

InventoryUpdate.dtd

Appendix B: XML Documents

custOrders.xml

Riordan Manufacturing Order Information

Bickford Organic Juices

11/01/2004

11:45:05

Item ID

Item Type

Description

Quantity

Shipping Status

Shipping Date

True

RMFG176a

CPHalf

Clear Plastic Bottles 1/2 Liter

20000

Shipped

10/23/2006

Removed

Shipping Information

Shipping Billing Order ID: B123586

Truck Number: 213513

Ship Date: 10/23/2006

Shipping Company: Huffman Trucking

True

recdOrders.xml

Riordan Manufacturing Raw Materials Order Information

Brooks Chemical Supply

10/21/2004

12:52:07

Item ID

Item Type

Description

Quantity

Shipping Status

Shipping Date

True

BCHEM012

CPPel02

Pellets for clear Plastic Bottles

8 cs

Received

10/23/2006

Added

Receiving Information

Shipping/Receiving Supervisor: Jim Smith

Truck Number: 173427

Date Received: 10/23/2006

Shipping Company: Huffman Trucking

Status: Unloaded

True

custOrders2.xml

Riordan Manufacturing Order Information

Bickford Organic Juices

11/01/2004

11:45:05

True

Removed

Order Information

Item ID: RMFG176a

Item Type: CPHalf

Description: Clear Plastic Bottles 1/2 Liter

Quantity: 20000

Shipping Status: Shipped

Shipping Date: 10/23/06

Shipping Information

Shipping Billing Order ID: B123586

Truck Number: 213513

Ship Date: 10/23/2006

Shipping Company: Huffman Trucking

True

recdOrders2.xml

Riordan Manufacturing Raw Materials Order Information

Brooks Chemical Supply

10/21/2004

12:52:07

True

Added

Order Information

Item ID: BCHEM012

Item Type: CPPel02

Description: Pellets for clear Plastic Bottles

Quantity: 8 cs

Shipping Status: Received

Shipping Date: 10/23/06

Receiving Information

Shipping/Receiving Supervisor: Jim Smith

Truck Number: 173427

Date Received: 10/23/2006

Shipping Company: Huffman Trucking

Status: Unloaded

True

InventoryUpdate.xml

True

CPHalf

50000

Clear Plastic Bottle 1/2 Liter

Added

CPPel02

200000

Pellet for Clear Plastic Bottle

Removed

Appendix C: Cascading Style Sheets

Orders.css

Order {

width: 620;

font-size: 12pt;

}

/* all elements appear in blocks unless designated otherwise */

* {display: block}

/* hidden elements */

IsInventoryUpdated, ItemAction, IsValid {display: none}

DateTime {

position: absolute;

top: 0px;

left: 590pt;

font-size: 8pt;

}

Heading {

font-family: Arial, Helvetica, sans-serif;

font-size: 20pt;

font-weight: bold;

text-align: center;

margin-top: 20pt;

margin-left: 5pt;

margin-right: 5pt;

border-bottom: 2px solid maroon;

}

Customer {

font-family: Arial, Helvetica, sans-serif;

font-size: 14pt;

font-style: italic;

text-align: center;

margin-top: 5pt;

margin-bottom: 10pt;

}

Titles {

font-size: 10pt;

margin-bottom: 10;

}

Column {

display: inline;

color: maroon;

text-decoration: underline;

}

Column[id="1"] { position: relative; left: 40pt;}

Column[id="2"] { position: relative; left: 110pt;}

Column[id="3"] { position: relative; left: 190pt;}

Column[id="4"] { position: relative; left: 260pt;}

Column[id="5"] { position: relative; left: 285pt;}

Column[id="6"] { position: relative; left: 310pt;}

OrderInfo { display: inline }

Orders {

display: inline;

font-size: 10pt;

}

ItemID {

display: inline;

position: relative;

left: 40pt;

}

ItemType {

display: inline;

position: relative;

left: 100pt;

}

ItemDescription {

display: inline;

position: relative;

left: 150pt;

}

ItemQuantity {

display: inline;

position: relative;

left: 190pt;

}

ShippingStatus {

display: inline;

position: relative;

left: 240pt;

}

StatusDate {

display: inline;

position: relative;

left: 285pt;

}

SInfoTitle {

font-size: 10pt;

font-style: italic;

}

SName {

display: inline;

color: maroon;

font-variant: small-caps;

}

ShippingInformation {

width: 300;

background-color: rgb(255,243,209);

border: 1 solid black;

padding: 5pt;

font-family: Arial, Helvetica, sans-serif;

margin-top: 20pt;

margin-left: 20pt;

margin-right: 450pt;

}

SInfo {

display: list;

list-style: square inside;

color: teal;

font-size: 8pt;

}

Orders2.css

Order { width: 620pt;

font-size: 12pt;

}

/* all elements appear in blocks unless designated otherwise */

* {display: block}

/* hidden elements */

IsInventoryUpdated, ItemAction, IsValid {display: none}

DateTime {

position: absolute;

top: 0px;

left: 450pt;

font-size: 8pt;

}

Heading {

font-family: Arial, Helvetica, sans-serif;

font-size: 18pt;

font-weight: bold;

text-align: center;

margin-top: 20pt;

margin-left: 5pt;

margin-right: 5pt;

border-bottom: 2px solid maroon;

}

Customer {

font-family: Arial, Helvetica, sans-serif;

font-size: 14pt;

font-style: italic;

text-align: center;

margin-top: 5pt;

margin-bottom: 10pt;

}

OInfoTitle {

font-size: 14pt;

font-weight: bold;

text-align: center;

}

OName {

display: inline;

color: black;

font-family: Arial, Helvetica, sans-serif;

font-variant: small-caps;

font-weight: bold;

}

OrderInfo {

width: 450pt;

background-color: ivory;

padding: 5pt;

font-family: Arial, Helvetica, sans-serif;

font-size: 12pt;

margin-top: 20pt;

margin-left: 10pt;

}

OInfo {

display: list-item;

color: black;

font-family: Times New Roman, serif;

font-size: 12pt;

}

SInfoTitle {

font-size: 10pt;

font-style: italic;

}

SName {

display: inline;

color: maroon;

font-variant: small-caps;

}

ShippingInformation {

width: 300pt;

background-color: rgb(255,243,209);

border: 1pt solid black;

padding: 5pt;

font-family: Arial, Helvetica, sans-serif;

margin-top: 20pt;

margin-left: 20pt;

margin-right: 450pt;

}

SInfo {

display: list-item;

list-style: square inside;

color: teal;

font-size: 8pt;

}

-----------------------

1

13

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download