The value and success of standards depends on how widely they are adopted and used. Adoption and use depends on applicability and ease of use of the standard for the use cases it is developed for. This requires that a standard is continuously improved and adapted to the requirements of the users, while at the same time meeting the expected quality standards.
Requirements of users of a standard change over time and so does the user community, which is growing for standards deemed valuable. This means that a process to manage the requests for changes to the deliverables from the users has to be in place.
For FL3DMS (Facilities Lifecycle 3D Model Specification) a Change Request Procedure has been developed. It is based on similar procedures from other standardization initiatives with transparency being an important element. The procedure manages the processes of registration of the Change Request (CR), administration of the change request, approval for working on the change request, delivery of the draft for the change and approval for acceptance of the change.
All users can ask for changes but the participants in the project determine which changes to be handled and how.
The process of the Change Request Procedure is briefly described below. A copy of the Change Request Procedure can be found here
1. Initiating a Change Request:
FL3DMS has streamlined the Change Request initiation process to ensure that stakeholders can propose changes efficiently. Participants, users, or any other relevant stakeholders can initiate a Change Request by completing a standardized form. This form captures essential details, including the nature of the change, its impact on project components, and the rationale behind the proposed modification.
To ensure consistency and precision in documenting change proposals, FL3DMS (Facilities Lifecycle 3D Model Specification) provides a user-friendly CR template in the form of an Excel spreadsheet. This template is available for download through the project's SharePoint platform, allowing participants and other stakeholders to access and utilize it efficiently.
Once the Submitter completes the CR Form, the next step is to forward it to the Secretary via email. This streamlined submission process ensures that Change Requests are promptly received and ready for evaluation by the team. The form can be send to: This email address is being protected from spambots. You need JavaScript enabled to view it..
Download here
2. Registration, Evaluation and Impact Assessment:
All Change Requests with the required information will be registered in the CR register, which contains all CRs and their status. An audit trail from CRs to changes made to the deliverables is secured.
Once a Change Request is submitted, it undergoes a thorough evaluation for approval to work on it and implement a solution. Dedicated teams and eventually all participants carefully review the proposed changes to assess their feasibility, potential impact, and alignment with project objectives. This evaluation is critical in maintaining the project's overall integrity and ensuring that any approved changes enhance, rather than hinder project outcomes.
3. Implementation:
Approved Change Requests move into the implementation phase. The team responsible for the approved CR will work on a draft for the solution for the CR.
4. Review and Approval:
The proposed solution for the CR will be reviewed by all participants and updated if required until consensus is achieved among the participants that the solution is appropriate for adoption in the standard.