[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-307648-105":53,"doc-detail-307648-en":127},{"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":120,"head_meta":122,"extra_data":124,"updated_unix":126},105,"en","new-software-request-form-revised-92025-page-1-of-6","New-Software-Request-Form - Revised 9/2025 - Page 1 of 6","","Process for requesting and evaluating new software for Coppin State University’s technology ecosystem. Departments must initiate early conversations with IT to reduce security, privacy, and compatibility risks. IT evaluates submissions against security, technical fit, accessibility, and level-of-effort criteria, and campus requesters follow the university business process after contract approval. Submission requires an intake form plus supporting documents such as SOC2/HECVAT, SLA, VPAT, technical specs, and contract scope, while unapproved requests receive documented rationale.",{"@graph":63,"@context":119},[64,80,102],{"@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":36,"@type":70,"position":76},"https://docshare.wps.com/template/forms/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/new-software-request-form-revised-92025-page-1-of-6/307648/",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/new-software-request-form-revised-92025-page-1-of-6/307648.png","ImageObject",442,249,{"name":88,"@type":89},"Himbo","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-23","2026-09-19",true,{"@type":98,"interactionType":99,"userInteractionCount":101},"InteractionCounter",{"@type":100},"ViewAction",6,{"@type":103,"mainEntity":104},"FAQPage",[105,111,115],{"name":106,"@type":107,"acceptedAnswer":108},"Who should departments contact before seeking new software?","Question",{"text":109,"@type":110},"Departments should engage the Division of Information Technology in initial conversations to mitigate challenges introduced by new technology.","Answer",{"name":112,"@type":107,"acceptedAnswer":113},"What criteria does IT use to review a new software request?",{"text":114,"@type":110},"IT reviews for Security, Technical alignment, Accessibility, and Level of Effort, including whether a technical demo is needed.",{"name":116,"@type":107,"acceptedAnswer":117},"What supporting documents are required when submitting the form?",{"text":118,"@type":110},"Submissions should include items such as a SOC2 Audit Report or HECVAT, a Service Level Agreement for cloud-hosted software, a VPAT, technical specifications/implementation documentation, and contract or scope of work/order form.","https://schema.org",{"og:url":78,"og:type":121,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":123,"canonical":78},"index,follow",{"doc_id":125,"site_id":56},307648,1790950125,{"code":4,"msg":5,"data":128},{"doc_id":125,"user_id":129,"nickname":88,"user_avatar":130,"doc_module":9,"category_id":35,"category_name":36,"doc_title":59,"doc_description":61,"doc_content":131,"file_id":132,"file_url":133,"file_type":134,"file_size":135,"view_count":101,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":101,"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":73},687197100911,"https://ap-avatar.wpscdn.com/avatar/a000239b6f1da00475?x-image-process=image/resize,m_fixed,w_180,h_180&k=1785132997149421697","Division of Information Technology  \nProcess for Software Purchases on Campus  \nBefore starting the process of seeking new software, departments should engage IT in initial conversations to help mitigate any challenges a new technology solution may impose when being introduced to the university’s technology ecosystem.  \nIn today's digital world, universities rely heavily on software to manage operations, teach courses, and support students. While the bells and whistles of systems can be exciting and enchanting, it is essential that all technical solutions in the Coppin State University ecosystem are secure, align with the university priorities, and be compatible with existing systems.  \n1. Meets Security Requirements. IT is responsible for ensuring the security of the university's network and technological systems both on site and off premise (cloud hosted) . Many software applications can contain vulnerabilities that can lead to security breaches, exposing sensitive data to hackers. Further, some companies that manage data do not take due diligence to ensure that data will be transmitted, stored, maintained, processed, and disposed of in a way that is strictly confidential. By evaluating software before introducing it to the campus, IT can identify potential security risks that may be harmful to the campus. Implementing new software without proper evaluation may introduce security vulnerabilities, which can compromise the university's data and system functionality. Evaluating software to ensure it meets IT security and privacy regulations reduces the risk of security breaches.  \n2. Aligns with University Priorities. Evaluating software before installation ensures that the software meets the university's needs and objectives. IT can evaluate software based on its functionality, usability, and compatibility with existing systems. This helps ensure that the university invests in software that enhances productivity, efficiency, and innovation, and aligns with the university's strategic goals.  \n3. Compatible with the University’s Technological Infrastructure. Evaluating software can help ensure that it is compatible with existing systems and infrastructure. IT must ensure that new software can integrate with the university's existing systems to prevent compatibility issues that could disrupt operations. Evaluating software for compatibility can help identify potential integration issues before deployment, saving time and resources and ensuring that the software can be used effectively.  \nCoppin State University’s Division of Information Technology is the agent responsible for this task. As such, campus constituents should comply with the following protocol when seeking new software.  \nCompleting this process does not guarantee the request will be approved. If it is not approved, documentation will be provided for the rationale.  \nNew Software Request Form (revised 9/2025) Page 1 of 6  \nSteps for Requesting New Software  \n1. Complete the Intake Form for New Software. This form requires the area to assemble necessary documents and requirements regarding the project. No software may be permissible within the University’s digital ecosystem if it does not align with IT Security requirements.  \n2. IT will review the form and give an assessment for and provide a recommendation regarding:  \na. Security – if the software meets the minimum standards outlined by IT.  \nb. Technical – if the software will properly align in Coppin’s ecosystem; if technology support is needed, if IT is able to fulfill the requirements. A technical demo will be required.  \nc. Accessibility – if the software meets digital accessibility standards.  \nd. Level of Effort – if IT support is needed, what would be the level of effort from IT (estimated time committed to the support and the timeline IT will be able to fulfill the request)  \n3. The requester must go through the university business process. Once the contract has been approved by the university, then the re","cbCaioYp1gL5wXkW","https://ap.wps.com/l/cbCaioYp1gL5wXkW","pdf",319747,"English","# Steps for Requesting New Software\n## Complete the Intake Form for New Software\n## IT Review and Assessment\n## Business Process After Contract Approval\n# New Software Request Form\n## Request Submission Requirements","[{\"question\":\"Who should departments contact before seeking new software?\",\"answer\":\"Departments should engage the Division of Information Technology in initial conversations to mitigate challenges introduced by new technology.\"},{\"question\":\"What criteria does IT use to review a new software request?\",\"answer\":\"IT reviews for Security, Technical alignment, Accessibility, and Level of Effort, including whether a technical demo is needed.\"},{\"question\":\"What supporting documents are required when submitting the form?\",\"answer\":\"Submissions should include items such as a SOC2 Audit Report or HECVAT, a Service Level Agreement for cloud-hosted software, a VPAT, technical specifications/implementation documentation, and contract or scope of work/order form.\"}]","New-Software-Request-Form - Revised 9/2025 - Page 1 of 6 | PDF",1789852551]