Welcome!

Microservices Expo Authors: Stackify Blog, Aruna Ravichandran, Dalibor Siroky, Kevin Jackson, PagerDuty Blog

Related Topics: Microservices Expo, Java IoT, Industrial IoT, Machine Learning

Microservices Expo: Blog Feed Post

The Solution Acquisition Architect - Sharding the Procurement

The SA's role is essentially to be the IT architecture, engineering and resource management lead

The role, impact and usefulness of the "Solution Architect" (i.e., "SA" to the "Enterprise Architect" or "System Architect") has been clarifying for several years across the IT Consulting community, particularly given the increasingly complex nature of SOA, Cloud-centric and Multi-Platform solutions required to meet increasingly real-time, agile and resource-constrained business information management requirements. The SA's role is essentially to be the IT architecture, engineering and resource management lead, as an IT solution is first conceived, planned and begins implementation.

Very often, the SA's efforts are initially delivered as part of a proposal - complete with an engineering plan and schedule, high-level system architecture and product list, plus a cost estimate (both labor and direct). This typically assumes the proposals are meeting pre-defined acquisition strategies - i.e. they need to be "Firm Fixed Price", "Cost-Plus", fall as Task Orders under a previously-awarded "IDIQ", etc.

Therefore, the acquisition strategy may in fact be introducing constraints or guidance into proposed solutioning that don't necessary result in the best, most creative and informed solution. The acquisition strategy in effect doesn't result in the very best, informed responses from the IT vendor and consulting community.

Mitigation strategies that government agencies leverage sometimes include early series of "Requests for Information (RFIs)", Industry Days with Q/A sessions, "Draft" RFPs (soliciting feedback before the final is published), Prototype Bake-Offs, etc. There are actually many variations on the theme of soliciting input from the contractor community, in order to produce the most fair, value-add and mission-acceptable RFP. But this is usually after the acquisition strategy has been defined.

In my experience, on both sides of the Federal (and commercial) IT acquisition process (helping to develop and conduct acquisitions, as well as leading responses), a "Solution Acquisition Architect" would be a much-needed addition to the acquisition management team (SAA). This role would essentially operate as a traditional SA, commensurate with IT consulting best practices, but help shape an appropriate acquisition approach (and ultimately the RFP, procurement T&C or contract) in a way that best anticipates the response and capabilities of the IT consulting/vendor community and technology context.

This line of thinking was recently crystallized (to me) after reading the recent FCW Joint Special Report

on the readiness of the Federal Government for procuring cloud services. The series of articles essentially summarize that the Government's current procurement methods, skills and resources aren't yet optimized for obtaining cloud services.

I might go further and posit that the procurement resources aren't only sub-optimal for addressing cloud services, but also for a number of current trends in dealing with information access, visualization and delivery across the traditional firewalls - including SOA integration, open-sourced data visualization and situational awareness, mobile and "big" data management, etc.

One reason the procurement resources are sub-optimal, and tend to result in procurements that are too long, cost-ineffective, too rigid and ultimately not the very best value, is because the role of the Solution Architect isn't standard in designing the acquisition plan and ultimate solicitation. Many times the available technical architects, SMEs, or separately-contracted PMO shops are pressed into service, to generate the RFP language, review the RFIs, confirm the FFP/Single Contract approach.

However, the solution architect-standard methodology and input that might deliver a solicitation (possibly spread among multiple types of awards, and extending or leveraging existing contracts) that is likely to attract the most advanced, real-world experienced thinking and sourcing to the project - simply isn't used.

This of course assumes that there exist Solution Architects and methodology that includes the knowledge of acquisition types, risks, constraints, processes. That's hard to find, especially on the solicitor side of the table. One suggestion might be to establish a program that rotates industry SAs into the Federal Government, for purposes of supporting acquisition strategies, and also to help develop pockets of expertise within the Government procurement community who are aligned with and cognizant of the vendor response communities solution architecture methodologies.

