Jump to content

Aldon Inc.

Add links
From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by 2600:8800:2082:cc00:d488:9951:2b51:2fb1 (talk) at 16:54, 23 December 2020 (→1979-1989: Beginnings: Modified name to reflect the actual formal name of the company. The Emeryville office was closed in 2019.). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Rocket Aldon
Company typeSubsidiary
IndustryComputer software
Founded1979
HeadquartersWaltham, Massachusetts
ParentRocket Software
Websitewww.aldon.com

Aldon is a business unit of Rocket Software. It develops, manufactures, licenses and supports software change management products for the enterprise application lifecycle management (ALM) and software change management (SCM) markets.[1][2]

Headquartered in Waltham, Massachusetts, U.S., Rocket Software also has offices globally. The current suite of Aldon products includes Aldon Lifecycle Manager, Aldon Deployment Manager, Aldon Community Manager, and Aldon CMDB. Aldon invests more than 25% of its revenue into research and development.[3] Companies use Aldon's products for enterprise software application configuration and change management for their IT business processes.[1]

History

1979-1989: Beginnings

Aldon Computer Group was founded in 1979 by Albert Magid and Don Parr to provide tools for midrange software developers.[1] The company's products were designed to provide infrastructure around complex software projects.

Aldon's first product, Compare, a file and database compare tool for the IBM mainframe computer, was introduced in 1982.[4] In 1983, S/Compare, the first source change documentation tool on the market, was offered. At that time, Aldon also sold an object file compare tool called O/Compare.[4][5] Originally developed for the HP 3000, S/Compare was part of a suite of comparison tools for that environment. Designed to enable programmers to identify differences in program code, it used advanced algorithms to provide comparisons that were more accurate than other tools could produce. Customers used S/Compare to identify the changes they had made to purchased packages, allowing them to integrate those changes into new releases of the packages they had bought.[5]

S/Compare was eventually developed into a comprehensive source compare and merge tool, known as Aldon Harmonizer. The product compared current releases with new releases and then merged the versions to create a whole new set of source and objects. It also supported parallel development by identifying and merging the work of two or more programmers who had modified the same program simultaneously.[5]

In the late 1980s, Harmonizer was converted to run on IBM's System/38 minicomputer platform,[6] a precursor to the AS/400 (later known as iSeries, Application System/400, System i and now IBM i). Aldon's decision to convert its product to run on IBM's platform marked Aldon's entry into IBM i development.

Aldon made its home in downtown Oakland, California, for its initial twenty-four years of business, with the first office located in the Financial Center Building on 14th and Franklin Streets. Aldon relocated to Emeryville on February 18, 2003.[4]

1989-1999: An Embrace of IBM's iSeries and Entry into Multi-Platform Development

In 1990, Aldon released Aldon/CMS, a software change management (SCM) system for traditional iSeries development. [4] Aldon/CMS was renamed Aldon Lifecycle Manager (iSeries edition).

In 1996, Daniel Magid took the helm as CEO of Aldon. [7]Magid came to Aldon from IBM, where he had worked in both marketing and sales, selling midrange computer systems for the General Systems Division.[7]

In 1997, Aldon began the development of the multi-platform product, Aldon Affiniti, which would allow coders to use process management to handle complex development environments across multiple platforms, including UNIX, Windows, Linux, Mainframe and iSeries.[7]

Aldon Affiniti, later known as Aldon Lifecycle Manager (Enterprise Edition), or LM(e), was released in 1998.[7]

2000–present: Regulatory Compliance, SOA and the Move to Distributed Platforms

Regulatory compliance became a much larger concern for businesses after 2004. In 2004-2005, with the collapse of Enron, Global Crossing, Tyco, WorldCom and other financial companies, governments began to mandate standards such as those in the Sarbanes-Oxley Act. While not required for everyone, it became evident to companies that complying with the regulations was good business practice.[8] Companies began seeking automation to assist with SOX compliance.[9] Other industries had their own new sets of compliance requirements: HIPAA (healthcare), Gramm-Leach-Bliley (financial institutions), 21CFR Part 11 (Food and Drug Administration), Basel II (banking laws and regulations), environmental protection laws and standards and more.[8]

