Enterprise System Spectator blog: ERP and enterprise system vendor evaluation, selection, and implementation.

The Enterprise System Spectator

Monday, May 09, 2005

Blogging from the Lawson user conference

I'm in San Diego today, attending the Lawson "CUE" user conference as a member of the press. I'll be updating this post through the day with observations. There is an announcement about to be made concerning a major change in the technology platform for Lawson, code-named "Landmark," and we're supposed to learn more in the keynote session that starts in a few minutes. In the meantime, read the press release on Lawson's website.

Lawson's Landmark business application platform
Dean Hager presented an overview of Landmark, and Richard Patton, Lawson's Chief Architect, provided more details in a press conference. Afterwards, for more answers, I interviewed Patton along with founder Richard Lawson and Pramod Mathur on the Landmark team. The rest of this section is going to be a bit more technical than I normally write, so be forewarned.

Landmark is Lawson's new technology platform that will, over time, replace the current Lawson "environment" that allows Lawson applications to run across multiple databases and operating systems. Landmark allows Lawson's business domain experts to specify applications in a high level domain-specific language (DSL) which then generates JAVA program code. Lawson's approach is based on "pattern language technology," including the work of architect Christopher Alexander in The Timeless Way of Building. Patterns have been a hot topic for a long time in the software engineering community, especially among practitioners of object oriented design and development, but I have not seen it discussed at all in the realm of enterprise application software.

When I read the press release, at first I was concerned that Lawson was heading down the path of developing a proprietary CASE tool or 4GL, a strategy that has failed most other vendors. But Lawson is not taking such an approach. Landmark is essentially a plug in for the open source Eclipse application development framework. The program code that it generates runs on any J2EE-compliant application server, such as the open source Tomcat or JBOSS, or proprietary servers such as IBM's, BEA's, or Oracle's. Software objects created by Landmark will be enabled for web services, allowing them to interoperate in a service oriented architecture.

Lawson believes that its approach allows it to focus on its domain expertise and what it calls its "signature features," such as "drill around," audit trails, and effective dating. Software quality should increase greatly as Landmark's code generation approach allows orders-of-magnitude reduction in the number of lines of program code. Patton quotes a 17x reduction in lines of code for Lawson's Vendor module, and a 41x reduction in Lawson's Employee module.

In terms of customer rollout, Lawson is emphasizing a co-existence approach: new Lawson modules will be written from this point forward under Landmark and will coexist and interoperate with existing Lawson modules. Existing modules will be "re-factored" in Landmark. Installed base clients can move incrementally to Landmark written versions.

Lawson's leadership is genuinely excited about the introduction of Landmark. Richard Lawson himself largely disappeared from public view for the last three years as he led a team of technology architects in crafting this vision and developing the basic framework of Landmark. What appeals to me most about Lawson's approach is that it may be leading edge, but it's not something created by Lawson in a vacuum. Domain specific languages (DSL) are commonly used by software developers in other domains. When I pressed for examples, Lawson pointed specifically to discussions they have had with Bell Labs and with another software developer that it was not free to name.

At this point, to Lawson's customers, Landmark just is a vision--although after three years in the lab, Landmark is much more than a statement of direction. The first Landmark application should be introduced within the next year and at that point we should have a good indication whether Lawson is able to deliver.

Offshore delivery of professional services
Lawson announced today that it has put together a "blended professional services" offering in partnership with Indian offshore services provider Xansa. Lawson was already using Xansa internally to provide some maintenance programming for existing Lawson products, leveraging the lower cost of labor offshore. Now Lawson will offer Xansa offshore resources to Lawson clients, to be managed by Lawson personnel onshore, to deliver customer projects such as integration and interface programming, data conversion, and development of custom forms and reports.

Lawson customers will appreciate the lower cost of delivery, as long as Lawson continues to step up to the role of being the "one throat to choke."

