To: MSC Supplier IT Contacts - Clark Software



Manufacturing Support Center (MSC)

IT Connectivity Instructions

Table of Contents

Background 4

MSC IT Connectivity Summary 4

Supplier Connectivity 5

Overview 5

High-Availability Connection for Critical applications 5

T1 ANX circuit with ISDN backup from AT&T 5

High Availability ANXTunnelz configuration 6

Support Requirements 6

Extranet Documentation 6

Sample Diagram for MSC Local ANX Connectivity 7

Application Installation and Support Procedures 8

CMMS 8

Installation 8

CMMS3 Printing Over ANX 8

Sending ASNs via EDI 8

Obtaining Bridge Files from CMMS 9

End User Support 10

Technical Support 10

ILVS 11

Installation 11

End User Support 11

Technical Support 11

SMART 12

Installation 12

Firewall Configuration 12

Authorizing Users 13

End User Support 13

Technical Support 13

Broadcast 14

Installation 14

Supplier IP Broadcast Client 14

Circuit Order 14

End User Support 14

Technical Support 14

Attachment 1: MSC Supplier IT Scope 15

Attachment 2: MSC IT Troubleshooting Flow 16

Attachment 3: MSC IT Launch Check List 17

Attachment 4: Sample IP Broadcast Plan 18

Attachment 5: Sample IP Broadcast Plan 19

Background

Manufacturing Support Centers, or MSC's, are material warehouses operated by a 3rd party trading partner that manage materials and inventory for Ford assembly plants. These facilities are typically adjacent to or near the assembly plants, and receive and manage the flow of material into the plants. A plant may have one or more MSC operations performing different material services, which may include:

• Sequencing of materials by In-Line Vehicle Sequence or Broadcast

• Metering of material to line-side or to plant marketplaces

• Light or Heavy sub-assembly work

• Supplier Parks, including Bailment situations

• Deconsolidation warehouses supporting multiple plants

• Repacking operations

• Returnable container management

• Standard Part Warehouses

MSC IT Connectivity Summary

The following information provides the details necessary for providing a supplier the application connectivity required as an MSC. Not every MSC will require all of these applications. Before pursuing connectivity for these applications, the MSC should confirm which applications are required for the business processes they will be supporting. Effective communication between the plant MP&L team, plant IT team and MSC business and IT teams is critical to the successful launch of IT connectivity to an MSC.

Application connectivity described in this document includes:

• CMMS – Ford's corporate inventory management system

• ILVS – a system for In-Line Vehicle Sequencing based on forecasted assembly sequence

• SMART – a tool for the Synchronous Material Replenishment Trigger process for delivery of material to line-side

• BROADCAST – a system for sequencing based on actual assembly line sequence

Supplier Connectivity

Overview

Ford's standard method for providing suppliers with IT connectivity to Ford is the Automotive Network eXchange (ANX). If the MSC supplier does not already have ANX connectivity to Ford they will need to set it up. This is the longest lead-time and highest cost IT related item and should be addressed very early in MSC launch planning. Complete details on ANX connectivity can be found at the following website: .

The MSC supplier is responsible for setting up, supporting and funding the ANX connection and related services.

The following basic steps must be taken to set up ANX connectivity with Ford:

1) Select and ANX certified service provider.

2) Register with ANXO as a trading partner.

3) Submit the "Supplier Telecommunications Agreement" document.

4) Submit the "Request to Establish a Secure Tunnel" form.

High-Availability Connection for Critical applications

Because of the critical nature of the MSC site running the SMART application, a highly available ANX connection is required. Prior to a new MSC launch, TCS will perform a survey of the MSC location and its connectivity back to its corporate data network. If the trading partner can prove that they are providing reliable connectivity from the MSC location to their ANX Egress (and can show that they have high availability configured into their ANX connection), then the trading partner's existing infrastructure can be leveraged for the critical MSC communications with Ford.

If the MSC operator does not have satisfactory internal infrastructure, a local, Highly Available ANX connection is required at the MSC location.

Components of this highly available local ANX connection include:

• T1 ANX circuit with ISDN backup from AT&T

• High Availability ANXTunnelz configuration (two CC500 cryptoclusters) at the MSC

T1 ANX circuit with ISDN backup from AT&T

AT&T offers ANX services with the option to provide automated failover (via ISDN dial) to the ANX network if the primary circuit were to fail. AT&T configures the on-site CSP router to dial an ANX Network ISDN PRI in the event of a primary circuit failure. The MSC is responsible for ordering the ISDN circuit from the local LEC. AT&T provides the MSC with a managed Cisco router with integrated CSU/DSU and ISDN BRI port.

The MSC operator should contact AT&T for a quotation for ANX services with the ISDN backup option.

High Availability ANXTunnelz configuration