In addition, tax code changes, RFID mandates, ISO 9001 and ISO 14000, SEI/CMM, change control management, UCCnet compliance and even tracking and reporting on contractual compliance and service-level agreements, were added to the list. Companies were under enormous pressure to comply with these various and complex mandates. [8]

The crisis was beneficial to software change management companies who for years had championed the benefits of structured, repeatable processes, visibility and audit trails for IT. SCM offered significant benefits to companies implementing best practices to meet compliance requirements.[8] The software could help companies provide what the government was asking of these them.

In May 2004, Aldon announced new brand names for its product suite, as well as the newly shortened company name.[10] The changes were designed to support Aldon's objective to penetrate the growing comprehensive, enterprise-wide, multi-platform application change management solutions.[5]

In February 2005, Aldon delivered to market the multiplatform version of Aldon Lifecycle Manager 5.0, which enabled organizations to run their source code repository on any AIX or Linux server, instead of requiring an iSeries server.[citation needed] Using Aldon Lifecycle Manager 5.0, developers could configure their views to individual work requirements, whether they were working with IBM, WebSphere Development Studio, Eclipse or Microsoft tools that are compliant with its Source Code Control Integration (SCCI) APIs. [11][12] The entry signified additional functionality of the product and moved Aldon from its traditional customer base into a distributed systems customer base. At fiscal year end 2005, the company announced 28 percent growth, which they attributed to the success of the new product functionality.[13]

In 2005-2006, IDC noted, “Aldon pushed out well beyond its earlier (and ongoing) focus for SCM in the iSeries environment with a multiplatform, process-centric solution...With the launch of Aldon Lifecycle Manager 5.0, which added server-side support for Linux, AIX and Windows, Aldon made a concerted, effective push beyond its base market.”[14]

In January 2007, Aldon joined Microsoft Corporation’s Midrange Alliance Program.[citation needed] The MAP was created in 2005 to help iSeries users modernize their legacy environments in the following ways: extending OS/400 applications to Windows, integrating OS/400 and Windows applications and ultimately migrating workloads to Windows from OS/400. [15] Aldon was noted as the first provider of change management software to join the group.[15]

In May 2007, Aldon added features to its ALM offering to further aid parallel development. A graphical interactive compare and merge utility was designed to enable developers working in distributed environments to see what was different between programs. Conflict resolution allowed developers to sort and identify version conflicts using status tags, such as active, pending, or cleared, improving parallel development. [16] Aldon began to see their larger parent corporations implement the product company-wide as their change management standard.[17] Nintendo of America, for example, selected Aldon Lifecycle Manager to manage the development of corporate applications across its multi-platform enterprise.[17]

On May 7, 2007, Aldon announced the acquisition of the business by Marlin Equity Partners, a Los Angeles, California-based private investment firm.[18]

On March 22, 2011 Marlin Equity Partners sold Aldon to Rocket Software, Inc.

Products

Aldon's products include:

  • Aldon Lifecycle Manager (Enterprise Edition and IBM i Edition): provides enterprise application configuration and change management. It manages all the parts of an application and its release lifecycles so that all changes move through the appropriate processes before they are promoted to production. [1]
  • Aldon Community Manager is an IT Service Desk that manages change requests, requirements and incidents and automates the workflow associated with the software development process. The product enables collaboration in the continuing development and deployment of applications. It also ties IT more closely to business goals by bringing in the right decision makers to prioritize change requests as they arise.[19]
  • Aldon Deployment Manager: Working in conjunction with Aldon Lifecycle Manager, Aldon Deployment Manager automates the deployment of all the application parts to the appropriate servers, machines or deployment targets throughout the lifecycle.[19]
  • Aldon CMDB is a centralized repository of configuration items (CIs), for IT Service Management. Aldon CMDB works in tandem with Aldon Community Manager to manage change, asset, and portfolio items.

