In today’s mobile society, the current and future generation of “mobile” devices (i.e. smartphones, tablets, “phablets,” special purpose devices, etc.) and the applications that can be hosted on them provide a significant opportunity to improve the way we work. This is especially true for those workers whose job involves traveling during the day to work directly with customers “in the field.” In this post, I’ll share some recent experiences we’ve had in working with mobile field workers as part of an analysis effort to define requirements for a tablet-based application.

Approach:

The specific approach we used for this project was to “follow” or “shadow” the workers as they performed their activities and collect observations about:

  • The tasks they performed,
  • The devices and applications they used to support those tasks, and
  • The types of information and work products (forms, documents, etc.) they either collected or produced in course of performing the tasks.

We worked with both staff personnel and supervisor personnel, and we looked at both scenarios where customers would come into a field office and scenarios where the field staff would meet customers at a field location directly. We then followed the observation sessions with one-on-one interviews to review the observations and ask more specific questions.

Based on our experiences, we identified what we would consider to be some key recommendations for business analysts, product managers, or others seeking to elicit requirements for mobile worker applications. Read More…

70% of all devices sold in 2012 were tablets or smartphones. Tablet purchases by businesses will grow three times by 2016. These numbers, provided by Gartner, confirm what we already know from walking in the mall or sitting at a cafe…and the news for PC sales doesn’t appear to be improving any time soon.

Navigating this post-PC world can a frightening experience when your corporate lifeblood relies on the dominance of PCs. Compounding this is the fragmentation of the emerging market across native mobile platforms, three primary desktop browsers (exponentially more when including mobile), and varying device form factors and operating system flavors. Read More…

Technology is advancing rapidly, and with its advance comes new and useful ways to complete everyday tasks. In this post I’d like to talk about some of the benefits of replacing the paper- or desktop-based ways of an employee whose job is performed primarily in the field. (Home health workers or field service technicians, for example.)

Quality custom software that’s designed to meet the specific needs of a business is easy to adapt and should have minimal adoption time and training costs. Workflows that are built according to an employee’s ideal task flow should encourage thorough service calls and better communication flow in all directions.

As an employee who may have to make several service trips per day, mobility is essential. Paper can be completely eliminated, pictures no longer lost or need to be transferred by media card, forms can be filled out by simply speaking into a microphone and tapping on some check boxes. Signatures can be captured easily just by swiping a finger on a screen, bar codes can be read and captured. The possibilities for becoming more productive are expanding each day. Read More…

Broken iphone Screen - Broken Web PageI was rushing out of my house on a Thursday afternoon and my phone fell squarely onto the pavement. As I picked it up and gingerly turned it over in my hands, I gasped. The screen was cracked, utterly and completely. It was a moment so steeped in idiocy that I almost laughed at myself. If you drop a phone it breaks, right? Except that it hadn’t and I’d dropped it a million times before. Maybe this was just its time to die its little death or maybe this was a particularly horrible fall. Whatever it was, it happened and it was over.

Later, at the store, my conversation with the girl replacing my phone went a little like this:

Helpful Girl: So if you’re phone is backed up, I’ll delete everything on it and get you started with a new one.

Me: It is.

HG: Ok, is it backed up to the cloud?

Me:

HG: (concern on her face) What did you do to back it up?

Me: My husband plugged it into the computer and made a copy.

HG: Ok, if you’re sure you have a copy…

Me: I am…?

Did I mention that I’m a Business Analyst for an IT company? That I used to recruit for that same company? That I regularly talk with customers about what we can do for them and how we can ease their pain points with technology-based solutions? If you’re rolling you’re eyes at me, that makes two of us. But as I’ve discovered, working in technology isn’t all about the technology, it’s about the people. Read More…

Good question. And we’ve got the answer.

Here at AIS, we’ve spent hundreds of thousands of hours envisioning, designing and constructing SharePoint-based solutions for our clients. With each new version of SharePoint, we make additional investments to deeply understand the new release’s capabilities.

We’ve taken a look at all the changes and enhancements in the latest version — and you just have to look at our blog archives to realize that a LOT has changed in 2013 — and put together a short, easy-to-read whitepaper that highlights the top new features that make SharePoint 2013 a must-have for your business, including:

  • Smarter Search
  • Simpler and Mobile-Ready UI
  • The game-changing SharePoint App Store Model
  • Better Workflow
  • Social SharePoint
  • Easy Migration Tools
  • Lower Costs
  • And much more!

