Ford Supply Chain Management

Software Requirement Specification

SUBMITTED IN PARTIAL FULFILLMENT OF THE REQUIREMENT FOR MINOR PROJECT At

A&M INSTITUTE of COMPUTER & TECHNOLOGY

Under Mr. ANIL PANDIT

(HOD OF COMPUTER DEPARTMENT)
SUBMITTED BY Mr. VARUN KUMAR (Roll No-104022141369) Mr. MANOJ (Roll No-104022141335)

INFORMATION TECHNOLOGY

PUNJAB TECHNICAL UNIVERSITY

JALANDHAR(PUNJAB)
1

Ford Chain

Supply Management
Presented By-

Mr. VARUN KUMAR

Mr. MANOJ

Table of Contents
Title Page Introduction
Distribution Finance Manufacturing

Why is this Particular Project Chosen?

Explanation

Working Environment
Understanding AS/400

Why Use AS/400t Technology

Multiple Platform Support Performance Security DB2/400 Data base

Plan Of the Work Objectives of the Project Data Flow Diagram Methodologies Adopted Testing Technology Scope of the Project Users
Assumptions

Software Requirement Hardware Requirement Reference

Introduction to Project:
Ford supply chain management is a live project running in ADVERB SOLUTION, Noida. Ford Motor Company, a global automotive industry leader based in Dearborn (United States) manufactures and distributes automobiles in 200 markets across six continents. Ford Motor Company had developed an application to maintain their Inventory, Purchase and Sales activities. This application is based on product system which stores information about all products produced and used by the company which consists of raw materials, work in process inventory and finished goods including goods made by other companies and used by Ford Motor Company. It also maintains brief details about its vendors, purchase requisitions, purchase orders, sales orders and to handle its order entries. This project is having three main modules 1 Distribution 2 Finance 3 Manufacturing

Why This Topic is Chosen:

We want to do our project training in some robust technologies and for that we have chosen AS/400 and then we have applied in ADVERB SOLUTION, Noida for training and got confirmation from ADVERB HR department. Ford supply chain management is a live project running with ADVERB and we are entitled with it.

Working Environment
Understanding AS/400 DEFINITION:
The IBM AS/400 is IBM's previous generation of midrange computer systems for IBM i users, and was subsequently replaced by the IBM Power Systems in April 2008. The platform was first introduced as the AS/400 (Application System/400) on June 21, 1988 and later renamed to the eServer iSeries in 2000. As part of IBM's Systems branding initiative in 2006, it was again renamed to System i. The codename of the AS/400 project was "Silver Lake", named for the lake in downtown Rochester, Minnesota, where development of the system took place. In April 2008, IBM announced its integration with the System p platform. The unified product line is called IBM Power Systems and features support for the IBM i (previously known as i5/OS or OS/400), AIX and GNU/Linux operating systems.

Summary The predecessor to AS/400, IBM System/38, was first made available in August 1979 and was marketed as a minicomputer for general business and departmental use. It was sold alongside three other product lines, each with a different architecture (System/3, System/32, System/34). The confusion that resulted from IBM offering these overlapping product lines that weren't compatible with each other along with the sluggish performance of System/38 significantly impacted IBM's sales. Digital Equipment Corporation, at the time one of IBM's main competitors, exploited this weakness with their wide ranging VAX product line based on a single architecture, and actively promoted the compatibility between all machines in the family. IBM's response, the IBM 9370 "baby mainframe," was a commercial failure. Realizing the importance of compatibility with the thousands of programs written in legacy code, IBM launched the AS/400 midrange computer line in 1988. AS stands for "Application System." Great effort was made during development of the AS/400 to enable programs written for the System/34 and System/36 to be moved to the AS/400.