ANXeBusiness offers, as an option, a two node CC500 CryptoCluster configuration for trading partners that perform mission critical services and cannot tolerate a failure of the IPSec device used to establish IPSec tunnels over the ANX network.

The MSC operator should contact ANXeBusiness for a price quote for the high availability option.

Support Requirements

As with all ANX Certified Service Provider (CSP) connections the ANX transport, including the on-site router, will be managed by the CSP, in this case AT&T.

The local ISDN circuit, used for backup purposes, will be supported by the local LEC.

ANXTunnelz is a fully managed end-to-end service of IPSec tunnels, which connect trading partners over the ANX network. ANXeBusiness is the service provider for the ANXTunnelz service. ANXeBusiness is responsible for supporting the CC500 hardware as well as the IPSec tunnel between the MSC and Ford.

See ANXTunnelz trading partner contract for SLA information.

Extranet Documentation

The MSC TCP/IP connectivity model utilizes standard supplier connectivity processes, infrastructure and policies. MSC IPSec tunnels must use the ANXTunnelz service to benefit from the High Availability infrastructure in the Ford Extranet.

Note: No special provisions are made within the Ford extranet to service MSC connections.

Sample Diagram for MSC Local ANX Connectivity

[pic]

Application Installation and Support Procedures

CMMS

Installation

The MSC is responsible for purchasing, installing and supporting the IBM 32 bit emulator software required for CMMS3.

Once your ANX connection to Ford is established, you will automatically have connectivity to CMMS3. To access CMMS3, configure your emulator for host: 19.5.72.22, port: 5031.

CMMS3 Printing Over ANX

Once suppliers have ANX connectivity to Ford they are automatically granted access to the necessary mainframe print queues. However, the specific print queue on the Ford network must still be mapped. To request a new print queue, the MSC should submit a request via email to GSEC@. The request should include the following information and could take up to 72 business hours to be processed.

• Facility Name

• Contact Name and Phone Number

• IP address of the Print Server

o This must be a standalone Print server that is always on, not a workstation that also functions as a print server.

In response to this request, the MSC will be provided with a print queue name and an RVP number for the new print queue. For the print server to function in the Ford environment, the MSC must:

1. Ensure that an LPD service is running on the print server.

2. Add a print queue with the assigned print queue name.

3. Use the RVP number assigned to the print queue as the print destination for the MSC mainframe applications.

4. Allow LPR (TCP port 515) traffic from 19.59.28.90 and 19.5.34.90 to pass through the MSC firewall.

Sending ASNs via EDI

The following information pertains to MSCs that need to send ASNs through their own proprietary software.

In order to send ASNs from the MSCs proprietary software, the MSC will need to have and EDI mailbox. Once the MSC has an EDI mailbox set up, they will need to complete testing in both Test and Production environments.

For complete instructions on setting up an EDI mailbox and testing and sending ASNs to Ford using EDI please visit the GSEC website at .

The ASN should contain the following information:

1. Total weight of shipment - MEA - 03 - Mandatory

2. Code identifying the type of packaging - TD1 - 01 - Mandatory

3. Ship from location code - N1 - 04 - Must use Alternate Receiving Location supplier code.

4. Purchase order number - PRF - 01 - Ford supplied value

5. Customer order number - REF - 02 - MSC supplied value

6. Packing list number - REF - 02 - MSC supplied value

The MSC should coordinate ASN testing through a CMMS3 subject matter expert plant representative or contact Renee Eisenhart (Reisenha@) to coordinate the test.

Obtaining Bridge Files from CMMS

The "Bridge 2-01" file is commonly used for maintaining Balance on Hand (BOH) accuracy between the service provider's inventory system and CMMS3. The file is obtained via FTP over an ANX connection to Ford.

Note that the service provider is responsible for the manipulation of the file for their company use. Additionally, the service provider will not be permitted to send data back to CMMS3.

The MSC should contact Renee Eisenhart (Reisenha@) in MP&L Systems Planning & Implementation to obtain the file name.

Instructions for obtaining a CMMS3 Bridge file are listed below:

FTP Process for Customers

1. Customer/User must have a VALID RACF-authorized FTPid on the Facility they wish to use. If an FTPid does not exist one can be requested on the web from SILAS.

2. Once an FTPid has been assigned, the Customer/User will need the BPD Group to allocate a RACF-qualified dataset on the Facility for their use.

3. The BPD Group will then request RACF READ or UPDATE* authority on the Facility to the RACF-qualified file.

*UPDATE is the preferred method so that the Customer/User can write to and/or EMPTY the file when they are done.

Sending Data To/Receiving Data From Facility B:

IP address/script (for Facility B) is:

syb1.dearborn.(exit

append ' ................
................

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

Google Online Preview   Download