Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions content/en/casestudies/_index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
---
title: "Case Studies & Sucess Stories "
linkTitle: "Case Studies"
description: "Discover how organizations are leveraging SW360 to improve their software supply chain management and compliance workflows"
menu:
main:
weight: 80
---
---
Welcome to our Success Stories section! Here you'll find real-world examples of how organizations are using SW360 to transform their software supply chain management and compliance processes. These stories showcase the practical benefits and impact of implementing SW360 in various organizational contexts.

Each success story provides detailed insights into:
- The organization's challenges before implementing SW360

Check failure on line 13 in content/en/casestudies/_index.md

View workflow job for this annotation

GitHub Actions / linter_check

Lists should be surrounded by blank lines

content/en/casestudies/_index.md:13 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- The organization's challenge..."] https://github.com/DavidAnson/markdownlint/blob/v0.37.4/doc/md032.md
- How they integrated SW360 into their workflow
- The specific benefits and improvements achieved
- Key metrics and results
- Best practices and lessons learned

We invite you to explore these stories to understand how SW360 can help your organization improve its software supply chain management and compliance processes.

Check failure on line 19 in content/en/casestudies/_index.md

View workflow job for this annotation

GitHub Actions / linter_check

Trailing spaces

content/en/casestudies/_index.md:19:161 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1] https://github.com/DavidAnson/markdownlint/blob/v0.37.4/doc/md009.md

Check failure on line 19 in content/en/casestudies/_index.md

View workflow job for this annotation

GitHub Actions / linter_check

Files should end with a single newline character

content/en/casestudies/_index.md:19:161 MD047/single-trailing-newline Files should end with a single newline character https://github.com/DavidAnson/markdownlint/blob/v0.37.4/doc/md047.md
92 changes: 92 additions & 0 deletions content/en/casestudies/bosch-implementation.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,92 @@
---
title: "Bosch: Streamlining Software Supply Chain Management with SW360"
description: "How Bosch Implemented SW360 to Enhance Software Component Management, Ensure Compliance, and Streamline Workflow Integration."
date: 2024-03-20
image: "img/casestudies/bosch2-logo.jpg"
layout: "casestudies/single"
---

## The Challenge
---

Bosch, a leading global supplier of technology and services, faced significant challenges in managing their software supply chain. With thousands of software components used across their products, they needed a robust solution to:

- Track and manage software components across their global operations
- Ensure compliance with various license requirements
- Maintain accurate software bill of materials (SBOM)
- Streamline the approval process for new software components

Check failure on line 17 in content/en/casestudies/bosch-implementation.md

View workflow job for this annotation

GitHub Actions / linter_check

Lists should be surrounded by blank lines

content/en/casestudies/bosch-implementation.md:17 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Streamline the approval proc..."] https://github.com/DavidAnson/markdownlint/blob/v0.37.4/doc/md032.md
---
## The Solution
---
Bosch implemented SW360 as their central software component management platform. The implementation included:

- Integration with their existing development tools and workflows
- Customization of SW360 to match their specific requirements
- Training of teams across different departments
- Establishment of clear processes for component management

Check failure on line 26 in content/en/casestudies/bosch-implementation.md

View workflow job for this annotation

GitHub Actions / linter_check

Lists should be surrounded by blank lines

content/en/casestudies/bosch-implementation.md:26 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Establishment of clear proce..."] https://github.com/DavidAnson/markdownlint/blob/v0.37.4/doc/md032.md
---
## Key Benefits
---
#### 1. **Improved Efficiency**

Check failure on line 30 in content/en/casestudies/bosch-implementation.md

View workflow job for this annotation

GitHub Actions / linter_check

Heading levels should only increment by one level at a time

content/en/casestudies/bosch-implementation.md:30 MD001/heading-increment Heading levels should only increment by one level at a time [Expected: h3; Actual: h4] https://github.com/DavidAnson/markdownlint/blob/v0.37.4/doc/md001.md
- Reduced time for software component approval by 60%

Check failure on line 31 in content/en/casestudies/bosch-implementation.md

View workflow job for this annotation

GitHub Actions / linter_check

Unordered list indentation

content/en/casestudies/bosch-implementation.md:31:1 MD007/ul-indent Unordered list indentation [Expected: 0; Actual: 3] https://github.com/DavidAnson/markdownlint/blob/v0.37.4/doc/md007.md

Check failure on line 31 in content/en/casestudies/bosch-implementation.md