In 2000, in accordance with IBM's eServer initiative, the AS/400 series was rebranded as the eServer iSeries. In 2006, it was again rebranded as the IBM System i. In 2008, almost 20 years after being introduced, the System i and IBM System p product lines were combined into a new product line called the IBM Power Systems line The AS/400 operating system was originally named OS/400 (following the pattern begun with OS/360 and followed with OS/2). The operating system has undergone name changes along with the rebranding of IBM's server lineup. The operating system was rebranded as i5/OS to correspond with the introduction of POWER5 processors and the rebranding of the hardware to eServer iSeries. For the 6.1 release, the operating system was again renamed to iBM i. The operating system is object-based. Features include a RDBMS (DB2/400), a menu-driven interface, support for multiple users, dumb terminal support (IBM 5250), and printers. It supports security, communications, and web-based applications which can be executed inside the optional IBM Web Sphere Application Server or as PHP/MySQL applications inside a native port of the Apache web server. Unlike the "everything is a file" feature of Unix and its derivatives, on OS/400 everything is an object (with built-in persistence and garbage collection). OS/400 offers Unix-like file directories using the Integrated File System. Java compatibility is implemented through a native port of the Java virtual machine. OS/400 Version 4, Release 4 (V4R4) introduced LPARs (logical partitions) allowing multiple virtual systems to run on a single hardware footprint. Features The IBM System i platform extended the System/38 architecture of an object-based system with an integrated DB2 relational database. Equally important are the virtual machine and single-level storage concepts which established the platform as an advanced business computer. Instruction set One feature that has contributed to the longevity of the IBM System i platform is its high-level instruction set (called TIMI for "Technology Independent Machine Interface" by IBM), which allows application programs to take advantage of advances in hardware and software without recompilation. TIMI is a virtual instruction set independent of the underlying machine instruction set of the CPU. User-mode programs contain both TIMI instructions and the machine instructions of the CPU, thus ensuring hardware independence. This is conceptually somewhat similar to the virtual machine architecture of programming environments such as Smalltalk, Java and .NET. The key difference is that it is embedded so deeply into

the AS/400's design as to make applications effectively binary-compatible across different processor families. Unlike some other virtual-machine architectures in which the virtual instructions are interpreted at run time, TIMI instructions are never interpreted. They constitute an intermediate compile time step and are translated into the processor's instruction set as the final compilation step. The TIMI instructions are stored within the final program object, in addition to the executable machine instructions. This is how application objects compiled on one processor family (e.g., the original CISC AS/400 48-bit processors) could be moved to a new processor (e.g., PowerPC 64-bit) without re-compilation. An application saved from the older 48-bit platform can simply be restored onto the new 64-bit platform where the operating system discards the old machine instructions and re-translates the TIMI instructions into 64bit instructions for the new processor. The IBM System i's instruction set defines all pointers as 48-bit. This was the original design feature of the System/38 (S/38) in the mid 1970s planning for future use of faster processors, memory and an expanded address space. The original AS/400 CISC models used the same 48-bit address space as the S/38. The address space was expanded in 1995 when the RISC PowerPC RS64 64-bit CPU processor replaced the 48-bit CISC processor. For 64-bit PowerPC processors, the virtual address resides in the rightmost 64 bits of a pointer while it was 48 bits in the S/38 and CISC AS/400. The 64-bit address space references main memory and disk as a single address set which is the single-level storage concept. Software The IBM System i includes an extensive library-based operating system, i5/OS, and is also capable of supporting multiple instances of AIX, Linux, Lotus Domino, Microsoft Windows 2000 and Windows Server 2003. While i5/OS, AIX, Linux and Lotus Domino are supported on the POWER processors, Windows is supported with either single-processor internal blade servers (IXS) or externally linked multipleprocessor servers (IXA and iSCSI). iSCSI also provides support for attachment of IBM Bladecenters. Windows, Linux, and VMware ESX(VI3) are supported on iSCSI attached servers. LPAR (Logical Partitioning), a feature introduced from IBM's mainframe computers, facilitates running multiple operating systems simultaneously on one IBM System i unit. A system configured with LPAR can run various operating systems on separate partitions while ensuring that one OS cannot run over the memory or resources of another. Each LPAR is given a portion of system resources (memory, hard disk space, and CPU time) via a system of weights that determines where unused

