Making critical policies easier to govern, find, and apply
PLN Indonesia Power, a subsidiary of PT PLN (Persero), is Southeast Asia’s largest power generation company, with a total capacity of 21.08 GW. Established in 1995, the company plays a central role in Indonesia’s energy sector, where reliable operations depend on clear standards, disciplined processes, and timely decisions.
Policy documents support that operating model. They define responsibilities, explain procedures, establish controls, and help employees work consistently across a large organization. But policy information creates value only when people can find the right document, understand its meaning, and trust that it is current.
PLN Indonesia Power already manages policy documents within its SharePoint-based Knowledge Center. However, the system no longer provided the search, classification, workflow, and usability needed by a growing organization. Suitmedia helped develop a new Policy module within the existing platform, creating a more structured way to submit, review, approve, search, classify, and access both public and confidential policies.
A document repository had become an operational bottleneck
1. Policies were more than files in a library
In a power generation company, policies influence safety, compliance, procurement, operations, risk management, and decision-making. They are part of how the organization works, not simply documents stored for reference.
That makes policy management more demanding than file storage. Employees need to know which version is valid, who approved it, where it applies, and how to interpret important terms.
The previous Knowledge Center provided a foundation, but its policy capabilities were not sufficiently advanced for the organization’s evolving needs. PLN Indonesia Power needed a system that managed the policy lifecycle, not just the policy file.
2. Employees were spending too much time looking for answers
Users might know the topic of a policy without knowing its exact title. They may search by department, process, keyword, or a phrase used in daily work.
If the system relies on exact document names or rigid navigation, employees must guess how the organization labeled the policy. That creates delays and increases the chance that they rely on older versions, informal explanations, or documents stored elsewhere.
The business impact is significant. Every minute spent searching for the right policy is time not spent on the operational decision itself.
3. The policy lifecycle was not visible enough
A policy usually passes through submission, review, approval, publication, and future revision. When those stages are handled through separate emails, folders, or manual follow-ups, status becomes difficult to track.
Reviewers may not know which documents require attention. Administrators may not know whether a policy is waiting for approval or has already been released. Employees may not know whether the version they found is official.
PLN Indonesia Power needed a clearer process that made document status and responsibility visible.
4. Public and confidential policies required different treatment
Not every policy should be available to every user. Some documents can be shared broadly, while others contain information that should be restricted by role or organizational need.
This created a dual requirement: make approved policies easy to find for authorized users while protecting confidential information from unnecessary exposure.
The solution had to integrate access control into the user experience. Security could not be treated as a separate technical layer that made ordinary document access unnecessarily difficult.
5. A growing library needed stronger organization
As the number of policies increases, a flat document list becomes harder to manage. Users need categories, topics, and consistent classifications to browse and filter the collection.
Without a clear taxonomy, search has to carry too much of the workload. That makes the system less useful when users do not know the exact terms used in a document.
A stronger classification structure would help both sides of the process. Administrators could manage the library consistently, while employees could approach policies through subjects that made sense to them.
6. Policy terminology could lead to inconsistent interpretation
Policies often contain specialized language, internal abbreviations, and formal definitions. Different teams may interpret the same term differently when no shared reference exists.
This can weaken consistency across locations and functions. A glossary linked to relevant policies could give employees a common explanation without forcing them to search through separate reference materials.
The objective was not to simplify policy language beyond accuracy. It was to make important terms easier to understand in context.
7. The existing system limited future improvement
The SharePoint-based Knowledge Center did not offer all the advanced features and modern technology required by PLN Indonesia Power’s future needs.
A short-term visual update would not be enough if the platform remained difficult to extend. The company needed a stronger foundation for search, workflows, classification, content management, and future integration.
This made the project a capability upgrade. The new module had to improve today’s work while creating room for tomorrow’s requirements.
8. Administrative effort was being repeated unnecessarily
When users cannot find documents easily, they ask colleagues or administrators for help. When approval status is unclear, staff send follow-up messages. When categories are inconsistent, administrators spend time reorganizing information.
These inefficiencies may appear small, but they accumulate across a large organization.
The Policy module needed to reduce searching, repeated communication, manual categorization, and uncertainty. Its purpose was to return time to employees and administrators while strengthening control.
Designing one connected workflow for policy creation and use
1. Start with the people who manage and consume policies
Suitmedia began with UI/UX design focused on the needs of different policy users.
Authors and administrators needed to submit and organize documents. Reviewers and approvers needed to assess them. Employees needed to search, view, understand, and download approved policies.
Mapping these responsibilities helped create a role-appropriate experience. Users could see the actions relevant to them without facing a long list of functions designed for someone else.
2. Integrate the module into the Knowledge Center
The new Policy module was developed within PLN Indonesia Power’s existing Knowledge Center rather than as a disconnected platform.
This preserved a familiar entry point for users and reduced duplication in the broader knowledge management environment.
Integration also strengthened continuity. Employees could access policy information through an institutional system they already recognized, while benefiting from a more capable and focused module.
3. Create a structured submission process
The module allowed authorized users to submit policy documents through a defined workflow.
A structured submission process ensured that each document entered the system with the information needed for review, classification, ownership, and future retrieval.
This improved quality at the start of the lifecycle. A document that is submitted consistently is easier to manage throughout review, approval, publication, and revision.
4. Keep review and approval in the same workflow
The platform supported document review and approval within one connected process.
This made it easier to see what had been submitted, which documents required action, and where each policy stood. It also reduced dependence on separate email chains and manually maintained status records.
Keeping the process together strengthened accountability. The organization could build a clearer history of how a policy moved from draft to approved document.
5. Make approved policies easy to view and download
Most employees use the system to find and apply policies, not to manage them. Their experience needed to be direct and reliable.
Users could search for a policy, view its content, and download it when necessary. This reduced the effort required to access official information and helped employees work from the correct version.
The result connected usability with compliance. Employees are more likely to follow the right standard when it is easy to find and understand.
6. Improve search with Elastic Search
Suitmedia integrated Elastic Search to provide faster and more flexible policy discovery.
Users could search with relevant terms without knowing the exact title of a document. This reflected how employees actually look for information: through subjects, processes, keywords, and everyday language.
The solution was implemented without paid plugins, supporting cost efficiency while still delivering a high-performance search experience.
7. Organize the library through categories and taxonomy
The module included category and taxonomy management to give the policy library a clearer structure.
This supported browsing and filtering, especially for users who were unsure what search term to enter. It also helped administrators maintain consistency as new documents were added.
Taxonomy became a form of organizational memory. It made the growing collection easier to understand and reduced the likelihood that important policies would become buried.
8. Link glossary terms to relevant policies
Glossary management allowed specific terms to be connected to the policies where they mattered.
This helped employees understand specialized language without leaving the document or searching elsewhere. Definitions became available at the point of need.
A shared glossary also supported consistency across teams. Employees could refer to the same explanations when applying policies in different operational contexts.
9. Support different access levels
The system was designed to manage both public and confidential policies.
This meant access could be aligned with the user’s role and the document’s sensitivity. Authorized users could work efficiently, while restricted information remained protected.
The balance was important. A secure platform should not force users to navigate unnecessary complexity, but it must prevent inappropriate access.
10. Build a modern and scalable technical foundation
The frontend and backend were developed using modern technologies that supported performance, maintainability, and future expansion.
This gave PLN Indonesia Power more than a redesigned interface. It created a system that could evolve as policy requirements, categories, workflows, and user expectations changed.
The technology served the organization’s operating model. It was selected to reduce present inefficiencies and avoid recreating them later.
11. Test the complete document lifecycle
Testing covered the major user journeys, including uploading, reviewing, approving, viewing, downloading, searching, and managing categories and glossaries.
This ensured that individual features worked together as one system. A document management platform can appear functional screen by screen but still fail when users move through the full lifecycle.
Testing helped identify friction before it affected broader adoption.
12. Plan for post-launch improvement
The project included post-launch support and monitoring.
This allowed PLN Indonesia Power and Suitmedia to respond to user feedback, refine workflows, and update the system as new requirements emerged.
This was essential because policy management needs often become clearer after real users begin working with the platform. Continuous improvement protected the value of the initial investment.
13. Design for organizational scale
PLN Indonesia Power manages a large and complex operation. The Policy module needed to support many documents, users, categories, and access requirements.
Scalability was therefore a starting requirement, not a future enhancement. The platform had to remain useful as the policy library grew and more teams depended on it.
A scalable structure protects usability and performance over time.
A more productive system for policy access and control
1. Policy management became more streamlined
The new module allowed users to upload, review, view, and download policy documents through a more coherent process.
This reduced the number of separate tools and manual steps involved in policy administration.
PLN Indonesia Power gained a more dependable operating foundation for managing policy knowledge.
2. Employees found official information more easily
Improved search, categories, and taxonomy reduced the effort required to locate relevant documents.
Employees could approach the library through keywords, topics, or classifications instead of relying only on exact titles.
This made the Knowledge Center more useful for daily work and reduced dependence on informal document sharing.
3. Review and approval became easier to monitor
A connected workflow made it clearer which policies were submitted, under review, awaiting approval, or ready for access.
This reduced the need for repeated status checks and improved accountability among reviewers and approvers.
The organization gained a more reliable view of the policy pipeline.
4. Glossaries helped reduce ambiguity
Linked definitions made specialized policy language easier to interpret.
This supported more consistent application of policies across teams and locations, reducing the likelihood that important terms would be understood differently.
The glossary also made the system more educational for employees who were less familiar with internal terminology.
5. Categories created a foundation for long-term organization
Taxonomy and category management helped PLN Indonesia Power maintain order as the policy library expanded.
A well-structured collection is easier to search, manage, and govern. The benefit becomes more visible over time, as every new document has a clearer place in the system.
6. The CMS improved administrative ownership
The content management system gave authorized users a more manageable way to oversee documents, classifications, and glossary information.
This reduced reliance on technical teams for routine updates and improved the speed of policy administration.
Internal teams gained greater control over the quality and relevance of the library.
7. Productivity improved through reduced manual handling
Employees spent less time searching for documents, while administrators spent less time managing disconnected records and follow-ups.
The combined improvement streamlined document handling and created more capacity for work requiring judgment.
The result was not simply a faster system. It was a more efficient way of managing organizational knowledge.
8. Security and accessibility were better balanced
The platform made approved policies easier to access while supporting appropriate handling of confidential documents.
This helped PLN Indonesia Power strengthen information control without making the system unusable for authorized employees.
The balance supported both operational effectiveness and institutional responsibility.
9. The platform adapted to future needs
PLN Indonesia Power reported that the technology was appropriate for current requirements and adaptable for future needs.
This was a significant outcome because policy management systems often need to change as governance requirements, organizational structures, and document volumes evolve.
The new foundation gave the organization room to improve without returning to the limitations of the previous system.
10. The Knowledge Center became more valuable as a business resource
The Policy module strengthened the Knowledge Center’s role as a source of operational guidance.
Employees could access policies more easily, administrators could manage them more consistently, and leaders could rely on a more structured process for governance.
The system helped transform documents into usable organizational knowledge.
11. PLN Indonesia Power recognized the quality of delivery
The client highlighted Suitmedia’s responsiveness, professionalism, documentation, and reliable post-launch support.
PLN Indonesia Power also described the CMS as user-friendly and the overall system as a significant productivity improvement.
This feedback demonstrates that enterprise technology projects depend on both the delivered platform and the quality of collaboration surrounding it.
The deeper lesson: document systems should reduce uncertainty, not simply store information
1. Storage creates little value without findability
A repository can contain every required document and still fail if employees cannot locate the right one.
Search, taxonomy, categories, and clear presentation are what turn storage into useful access.
2. Policy governance should be part of everyday work
Submission, review, approval, publication, and access should happen within a connected workflow.
When governance is built into the system, it becomes less dependent on memory, informal follow-up, or manual reconstruction.
3. Search is a control mechanism
If employees cannot find the official policy, they may use an outdated or unofficial version.
A flexible search experience supports compliance by making the correct information easier to reach.
4. Definitions improve consistency across a large organization
Specialized language can create different interpretations across departments.
A shared glossary linked to policies helps employees apply the same terms in the same way, strengthening operational consistency.
5. Classification protects the system from future overload
Taxonomy and categories require effort, but they prevent a growing collection from becoming unmanageable.
The earlier an organization creates structure, the less expensive it is to maintain findability later.
6. Access control must support legitimate work
Security should protect confidential information without forcing authorized users through unnecessary obstacles.
Clear roles, permissions, and document handling rules create a better balance between protection and productivity.
7. Technology should be selected for adaptability
A system that solves today’s problem but cannot accommodate tomorrow’s workflow creates another form of technical debt.
Modern, scalable architecture gives the organization more options as its policy environment changes.
8. Post-launch stewardship is part of the solution
Users will reveal new needs once the system becomes part of daily work.
Monitoring, documentation, support, and iterative improvements help ensure that the platform continues to deliver value beyond launch.
Strategic Insights for the C-Suite
- Treat policy management as a productivity and governance capability. The value is not in storing documents, but in helping employees find, understand, and apply the correct policy quickly.
- Build the full policy lifecycle into one workflow. Submission, review, approval, publication, search, and revision should be connected. Fragmentation creates delay and weakens accountability.
- Invest early in findability and classification. Search, taxonomy, categories, and glossaries prevent growing document libraries from becoming operational bottlenecks.
- Balance security with usability. Public and confidential policies can coexist when access rules are clear and role-based. Protect sensitive information without making legitimate work difficult.
- Plan for continuous improvement from the start. Enterprise knowledge systems evolve with the organization. Post-launch support, internal ownership, and adaptable technology preserve long-term value.
