Loading
Calvin T. Nesbitt
This is a live streamed presentation. You will automatically follow the presenter and see the slide they're currently on.
No presentation currently in progress.
Make a free appointment today!
s
y
s
t
e
m
s
Waiting for humans
Presented by Calvin T. Nesbitt
Founder, Principal Engineer
Founder, Principal Engineer
calvin@designer.systems
This you must always bear in mind,
what is the nature of the whole,
and what is my nature,
and how is this related to that,
and what kind of a part it is
of what kind of a whole.
—Marcus Aurelius
consumer expectations
extent of modern technology
Vendor
Client
service
V
one service to many organizations
C
C
C
many services to one organization
V
V
V
C
V
V
V
C
\( \approx \) fees
V
V
V
network & switching costs
configuration costs
C
\( \bold a \)
V
\( \bold b \)
network & switching costs
configuration costs
C
matrix complexity grows
V
V
V
C
C
C
config costs rise
C
C
C
V
V
V
reduced config costs
increased N&S costs
many-to-many service-organization mapping
M
V
V
V
C
C
C
multisourcing
\( - \space \text{network costs} \)
standard
cutover
procedure
\( - \space \text{switching costs} \)
staff specialization
& automation
\( - \space \text{config costs} \)
economies
of scale
\( - \space \text{config costs} \)
M
V
V
V
C
C
C
The Vendor must grow
M
V
V
V
C
C
C
Generalization
increased MSP fees
larger client pools
increased config costs
M
C
C
C
V
\( \bold v \)
V
\( \text{nas}(\bold v, x) \propto \text{cfg}(\bold v) \)
Never attribute to malice or stupidity that which can be explained by moderately rational individuals following incentives in a complex system.
—Douglas W. Hubbard
Competitive MSPs mitigate platform decay via
V
V
V
C
C
C
V
V
V
C
C
C
custom scale
custom form
general service
destructuring
V
V
V
C
C
C
Robotic Process Automation
Operations Platform Integration
Service-Oriented Architecture
Implementation Strata
input
output
data vendor
client
digest
client
client
control vendors
data vendor
data vendor
Data Flow Category
hook (reactive)
timer (proactive)
data vendors
vendor-agnostic
data structure
stateless functions
Digest
Direct vendor↔vendor integration
Interfaces between platform APIs (hopefully)
\( O_a \)
\( O_b \)
\( O_c \)
Composable output services
data vendor
control vendors
data vendor
data vendor
ACME, Inc.
\( \text{complex vendor} \)
input
digest
API
data vendor
client
client
client
data vendor
data vendor
Nadir LLC
\( \text{complex client} \)
input
output
The significance of the chrysalis is change.
—Thomas Harris
IT Service
Management
Identity
& Access
Management
Customer
Relationship
Management
Network
Monitoring
Systems
NMS
ITSM
CRM
IAM
presentation
procedure*
Stages of information development
narrative
(subjective)
business process as data structure
(objective)
human
reification
HMC pattern
permissions?
pattern
(hardware, networking, virtualization, cloud, multi-cloud, etc.)
Corporate Policy
Corporate Policy
Promises:
Corporate Policy
Realities:
implementation
Integration mitigates vendor change
Architecture tolerates
administration change
Corporate Policy
Automation reflects management change
Designer Systems LLC
Full Customer
Ownership
Complexity
Flexibility
Factoring
Growth
vs. Entropy