Please CLICK HERE to download your free copy.

Not familiar with SharePoint as a business solution? Take a look at our SharePoint solutions on our website and contact us to learn more about how SharePoint can transform your organization.

Have you ever attended a technical training event, and three days later, couldn’t really remember what you were trained on? In trying to recall what you just sat through, your mind comes up with the mental equivalent of a desolate Wild Wild West ghost town, perhaps with a sad tumbleweed or two passing through. You are not alone! At one point or another, we’ve all fallen victim to a training presentation that simply does not stick.

Training is an opportunity to engender a self-propelling domino effect of learning that can better humanity.

As a training developer, it’s my job to prevent students from walking away empty-minded. Come to think of it, this is also the goal for most sales people. You want your presentation to make a lasting impression: You want something to hit home — to stick —for the other person, in order to produce results. Whether those results are improved on-the-job performance or the President’s Club Award for Outstanding Sales, it doesn’t matter. Recognize that training is so much more than a stand-alone event: It is an opportunity to engender a self-propelling domino effect of learning that can better humanity.  “Well, when you put it that way, serving as a Trainer is an honor and a privilege!” my colleague said to me.  Yes, indeed it is! Read More…

The SharePoint Leap

In my job, I have an opportunity not afforded to most: I get to listen to all of the risks, challenges, and issues (a.k.a. problems) that other organizations face. (I know, you’re jealous, right?)  From issues with large-scale hardware deployments to the risks of implementing new federal bureaucratic form processing, I get to hear it all.  Without fail, nearly all of those discussions start with someone in the room declaring, “We do it different here.”

If I had a dollar for every time I heard, “we do it different here” during a federal project kick-off meeting, well…I would have about twenty or thirty bucks, but that’s not my point. The point is you don’t do it differently!  Human nature is human nature and given similar constraints, regulations, policies and procedures, the outcomes will be similar.  Beyond the obvious irony in nearly all organizations declaring their uniqueness, I am struck by the actual similarities of the problems.

Read More…

With the SharePoint Conference 2012 behind us, I have been reflecting on our SharePoint journey so far…and on the road ahead. And what an incredible journey it has been! SharePoint has allowed AIS to build mission-critical applications for various large federal government agencies and commercial organizations. And not just ECM or document management systems (which are great workloads enabled by SharePoint) but enterprise-class applications for tens of thousands users (such as the FBI’s Delta Project), built using SharePoint platform elements such as workflows, lists, libraries, search, etc.

This blog entry is comprised of two parts. The first part will focus on the SharePoint journey so far. Through a series of short video clips, I will present some of the key insights we have derived over the many years of building custom applications on SharePoint. We will end this the first part with a short demonstration of SharePoint-based Case Management application that brings together many of the key concepts. The second part will focus on the road ahead and the most important enhancements made in SharePoint 2013. Read More…

N-tier development is not a new methodology. I remember learning about it in 200-level courses back in 2000, and I used it in ASP.NET development before I jumped on the SharePoint bandwagon. However, one of the things I’ve noticed over the years as a SharePoint developer is that most project development is done in the SharePoint object’s code behind or a few helper classes. This isn’t always the case —sometimes the solution isn’t complex enough to warrant a tiered approach (i.e. a single Event Receiver). But a recent project highlighted the power behind N-tiered architecture.

The client has a custom solution that they provide as a service: A master document (Microsoft Word) is split into section documents (also Word) by a project manager. Each section is assigned to a person to be modified in Word (the client also provides a Word plug-in for this modification). Once the sections are properly marked up, the master document is recreated from the sections. We were brought in to implement this solution in SharePoint 2010. Read More…

In order to meet ever-increasing customer demands and compete on a global scale, many organizations need to be able to fold new systems and/or new features into existing systems quickly and cheaply. These organizations — and perhaps yours — have portfolios of existing systems and infrastructures that were implemented literally decades ago.

These “legacy” systems, while well-architected for the demands and market conditions of the past, have often become increasingly complex through the years and more costly to maintain. What’s more, these systems are based on technologies that simply don’t provide the flexibility and disciplined agility that modern programming languages and frameworks can. Read More…