You are on page 1of 0

CONFIDENTIAL

Technical Proposal for Implementing


LogicApps EMI solution
Beverage Plant, Danfa
Submitted by:
Levergent Technologies
G.R. Mansion, Second Floor
4/11 Srinivasa Road, T.Nagar, Chennai 600017
Tel: +91 (44) 42605282
www.levergent.com
May 8, 2013
Technical proposal for LogicApps EMI Page ii
Document Control
Date Author Version Change Reference
2 August 2013 RaguramBalasubbu 1.0 Draft
Reviewers
Name Position
VenkatSankaran Principal
Distribution
Copy No. Name Location
1 Beverage Plant, Danfa Danfa
2 Library Levergent, India
Technical proposal for LogicApps EMI Page iii
Confidential Disclosure Agreement
Effective August 2, 2013, Levergent Technologies., and its subsidiaries worldwide
(hereinafter referred to as DISCLOSER), desires to disclose to Beverage Plant,
Danfa(hereinafter referred to as RECIPIENT)and its group of companies
worldwide, certain confidential information that is contained in this study
document. In receiving this document, RECIPIENT acknowledges that the
document and the information contained herein is Confidential Information and
agrees to the following restrictions:
RECIPIENT accepts this Confidential Information for the sole purpose of evaluating
the same for its own contemplated use and hereby agrees not to make use of
the disclosed Confidential Informationother than the purpose of evaluation, or to
disclose the same to any third party or parties without the written prior consent of
DISCLOSER. All such disclosures shall be in writing. RECIPIENT shall protect said
Confidential Information with the same degree of care as it applies to protect its
own.
It is recognized that RECIPIENT may be required to disclose such Confidential
Information to employees, for purposes of evaluation. RECIPIENT will exercise
reasonable care in the selection of such employees, and will fully advise all such
persons of the confidentiality of this Confidential Information and shall secure the
agreement of all such persons to comply with the terms and conditions of this
Agreement. The number of such employees will be limited to those who need to
know for said evaluation purposes.
If the period for evaluation has expired, or the RECIPIENT has notified DISCLOSER
in writing that it is no longer interested in continuing with the evaluation, or if
negotiations between the parties have commenced but DISCLOSER has notified
RECIPIENT in writing that in DISCLOSER sole discretion a satisfactory agreement
cannot be reached, then RECIPIENT will promptly communicate to DISCLOSER
within thirty (30) days.
The period of this Agreement is until five (5) years from either the termination of
evaluation or negotiations by RECIPIENT or DISCLOSER whichever occurs last, as
specified in Paragraph 3 above. All obligations of the RECIPIENT with respect to
the use and disclosure of Confidential Information hereunder shall termi nate at
the end of such five-year period.
The above constitutes the full and complete Agreement in this matter by and
between the parties hereto.
Technical proposal for LogicApps EMI Page iv
Contents
Confidential Disclosure Agreement ...................................................................................iii
1. Introduction ...............................................................................................................1
2. Beverage Bottling line Efficiency Challenges .....................................................2
2.1 Washing...............................................................................................................2
2.2 Filling.....................................................................................................................2
2.3 Quality Inspection..............................................................................................2
2.4 Labeling...............................................................................................................2
3. Enterprise Manufacturing Intelligence.................................................................4
3.1 Need for EMI Solution........................................................................................4
3.2 Footprint of EMI Software.................................................................................5
4. Solution Recommendations for Beverage Plant Danfa.................................6
4.1 LogicApps EMI Solution.....................................................................................6
4.1.1 Core LogicApps EMI solution....................................................................6
4.1.2 Add-on modules .........................................................................................7
4.1.3 Solution Architecture..................................................................................8
4.2 Beverage and Mineral Water Beverage Line ..............................................9
4.3 Other Core Processes .....................................................................................12
4.3.1 Syrup Room Operations...........................................................................12
4.3.2 Water Treatment Plant.............................................................................12
4.3.3 RO and Ozone Treatment Plant.............................................................12
4.3.4 Other Support Infrastructure ...................................................................13
5. Implementation and Deliverables ......................................................................14
5.1 Implementation Methodology .....................................................................14
5.1.1 Requirement Phase..................................................................................14
5.1.2 Installation and Configuration................................................................14
5.1.3 Monitoring and training phase...............................................................14
5.1.4 Training........................................................................................................15
5.1.5 User Acceptance Testing (UAT) .............................................................15
5.1.6 Go-Live........................................................................................................15
5.1.7 Change Requests .....................................................................................15
5.1.8 Post-Implementation Support Phase ....................................................15
5.1.9 Project Sign-off ..........................................................................................16
Technical proposal for LogicApps EMI Page v
5.2 Project Plan.......................................................................................................16
5.3 Deliverables ......................................................................................................16
5.4 Risk Management............................................................................................16
5.4.1 Requirements Gathering.........................................................................16
5.4.2 Adaptation of New System (Change Management) .......................16
5.4.3 Third Party Equipment procured by Beverage Plant, Danfa.........16
5.4.3.1 Server ....................................................................................................16
5.4.3.2 Operating System and Database Licenses ..................................17
5.4.3.3 LogicApps Hardware ........................................................................18
Technical proposal for LogicApps EMI Page 1 of 19
1. Introduction
This proposal is submitted to Beverage Plant, Danfa based on the
proposed plant layout received from customerLogicApps Enterprise
Manufacturing Intelligence (EMI) Solution to calculate the following:
Overall Equipment effectiveness Calculation
Monitoring of down time due to events from production
Integration of Plant data to Beverage Plant, Danfas ERP solution
This proposal presents selected features of LogicApps EMI to Beverage
Plant, Danfa business requirement for Beverage Hall.
We have identified and recommended critical areas where Beverage
Plant, Danfa can benefit from implementation of Levergents LogicApps
EMI solution.
Technical proposal for LogicApps EMI Page 2 of 19
2. Beverage Bottling line Efficiency Challenges
Companies in the Mineral Water and Juicebottling industry face
competitive pressures to increase productivity and improve efficiency.
Here are some of the industry-specific challenges faced by
beveragebottling companies:
2.1 Washing
Bottles need to be washed at correct temperature and
pressure.The wrong temperature may cause cracks to form in
bottle, or prevent bottles from getting clean and hygienic.
Operators need to be alerted when washing units are not
operating at proper temperature and pressure.
Bottles that have developed cracks in the washing process need
to be identified and removed.
2.2 Filling
Mixer in filling station needs to operate at the proper temperature
and pressure.
Product changeovers on a filling line need to happen following
proper procedures and under time pressure.
Bottle bursts need to be prevented or reduced. When glass
bottles burst during the filling process, there is a serious health risk
to consumers and employees. Dangerous glass splinters fly
around, which can hit employees and land in other bottles that
are intended for consumers.
When a bottle bursts during filling, bottles in vicinity of the burst
bottle have to be rejected because of chance that glass splinters
have landed in the bottles and contaminated the product.
Filling line has to be stopped after a bottle burst to clean the filling
line and remove glass splinters.
Employee may be injured if hit by glass splinters from an exploding
bottle.
2.3 Quality Inspection
After filling, it is critical that bottles containing foreign objects are
detected.
The failure to identify foreign object before the product hits the
market can threaten consumer safety, have a devastating effect
on the clients brand, and expose the Bottling companies to legal
liability.
2.4 Labeling
Bottles need to have the correct brand label. Mislabeling would
lead to the rejection of an otherwise good product.
Technical proposal for LogicApps EMI Page 3 of 19
Bottles need to have labels that are firmly affixed and centered on
the bottle. Poor labeling would lead to the rejection of an
otherwise good product.
Operators need to reduce time needed to change labels for
different production runs.
Liquids that have escaped from bottles may contaminate the
labeling machine.
It is critical to avoid making mistakes on the best-before label,
which could the lead to rejection of otherwise good product.
Technical proposal for LogicApps EMI Page 4 of 19
3. Enterprise Manufacturing Intelligence
Enterprise Manufacturing Intelligence (EMI) software brings a companys
manufacturing-related data from many sources for reporting, analysis,
displaying information, and passing data between ERP systems and plant-
floor systems.
3.1 Need for EMI Solution
Manufacturing companies in the breweries can benefit from an EMI
solution for the following reasons:
1. Reducing manufacturing costs
Breweriesneed to increase capacity on their lines without making
investments in new, expensive machinery. EMI software tools help you to
measure where lost machine time occurs, and understand where
available capacity can be unlocked.
2. Eliminate manual data entry and data collection processes
Brewerieshave trouble collecting accurate and timely production data,
such as production counts, rejection rates, reasons for rejections, and
equipment downtimes. Typically, production data is tracked manually
and entered into ERP systems at the end of shifts, or several days later. This
does not enable quick, real-time decision-making.
3. Improve communication between managers and breweries
When the planning team needs information about a production run, they
have to call down to the line and speak with an operator, who gets pulled
away from other duties. EMI software enables managers and planners to
get real-time information about bottling plant activities on their own
information dashboard.
4. Event-based vs. transactional-based manufacturing information
EMI software is event-based. It monitors business activities based on user-
defined rules. When the software detects data meeting prescribed
conditions, such as out-of-tolerance ranges, the software automatically
issues a response. Such responses can be e-mail or SMS alerts, audio or
visual alarms, or shutting down of machines or entire bottling line. EMI
software reduced the gap between bottling plant operations and ERP
software, which is transaction-based, not event-driven.
Technical proposal for LogicApps EMI Page 5 of 19
5. Measure process performance by implementing KPIs
Improvements in breweries can happen when you are measuring
meaningful performance measurements with accurate, real-time data.
EMI software enables breweries to accurately measure key performance
indicators (KPIs), such as rejection rates and O.E.E.
6. Reduce cycle times, increase throughput, and lower inventories
Production equipment on the bottling line will stop for short periods of time
for various reasons. These short downtimes, lasting only a few minutes,
often go unrecorded. EMI software can capture and measure these short
downtimes, so they can be tracked and managed.
3.2 Footprint of EMI Software
Enterprise Manufacturing Intelligence software gives real -time visibility to
the wealth of manufacturing information during production runs. EMI
software pulls data from multiple sources, including the machines on the
plant floor, so that planners and managers can understand what is
happening on the plant floor while the events are happening. In this way,
EMI software gives critical information for quicker and better decision
making.
Enterprise Manufacturing Intelligence tends to have the following
components:
Aggregation EMI software aggregates data from multiple
sources, including machine output, manually-
entered data, and other database applications.
Contextualization EMI software provides a structure or model to
help you organize, find, and understand your
data.
Analysis EMI software enables you to analyze data across
multiple sources so that you can make quick and
better decisions.
Visualization EMI software provides multiple tools for visualizing
your data and alerting decision maker to key
information that requires actions. This includes
information dashboards, visual factory displays,
and e-mail/SMS alerts.
Propagation EMI software ensures that data from the plant
floor is automatically transferred to enterprise
systems, like SYSPRO.
Technical proposal for LogicApps EMI Page 6 of 19
4. Solution Recommendations for Beverage Plant Danfa
From our observations on Layout received from beverage plant Danfa, Levergent believes that Beverage
Plant, Danfawould benefit from implementing the LogicApps Enterprise Management Intelligence solution.
LogicApps is a complete EMI solution built to ISA 95 standards and uses secure, encrypted wireless technology
for communications.
Please note that we have not conducted a full process analysis in this document. If we move forward with an
implementation of LogicApps EMI software, we would conduct a detailed requirements analysis of the
bottlingoperations and finalize the solution components (number of LogicApps devices and third party devices)
along with plant team.
4.1 LogicApps EMI Solution
LogicApps EMI is a real time plant monitoring solution that seamlessly connects all plant events to decision
makers and enterprise solutions. LogicApps EMI solution is built with predictive algorithms enabling pre event
notifications using plant performance models to productively notify plant decision makers to enable pre event
decisions.
4.1.1 Core LogicApps EMI solution
The core LogicApps Emi solution is a single integrated product from:
1. Production Scheduling: a Production sequencing module which LogicApps uses to monitor the real-time
plan Vs. actuals.
2. Production monitoring, process losses and process traceability: module use to real-time monitor line level
production, machine level production, and losses reason codes. This module also builds a digital travel card
that tracks various manufacturing conditions both in terms of quantity and quality parameters. This
functionality is also used in the beverage bottling process to build batch level process consistency.
3. Quality impact in production: Critical process parameters, first off inspection and periodic inspections are
monitored using this process. This is only a monitoring process as the data collected from this will be used to
analyze quality related process losses that affect overall efficiency of a bottling hall.
4. Plant maintenance impact in production: Critical maintenance parameters, preventive maintenance
stoppages, break down maintenance stoppages are recorded. This does not include integration into a
CMMS system or build reliability maintenance based solution
5. Integration to ERP using LogicApps EMI sync seamless enterprise connector to ERP solutions
Technical proposal for LogicApps EMI Page 7 of 19
The core product will meet the proposed business requirement of Beverage Plant, Danfa for monitoring bottling
hall performance efficiency. Core product is a single integrated product primarily focused on production
functionalities only.
4.1.2 Add-on modules
The implementation of add-on modules requires core product to be implemented as a mandatory pre-
requisite.
1. Plant quality for seamless integration with ERP and LIMS
2. Mobile plant quality for patrol inspection and seamless integration with ERP and LIMS
3. Plant maintenance including reliability center maintenance approach, meter based maintenance, etc.
4. Mobile plant maintenance for field crew with seamless integration to ERP
5. Costing Activity based costing
6. Enterprise Energy Management
7. Attendance System integration
Technical proposal for LogicApps EMI Page 8 of 19
4.1.3 Solution Architecture
Technical proposal for LogicApps EMI Page 9 of 19
4.2 Beverage and Mineral Water Beverage Line
The following chart shows how we can implement LogicApps EMI functionality for the PET bottle line:
Processes
LogicApps EMI Functionality
Aggregation Contextualization Analysis Visualization Propagation
Blow molding Bottle count: it does
not appear that the
blow molding machine
provides cycle count
data that can be
captured by LMC.
Running time /
Downtime: LMC should
be able to capture
running time and
downtime for the blow
molding machine.
Rejection counts: LMC
should be able to
capture rejection
counts from the
machine.
Productivity: bottle
counts would help
determine whether
bottle creation process
is hitting production
targets.
Plant Maintenance:
running time of blow
molding machine can
be monitored to
determine when to
schedule preventive
maintenance of
equipment.
Bottle count rates can
be compared against
production targets to
determine whether
blow molding process is
above or below shift
targets.
MAINTANANCE: Total
running time can be
monitored and
compared against
prev. maintenance
schedule.
Alerts can be triggered
if bottle count rates fall
below threshold
targets. Alerts can be
displayed on factory
displays and
dashboard screens, as
well as sent by e-mail
or SMS, allowing
corrective action to be
taken immediately.
When running time
approaches threshold
for prev. maintenance,
alerts can be triggered.
5S:Work instructions
can be displayed
during product
changeovers.
If required, bottle
counts can be passed
to ERP system and
associated with
production order.
EMI system can
communicate with ERP
to automatically
generate maintenance
orders for blow molding
equipment.
Technical proposal for LogicApps EMI Page 10 of 19
Processes
LogicApps EMI Functionality
Aggregation Contextualization Analysis Visualization Propagation
Filling LMCs can capture
following data from
filling machines:
Cycle counts
Running time /
downtime
Failure rate (e.g.,
burst bottles)
Pressure, temperature
of mix
Productivity: cycle
counts and downtime
of filling line will affect
OEE for equipment.
Quality: pressure and
temperature of mix will
affect quality of the
product.
Plant Maintenance:
running time of filling
line should be tracked
to determine when to
schedule preventive
maintenance of
equipment.
OEE of filling line can
be analyzed to
determine process
improvements.
Failure rates can be
analyzed to identify
issues in blow molding
and inspection stages.
QUALITY:Pressure and
temp. of mix should be
monitored to ensure
that they stay within
threshold ranges.
MAINTANANCE: Total
running time should be
monitored and
compared against
prev. maintenance
schedule.
OEE of filling line can
be displayed as part of
process improvement
measures.
E-mail or SMS alerts
can be triggered if
pressure ortemp.falls
outside of allowed
ranges.
Alerts can also be
triggered when filling
line uptime
approaches threshold
for prev. maintenance.
5S: Work instructions
can be displayed
during product
changeovers.
If required, OEE data
can be passed to ERP
system.
EMI system can
communicate with ERP
to automatically
generate maintenance
orders for filling line
equipment.
Quality check Reason codes:
although quality check
is manual process,
operator could use
keypad to enter reason
codes as bottles are
removed.
Rejection counts:
manual entry of reason
codes would also serve
as running count of
bottle rejections.
Rejection counts should
be subtracted from
filled bottle totals to
determine whether
overall bottle count is
sufficient for production
plan.
Rejection counts and
reason codes can be
compared against past
experience. Rejection
rate outside of normal
ranges may indicate
operator error.
Reason codes may be
analyzed to identify
issues in blow molding,
inspection, or filling
stages.
Rejection counts can
be used to adjust
displayed bottle counts
when tracking actual
vs. target counts during
a production run.
Alerts can be triggered
if rejection rates fall
outside a threshold
based on past
experience, so that
possible operator error
can be investigated.
If required, rejection
counts can be passed
to ERP system and
associated with
production order.
Technical proposal for LogicApps EMI Page 11 of 19
Processes
LogicApps EMI Functionality
Aggregation Contextualization Analysis Visualization Propagation
Cooling LogicApps LMCs can
capture temperature
data for each of the
cooling chambers.
Temperature data
affects product quality
in that it ensures that
cooling process is
executed correctly.
Temperature can be
monitored to ensure
that it stays within
proper ranges.
Alerts can be issued on
visual displays and sent
by e-mail or SMS if
temp.falls outside of
threshold ranges.
Packing Production
counts:packing is an
automatic process,
which would allow us
to capture production
counts.
Production counts can
be compared against
target goals for the
shift.
Production rate can be
analyzed to determine
whether production run
is on target.
Actual vs. target counts
for final product can
be displayed on plant
floor to increase
productivity.
Plant operations made
visible to planners and
managers by giving
access to production
rates in real time.
Alerts can be issued if
production rates fall
behind target rates.
Production counts are
passed to ERP systems
and associated with
production order.
Technical proposal for LogicApps EMI Page 12 of 19
4.3 Other Core Processes
4.3.1 Syrup Room Operations
LogicApps EMI is a comprehensive solution that could also do real-time
integration and tracking of all areas of Syrup room operations like:
Concentration level of dosage tank
Pressure level of dosage tank
Temperature level of dosage tank
Flow rate of Syrup
Flow rate of CO2
Flow rate of water & Line feeds
Real time process monitoring and control of entire Brewing process
including:
Cleaning and Sanitizing Tracking and documentation of both
cleaning and sanitation process.
HACCP Documentation - Documentation of Hazard analysis and
critical control points
4.3.2 Water Treatment Plant
LogicApps EMI Solution can be used to aggregate data from equipment
in your water treatment plant, including:
Carbon towers
Softeners
Filtration systems
Deionization systems
Disinfection systems (chemical injection, UV disinfection, ozone)
Degasification systems
Our LogicApps EMI Solutioncan aggregate data from equipment in the
water treatment plant, enabling MAINTANANCE initiatives and giving
visibility to real-time operations of the water treatment operations.
4.3.3 RO and Ozone Treatment Plant
LogicApps EMI solution can be used to aggregate data from the RO and
Ozone treatments equipment to capture the following quality parameters.
PH & TDS Parameter Measurement
Ozone Level
Technical proposal for LogicApps EMI Page 13 of 19
4.3.4 Other Support Infrastructure
LogicApps EMI Solution can also be used to manage other support
equipment, including:
Generators
Compressors
Pumps
Technical proposal for LogicApps EMI Page 14 of 19
5. Implementation and Deliverables
5.1 Implementation Methodology
Our implementation methodology includes the following phases:
5.1.1 Requirement Phase
The requirement phase involves the product standard functionality
walkthrough based on the mentioned functionalities in the proposal
document. Based on the product standard functionalities we will be
collecting additional user requirements to serve the business purpose. The
requirements will be recorded and documented. The scope of the project
will be determined and will be getting requirements sign off from the user.
5.1.2 Installation and Configuration
The application and the database will be installed in the server
and the server will be commissioned at the plant.
Once the server commissioning is over, the application
standard functionalities will be deployed in the server.
Then the master data collection from the user and data
validation will take place. Once finished with validation, the
data is loaded in the system.
Delivery of the finalized LogicApps solution components and
commissioning of the same.
Connection of LMCs to the input source and verification of
signal transmission from the input source to LMCs.
Configuration of network and hardware devices with software
application.
Testing the data transmission from source to destination and
ensuring for data accuracy
Configuration of SMS/e-mail messaging based on customer
requirements.
Configuration of reports and dashboards in the application
and ensuring data accuracy.
5.1.3 Monitoring and training phase
The monitoring phase involves the monitoring of the data collectively for
commissioned lines. The monitoring phase will happen for 10 working days
which includes application, devices verifications, report verifications,
dashboards, email and SMS alerts.
Simultaneously the training will be given to users on the functionalities and
usage of the system. The SOPs and user manuals will be delivered to the
users.
Technical proposal for LogicApps EMI Page 15 of 19
5.1.4 Training
Extensive training for the Plant Floor Operators and Supervisors
for their usage of the solution (LogicApps EMI)
Operators: Operators will be educated, how to operate the
LMC and other required devices to enter the Program Number,
line down reason and how to start and stop the shift.
Engineers and Managers: All users will be trained on how to
monitor the dashboards, reports and how to configure the
system.
LogicApps Product Administrator: System Administrator will be
trained how to add users, define roles for a user, assigning
reports to the user. System Administrator will be trained how to
configure the SMS alert, automatic email reports for users and
diagnosing the network.
The training will be conducted for 10 working days with the user
in the LIVE environment.
5.1.5 User Acceptance Testing (UAT)
In this phase, we conduct sessions with users on the delivered
functionalities for conformance as desired by the users and find out any
mismatches and rectify the same. All parameters configured are checked
for their authenticity and correctness. Users at different levels are also
consulted for their acceptance on the functionalities and usage of the
system functionalities and their ease of use. We will get the approval on
the functionalities delivered and get a UAT sign-off from the user.
5.1.6 Go-Live
Once the User Acceptance Testing (UAT) phase is completed, the system
will go LIVE from the date suggested by the user. This phase includes the
usage of the system by the end users as defined in the user manuals and
SOPs. We will be providing assistance to the users on using the system
effectively.
5.1.7 Change Requests
The changes on the functionalities (if any) will be received from the user
and it will be recorded. The functionalities will be analyzed with the
defined scope and recorded as change requests. If any functionality is
found out of scope (sec 4.1.1), it will be considered as scope extension.
The change requests will have impact on the timeline and cost of the
project.
5.1.8 Post-Implementation Support Phase
On-site consultants will remain onsite for a period of defined
period to ensure that customer is utilizing the LogicApps EMI
solution to its full potential and have realized business gains
from the LogicApps EMI implementation. The post
implementation support will be for 2 weeks.
Technical proposal for LogicApps EMI Page 16 of 19
5.1.9 Project Sign-off
On the successful completion of the post-implementation,
which includes the delivery of accepted change requests and
full customer satisfaction, Levergent will proceed with customer
sign-off on the project. Levergent will continue to provide
product support as per the terms of customers support
agreement. (ref. commercial proposal)
5.2 Project Plan
The detailed project plan will be submitted after the award of the
contract.
5.3 Deliverables
Implementation Plan
Product user manuals and SOPs
All the agreed functionalities(software and hardware)
5.4 Risk Management
The following are the expected risks during implementation of the
LogicApps EMI solution:
5.4.1 Requirements Gathering
Risk: Ensuring that LogicApps EMI Management Software is
configured to meet your requirements.
Mitigation: Levergent asks you to provide a Project Coordinator to
help the implementation team in understanding the requirements
and to appraise the team about specific issues and problems.
5.4.2 Adaptation of New System (Change Management)
Risk:Beverage Plant, Danfa stakeholders and users may have
trouble adapting the new system.
Mitigation: Levergent will provide comprehensive training on using
the various features of the system. Beverage Plant, Danfa is asked
to assist in this effort by communicating the advantages of the
system to their users.
5.4.3 Third Party Equipment procured by Beverage
Plant, Danfa
Beverage Plant, Danfa will be required to purchase the following items,
which are not included as part of the LogicApps EMI solution:
5.4.3.1 Server
We recommend that Beverage Plant, Danfarun the LogicApps
Management Software on a dedicated server. A server with the following
or similar specifications should be used:
Dell Power Edge R410 Rack-Mount Server with Intel Xeon X3430 Processor
(2.4GHz, 8M Cache, Turbo), 8GB memory, 2 hard drives (450 GB, 15K RPM,
6Gbps SAS 3.5 hot pluggable).
Technical proposal for LogicApps EMI Page 17 of 19
5.4.3.2 Operating System and Database Licenses
The following Microsoft licenses will be required to run the LogicApps
Management Software:
Item Qty.
Microsoft Windows Server 2008 Std Ed Server License 1
Microsoft Windows Server 2008 Std Ed Client Access License TBD
Microsoft SQL Server 2008 Std Ed Server License 1
Microsoft SQL Server 2008 Std Ed Client Access License TBD
The quantity of client access licenses required is determined by the
number of users who will access the LogicApps EMI Management
Software.
Technical proposal for LogicApps EMI Page 18 of 19
5.4.3.3 LogicApps Hardware
S.No Line No Stage Required
Hardware
QTY
1 Beverage Line Blow Molder LMC, Sensor 1
2 Filler & Light Check LMC, Sensor,
Machine Interface
2
3 Adhesive Labeller& Ink-Jet
Coder
LMC, Sensor,
Coder Interface
1
4 Shrink Rap and Final Packing LMC, Sensor 1
5 Carbon Towers &Softners LMC, Sensor 1
6 Filteration unit LMC, Sensor 1
7 RO & Ozone Treatment LMC, Sensor 1
8 Mixing Tank & Agitator LMC, Sensor 1
9 Mineral Water
Beverage Line
Blow Molder LMC,Sensor 1
10 Filler & Light Check LMC, Sensor,
Machine Interface
2
11 Adhesive Labeller& Ink-Jet
Coder
LMC, Sensor 1
12 Shrink Rap and Final Packing LMC, Sensor 1
13 Carbon Towers &Softners LMC, Sensor 1
14 Filteration unit LMC, Sensor 1
15 RO & Ozone Treatment LMC, Sensor 1
16 Mixing Tank & Agitator LMC, Sensor 1
17 Fruit Juice Carbon
Machine Line
UHT LMC 1
18 Filler LMC 1
19 Ink-Jet Decoder & Shrink Rap LMC 1
20 Carbon Towers &Softners LMC, Sensor 1
21 Filteration unit LMC, Sensor 1
22 RO & Ozone Treatment LMC, Sensor 1
23 Mixing Tank & Agitator LMC, Sensor 1
24 Quality Check Quality Parameters PDA 2 Nos