[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-241288-105":53,"doc-detail-241288-en":126},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","neon-configuration-management-plan-cmp","NEON Configuration Management Plan (CMP)","","NEON Configuration Management Plan (CMP) defines how configuration management is planned, organized, governed, and executed for the National Ecological Observatory Network. It documents responsibilities and authority across NSF and internal roles, outlines configuration management planning and administration, and specifies configuration tools. The plan records release and approval information, establishes scope and order of precedence, and maintains a change record with historical revisions aligned to configuration management standards.",{"@graph":63,"@context":118},[64,80,101],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":51,"@type":70,"position":76},"https://docshare.wps.com/template/general/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/neon-configuration-management-plan-cmp/241288/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/neon-configuration-management-plan-cmp/241288.png","ImageObject",442,249,{"name":88,"@type":89},"supergirl","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-09-22","2026-09-12",true,{"@type":98,"interactionType":99,"userInteractionCount":47},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"What is the purpose of the NEON Configuration Management Plan (CMP)?","Question",{"text":108,"@type":109},"The CMP establishes the configuration management approach for NEON, defining how it is planned, administered, and governed. It also specifies purpose and scope for consistent execution across the program.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"What scope and order of precedence are defined in the CMP?",{"text":113,"@type":109},"The CMP includes scope statements and an order of precedence section to clarify which requirements or documents take priority. This supports consistent interpretation during configuration management activities.",{"name":115,"@type":106,"acceptedAnswer":116},"How is change history tracked within the CMP?",{"text":117,"@type":109},"A change record lists revisions with dates, ECO numbers, and descriptions of updates. It also references approvals and mentions alignment with configuration management standards and system changes.","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},241288,1789985442,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":50,"category_name":51,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":47,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":135,"language":136,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":61,"update_tm":140,"read_time":35},962088121634,"https://ap-avatar.wpscdn.com/davatar_9964176cb1d06d4a9deccf72a44ae3dc","NEON CONFIGURATION MANAGEMENT PLAN (CMP)  \n\n| PREPARED BY | ORGANIZATION | DATE |\n| --- | --- | --- |\n| Jennifer DeNicholas | CM | 03/21/2017 |\n| Kathy Kirby | PMO | 11/10/2016 |\n| Joe Harpring | PQM | 11/10/2016 |\n|  |  |  |\n|  |  |  |\n\n\n| APPROVALS | ORGANIZATION | APPROVAL DATE |\n| --- | --- | --- |\n| Rick Farnsworth | PMO | 04/05/2017 |\n| Ellie Baptiste-Carpenter | OPS | 04/06/2017 |\n|  |  |  |\n\n\n| RELEASED BY | ORGANIZATION | RELEASE DATE |\n| --- | --- | --- |\n| Jennifer DeNicholas | CM | 04/06/2017 |\n\nSee configuration management system for approval history.  \nThe National Ecological Observatory Network is a project solely funded by the National Science Foundation and managed under cooperative agreement by Battelle. Any opinions, findings, and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the  \nNational Science Foundation.  \nChange Record  \n\n| REVISION | DATE | ECO \\# | DESCRIPTION OF CHANGE |\n| --- | --- | --- | --- |\n| A | 05/15/2009 | NEON.MGMT.NPR.000047.CRE | Initial Release of the NEON CMP |\n| A.1 | 07/23/2009 |  | Changes per PDR |\n| B | 09/22/2009 | NEON. MGMT. NPR.000084.CRE | Approval of submitted changes |\n| C_DRAFT | 3/01/2011 | EC0-00280 | Page 1 – 21 Revised to be in line with the new Configuration Management System (CMS) and added Hardware CM. Tracked changes version of this document is available in the CMS. NSF Pre Con version. |\n| C1_DRAFT | 10/11/2011 | ECO-00288 | Update document to new document numbers/template throughout the document. |\n| D | 07/16/2012 | ECO-00327 | Major update / rewrite of CMP to be inline with ANSI-EIA-STD-649-\u003Cbr>B_Configuration Management Standard. Tracked changes version of this document is available in Oracle Agile PLM. |\n| E | 10/15/2015 | ECO-03371 | Major update/rewrite to make the CM Plan comprehensive and consistent with ANSI/EIA-649-B and feedback from NSF. |\n| F | 10/16/2015 | ECO-3379 | Correction to NSF CR Criteria |\n| G | 11/14/2016 | ECO-04315 | Overhaul of entire CMP, update the PCCB process |\n| H | 04/06/2017 | ECO-04610 | Updates to Figure 5: NEON Assembly Numbering Schema, includes mention of CVAL documentation |\n|  |  |  |  |\n\n| Title: NEON Configuration Management Plan (CMP) |  | Date: 04/06/2017 |\n| --- | --- | --- |\n| NEON Doc. \\#: NEON. DOC.000004 | Author: J. DeNicholas | Revision: H |\n\nTABLE OF CONTENTS  \n1 DESCRIPTION..............................................................................................................................1  \n1.1 Purpose ......................................................................................................................................... 1  \n1.2 Scope ............................................................................................................................................. 1  \n1.2.1 Order of Precedence ............................................................................................................. 3  \n2 RELATED DOCUMENTS AND ACRONYMS .....................................................................................4  \n2.1 Applicable Documents .................................................................................................................. 4  \n2.2 Reference Documents................................................................................................................... 4  \n2.2.1 External References .............................................................................................................. 4  \n2.2.2 Acronyms .............................................................................................................................. 5  \n2.2.3 Definitions ............................................................................................................................. 5  \n3 CONFIGURATION MANAGEMENT PLANNING AND ADMINISTRATION ..........................................9  \n3.1 Responsibility and Authority ...........................","cbCaie2AgNHrl66F","https://ap.wps.com/l/cbCaie2AgNHrl66F","pdf",1564802,48,"English","# 1 Description\n## 1.1 Purpose\n## 1.2 Scope\n## 1.2.1 Order of Precedence\n# 2 Related Documents and Acronyms\n## 2.1 Applicable Documents\n## 2.2 Reference Documents\n## 2.2.1 External References\n## 2.2.2 Acronyms\n## 2.2.3 Definitions\n# 3 Configuration Management Planning and Administration\n## 3.1 Responsibility and Authority\n## 3.1.1 National Science Foundation (NSF)\n## 3.1.2 Program Manager (PM)\n## 3.1.3 Deputy Program/Program Manager (DPM)\n## 3.1.4 Systems Engineering (SE) Lead\n## 3.1.5 Science Lead\n## 3.1.6 Engineering Lead\n## 3.1.7 Program Finance and Controls Lead\n## 3.1.8 Data Products Lead\n## 3.1.9 Quality Lead\n## 3.1.10 Initial Operations Lead\n## 3.1.11 NEON Staff and IPT Leads\n## 3.1.12 Configuration Manager\n## 3.1.13 Configuration Analysts\n## 3.2 Configuration Tools","[{\"question\":\"What is the purpose of the NEON Configuration Management Plan (CMP)?\",\"answer\":\"The CMP establishes the configuration management approach for NEON, defining how it is planned, administered, and governed. It also specifies purpose and scope for consistent execution across the program.\"},{\"question\":\"What scope and order of precedence are defined in the CMP?\",\"answer\":\"The CMP includes scope statements and an order of precedence section to clarify which requirements or documents take priority. This supports consistent interpretation during configuration management activities.\"},{\"question\":\"How is change history tracked within the CMP?\",\"answer\":\"A change record lists revisions with dates, ECO numbers, and descriptions of updates. It also references approvals and mentions alignment with configuration management standards and system changes.\"}]","NEON Configuration Management Plan (CMP) | PDF",1789173141]