[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-239446-105":53,"doc-detail-239446-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","manufacturing-project-plans-objective","Manufacturing Project Plans - Objective","","Manufacturing Project Plans presents the Whitemarsh approach to engineering project planning using standardized work breakdown structures, earned-value proven metrics, and metadata management in the Metabase system, including earned value–based reporting support. The paper frames project-management data as metadata that abstracts real projects, aligning it with real-product metadata so both can be managed in a common database. It outlines objectives, key topics, WBS understanding, and key practices that address estimation, scheduling, staffing, and earned value recording to improve project execution.",{"@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":11,"@type":70,"position":76},"https://docshare.wps.com/template/presentations/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/manufacturing-project-plans-objective/239446/",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/manufacturing-project-plans-objective/239446.png","ImageObject",442,249,{"name":88,"@type":89},"Ethan Miller","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-30","2026-09-11",true,{"@type":98,"interactionType":99,"userInteractionCount":30},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"What is the main objective of the paper on manufacturing project plans?","Question",{"text":108,"@type":109},"The paper presents the Whitemarsh approach to engineering project plans using standardized WBS collections, earned-value metrics, and management within the Metabase metadata management system, which supports earned value–based reporting.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"How does the paper define work breakdown structures (WBS)?",{"text":113,"@type":109},"A WBS is a breakdown of work. Since work can be a product (noun) or processes (verb), the paper treats WBS as both product and process breakdown structures.",{"name":115,"@type":106,"acceptedAnswer":116},"Why does the paper claim project-management data should be managed with real-product metadata?",{"text":117,"@type":109},"Project-management data is treated as metadata representing abstractions of real projects, overlapping in purpose and content with real-product metadata, so both belong in the same database under a common metadata management system (Metabase).","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},239446,1791289249,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":8,"category_name":11,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":30,"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":8},687207017582,"https://ap-avatar.wpscdn.com/davatar_994ba38a5ba835b3df7d355c54d3ed8d","Manufacturing Project Plans  \nWhitemarsh Information Systems Corporation 2008 Althea Lane Bowie, Maryland 20716 Tele: 301-249-1142  \n[Email: Whitemarsh@wiscorp.com](Email: Whitemarsh@wiscorp.com)[ ](Email: Whitemarsh@wiscorp.com)[Web: www.wiscorp.com](Web: www.wiscorp.com)  \nTable of Contents  \n1.0 Objective .............................................................. 1  \n2.0 Topics ................................................................. 1  \n3.0 Understanding Work Breakdown Structures ................................... 2  \n3.1 Understanding WBS .................................................. 4  \n3.2 Homogeneous Wn&vBS............................................... 6  \n3.3 Heterogeneous Wn&vBS .............................................. 9  \n3.4 Work Plan Summary ................................................. 11  \n4.0 Highly Engineered Project Management ..................................... 13  \n5.0 Standardized Project and Deliverables Templates .............................. 15  \n6.0 Assessing and Assigning Staff ............................................. 18  \n7.0 Project Plan Constriction and Estimation .................................... 20  \n8.0 Recording Work and Generating Earned Value Reporting ....................... 26  \n9.0 Conclusions ........................................................... 27  \n10.0 References ............................................................ 28  \nCopyright 2008, Whitemarsh Information Systems Corporation Proprietary Data, All Rights Reserved ii  \n1.0 Objective  \nThe objective of this paper is to present the Whitemarsh approach to engineering project plans through the use of collections of standardized work breakdown structures, earned-value proven metrics, and the management of these plans within a comprehensive metadata management system, Metabase, that additionally supports earned value based reporting.  \nThis paper asserts that there is no real difference between real-product metadata and project-management data. Project management data is metadata because it represents an abstraction of real-projects. Both forms of these metadata overlap in content and purpose. Each however has a different use-perspective. Real-product metadata serves to identify, catalog, and manage metadata-based representations of deliverables (i.e., data and process models) . In contrast, project-management data identifies, catalogues, and manages the projects that ultimately result in the creation of real-product metadata.  \nConsequently, this paper asserts that because of the overlap of purpose and content, both real-product metadata and project-management data belong in the same database and should be managed by a common metadata management system. For Whitemarsh, that means the Metabase System. As of the writing of this Short Paper, both the Metabase System and the Whitemarsh project management system exist but have not yet been integrated. The points of integration are obvious and were designed to be so. Additionally, the development environment employed by Whitemarsh enables the integration of these data and systems in just a few staff months.  \n2.0 Topics  \nThe topics is this paper include:  \n! Understanding Work Breakdown Structures! Highly Engineered Project Management! Standardized Project and Deliverables Templates! Assessing and Assigning Staff  \n! Project Plan Construction and Estimation! Recording Work and Generating Earned Value Reporting  \nMore software projects have gone awry for lack of calendar time than for all other causes combined. Why is this cause of disaster so common? Five reasons come to mind.  \n! First, our techniques of estimating are poorly developed. More seriously, they reflect an unvoiced assumption which is quite untrue, i.e., that all will go well.  \n! Second, our estimating techniques fallaciously confuse hours expended with deliverables accomplished, hiding the assumption that men and months are interchangeable.  \nCopyright 2008, Whitemarsh Inform","cbCaipCioWxNyjnF","https://ap.wps.com/l/cbCaipCioWxNyjnF","pdf",322189,32,"English","# Objective\n# Topics\n# Understanding Work Breakdown Structures\n## Understanding WBS\n## Homogeneous Wn&vBS\n## Heterogeneous Wn&vBS\n## Work Plan Summary\n# Highly Engineered Project Management\n# Standardized Project and Deliverables Templates\n# Assessing and Assigning Staff\n# Project Plan Construction and Estimation\n# Recording Work and Generating Earned Value Reporting\n# Conclusions\n# References","[{\"question\":\"What is the main objective of the paper on manufacturing project plans?\",\"answer\":\"The paper presents the Whitemarsh approach to engineering project plans using standardized WBS collections, earned-value metrics, and management within the Metabase metadata management system, which supports earned value–based reporting.\"},{\"question\":\"How does the paper define work breakdown structures (WBS)?\",\"answer\":\"A WBS is a breakdown of work. Since work can be a product (noun) or processes (verb), the paper treats WBS as both product and process breakdown structures.\"},{\"question\":\"Why does the paper claim project-management data should be managed with real-product metadata?\",\"answer\":\"Project-management data is treated as metadata representing abstractions of real projects, overlapping in purpose and content with real-product metadata, so both belong in the same database under a common metadata management system (Metabase).\"}]","Manufacturing Project Plans - Objective | PDF",1789148943]