ERP Business Analyst in Boston

Interviewing scientists, clinicians and engineers who have little time

In a Cambridge lab, a teaching hospital department or an engineering group in the suburbs, the people who know how work really happens are also the people with the least free time. A principal investigator may approve purchases from a phone between experiments. A clinical research manager may be the only person who knows how site payments are tracked. Asking them to attend a series of long workshops rarely works.

I adapt the method instead. Short interviews with a fixed list of questions, sent in advance, cover the essentials. When a task is clearer on screen than in words, a recorded screen walk-through of the current spreadsheet or portal replaces a meeting. Administrators and department finance staff, who handle the detail day to day, get longer sessions because they can describe exceptions accurately.

After each conversation I send a written summary for the person to correct. That step matters more in Boston than in many places, because the requirements will later be read by auditors, sponsors or contracting officers who expect precision. It also gives busy experts a way to contribute without another meeting. The US ERP business analyst page covers sales tax, vendor reporting and multi-entity requirements that apply across the country.

Sponsored awards: effort, cost transfers and subawards as requirements

Research institutes, universities and hospital-affiliated research groups carry awards with detailed rules on how costs are charged. When these organizations replace a finance or grants system, the requirements often stop at the obvious: create an award, record a budget, report spending. The harder parts are where projects go wrong.

Payroll distribution is one. Salaries are split across several awards and departmental funds, the split changes during the year, and effort reported later has to agree with what was charged. Cost transfers are another: moving a charge from one award to another needs a reason, an approval and a time limit set by your own policy. Subawards to partner institutions bring invoices that must be checked against budgets and progress before payment.

I write each of these as a requirement with an example and a pass condition. For instance, a cost transfer without a written justification cannot be posted, or an effort statement cannot be certified while payroll for that period is still open. How federal cost principles apply to your organization is a matter for your sponsored programs office and auditors. I see to it that the chosen system can enforce whatever they decide.

Defense and aerospace suppliers in the suburbs

Greater Boston has a long-standing base of defense electronics, sensor and aerospace companies, and many smaller manufacturers and engineering firms supply them. Once a company takes on government contracts directly or as a subcontractor, its finance system faces expectations that commercial customers never asked for.

The requirements usually include timekeeping where employees record hours against specific charge codes, with corrections that leave a visible trail. Costs must be grouped into pools so that indirect rates can be calculated, and unallowable costs must be kept apart. Billing may follow formats set by the contract, and some customers require reports on progress against budget. Controlled technical data and cybersecurity requirements can affect where the system is hosted and who may administer it.

I capture these needs in plain language, map where the data comes from and flag every point that depends on contract terms or regulation. Whether a given system or hosting arrangement satisfies a particular clause or cybersecurity standard is a question for your contracts and compliance advisors, so I mark those items for their review rather than answering them myself. The engineering industry page describes the project accounting side in more depth.

Massachusetts data security rules and the access requirements they imply

Massachusetts has a data security regulation that expects businesses holding personal information about residents to maintain a written information security program. In an ERP project, that program becomes a source of concrete requirements, yet it is often left out because nobody connects the policy document to the system design.

Personal information sits in more ERP corners than people expect: employee records and bank details in payroll interfaces, customer and donor contact data, vendor tax identifiers and student or patient billing details passed from other systems. I work through each area with your security lead and write requirements for role-based access, separation of duties between those who create vendors and those who pay them, masking of sensitive fields in reports and exports, and logs that show who viewed or changed what.

These requirements also help with vendor due diligence. A platform that cannot restrict field-level access or keep a usable audit trail is easier to spot during scripted demonstrations than after go-live. Interpretation of the regulation and any notification duties remains with your counsel. The requirements simply make sure the chosen system does not undermine the program you already have.

What you receive and how it carries into testing

At the end of the analysis you hold a requirement catalog with a numbered entry for each need, its owner, its priority and a pass condition. Alongside it sit process maps for the flows that cross departments, a list of open questions for your advisors, and a glossary that settles what terms like award, project, fund and cost center mean in your organization. In Boston institutions those words are used differently from one department to the next, and agreeing them early prevents confusion later.

The catalog feeds vendor evaluation directly. Each platform or implementer answers the same numbered items, and scripted demonstrations follow scenarios drawn from your own work, such as moving a lab purchase between awards or charging an engineer's hours to the right contract.

Later, the same numbers become the backbone of user acceptance testing. Each test traces back to a requirement and its owner signs it off. If you already have a platform in mind, see freelance ERP consulting in Boston for second opinions on proposals, or the requirements gathering service for the general method.