|By Al Soucy||
|June 27, 2014 11:00 AM EDT||
I was asked by Mr. Peter Hastings (NH DoIT Commissioner) to document the benefits and activities behind the Standardization and Centralization Initiative (SACI). This initiative concerns the standardization of the software configuration management tool, defect tracking tool and standardizing production compiles across the enterprise of state government. In addition this includes the storage of assets for disaster recovery purposes, securing and controlling state source data assets, intellectual property and mission-critical data assets across the enterprise of state government.
This article will cover how the State of NH is working to save money in efficiencies related to standardizing and centralizing state data assets. Every state wants to save money for its citizens and stakeholders but saving money in state government can be a very challenging task. The fact that every agency in state government is basically its own separate entity makes this even more difficult. Initiatives of this size and scope can be complicated to implement if agencies don't understand the value and don't feel the need to cooperate or collaborate to achieve success and understand that the savings is in their best interest. In today's economy no one wants to spend any money to achieve any savings to begin with because they don't have the money to make any capital investments.
Attempting to standardize any process, tool or initiative across the enterprise of state government is no easy task. The Standardization and Centralization Initiative (SACI) is no exception. This project standardizes the Software Configuration Management (SCM) tool across the entire enterprise of state government, secures, controls and centralizes all state source data assets, intellectual property and mission-critical assets for state government and for disaster recovery purposes, meeting the Federal COOP requirements as set forth by Homeland Security.
To introduce a directive of this magnitude speaks to the courage of Commissioner Peter Hastings for taking on such a challenging initiative across the enterprise of state government. You need a leader who can communicate effectively to the agency heads that there is value in this initiative that will ultimately lead to savings across the enterprise. The State of NH will receive many benefits from this initiative and there have been many hurdles to achieving such a huge undertaking. This initiative reflects the understanding of Commissioner Peter Hastings to address enterprise-wide level inconsistencies that cost the State of NH money and realize a cost savings instead.
This initiative establishes a centralized virtualized repository environment for all state software assets. It standardizes the Software Configuration Management (SCM) tool, Defect Tracking tool and formalizes production compiles across the enterprise. This initiative set in motion by Commissioner Peter Hastings at the State of NH is transforming state government software development activities across the enterprise of state government thereby streamlining processes and saving resources, time and money for the citizens of NH and the stakeholders of state government software development activities. I don't see any initiative like this taking place or being tackled anywhere else in the country on a state level and over the long term this will potentially save the State of NH perhaps millions of dollars.
Business Problem and Solution
Prior to the implementation of the SACI (Standardization and Centralization Initiative), state source data assets were spread across the enterprise of state government anywhere and everywhere. No one really knew where all the assets were truly located. State developers would leave for other opportunities and managers would hire a new developer and not be able to point the developer to the latest greatest application source assets for a specific project. Some developers were storing assets on their local drives, others on shared drives and no one knew where they were placed. Others stored these valuable assets on CDs and DVDs, which could be lost, and local drives, which can crash, and assets would be misplaced and lost. This resulted in a lot of state money being expended to re-create these assets again.
Let's just say a lot of state resources, time and money can be wasted this way: lost code, overwritten code, deleted files, no source code control, restores of assets and many flavors of other types of source code control tools contained within a silo across the enterprise. This can apply really to any organization.
Commissioner Peter Hastings realized quickly once becoming Commissioner that if he standardized and centralized all of the state's assets - whether they be source data assets of application source code, intellectual property related to applications that are supported inside and outside of state government, and secured and controlled state mission-critical assets in a centralized repository - that this would save the state a lot of money.
Commissioner Peter Hastings provided a directive to implement the Standardization and Centralization Initiative (SACI) and save money on activities related to software development and transform state government with more status accounting of software development activities across the enterprise of state government. There is visibility into software development activities that did not exist before this initiative.
The direction was to place all existing physical servers housing software assets and software developers across the enterprise in a virtual environment on one server and on one standard tool across the enterprise to centralize the state source data assets, intellectual property and mission-critical assets.
There is a cost savings to the state with this initiative alone with fewer software configuration management (SCM) servers in technical support and electricity and a myriad of other savings I'll speak to later. This initiative would centralize and standardize the users, licenses, assets and support across the enterprise for software development activities.
Improvement to Government
Intellectual property is a valuable commodity and it needs to be secured and controlled. The Federal government realizes this as well with some of the problems experienced with NSA securing metadata for the gathering program for phone calls, emails, etc. Standardizing tools and centralizing assets to reduce cost and streamline software development activities makes sense on so many levels (reduction in support, fewer physical SCM servers to maintain and support, less electricity, less software to install, fewer operating systems to maintain, fewer servers to back-up, easier to maintain SCM licenses, less of a learning curve for developers from one state agency to another on an SCM tool, more formalized development, more disciplined development, status accounting now available on software development activities, common code library can be shared to reuse code, future upgrades to the clients are easier, standard defect tracking being used which is centralized, etc.). All these savings add up and benefit state government in managing the cost of software development activities.
In addition when all users are in a centralized virtual environment the cloud concept can now be applied from within the standardized Software Configuration Management (SCM) tool to reuse common functionality code across the enterprise. A common code library for common functionalities between agencies across the enterprise can be set up and code that could be shared, reused, understood can all be under the secure umbrella of SCM.
Standardizing the Software Configuration Management tool allows groups to be created that have certain levels of access all the way down to a process or a file. It's easier to allow some teams or many teams to browse this library of shared common code. It also educates other teams on how one team versus another might be developing common functionalities. It can save the state money rather than reinventing the wheel on common functionalities already written by another development team.
This initiative saves the state resources, time and money on development activities:
- All state source data assets are centralized - diminishes the overhead of physical support.
- All processes are standardized by the use of one product to support multiple platforms. When a tool has a generic repository that houses any type of data asset any development platform can be secured and controlled. In large organization there can be legacy platforms that have to be sustained sometimes for years and a generic repository supports that effort.
- Allows movement of a developer from one project to another with more flexibility.
- Common functionality libraries can be set up for all development platforms (Visual Studio, PowerBuilder, Java, etc.) so that all developers can have access to reusable code under a SCM secure umbrella.
- Provides transparency to all managers with a view into a life cycle as to what developers are working on in any SCM State across the enterprise of State government.
Many large organizations have too many varying methods, tools, and processes and this creates silos of development, which overall is counterproductive to the whole. This makes it harder to not only know what the team(s) are doing or developing in or have access to or to interchange that skill set with another development team.
When all developers are using the same tool they can easily be provided access to another project via the secure cloud of the standardized SCM tool and work any project and have a much smaller learning curve by not leaving the development environment but seeing a new project in their view in the SCM tool.
When all users/developers are on one server that contains all the licenses for the tool and the assets are centralized and the SCM tool is standardized, the state can save money in various ways on activities related to software development and transform state government with more status accounting and visibility into software development not only for state developers but contractors as well.
The following is a list of the benefits of this project to State Government: Standardization and Centralization Imitative (SACI):
Benefits of the Project:
- This project will standardize the state's Software Configuration Management (SCM) Tool so that one product is being used by all agencies and this will save the state time, money and resources by having one tool across the enterprise to support.
- Provides the state with a smaller learning curve from software development team to software development team across the enterprise and allows software developers to save time by not learning a different tool from agency to agency. This allows for more focus on software development activities for application development.
- Allows for cloud software development to occur in a secure umbrella of SCM and allows for reuse of source code to save the State time, money and ultimately resources on software development activities. Prevents re-inventing the wheel on common functionalities.
- Allows for software developers to be interchanged between agencies more easily without the need to learn a new SCM tool for software configuration management activities.
- Precludes lost source code (source data assets, intellectual property, mission-critical assets) from agency to agency that saves the State time, money and resources over the long term.
- This will save the state money on electricity as well because all software developers will be on one virtual server versus three or four physical servers. Power consumption is a big deal with servers. It takes a great deal of energy to keep them cool and running.
- This will save the State money in terms of manpower as well with only one virtual server to maintain and back-up and one operating system to maintain and support rather than three or four.
- Saves the state money with all state data assets, intellectual property and mission critical assets centrally located rather than spread out all over the place across the enterprise.
- This methodology allows for better control of disaster recovery to meet Federal COOP requirements across the enterprise when it concerns State source data assets and intellectual property. These requirements are set up by Homeland Security to maintain business continuity.
- This allows state managers more visibility into software development activities and allows for better time management of these resources. It removes the silo effect.
- Standardize Defect Tracking for all state agencies so that one tool is used across the enterprise for all reporting against application development. This centralizes reporting.
- Standardize production compilations so that compilations and debugging issues are minimized across the enterprise for software development activities.
- When contractors use our standardized tool we have greater insight into their software development activities and at least have the assets secured and controlled within state government.
- When contractors use our standardized tool and house the State assets within our infrastructure it allows State software developers to shadow contractors and parallel the contractors work so that when the contract is complete State staff can sustain the application. This saves the State money because state staff can do the work cheaper than contractors.
- Harvest SCM integrates with all the software development platforms that we use here at the State today even legacy applications. So, one tool rather than a myriad of tools can perform the task of SCM and this saves the State time and money with only one tool to support across the enterprise and it takes only two people to support the entire infrastructure across the enterprise.
The final result is one virtual software development server, which would include intellectual property of various types (application code - VS, PB, Java, docs, etc., or Oracle code, SQL code, Access, etc.) and mission-critical assets.
What will have been achieved across the enterprise:
- Centralized State Data Assets across the Enterprise of State Government
- Centralized Data Asset Repositories
- Standardize Software Configuration Management (SCM) Tool
- Standardize Application Compilers - OpenMake
- Standardize Defect Tracking System
- Created Common Code Library for Common Functionalities
- Provide Status Accounting and Auditing of SCM projects
- Provide IT Managers and Commissioners visibility into Software Development Activities across the Enterprise of State Government
It's difficult to measure these savings in terms of real dollars today (ROI) but the savings can be measured by the streamlining of software development activities across the enterprise. The increased efficiency and quality improvements as well as a reduction of errors and or duplicative efforts are the real payback to this initiative.
My background is that I have been working in Software Configuration Management (SCM) for a few years now and I am presently, the administrator of SCM at the State of NH. SCM is a process-based Software Configuration Management (SCM) tool for managing application source code, intellectual property and mission critical assets. In this capacity I also secure these assets for disaster recovery purposes. I manage 400 plus applications housed in SCM and support 400 users using the product. The development tools we currently use are PowerBuilder PBV8, PBV11 and 12; Visual Studio 2003, 2005, 2008, 2010 and 2012; Eclipse, Juno, RAD, Mule, Cold Fusion, Java, COBOL and VB.
As the Software Configuration Manager (SCM), I provide the administration of the source code management tool. This includes the entire infrastructure of the environment for development, developing life cycles, providing best practices, procedures, processes, documentation; defect tracking, disaster recovery, maintaining build machines and the training of all the developers on proper source code management using the development tools in our development environment.
With all the incredible momentum behind the Internet of Things (IoT) industry, it is easy to forget that not a single CEO wakes up and wonders if “my IoT is broken.” What they wonder is if they are making the right decisions to do all they can to increase revenue, decrease costs, and improve customer experience – effectively the same challenges they have always had in growing their business. The exciting thing about the IoT industry is now these decisions can be better, faster, and smarter. Now ...
Jan. 18, 2017 01:30 AM EST Reads: 4,190
WebRTC is about the data channel as much as about video and audio conferencing. However, basically all commercial WebRTC applications have been built with a focus on audio and video. The handling of “data” has been limited to text chat and file download – all other data sharing seems to end with screensharing. What is holding back a more intensive use of peer-to-peer data? In her session at @ThingsExpo, Dr Silvia Pfeiffer, WebRTC Applications Team Lead at National ICT Australia, looked at differ...
Jan. 18, 2017 01:15 AM EST Reads: 4,857
The cloud market growth today is largely in public clouds. While there is a lot of spend in IT departments in virtualization, these aren’t yet translating into a true “cloud” experience within the enterprise. What is stopping the growth of the “private cloud” market? In his general session at 18th Cloud Expo, Nara Rajagopalan, CEO of Accelerite, explored the challenges in deploying, managing, and getting adoption for a private cloud within an enterprise. What are the key differences between wh...
Jan. 18, 2017 01:00 AM EST Reads: 6,041
"Splunk basically takes machine data and we make it usable, valuable and accessible for everyone. The way that plays in DevOps is - we need to make data-driven decisions to delivering applications," explained Andi Mann, Chief Technology Advocate at Splunk and @DevOpsSummit Conference Chair, in this SYS-CON.tv interview at @DevOpsSummit at 19th Cloud Expo, held November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA.
Jan. 18, 2017 01:00 AM EST Reads: 2,002
"Logz.io is a log analytics platform. We offer the ELK stack, which is the most common log analytics platform in the world. We offer it as a cloud service," explained Tomer Levy, co-founder and CEO of Logz.io, in this SYS-CON.tv interview at DevOps Summit, held November 3-5, 2015, at the Santa Clara Convention Center in Santa Clara, CA.
Jan. 18, 2017 12:45 AM EST Reads: 6,238
Adding public cloud resources to an existing application can be a daunting process. The tools that you currently use to manage the software and hardware outside the cloud aren’t always the best tools to efficiently grow into the cloud. All of the major configuration management tools have cloud orchestration plugins that can be leveraged, but there are also cloud-native tools that can dramatically improve the efficiency of managing your application lifecycle. In his session at 18th Cloud Expo, ...
Jan. 18, 2017 12:45 AM EST Reads: 5,938
In his session at @DevOpsSummit at 19th Cloud Expo, Robert Doyle, lead architect at eCube Systems, will examine the issues and need for an agile infrastructure and show the advantages of capturing developer knowledge in an exportable file for migration into production. He will introduce the use of NXTmonitor, a next-generation DevOps tool that captures application environments, dependencies and start/stop procedures in a portable configuration file with an easy-to-use GUI. In addition to captur...
Jan. 18, 2017 12:30 AM EST Reads: 2,774
"ReadyTalk is an audio and web video conferencing provider. We've really come to embrace WebRTC as the platform for our future of technology," explained Dan Cunningham, CTO of ReadyTalk, in this SYS-CON.tv interview at WebRTC Summit at 19th Cloud Expo, held November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA.
Jan. 18, 2017 12:00 AM EST Reads: 2,253
Due of the rise of Hadoop, many enterprises are now deploying their first small clusters of 10 to 20 servers. At this small scale, the complexity of operating the cluster looks and feels like general data center servers. It is not until the clusters scale, as they inevitably do, when the pain caused by the exponential complexity becomes apparent. We've seen this problem occur time and time again. In his session at Big Data Expo, Greg Bruno, Vice President of Engineering and co-founder of StackIQ...
Jan. 18, 2017 12:00 AM EST Reads: 7,728
One of the hottest areas in cloud right now is DRaaS and related offerings. In his session at 16th Cloud Expo, Dale Levesque, Disaster Recovery Product Manager with Windstream's Cloud and Data Center Marketing team, will discuss the benefits of the cloud model, which far outweigh the traditional approach, and how enterprises need to ensure that their needs are properly being met.
Jan. 17, 2017 11:30 PM EST Reads: 4,307
Containers have changed the mind of IT in DevOps. They enable developers to work with dev, test, stage and production environments identically. Containers provide the right abstraction for microservices and many cloud platforms have integrated them into deployment pipelines. DevOps and Containers together help companies to achieve their business goals faster and more effectively. In his session at DevOps Summit, Ruslan Synytsky, CEO and Co-founder of Jelastic, reviewed the current landscape of D...
Jan. 17, 2017 11:15 PM EST Reads: 4,885
In 2014, Amazon announced a new form of compute called Lambda. We didn't know it at the time, but this represented a fundamental shift in what we expect from cloud computing. Now, all of the major cloud computing vendors want to take part in this disruptive technology. In his session at 20th Cloud Expo, John Jelinek IV, a web developer at Linux Academy, will discuss why major players like AWS, Microsoft Azure, IBM Bluemix, and Google Cloud Platform are all trying to sidestep VMs and containers...
Jan. 17, 2017 11:00 PM EST Reads: 532
IoT is at the core or many Digital Transformation initiatives with the goal of re-inventing a company's business model. We all agree that collecting relevant IoT data will result in massive amounts of data needing to be stored. However, with the rapid development of IoT devices and ongoing business model transformation, we are not able to predict the volume and growth of IoT data. And with the lack of IoT history, traditional methods of IT and infrastructure planning based on the past do not app...
Jan. 17, 2017 10:30 PM EST Reads: 694
The many IoT deployments around the world are busy integrating smart devices and sensors into their enterprise IT infrastructures. Yet all of this technology – and there are an amazing number of choices – is of no use without the software to gather, communicate, and analyze the new data flows. Without software, there is no IT. In this power panel at @ThingsExpo, moderated by Conference Chair Roger Strukhoff, Dave McCarthy, Director of Products at Bsquare Corporation; Alan Williamson, Principal ...
Jan. 17, 2017 10:30 PM EST Reads: 2,341
DevOps and microservices are permeating software engineering teams broadly, whether these teams are in pure software shops but happen to run a business, such Uber and Airbnb, or in companies that rely heavily on software to run more traditional business, such as financial firms or high-end manufacturers. Microservices and DevOps have created software development and therefore business speed and agility benefits, but they have also created problems; specifically, they have created software securi...
Jan. 17, 2017 09:30 PM EST Reads: 1,770