How is the asset management system construction programme prepared? Structures and elements
RFID Knowledge

How is the asset management system construction programme prepared? Structures and elements

PublishedShanghai Zejie Smart Technology Co., Ltd.

A land-based asset management system construction programme has three central elements: to tell the status quo, to run business processes and to break down the implementation rhythm. The structure typically contains seven blocks of situation diagnosis, needs analysis, architecture design, functional planning, implementation pathways, risk control and investment measurement, each supported by specific data and not general terms.

Element 1: Status diagnosis to be available in numbers and scenes

The first step in writing the program is not to introduce system functionality, but to clarify "what exactly hurts the assets currently under management." It is suggested that we look at three dimensions:

After that, we're going to publish a report on the status of asset management, and we're going to prioritize the problem by "emergency" and "impact." This step is the basis for all the next designs, without a list of functionality supported by real data, and it's going to be the skyscraper.

Point 2: Needs combo by role, not system module

The common error zone is the direct listing function: an inventory, a statement and approval. This way you can see that the A-C side does not recognize the account, and you have to change it to a role perspective.

It is suggested that demand be collected by four categories of actors:

Have people in each role identify five to eight key use cases and give both a baseline, such as "counting 3,000 machines currently takes eight administrators a month," and a target, such as "five working days after go-live." That makes the requirements list credible.

Element 3: The architecture design should give a selection basis, not a stack of terms

The structure chapter is the easiest to write about the right, but useless, kind of "Assisting the clouds, Supporting High-Standing" bullshit. A truly land-defeating structure answers the following questions:

  1. Deployment model: Privatization deployment or SaaS subscription? Enterprises that involve asset data sensitivity usually opt for privatization; SaaS options for quick-on-line and limited budgets.
  2. Integrated object: Which systems are to be reached? Common are ERP, financial software, OA, HR.
  3. Identification method: barcode, QR code, or RFID? Choose RFID for numerous high-value assets that need bulk counts. QR codes are best value for low-cost assets in moderate quantities.
  4. The audit logs record who, when and what.

A system chart is used to draw these relationships more intuitively than three pages of text.

Point 4: Functional planning to cover the full life cycle of assets

The skeleton of the functional chapter is the entire life cycle of the asset, with each link specifying the specific function point and operating scene:

The move end is a frame, not a sub-section. A line employee does not sit in front of a computer to manage the APP.

Point 5: The implementation path should be phased with clear milestones

The project cycle proposes a plan of 8-12 months in three phases:

Key deliverables (systems, documentation, training records) and acceptance standards are listed at each stage to avoid the project being overloaded.

Point 6: Risk and budget need to be written, not cakes

The risk section is not a response to the work, but lists at least three types of risks and options for responding:

The budget section proposes four-part listings of software, implementation, hardware (including RFID tags and inventory guns), services (training + annual security) to avoid the last-minute discovery of an offer.

Element 7: Programme documents themselves should be standardized to facilitate review

A complete asset management system construction programme is proposed to be organized along the following catalogue structure, which will facilitate internal review processes on the one side:

  1. Project context and construction objectives
  2. Current situation research and problem analysis
  3. Operational requirements and functional planning
  4. Technical architecture and deployment programme
  5. Implementation plans and organizational safeguards
  6. Investment estimates and benefit analysis
  7. Risk identification and response measures
  8. After-sale services and transportation programme

Each chapter is contained in 5-8 pages, within 50 pages of the full text.

The design of the asset management system construction programme is essentially to help A to break down the vagueness of "manipulation" into an enforceable action. Shanghai-based technology found in asset management consultations for multiple manufacturing and distribution enterprises that it was possible to review whether the project could be delivered on time, depending largely on whether the two chapters on demand and status were well established. The technical framework is skeletons, business processes are flesh and blood, data landing is soul -- one is not impossible.

If you write this kind of project for the first time, it is suggested that you take a model for industry and fill out the chapters with real data from your own business, faster than from scratch. Read it to a colleague who was not involved in the project, where it's not read, it's too abstract, and needs to continue to be removed.