See also

References

  1. ^ a b c d Andy Kellett. The Aldon Suite: Technology Audit. Butler Group. April, 2007. Reference Code: TA001225ADT.
  2. ^ Kim Wilsher. Aldon Press Kit: Corporate Backgrounder. Red Lorry Yellow Lorry. London, UK. August, 2007.
  3. ^ Sarah Johansen. Aldon Update for IDC. January, 2006. As presented to IDC.
  4. ^ a b c d Christy White. Key Events in Aldon’s History. Interview with Daniel Magid. August 16, 2007.
  5. ^ a b c d Wayne Madden. Celebrating 20 Years Together! Systemi Network. July 1, 2002. (http://www.systeminetwork.com/search/f3/index.cfm?fuseaction=search.searchByKeyword).
  6. ^ Sarah Johansen. Aldon Corporate Fact Sheet. May, 2006.
  7. ^ a b c d Christy White. Key Events in Aldon’s History. August 16, 2007.
  8. ^ a b c d Mary Lou Roberts. iSeries ISVs Make Big Investments in Regulatory Compliance. July 11, 2005. (http://www.itjungle.com/tfh/tfh071105-story03.html.) The Four Hundred: iSeries and AS/400 Insight. Volume 17, Number 27.
  9. ^ Alex Woodie. 2005: A SOX Auditor's Odyssey. http://www.itjungle.com/fhs/fhs012505-story01.html. Volume 5, Number 4-January 25, 2005.
  10. ^ Aldon Redefines Solution Suite for Enterprise Change Management with New Brand Identity. Aldon Computer Group Also Changes Company Name to Aldon. Press release. May 7, 2004.
  11. ^ Alex Woodie. Aldon Opens Up to AIX and Linux with Lifecycle Manager 5.0. (http://www.itjungle.com/tug/tug022405-story03.html.) Volume 2, Number 8-February 24, 2005.
  12. ^ Aldon Announces Aldon Lifecycle Manager 5.0. Intelligent Enterprise. (http://www.intelligententerprise.com/info_centers/ent_dev/showArticle.jhtml?articleID=161601133.) April 26, 2005.
  13. ^ Business Wire. Aldon Year End Marks Success of Multi-Platform Change Management Market; Company Sees Strong Enterprise Growth, Fortune 100 Adoption, SOX Impact, IT Business Process Demand. (http://goliath.ecnext.com/coms2/summary_0199-4226745_ITM) May 16, 2005.
  14. ^ Melinda-Carol Ballou. Worldwide Software Change and Configuration Management 2005 Vendor Shares. December, 2006. IDC #204821.
  15. ^ a b Alex Woodie. Aldon Joins Microsoft's Midrange Alliance Program. (http://www.itjungle.com/fhs/fhs012307-story07.html). January 23, 2007. Four Hundred Stuff: Hardware, Software, and Services. Volume 7, Number 3.
  16. ^ Alex Woodie. Aldon Tackles Parallel Development Problems with LMi 7.5. (http://www.itjungle.com/fhs/fhs041007-story01.html.) April 10, 2007.
  17. ^ a b David Sims. CRM and Relationship Management Software News - OmniTI, Mimosa, Aldon, WebTrends. (http://www.tmcnet.com/news/2006/03/14/1456258.htm, TMCnet.: on the web. March 14, 2006.
  18. ^ Timothy Prickett Morgan. Aldon Acquired by Marlin Equity Partners. http://www.itjungle.com/breaking/bn050907-story02.html. IT Jungle. May 9, 2007.
  19. ^ a b David Rubinstein. No More Change for Change’s Sake: Aldon tool empowers businesses to prioritize incident requests. (http://www.sdtimes.com/article/story-20051215-12.html). SD Times, December 15, 2005. Retrieved on August 16, 2007.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Aldon_Inc.&oldid=995928368"