Recent Blog Posts

Your Environment Dictates Your Mobile Analytics Design

groupwork-mobile-laptop copy.jpgAnyone who has designed or developed a new product knows that understanding the environment in which the product or solution will be used by its end users is extremely important.


The environment is where we can successfully connect audience and purpose not only to leverage the technology’s strengths but also to minimize its weaknesses within a supported infrastructure.

We need to go beyond just identifying the basic parts of our environment and instead taking a holistic view of the entire system in order to deliver an integrated mobile solution that is consistent and predictable at each layer.


Many of the considerations for the environment may largely be influenced by your organization’s build vs. buy decision on mobile analytics solutions. A close review of the key components that make up the mobile analytics environment can prove to be beneficial.


Mobile device is the host

This is where the mobile analytics journey starts for end users. It’s critical to know and understand:

  • Which kind of mobile device (smartphone or tablet) is targeted? This influences both how we design the actual mobile asset user interface, and how we improve the steps of mobile consumption.
  • What the users will do in case of an issue. So they won’t be confused and discouraged right at the onset of their mobile analytics journey, there must be a commitment for end-user support and the required resources for the project to succeed.


Mobile app is where the action takes place

Once the user successfully gets through the setup and configuration steps, the mobile app is where they will spend most of their time. We need to:

  • Gauge our users’ overall mobile readiness. They will need to get used to standard mobile features (smaller screen and different functionality) in addition to unique mobile app components such as navigation, personalization, or custom query execution.
  • Consider if there are also opportunities to supplement with additional mobile assets that may be executed outside the app. These may be in the form of a simple PDF document or as complicated as integration with another mobile apps or systems.
  • Be aware of the strengths and weaknesses of our solution (app or otherwise). Instead of using cookie cutter solutions, we need to take into account the unique elements of our environment.


Mobile network is what makes it live

The mobile network is the equivalent of a “digital bridge” that allows us to connect to our platform and execute our mobile analytics assets. However, people frequently forget that this digital bridge can be made up of multiple networks.


Different conditions will directly impact the availability as well as the performance of our solution:

  • In office environments where we have direct access to our corporate networks through local Wi-Fi, we can enjoy a fast connection.
  • When we are connecting remotely (like using VPN), the bandwidth may be limited.
  • With remote access conditions (limited Wi-Fi at the airport or lack thereof), we may not even have access to the network.


This is, again, why understanding your audience becomes crucial— so you can provide additional options both on the software (such as offline viewing once the mobile asset is downloaded) or on the hardware (such as mobile hotspot through the wireless service carrier).


Bottom line: Your environment dictates your design

Understanding your environment at all levels—not just what happens within the app or device but also how the device is used—is critical to mobile analytics design because it gives us a chance to validate our assumptions and proactively manage both user perceptions and expectations.


If you’re delivering the solution and you’re the face of mobile analytics, your users may not necessarily differentiate between what’s in your control and what isn’t. When you better understand your environment and how your users will operate in that unique environment, you set your mobile analytics project up for success.


Stay tuned for my next blog in the Mobile Analytics Design series.


You may also like the Mobile BI Strategy series on IT Peer Network.

Connect with me on Twitter @KaanTurnali, LinkedIn and here on the IT Peer Network.

A version of this post was originally published on and also appeared on the SAP Analytics Blog.

Read more >

Making Industry Innovators: Using Social Media to Be More Than a Business Leader


A CIO’s official title doesn’t include “Person Keeping the Computers Running.” Yes, you help ensure that happens, but according to’s 2015 State of the CIO, an alarming 13 percent of IT professionals don’t see CIOs as industry leaders, despite the fact that 44 percent of those CIOs report directly to the CEO.


In previous blogs, I’ve discussed how CIOs can use social media to continue learning about the industry and raise awareness of the CIO as an influential business leader. But how can a CIO grow their social media presence to become more than the face of their business’s tech? By taking advantage of social media’s wealth of knowledge to truly innovate for their company and share successes to inspire industry change.


Engage With Fellow Innovators


One way CIOs can improve the face of social IT is by collaborating and engaging with some of the most influential CIOs on social media. This sort of teamwork adds value and vision to the industry and champions adoption of new technologies.


If you’ve been experimenting on social media lately by retweeting IT influencers or reposting articles on LinkedIn, it’s time to up your game and actually engage. Challenge insights, compare notes, and share stories about trying new tech or processes others have adopted. Here are a few ways to improve your engagement with industry leaders:

  • Retweet content and give your reaction or insight.
  • Comment on LinkedIn posts to initiate conversations.
  • Tag influencers in posts discussing new tech.
  • Share success stories of your own tech adoptions.
  • Source help from industry leaders when you have a question.


