Swt (System Wide Test) Efficiency

SWT (system Wide Test)

Efficiency of overall software through reports

Elapsed Time for report accrual and database analysis

Database query time and system analysis

Database Scrapping efficiency throughput analysis:

production integration (ERP)

Reliability of production plans

Inventory check and analysis

Engineering

Scheduling analysis scripting

Connectivity control with foreign allocators

External/Internal connectivity and integration (across customers)

Quality Control

Efficiency of Financial standard reports

Integration of costing with materials management cost and profitability generation

The major software functionality tested above states that the general behavior of the software primarily focuses on integration. A test plan will test the above metrics to show that there is both vertical and horizontal integration of the MRPS across the organization. The ultimate deliverable of this test is that reports are accrued that accurately depict the company's workflow and productivity in accordance with cost.

Timeline:

The actual timeline from conception and implementation to actual execution and support of our proposed MRP solution will be a long-term solution. The following time line provides a firm assessment of the steps necessary for a completion of the product life cycle within our business development orientation:

System performance analysis: 2 weeks

Executive review of implementation strategy and analysis: 1 week

Downtime configuration for current system: 1 week

Implementation of system: 4 weeks

Implementation of system (integration): 2-week

Implementation of system (test): 2-week

Integration of MRP with current system: 2 weeks

Training (it support): 3 weeks

Training (general employee): 3 weeks

Final system check and "Green Light": 3-week

End system performance analysis: 1 week

End executive review: 3-week

Implementation of this solution requires four specific agents, system analysts, project managers, it support and training, and executive committee. The project will be initialized by system analysts who explore the implication of their current system and the constraints provided by the new MRP solution. Project managers monitor the communication between the executive committee specifications and system analysts, while the it support division provides ongoing support, maintenance and training for the system. There are several constraints for this project, primarily, the MRP solution must be developed in parallel in the current system so that no downtime is experienced during implementation. Which means that a flawless transition between systems must take place, taxing all agents involved. Implementation time will be significant because the longer the implementation period, more costs will accrue for double usage of the ongoing MRP solution. However, careful implementation and training will allow for a smoother transition between systems, which will be crucial for operations. The training procedure will be two steps, first the it support staff then the general staff.

The recommended training program will be initiated by the commercial broker of the MRP solution. The majority of commercial software available provide both support and training as part of their provisional commercial package.