Logistics IT Requirements Specifications
Plan and Control with a System
Assuming our IT concept were the floor plan of a new factory hall, then detailed planning would need to describe the complete interior fit-out — from the ceiling light down to the floor outlet. That is exactly what we do for logistics IT: with a requirements specification (functional specification).
When introducing new logistics software, there are a few challenges that LogistikPlan addresses in a special way during project execution:
► Special challenges:
- If the new software has to be integrated into an existing corporate IT landscape, technical compatibility between subsystems is a given. However, this criterion already has a major impact in early phases of software selection on the time and cost required later for customization. External interfaces are particularly important here. The ability to replicate (simulate) and verify (document) exchanged data is not a given with some software providers.
- User acceptance and qualification are also critical for a successful implementation. Introducing the software changes the way logistics processes are executed. System selection and implementation must not be done only “at the drawing board”, but with intensive involvement of the people who run the processes.
► Logistics IT systems within the scope of our planning:
- Warehouse management (WMS) / warehouse control center (German: LVS)
- Software for warehouse organization, inventory counting, and picking (e.g., pick-by-voice)
- Material flow control (MFC) and forklift guidance systems
- Workstation equipment (e.g., mobile systems for posting, scanning, coding, labeling)
- Production planning and control (PPC), MES
- Container management and pallet/load carrier management
- Supply chain management (SCM), telematics systems, and traceability software for supply-chain tracking
- Route planning, transport management, fleet management
- Yard management and weighing, time-slot and dock/door management (slot management)
- Quality measurement and statistics for logistics services (monitoring and reporting systems)
► Our services for detailed planning of logistics IT
Based on the logistics IT concept, LogistikPlan refines the process requirements and prepares the specification for the IT system to be tendered in the form of a requirements specification (functional specification).
- Determining requirements for the core processes of warehousing, intralogistics, and outbound logistics
- Creating detailed process maps indicating IT-related sub-processes, transaction types, and documents
- Defining IT-side functions / rules / organizational principles according to which the warehouse is to be operated, e.g.
- Warehouse management with put-away and replenishment rules such as FIFO
- Inventory optimization to consolidate / clean up stock
- Warehouse process optimization based on ABC and XYZ analysis
- Shipping planning, route planning, and transport dispatching
- Forklift control
- Load carrier and container management
- Returns management
► Our services for creating the requirements specification
- Developing the software function structure based on usage scenarios and user-specific roles (e.g., warehouse management, forklift operation, logistics controlling)
- Information flow concept with a detailed description of information exchange between stakeholders throughout the logistics order-to-delivery process
- Configuring site- or customer-specific functional requirements (e.g., inventory management, batch management, parcel packing)
- Defining master data, parameters, and system information to be maintained in the system
- Identification and labeling concept (items, load carriers, warehouse zones, bin locations, etc.), based on end-to-end use of barcode and scanner systems for all inventory and inbound/outbound shipments
- Deriving the catalog of requirements for system functions and system configuration (hardware and network structure), incl. interfaces to upstream and adjacent IT systems and, if applicable, downstream systems and the required hardware
- Project schedule (phased plan) for testing and introducing the IT system, if necessary with phased implementation / activation of individual system functions
- Defining software test requirements, acceptance criteria, and test procedures
- Documenting all requirements as a functional specification to prepare the tendering and awarding process
Results at a glance:
- Description of the software function structure based on usage scenarios
- Information flow concept describing all core and supporting processes
- Identification and labeling concept
- Interface concept including boundaries to the host system and surrounding IT functions
- Phased plan for testing and rolling out system functions
