Pregled

Ovaj ulaz opisuje studija slučaja opisuje stvarni MRO (Održavanje, Popravak i operacije) tijek proces odobravanja provodi u MAHOVINA.

To nije otvoreno tehničke rasprave, već služi za pružanje stvarnom svijetu primjer koji pokazuje kako MOSS platforma upoznao stvarne potrebe.

(Ovaj ulaz je pošta prijeći između http://paulgalvin.spaces.live.com i http://blogs.conchango.com)

Pozadina

Klijentovog MRO proces bio obilježen sljedeće

• Priručnik proces odobravanja.
• Neki podržavaju korištenje Excel proračunske tablice.
• Irregular approval process. The same MRO purchase approval process would vary day to day, Osoba prema osobi.
• Mnogo papiru i rukom pisane potpisa — kupnju obespravljivanja obvezne do 3 pisani potpisi prije konačnog odobrenja.

Ciljevi ovog projekta su:

• Potpuno automatizirati proces.
• Provođenje poslovne standarde za odobrenje.
• Osigurati konsolidirani pogled MRO kupovnu raznim menadžerima.
• Detailed audit trail.

As a side effect of the solution, pisani potpisi su više nisu potrebni.

Proces odobravanja

The approval process consists of four "swim lanes": Pokretač, Izravna manager, Funkcionalna manager i dijeljenje menadžer.

Pokretač:

Sees the need for the purchase and starts the process. Note that the originator may or may not actually enter the purchase requisition, but instead direct another staff member to do so. Neki puta, the originator does not have the technical expertise to fill out the PO requisition. Na primjer, Korisnik svibanj želite zahtjevnicama novi laptop računalo, , ali ne znam najbolji prodavač, IT standardima, itd.. U tom slučaju, the originator works with IT and IT actually fills out the requisition.

Izravna manager:

To je izravna menadžer inicijatora (koje može biti različito od osobe koja je zapravo ušao u PO rekvizicije u MOSS). Direct managers must approve the PO requisition before the system seeks approval further down the line.

Funkcionalna Manager:

The functional manager is the individual responsible for ensuring that the proposed purchase conforms to enterprise standards within the scope of a particular corporate function. Na primjer, IT purchases are approved by an IT functional manager.

Division Manager:

Division managers approve purchase requisitions strictly by dollar amount. Division manager approve purchase requisitions in excess of a configurable dollar amount.

Rješenje

We used the following tools and components to implement the solution:

MOSS: Serves as the platform off which everything else "hangs". MOSS provides bedrock services for security, master data, revizije staze i druge značajke.

InfoPath Forms Services: MOSS komponenta, to omogućava korisnicima da ispunite kupnju obespravljivanja putem web preglednika.

SharePoint Designer (SPD): Koristili smo SPD provesti automatski tijek procesa.

Web usluga: A c# web service enhances the user experience by enabling cascading selections lists in the InfoPath form and provides better performance with respect to filtering data. Vidjeti ovdje za tehničku dubokom zaronu na ovu temu i naše razloge za to koristi.

Prilagođeni popisi: MOSS user profiles provided a given user’s direct manager, but did not provide most of the data that controlled workflow decisions (e.g. Izdvojena li upravitelj dužan odobriti PO rekvizicije). We used custom lists in an "Enterprise Data" site to maintain data such as "Divisional Manager Approval Dollar Amount", "Functional Area Manager" and so forth. Lists integrated very nicely with InfoPath and also provide create/update/delete (CRUD) funkcionalnost i sigurnost revizije iz kutije.

Use Case

Ovaj slučaj pokazuje kako korištenje rješenje uklapa zajedno:

1. Paul wants a new laptop. He describes his needs to Vivek, IT osoba upoznat s korporativnim standardima laptop, povlaštene dobavljači, itd..
2. Vivek prijavljuje na MOSS, accesses the PO Requisition form and enters the requisition on behalf of Paul. The form prompts Vivek for a purchase category which then uses the web services to populate a drop-down list of company-approved vendors. Vivek also specifies the corporate functional area of this purchase (e.g. "IT" or "Finance").
3. SPD based rada počinje, Određuje Pavlov izravna menadžer i putevi rekvizicija za njegov menadžer, Stacy.
4. Stacy odobrava kupnju rekvizicije.
5. SPD workflow inspects the requisition and determines it’s an IT purchase. It routes the workflow to the IT functional manager, Wonson.
6. Wonson odobrava rekvizicije.
7. SPD tijeka ponovno pregledava rekvizicije i utvrdi da je iznos kupnje prelazi maxium dolar iznos te ga usmjerava na direktora sektora za odobrenje.
8. Podjela manager odobrava kupnju rekvizicije.

Bilješke

• The use case demonstrates a "clean" run with no rejections or jumps.
• Every approver has the ability to approve or reject the requisition as well as provide written comments. These are logged in the audit trail.
• Ako odgovorni menadžer odbacuje kupnju rekvizicije u bilo kojem trenutku, the PO requisition is "dead" and the process must be started from the beginning.
• Workflow obavještava začetnikom na svakom koraku.
• Pismena potpisa — Klijent određuje (nakon nekih silovitim preporuka) da je tijek revizije kako je propisano preko tijeka povijesti, služio njihov revizije treba.
• Napor — it took approximately three man weeks to implement this solution.

Zaključak

This solution leverages MOSS as a development and run-time platform. The client was able to leverage core MOSS features to automate a routine business process that affected nearly every employee in the company. With the exception of a simple web service (koja sama po sebi utjecati Moss), almost no actual "programming" bila potrebna.

The solution also serves as a "showcase" za klijenta, demonstrating how different MOSS features can be combined to create a fully featured business application and generate new consulting opportunities in the future.

Rječnik

MRO: Održavanje, repair and operations. These purchases typically include items such as notepads, stolice, osobna računala, pisači, mobitela i slično.