Request For Proposal (RFP) Scope Development

At yesterday's management meeting you became the team leader for selecting and implementing an automated production line data collection and reporting system to support new KPI and OEE initiatives.

Now what?

If you were tasked with selecting and implementing new packaging equipment, no problem. That is very likely something you have done in your sleep.

But developing specifications and an RFP for specialized software and a vendor to support it? Where do you even start?

One very practical starting point includes ZPI Professional Services. We routinely help companies define their software project requirements and then develop a detailed User Requirement Specification (URS) that thoroughly addresses their requirements, their timeline and their budget.

Our packaging line analysis experts know what questions to ask and how to ask them. They can help with explaining all the industry jargon like "scalable" and "enterprise software" And most importantly, they know what you don't know, but definitely need to know.

Our packaging line analysis experts will help you build a solid foundation for your project that will ensure a successful implementation.

ZPI personnel are prepared to serve as embedded project team members, as team coaches or as team leaders. They can also develop the URS under the direction of the project leader.

For examples of what can be included in a requirements package please scroll down.

For more details about Monitor & Report professional services, please e-mail us at ZPI@ProMachBuilt.com.

Examples Of What Can Be Included In A URS
  • Functional RequirementsIncludes standard and custom reporting requirements, dashboard requirements, language requirements, etc.
  • Technical RequirementsIncludes a wide variety of infrastructure information including programming languages, system security, integration capabilities with enterprise software systems, etc.
  • System Access RequirementsIncludes identification of the types of devices and operating systems that can access the system, etc.
  • Data Collection RequirementsIncludes identification and definitions of customer specified and ZPI recommended data to be collected.
  • User Support RequirementsDefines how end users will be trained and supported during the implementation process and how they will be supported during post start-up use of the system.
  • Operational RequirementsIncludes identifying who will be using the system as well as where, how, when, and why to ensure effective performance for both site and corporate applications.
  • CostsIncludes detailed identification of all acquisition and installation costs as well as ongoing support and maintenance expenses.
  • Risk & Success FactorsIncludes prerequisites for successful project outcomes, effective ongoing use of the system and identification of avoidable issues that can lead to unsuccessful outcomes.
  • Data Transport RequirementsIncludes identifying required intersystem interfaces and data formats.