Initial work
This commit is contained in:
@@ -0,0 +1,23 @@
|
||||
# Build Process
|
||||
|
||||
This book is managed as a collection of Markdown files, designed to be compatible with tools like GitBook or AsciiDoctor.
|
||||
|
||||
## Structure
|
||||
The book is organized into a `SUMMARY.md` file which acts as the Table of Contents, and individual chapter files.
|
||||
|
||||
## Building the Book
|
||||
To build the book for production, follow these steps:
|
||||
|
||||
1. **Clone the repository**:
|
||||
```bash
|
||||
git clone <repository-url>
|
||||
```
|
||||
|
||||
2. **Validation**:
|
||||
Ensure all links in `SUMMARY.md` point to existing files in the `supply_chain/book/` directory.
|
||||
|
||||
3. **Deployment**:
|
||||
The content is designed to be hosted on a static site generator. If using GitBook, simply push the changes to the repository and the build process will be triggered automatically.
|
||||
|
||||
## Contributing
|
||||
New chapters or updates to existing chapters should be submitted via pull requests, ensuring that any new sections are added to `SUMMARY.md`.
|
||||
@@ -0,0 +1,9 @@
|
||||
# Summary
|
||||
|
||||
* [Introduction](ch01_intro.md)
|
||||
* [Anchor Theories](ch02_theories.md)
|
||||
* [Practical Frameworks](ch03_frameworks.md)
|
||||
* [Practitioner's Perspective](ch04_practitioner_perspective.md)
|
||||
* [Virtual Resource Deep-Dive](ch05_virtual_resources.md)
|
||||
* [Supply Chain Tooling: From ERPs to Orchestrators](ch07_tooling.md)
|
||||
* [Annotated Bibliography](ch06_bibliography.md)
|
||||
@@ -0,0 +1,5 @@
|
||||
# Introduction
|
||||
|
||||
This book serves as a comprehensive knowledge base for understanding Supply Chain Management (SCM), bridging the gap between traditional physical logistics and the modern orchestration of virtual resources in cloud computing.
|
||||
|
||||
The goal is to provide a framework for analyzing how the principles of moving physical goods (atoms) are evolving into the principles of managing digital capacity (bits).
|
||||
@@ -0,0 +1,32 @@
|
||||
# Anchor Theories
|
||||
|
||||
These theories provide the academic and strategic foundation for SCM, offering frameworks to analyze competitive advantage, governance, and adaptability.
|
||||
|
||||
## Resource-Based View (RBV)
|
||||
- **General Purpose:** Proposes that sustained competitive advantage comes from possessing resources that are **Valuable, Rare, Inimitable, and Non-substitutable (VRIN)**.
|
||||
- **Application to Virtual Resources:**
|
||||
- **The Physical Layer:** The massive scale of data centers, proprietary custom silicon (e.g., TPUs, Graviton), and global fiber networks are the primary VRIN resources.
|
||||
- **Virtualization as Capability:** The ability to efficiently slice physical hardware into virtual units (VMs, Containers) is the strategic capability that transforms raw hardware into a service.
|
||||
- **Competitive Edge:** Derived from the **density** and **utilization efficiency** of the hardware.
|
||||
|
||||
## Dynamic Capabilities Theory (DCT)
|
||||
- **General Purpose:** Focuses on a firm's ability to "integrate, build, and reconfigure" internal and external competencies to address rapidly changing environments.
|
||||
- **Application to Virtual Resources:** This is the theoretical foundation of **Cloud Elasticity**.
|
||||
- **Sensing:** Real-time telemetry of CPU/RAM utilization.
|
||||
- **Seizing:** Automated scaling triggers (Auto-scaling groups) provisioning resources in response to demand.
|
||||
- **Reconfiguring:** Live migration of VMs across hosts to optimize power or avoid failure.
|
||||
- **Temporal Shift:** Agility in virtual SCM is measured in milliseconds rather than weeks.
|
||||
|
||||
## Transaction Cost Economics (TCE)
|
||||
- **General Purpose:** Analyzes the "make vs. buy" decision based on transaction costs and asset specificity.
|
||||
- **Application to Virtual Resources:**
|
||||
- **The Cloud Shift:** Moving from on-prem (Make) to Cloud (Buy) reduces transaction costs, converting Capital Expenditure (CapEx) into Operational Expenditure (OpEx).
|
||||
- **Asset Specificity & Lock-in:** Occurs when users adopt provider-specific APIs or proprietary formats (e.g., DynamoDB), increasing "switching costs."
|
||||
|
||||
## Agency Theory
|
||||
- **General Purpose:** Examines the relationship between a 'principal' and an 'agent' and the conflicts of interest that arise when goals are misaligned.
|
||||
- **Application to Virtual Resources:** Relevant in the context of SLAs (Service Level Agreements) and the governance of managed services where the provider (agent) manages resources for the user (principal).
|
||||
|
||||
## Contingency Theory
|
||||
- **General Purpose:** Suggests there is no single "best way" to manage a supply chain; the optimal approach depends on the internal and external situation.
|
||||
- **Application to Virtual Resources:** Justifies different orchestration strategies depending on the workload volatility (e.g., steady-state enterprise apps vs. highly volatile viral content).
|
||||
@@ -0,0 +1,25 @@
|
||||
# Practical Frameworks
|
||||
|
||||
Industry-standard frameworks allow practitioners to map processes and benchmark performance.
|
||||
|
||||
## The SCOR Model (Supply Chain Operations Reference)
|
||||
The SCOR model is the gold standard for process management. Below is the adaptation of the SCOR processes for virtual/digital supply chains:
|
||||
|
||||
| SCOR Process | Physical SCM Interpretation | Virtual Resource Interpretation |
|
||||
| :--- | :--- | :--- |
|
||||
| **Plan** | Demand forecasting, Production scheduling | Capacity planning, Predictive auto-scaling |
|
||||
| **Source** | Procurement of raw materials/parts | Procurement of servers, NICs, Disk arrays |
|
||||
| **Make** | Manufacturing, Assembly | **Virtualization:** Hypervisor slicing, Containerization |
|
||||
| **Deliver** | Warehousing, Logistics, Shipping | **Orchestration:** API calls, Network routing, VM deployment |
|
||||
| **Return** | Reverse logistics, Recycling | **De-provisioning:** Releasing RAM/CPU back to the pool |
|
||||
| **Enable** | Management, Data, Infrastructure | **Control Plane:** Kubernetes, OpenStack, Cloud Console |
|
||||
|
||||
## Critical Breakdowns in Adaptation
|
||||
When moving from physical to virtual frameworks, three key concepts shift:
|
||||
1. **Lead Time:** Physical lead time (shipping) is replaced by near-instantaneous delivery, although the "sourcing" of physical hardware still retains traditional lead times.
|
||||
2. **Waste:** Physical scrap is replaced by **"Resource Stranding"**—where one resource (e.g., RAM) is exhausted, rendering other available resources (e.g., CPU) unusable.
|
||||
3. **Logistics:** Transportation is replaced by **Network Latency**. The "last mile" is the distance between the edge server and the end-user.
|
||||
|
||||
## Other Relevant Frameworks
|
||||
- **The Five Critical Phases:** Planning $\rightarrow$ Sourcing $\rightarrow$ Manufacturing $\rightarrow$ Delivery $\rightarrow$ Returns.
|
||||
- **Digital Supply Chain Frameworks:** Emphasis on "Digital Twins," IoT real-time visibility, and AI-driven predictive analytics to transition from reactive to proactive management.
|
||||
@@ -0,0 +1,14 @@
|
||||
# Practitioner's Perspective
|
||||
|
||||
Modern SCM is viewed as a series of integrated material, information, and financial flows.
|
||||
|
||||
## Core Methodologies
|
||||
- **Demand Planning:** Shifting from historical data to AI-driven predictive forecasting.
|
||||
- **Inventory Management:** Utilizing Just-in-Time (JIT) and Safety Stock optimization to balance cost and availability.
|
||||
- **Lean vs. Agile:** Reducing waste (Lean) while maintaining the ability to pivot rapidly (Agile).
|
||||
|
||||
## The Modern Shift: Agility and Resilience
|
||||
Professionals are moving away from purely cost-optimized, "just-in-time" chains toward **Resilience**.
|
||||
- **Diversification:** Reducing reliance on single suppliers to avoid catastrophic failures.
|
||||
- **Digital Service Agility:** In the context of digital services, resilience means the ability to handle massive, unpredictable spikes in demand without service degradation.
|
||||
- **Sustainability:** Integration of circular supply chains and carbon footprint reduction.
|
||||
@@ -0,0 +1,19 @@
|
||||
# Virtual Resource Deep-Dive
|
||||
|
||||
Virtual SCM focuses on the algorithmic flow of capacity rather than the physical flow of goods.
|
||||
|
||||
## Demand for Digital Content (The "Cat Meme" Effect)
|
||||
When content goes viral, the virtual supply chain reacts through:
|
||||
- **Immediate Elasticity:** The system senses a spike in CPU utilization $\rightarrow$ triggers auto-scaling $\rightarrow$ increases the "supply" of compute.
|
||||
- **Edge Distribution:** CDNs replicate the asset (the meme) to edge servers, moving "inventory" closer to theuser to minimize latency.
|
||||
- **Bottleneck Shift:** The constraint shifts from "production" (generating the page) to "network throughput" and "regional capacity limits."
|
||||
|
||||
## Cloud Capacity Procurement
|
||||
- **Storage as a Commodity:** Services like **GCS (Google Cloud Storage)** and **S3 (Amazon S3)** treat vast pools of unstructured data as a scalable, virtualized commodity, abstracting the physical disks from the user.
|
||||
- **Overcommitment:** Providers often "over-sell" virtual resources (e.g., CPU overcommitment), betting that not all tenants will peak simultaneously—a form of virtual inventory speculation.
|
||||
|
||||
## Mapping Virtual Services to Physical Resources
|
||||
The "production" of a virtual service is the mapping of software requirements to physical hardware:
|
||||
- **Generic Resources:** The primary raw materials are **CPU** and **RAM**.
|
||||
- **Resource Stranding:** A critical failure in virtual SCM where a physical host has available CPU but is out of RAM, leading to wasted, unusable capacity.
|
||||
- **Orchestration:** Tools like **Kubernetes** act as the "Supply Chain Manager," performing real-time planning and delivery of resources.
|
||||
@@ -0,0 +1,16 @@
|
||||
# Annotated Bibliography
|
||||
|
||||
## Theory
|
||||
- **Barney, J. B. (1991). *Firm Resources and Sustained Competitive Advantage*.** Foundational text for the Resource-Based View (RBV).
|
||||
- **Teece, D. J., et al. (1997). *Dynamic Capabilities and Strategic Management*.** Defines the ability to integrate and reconfigure competencies (DCT).
|
||||
- **McIvor (2009). *How the transaction cost and resource‐based theories of the firm inform outsourcing evaluation*.** Integrates TCE and RBV for outsourcing analysis.
|
||||
|
||||
## Frameworks & Standards
|
||||
- **Association for Supply Chain Management (ASCM). *SCOR Model*.** The industry-standard process reference model for SCM.
|
||||
- **American Productivity & Quality Center (APQC). *SCM Benchmarks*.** Provides standardized performance metrics for supply chain operations.
|
||||
|
||||
## Virtual Resources & Cloud Computing
|
||||
- **Song, W. *Dynamic Resource Allocation using Virtual Machines for Cloud Computing*.** Explores the mechanics of allocating virtual resources dynamically.
|
||||
- **ResearchGate. *Cloud Computing Virtualization of Resources Allocation for Distributed Systems*.** Technical analysis of how physical resources are virtualized.
|
||||
- **IEEE Explore. *Towards Intelligent Resource Allocation in Highly-Distributed Content Delivery Networks (CDNs)*.** Discusses optimization of content placement and routing.
|
||||
- **Google Research. *Solving virtual machine puzzles: How AI is optimizing cloud computing*.** Demonstrates the use of AI to minimize resource stranding and maximize hardware utilization.
|
||||
@@ -0,0 +1,93 @@
|
||||
# Supply Chain Tooling: From ERPs to Orchestrators
|
||||
|
||||
## Introduction
|
||||
The management of resources—whether they are physical goods moving through a global shipping network or virtual compute cycles moving through a distributed cloud environment—shares a fundamental logic: the need for planning, sourcing, execution, and monitoring. While traditional Supply Chain Management (SCM) deals with the "atoms" of the physical world, Virtual Resource Orchestration deals with the "bits" of the digital world. This chapter explores the tooling ecosystem that enables these two parallel supply chains, moving from the monolithic Enterprise Resource Planning (ERP) systems of old to the dynamic orchestrators of the modern cloud.
|
||||
|
||||
---
|
||||
|
||||
## 1. Traditional SCM Tooling: Managing the Physical Flow
|
||||
|
||||
Traditional SCM tools are designed to handle the complexity of procurement, inventory, logistics, and distribution. These tools typically focus on reducing lead times, optimizing warehouse space, and ensuring the right product reaches the right customer at the right time.
|
||||
|
||||
### 1.1 Enterprise Resource Planning (ERP)
|
||||
ERPs serve as the "single source of truth" for a company's operations, integrating finance, HR, and supply chain into one database.
|
||||
|
||||
| Tool | Primary Function | Type | Role in SCM |
|
||||
| :--- | :--- | :--- | :--- |
|
||||
| **SAP S/4HANA** | Comprehensive business suite for large enterprises. | Commercial | Planning & Sourcing |
|
||||
| **Oracle SCM Cloud** | Integrated cloud suite for supply chain and logistics. | Commercial | Planning & Execution |
|
||||
| **Odoo** | Modular ERP with a strong focus on flexibility and ease of use. | Open-Source / Commercial | Planning, Sourcing & Execution |
|
||||
|
||||
### 1.2 Specialized Execution Systems (WMS & TMS)
|
||||
When an ERP's native capabilities are insufficient for complex logistics, specialized systems are deployed.
|
||||
|
||||
| Tool | Primary Function | Type | Role in SCM |
|
||||
| :--- | :--- | :--- | :--- |
|
||||
| **Manhattan Associates** | Advanced Warehouse Management Systems (WMS). | Commercial | Execution (Warehousing) |
|
||||
| **Blue Yonder** | Transportation Management (TMS) and demand planning. | Commercial | Execution (Transport) |
|
||||
| **Fishbowl** | Inventory management and basic WMS for SMBs. | Commercial | Execution (Warehousing) |
|
||||
|
||||
### 1.3 Planning and Sourcing Tools
|
||||
These tools focus on the "upstream" part of the supply chain: demand forecasting and supplier management.
|
||||
|
||||
| Tool | Primary Function | Type | Role in SCM |
|
||||
| :--- | :--- | :--- | :--- |
|
||||
| **Kinaxis** | Concurrent planning and agility for demand/supply. | Commercial | Planning |
|
||||
| **o9 Solutions** | AI-powered platform for integrated business planning. | Commercial | Planning |
|
||||
| **SAP Ariba** | Cloud-based procurement and supplier management. | Commercial | Sourcing |
|
||||
|
||||
---
|
||||
|
||||
## 2. Virtual Resource Orchestration: The Digital Supply Chain
|
||||
|
||||
In the realm of cloud computing, the "supply chain" consists of CPU, RAM, Storage, and Network bandwidth. Orchestration tools act as the managers that procure these resources from cloud providers and distribute them to applications.
|
||||
|
||||
### 2.1 Container Orchestration (The "Execution" Layer)
|
||||
If a container is a "package," then an orchestrator is the warehouse manager that decides where each package goes and how it scales.
|
||||
|
||||
| Tool | Primary Function | Type | Role in SCM |
|
||||
| :--- | :--- | :--- | :--- |
|
||||
| **Kubernetes** | The industry standard for automating deployment and scaling of containers. | Open-Source | Execution |
|
||||
| **HashiCorp Nomad** | Flexible orchestrator for both containerized and non-containerized workloads. | Open-Source / Commercial | Execution |
|
||||
| **Docker Swarm** | Native orchestration for Docker containers, focused on simplicity. | Open-Source | Execution |
|
||||
|
||||
### 2.2 Infrastructure as Code (IaC) and CMPs (The "Planning & Sourcing" Layer)
|
||||
Before an application can run, the infrastructure must be "sourced" (provisioned). IaC allows this to be done via code.
|
||||
|
||||
| Tool | Primary Function | Type | Role in SCM |
|
||||
| :--- | :--- | :--- | :--- |
|
||||
| **Terraform** | Declarative tool to provision resources across multiple cloud providers. | Open-Source / Commercial | Planning & Sourcing |
|
||||
| **Pulumi** | Use general-purpose languages (TypeScript, Python) to define infrastructure. | Open-Source / Commercial | Planning & Sourcing |
|
||||
| **Crossplane** | Extends Kubernetes to manage external infrastructure via a control plane. | Open-Source | Sourcing |
|
||||
| **Ansible** | Configuration management tool for automating server setup. | Open-Source | Execution (Config) |
|
||||
| **AWS CloudFormation**| AWS-native infrastructure provisioning. | Free (with AWS) | Sourcing |
|
||||
| **Azure Bicep** | Azure-native domain-specific language for deploying resources. | Free (with Azure) | Sourcing |
|
||||
|
||||
### 2.3 Monitoring and Observability (The "Sensing" Layer)
|
||||
In the Digital Control Tower (DCT) model, sensing is critical. These tools provide the real-time visibility necessary to adjust the virtual supply chain.
|
||||
|
||||
| Tool | Primary Function | Type | Role in SCM |
|
||||
| :--- | :--- | :--- | :--- |
|
||||
| **Prometheus** | Time-series database and monitoring system for metrics. | Open-Source | Monitoring/Sensing |
|
||||
| **Grafana** | Visual dashboarding for metrics and logs. | Open-Source / Commercial | Monitoring/Sensing |
|
||||
| **Datadog** | Full-stack observability platform with AI-driven insights. | Commercial | Monitoring/Sensing |
|
||||
|
||||
---
|
||||
|
||||
## 3. Comparative Analysis: Physical vs. Virtual Tooling
|
||||
|
||||
The evolution of these two fields shows a striking convergence in philosophy.
|
||||
|
||||
| Dimension | Traditional SCM | Virtual Orchestration | Parallel Logic |
|
||||
| :--- | :--- | :--- | :--- |
|
||||
| **Unit of Work** | Pallet / Container / SKU | Container / Pod / VM | The "Standard Unit" of transport. |
|
||||
| **Planning** | Demand Forecasting / MRP | Terraform / Pulumi | Defining the desired state. |
|
||||
| **Sourcing** | Procurement / Vendor Mgmt | Cloud APIs / Crossplane | Acquiring the necessary capacity. |
|
||||
| **Execution** | WMS / TMS / Shipping | Kubernetes / Nomad | Moving and placing the resource. |
|
||||
| **Sensing** | IoT / RFID / Inventory Audit | Prometheus / Grafana | Real-time state validation. |
|
||||
|
||||
### From Monoliths to Microservices
|
||||
Traditional SCM began with the "Monolithic ERP"—a single, massive system that did everything. Virtual orchestration, conversely, was born in the era of microservices, favoring "Best-of-Breed" tools (e.g., Prometheus for metrics, Grafana for views, K8s for execution) connected by APIs. Interestingly, modern ERPs like Odoo are moving toward the modular, API-driven approach of the cloud, while cloud platforms are creating more integrated "portals" that resemble the all-in-one nature of early ERPs.
|
||||
|
||||
## Conclusion
|
||||
Whether managing a fleet of trucks or a fleet of clusters, the goal remains the same: **optimization of resource flow**. The transition from ERPs to Orchestrators represents a shift from static, long-term planning to dynamic, real-time adjustment. Understanding both ecosystems allows architects to apply the rigor of industrial supply chain management to the volatility of the cloud.
|
||||
Reference in New Issue
Block a user