Target release3.1
Epic

Document status

Document owner
Sam Im (Deactivated)
Technical LeadTechnical Lead who reviews or supports document


Goals/Scope

Background

The administrator is the only user that will create, assign, and edit facilities. Facility data is gathered prior to beginning configuration of OpenLMIS. Facility types are predefined and necessary for facility management.

Assumptions

User Stories


#TitleUser StoryLabelImportanceJIRA Tickets
1Creating or edit a facilityAs an administrator I need to create a new facility so that I can update assignments to use the new facility in the requisition process.


Acceptance Criteria:

  • Create new facility with required fields: Facility code, facility name, facility type, Active Facility (Y/N), Operational date selection, Geographic Zone drop-down selection (per existing data setup)
  • Validation for facility fields: text field data exists, radio button selected for Y/N
  • Error messages for field validation before saving
  • Associate supported programs and start dates (schedules)
  • Admin can select a facility from search page to edit
  • Admin can edit facility fields
Relevant labels to distinguish source. From which system, or which country? Must Have, Nice to Have
  • Geographic Zone setup must be included (Would this be a separate setup process or part of this story?)
  • Assigning the supported programs and schedules
  • Should certain fields be uneditable once they've been created and assigned? To be determined for a future implementation.
  • Facility Codes can change per business requirements
2View & Assign an existing facility

As an administrator I need to assign facility details so that the facilities are utilized in the requisition process

Acceptance Criteria:

  • Admin can view list of existing facilities and associated details of the facility or search for a specific facility to take further action (edit a facility user story below)
  • Adding or editing programs and schedules to facility





4Facility FTP Settings

As an administrator I need to add and edit Facility FTP settings by facility so that I can complete the setup for the requisition workflow process.

Acceptance Criteria:

  • Admin can select facility from search page to add Facility FTP settings
  • Admin can edit Facility FTP settings by facility


 (moved to Supply Lines feature)

Diagrams


Dependencies

Identify initial dependencies that are on the critical path for this functionality and may affect the delivery time and serving of business goals. Include links to stories.

DescriptionLink
Name of story or release Link to JIRA


Open Questions

Initial communication between stakeholders and the development team to help understand scope and estimates.

Below is a list of questions to be addressed as a result of this requirements document:

#QuestionOutcomeStatus
1

Is the designation for Service Delivery Point needed? Per the 2.0 Configuration Guide: "The facility is SDP attribute is a flag to indicate whether or not this facility is a service delivery point. The setting for this flag does not control whether or not a facility can submit requisitions or receive deliveries, but is useful for sorting facilities when generating reports." Which reports?

SDP is not in current v3 schema and would need to be added to whole stack per Chongsun.

Mary Jo Kochendorfer (Deactivated): I think it is okay if we leave this off for now. Open, In Progress, Closed, and date of closure
2Once a facility has been given a "Go-Live Date" should this be made uneditable? Change "Go-Live" in UI to say Operational Date, or Effective Date?Mary Jo Kochendorfer (Deactivated): What is the impact of making it editable? I think it is okay to leave this editable since someone may accidentally put the wrong date. Since the Admin is the only making edits I think it would be okay. I'm not partial to which wording to use. We should check if this date is referenced for reporting.
3Once a program Start Date has been entered, should this be made uneditable?

Mary Jo Kochendorfer (Deactivated) : I feel the same way as above.


4Facility codes can change per business use cases, once they've been created. How will this be tracked and managed? This appears in user dropdown selections and some reports (R&R). What is the desired behavior? What is the behavior if the process for changes is a batch upload for multiple facility updates? (example, facility changes are completed in a batch process in a UAT environment, reviewed, and then scheduled to run in production after it has been approved)

Out of Scope