At the end of the day, the right help might be requested in the right manner, from the best available respondents - and maybe the "Cloud Services Procurement" that's been taking 6 months to complete, can be "sharded" more efficiently into reasonable, informed and truly useful procurement options.

Read the original blog entry...

More Stories By Ted McLaughlan

Summary: Currently a Federal Enterprise Architect with Oracle, Ted has over 25 years in Commercial and Government Information Technology with University of Virginia, EDS, Accenture, KME Internet Marketing, Blackstone Technology Group, NavigationArts and CSC; additional focus recently on Interactive Design, Web 2.0 Internet Marketing, SEO, Social Media and Advertising. Specialties: Enterprise Architecture and Information Management, SOA/ESB, Enterprise Integration, Business Intelligence, Internet Safety and Security, Family Content Networks, Knowledge Management and Collaboration, User-Defined Operational Pictures/Common Operating Pictures (UDOP/COP), Situational Awareness, Portals, Internet Marketing and Search Engine Optimization (SEO), Website Design/Development and Optimization - Certified Systems Engineer - Certified Enterprise Solution Architect

@MicroservicesExpo Stories
How is DevOps going within your organization? If you need some help measuring just how well it is going, we have prepared a list of some key DevOps metrics to track. These metrics can help you understand how your team is doing over time. The word DevOps means different things to different people. Some say it a culture and every vendor in the industry claims that their tools help with DevOps. Depending on how you define DevOps, some of these metrics may matter more or less to you and your team.
For many of us laboring in the fields of digital transformation, 2017 was a year of high-intensity work and high-reward achievement. So we’re looking forward to a little breather over the end-of-year holiday season. But we’re going to have to get right back on the Continuous Delivery bullet train in 2018. Markets move too fast and customer expectations elevate too precipitously for businesses to rest on their laurels. Here’s a DevOps “to-do list” for 2018 that should be priorities for anyone w...
If testing environments are constantly unavailable and affected by outages, release timelines will be affected. You can use three metrics to measure stability events for specific environments and plan around events that will affect your critical path to release.
In a recent post, titled “10 Surprising Facts About Cloud Computing and What It Really Is”, Zac Johnson highlighted some interesting facts about cloud computing in the SMB marketplace: Cloud Computing is up to 40 times more cost-effective for an SMB, compared to running its own IT system. 94% of SMBs have experienced security benefits in the cloud that they didn’t have with their on-premises service
DevOps failure is a touchy subject with some, because DevOps is typically perceived as a way to avoid failure. As a result, when you fail in a DevOps practice, the situation can seem almost hopeless. However, just as a fail-fast business approach, or the “fail and adjust sooner” methodology of Agile often proves, DevOps failures are actually a step in the right direction. They’re the first step toward learning from failures and turning your DevOps practice into one that will lead you toward even...
DevOps is under attack because developers don’t want to mess with infrastructure. They will happily own their code into production, but want to use platforms instead of raw automation. That’s changing the landscape that we understand as DevOps with both architecture concepts (CloudNative) and process redefinition (SRE). Rob Hirschfeld’s recent work in Kubernetes operations has led to the conclusion that containers and related platforms have changed the way we should be thinking about DevOps and...
The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Microservices being modular these are faster to change and enables an evolutionary architecture where systems can change, as the business needs change. Microservices can scale elastically and by being service oriented can enable APIs natively. Microservices also reduce implementation and release cycle time and enables continuous delivery. This paper provides a logical overview of the Mi...
While walking around the office I happened upon a relatively new employee dragging emails from his inbox into folders. I asked why and was told, “I’m just answering emails and getting stuff off my desk.” An empty inbox may be emotionally satisfying to look at, but in practice, you should never do it. Here’s why. I recently wrote a piece arguing that from a mathematical perspective, Messy Desks Are Perfectly Optimized. While it validated the genius of my friends with messy desks, it also gener...
The next XaaS is CICDaaS. Why? Because CICD saves developers a huge amount of time. CD is an especially great option for projects that require multiple and frequent contributions to be integrated. But… securing CICD best practices is an emerging, essential, yet little understood practice for DevOps teams and their Cloud Service Providers. The only way to get CICD to work in a highly secure environment takes collaboration, patience and persistence. Building CICD in the cloud requires rigorous ar...
The enterprise data storage marketplace is poised to become a battlefield. No longer the quiet backwater of cloud computing services, the focus of this global transition is now going from compute to storage. An overview of recent storage market history is needed to understand why this transition is important. Before 2007 and the birth of the cloud computing market we are witnessing today, the on-premise model hosted in large local data centers dominated enterprise storage. Key marketplace play...
The cloud revolution in enterprises has very clearly crossed the phase of proof-of-concepts into a truly mainstream adoption. One of most popular enterprise-wide initiatives currently going on are “cloud migration” programs of some kind or another. Finding business value for these programs is not hard to fathom – they include hyperelasticity in infrastructure consumption, subscription based models, and agility derived from rapid speed of deployment of applications. These factors will continue to...
Some people are directors, managers, and administrators. Others are disrupters. Eddie Webb (@edwardawebb) is an IT Disrupter for Software Development Platforms at Liberty Mutual and was a presenter at the 2016 All Day DevOps conference. His talk, Organically DevOps: Building Quality and Security into the Software Supply Chain at Liberty Mutual, looked at Liberty Mutual's transformation to Continuous Integration, Continuous Delivery, and DevOps. For a large, heavily regulated industry, this task ...
Following a tradition dating back to 2002 at ZapThink and continuing at Intellyx since 2014, it’s time for Intellyx’s annual predictions for the coming year. If you’re a long-time fan, you know we have a twist to the typical annual prediction post: we actually critique our predictions from the previous year. To make things even more interesting, Charlie and I switch off, judging the other’s predictions. And now that he’s been with Intellyx for more than a year, this Cortex represents my first ...
"Grape Up leverages Cloud Native technologies and helps companies build software using microservices, and work the DevOps agile way. We've been doing digital innovation for the last 12 years," explained Daniel Heckman, of Grape Up in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
The Toyota Production System, a world-renowned production system is based on the "complete elimination of all waste". The "Toyota Way", grounded on continuous improvement dates to the 1860s. The methodology is widely proven to be successful yet there are still industries within and tangential to manufacturing struggling to adopt its core principles: Jidoka: a process should stop when an issue is identified prevents releasing defective products
Defining the term ‘monitoring’ is a difficult task considering the performance space has evolved significantly over the years. Lately, there has been a shift in the monitoring world, sparking a healthy debate regarding the definition and purpose of monitoring, through which a new term has emerged: observability. Some of that debate can be found in blogs by Charity Majors and Cindy Sridharan.
We seem to run this cycle with every new technology that comes along. A good idea with practical applications is born, then both marketers and over-excited users start to declare it is the solution for all or our problems. Compliments of Gartner, we know it generally as “The Hype Cycle”, but each iteration is a little different. 2018’s flavor will be serverless computing, and by 2018, I mean starting now, but going most of next year, you’ll be sick of it. We are already seeing people write such...
It’s “time to move on from DevOps and continuous delivery.” This was the provocative title of a recent article in ZDNet, in which Kelsey Hightower, staff developer advocate at Google Cloud Platform, suggested that “software shops should have put these concepts into action years ago.” Reading articles like this or listening to talks at most DevOps conferences might make you think that we’re entering a post-DevOps world. But vast numbers of organizations still struggle to start and drive transfo...
Let's do a visualization exercise. Imagine it's December 31, 2018, and you're ringing in the New Year with your friends and family. You think back on everything that you accomplished in the last year: your company's revenue is through the roof thanks to the success of your product, and you were promoted to Lead Developer. 2019 is poised to be an even bigger year for your company because you have the tools and insight to scale as quickly as demand requires. You're a happy human, and it's not just...
"Opsani helps the enterprise adopt containers, help them move their infrastructure into this modern world of DevOps, accelerate the delivery of new features into production, and really get them going on the container path," explained Ross Schibler, CEO of Opsani, and Peter Nickolov, CTO of Opsani, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.