By increasing your social media engagement, you’ll foster new relationships. Discussing topics important to your company and possible solutions not only raises IT awareness, it also puts your brand at the forefront of the conversation.


Sourcing Innovation From Social Channels


Your everlasting role as a social CIO is to continue learning. If you’re learning from social media, you should also be applying what you learn. A social CIO knows how to rise from reactive facilitator to proactive leader.


A reactive facilitator sources solutions that might already be in motion in their own IT group or social connections. That’s a step in the right direction toward staying current and relevant in the tech conversation. But a proactive leader stays one step ahead of the game by keeping an eye out for needs and seeking (or creating) solutions. As you become more knowledgeable, you’ll notice trends and be actively in tune with where the industry is headed.


I’m constantly impressed by CIO collaboration on social media. It’s becoming less about marketing and more about improving the industry itself with true innovation. There’s too much opacity today among enterprises. When IT decision makers begin to show a little bit of transparency and share solutions, they improve global technology for the better.


Now that you know how to connect and engage with the IT greats, get out there and collaborate with others to improve your own business and solutions. As you gain more notoriety on social media, you’ll have people coming to you with questions and suggestions of their own — which is a great segue to my next blog post on using social media for talent acquisition. Stay tuned …


Leave your comments below or continue the conversation on Twitter and on LinkedIn.

Read more >

Improving Sepsis Diagnosis and Reducing Cost with Big Data


Sepsis is one of the leading causes of hospital readmissions and death in the United States, impacting some 750,000 patients per year at a cost of $16.7 billion annually to the healthcare system. Reducing the impact of sepsis cases even slightly would significantly enhance patient outcomes and reduce unnecessary expenses.


While the understanding and treatment of sepsis is improving, early detection and diagnosis of the condition continues to be an issue. In the above video, see how Cerner developed  a solution to the sepsis challenge – the St. John Sepsis Agent, which uses Intel technology and to date has helped save more than 2,700 lives by identifying sepsis in the early stages. According to Cerner, organizations can achieve $5,882 in medical savings per treated patient, a 21 percent reduction in length of stay, and a 24 percent reduction in in-hospital patient mortality rates by implementing the St. John’s Sepsis Agent.


Also in the case study video, see how Cerner aggregates big data and utilizes analytics to enable population health, and how Intel and Cloudera allow Cerner to provide a technology platform to support massive amounts of storage capacity, scalable parallel processing with near real-time alerts,  as well as high levels of security.


How is your organization using big data to enable population health?

by Steve Leibforth, Intel Americas

Leibforth photo.jpg


Read more >

Web Services-based Development: Challenges and Opportunities

Unlike software components operating within an enterprise, the Web services model establishes a loosely coupled relationship between a service producer and a service consumer. Service consumers have little control over services that they employ within their applications. A service is … Read more >

The post Web Services-based Development: Challenges and Opportunities appeared first on Intel Software and Services.

Read more >

HIMSS 16 Focus: Impact of Technology on Patients

It’s seems like just yesterday that we were leaving Chicago and basking in the innovation on display at HIMSS 15. Actually, since the last show was in April and now the biggest event in healthcare technology is back in its usual calendar slot, we’re ready for the second HIMSS in less than 12 months.


This year, the healthcare technology community is headed to Las Vegas February 29 to March 3, 2016, to see what innovation will be on the healthcare horizon in 2016 and beyond.  You should expect to see more conversations around how the patient, and their user generated data, plays into healthcare going forward. HIMMS_1.jpg


At Intel, we’re approaching HIMSS 16 with a critical eye on three areas that we feel are focal points for CMIOs: precision medicine, health IT and medical devices, and consumer health. All are patient-focused.


