This can produce extended discussions on which fields areuseful and appropriate for users throughout the organization. PROJECT & OPERATIONAL MANAGEMENTcommon site classification typesEnterprise:A plan for enterprise sites has the highest level of governance associatedwith it. Taxonomy and the need for a consistent approach toorganization of information is necessary as well.Departmental:Departmental sites still have a large number of users even if the entireenterprise isnt dependant upon them. Sites with (PII) personally identifiableinformation should be appropriately flagged and secured and audited.9. Provide site owners with a speci c checklistof exactly what functionality you want them to check. One of the ways to combat this problem is to establish quotas forsites as they are created. SharePoint 2016 Visual Web Part Tutorial - SPGuides. There is the potential that for many different internal andexternal groups developing code for the SharePoint platform, having onerepository for all of code may not be the first choice. communicate to the CXOs that have a vested interest, Click icon to view map contentsClick label to view this node's details, as well as Enterprise sites tend to be focused on communication onthe dissemination of information and not so much on collaboration orworking together. The platform itselfmay largely be out-of-the-box functionality of SharePoint. information management policies such as content types with auditing What format the communications will be in? The BdcMetadata.XSD file can be locatedin the \Bin folder of the Office SharePoint Server 2007 installationdirectory, normally located at root \Program Files\Microsoft OfficeServer\12.0\Bin\.multiple bdc application definitionsWhen developing BDC Application definitions, the easiest approach tocreating the definition is to include all fields in the table, making themavailable for later use by anyone. In short, a taxonomy makes it easier to organize andfind things on a Web site.Taxonomic l Permanent Controlled; tightly governed Push information to users Dashboards, BusinessIntelligence, BPM Applications, Content Portaladministrators CorporatestakeholdersDivision Portals Permanent Controlled; tightly governed Push information to users All public sites - content isdivisional information Dashboards, BusinessIntelligence, BPM Applications, Content Portaladministrators Divisional businessownersDepartment, Group& Team Sites Permanent and Temporary Sharing information (push/pull) Collaboration Ad hoc, lax control Divisional businessowners Departmentalbusiness ownersProject Team Sitesand Workspaces Short lived, timed expiration Collaboration Ad hoc, lax control Departmentalbusiness ownersMy Sites Permanent Personal info Pull information Ad hoc, lax control Portaladministrators Employees. )sponsorshipEstablish a SharePoint Governance board to review adoption andcontrolsSolicit executive champions to create management attention to thevalue of the initiativeEncourage business evangelists to share power of SharePoint withother business leaders, PROJECT & OPERATIONAL MANAGEMENTroles and termsDene clear roles and responsibilities for the initiation of theSharePoint technologies platformsDene clear roles and responsibilities for the initiation of theSharePoint operationDene strategic teams to address strategy issuesEstablish cross-functional problem resolution to address complexissues which arisesite and platform classicationCreate classications by number of users and longevity (include):Create an Enterprise classicationCreate a Departmental classicationCreate a Team classicationCreate a Project classicationCreate a Personal classicationCreate classications by type of use (include):Create a portal for communications classicationCreate an application for tactical results classicationCreate a collaboration to facilitate team operations classicationservice level agreementsCreate a service level agreement around the length of time andapprovals necessary to create a siteEstablish service level agreements for problem resolution throughthe help deskNegotiate performance service level agreements for the rst loadof a site, subsequent loads of a site, and performance at remotelocations, DEVELOPMENT & CONFIGURATIONcustomization toolsDene what customization tools will be allowedCommunicate what actions will be allowed and not allowed in thetools (i.e. These pages often arecalled frequently and have a very low tolerance for a response time.Because of this the load balancers will need to be con gured to access ahealth page. ENTERPRISE SEARCHthe business data catalogThe Business Data Catalog provides the bdcMetadata.XSD le, an XMLSchema De nition File (XSD) that de nes the XML element mappingstructure necessary for creating an Application Denition le. Have a Governance and Information Management Plan. Time and cost management of the platformproject, communication of objectives, ensuring the production ofdeliverables, guiding the timelines, and management of expectations areall critical actions that should happen from a project management role(s).Service Owner:These roles are for managing the ongoing life of a centralized governanceand platform. Having specific governancearound departmental sites allows you to relax some standards forenterprise-type sites and create solutions which more directly fit thecollaborative needs of the depar, INFORMATION ARCHITECTURE Ensure understanding of what information architecture is and how it fits in with the Intranet strategy Ensure stakeholders understand why information architecture is critical Consider hiring an information architecture professional Build wireframes for 4-5 most popular pages (for, A107 Adam Street PROJECT & OPERATIONAL MANAGEMENTdefining rolesDefining roles within the governance team and within SharePointdeployment at large is a seemingly uncomplicated task that oftenbecomes difficult as staff rotates. Governance Checklist Guide nformation ArchitectureProject & Operational ManagementDevelopment & Configuration6-1667-89-10Infrastructure11Testing & Provisioning12Operational Concerns13Education & Training14Taxonomy & Navigation15Enterprise Search16Custom Checklist17Back-to-FrontTips & Information2-13Enterprise Search2Taxonomy & Navigation3Education & Training4Operational Concerns5Testing & Provisioning6Infrastructure7Development & ConfigurationProject & Operational ManagementInformation ArchitectureInformation Architecture Guide (graphic)Notes8-910-11121314-17, INFORMATION ARCHITECTURE Ensure understanding of what information architecture is and how itfits in with the Intranet strategy Ensure stakeholders understand why information architecture iscritical Consider hiring an information architecture professional Build wireframes for 4-5 most popular pages (for example, a Homepage, a Policies and Procedures page, a Department page, and aSearch Results page) Design simple sketches for each wireframe (links, content and fullfunctionality to be added later) Create a sitemap to plan the overall structure Create sitemap subsections for popular groups or departments,then build out lower-level sections, such as Project sites Build content types for structured departments, regions, or businesssite collections, Project & Operational Managementcommunication Establish a communications plan (include): Who will do communications plan? This is designed to prevent malicious sites from being run onthe server and to make it harder for any potential infection to report backon the infections success.load balancingLoad balancers keep alive pages that they expect to return a standardvalue to indicate that the server is operational. De ningwhat the monitoring policies are, including who will be noti ed whenthere is a problem with the server, or with an individual site will eliminateconfusion as to who owns the resolution of server problems includingproblems with speci c sites.disaster recovery and backupThe fundamental building block of disaster recovery plans are backups.Backups of the data, failover hardware, and redundant connectivity. Explaining what actions are expected out of these roles as wellas the frequency of commitment can be helpful.Operational Management:These roles are responsible for the day-to-day care and feeding ofthe system including backups and restores, monitoring, and capacitymanagement. Have a killer backup strategy that meets the needs of your business andmake sure it works before day one.4. However,integrating SharePoint into your environments, handing secure sign on,creating site definitions, and many other tasks may best be centralized sono one user must bear the burden and consistency exists throughout thesolution. which will inform users they are on the corporate Intranet. unghosting)site denitions and templatesEstablish guidelines for the development of site denitions andmechanisms for coordinating ID usageCommunicate policies for site template deployment, such as therequirements for a globally installed templatesource code and build controlDetermine if a central repository will be required for all codeinstalled on the platformEstablish standards for building components either on a centralizedserver or as guidelines for building softwareCommunicate expectations as to reference documentation(compiler generated) and warnings (whether they are allowed)on-going source code supportDescribe the responsibilities of business unit for ongoing codesupportdevelopment standardsConsider guidelines for which assemblies may be installed to theGlobal Assembly Cache (GAC) and which may notEstablish rules about the use of the AllowPartiallyTrustedCallers, DEVELOPMENT & CONFIGURATIONbrandingEstablish templates for what the SharePoint sites will look likeDetermine which types of sites may be modied and which may notDene which parts of the template may be changed by site owners,and which may notCreate and manage a master page gallery and create solutiondeployments packages to rollout if necessaryEnsure that your sites visual designer includes some sort ofbranding in all content creationRequire use of templates on higher level pages to enforce brandconsistencyRemember to allow room for sub-branding of individual teams orproject brands, INFRASTRUCTURErewallsConsider rules for outbound connections from the web servers foruse by the XML and RSS Viewer web partCommunicate rewall and security restrictions including any webpart restrictions such as ActiveX controls or external RSSrecovery, load balancing and failoverDecide upon and communicate the backup, clustering, loadbalancing and failover strategy and related service level agreementsenvironmentsDene the environments which will be used to develop and testsolutions in SharePointDescribe the actions which are expected and those which areprohibited in each environmentCommunicate policies for site template deployment such as therequirements for a globally installed template, TESTING & PROVISIONINGtestingPrior to launch, require content owners or editors to test their owncontentOffer a convenient mechanism for site owners to provide testingfeedbackCreate thorough test plans and let site owners know specicallywhat you want them to testprovisioningDetermine an approval process for information policies such asexpiration, compliance and auditingEstablish and document user policies and rights policies includingsecuring restricted areasPublish guidelines outlining appropriate application and contenttypesConsider forbidding condential data on your SharePoint site orlimiting it to specic site collections or web applications which aremore tightly controlled, audited, and managedClearly dene remote access policies to ensure security, OPERATIONAL CONCERNSmonitoring, uptime and downtimeEstablish monitoring at the server and web application levelDene responses to each type of failure that may occur; useMicrosoft Operations Manager Packs for applicable areas in thedeployment such as IIS, SQL, WSS 3.0, and SharePoint Server 2007Dene scheduled downtime periods if neededCommunicate the procedure to report unscheduled downtime orspecic performance issues (consider using another medium foroutage notication)Dene response procedures to unscheduled downtimedisaster recoveryPlan for single le recovery (perhaps using version control and therecycle bin)Plan for single or multiple site recoveryPlan for server recoveryPlan for data center recoverydata and document recoveryCodify corporate records management requirements into SharePointDene rules for archive of sites including warnings and approvalsquotas and reportingEstablish default storage quota templates by web applicationEstablish process for requesting a larger quota, including maximumquotasDene required auditing reports and establish storage usage reports,including how the data will be gathered and frequencyDevelop activity based reporting for administrators and businessusers, EDUCATION & TRAININGtraining budgetInclude realistic training costs as part of your earliest estimatesAllocate budget for IT staff, Development staff, and business users.Consider train the trainer and onsite training to reduce costsinitial trainingAcquire end user training and resourcesAcquire help desk training and resourcesAcquire administrator training and resourcesDevelop administrator policy guides which describe organizationspecic policiesAcquire developer training and resourcesDevelop developer policy guides which describe organization specicdevelopment policiesProvide separate training for site managers, application designers,information workers, and end userscommunity developmentCreate online forums where users can support each other and askquestionsCreate opportunities for face-to-face learning in unstructured orsemi-structured environments, such as lunch and learns or afterhours discussionsrenewal trainingPlan for renewal training which gathers the learning from multiplegroups and exposes it to other groupsPerform periodic audits of the platform to discover what features arenot being utilized and which features are not being utilized correctly, NAVIGATION & TAXONOMYtaxonomyGive one group control over the taxonomyConsider hiring or utilizing a professional taxonomist or in housetaxonomist who has been trained or has experience with SharePointtechnologyUse the taxonomy for consistent labeling of the siteBuild one set of taxonomy labels prior to nalizing your wireframesUpdate taxonomy to provide useful search metadatasite directoriesDene the structure of the site directories including the majorgroupings and associationsDevelop a linking strategy between different types of sites such asenterprise, divisional, departmental, team, etc.content typesDene core content types in the organization and include in sitetemplates or site denitionsDene key elds to link documents and operational systems, ENTERPRISE SEARCHsearchAssign workows for content creation so only the best information isavailable for search indexingIntegrate your taxonomy with search planningUse hit highlighting, best bets, and people searchIncorporate alternative content forms such as blogs and Wikis intoyour search resultsUtilize BDC functionality in SharePoint to enable search on customerrelationship management or partners, products and moresearch locationsEstablish content sources to the le based repositories in theorganizationUse the Business Data Catalog to allow searching of business datasearch relevancyDene who will be responsible for core relevancy settingsImplement organizational enhancements of the noise words le,thesaurus le, and keyword best bests, CUSTOM CHECKLISTadditional checklist itemsnotes, acronyms, denitions, and references, SharePoint GovernanceChecklist GuideTIPS & INFO. Leverage version history andversion control to maintain a history and master document that all canrefer to.7. This can produce extended discussions on which elds areuseful and appropriate for users throughout the organization. In fact, this phase should be carefully managed. Understandingand communicating the difference between site definitions and sitetemplates is important because site definitions require unique identifiersand therefore, coordination. It may bethat an organization decides to create multiple Application Denitionsto the same data structure, one perhaps complete with all elds and onerestrictive with limited eld access, then assigning speci c permissions onlyallowing company access to the more restrictive of the de nitions.using web parts to add application denitionsWeb Parts are the easiest way to surface data from new ApplicationDe nitions.
Lakeside Resort Lake Michigan, Yellow Jacket 95760 Rebuild Kit, Car 360 Degree Camera Installation Manual, Nike Fear Of God Triple Black, Mini Whiteboard Target, Backwash Hose Near Texas, Door Damper Adjustment, Bottles And Cans Recycling Near Me, Ultrasonic Toothbrush Vs Electric, Lucky Lotus Des Moines Delivery, Metallic Skirt Outfit, Chips Ahoy Ice Cream Near Me,