resources are allocated at any given time. The operating systems supported (and commonly used) under the LPAR schemes are i5/OS, AIX, and Linux. Other features include an integrated DB2 database management system, a menudriven interface, multi-user support, non-programmable terminals (IBM 5250) and printers, security, communications, clientserver and web-based applications. Much of the software necessary to run the IBM System i is included and integrated into the base operating system. The IBM System i also supports common clientserver systems such as ODBC and JDBC for accessing its database from client software such as Java, Microsoft .NET languages and others. The IBM System i also provide an environment for AIX applications to run natively on i5/OS without the need for an AIX LPAR. AIX programs are binary compatible with OS/400 when using OS/400's PASE (Portable Applications System Environment). PASE is essentially "an operating system within an operating system", supporting the most recent stable version of AIX. Most AIX 5L compatible binaries may be executed without modification or recompilation in the PASE environment. Exceptions to this are programs that contain direct calls to AIX kernel based APIs as there is no AIX kernel in PASE. If necessary an AIX program may be built directly in PASE using a standard AIX XL C/C++ compiler, for example if native APIs are to be used. In that case APIs are provided to translate between the AIX style pointers and the native 16 byte pointers. Support is provided for running both 32 and 64bit AIX executables. IBM systems may also come with programming and development software like Programming Development Manager. Programming Programming languages available for the AS/400 include RPG, assembly language, C, C++, Pascal, Java, EGL, Perl, Smalltalk, COBOL, SQL, BASIC, PHP, PL/I, Python and REXX. Several CASE tools are available: AllFusion Plex (see *Plex Wiki), Accelerator for IBM i, ADELIA, Synon, AS/SET, IBM Rational Business Developer Extension, LANSA, ProGen Plus and GeneXus. The ILE (Integrated Language Environment) programming environment allows programs from ILE compatible languages (C, C++, COBOL, RPG, FORTRAN, and CL), to be bound into the same executable and call procedures written in any of the other ILE languages.

The IBM System i fully supports the Java language, including a 32-bit Java Virtual Machine (JVM) and a 64-bit JVM. Commands in the Control Language (CL) are promptable using the keyboard F4 function key, and most provide cursor-sensitive help to make specifying command parameters simpler. All command names and parameter keywords are based upon uniform standardized and mostly 3-letter abbreviations for verbs and subjects, making for easy rendering and interpretation by the application developer, as opposed to other operating systems with often cryptic or inconsistent command names for related functions or command parameter switches. For instance, the parameter keyword to apply a text description to any object to be created or changed is spelled the same way for all such commands. Examples: CRTUSRPRF - Create user profile DSPUSRPRF, CHGUSRPRF, DLTUSRPRF - Display, change, and delete user profile DLTLIB - Delete library CRTLIB, DSPLIB, CHGLIB - Create, display, and change a library ADDLIBL, CHGLIBL - Add to or change library list CPYF, CRTF, DSPF, CHGF, DLTF - Copy, create, display, change, and delete file WRKACTJOB - Work with Active Jobs WRKSYSSTS - Work with System Status STRSST, STRPASTHR, STRSBS - Start System Service Tools, start pass through (remote login), start subsystem VRYCFG - Vary configuration, bring interfaces up or down PWRDWNSYS - Power Down System WRKSPLF - Work with spooled files

For traditional business programming languages such as RPG, COBOL, and C, the IBM System i provides an interface to the integrated database that allows these languages to treat database files much like other platforms treat ISAM or VSAM files. Support for 5250 display operations is provided via display files, an interface between workstations, keyboards and displays, and interactive applications, as opposed to batch processing with little or no user interaction. ASCII terminals and PC workstations are equally and well supported, also via internet or LAN network

access supplemented by either IBM or non-IBM communication software, for example TELNET or TELNET 5250.