To learn more about these pillars, you’re invited to the Intel booth (#3032) to view the latest technology platforms that focus on the rise of patient engagement and consumer generated health data. We encourage you to stop by and take a guided tour, where you’ll see these demonstrations:


  • Precision Medicine: From genome sequencing to targeted treatment plan all in one day
  • Health IT and Medical Devices: Securely connecting patients, clinicians and their data for proactive healthcare wherever you are
  • Consumer Health: Engaging connections among people, their data and care community to empower health ownership


Outside of the Intel booth, you will find our technology in a number of HIMSS Kiosks that showcase real solutions available today:


  • Population Health Zone Kiosk #14099: IOT Big Cloud Analytics will share how analytics are helping to proactively improve healthcare
  • Connected Health Zone Kiosk #15208: Fujitsu will showcase a communication tool integrated EMR used at the National Cancer Center, personal health record for pregnant women and personal health records for dental solutions
  • Intel Security Kiosk and Cyber Security Challenge #9908: Come take the Security Breach Challenge and learn how to combat cybercrime through efficient breach detection and response


Finally, be sure to follow @IntelHealth on Twitter to keep up-to-date on all the happenings going on at the event. We’ll be live tweeting from the show floor and sharing pictures of new health IT products/services that we discover. We’ll also be giving away a Basis Peak watch every day during HIMSS through a Twitter contest so be on the lookout for how you can win.


HIMSS is always a great event and we are looking forward to seeing you in Las Vegas.


What are you most looking forward to seeing at HIMSS16? Tweet us @IntelHealth.

Read more >

Meet the Outward Sympathizer – An Often-Overlooked Type of Insider Threat Agent

BLOG-OutwardSympathizer.pngBased on reports in recent news, some forms of insider threat get a lot of attention. Just about everyone has heard of examples of damage caused by a disgruntled employee, workplace violence, or theft of intellectual property. But insider threat is actually much larger than those common examples.  At Intel, we’ve been studying this situation and have documented our findings in a white paper we call the Insider Threat Field Guide. In this field guide, we discuss 13 distinct insider threat agent types and the insider events they are most likely to cause, providing a comprehensive approach to identifying the most likely insider threat vectors.  We are sharing this guide so other companies can improve their security stance too. 


For example, one threat agent type we identified is the “outward sympathizer.” Our identification of this character is unique in the industry—we were unable to find any published analysis of this type of insider threat. We define an outward sympathizer as a person who knowingly misuses the enterprise’s systems to attack others in support of a cause external to the enterprise.


As we developed the field guide, we characterized the outward sympathizer threat as follows:

  • An insider of any status that acts in a manner harmful to the enterprise when reacting to external triggering events.
  • Harm may occur incidentally (nonhostile) or intentionally (hostile) and may take any form, including violence.
  • Actions are most likely reactive and emotional, episodic rather than ongoing.
  • Triggering events can be of any scale, from personal to worldwide, and related to any cause.
  • Collusion is more likely to occur if the triggering event has wide applicability within the worker population, such as a regional conflict.
  • The probability of attack is directly proportional to the impact and intensity of the triggering event, and inversely proportional to the general morale and the security awareness of the employee population.


The outward sympathizer is a complex threat agent and triggering events can vary widely. Perhaps there is conflict in a country in which family resides, or an environmental issue that the insider feels strongly about. It can be difficult to predict what will trigger an outward sympathizer attack because the reason for the attack may be entirely unique to the sympathizer and not obvious to others.


Outward sympathizer activity can occur at three escalating levels. Even the most benign level could potentially have devastating consequences for the enterprise.

  • Level 1 – Insider misuses company resources (nonhostile). In this scenario, the insider inappropriately uses company resources to independently support a cause, but the company itself is not attacked. For example, the insider is upset about something so he or she downloads hacker tools onto company servers and uses them to attack someone else. There is no intent to harm the enterprise; in fact the insider probably hopes the company never finds out about it and may assume that his or her identity is protected by firewalls from outside detection. In any case, the attacked entity may believe the enterprise itself is attacking them, and may retaliate in many ways.
  • Level 2 – Insider inappropriately discloses company information to directly support an external cause. The information may be posted publicly to embarrass the company, or may be directed to an activist organization to support their intelligence gathering. The actor may be a planted agent.
  • Level 3 – Insider directly attacks the company from the inside or enables an attack from the outside. The attack can take any form, including data theft, destruction of hardware or facilities, or internal violence or sabotage. The actor is most likely a disgruntled insider but may be a planted agent. Note that at this level, the line blurs between outward sympathizer and disgruntled insider. The important difference is that outward sympathizers are not triggered to action by something that happened to them personally but instead are upset about something external to the enterprise.


Enterprises should include outward sympathizers in their own insider threat models and plan for mitigation. Because this type of threat agent presents differently than most other characters, particularly at the benign level, it can be hard to detect—in fact, some of their methods may not be traceable back to the individual. The unique aspects of the outward sympathizer are motivation and timing, so the most effective mitigations will target those.

15-0701 Snackable Graphics_new-01.png

Research by CERT and others suggests that strong tone-from-the-top security messaging is an effective behavioral deterrent, especially for non-professional threat actors. In addition, we use the following techniques to help minimize the likelihood of outward sympathizer events:

    • Providing specific examples during annual security training
    • Training managers to detect and appropriately handle warning signs
    • In conflict regions, ensuring managers and HR communicate quickly and regularly about personal safety and any available corporate support

    The technical methods used by outward sympathizers are not unique (as a class) and follow classic attack patterns. Technical controls are environmental, not specific. In particular, although it is common to monitor networks for incoming attacks, it is less common to monitor for outgoing attacks. Other effective technical controls include the following:

    • Limiting access to least-privilege
    • Checking the internal environment for hacking tools such as Low Orbit Ion Cannon (LOIC)
    • Watching for misuse such as outgoing distributed denial-of-service (DDOS) attacks


    Intel IT’s Insider Threat Field Guideincluding our understanding of the outward sympathizer threat agent—is an innovative way of looking at the full scope of insider threats. I believe other security professionals can use the field guide to identify and prioritize insider threats, communicate the risk of these threats, and optimize the use of information security resources to develop an effective defense strategy. I encourage you to share your feedback on the field guide by leaving a comment below. In addition, if you are looking for more information about our other security solutions, check out the 2015-2016 Intel IT Annual Performance Report.  We hope you will join the conversation!

    Read more >


    A growth hacking is a process of building a strategic synergy to get the job done which won’t be possible or that effective otherwise. Startups come up with great ideas in the market. The entrepreneurial world keeps an eye on the budding entrepreneurs and scalable startup ideas. The mobile app-based startups might be an eye-catching proposition for investors as well as enterprises.

    The world is changing rapidly. People are getting more and more tech-savvy. Smartphones are a kind of NEED. People take help from mobile apps. The Cortana, Siri, and the Google Now have become the popular personal assistants in today’s world.

    Why not dig a little deeper in order to understand what it takes to build a professionally sound and socially viral mobile app?

    Before hitting that chord of making a successful mobile app-based startup, it won’t be bad to understand the stages of building a mobile app. After all, once you want to build next Snapchat, Instagram, or Periscope, you must have a clear idea of what it takes to build a mobile app.

    Take a look at the different stages of mobile app development:

    1. Research and Development

    R&D is, of course, the start of the app building process. When you’re looking to start an app-based startup, your priority would be finding the potential idea before beginning the process. R&D process will help you explore the market. Let’s not barge into the new discussion what could be the ideal R&D process layout, because every business has its own style of moving on. Moreover, it depends on the demographics of the audience that app is intended for. The important part is that before doing anything on the mobile app idea, the point should come first is the ‘Research and Development’, because it would enable you to identify the market need, target audience, and the competitors.

    1. Prototype designing

    The prototype designing is a process of creating the mockups of any procedure to help guide the team, customer, or the audience. In mobile app development, the prototype designing does help when different stages of an app are described on the layout. The prototype designing comes at the point where you have a clear idea to pull off. You won’t be able to design the prototype unless you haven’t done your homework for creating the next big thing on mobile.

    1. Features Alignment

    The feature alignment could be the next vital stage in your app development process. At this point, you may have developed a few parts of your app’s software, meaning this stage could give you a glimpse of how your app would look like after completion. During this stage, the source code isn’t at the final point which gives you an opportunity to alter the concept of your mobile app and fill in new ideas (if necessary).

    1. Product development

    Once the features get aligned and the mobile app moves towards the development, meaning that it would be in the shape now. During this stage, you will be able to see or use the product (app) partially. Let’s say it the beta version of your app. The important part of this stage is that you can see the app and you still have a few chances to make major changes. Although, it’s not ideal to say that, but it would be better off to do right here before coming backward after the launch.

    1. Testing and Analysis

    Once there is nothing to change in the concept and idea of the app. It’s almost finished with the major development. What comes next could be minor touchups which are totally normal during any kind of code-based product. Testing and Analysis would definitely remove the small hiccups in the mobile app.

    1. Refining the Core

    The core refining is sort of giving the final proofing before the app hits the marketplace. Normally, it is used by the team members first or sometimes a company releases the invite-based beta testers to help analyze the product before making it public. This could be essential, because the feedback funnel is quite clear when you have a select number of people trying and analyzing the product.

    1. Releasing the App

    At last, once things are good to go. Your mobile app hits the marketplace. Once a company follows the simple procedure of developing a mobile app, things would be a whole lot better at the end. In this way, the release of an app would ensure that app is quite bugs free and users are likely to experience the flawless interface. Obviously, bugs and feature failures are parts of the process. Once the users increase, the user-experience and interface testing increase, which could highlight some weaknesses and bugs, and they are likely to be pointed out to bring more perfection.

    Are you going to launch your App-based startup?

    Startups is a huge trend. The tech giants keep an eye on the budding startups. Once you find something relevant and interesting, they reach out to those startups to acquire those startups. Crunchbase keeps the entrepreneurs, investors, and the startups updated with the latest news on startups acquisition.

    The question of the day is, when will you build your mobile-based startup?

    The year 2016 is certainly the year of mobile apps and technology, which is why CitrusBits is gearing up to provide the best mobile app solutions. Contact us for advice on your mobile app development.

    Read more >