Update, May 11. Lawson and IBM have now announced that Landmark will be based on IBM's Websphere technology. I guessed this on Monday when I interviewed Lawson executives about Landmark, but they wouldn't confirm it at the time. I don't know why they had to hold back this piece of the puzzle for two days after the Landmark announcement, except that I suppose it gives them one more thing to announce during their user conference. Basing Landmark largely on IBM technology is a good thing. Application software vendors are notoriously poor at building proprietary development toolsets, and the more Lawson can incorporate publicly available components in its development platform, the better. IBM, which doesn't compete with ISVs, is a great choice.

Lawson says that during the first half of 2006, it will releases upgrades to its financials, SCM, HR, performance management, and procurement modules, with embedded core components of IBM's WebSphere, DB2, Rational, and Tivoli technology.

For more, check out Lawson's press release.

by Frank Scavo, 5/09/2005 08:35:00 AM | permalink | e-mail this!

 Reader Comments:

This comment has been removed by a blog administrator.
Post a Comment

Links to this post:


Powered by Blogger

(c) 2002-2016, Frank Scavo.

Independent analysis of issues and trends in enterprise applications software and the strengths, weaknesses, advantages, and disadvantages of the vendors that provide them.

About the Enterprise System Spectator.

Frank Scavo Send tips, rumors, gossip, and feedback to Frank Scavo, at .

I'm interested in hearing about best practices, lessons learned, horror stories, and case studies of success or failure.

Selecting a new enterprise system can be a difficult decision. My consulting firm, Strativa, offers assistance that is independent and unbiased. For information on how we can help your organization make and carry out these decisions, write to me.

My IT research firm, Computer Economics provides metrics for IT management, such as IT spending and staffing benchmarks, ROI/TCO studies, outsourcing statistics, and more.

Go to latest postings

Search the Spectator!
Join over 1,700 subscribers on the Spectator email list!
Max. 1-2 times/month.
Easy one-click to unsubscribe anytime.

Follow me on Twitter
My RSS feed RSS News Feed

Computer Economics
ERP Support Staffing Ratios
Outsourcing Statistics
IT Spending and Staffing Benchmarks
IT Staffing Ratios
IT Management Best Practices
Worldwide Technology Trends
IT Salary Report

Get these headlines on your site, free!


2014 Best Independent ERP Blog - Winner

2013 Best ERP Writer - Winner

Alltop. We're kind of a big deal.
Constant Contact 2010 All Star Technobabble Top 100 Analyst Blogs

Key References
Strativa: Business strategy consulting, strategic planning
Strativa: IT strategy consulting
Strativa: Business process improvement, process mapping, consultants
Strativa: IT due diligence
Strativa: ERP software selection consulting and vendor evaluation
Strativa: CRM software selection consulting and vendor evaluation
Strativa: Project management consulting, change management
StreetWolf: Digital creative studio specializing in web, mobile and social applications
Enterprise IT News: diginomica

Spectator Archives
May 2002
June 2002
July 2002
August 2002
September 2002
October 2002
November 2002
December 2002
January 2003
February 2003
March 2003
April 2003
May 2003
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
July 2008
August 2008
September 2008
October 2008
November 2008
December 2008
January 2009
February 2009
March 2009
April 2009
May 2009
June 2009
July 2009
August 2009
September 2009
October 2009
November 2009
December 2009
January 2010
February 2010
March 2010
April 2010
June 2010
July 2010
August 2010
September 2010
October 2010
November 2010
December 2010
January 2011
February 2011
March 2011
April 2011
May 2011
July 2011
August 2011
September 2011
October 2011
November 2011
December 2011
January 2012
February 2012
March 2012
April 2012
May 2012
June 2012
July 2012
September 2012
October 2012
December 2012
January 2013
February 2013
March 2013
May 2013
June 2013
July 2013
September 2013
October 2013
December 2013
January 2014
February 2014
March 2014
April 2014
May 2014
June 2014
July 2014
August 2014
September 2014
October 2014
November 2014
December 2014
February 2015
March 2015
April 2015
May 2015
June 2015
July 2015
September 2015
October 2015
November 2015
February 2016
May 2016
June 2016
July 2016
August 2016
September 2016
October 2016
Latest postings