Tag Archive for SP2010

CorasWorks Idea Management v1.1 for SP2010 Unveils at Tech Ed

Tech Ed is cooking down in New Orleans.  We turned up the heat even further by unveiling Cim v1.1 for SP2010.  If you are there, get over to booth 345 and check it out.  For the rest of us, I’ll walk you through a few screenshots to highlight some changes in Cim v1.1.

First, it sports a new upgraded, customizable UI as shown below.  Over the last month we’ve tweaked the Idea Community Portal UI to play very nicely with SP2010.

Cimv1.1-sp2010-home

 

We have also upgraded the Idea Community modules in a number of ways.  At the core, we improved the architecture to make it easier to support integration with downstream processes (review, approval, management and implementation phases). In the UI we support a number of features highlighted below: Status bar showing updates from downstream processes, new Star Power algorithm used in our Top 10 Rankings, and group document uploads allowing any community members to add documents to an idea in addition to comments.

Cimv1.1-sp2010-community

 

Our Top 10 Listings shown below now support a Portfolio approach.  Just add a new Community, Campaign, Challenge or Contest to the system and it is ready to go in the Top 10 Listings – giving you Most Recent and Highest rated.  You can also customize the listings such as adding fields or style, and, you can create your own unique ones.

Cimv1.1-sp2010-Top10

 

The Administrative UI’s of the various modules of Cim have been updated to take advantage of the new SP2010 UI such as the Ribbon Bar shown below.  Thus, they are consistent with the user experience of all SharePoint 2010 users – and easy to use.

Cimv1.1-sp2010-Admin

 

The new user dialogs in the Review and Management sites use pop-up modal forms as shown below to make it easier for users to modify.  In addition, it is point and click to modify the forms to not show fields, such as system fields, that aren’t relevant to a particular task.

 

Cimv1.1-sp2010-modal

 

In addition, in our Idea Portfolio Management site we now provide for customizable actions to drive downstream processes.  For instance, imagine a New Product is approved for development.  As shown below, this approved innovation is being “pushed” into a Program Management Office to kick off the development project.  Other actions can be added for different workstreams such as pushing approved process changes into team sites for different teams to implement the process changes.

downstream

 

These are some of the changes for the new Cim v1.1 on SP2010.  However, they are just screenshots.  It is far better to get a demo and experience an actual business scenario that means something to your business – where ideas are captured and turned into results using Cim.

Until then,

william

CorasWorks Business Solutions on SharePoint

With the RTM of SharePoint 2010 on May 12th, we released our first two Business Solutions –Idea Management and IT Project Management.  We’ve had a lot of activity since then and questions.  In this article, I’ll give you a primer on our Solution product line and answer some of the questions.

Same Value Prop: CorasWorks Solutions offer the same value prop as our Applications – reduce the risk, cost and time to deliver business value on SharePoint.  The Solutions are targeted at a specific purpose such as Idea Management, and, generally a specific business group buyer.

Broader Problems, Flexible Implementations: Unlike our Applications they are not available in the App Store and aren’t plug and play – meaning you don’t just download, install and use them.  They are a bit bigger animal.  Solutions address broader problems.  To be effective, they are based upon a modular framework.  For instance, the IT Project Management solution has 10 modules.  They are productized and designed to snap together.  However, you customize the modules as part of a full solution to meet the specific needs of the business group.  Thus, each implementation is a different flavor and requires some services.  We have created standardized Jump Start service offerings for each solution to get you going quickly.

Enterprise 2.0: These Solutions represent a new Enterprise 2.0 approach from CorasWorks.  They have a very web 2.0 look and feel.  The standard UI is not heavy components but light UI’s that are customizable with CSS and XSLT.  The modules tend to focus on enterprise 2.0 style social collaboration.  We’ve done a lot of work figuring out how to properly balance structured apps with social collaboration to create a balanced approach to Enterprise 2.0.  This is a key part of our approach on SP2010 as we roll forward.  I hope we got it right – you tell me.

Portal-Centric: Each solution is portal-centric.  We are targeting solutions where you start with a Department Portal or Application Portal.  Look at IT Project Management.  It starts with a rich, web 2.0 Portal with a host of social collaborative features.  It is a place to go.  Then, you have the ability to drop in Snaplets from other CorasWorks and third party applications and sites distributed across your SharePoint environment.  This means that you don’t have to go to as many places to do your work – the information and functionality is brought to you in the solution portal.

