SharePoint & intranet
Anonymized client caseManufacturing Intranet Apps
A SharePoint 2013/Online and SQL Server intranet program for a North American food packaging manufacturer, improving product data, invoices, reporting, CRM readiness, sales tools, and multi-site collaboration.
Delivery evidence
What this example shows about delivery.
The evidence type is stated clearly so readers can distinguish anonymized client work from a reusable architecture practice or representative delivery example.
Anonymized client case
Foodservice packaging manufacturer with 11 US facilities
Outdated intranet and fragmented master data
Better reporting, product demos, invoices, and internal collaboration
Client Context
The client managed thousands of packaging product solutions across multiple facilities.
The source case describes one of the largest foodservice packaging companies in North America, with eleven facilities in the United States and a broad product portfolio.
As product categories and acquired businesses grew, the existing intranet and data landscape became harder for internal teams to use.
Challenge
The old intranet and fragmented master data limited reporting and daily work.
- The existing intranet was built on outdated .NET technology.
- Customer master, item master, and invoice histories were not fully integrated into the data warehouse.
- Sales and profitability metrics by item and customer were difficult for management to analyze.
- CRM could not be fully effective without complete customer, item, and invoice data.
- A previous third-party maintenance partner was not meeting delivery expectations.
Solution
A four-person Shinetech team built SharePoint-based applications around SQL Server data.
Shinetech worked with the client's project-management leaders to develop a SharePoint 2013/Online solution that processed SQL Server data for end users.
The work required precise collaboration between the client's onshore team, which explored business requirements, and Shinetech's offshore team, which built the technical solution.
Business Workflows
The intranet became a place for product, invoice, sales, and reporting work.
- Help staff find and manage consumer invoices quickly.
- Support financial transactions and daily operational work.
- Give sales teams better tools to demonstrate products and designs to clients.
- Improve reporting out of the data warehouse.
- Prepare the business for CRM improvement and future single-order or ERP integration.
Result
Internal teams gained a more useful operating layer across manufacturing sites.
The client's sales team used the new solutions to demonstrate products and designs more effectively. Internal teams could use the intranet with more confidence, improving processes and collaboration among manufacturing sites.
Shinetech continued providing maintenance while adding feature enhancements and functionality to the company's platforms.
Reusable lessons
What a similar engagement should clarify early.
- Map the business workflow and the roles that need different visibility.
- Confirm the data and access boundary before implementation.
- Choose a first release small enough to review and real enough to prove fit.
- Keep QA, documentation, handover, and ownership visible from the beginning.