Lift & Shift is an approach to migrating a legacy business application hosted in an on-premises data center environment to one hosted in the cloud. The goal is to move the application “as-is,” with little to no changes to the business functions performed by the application. One common lift and shift scenario is the migration of applications that were not originally developed for distributed cloud environments, but once moved, can take advantage of some of the benefits of cloud computing, such as increased availability and/or reduced total cost of operations (TCO).
This blog details some important considerations and challenges associated with the lift and shift method, based on our real-world experiences moving both custom and packaged (commercial) legacy applications to Microsoft Azure. Read More…
What is MTConnect?
MTConnect is the communication standard of choice for manufacturing. It allows organized retrieval of data from shop floor equipment in a structured XML.
The adjacent diagram depicts the key components of MTConnect. Let us start with the shop floor equipment shown at the bottom of the diagram – a CNC lathe. Above that, we have an optional adapter component that converts machine-specific data into a MTConnect defined format. The adapter component is optional as most manufacturers are building this capability directly into their machines. On the top is the agent component responsible for converting MTConnect data into XML. Additionally the agent also exposes a RESTful service that can be used to retrieve data. Read More…
At a recent holiday dinner, a conversation with a friend eventually progressed to the topics of self-driving cars and facial-recognition software – and the overall roles and capabilities of artificial intelligence (AI). My friend’s assertion was that “AI is ultimately about pattern matching.” In essence, you equip the AI with a library of “patterns” and their corresponding associated actions. Based on the input it receives from the real world, the AI software program will then make an attempt to match the input to a stored pattern and execute the corresponding associated action.
Of course any program, regardless of whether it is designed to steer a car or detect a face in an image, relies on pattern-matching at the lowest level. That said, as we will see shortly, a deep learning-based approach is a fundamentally different way to solve the problem. And it’s an approach that is poised to reinvent computing. Read More…
AIS recently worked with the General Services Administration (GSA) Technology Transformation Services Division, better known as 18F. The engagement involved working with 18F to digitize the Division of Labor’s Section 14(c) certification application process (part of the Fair Labor Standards Act). This is currently a paper-based process that 18F hoped to modernize as an intuitive, online application…and to do it using agile methodologies.
AIS was tasked with building the first version of the digital form within a 60-day period of performance – much shorter than typical federal contracts. AIS pulled together a multi-disciplinary team comprised of user researchers, designers, and front- and back-end web developers to work closely with 18F and the Division of Labor (DOL) Product Owner. The team built the entire form with complex validation along with a registration and login and an administrative section to process the form applications. They performed multiple usability tests with actual end users, and followed 18F’s principles of working in the open using a public GitHub repository. All User Stories and discussion threads were thoroughly documented in that repository’s issues list.
AIS was able to work together with many divisions inside DOL to make this happen. We addressed security concerns by the Chief Information Security Officer (CISO) and worked with the CIO office to coordinate delivery of the application and a testing and staging environment for deployment. We also set up a Continuous Integration/Continuous Deployment process so that multiple DOL stakeholders could stay abreast of what was happening and exercise the existing application state. We were even able to address legal concerns with testing by external citizens by getting signed consent forms for testing and recording the sessions.
The collaboration was so successful that our client wrote their own blog post on the project, detailing exactly “how government and private industry can work together using agile methodologies to produce great results.” You can read it here.
These types of successful, agile engagements break down the myths that software development for the government needs to take months (or even years). Government can and will move faster, and after every small win like this project, the traditional methods of building software and procuring software development are changing across the industry. This bodes well not just for the citizens who need to interact with these digital services… but also for saving our tax dollars.
What does a UX Process really look like? Honestly, depending on the project, it can look many different ways. I personally prefer to use a combination of in-depth process techniques, rather than just focusing on one specific area. It is critical to understand that UX is made up of several different components, each having its own importance.
There’s Research and Testing, Information Architecture, Content Strategy, Interaction Design, Visual Design and Front End Development. Today I want to focus on the first three areas.
These disciplines can play a significant role in building stable release processes that help ensure project milestones are met.
Continuous Integration (CI) and Continuous Delivery (DC) are rapidly becoming an integral part of software development. These disciplines can play a significant role in building stable release processes that help ensure project milestones are met. And in addition to simply performing compilation tasks, CI systems can be extended to execute unit testing, functional testing, UI testing, and many other tasks. This walkthrough demonstrates the creation of a simple CI/CD deployment pipeline with an integrated unit test.
There are many ways of implementing CI/CD, but for this blog, I will use Jenkins and GiHub to deploy the simple CI/CD pipeline. A Docker container will be used to host the application. The GitHub repository hosts the application including a Dockerfile for creating an application node. Jenkins is configured with GitHub and Docker Plugin. Read More…
It all started with an email from a customer: They wanted an event app for an upcoming regional sales summit. The requirements fit the mold of a typical event app (session schedule and downloadable documents, photo sharing, surveys, sync with Outlook, etc.), but there was one small problem. The app needed to be done in less than a week.
Fortunately, we knew exactly what tools to use and how to put them to work for our client.
Read the rest of the story, and find out exactly how we got the job done, over at the Microsoft PowerApps Blog.
Make no mistake, most organizations and government agencies are—at least in part—software companies. The backbone of the services and products they sell, the internal business processes they use, and the customer feedback mechanisms they rely on are all built on software. Even in the age of software as a service (SaaS) – a modern organization’s portfolio of applications and the specifics of how these apps are used influence its most important decisions.
So while it’s easy to understand that software is a foundational component to modern business, often the decision to invest in building or offering software to users must also be accompanied by a more specific, anticipated return on that investment. That process can go like this:
In an earlier blog I gave an overview of the Microsoft Bot Framework. Today we’ll take a look at the developer experience, building a starter bot, and integrating LUIS.
Let’s Build a Bot!
Let’s build a simple bot to test drive some of the features of the Bot Framework and LUIS.
DevOps is the latest catchphrase that everyone claims to be doing.
Gartner recommends that “leaders wishing to create a significant, lasting impact on IT performance should look to move beyond the Bimodal paradigm in the space of months rather than years.” Leading and executing on this cultural change is very challenging in enterprise IT. The urgency is to ensure your line-of-business teams remain engaged with enterprise IT, rather than deepening the divide between infrastructure operations and application development teams. In today’s rich marketplace for cloud-based solutions including infrastructure, platform, and software as services, application teams and line-of-business customers have options beyond traditional enterprise IT operations for hosting their solutions. Read More…