tieBridge Success, independently verified
About Services Project Delivery Assurance™ Case Studies Insights Team Careers Start a conversation
← All case studies

Public Power Utility — the 3rd largest in the U.S.

From Scattered Content to a Single System of Record

Client

Long Island Power Authority (LIPA)

Engagement

End-to-end EDRM/ECM delivery, requirements through phased implementation

Our role

Owner's Advisor & Implementation Lead

9

Engagement roles, from requirements development through implementation management

~280

Functional and non-functional requirements authored across seven domains

1

Governed repository for both living documents and final records

3

Deployment waves phasing the rollout, records and compliance first

Overview

The Long Island Power Authority (LIPA), the third-largest public power utility in the United States, set out to strengthen how it manages its documents and records. The effort grew from a records-management initiative led by the General Counsel to improve legal and regulatory compliance — at a time when document-management practices across the organization were non-standardized and inefficient. LIPA engaged tieBridge to lead the effort end to end: to define what the new system had to do, procure both the software and an implementation partner, negotiate the contracts, and manage a phased, multi-year rollout. In effect, tieBridge served as LIPA's owner's-side advisor and implementation lead — from the first requirement through deployment.

The challenge

LIPA faced a compliance-driven modernization with a strategic decision at its core:

  • Records management needed to be strengthened for legal and regulatory compliance — a priority set by the General Counsel — while document-management practices across the organization were non-standardized and non-optimized.
  • A foundational question had to be settled first: implement records management alone, or an integrated document-and-records (EDRM/ECM) platform? A siloed records system risked weak adoption and "shadow" copies of records persisting in local, ad-hoc systems — discoverable long after the official copies had been disposed of.
  • LIPA needed a rigorous, defensible procurement to select both a software product and an implementation partner, with requirements specific enough to compare specialist vendors fairly.
  • The system had to serve very different departmental needs — some using it only as a repository for final records, others for full document lifecycle management — without imposing redundant data entry.
  • A multi-year, enterprise-wide rollout had to be sequenced to deliver records and compliance value first, and to generate benchmarks for later phases — all without disrupting the business.

Our role across the engagement lifecycle

tieBridge's role spanned the full lifecycle — continuity that carried the same context from the first strategic decision through to a working, governed system:

  • Scope definition & requirements development — resolved the foundational scope question in favor of an integrated EDRM/ECM approach, then authored roughly 280 functional and non-functional requirements across seven domains (records management, repository, organization and retrieval, document management and workflow, system, usability, and technical), each structured for a formal compliance response.
  • Competitive landscape assessment — evaluated the market of enterprise content and records-management product and implementation vendors.
  • Qualified bidder identification — developed a slate of potential qualified bidders.
  • Procurement orchestration — organized and ran the RFP end to end, structured to select both a software product and implementation services.
  • Proposal evaluation — evaluated the responses received against the requirements.
  • Solution-demonstration guidance — developed detailed guidance for each proposer's solution demonstration, so vendors were compared on real capability rather than sales polish.
  • Vendor recommendation — delivered recommendations for both the product and the implementation partner.
  • Contract negotiation — led negotiation of the resulting contract terms.
  • Implementation management — project-managed the phased, multi-wave implementation on LIPA's behalf, including issue management, scope clarification, and task-order planning.

Deciding what to buy before deciding how to buy it

The most consequential work happened before the RFP. LIPA's need began with records management and compliance, but tieBridge pressed a prior question: should the utility buy a records system, or an integrated document-and-records platform? A records-only silo, the team showed, would struggle for adoption and leave "shadow" copies of records scattered across local systems — discoverable even after official copies were disposed of. tieBridge framed the trade-offs and steered LIPA to an integrated EDRM/ECM repository, phased to prioritize records and compliance first — shaping what was bought, not just how.

One repository, many departments

The requirements had to hold a deliberate tension: a single governed repository that some departments would use only for final records, and others for full document lifecycle management — creation, versioning, workflow, retention, and disposition. tieBridge specified a system that flexes to each department's needs from one source of truth, without forcing redundant data entry — so compliance and day-to-day productivity were served by the same platform rather than competing ones.

Delivering in waves

tieBridge's mandate ran past selection and into delivery. Having defined the requirements, run the procurement, and negotiated the contracts, the team project-managed a phased, multi-wave rollout on LIPA's behalf — sequencing enterprise records management and a small set of pilot departments first, so the earliest waves delivered compliance value and produced benchmarks that de-risked the ones that followed. Managing issues and scope clarifications along the way kept what was delivered aligned with what was specified.

Impact

  • Resolved a foundational strategy question early — an integrated document-and-records repository rather than a records-only silo — steering LIPA away from an approach that risked weak adoption and undiscoverable shadow copies.
  • Gave LIPA a rigorous requirements foundation of roughly 280 functional and non-functional requirements across seven domains, anchoring both the procurement and the implementation.
  • Ran a disciplined, defensible procurement that selected both an enterprise content management product and an implementation partner, evaluated against a single standard with structured solution demonstrations.
  • Delivered a single, governed repository for both living documents and final records — strengthening records management for legal and regulatory compliance while improving everyday document lifecycle management.
  • Structured a phased, multi-wave rollout that delivered records and compliance value first and produced benchmarks to de-risk later waves.
  • Provided one continuous line of owner's-side expertise from requirements through contract negotiation and implementation — closing the handoffs that fragment large system projects.

Facing a similar challenge?

Start a conversation