{"id":70,"date":"2018-06-14T19:04:45","date_gmt":"2018-06-14T19:04:45","guid":{"rendered":"https:\/\/pressbooks.ccconline.org\/bus3060\/chapter\/ch09-6\/"},"modified":"2026-02-14T18:41:38","modified_gmt":"2026-02-14T18:41:38","slug":"ch09-6","status":"publish","type":"chapter","link":"https:\/\/pressbooks.ccconline.org\/bus3060\/chapter\/ch09-6\/","title":{"raw":"9.6 Total Cost of Ownership (TCO): Tech Costs Go Way beyond the Price Tag","rendered":"9.6 Total Cost of Ownership (TCO): Tech Costs Go Way beyond the Price Tag"},"content":{"raw":"<div id=\"slug-9-6-total-cost-of-ownership-tco-tech-costs-go-way-beyond-the-price-tag\" class=\"chapter standard\">\r\n<div class=\"ugc chapter-ugc\">\r\n<div id=\"fwk-38086-ch09_s06_n01\" class=\"bcc-box bcc-highlight\">\r\n<div class=\"textbox textbox--learning-objectives\"><header class=\"textbox__header\">\r\n<p class=\"textbox__title\"><span style=\"font-family: 'Cormorant Garamond', serif; font-size: 1em; font-style: normal; font-weight: bold;\">Learning Objectives<\/span><\/p>\r\n\r\n<\/header>\r\n<div class=\"textbox__content\">\r\n<p id=\"fwk-38086-ch09_s06_p01\" class=\"nonindent para\">After studying this section you should be able to do the following:<\/p>\r\n\r\n<ol id=\"fwk-38086-ch09_s06_l01\" class=\"orderedlist\">\r\n \t<li>List the different cost categories that comprise total cost of ownership.<\/li>\r\n \t<li>Understand that once a system is implemented, the costs of maintaining and supporting the system continue.<\/li>\r\n \t<li>List the reasons that technology development projects fail and the measures that can be taken to increase the probability of success.<\/li>\r\n<\/ol>\r\n<\/div>\r\n<\/div>\r\n<\/div>\r\n<p id=\"fwk-38086-ch09_s06_p02\" class=\"nonindent para editable block\">Managers should recognize that there are a whole host of costs that are associated with creating and supporting an organization\u2019s information systems. Of course, there are programming costs for custom software as well as purchase, configuration, and licensing costs for packaged software, but there\u2019s much, much more.<\/p>\r\n<p id=\"fwk-38086-ch09_s06_p03\" class=\"indent para editable block\">There are costs associated with design and documentation (both for programmers and for users). There are also testing costs. New programs should be tested thoroughly across the various types of hardware the firm uses, and in conjunction with existing software and systems, <em class=\"emphasis\">before<\/em> being deployed throughout the organization. Any errors that aren\u2019t caught can slow down a business or lead to costly mistakes that could ripple throughout an organization and its partners. Studies have shown that errors not caught before deployment could be one hundred times more costly to correct than if they were detected and corrected beforehand (Charette, 2005).<\/p>\r\n<p id=\"fwk-38086-ch09_s06_p04\" class=\"indent para editable block\">Once a system is \u201cturned on,\u201d the work doesn\u2019t end there. Firms need to constantly engage in a host of activities to support the system that may also include the following:<\/p>\r\n\r\n<ul id=\"fwk-38086-ch09_s06_l02\" class=\"itemizedlist editable block\">\r\n \t<li>providing training and end user support<\/li>\r\n \t<li>collecting and relaying comments for system improvements<\/li>\r\n \t<li>auditing systems to ensure <span class=\"margin_term\"><a class=\"glossterm\">compliance<\/a><\/span> (i.e., that the system operates within the firm\u2019s legal constraints and industry obligations)<\/li>\r\n \t<li>providing regular backup of critical data<\/li>\r\n \t<li>planning for redundancy and disaster recovery in case of an outage<\/li>\r\n \t<li>vigilantly managing the moving target of computer security issues<\/li>\r\n<\/ul>\r\n<p id=\"fwk-38086-ch09_s06_p05\" class=\"indent para editable block\">With so much to do, it\u2019s no wonder that firms spend 70 to 80 percent of their information systems (IS) budgets just to keep their systems running (Rettig, 2007). The price tag and complexity of these tasks can push some managers to think of technology as being a cost sink rather than a strategic resource. These tasks are often collectively referred to as the <strong><span class=\"margin_term\"><a class=\"glossterm\">total cost of ownership (TCO)<\/a><\/span><\/strong> of an information system. Understanding TCO is critical when making technology investment decisions. TCO is also a major driving force behind the massive tech industry changes discussed in <strong>Chapter 10 \u201cSoftware in Flux: Partly Cloudy and Sometimes Free<\/strong>\u201d.<\/p>\r\n\r\n<div id=\"fwk-38086-ch09_s06_s01\" class=\"section\">\r\n<h2 class=\"title editable block\">Why Do Technology Projects Fail?<\/h2>\r\n<p id=\"fwk-38086-ch09_s06_s01_p01\" class=\"nonindent para editable block\">Even though information systems represent the largest portion of capital spending at most firms, an astonishing one in three technology development projects fail to be successfully deployed (Dignan, 2007). Imagine if a firm lost its investment in one out of every three land purchases, or when building one in three factories. These statistics are dismal! Writing in <em class=\"emphasis\">IEEE Spectrum<\/em>, risk consultant Robert Charette provides a sobering assessment of the cost of software failures, stating, \u201cThe yearly tab for failed and troubled software conservatively runs somewhere from $60 to $70 billion in the United States alone. For that money, you could launch the space shuttle one hundred times, build and deploy the entire 24-satellite Global Positioning System, and develop the Boeing 777 from scratch\u2014and still have a few billion left over\u201d (Charette, 2005).<\/p>\r\n<p id=\"fwk-38086-ch09_s06_s01_p02\" class=\"indent para editable block\">Why such a bad track record? Sometimes technology itself is to blame, other times it\u2019s a failure to test systems adequately, and sometimes it\u2019s a breakdown of process and procedures used to set specifications and manage projects. In one example, a multimillion-dollar loss on the NASA Mars Observer was traced back to a laughably simple oversight\u2014Lockheed Martin contractors using English measurements, while the folks at NASA used the metric system (Lloyd, 1999). Yes, a $125 million taxpayer investment was lost because a bunch of rocket scientists failed to pay attention to third grade math. When it comes to the success or failure of technical projects, the devil really is in the details.<\/p>\r\n<p id=\"fwk-38086-ch09_s06_s01_p03\" class=\"indent para editable block\">Projects rarely fail for just one reason. Project post-mortems often point to a combination of technical, project management, and business decision blunders. The most common factors include the following<sup>2<\/sup>:<\/p>\r\n\r\n<ul id=\"fwk-38086-ch09_s06_s01_l01\" class=\"itemizedlist editable block\">\r\n \t<li>Unrealistic or unclear project goals<\/li>\r\n \t<li>Poor project leadership and weak executive commitment<\/li>\r\n \t<li>Inaccurate estimates of needed resources<\/li>\r\n \t<li>Badly defined system requirements and allowing \u201cfeature creep\u201d during development<\/li>\r\n \t<li>Poor reporting of the project\u2019s status<\/li>\r\n \t<li>Poor communication among customers, developers, and users<\/li>\r\n \t<li>Use of immature technology<\/li>\r\n \t<li>Unmanaged risks<\/li>\r\n \t<li>Inability to handle the project\u2019s complexity<\/li>\r\n \t<li>Sloppy development and testing practices<\/li>\r\n \t<li>Poor project management<\/li>\r\n \t<li>Stakeholder politics<\/li>\r\n \t<li>Commercial pressures (e.g., leaving inadequate time or encouraging corner-cutting)<\/li>\r\n<\/ul>\r\n<p id=\"fwk-38086-ch09_s06_s01_p04\" class=\"indent para editable block\">Managers need to understand the complexity involved in their technology investments, and that achieving success rarely lies with the strength of the technology alone.<\/p>\r\n<p id=\"fwk-38086-ch09_s06_s01_p05\" class=\"indent para editable block\">But there is hope. Information systems organizations can work to implement procedures to improve the overall quality of their development practices. Mechanisms for quality improvement include <strong><span class=\"margin_term\"><a class=\"glossterm\">capability maturity model integration (CMMI)<\/a><\/span><\/strong>, which gauge an organization\u2019s process maturity and capability in areas critical to developing and deploying technology projects, and provides a carefully chosen set of best practices and guidelines to assist quality and process improvement<sup>1<\/sup> (Kay, 2005).<\/p>\r\n<p id=\"fwk-38086-ch09_s06_s01_p06\" class=\"indent para editable block\">Firms are also well served to leverage established project planning and software development methodologies that outline critical businesses processes and stages when executing large-scale software development projects. The idea behind these methodologies is straightforward\u2014why reinvent the wheel when there is an opportunity to learn from and follow blueprints used by those who have executed successful efforts. When methodologies are applied to projects that are framed with clear business goals and business metrics, and that engage committed executive leadership, success rates can improve dramatically (Shenhar &amp; Dvir, 2007).<\/p>\r\n<p id=\"fwk-38086-ch09_s06_s01_p07\" class=\"indent para editable block\">While software development methodologies are the topic of more advanced technology courses, the savvy manager knows enough to inquire about the development methodologies and quality programs used to support large scale development projects, and can use these investigations as further input when evaluating whether those overseeing large scale efforts have what it takes to get the job done.<\/p>\r\n\r\n<div id=\"fwk-38086-ch09_s06_s01_n01\" class=\"bcc-box bcc-success\">\r\n<div class=\"textbox textbox--key-takeaways\"><header class=\"textbox__header\">\r\n<p class=\"textbox__title\"><span style=\"font-family: 'Cormorant Garamond', serif; font-size: 1em; font-style: normal; font-weight: bold;\">Key Takeaways<\/span><\/p>\r\n\r\n<\/header>\r\n<div class=\"textbox__content\">\r\n<ul>\r\n \t<li data-pm-slice=\"1 1 []\">Information systems are expensive to build and maintain. The full cost (called total cost of ownership, or TCO) includes software, support, training, security, backups, and more.<\/li>\r\n \t<li>Many information systems projects fail because of technical problems, poor planning, or management mistakes.<\/li>\r\n \t<li>Using good development methods (like CMMI), strong leadership, and clear business goals can improve success.<\/li>\r\n \t<li>Fixing errors after a system is launched can cost up to 100 times more than catching them early.<\/li>\r\n \t<li>Most companies spend 70\u201380% of their IS budget just keeping current systems running.<\/li>\r\n \t<li>About one-third of technology projects never get fully deployed.<\/li>\r\n \t<li>Careful planning and proven development practices help organizations build better systems.<\/li>\r\n<\/ul>\r\n<\/div>\r\n<\/div>\r\n&nbsp;\r\n\r\n<\/div>\r\n<div id=\"fwk-38086-ch09_s06_s01_n02\" class=\"bcc-box bcc-info\">\r\n<div class=\"textbox textbox--exercises\"><header class=\"textbox__header\">\r\n<p class=\"textbox__title\"><span style=\"font-family: 'Cormorant Garamond', serif; font-size: 1em; font-style: normal; font-weight: bold;\">Questions and Exercises<\/span><\/p>\r\n\r\n<\/header>\r\n<div class=\"textbox__content\">\r\n<ol id=\"fwk-38086-ch09_s06_s01_l03\" class=\"orderedlist\">\r\n \t<li>List the types of total ownership costs associated with creating and supporting an organization\u2019s information systems.<\/li>\r\n \t<li>On average, what percent of firms\u2019 IS budgets is spent to keep their systems running?<\/li>\r\n \t<li>What are the possible effects of not detecting and fixing major system errors before deployment?<\/li>\r\n \t<li>List some of the reasons for the failure of technology development projects.<\/li>\r\n \t<li>What is the estimated yearly cost of failed technology development projects?<\/li>\r\n<\/ol>\r\n<\/div>\r\n<\/div>\r\n&nbsp;\r\n\r\n<\/div>\r\n<\/div>\r\n<p class=\"indent\"><sup>1<\/sup>Carnegie Mellon Software Engineering Institute, <em class=\"emphasis\">Welcome to CMMI<\/em>, 2009, <a class=\"link\" href=\"http:\/\/www.sei.cmu.edu\/cmmi\" target=\"_blank\" rel=\"noopener\">http:\/\/www.sei.cmu.edu\/cmmi<\/a>.<\/p>\r\n<p class=\"indent\"><sup>2<\/sup>List largely based on R. Charette, \u201cWhy Software Fails,\u201d <em class=\"emphasis\">IEEE Spectrum<\/em>, September 2005.<\/p>\r\n\r\n<\/div>\r\n<\/div>","rendered":"<div id=\"slug-9-6-total-cost-of-ownership-tco-tech-costs-go-way-beyond-the-price-tag\" class=\"chapter standard\">\n<div class=\"ugc chapter-ugc\">\n<div id=\"fwk-38086-ch09_s06_n01\" class=\"bcc-box bcc-highlight\">\n<div class=\"textbox textbox--learning-objectives\">\n<header class=\"textbox__header\">\n<p class=\"textbox__title\"><span style=\"font-family: 'Cormorant Garamond', serif; font-size: 1em; font-style: normal; font-weight: bold;\">Learning Objectives<\/span><\/p>\n<\/header>\n<div class=\"textbox__content\">\n<p id=\"fwk-38086-ch09_s06_p01\" class=\"nonindent para\">After studying this section you should be able to do the following:<\/p>\n<ol id=\"fwk-38086-ch09_s06_l01\" class=\"orderedlist\">\n<li>List the different cost categories that comprise total cost of ownership.<\/li>\n<li>Understand that once a system is implemented, the costs of maintaining and supporting the system continue.<\/li>\n<li>List the reasons that technology development projects fail and the measures that can be taken to increase the probability of success.<\/li>\n<\/ol>\n<\/div>\n<\/div>\n<\/div>\n<p id=\"fwk-38086-ch09_s06_p02\" class=\"nonindent para editable block\">Managers should recognize that there are a whole host of costs that are associated with creating and supporting an organization\u2019s information systems. Of course, there are programming costs for custom software as well as purchase, configuration, and licensing costs for packaged software, but there\u2019s much, much more.<\/p>\n<p id=\"fwk-38086-ch09_s06_p03\" class=\"indent para editable block\">There are costs associated with design and documentation (both for programmers and for users). There are also testing costs. New programs should be tested thoroughly across the various types of hardware the firm uses, and in conjunction with existing software and systems, <em class=\"emphasis\">before<\/em> being deployed throughout the organization. Any errors that aren\u2019t caught can slow down a business or lead to costly mistakes that could ripple throughout an organization and its partners. Studies have shown that errors not caught before deployment could be one hundred times more costly to correct than if they were detected and corrected beforehand (Charette, 2005).<\/p>\n<p id=\"fwk-38086-ch09_s06_p04\" class=\"indent para editable block\">Once a system is \u201cturned on,\u201d the work doesn\u2019t end there. Firms need to constantly engage in a host of activities to support the system that may also include the following:<\/p>\n<ul id=\"fwk-38086-ch09_s06_l02\" class=\"itemizedlist editable block\">\n<li>providing training and end user support<\/li>\n<li>collecting and relaying comments for system improvements<\/li>\n<li>auditing systems to ensure <span class=\"margin_term\"><a class=\"glossterm\">compliance<\/a><\/span> (i.e., that the system operates within the firm\u2019s legal constraints and industry obligations)<\/li>\n<li>providing regular backup of critical data<\/li>\n<li>planning for redundancy and disaster recovery in case of an outage<\/li>\n<li>vigilantly managing the moving target of computer security issues<\/li>\n<\/ul>\n<p id=\"fwk-38086-ch09_s06_p05\" class=\"indent para editable block\">With so much to do, it\u2019s no wonder that firms spend 70 to 80 percent of their information systems (IS) budgets just to keep their systems running (Rettig, 2007). The price tag and complexity of these tasks can push some managers to think of technology as being a cost sink rather than a strategic resource. These tasks are often collectively referred to as the <strong><span class=\"margin_term\"><a class=\"glossterm\">total cost of ownership (TCO)<\/a><\/span><\/strong> of an information system. Understanding TCO is critical when making technology investment decisions. TCO is also a major driving force behind the massive tech industry changes discussed in <strong>Chapter 10 \u201cSoftware in Flux: Partly Cloudy and Sometimes Free<\/strong>\u201d.<\/p>\n<div id=\"fwk-38086-ch09_s06_s01\" class=\"section\">\n<h2 class=\"title editable block\">Why Do Technology Projects Fail?<\/h2>\n<p id=\"fwk-38086-ch09_s06_s01_p01\" class=\"nonindent para editable block\">Even though information systems represent the largest portion of capital spending at most firms, an astonishing one in three technology development projects fail to be successfully deployed (Dignan, 2007). Imagine if a firm lost its investment in one out of every three land purchases, or when building one in three factories. These statistics are dismal! Writing in <em class=\"emphasis\">IEEE Spectrum<\/em>, risk consultant Robert Charette provides a sobering assessment of the cost of software failures, stating, \u201cThe yearly tab for failed and troubled software conservatively runs somewhere from $60 to $70 billion in the United States alone. For that money, you could launch the space shuttle one hundred times, build and deploy the entire 24-satellite Global Positioning System, and develop the Boeing 777 from scratch\u2014and still have a few billion left over\u201d (Charette, 2005).<\/p>\n<p id=\"fwk-38086-ch09_s06_s01_p02\" class=\"indent para editable block\">Why such a bad track record? Sometimes technology itself is to blame, other times it\u2019s a failure to test systems adequately, and sometimes it\u2019s a breakdown of process and procedures used to set specifications and manage projects. In one example, a multimillion-dollar loss on the NASA Mars Observer was traced back to a laughably simple oversight\u2014Lockheed Martin contractors using English measurements, while the folks at NASA used the metric system (Lloyd, 1999). Yes, a $125 million taxpayer investment was lost because a bunch of rocket scientists failed to pay attention to third grade math. When it comes to the success or failure of technical projects, the devil really is in the details.<\/p>\n<p id=\"fwk-38086-ch09_s06_s01_p03\" class=\"indent para editable block\">Projects rarely fail for just one reason. Project post-mortems often point to a combination of technical, project management, and business decision blunders. The most common factors include the following<sup>2<\/sup>:<\/p>\n<ul id=\"fwk-38086-ch09_s06_s01_l01\" class=\"itemizedlist editable block\">\n<li>Unrealistic or unclear project goals<\/li>\n<li>Poor project leadership and weak executive commitment<\/li>\n<li>Inaccurate estimates of needed resources<\/li>\n<li>Badly defined system requirements and allowing \u201cfeature creep\u201d during development<\/li>\n<li>Poor reporting of the project\u2019s status<\/li>\n<li>Poor communication among customers, developers, and users<\/li>\n<li>Use of immature technology<\/li>\n<li>Unmanaged risks<\/li>\n<li>Inability to handle the project\u2019s complexity<\/li>\n<li>Sloppy development and testing practices<\/li>\n<li>Poor project management<\/li>\n<li>Stakeholder politics<\/li>\n<li>Commercial pressures (e.g., leaving inadequate time or encouraging corner-cutting)<\/li>\n<\/ul>\n<p id=\"fwk-38086-ch09_s06_s01_p04\" class=\"indent para editable block\">Managers need to understand the complexity involved in their technology investments, and that achieving success rarely lies with the strength of the technology alone.<\/p>\n<p id=\"fwk-38086-ch09_s06_s01_p05\" class=\"indent para editable block\">But there is hope. Information systems organizations can work to implement procedures to improve the overall quality of their development practices. Mechanisms for quality improvement include <strong><span class=\"margin_term\"><a class=\"glossterm\">capability maturity model integration (CMMI)<\/a><\/span><\/strong>, which gauge an organization\u2019s process maturity and capability in areas critical to developing and deploying technology projects, and provides a carefully chosen set of best practices and guidelines to assist quality and process improvement<sup>1<\/sup> (Kay, 2005).<\/p>\n<p id=\"fwk-38086-ch09_s06_s01_p06\" class=\"indent para editable block\">Firms are also well served to leverage established project planning and software development methodologies that outline critical businesses processes and stages when executing large-scale software development projects. The idea behind these methodologies is straightforward\u2014why reinvent the wheel when there is an opportunity to learn from and follow blueprints used by those who have executed successful efforts. When methodologies are applied to projects that are framed with clear business goals and business metrics, and that engage committed executive leadership, success rates can improve dramatically (Shenhar &amp; Dvir, 2007).<\/p>\n<p id=\"fwk-38086-ch09_s06_s01_p07\" class=\"indent para editable block\">While software development methodologies are the topic of more advanced technology courses, the savvy manager knows enough to inquire about the development methodologies and quality programs used to support large scale development projects, and can use these investigations as further input when evaluating whether those overseeing large scale efforts have what it takes to get the job done.<\/p>\n<div id=\"fwk-38086-ch09_s06_s01_n01\" class=\"bcc-box bcc-success\">\n<div class=\"textbox textbox--key-takeaways\">\n<header class=\"textbox__header\">\n<p class=\"textbox__title\"><span style=\"font-family: 'Cormorant Garamond', serif; font-size: 1em; font-style: normal; font-weight: bold;\">Key Takeaways<\/span><\/p>\n<\/header>\n<div class=\"textbox__content\">\n<ul>\n<li data-pm-slice=\"1 1 []\">Information systems are expensive to build and maintain. The full cost (called total cost of ownership, or TCO) includes software, support, training, security, backups, and more.<\/li>\n<li>Many information systems projects fail because of technical problems, poor planning, or management mistakes.<\/li>\n<li>Using good development methods (like CMMI), strong leadership, and clear business goals can improve success.<\/li>\n<li>Fixing errors after a system is launched can cost up to 100 times more than catching them early.<\/li>\n<li>Most companies spend 70\u201380% of their IS budget just keeping current systems running.<\/li>\n<li>About one-third of technology projects never get fully deployed.<\/li>\n<li>Careful planning and proven development practices help organizations build better systems.<\/li>\n<\/ul>\n<\/div>\n<\/div>\n<p>&nbsp;<\/p>\n<\/div>\n<div id=\"fwk-38086-ch09_s06_s01_n02\" class=\"bcc-box bcc-info\">\n<div class=\"textbox textbox--exercises\">\n<header class=\"textbox__header\">\n<p class=\"textbox__title\"><span style=\"font-family: 'Cormorant Garamond', serif; font-size: 1em; font-style: normal; font-weight: bold;\">Questions and Exercises<\/span><\/p>\n<\/header>\n<div class=\"textbox__content\">\n<ol id=\"fwk-38086-ch09_s06_s01_l03\" class=\"orderedlist\">\n<li>List the types of total ownership costs associated with creating and supporting an organization\u2019s information systems.<\/li>\n<li>On average, what percent of firms\u2019 IS budgets is spent to keep their systems running?<\/li>\n<li>What are the possible effects of not detecting and fixing major system errors before deployment?<\/li>\n<li>List some of the reasons for the failure of technology development projects.<\/li>\n<li>What is the estimated yearly cost of failed technology development projects?<\/li>\n<\/ol>\n<\/div>\n<\/div>\n<p>&nbsp;<\/p>\n<\/div>\n<\/div>\n<p class=\"indent\"><sup>1<\/sup>Carnegie Mellon Software Engineering Institute, <em class=\"emphasis\">Welcome to CMMI<\/em>, 2009, <a class=\"link\" href=\"http:\/\/www.sei.cmu.edu\/cmmi\" target=\"_blank\" rel=\"noopener\">http:\/\/www.sei.cmu.edu\/cmmi<\/a>.<\/p>\n<p class=\"indent\"><sup>2<\/sup>List largely based on R. Charette, \u201cWhy Software Fails,\u201d <em class=\"emphasis\">IEEE Spectrum<\/em>, September 2005.<\/p>\n<\/div>\n<\/div>\n","protected":false},"author":217,"menu_order":6,"template":"","meta":{"pb_show_title":"on","pb_short_title":"","pb_subtitle":"","pb_authors":[],"pb_section_license":""},"chapter-type":[49],"contributor":[],"license":[],"class_list":["post-70","chapter","type-chapter","status-publish","hentry","chapter-type-numberless"],"part":51,"_links":{"self":[{"href":"https:\/\/pressbooks.ccconline.org\/bus3060\/wp-json\/pressbooks\/v2\/chapters\/70","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pressbooks.ccconline.org\/bus3060\/wp-json\/pressbooks\/v2\/chapters"}],"about":[{"href":"https:\/\/pressbooks.ccconline.org\/bus3060\/wp-json\/wp\/v2\/types\/chapter"}],"author":[{"embeddable":true,"href":"https:\/\/pressbooks.ccconline.org\/bus3060\/wp-json\/wp\/v2\/users\/217"}],"version-history":[{"count":7,"href":"https:\/\/pressbooks.ccconline.org\/bus3060\/wp-json\/pressbooks\/v2\/chapters\/70\/revisions"}],"predecessor-version":[{"id":646,"href":"https:\/\/pressbooks.ccconline.org\/bus3060\/wp-json\/pressbooks\/v2\/chapters\/70\/revisions\/646"}],"part":[{"href":"https:\/\/pressbooks.ccconline.org\/bus3060\/wp-json\/pressbooks\/v2\/parts\/51"}],"metadata":[{"href":"https:\/\/pressbooks.ccconline.org\/bus3060\/wp-json\/pressbooks\/v2\/chapters\/70\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/pressbooks.ccconline.org\/bus3060\/wp-json\/wp\/v2\/media?parent=70"}],"wp:term":[{"taxonomy":"chapter-type","embeddable":true,"href":"https:\/\/pressbooks.ccconline.org\/bus3060\/wp-json\/pressbooks\/v2\/chapter-type?post=70"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/pressbooks.ccconline.org\/bus3060\/wp-json\/wp\/v2\/contributor?post=70"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/pressbooks.ccconline.org\/bus3060\/wp-json\/wp\/v2\/license?post=70"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}