1. Foundations of Logistics Information SystemsIntroduction and ContextLogistics is often described as the movement and storage of goods, but physical movement alone does not create reliable logistics performance. Every movement is accompanied by information: what is being moved, in what quantity, from where, to where, by which mode, at what time, under what conditions, and with what documentation. Information enables logistics organisations to plan operations, coordinate participants, monitor execution, resolve exceptions, measure performance, and comply with legal and commercial requirements. A logistics information system (LIS) is the organised combination of people, processes, data, technology, and governance used to collect, process, communicate, and use logistics information. It may be as simple as a structured paper register in a small warehouse or as sophisticated as a cloud-based ecosystem integrating enterprise resource planning, warehouse management, transport management, supplier portals, customer applications, sensors, analytics, and artificial intelligence. The significance of an LIS lies not merely in automation. A poorly designed digital system can reproduce inaccurate processes at greater speed, while a well-designed system can improve visibility, coordination, responsiveness, and control. The central concern is therefore not technology in isolation, but the relationship among information flows, business processes, organisational roles, and technological infrastructure. Logistics information systems are foundational to supply chain management because logistics decisions are interdependent. A purchasing decision affects inbound transport; inbound timing affects warehouse capacity; warehouse availability affects order fulfilment; fulfilment performance affects customer service and transport scheduling. Information systems provide the connective tissue through which these activities are coordinated. Learning ObjectivesAfter studying this chapter, the learner should be able to: 1. Explain the role and characteristics of information flows in logistics. 2. Distinguish data, information, knowledge, and logistics intelligence. 3. Describe the components and architecture of a logistics information system. 4. Apply systems theory, process thinking, and the people–process–technology framework. 5. Explain transaction-processing principles and their relevance to logistics control. 6. Evaluate information quality and identify the consequences of poor information. 7. Trace the evolution from manual records to integrated digital logistics ecosystems. 8. Analyse the organisational, managerial, ethical, and technological implications of LIS adoption. From Physical Flows to Information FlowsA logistics process normally contains at least three linked flows. The first is the physical flow of materials, products, equipment, documents, or returned items. The second is the information flow that describes, authorises, schedules, and confirms the physical flow. The third is the financial flow involving prices, invoices, payments, credits, duties, and claims. Although these flows are analytically distinct, they are operationally connected. For example, a customer order initiates an information flow. The order may create a demand signal, trigger inventory allocation, generate a picking instruction, produce a transport requirement, and ultimately result in an invoice. The physical product may move through several facilities, but the information system records each relevant event. If the information is delayed or inaccurate, the physical process may continue without effective control. Information flows can be classified in several ways. A forward flow moves from supplier to customer, such as an advance shipping notice. A backward flow moves from customer or downstream operations toward the source, such as a sales forecast, delivery confirmation, product return, or customer complaint. Horizontal flows connect departments at the same organisational level, while vertical flows support managerial reporting and strategic decisions. Internal flows occur within an organisation; external flows connect suppliers, carriers, regulators, financial institutions, and customers. Logistics information also differs by time horizon. Strategic information supports network design, facility location, outsourcing, and long-term capacity decisions. Tactical information supports inventory policies, transport planning, workforce scheduling, and supplier coordination. Operational information supports receiving, picking, loading, dispatch, tracking, and delivery confirmation. Effective systems connect these horizons without confusing their different levels of detail and urgency. Data, Information, Knowledge, and IntelligenceData are recorded observations or symbols, such as a product code, quantity, timestamp, temperature reading, or vehicle identification number. Data become information when they are processed and placed in a meaningful context. “Item A was scanned at 14:05 at Dock 3” is more informative than an isolated scan code because it communicates an event, place, and time. Knowledge involves understanding relationships and implications. A logistics supervisor may know that repeated late scans at a particular dock indicate congestion during a shift change. Logistics intelligence goes further by supporting informed action through analysis, prediction, and decision support. For example, a system may identify that late dispatches are likely when inbound vehicles arrive within a particular time window and recommend revised dock appointments. This distinction is important because digitising data does not automatically create useful information or better decisions. The value of an LIS depends on whether relevant data are captured accurately, processed appropriately, interpreted competently, and converted into action. The Logistics Information System as a Socio-Technical SystemA logistics information system should be understood as a socio-technical system. It contains technical artefacts, but it also depends on human judgement, organisational structures, operating procedures, incentives, and institutional rules. Technology changes how work is performed; at the same time, existing work practices influence how technology is configured and used. Systems theory provides a useful foundation. An organisation can be viewed as an open system that receives inputs from its environment, transforms them through processes, produces outputs, and uses feedback to adjust its behaviour. In logistics, inputs include customer orders, forecasts, inventory, vehicles, labour, supplier commitments, and regulatory requirements. Transformation includes planning, purchasing, receiving, storing, picking, packing, transporting, and returning goods. Outputs include deliveries, service information, invoices, performance reports, and customer outcomes. Feedback includes delivery failures, stock discrepancies, claims, forecasts, and performance measures. Several systems concepts are especially relevant: - Interdependence: A change in one logistics activity can affect other activities. Increasing order frequency may improve customer responsiveness but increase picking and transport costs.
- Boundaries: A system has a defined scope, although its boundaries may be difficult to draw. A warehouse system may include receiving and dispatch but depend on external transport and supplier systems.
- Interfaces: Interfaces are points where processes, departments, or systems exchange information. Many logistics failures occur at interfaces rather than within individual activities.
- Feedback: Performance information enables corrective action. Without timely feedback, errors become embedded in subsequent decisions.
- Emergent performance: Overall service, resilience, or congestion may result from interactions among components rather than from one component alone.
Systems thinking discourages local optimisation. A warehouse may minimise its own labour cost by batching orders, but this may increase transport waiting time or reduce customer responsiveness. An LIS should therefore support end-to-end process objectives rather than only departmental targets. Process Thinking and the People–Process–Technology FrameworkProcess thinking focuses on how work moves from an initial requirement to a defined outcome. It asks what triggers the process, what activities occur, who performs them, what information is required, where decisions are made, and how completion is verified. Common logistics processes include order-to-cash, procure-to-pay, plan-to-deliver, warehouse receiving, fulfilment, transport execution, and returns management. A process perspective reveals that a system is not simply a collection of screens or devices. It is a mechanism for supporting work. A warehouse management system, for example, is valuable because it coordinates receiving, put-away, replenishment, picking, counting, and dispatch—not because it merely stores records. The people–process–technology framework provides a practical method for analysing LIS design and implementation. People include warehouse operators, planners, drivers, supervisors, managers, customers, suppliers, system administrators, analysts, and senior sponsors. Their skills, incentives, authority, trust, and willingness to use information affect system performance. A barcode system may fail if operators are not trained or if performance targets encourage bypassing scans. Processes define how activities are performed and controlled. They include business rules, approvals, exception procedures, standard operating procedures, and performance measures. Automating an unclear or conflicting process can make the problem more difficult to detect. Technology includes hardware, software, networks, databases, integration tools, mobile devices, sensors, and analytical platforms. Technology should be selected according to process requirements and organisational capability, rather than because it is fashionable or technically impressive. The framework implies that implementation is a change-management issue. Successful adoption requires process ownership, user participation, training, communication, data governance, support, and appropriate measures. It also requires recognition that different groups may have conflicting interests. A system designed for managerial visibility may be perceived by operators as surveillance; a system designed for customer convenience may increase workload in the warehouse. Components and Architecture of a Logistics Information SystemAlthough architectures vary, most logistics information systems contain several connected layers. The transaction layer records operational events such as purchase orders, sales orders, receipts, picks, shipments, delivery confirmations, inventory adjustments, invoices, and returns. This layer provides the factual basis for other system functions. The execution layer supports operational activities. Warehouse management systems coordinate storage and fulfilment; transport management systems support carrier selection, route planning, tendering, tracking, freight settlement, and delivery performance; fleet systems monitor vehicles and driver activity. The planning and coordination layer supports forecasting, replenishment, inventory positioning, capacity planning, production coordination, and network decisions. Enterprise resource planning systems often connect financial, procurement, sales, and operational processes. The integration layer enables communication among internal applications and external partners. Application programming interfaces, electronic data interchange, message queues, and cloud integration platforms may transmit orders, shipment notices, status events, invoices, and master-data updates. The data and analytics layer contains operational databases, data warehouses, dashboards, reporting tools, and analytical models. It transforms events into measures such as order cycle time, inventory accuracy, fill rate, transport utilisation, and on-time delivery. The governance and security layer establishes access rights, data ownership, retention rules, audit trails, privacy controls, cybersecurity measures, and standards for data definitions. This layer is often less visible than software applications but is essential for reliable operation. Master data deserve particular attention. Product identifiers, units of measure, locations, supplier records, customer addresses, packaging hierarchies, vehicle details, and delivery calendars are reused across transactions. An incorrect unit of measure can cause over-ordering, incorrect picking, or inaccurate inventory reporting. Master-data governance therefore has a direct operational impact. Transaction Processing: The Operational CoreTransaction processing is the systematic capture, validation, storage, and updating of business events. Logistics depends on high volumes of transactions, many of which occur under time pressure and across organisational boundaries. A transaction normally has a business meaning, a time, an actor or source, a location, a quantity or value, and a status. A receiving transaction, for instance, may identify the purchase order, supplier, vehicle, dock, product, quantity expected, quantity received, condition, time, and employee or device recording the event. Transaction-processing systems require several principles: 1. Validity: The transaction must represent an authorised and plausible event. A shipment should not be confirmed against a closed order without an approved exception. 2. Completeness: Required transactions and fields should be captured. Missing delivery confirmations weaken customer service and financial control. 3. Consistency: Related records must agree. Inventory balances, order status, and shipment status should not contradict one another. 4. Timeliness: Information must be available when decisions require it. A delivery status received after a customer has already escalated a failure has limited operational value. 5. Traceability: The system should preserve who performed an action, when it occurred, what changed, and why. 6. Recoverability: Transactions should be protected against equipment failure, communication interruption, or processing errors. In database practice, transaction integrity is frequently associated with the ACID properties: atomicity, consistency, isolation, and durability. Atomicity means that a transaction is completed fully or not at all. Consistency means that processing preserves defined rules. Isolation limits inappropriate interference among simultaneous transactions. Durability means that a completed transaction remains recorded despite later system interruption. These principles are particularly important when inventory, financial, and shipment records are updated concurrently. Not every logistics event needs identical processing. Some decisions require real-time or near-real-time processing, such as automated inventory allocation or temperature alerts. Other activities can use batch processing, such as overnight performance reports or periodic financial consolidation. The appropriate choice depends on decision urgency, cost, network reliability, and operational risk. Information Quality and Decision ReliabilityInformation quality is multidimensional. Accuracy concerns whether information correctly represents reality. Completeness concerns whether necessary fields and events are present. Timeliness concerns whether information is available when needed. Consistency concerns agreement across records and systems. Relevance concerns usefulness for the particular decision. Accessibility concerns whether authorised users can obtain and understand the information. Granularity concerns the level of detail, while reliability concerns confidence in the source and processing method. Quality is contextual. A highly detailed data set may be unnecessary for a strategic network decision but essential for investigating a damaged shipment. Conversely, a real-time dashboard may appear impressive but be misleading if its underlying data are incomplete or delayed. Poor information quality creates direct and indirect costs. Incorrect stock records may cause stockouts, emergency purchases, excess safety stock, and customer dissatisfaction. Inaccurate addresses may produce failed deliveries and additional transport cost. Duplicate supplier records may distort spend analysis. Delayed data may lead managers to react to conditions that no longer exist. Data quality should be managed as a process rather than as a one-time cleaning exercise. Organisations should define data ownership, validation rules, standard formats, exception handling, periodic audits, and correction responsibilities. Useful controls include barcode validation, mandatory fields, range checks, duplicate detection, reconciliation, cycle counting, and event-based alerts. A distinction should be made between data quality and decision quality. Good data do not guarantee a good decision if the analytical model is inappropriate, objectives are conflicting, or decision-makers misunderstand the situation. Nevertheless, poor data place a ceiling on achievable decision quality. The Evolution of Logistics Information SystemsEarly logistics records were predominantly manual. Paper purchase orders, stock cards, dispatch registers, invoices, and signed delivery notes provided evidence of activity. These records were familiar and inexpensive to begin with, but they were slow to update, difficult to consolidate, vulnerable to transcription errors, and often inaccessible across locations. The next stage involved office automation and standalone spreadsheets. Spreadsheets improved calculation and reporting, but frequently created multiple versions of the truth. Different departments could maintain different product codes, inventory balances, and customer lists. The apparent flexibility of spreadsheets could therefore produce hidden control risks. Enterprise systems introduced integrated databases and common transaction structures. ERP systems connected finance, procurement, sales, inventory, and selected logistics processes. Warehouse and transport management systems added specialised functionality. Integration reduced duplicate entry and improved visibility, although implementation complexity and data migration remained substantial challenges. Internet-based systems enabled electronic data interchange, supplier portals, customer tracking, online booking, and cloud applications. Logistics information began to cross organisational boundaries more easily. Mobile computing and barcode or radio-frequency identification technologies shifted data capture closer to the point of activity. The contemporary logistics environment is increasingly ecosystem-oriented. Cloud platforms, application programming interfaces, internet-of-things devices, telematics, geospatial systems, robotics, analytics, and artificial intelligence may connect manufacturers, logistics service providers, carriers, marketplaces, regulators, and customers. Digital twins and control towers seek to provide a coordinated view of network conditions, while predictive models estimate demand, arrival times, congestion, maintenance needs, or disruption risk. This evolution is not a simple replacement of old technology by new technology. Each stage introduces new capabilities and new dependencies. Digital systems can improve speed and visibility but also increase exposure to cyberattack, vendor concentration, privacy concerns, algorithmic bias, system outages, and poorly understood automated decisions. Practical Applications Across Logistics ActivitiesIn procurement, an LIS can consolidate requirements, issue purchase orders, compare supplier confirmations, monitor lead times, and identify delivery deviations. Inbound visibility allows a warehouse to plan labour and dock capacity before goods arrive. In inventory management, systems record receipts, issues, transfers, adjustments, and counts. They can apply reorder policies, identify slow-moving stock, classify items, and support allocation across locations. However, automated replenishment is only as reliable as demand data, lead-time assumptions, and inventory records. In warehousing, mobile terminals and scanning can guide put-away, picking, packing, and loading. Location logic can reduce travel, while task interleaving can balance work. Systems may also support slotting, labour planning, cycle counting, and exception management. In transport, a transport management system can consolidate shipments, select carriers, plan routes, issue tenders, monitor milestones, calculate freight charges, and evaluate carrier performance. GPS and telematics can provide location and vehicle information, but tracking data must be interpreted within operational context. In customer service, shipment visibility, estimated arrival times, proof of delivery, and exception alerts improve communication. The best systems do not merely display status; they support action, such as rescheduling, rerouting, customer notification, or claims initiation. In reverse logistics, information systems identify returned products, reasons for return, condition, disposition, refunds, repairs, recycling, and recovery value. Reverse flows often require different rules from forward distribution and should not be treated as an administrative afterthought. An Illustrative Case: NorthStar Distribution’s Visibility FailureBackgroundNorthStar Distribution is a fictional regional wholesaler supplying electrical components to construction contractors and retail outlets. It operates two warehouses and contracts transport to several carriers. For years, orders were recorded in an ERP system, warehouse activity was managed through spreadsheets and printed pick lists, and carriers sent delivery information by email. Situation and ProblemNorthStar experienced increasing customer complaints about late deliveries and incorrect stock availability. The sales department promised products shown as available in the ERP system, while warehouse staff knew that some items had been damaged, misplaced, or reserved for other orders. Carrier status updates were often received one or two days after delivery. Managers responded by increasing inventory and expediting shipments, which raised cost without resolving the underlying visibility problem. AnalysisA process review identified three major interface failures. First, warehouse adjustments were entered into the ERP system only at the end of a shift. Second, the sales and warehouse teams used different product descriptions for several similar components. Third, there was no standard event vocabulary for carriers; terms such as “dispatched,” “in transit,” and “delivered” were interpreted differently. Using the people–process–technology framework, the problem was not classified as a software deficiency alone. Employees lacked agreed procedures for damage reporting and reservation status. Supervisors were measured on warehouse throughput, which encouraged delayed exception entry. The existing technology could support scanning but had not been configured to require it. Approach and SolutionNorthStar first mapped the order-to-delivery process and defined ownership for each event. It established common master data for products, locations, and units of measure. Barcode scanning was introduced at receiving, picking, loading, and dispatch. A mobile exception form recorded damage, shortage, and substitution at the point of discovery. The company then integrated carrier milestone messages through an API and created a shared status vocabulary. The dashboard distinguished planned, confirmed, delayed, and exception events rather than displaying a single vague status. Governance rules specified who could alter inventory, who approved adjustments, and how corrections were audited. Training focused on why each scan mattered to the next process, not merely on device operation. Performance measures were revised to include inventory accuracy, scan compliance, order cycle time, and on-time delivery. A phased implementation began with one warehouse and a limited carrier group. OutcomeThe changes improved the timeliness and consistency of operational information and reduced the need for emergency expedites. More importantly, managers could distinguish a genuine transport delay from an inventory-record problem. The case does not claim that technology alone solved the business problem; improvement resulted from coordinated changes to data, process ownership, employee behaviour, integration, and performance measurement. Learning PointsThe case illustrates that information failures frequently occur at organisational interfaces. It also demonstrates the value of event definitions, master-data governance, point-of-activity capture, phased implementation, and measures aligned with end-to-end outcomes. Visibility is useful only when it is trusted and connected to decisions. Challenges, Risks, and Common MistakesA common mistake is treating system implementation as an IT project rather than an organisational change programme. Another is automating an unstable process before clarifying responsibilities and controls. Organisations may also underestimate data migration, master-data maintenance, user training, integration testing, and post-implementation support. Integration creates dependency. If a carrier platform, cloud provider, network, or identity service becomes unavailable, logistics operations may be disrupted. Business continuity requires backup procedures, recovery objectives, alternative communication channels, and periodic testing. Cybersecurity risks include unauthorised access, ransomware, credential theft, malicious alteration of shipment or payment data, and disruption of operational technology. Controls should include least-privilege access, strong authentication, patching, network segmentation where appropriate, monitoring, backups, incident response, and supplier-risk assessment. Automation can also produce inappropriate decisions when algorithms rely on biased or incomplete historical data. A routing or allocation model may favour easily served locations, penalise certain suppliers unfairly, or conceal assumptions from users. Human oversight, explainability proportional to risk, model validation, and escalation procedures are therefore important. Privacy is relevant when systems collect driver location, employee activity, customer addresses, or behavioural data. Organisations should collect only what is necessary, define legitimate purposes, restrict access, protect data, and comply with applicable privacy and employment regulations. Records may also be subject to customs, tax, product-safety, transport, and contractual retention requirements. Current Developments and Best PracticesSeveral developments are shaping logistics information systems. Real-time event-sharing standards seek to improve interoperability among partners. Internet-of-things devices provide condition and location data for sensitive products. Artificial intelligence supports demand forecasting, anomaly detection, estimated arrival times, document extraction, and predictive maintenance. Digital control towers combine data from multiple systems to identify network exceptions. Robotics and autonomous equipment increasingly depend on accurate task and location data. These developments should be evaluated according to business value, data readiness, risk, scalability, and workforce impact. A sophisticated tool is not automatically appropriate for every organisation. Sound practice generally involves: - defining logistics processes and outcomes before selecting technology;
- assigning ownership for master data, transactions, and exceptions;
- using common identifiers, units, status definitions, and interface standards;
- capturing information as close as possible to the event;
- designing controls for accuracy, security, traceability, and recovery;
- involving users and external partners in requirements and testing;
- implementing in manageable stages with measurable benefits;
- monitoring both system performance and business performance; and
- reviewing automated decisions, emerging risks, and regulatory obligations regularly.
Chapter SummaryA logistics information system links physical, informational, and financial flows through people, processes, technology, data, and governance. Systems theory explains logistics as an open, interdependent system requiring feedback and end-to-end coordination. Process thinking focuses attention on triggers, activities, interfaces, decisions, and outcomes, while the people–process–technology framework shows why technical solutions must be supported by capable users and well-designed work methods. Transaction processing provides the operational record of logistics events and depends on validity, completeness, consistency, timeliness, traceability, and recoverability. Information quality influences inventory, service, cost, compliance, and managerial decisions. Logistics systems have evolved from paper records and spreadsheets to integrated, cloud-based, data-rich ecosystems involving mobile devices, sensors, analytics, artificial intelligence, and external partners. The same digital connectivity that creates visibility also introduces cybersecurity, privacy, integration, continuity, and governance risks. Effective LIS management therefore requires technical competence together with process discipline, organisational leadership, ethical judgement, and continuous improvement. Key TermsLogistics information system: An organised combination of people, processes, data, technology, and governance used to manage logistics information. Information flow: The movement of data and information among activities, departments, organisations, or decision levels. Master data: Relatively stable reference data, such as product, location, supplier, customer, and unit-of-measure records. Transaction processing: The capture, validation, storage, and updating of operational business events. Data quality: The fitness of data for use, including accuracy, completeness, timeliness, consistency, relevance, and accessibility. Systems theory: An approach that views an organisation as an interdependent system of inputs, processes, outputs, and feedback. Process thinking: The analysis of work as connected activities that transform an input into an outcome. People–process–technology framework: A framework examining human, procedural, and technical conditions jointly in system design and implementation. Enterprise resource planning: Integrated software supporting cross-functional organisational processes and shared data. Warehouse management system: Software that plans, directs, records, and controls warehouse operations. Transport management system: Software supporting transport planning, execution, tracking, settlement, and performance management. Application programming interface: A defined mechanism through which software applications exchange data or services. Electronic data interchange: Structured computer-to-computer exchange of standard business documents. Event visibility: The ability to observe and interpret relevant logistics milestones and exceptions. Data governance: Policies, roles, standards, controls, and accountability for managing organisational data. ACID properties: Atomicity, consistency, isolation, and durability principles supporting reliable transaction processing. Digital ecosystem: A network of interconnected organisations, platforms, devices, applications, and data services. Control tower: A coordinated information and analytics capability used to monitor and manage supply chain events and exceptions. Traceability: The ability to reconstruct the origin, movement, changes, and status of a product or transaction. Exception management: The identification, prioritisation, investigation, and resolution of deviations from planned logistics performance. Review QuestionsShort Answer Questions1. Distinguish between data, information, knowledge, and logistics intelligence. 2. What are the principal dimensions of information quality? 3. Explain the role of feedback in a logistics information system. 4. What is master data, and why is it important in logistics? 5. State the ACID properties of transaction processing. Long Answer Questions1. Explain how physical, information, and financial flows interact in a logistics process. 2. Discuss the people–process–technology framework and its implications for LIS implementation. 3. Describe the major layers or components of a contemporary logistics information system. 4. Analyse the evolution from manual logistics records to digital logistics ecosystems. 5. Explain the major cybersecurity, privacy, continuity, and governance risks associated with integrated logistics systems. Analytical / Application Questions1. A warehouse reports high throughput but persistent inventory inaccuracies. Use systems theory and process thinking to identify possible causes and propose measures. 2. A carrier provides frequent real-time location data, but customers still receive unreliable estimated delivery times. Analyse the information-quality and process issues that may explain this result. 3. Design a people–process–technology implementation approach for introducing barcode scanning and carrier integration in a medium-sized distribution centre. Include controls and performance measures. 22. Multiple Choice Questions with AnswersQuestion 1Which statement best explains why logistics information is more than a record of physical movement? A. It replaces the need to move products physically. B. It authorises, schedules, coordinates, and evaluates physical movement. C. It is used only for financial reporting. D. It eliminates the need for logistics employees. Correct Answer: B. It authorises, schedules, coordinates, and evaluates physical movement. Question 2A warehouse system shows stock as available although damaged units have not been recorded. Which information-quality dimension is most directly affected? A. Accuracy B. Accessibility C. Granularity D. Confidentiality Correct Answer: A. Accuracy Question 3Which example best represents feedback in a logistics system? A. A supplier receives an original purchase order. B. A warehouse stores a product at a designated location. C. Delivery-failure data are used to revise routing and customer-notification procedures. D. A vehicle begins a scheduled journey. Correct Answer: C. Delivery-failure data are used to revise routing and customer-notification procedures. Question 4Under the people–process–technology framework, requiring employees to scan goods at receiving primarily addresses which combination? A. Only technology B. Only people C. Process supported by technology and user behaviour D. Financial control without operational impact Correct Answer: C. Process supported by technology and user behaviour Question 5Which transaction-processing principle requires a completed transaction to remain recorded after a system restart? A. Atomicity B. Consistency C. Isolation D. Durability Correct Answer: D. Durability Question 6A company has different product codes in its purchasing and warehouse systems. What is the most likely consequence? A. Improved interoperability B. Inconsistent records and unreliable coordination C. Automatic improvement in forecasting D. Greater transaction durability Correct Answer: B. Inconsistent records and unreliable coordination Question 7Why is local optimisation potentially harmful in logistics? A. It always increases technology costs. B. Improving one department’s measure may worsen end-to-end performance. C. It prevents the use of paper records. D. It makes all processes fully automated. Correct Answer: B. Improving one department’s measure may worsen end-to-end performance. Question 8Which activity is most characteristic of a transport management system? A. Defining employee privacy policies B. Planning shipments, selecting carriers, and monitoring delivery milestones C. Creating product designs D. Replacing all enterprise financial records Correct Answer: B. Planning shipments, selecting carriers, and monitoring delivery milestones Question 9NorthStar’s delayed warehouse updates mainly caused which type of operational problem? A. The system had no database at all. B. Information was unavailable when decisions required it. C. The organisation had excessive data security. D. The carrier used too many vehicles. Correct Answer: B. Information was unavailable when decisions required it. Question 10Which is the most appropriate reason to evaluate an artificial-intelligence logistics tool before deployment? A. All AI tools eliminate the need for human oversight. B. Historical data and automated decisions may contain bias or inappropriate assumptions. C. AI systems cannot process logistics data. D. Digital systems do not require governance. Correct Answer: B. Historical data and automated decisions may contain bias or inappropriate assumptions.
|
