Point of sale - Common architectural elements

Part 2 - Common architectural elements

In our previous article from this series we've introduced a use case around point of sale imaging for retail stores.

The process was laid out how we've approached the use case and how portfolio solutions are the base for researching a generic architecture. 

The only thing left to cover was the order in which you'll be led through the architecture details.

This article starts the real journey at the very top, with a generic architecture from which we'll discuss the common architectural elements one by one.

This will start our journey into the logical elements that make up the point of sale imaging architecture.

Point of sale - An architectural introduction

This article kicks off the first in the series sharing another new architecture. It's focusing on presenting access to ways of mapping successful implementations for specific use cases.

It's an interesting challenge creating architectural content based on common customer adoption patterns. That's very different from most of the traditional marketing activities usually associated with generating content for the sole purpose of positioning products for solutions. When you're basing the content on actual execution in solution delivery, you're cutting out the chuff. 

What's that mean?

It means that it's going to provide you with a way to implement a solution using open source technologies by focusing on the integrations, structures and interactions that actually have been proven to work. What's not included are any vendor promises that you'll find in normal marketing content. Those promised that when it gets down to implementation crunch time, might not fully deliver on their promises.

Enter the term Portfolio Architecture. 

Let's look at these architectures, how they're created and what value they provide for your solution designs.

How to setup the OpenShift Container Platform 4.7 on your local machine

 Are you looking to develop a few projects on your local machine and push them on to a real OpenShift Container Platform without having to worry about cloud hosting of your container platform?

Would you like to do that on one of the newer versions of OpenShift Container Platform such as version 4.7?

Look no further as CodeReady Containers puts it all at your fingertips. Experience the joys of cloud native development and automated rolling deployments. 

The idea was to make this as streamlined of an experience as possible by using the same CodeReady Containers Easy Install project. Let's take a look at what this looks like.

Supply chain integration - Example store integration architecture

Part 3 - Example store integration architecture

 In our previous article from this series shared a look at the logical common architectural elements found in supply chain integration for retail stores.

The process was laid out how we've approached the use case and how portfolio solutions are the base for researching a generic architecture. 

It started with laying out the process of how we've approached the use case by researching successful customer portfolio solutions as the basis for a generic architecture.

Having completed our discussions on the logical view of the architecture, it's now time to look at a specific example.

This article walks you through an example store integration scenario showing how expanding the previously discussed elements provides an example for your own store integration scenarios.

Supply chain integration - Common architectural elements

Part 2 - Common architectural elements

 In our previous article from this series we introduced a use case around supply chain integration for retail stores.

The process was laid out how we've approached the use case and how portfolio solutions are the base for researching a generic architecture. 

The only thing left to cover was the order in which you'll be led through the architectural details.

This article starts the real journey at the very top, with a generic architecture from which we'll discuss the common architectural elements one by one.

This will start our journey into the logical elements that make up the supply chain integration architecture.

Windows 10 installation using USB stick won't install, fix formatting USB with MBR using a Mac (error 0x80300002)

It's been some years since I have had to do anything with a Windows installer, but this last week I spent the better part of four hours wrestling with installing Windows 10 on a brand new gaming machine.

Now I know that this should be really straight forward as it's just a normal disk in a desktop machine, but it really seems to be a tricky problem due to the lack of clear error messages you get when it fails to start the installation.

The basis is getting a valid copy of Windows 10 in an ISO download, putting it on a bootable USB stick, putting that in a port on the new machine, booting the machine to start the USB installer, clicking a few times to get your new disk formatted, partitioned, and finally watching the installation start copying files onto your new machine.

You would think it's that easy, right?

My journey was a bit harder than that... but I want to share the solution for others.

Supply chain integration - An architectural introduction

Part 1 - An architectural introduction

If you've been following the writing here over the last few years, you've grown accustomed to the sharing of various architectures. They're focusing on presenting access to ways of mapping successful implementations for specific use cases.

It's an interesting challenge in our mission of creating of architectural content based on common customer adoption patterns. That's very different from most of the traditional marketing activities usually associated with generating content for the sole purpose of positioning products for solutions. When you're basing the content on actual execution in solution delivery, you're cutting out the chuff. 

What's that mean?

It means that it's going to provide you with a way to implement a solution using open source technologies by focusing on the integrations, structures and interactions that actually have been proven to work. What's not included are any vendor promises that you'll find in normal marketing content. Those promised that when it gets down to implementation crunch time, might not fully deliver on their promises.

Enter the term Portfolio Architecture. 

Let's look at these architectures, how they're created and what value they provide for your solution designs.

Business optimisation architecture - Example vaccine scheduling

Part 4 - Example vaccine scheduling

In the previous article from this series we looked at an example architecture for retail planning optimisation.

It started with laying out the process of how we've approached the use case by researching successful customer portfolio solutions as the basis for a generic architecture.

The specific example of how retail organisations can optimise delivery planning, employee rostering, and optimise task assignments was laid out in the architecture diagram.

This article continues on with another specific example that focuses on how retail stores around the world are helping deliver vaccinations through their pharmacies. It walks you through an example optimisation scenario showing how to provide for customer vaccine scheduling.

Business optimisation architecture - Example planning optimisation

Part 3 - Example planning optimisation

In our previous article from this series we shared the logical view of the business optimisation use case for retail stores.

The process was laid out how we've approached the use case and how portfolio solutions are the base for researching a generic architecture. 

It started with laying out the process of how we've approached the use case by researching successful customer portfolio solutions as the basis for a generic architecture.

Having completed our discussions on the logical view of the architecture, it's now time to look at a specific example.

This article walks you through an example optimisation scenario showing how expanding the previously discussed elements provides an architecture for your own optimisation scenarios.