Integration with Applications/Sites/Portals:  The Solutions heavily leverage our Snaplet architecture and existing applications.  This means that you can snap off application functionality and distribute it to one or more solution portals.  For instance, the IT Project Management solution incorporates all of the CorasWorks Project Portfolio Management application – it is all pre-integrated.  There are elements, such as Project Gantt charts and Portfolio Risk/Issue heat maps, that you snap off the PPM sites and drop in the Portal.  The key is that with CorasWorks you are able to connect to any information across a SharePoint farm – cross Site Collections and Web Applications.  You can also take a Snaplet from one solution portal, such as an Idea Community for Product Ideas, and drop in into a different solution portal, such as the Product Management portal.  Yet, being a Snaplet, it is centrally configured. So, you make one change centrally and all distributed Snaplets instantly update.

Pricing and Requirements:  Each solution has a standard perpetual license fee for both SharePoint platforms.  They require the full CorasWorks Application Platform (Suite and Toolset).  There are separate editions for SP2007 and SP2010.  And, they support our bridge approach so that you can deploy on SP2007 today and smoothly upgrade to SP2010 when you are ready.

I hope that this gives you a good primer on CorasWorks Solutions.  Keep the questions coming and we’ll be back to you,

william

CorasWorks on SharePoint 2010: First, the Bridge

With our new release today of Workplace Suite (v10.3.1) and the Toolset (v1.6.1), we begin the process of transitioning into the SharePoint 2010 period.  Today’s release provides customers with the platform to bridge their SP2007 application environments to SP2010.  Let’s talk about it.

It works like this.  You install v10.3.1/v1.6.1 on your SP2007 environment and go about your business of building apps and building out your environment on SP2007.  When the time is right, tomorrow or in 2012, you just do an inplace upgrade of your SP2007 environment to SP2010 and your CorasWorks apps just keep on working.

image

The v10.3.1/v1.6.1 release runs on both SP2007 and SP2010.  This means that you do not have to do a rip and replace to move to the next platform.  Just upgrade.

We reckon that the SharePoint community has invested north of $5B in building out environments on SP2007.  With this release and our bridge approach we figure that we’ll be preserving some major investments as you move onto SP2010.  Let’s face it, the move from SP2003 to SP2007 was expensive and time consuming.  With the v10 bridge, you can continue adding business value through apps on SP2007 and then move to SP2010 and start taking advantage of its features and new apps.

Speaking of apps, with the v10.3.1 release today, we also released our first SP2010 app – our Help Desk v1.2 for SP2010.  You can install this app directly onto new SP2010 environments running v10.3.1 and you are good to go.  It uses the new .WSP Solution format vs. the .STP format.  The wave of apps for SP2010 on v10.3.1/v1.6.1 from CorasWorks and our Application Publishers will come surprisingly quickly.  You will first see existing apps that run on SP2007 made available for new SP2010 environments.  Then, you’ll see apps built just for SP2010 as the platform gets adopted.

This is all possible because we’ve had the opportunity to work with Microsoft since January of 2009.  Over the year they have worked hard to make SP2010 backward compatibility possible.  My hat is off to them.  This shows some real care for the investments that their customers have made in the platform on SP2007.  We have worked hard to properly plan our v10 releases which first came out in February of 2009 to be forward compatible and to put standards in place on the SP2007 platform so that the user population will have a consistent experience when they upgrade to SP2010.

A major example of this is our Ajax-based web dialogs.  On v10 on SP2007, our users have been getting used to doing data entry using pop-up web dialogs.  This carries over to SP2010. Another is being able to select multiple items in a display and act on them with a custom action – this user experience also carries forward.

Our plan is to continue building out the v10 platform.  Our next release, v10.4 for SP2007 and SP2010 will come out in Q2.  It will keep getting better for users on SP2007 and on SP2010 and start to embrace, enhance, and extend SP2010 features.  You will shortly see this starting to show up in the apps for SP2010.

Simultaneously, we are working on the next CorasWorks version that will be SP2010 only.  When we release this version, it will run side by side with your v10-based apps and environment, yet, it will take much greater advantage of the SP2010 feature set.  This side-by-side approach worked well for our customers when we transitioned between our v9 and v10 versions during the SP2007 period.

William