Connection Requirements Specification
Connection Requirements Specification... 1 GEC HUB... 1 1. General... 4 1.1 INTRODUCTION... 4 1.1.1 ANX Connectivity Method...4 1.1.2 VAN Connectivity Method...4 1.1.3 WAM Connectivity Method...5 2.0 Setup and Connection Requirements... 5 2.1 ANX IMPLEMENTATION... 5 2.1.1 ANX Vendor Selection...5 2.1.2 IPSEC Vendor Selection...5 2.1.3 Customer Registration with the ANX Overseer...5 2.1.4 Customer Contract with ANX Certified Service Provider...6 2.1.5 Request Tunnel with Ford for ANX...6 2.1.6 Submit Ford EDI Connection Request Form...6 2.1.7 GSDB Code...6 2.1.8 Testing...7 2.1.9 Additional Information...7 2.1.9.1 Firewall rules request to GSEC...7 2.1.9.2 Firewall rules at vendor site...7 2.1.9.3 Static routes added to Ford router...7 2.1.10 ANX Process Summary...8 2.1.11 ANX Work Plan...9 2.2 VAN IMPLEMENTATION...11 2.2.1 VAN Vendor Selection...11 2.2.2 VAN Mailbox Setup...11 2.2.3 VAN Confirmation and Connectivity Test...11 2.2.4 Submit Ford EDI Connection Request Form...11 2.2.5 GSDB Code...12 2.2.6 Testing...12 2.2.7 Typical Questions to Ask Your VAN...12 2.2.9 VAN Process Summary...13 2.2.10 VAN Work Plan...14 2.3 WAM IMPLEMENTATION...14 2.3.1 WAM ISP Selection...15 2.3.2 FSP...15 2.3.3 Submit Ford EDI Connection Request Form...15 2.3.4 GECHub/WAM Mailbox Setup...16 2.3.5 WAM Confirmation and Connectivity Test...16 2.3.6 GSDB Code...16 2.3.7 Testing...16 2.3.8 Typical Questions...16 2.3.9 WAM Process Summary...17 2.3.10 WAM Work Plan...18 2.3.11 Addendum 1 WAM Process and Procedures...18 2.3.12 WAM FAQs...20 Page 2 of 21 Date Issued: 04/26/2007
Revision Number Revision History Date Revision Author Description 0.0 06/11/2001 Gordon Draper Draft Release 1.0 02/27/2002 Steve Novotny WAM Section Addition 1.1 6/19/2002 Gordon Draper 2.3 WAM implementation user profile added 1.4 9/19/03 Gordon Draper ANX links and connectivity form information updated. Section 2.3.2 updated tokens no longer required. 1.5 08/18/04 Kathie Jahn Revised 2.1.5 2.1.13 with update ANX Tunnelz information, updated VAN Flow, Added COVISINT to the list of vans. 1.6 05/15/07 Michael Janeczko Removed names, removed links to pages down a URL tree, adjusted spacing. 1.7 06/03/09 Amy Fei Remove IBM Advantis from VAN Connectivity Method 1.8 06/03/09 Amy Fei Correct the VAN connectivity list Page 3 of 21 Date Issued: 04/26/2007
1. General 1.1 Introduction This document addresses the setup requirements for new trading partners / vendors with no previous Electronic Data Interchange (EDI) traffic with the Ford Motor Company. The EDI application and translation exist entirely on the Global Electronic Commerce (GEC) Hub. In particular, the document addresses connectivity requirements for EDI by using an Advanced Network Exchange (ANX) connection, a Value Added Network (VAN) connection, or a Public Internet/ISP Web Access Module (WAM) connection. 1.1.1 ANX Connectivity Method The first method of connecting to the Ford requires an ANX connection for EDI data transfers. Understanding the various ANX service requirements is key to the successful implementation of EDI. The services are as follows: ANX Service Provider (required) IPSEC Security Service Provider (optional) ANX Overseer Group (required) The ANX Service Provider is responsible for providing the ANX circuit and router. Estimate approximately 60 days to get an ANX circuit installed once the circuit is ordered. Add an additional week for some of the post circuit installation implementation steps. This will include filling out and returning to Ford representatives some required documents for establishing a secure tunnel. There are several ANX Certified Service Providers (CSP's). The list of CSP's includes MCI, AT&T, Ameritech, Ideal Technology Solutions, BCE Emergis, Equant Network Services, and Global Crossing. Please reference the http://www.anx.com website for a list of CSPs. These providers typically charge a one-time installation service fee and a monthly ANX service fee w/access. Fees vary by provider. Please check with the CSPs for pricing information. The IPSEC Security Service Provider is responsible for providing additional hardware (if required), software and services for firewall and IPSEC security management. This service is only required if you chose to out-source this operation. The service provider typically charges a one-time IPSEC product installation fee and a monthly IPSEC service fee. Please check with your ANX Service Provider for details. The ANX Overseer Group is responsible for enforcing the Service Level Agreement (SLA) and uptime requirements (99.965% network availability) of the ANX network. As a result, trading partners must pay a onetime fee along with an annual fee. Please reference the http://www.anx.com website for pricing details. 1.1.2 VAN Connectivity Method The second method of connecting to the Ford requires the use of a VAN connection for EDI data transfers. The VAN provides services that are similar to that of an ANX Service Provider and must be registered by the Ford Motor Company. The current list of registered VAN's is as follows: 1.) EasyLink 2.) GE/GXS 3.) Sterling Commerce 4.) Kleinschmidt 5.) COVISINT 6.) iconnect 7.) INOVIS/HARBINGER Page 4 of 21 Date Issued: 04/26/2007
8.) EDS*Elit For more information on registered VAN s, reference the website http://web.gsec.ford.com. Please consult your VAN for details. 1.1.3 WAM Connectivity Method The third method of connecting to the Ford requires the use of a public Internet connection for EDI data exchange. The WAM (Web Access Module) user utilizes a local ISP (Internet Service Provider) to access the GECHub through the Trading Partners FSP (Ford Supplier Network) account. The selection of the ISP is not controlled by Ford Motor Company. For more information on the WAM, reference the website http://web.gsec.ford.com (2.3 WAM Implementation section) 2.0 Setup and Connection Requirements This section of the document outlines the best practices used to setup a trading partner with Ford Motor Company via EDI. 2.1 ANX Implementation To implement an ANX connection, complete sections 2.1.1 through 2.1.9. 2.1.1 ANX Vendor Selection It is up to the trading partner to select their service provider. See the ANX Website http://www.anx.com/ for a current list of ANX CSP's. Trading partners are encouraged to obtain multiple quotes before making a decision. The selection and how it occurs is completely determined by the trading partner. The CSP can help the trading partner determine the amount of bandwidth required for the connection. The adding partner must determine the bandwidth before the ANX registration process can be completed. Trading Partner Action Item Determine bandwidth requirements and select ANX Certified Service Provider 2.1.2 IPSEC Vendor Selection The ANX Service Providers can recommend IPSEC vendors, if your staff needs assistance with this task. The IPSEC vendor addresses firewall administration, security, and encryption. Trading Partner Trading Partner Action Item Select IPSEC Vendor, if required 2.1.3 Customer Registration with the ANX Overseer The Trading Partner will need to register with the ANX as an ANX Trading Partner. Online registration is available through the ANX web site at http://www.anx.com/. The ANX registration form will require the Trading Partner to indicate the connection size and (bandwidth) needed. Once the registration paperwork has been submitted to and processed by the ANX, a trading partner number will be assigned to the Trading Partner. The processing of paperwork and assignment of trading partner number takes a minimum of 10 business days. Trading Partner Action Item Register with ANX Page 5 of 21 Date Issued: 04/26/2007
2.1.4 Customer Contract with ANX Certified Service Provider Since legal issues sometimes need to be resolved between the Trading Partner and the service provider, the signing of an actual contract can sometimes become a bottleneck. The customer must have registered with ANX and must have been assigned a trading partner number before a service provider will process an order. Trading Partner Action Item Sign CSP contract 2.1.5 Request Tunnel with Ford for ANX Once the Trading Partner is fully connected to the ANX network, the Trading Partner should access the GSEC external website and submit one of the following forms indicated on: https://www.suppcomm.ford.com/us/newtunnelproc.asp Assumptions for Internet VPN Users : 1) Trading Partner must already have high-speed internet connection 2) Trading Partner must have the expertise necessary to configure and bring the tunnel up on their end. 3) The only IPSec devices supported by Ford are the Checkpoint Firewall-1 (version4.1 or higher), Cisco PIX firewall or Cisco IOS. Should any other products be selected, the Trading Partner will have The sole responsibility of establishing the tunnel including troubleshooting connectivity problems. 4) This connection is strictly for Gateway-Gateway VPN's. We do not allow client VPN connections. This process created a secure tunnel to Ford's Firewall. A tunnel is an encrypted, authenticated communications path into the Ford Network. Ford and the Trading Partner then exchange a token data packet (between the Firewalls) to enable the secured tunnel. When Ford has completed the tunnel request, Ford will send an acknowledgement to the technical contact listed on the form. Trading Partner Action Item Submit appropriate tunnel request form 2.1.6 Submit Ford EDI Connection Request Form Once the Trading Partner is fully connected to the ANX network, the Trading Partner should access the GSEC external website and submit a " EDI Connection Request " form via the following URL: https://web.gsec.ford.com/gec/mailboxrequest/requesthome.asp The submission will be acknowledged via email back to the EDI analyst named on the form within 24 hours of submission. These requests are processed in sequential order. A Ford EDI Analyst will contact the Trading Partner within 1-8 days to begin the connectivity testing process. At this time the Trading Partner will be expected to begin the testing process. Trading Partner Action Items Submit "EDI Connection Request " form 2.1.7 GSDB Code The Ford buyer will issue a Trading Partners a GSDB code (some Trading Partners may already have several). The GSDB code is used as the ID for the Trading Partner's mailbox when it is created. The GSDB code is often referred to as the Trading Partner, Vendor ID supplier code. To assist Trading Partners in identifying the correct code - Use the Trading Partner/supplier code listed on checks received from Ford Motor Company Check with Trading Partner A/R or Buyer for a Trading Partner/supplier code Trading Partner Action Item - Validate or Obtain a GSDB Code Page 6 of 21 Date Issued: 04/26/2007
2.1.8 Testing Be sure to test the following: Connectivity test to the ANX Network Loop back test to the Complete system test Trading Partner Action Item Perform connectivity test to the ANX Network, Loop back test to the GEC Hub and Complete system test 2.1.9 Additional Information Listed below is some additional information to assist you with firewall rules and routing 2.1.9.1 Firewall rules request to GSEC Ford allows ALL outbound access. Therefore, if Ford initiates access, there are no firewall rules required on the Ford side. If the requirement is for Trading Partner initiated access to a Ford System, the Ford System must be a Properly Administered Host (PAH) and the GSEC team must process this request, ensuring that the appropriate Ford firewall rules are put in place. Depending on the type of access requested, Ford may require the following information: Source IP addresses Destination IP addresses TCP/IP ports required If the destination address is a Ford system (the application request is initiated by the Trading Partner's host), then the Ford system has to be a Properly Administered Host (PAH). The customer on the Ford side should verify that the Ford system is a PAH. If it is not already a PAH, it must meet the PAH requirements and be submitted as a PAH to the appropriate group. 2.1.9.2 Firewall rules at vendor site Ford will supply the Trading Partner or IPSEC vendor with the necessary IP addresses. 2.1.9.3 Static routes added to Ford router If necessary, static routes are configured on either or both sides of the connection. Page 7 of 21 Date Issued: 04/26/2007
2.1.10 ANX Process Summary Select CSP Select Connection Option Select IPSEC Product Register with ANX Visit http://www.anx.com or call 1.877.488.8269 Sign Contracts for Services Complete Installation & Configuration for Circuit and IPSEC Device Complete Subscription Assessment and Pay Fees to ANX ANX Member (Subscribed) Submit the Following Forms to Ford Select Connectivity method from: https://www.suppcomm.ford.com/us/newtunnelproc.asp EDI Connection request https://web.gsec.ford.com/gec/mailboxrequest/requesthome.asp Page 8 of 21 Date Issued: 04/26/2007
2.1.11 ANX Work Plan Task Task Id 1 Select ANX Certified Service Provider (please reference section 2.1.1 for detail) Responsible Prerequisite Duration Organization Task Trading Partner N/A Variable 2 Identify bandwidth requirements (please reference section 2.1.1 for detail) 3 Complete ANX Registration Form and submit to ANX (please reference section 2.1.3 for detail) 4 Negotiate contractual issues (please reference section 2.1.4 for detail) 5 Receive Trading Partner ID from ANX (please reference section 2.1.3 for detail) 6 Submit order for ANX connectivity through CSP (please reference section 2.1.4 for detail) 7 Select IPSEC solution (please reference section 2.1.2 for detail) Trading Partner in N/A Variable conjunction with the Certified Service Provider Trading Partner 1 1 business Trading Partner in conjunction with the Certified Service Provider 8 ANX connectivity configuration Certified Service Provider 9 Fully Subscribed: Full ANX network connectivity installed at Trading Partner site (including IPSEC gateway). Test tunnel to ANX established and working. ** All dedicated ANX customers will need to sign up for ANXtunnelz Service through www.anx.com N/A day Variable Trading Partner 3 7 to 10 business days Trading Partner 3,4 1 business day Trading Partner in 1 Variable conjunction with the Certified Service Provider Certified Service Provider 4 20 40 business days 4,5,8 1 business day 10 Submit tunnel request to Ford via https://www.suppcomm.ford.com/us/newtunnelproc.asp Trading Partner 9 1 business day (Reference section 2.1.5 for detail) 11 Exchange IP and port information with Trading Partner by email or telephone call 12 Complete tunnel request between Ford and Trading Partner 13 Submit EDI Connection Request form to Ford https://web.gsec.ford.com/gec/mailboxrequest/reques thome.asp (Reference section 2.1.6 for detail) Ford, Trading Partner Ford, Trading Partner Ford, Trading Partner 10 1 business day 10,11 2 5 business days 12 Variable Page 9 of 21 Date Issued: 04/26/2007
14 Submit firewall rules for Ford IPSEC gateway to GSEC (needed for Trading Partner initiation only. All traffic initiated by Ford is allowed by default) http://www.eni.ford.com/gsec/supp.asp?id=114 (Reference section 2.1.9 for detail) 15 Complete firewall rules for Ford IPSEC gateway (Reference section 2.1.9 for detail) Ford 12 1 business day Ford 14 2-3 business days Page 10 of 21 Date Issued: 04/26/2007
2.2 VAN Implementation To implement a VAN connection, complete sections 2.2.1 through 2.2.7. 2.2.1 VAN Vendor Selection The Trading Partner will have to select a Ford approved VAN. Trading Partner Action Items Select Ford approved VAN 2.2.2 VAN Mailbox Setup The VAN will create an account and/or mailbox ID(s) and setup Trade relationships with Trading Partner. Trading Partner Action Items Check status of VAN account 2.2.3 VAN Confirmation and Connectivity Test Trading Partner verifies confirmation of mailbox setup with VAN and begins connectivity testing with VAN. Trading Partner Action Items Verify mailbox setup and begin testing 2.2.4 Submit Ford EDI Connection Request Form Once the Trading Partner is fully connected to the VAN network, the Trading Partner should access the GSEC external website and submit a "Ford EDI Connection Request " form via the following URL: https://web.gsec.ford.com/gec/mailboxrequest/requesthome.asp The submission will be acknowledged via email back to the EDI analyst named on the form. These requests are processed in sequential order. A Ford EDI Analyst will contact the Trading Partner within 1-8 business days At this time the Trading Partner will be expected to begin the testing process (send/receive of data across this connection). The form should contain the following key information: Company Name VAN Information Ford Supplier Mailbox Codes Trading Partner Action Items Submit "Ford EDI Connection Request " form Trading Partner Action Items Check status of VAN account and trading partner (i.e. Ford) Page 11 of 21 Date Issued: 04/26/2007
2.2.5 GSDB Code See section 2.1.7 for GSDB Code. Trading Partner Action Item Validate GSDB Code 2.2.6 Testing Be sure to test the following: Connectivity test to the VAN Network Complete system test Trading Partner Action Items - Perform connectivity test to the VAN Network and Complete system test 2.2.7 Typical Questions to Ask Your VAN Listed below are some typical questions in selecting a VAN Do you impose a sign up fee? What is your monthly service fee? What is your fee per mailbox? What is your per character or volume fee? What is your thru-put capability? Page 12 of 21 Date Issued: 04/26/2007
2.2.9 VAN Process Summary Trading Partner selects a Ford approved VAN Trading Partner will establish a trading relationship with VAN VAN will create account and/or mailbox ID(s) and Trade relationships Trading Partner verifies VAN set up and begins connectivity testing with VAN Trading Partner submits "EDI Connection Request" form to https://web.gsec.ford.com/gec/mailboxrequest/requesthome.asp Ford will contact Trading Partner to setup a test date Page 13 of 21 Date Issued: 04/26/2007
2.2.10 VAN Work Plan Task Task Responsible Prerequisite Duration Id Organization Task 1 Select Ford Approved VAN Trading Partner N/A Variable 2 Request an account and/or mailbox ID(s) from the VAN Trading Partner in conjunction with 1 Variable 3 Create account and/or mailbox ID's and setup Trade relationships 4 Send appropriate confirmations to Trading Partner 5 Trading Partner verifies confirmations and conducts connectivity test 6 The "EDI Connection Request " form is submitted on https://web.gsec.ford.com/gec/mailboxrequest/r equesthome.asp VAN VAN in conjunction with Ford 1,2 Variable VAN 3 Variable Trading Partner in conjunction with VAN 4 Variable Trading Partner 6 1 business day 7 Assign an analyst to the test the EDI Ford 7 Variable Connection (please reference section 2.2.4 for detail) 8 Test date notification Ford 9 Variable Note The above work plan takes on average 10-15 business days to complete. 2.3 WAM Implementation Before implementing the WAM solution the following considerations should be taken into account. The WAM, (WEB Access Module) as of this writing, IS NOT AN APPORVED Q1 SOLUTION. Suppliers who are required to obtain, or intend on obtaining, a Q1 rating from Ford Motor Company should not choose the WAM as their primary EDI Solution. The WAM does not fill the requirement of a fully integrated EDI solution. The WAM is intended as a low cost solution for suppliers whose EDI volume is extremely low. While it is hard to specifically quantify, the following criteria could be used. Daily volume of fewer than 10 EDI documents, or 10 ASN with less than 20 parts total. File sizes that range less than 100kb, from tests run it is estimated that 100kb will take approximately 5 minutes to down load. The current process of uploading or down loading documents via the WAM will only accommodate single file transfer. Page 14 of 21 Date Issued: 04/26/2007
When down loading planning releases or ship schedules the file format is UN EDIFACT the guidelines for messages can be found at https://web.gsec.ford.com/gec/edispecs/edispecs.asp Web forms are available for Planning Releases, Ship Schedules, and the ASN only. The view is one part at a time one release or ASN at a time. The forms can be printed from your browser. An FSP (Ford Supplier Network) account is required to implement WAM EDI. The WAM (Web Access Module) is a web interface that communicates with the mailbox system. Suppliers that are setup for the WAM access it via the Ford Supplier Network portal using a standard web browser (Internet Explorer 5.5 or Netscape 4.7) Suppliers need the following setup before they can get to the WAM: 1. FSP account set up through Covisint. 2. mailbox with password hard coded for FSP access. 3. WAM account (with or without web forms). They must visit https://web.gsec.ford.com/gec/mailboxrequest/requesthome.asp in order to request a WAM setup. a. Email to econnect@ford.com for questions concerning WAM setup. 4. Internet account from local ISP (Internet Service Provider) 5. EDI software if not using predefined forms. If after reviewing the above considerations a supplier feels they fit the profile of a WAM user then proceed with the steps to implement the WAM. To implement a Web Access Module (WAM) connectivity solution complete steps 2.3.1 through 2.3.11. 2.3.1 WAM ISP Selection The Trading Partner must select an Internet Service Provider. It does not matter what ISP is selected as Ford Motor Company has no guidelines or requirements for Internet Service Providers. 2.3.2 FSP The Trading Partner MUST have an active FSP (Ford Supplier Portal) account requested by their CSA via: https://fsp.covisint.com/ They must also request an EDI access via the FSP through this website. 2.3.3 Submit Ford EDI Connection Request Form In order for the Trading Partner to be fully connected to via the WAM, the Trading Partner must access the GSEC external website and submit a "Ford EDI Connection Request " form to the following URL: http://web.suppcomm.ford.com. The submission will be acknowledged via email back to the EDI analyst named on the form within 24 hours of submission. These requests are processed in sequential order. A Ford EDI Analyst will contact the Trading Partner within 1-8 business days to test the ability to send/receive data across this connection The form should contain the following key information: Company Name and GSDB Code Page 15 of 21 Date Issued: 04/26/2007
Ford Plant Mailbox Codes WEB EDI with or without forms. Transactions required. (Currently available DELFOR (Material Release/830), DELJIT (Ship Schedule/862), DESADV (ASN/856). Trading Partner Action Items Submit "Ford EDI Connection Request " form Trading Partner Action Items Check status of WAM connectivity (i.e. Ford) 2.3.4 GECHub/WAM Mailbox Setup The Ford Connectivity Team will create an account and/or mailbox ID(s) and setup Trade relationships with Trading Partner and Ford sites. Trading Partner Action Items Check status of WAM account 2.3.5 WAM Confirmation and Connectivity Test Trading Partner verifies confirmation of mailbox setup with Ford Connectivity Team and begins connectivity testing to GECHub via WAM. 2.3.6 GSDB Code See section 2.1.7 for GSDB Code. 2.3.7 Testing Be sure to test the following: Connectivity test to the WAM/ via the FSP portal. Complete system test Trading Partner Action Items - Perform connectivity test via the WAM and complete system test 2.3.8 Typical Questions Do we currently have an FSP (Ford Supplier Network) account necessary to implement WAM EDI functionality? Do we supply Ford Motor Company with less than 20 parts? Do we send no more that 10 ASN's per day to Ford Plant locations? Since the WAM is not considered by the Ford Supplier Performance Group to be an integrated EDI solution (necessary to maintain a Q1 rating) is the negative impact to our current or future Q1 rating an important consideration for our company? Page 16 of 21 Date Issued: 04/26/2007
2.3.9 WAM Process Summary Trading Partner decides they low-volume and fit the profile for WAM EDI Connectivity Trading Partner will establish business relationship with an ISP Trading Partner will request set up EDI Access Token via the FSP Trading Partner submits "EDI Connection Request" form to https://web.gsec.ford.com/gec/mailboxrequest/requesthome.asp Information included will be Company Name, GSDB Code and Ford Plant codes. Ford verifies that Trading Partner "EDI Connection Request" form is complete and sets up Trading Relationships. Ford will contact Trading Partner to setup a test date. Page 17 of 21 Date Issued: 04/26/2007
2.3.10 WAM Work Plan Task Task Responsible Prerequisite Duration Id Organization Task 1 Select Internet Service Provider Trading Partner N/A Variable 2 CSA to request an FSP account (if not in place) Trading Partner in 1 Variable and EDI Access. conjunction with VAN 3 The "EDI Connection Request" form is Trading Partner 1, 2 Variable submitted to http://web.gsec.ford.com 4 Create account and/or mailbox ID's and setup Ford Connectivity 1-3 Variable Trade relationships Team 5 Send appropriate confirmations to Trading Ford Connectivity 1-4 Variable Partner Team. 6 Trading Partner verifies confirmations and requests connectivity test. Trading Partner 1-5 Variable 7 Assign an analyst to the test the EDI Ford 1-6 Variable Connection (please reference section 2.2.4 for detail) 8 Test date notification Ford 1-7 Variable Note The above work plan takes on average 10-15 business days to complete. 2.3.11 Addendum 1 WAM Process and Procedures Brief description: The WAM (Web Access Module) is a web interface to communicate with the mailbox system. Suppliers that are setup for the WAM access it via the Ford Supplier Network portal using a standard web browser (Internet Explorer 5.5 or Netscape 4.7). The WAM allows a user to download their data one transaction at a time and upload their data one file at a time. In general, the business team recommends the WAM be used for suppliers that send no more than 10 ASN's or documents daily and supply less than 20 parts. For those sending documents other than ASN's, document size should be limited to that WAM is NOT considered a fully integrated EDI solution for those suppliers that need to meet their Q1 ratings. Important background information: The WAM can be viewed two ways. WAM with web forms and WAM without web forms. WAM without web forms: WAM without web forms is for suppliers that have EDI software/translator and can input/output raw EDI to/from their EDI translator. WAM with web forms: WAM with web forms is for suppliers that do not have an EDI translator and need a low cost alternative for a standard EDI translator. Web forms can parse raw EDI, such as material releases and shipping schedules sent by Ford to its suppliers, and present it in a human readable/printable format. Web forms can also allow a user to Page 18 of 21 Date Issued: 04/26/2007
manually enter data into a web form, as in the case of an advance ship notice, and submit it to the. As of June 18, 2002 the web forms currently available are the planning release, ship schedule and the ASN. The ASN form requires users to fill in the information manually on line. How the FSP/WAM link works: High Level View A supplier logs into the FSP site. Under the heading of "Web EDI" they will see all of the GSDB codes they are allowed to view on the WAM. They choose a GSDB code and are then logged into the WAM. Upon entering they are taken to their inbox for that particular GSDB code. There they are allowed to view transactions such as material releases and shipping schedules sent from Ford. They can also go in the outbox, create an ASN and submit it to a particular Ford location. The Details Suppliers need the following setup before they can get to the WAM: 1. FSP account. 2. mailbox with password hard coded for FSP access. 3. WAM account (with or without web forms). They must log in to http://web.gsec.ford.com/gec/mailboxrequest/requesthome.asp to have account setup. Email to econnect@ford.com for questions concerning WAM setup. Suppliers accessing the WAM via the FSP web site must have an FSP account that has been granted the WEB EDI token. Suppliers can request FSP accounts and the WEB EDI token from their Corporate Security Administrator (CSA). The WEB EDI token is a permissions token granted to an FSP account that enables them to see a predefined list of GSDB codes setup in the WAM. The first time a supplier tries to access the WAM via FSP they will have to modify their page content to include the WEB EDI link. This can be done by clicking on "modify page" in the upper right corner of the main FSP page and following the instructions on the next page to add the WEB EDI "channel". Once added, the supplier will then see their GSDB codes under the WEB EDI heading on their main FSP page. When the supplier clicks on one of the WEB EDI GSDB codes the FSP logs the supplier into the WAM for that particular GSDB code. Process for connection to the WAM (Web Access Module)/Web EDI For anyone outside the Ford firewall (suppliers) the connection to the WAM is via the FSP website. Suppliers accessing the WAM via the FSP web site must have an FSP account that has been granted the web EDI token. Suppliers can request FSP accounts and the web EDI token from their Corporate Security Administrator (CSA). The web EDI token is a permissions token granted to an FSP account that enables them to see a predefined list of GSDB codes setup in the WAM. The first time a supplier tries to access the WAM via FSP they will have to modify their page content to include the web EDI link. This can be done by clicking on "modify page" in the upper right corner of the main FSP page and following the instructions on the next page to add a "channel". Once added the supplier will then see their GSDB codes under the web EDI heading on their main FSP page. In Summary - The supplier must have: A. FSP account (https:// FSP.ford.com) with web EDI token. B. mailbox with password hard coded for FSP access. C. WAM account (with or without web forms). D. Internet account from local ISP (Internet Service Provider). E. EDI Software (Optional). Procedure 1. Go to https://web.suppcomm.ford.com Page 19 of 21 Date Issued: 04/26/2007
2. Select your Geographic Region 3. Select Solmis Migration/Replacement 4. Scroll down and Select EDI Connection Request 5. Fill out form and Select New EDI Connection 6. Select on drop-down menu Web Access Module WAM 7. Answer all questions - a. Current EDI Connection to Ford None (New) b. New EDI Connection to Ford Web Access Module (WAM) c. EDI Hardware/Software i. Translation Sftw Select your EDI software or Other ii. Platform Select your platform or Other 8. Transaction Types 830, 856, 862 (DELFOR/DESADV/DELJIT - These are the current forms available and generally selected for low volume WAM users). 9. Mailbox (GS Sender Enter all of the mailbox/supplier codes you wish to access). 10. Addition Information - Comments (example) No current EDI software implemented for WAM Will use WAM Forms. 11. Submit Form If you have any questions email econnect@ford.com. 2.3.12 WAM FAQs What is the WAM? WAM or Web EDI is the Web Access Module. It is a low-cost EDI solution for low-volume suppliers to Ford Motor Company. Suppliers are set up for the WAM come in through the Ford Supplier Network portal. What is the overall functionality (capability) of the WAM? The WAM can be viewed two ways. WAM with web forms and WAM without web forms. WAM without web forms: WAM without web forms is for suppliers that have EDI software (translator) and can input/output raw EDI to and from their EDI translator. WAM with web forms: WAM with web forms is for suppliers that do not have an EDI translator and need a low cost alternative for a standard EDI translator. Web forms can parse raw EDI, such as material releases and shipping schedules sent to Ford to its suppliers, and present it in a human readable/printable format. Web forms can also allow a user to manually enter data into a web form. Such as an advance ship notice, and submit it to the. Does my company need Internet Access? Yes. Your company must have an Internet Access account with a local certified Internet Service Provider (ISP). What kind of software will I need? You will need to have an Internet Browser on your PC such as Internet Explorer version 5.5 or Netscape Navigator version 4.7 or above. As stated above it is not necessary to have EDI software if you are going to use the Web Forms method only. Page 20 of 21 Date Issued: 04/26/2007
How do I know if my company fits the profile of a WAM user? You must have a valid GSDB code from purchasing. If you supply Ford with less that 20 parts overall, submit less than 10 Advanced Shipping Notices per day and a Q1 rating is not important to doing business with Ford than you fit the profile. Will the WAM affect my Q1 rating? Yes. Since the WAM is NOT a fully integrated solution (computer to computer) as deemed necessary by the Ford Supplier Performance Group, your Q1 rating will be in jeopardy. Will my company need an FSP account? Yes. That can be obtained by going to: https://fsp.covisint.com/ and filling out the form. This should be done by your company's CSA (Corporate Security Administrator). How does the FSP/WAM link work? After WAM setup is complete, a supplier logs into the FSP site. Under the heading of "WEB EDI" they will see all of the GSDB codes they are allow to view on the WAM. They choose a GSDB code and are then logged into the WAM. Upon entering they are taken to their inbox for that particular GSDB code. There they are allowed to view transactions such as material releases and shipping schedules sent from Ford. They can also go into the outbox and create an ASN and submit it to a particular Ford location. What procedure should I then follow to get my company signed up for the WAM? Make sure that you have the following: 1. GSDB Code. 2. FSP Account 3. Web EDI Token 4. mailbox with password hard-coded for FSP Access. 5. WAM Account. Log into - https://w2k3qa.gsec.ford.com/gec/mailboxrequest/requesthome.asp to have account set up. - You can email ecconnect@ford.com for question concerning WAM setup. What additional steps do I need to follow to get started on the WAM? Suppliers accessing the WAM via the FSP web site must have an FSP account that has been granted the WEB EDI token. Suppliers can request FSP accounts and the WEB EDI token from their Corporate Security Administrator (CSA). The WEB EDI toke is a permissions token granted to an FSP account that enables them to see a predefined list of GSDB codes setup in the WAM. The first time a supplier tries to access the WAM via FSP they will have to modify their page content to include the WEB EDI link. This can be done by clicking on "modify page" in the upper right corner of the main FSP page and following the instructions on the next page to add the WEB EDI "channel". Once added, the supplier will then see their GSDB codes under the WEB EDI heading on their main FSP page. When the supplier clicks on one of the WEB EDI GSDB codes the FSP logs the supplier into the WAM for that particular GSDB code. Page 21 of 21 Date Issued: 04/26/2007