History The IBM System i, then known as the AS/400, was the continuation of the System/38 database machine architecture (announced by IBM in October 1978 and delivered in August 1979). The AS/400 removed capability-based addressing. The AS/400 added source compatibility with the System/36 combining the two primary computers manufactured by the IBM Rochester plant. The System/36 was IBM's most successful mini-computer but the architecture had reached its limit. The first AS/400 systems (known by the development code names Silverlake and Olympic) were delivered in 1988 under the tag line "Best of Both Worlds" and the product line has been refreshed continually since then. Guy Dehond from Inventive Designers was one of the beta-testers of Silverlake. The programmers who worked on OS/400, the operating system of the AS/400, did not have a UNIX background. Dr Frank Soltis, the chief architect, says that this is the main difference between this and any other operating system. The AS/400 was one of the first general-purpose computer systems to attain a C2 security rating from the NSA (Gould UTX/C2, a UNIX-based system was branded in 1986[5]), and in 1995 was extended to employ a 64-bit processor and operating system. The 1995 change-over from 48 to 64-bit required that all programs be 'observable', i.e. that the debugging information had not been stripped out of the compiled code. This caused problems for those who had bought third-party products that had no source and no observability. In 2008, the introduction of V6R1 caused similar problems, although this time IBM preferred to call it a "refresh".[6] In 2000 IBM renamed the AS/400 to iSeries, as part of its e-Server branding initiative. The product line was further extended in 2004 with the introduction of the i5 servers, the first to use the IBM POWER5 processor. The architecture of the system allows for future implementation of 128-bit processors when they become available. Although announced in 1988, the AS/400 remains IBM's most recent major architectural shift that was developed wholly internally. Since the arrival of Lou Gerstner in 1993, IBM has viewed such colossal internal developments as too risky. Instead, IBM now prefers to make key product strides through acquisition (e.g., the takeovers of Lotus Software and Rational Software) and to support the development of open standards, particularly Linux. It is noteworthy that after the departure of

10

CEO John Akers in 1993, when IBM looked likely to be split up, Bill Gates commented that the only part of IBM that Microsoft would be interested in was the AS/400 division. (At the time, many of Microsoft's business and financial systems ran on the AS/400 platform.[7][8]) Hardware The AS/400 was originally based on a custom IBM CISC CPU which used a CPU architecture known as Internal Micro Programmed Interface (IMPI) and an instruction set similar to the IBM 370. It was later migrated to a POWER-based RISC CPU family eventually known as RS64.

Plan of the work:

Firstly, we choose the Project that could be beneficial for all of us. Then, we discussed the main motive of our project. Then we decided about the information that our project will provide. We also discussed about the Technology that can meet our requirement and should be good performance wise. Later on, we made the Data Flow Datagram to show How our data flow is going on After that we made the E-R Diagram for the creation of database and set up relationship between them. Then we will design database for it ,do designing work and then we will start the coding work After doing so much Hard Work our project work will be complete somewhat and we will start making project report. But finally our Project will be Complete when we will run this project on the server online.

11

Objectives of the project

After thoroughly analyzing the existing system the following objectives have been set: Providing user friendly interface Easy access of data Easy maintenance Maintaining data consistency Providing better performance Adequate validation checks for data entry Facility to update the data time to time Adequate security of the database

12

Data Flow Diagram:

LEVEL-0

13

Level-1
14

Methodologies Adopted
The concept of master pages and content pages will be used-the master page is a common template which can be applied on more than one page and SDA (Screen design is used for screen designing). DB2/400 is being used for managing the data at the server side.

Project Scope
Ford motors is using this software for all their requirement including main module Distribution, finance, manufacturing with sub modules sales, purchase, A/R, A/R and G/L. It is handling all process of Ford. It is kind of big ERP.

Software Requirements:
Screen: SDA (Screen design Aid) Language: RPG (Report program generator), CL (Control Language) Report: RLU (Report Layout utility) OS: OS/400
Tool: Aldon

HARDWARE REQUIREMENTS:
IBM AS/400 Server

15

REFERENCES:
1 - ALL IBM RED BOOK 2 ITSPARK MANUAL 3 ROBERT COZY 4 INTERNET

16