In the past, MN.IT has accepted change requests from many paths, including email, telephone, and in-person visits. However, these requests can be quite complex and it is easy to omit important information or make mistakes when using the more informal methods. Going forward, MN.IT is strongly encouraging requests to come in via the Border Control Zone Request form. The rest of this document will assume that that form was used to start the request.
This document is focused on processing requests for incremental changes to existing zones. Setting up a new zone is a more complex process and is handled on a custom basis.
All requests go through the following review process:
In the case where the request is complete, sensible, complies with the security policy, doesn't involve other contacts, and has no scheduling constraints, the review and implmentation normally happens within one business day, which means that a request received today will be implemented by the end of (business day) tomorrow.
As an example, a request for a change to an Executive Branch zone may be received at 2pm. It will be checked and reviewed by the next MN.IT Joint Review Committee session and scheduled for implementation the next day.
The cutoff for requests that must be processed by the MN.IT Joint Review Committee is 8am (each business day). Requests received after that time may not be considered until the next business day.
Note that the change policies for some zones require additional notice. For those zones, all that we can do by the next business day will be to have completed the scheduling process. The implmentation will happen when permitted by the zone's policy.
It is sometimes the case that you need to add new functionality but you aren't sure exactly what rules are required. In such a case:
This is for a new application.
Seeing this text in the Notes field, we will contact you to arrange a time (or times) to work out the exact rules. Once the exact rules have been determined, we will update the request with the exact rules. If Executive Branch organizations are involved, the final rules will be reviwed by the MN.IT Joint Review Committee.