Chief Information Officer — Contract-Logistics Portfolio

The mandate

A contract-logistics portfolio has profitable flagship sites and a growing set of facilities whose true contribution is difficult to establish. Warehouse systems, labour tools, customer billing and finance records describe activity differently; contractual changes often reach operations before configuration or charging. The replacement CIO must create information continuity before the next network-profitability review.

Approximately 1,800 employees and material partners work across warehouse operations, transport coordination, engineering, commercial, finance, customer implementation, cyber and technology from Singapore. The CIO owns enterprise applications, infrastructure, service, cyber operations, architecture, data platforms and technology investment, reporting to the Group Chief Executive or designated executive-committee sponsor.

The first priority is a credible operating record for each contract. Customer scope, rate card, activity definitions, labour standards, asset assumptions and approved changes must connect to the systems executing and invoicing work. The CIO will not own commercial terms, but must ensure that an authorised term can be represented, tested and traced through fulfilment and billing.

Site technology varies because of acquisitions, customer requirements and local decisions. A single-system edict would interrupt good operations and absorb capital without proving value. The incoming executive will classify platforms by risk, strategic fit and migration readiness, then set explicit paths to retain, contain, modernise or retire them.

Warehouse management remains mission critical. Inventory accuracy, task release, replenishment, picking, packing and dispatch cannot pause for a transformation programme. Changes require representative-volume testing, recovery rehearsals and reconciled stock. A successful cutover is one in which physical custody and customer visibility agree after the first difficult shift, not merely when interfaces turn green.

Customer implementations need firmer technology gates. New contracts frequently compress discovery, data, integration and testing to protect a go-live date. The CIO will establish minimum evidence for scope, master data, capacity, cyber, support and fallback. Exceptions must name the executive accepting cost and service exposure.

Network profitability will be supported by consistent event and cost definitions. Labour hours, equipment use, storage, value-added tasks, transport touches and service failures must be attributable at a useful level. Technology will partner with finance and operations to remove reconciliation effort, while preventing a central model from erasing legitimate contract differences.

Architecture must reduce customer-specific fragility. Standard services for identity, integration, observability, master data and reporting should be reused; differentiating workflows can remain modular. The CIO will challenge bespoke code created solely because commercial commitments were not translated into configurable rules.

Cybersecurity has physical consequence. A compromised warehouse or integration channel can misroute inventory, expose customer data and stop despatch. Segmentation, privileged access, supplier connectivity, recovery and incident decisions require operational testing. Cyber exercises will include site leaders and customers where obligations demand it.

Infrastructure resilience will be measured at facility level. Connectivity, scanners, automation controllers, printing, power and cloud dependencies need defined recovery objectives. The technology team must demonstrate how a site continues safe custody when a central service is unavailable, and how transactions reconcile when service returns.

Technology economics will move beyond project approval. Run cost, licence consumption, vendor concentration, technical debt and change capacity will be visible by platform and contract where practical. Investment cases must distinguish savings, avoided risk, customer-funded capability and growth enablement. Unused licences or delayed decommissioning will not disappear inside a transformation budget.

The replacement transition needs deliberate knowledge transfer. The incumbent's vendor relationships, regulatory commitments, unresolved outages and architectural exceptions should be recorded and tested. The new CIO will independently assess the portfolio rather than inherit conclusions, while avoiding a disruptive reset during succession.

Talent will be organised around products and reliable services rather than projects alone. Site-facing technologists, architects, cyber specialists and product owners need clear accountability and succession. Strategic suppliers can provide scale, but design authority, customer judgement and recovery leadership must remain inside the organisation.

What you will own

• Contract-to-system and billing information integrity.
• Warehouse, labour, finance and customer platforms.
• Application portfolio and architecture pathways.
• Infrastructure, cyber operations and site resilience.
• Customer implementation technology gates.
• Technology economics, vendors and investment assurance.
• Digital talent, service ownership and succession.
• Executive and board reporting on technology exposure.

The first 12 months

Within 45 days, identify contracts where system configuration, operational activity and billing terms diverge; test recovery at the most dependent sites; and agree the incumbent handover record. Escalate any customer go-live lacking minimum technology evidence.

By month six, establish the application pathways, common contract-event definitions and implementation gates. Put site-level cyber and continuity exercises into operation, and assign internal owners to every critical service and strategic supplier.

At twelve months, reduce technology-attributable billing leakage by 40%, remove 25% of priority reconciliation effort and achieve 99.95% availability for critical fulfilment services. All tier-one sites must pass stock-reconciled recovery tests, while at least six fragile integrations are retired without material customer disruption.

What the sponsor will examine

• Customer promises represented faithfully in operational systems.
• Physical inventory reconciled through change and recovery.
• Architecture choices based on contract value and risk.
• Profitability definitions understood across functions.
• Cyber exercises testing operational consequence.
• Internal leaders able to govern vendors and services.

The person

You bring 22–28 years in information and technology leadership, including CIO authority in contract logistics, warehousing, distribution or another site-intensive service network. Your record covers mission-critical cutovers, customer integrations, cyber resilience, application rationalisation and technology cost accountability across Asia.

Candidates must provide evidence of a contract margin issue traced to technology or data design, and a warehouse recovery that preserved inventory integrity. This is a permanent onsite Singapore role with regular presence across regional facilities and customer implementations.

Compensation and terms

Base compensation is SGD 420,000–570,000 plus annual incentive and long-term participation linked to service continuity, information integrity, profitability visibility, cyber resilience and leadership succession. The permanent onsite Singapore CIO reports to the Group Chief Executive or designated executive-committee sponsor. Planned replacement allows an orderly incumbent transition.

Confidentiality

The organisation, sites, customers, contracts, system estate, cyber posture, suppliers and profitability evidence remain confidential. Detailed access follows conflict review, eligibility and signed confidentiality. Applicants must not approach warehouse operators, software providers or customers to identify the client or validate this search.