View workflow job for this annotation

GitHub Actions / linter_check

Lists should be surrounded by blank lines

content/en/casestudies/bosch-implementation.md:31 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Reduced time for software co..."] https://github.com/DavidAnson/markdownlint/blob/v0.37.4/doc/md032.md
- Automated license compliance checks

Check failure on line 32 in content/en/casestudies/bosch-implementation.md

View workflow job for this annotation

GitHub Actions / linter_check

Unordered list indentation

content/en/casestudies/bosch-implementation.md:32:1 MD007/ul-indent Unordered list indentation [Expected: 0; Actual: 3] https://github.com/DavidAnson/markdownlint/blob/v0.37.4/doc/md007.md
- Centralized component information

Check failure on line 33 in content/en/casestudies/bosch-implementation.md

View workflow job for this annotation

GitHub Actions / linter_check

Unordered list indentation

content/en/casestudies/bosch-implementation.md:33:1 MD007/ul-indent Unordered list indentation [Expected: 0; Actual: 3] https://github.com/DavidAnson/markdownlint/blob/v0.37.4/doc/md007.md

#### 2. **Better Compliance**
- Real-time license compliance monitoring
- Automated generation of compliance reports
- Reduced risk of license violations

#### 3. **Enhanced Collaboration**
- Unified platform for all teams
- Improved communication between departments
- Better visibility into software usage
---
## Results
---
- 70% reduction in time spent on manual component tracking
- 90% improvement in license compliance accuracy
- 50% reduction in compliance-related issues
- Significant improvement in audit preparation time
---
## Best Practices Learned
---
1. Start with a clear implementation strategy
2. Involve all relevant stakeholders early
3. Provide comprehensive training
4. Establish clear processes and guidelines
5. Regular review and optimization of workflows
---
## Future Plans
---
Bosch continues to expand their use of SW360, with plans to:

- Integrate with additional development tools
- Implement advanced analytics features
- Expand usage to more business units
- Contribute back to the SW360 community

This success story demonstrates how SW360 can transform software supply chain management in a large enterprise environment, leading to significant improvements in efficiency, compliance, and collaboration.

---
## Conclusion
---
The implementation of SW360 at Bosch has proven to be a transformative solution for their software supply chain management. Through this strategic adoption, Bosch has achieved remarkable improvements in efficiency, compliance, and collaboration across their global operations.

Key takeaways from this implementation include:

- The importance of having a centralized platform for managing software components in a large enterprise
- The significant impact of automation in reducing manual tracking and compliance efforts
- The value of establishing clear processes and providing comprehensive training
- The benefits of improved cross-departmental collaboration and visibility

The success of SW360 at Bosch demonstrates how open-source tools can effectively address complex enterprise challenges in software supply chain management. As Bosch continues to expand their use of SW360 and contribute to its development, they are setting a strong example for other organizations looking to improve their software component management processes.

This case study serves as a testament to how proper implementation of the right tools, combined with well-defined processes and stakeholder engagement, can lead to substantial improvements in enterprise software management practices.

---
##### For an in-depth understanding of how Bosch utilizes SW360, refer to this talk.


{{< youtube ifb8vkfwiT4 >}}

125 changes: 125 additions & 0 deletions content/en/casestudies/siemens-implementation.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,125 @@
---
title: "Siemens Implementation of SW360 "
description: "Siemens, a global leader in industrial automation and digitalization, leverages SW360 to streamline its open-source software (OSS) management across various business units."
date: 2021-01-20
image: "img/casestudies/siemens-logo.webp"
layout: "casestudies/single"
---

## The Challenge
---
**Overview:** Siemens, a global technology powerhouse, faced several challenges in managing their **open-source software (OSS) components** across numerous projects:

- **Centralize** the management of OSS-related data
- **Ensure compliance** with software licenses and security policies
- **Track vulnerabilities** and maintain an accurate **Software Bill of Materials (SBOM)**
- **Improve collaboration** between departments handling OSS components

**Key Pain Points:**
- Decentralized OSS management leading to inefficiencies
- Manual license compliance checks
- Difficulty in tracking and addressing software vulnerabilities
- Lack of effective cross-department collaboration

---

## The Solution
---
Siemens implemented **SW360** as the central OSS management platform to streamline their component tracking and ensure compliance:

- **Centralized Component Repository** for easy access and management of OSS components
- **Automated License Management** via integration with tools like FOSSology for compliance checks
- **Vulnerability Monitoring** with real-time tracking and alerts
- **REST API Integration** for seamless connectivity with existing development tools and workflows

**Technical Enhancements:**
- **Automated license compliance checks**
- **Continuous tracking of vulnerabilities** related to software components
- **Integration with development tools** to streamline OSS management

---

## Key Benefits
---
#### **Improved Efficiency**
**Before SW360:** Component tracking was done manually, leading to time-consuming efforts.
**After SW360:** A centralized platform automated tracking and improved approval processes.

- **Streamlined OSS component management**
- **Faster identification** of component dependencies and versions
- **Reduced manual tracking efforts**

#### **Better Compliance**
**Before SW360:** Compliance checks were manual and required significant effort.
**After SW360:** Real-time automated compliance checks significantly reduced compliance risks.

- **Continuous monitoring of license compliance**
- **Automated generation of compliance reports**
- **Reduced risk of license violations**

#### **Enhanced Collaboration**
**Before SW360:** Teams worked in silos, causing inefficiencies.
**After SW360:** The unified platform improved cross-department collaboration.

- **A single source of truth** for OSS data
- **Better coordination** across teams
- **Improved visibility into software usage**

---

## Results
---
#### **Impact on Siemens’ OSS Management:**
- **Improved component tracking** efficiency
- **Significant reduction** in manual compliance checks
- **Faster identification** and resolution of vulnerabilities
- **Improved audit preparation** through automated compliance reporting

#### **Performance Comparison: Before vs. After SW360**

| **Metric** | **Before SW360** | **After SW360** |
|----------------------------|------------------------------------------|------------------------------------------|
| 🔍 **Component Tracking** | Manual, time-consuming | Automated and centralized |
| 🛠 **Compliance Checks** | Performed manually, prone to errors | Automated with real-time monitoring |
| ⚡ **Approval Process** | Lengthy, multi-step manual process | Streamlined with faster approvals |
| 🔐 **License Violations** | High risk due to lack of real-time tracking | Reduced risk with automated checks |
| 📑 **Audit Preparation** | Labor-intensive, requiring manual data collection | Automated reporting saves time |
| 🤝 **Collaboration** | Siloed teams with limited visibility | Unified platform for seamless teamwork |

**Key Takeaway:** SW360 **significantly enhances efficiency, compliance, and collaboration**, reducing manual effort and improving software supply chain management.


---

## Best Practices Learned
---
- **Tailor the platform** to meet organizational needs
- **Engage key stakeholders early** in the process
- **Train all teams** thoroughly for optimal usage
- **Review and optimize workflows** regularly
- **Leverage automation** for efficiency and accuracy

---

## Future Plans
---
**Next Steps for Siemens:**
- **Expanding integration** with additional security and CI/CD pipelines
- **Implementing advanced analytics** to gain deeper insights
- **Increasing SW360 adoption** across more departments
- **Contributing to the open-source SW360 community**

**Looking Ahead:** Siemens aims to make **OSS management more seamless and secure** through **continuous innovation**.

---

## **Conclusion**
---
This success story highlights how **SW360 has transformed OSS management at Siemens**, leading to **improved efficiency, compliance, and collaboration** across their **software supply chain**.

**Final Thought:** Implementing an OSS management solution like **SW360** can significantly enhance the management of software dependencies at large-scale organizations.

---
##### For an in-depth understanding of how Siemens utilizes SW360, refer to this talk.

{{< youtube iJkyO7nJZaw >}}
85 changes: 85 additions & 0 deletions content/en/casestudies/toshiba-corp-implementation.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,85 @@
---
title: "Toshiba Corporation Utilization of SW360 "
description: "Toshiba Corporation has leveraged SW360 as a centralized platform for open-source software (OSS) compliance management, ensuring efficient tracking, license compliance, and vulnerability management across its software supply chain."
date: 2022-07-12
image: "img/casestudies/toshiba-logo.jpg"
layout: "casestudies/single"
---

## The Challenge
---
Toshiba Corporation, a global technology leader, faced significant challenges in managing their open-source software (OSS) components. With a vast number of software components used across various projects, they needed a robust solution to:

- Centralize the management of OSS-related data
- Ensure compliance with software licenses and security policies
- Track vulnerabilities and maintain an accurate Software Bill of Materials (SBOM)
- Improve collaboration between departments handling OSS components
---
## The Solution
---
Toshiba implemented **SW360** as their primary OSS management platform. The deployment included:

- Integration with their existing development tools and workflows
- Customization of SW360 to enhance dependency management and SBOM tracking
- Training of teams across various departments
- Establishment of clear guidelines and processes for OSS component management

---
## Key Benefits
---

#### **Improved Efficiency**
- Streamlined software component tracking across multiple teams
- Automated management of OSS metadata, including SPDX data
- Faster identification of component dependencies and versions

#### **Better Compliance**
- Real-time monitoring of OSS license compliance
- Automated generation of compliance reports
- Reduced risk of license violations and security vulnerabilities

#### **Enhanced Collaboration**
- Unified platform for all teams involved in OSS management
- Improved communication between different business units
- Better visibility into software usage and dependencies

---
## Results
---
- **Significant reduction in manual tracking efforts** for OSS components
- **Enhanced accuracy in license compliance** and security tracking
- **Improved audit preparation time**, ensuring faster and smoother processes
- **Better integration with SBOM standards**, enhancing transparency in software supply chains

---
## Best Practices Learned
---
- Start with a clear strategy for OSS management
- Involve key stakeholders early in the implementation process
- Provide comprehensive training for all users
- Establish well-defined processes and workflows
- Continuously review and optimize the system based on feedback

---
## Future Plans
---
Toshiba plans to continue expanding their use of SW360 by:

- Integrating with additional development and security tools
- Enhancing analytics capabilities for better decision-making
- Extending SW360 usage to more business units
- Actively contributing to the SW360 open-source community

---
## Conclusion
---

This success story highlights how SW360 has transformed OSS management at Toshiba, leading to improved efficiency, compliance, and collaboration across their software supply chain.

**Final Thought**: Implementing an OSS management solution like SW360 can be a game-changer for organizations dealing with large-scale software dependencies.


This success story highlights how **SW360 has transformed OSS management at Toshiba**, leading to improved efficiency, compliance, and collaboration across their software supply chain.



31 changes: 31 additions & 0 deletions layouts/casestudies/baseof.html
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
<!doctype html>
<html itemscope itemtype="http://schema.org/WebPage"
{{- with .Site.Language.LanguageDirection }} dir="{{ . }}" {{- end -}}
{{ with .Site.Language.Lang }} lang="{{ . }}" {{- end }} {{/**/ -}}
class="no-js">
<head>
{{ partial "head.html" . }}
</head>
<body class="td-{{ .Kind }} td-blog {{- with .Page.Params.body_class }} {{ . }}{{ end }}">
<header>
{{ partial "navbar.html" . }}
</header>
<div class="container-fluid td-outer">
<div class="td-main">
<div class="row flex-xl-nowrap">
<aside class="col-12 col-md-3 col-xl-2 td-sidebar d-print-none">
{{ partial "sidebar.html" . }}
</aside>
<main class="col-12 col-md-9 col-xl-8 ps-md-5 pe-md-4" role="main">
{{ if not (.Param "ui.breadcrumb_disable") -}}
{{ partial "breadcrumb.html" . -}}
{{ end -}}
{{ block "main" . }}{{ end }}
</main>
</div>
</div>
{{ partial "footer.html" . }}
</div>
{{ partial "scripts.html" . }}
</body>
</html>
31 changes: 31 additions & 0 deletions layouts/casestudies/list.html
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
{{ define "main" }}
<div class="td-content">
<div class="container">
<div class="row">
<div class="col-12">
<h1>{{ .Title }}</h1>
<div class="lead">{{ .Content }}</div>
</div>
</div>
<div class="row mt-5 ">
{{ range .Pages.ByDate.Reverse }}
<div class="col-md-6 col-lg-6 mb-4 ">
<div class="card h-100 ">
{{ if .Params.image }}
<img src="{{ .Params.image | relURL }}" class="card-img-top" alt="{{ .Title }}" style="max-height: 200px; object-fit: cover;">
{{ end }}
<div class="card-body">
<h5 class="card-title">{{ .Title }}</h5>
<p class="card-text">{{ .Description }}</p>
<div class="d-flex justify-content-between align-items-center">
<small class="text-bold">{{ .Date.Format "January 2, 2006" }}</small>
<a href="{{ .RelPermalink }}" class="btn btn-primary">Read More</a>
</div>
</div>
</div>
</div>
{{ end }}
</div>
</div>
</div>
{{ end }}
Loading