Gridsz Build is a module that enables you as a network owner to manage and steer your network rollout process. Every step in the construction phase, from requesting permits to completed connections, can be accurately tracked with full visibility into every single connection point.

During the rollout, your network data in Build is automatically and simultaneously synchronized with the other Gridsz modules that you use (or via API with your own systems). This makes every planned connection immediately visible to your active operators and providers and they can already order connections as they become available during the construction phase.

Build Management Service

The Build Management Service is the cornerstone of Build. This service uses four primary entities:

• Buildings
• Commercial Areas
• Construction Projects
• Points of Presence (PoPs)

Additionally, the Build Management Service empowers users to perform bulk editing on all connections associated with specific buildings. While bulk editing can often present challenges due to validations, Build offers users the option to bypass these rules, enhancing flexibility during data updates.

Overriding the validations may lead to unexpected data outcomes. Users are advised to exercise caution when executing this action.

Lastly, users can also specify the utilized Import Types of Build through this feature.

The majority of functionalities are accessible via APIs, with only a select few available through the GUI.

Status Model

The Status Model component illustrates the progression and status of Buildings, Construction Projects, Commercial Areas, and PoPs. It empowers Cluster admins to tailor workflows for specific entities by:

• Creating, reading, updating, and deleting (CRUD) statuses
• Defining transitions between these statuses

In the current iteration, users can solely add new statuses or transitions. For updates or deletions of a status or transition, please reach out to the Gridsz Support team.

Validation Service

All data inputs undergo validation to ensure compliance with established rules before storage in the BUILD database, in the majority of cases. Build offers a combination of pre-defined and tailored validation rules to maintain data integrity.

Any action failing validation will prompt a notification to the actor, detailing specific reasons for the failure. This feedback assists in rectifying data errors efficiently.

Import Service

To expedite the daily, weekly, or monthly updating of work progress in BUILD, Network Owners and Contractors have the option to upload CSV files containing their work to Google Bucket. Subsequently, BUILD will seamlessly import these files into the system.

Each party utilizes their own CSV templates for importing data. Understanding this diversity, BUILD offers a feature enabling Cluster admins to define custom “Import Types” tailored to their networks’ requirements.

Data synchronization: event-based API

To ensure seamless data synchronization across modules within the Gridsz platform, Build continuously transmits updates regarding the four main entities to a PubSub Server. This enables other modules to establish their subscriber mechanisms for accessing necessary data.

Given that most customers have a long-standing history with the Availability Checker, there’s a substantial amount of building and address data stored within it. To migrate this information to Build, we’ve established a daily cronjob. This cronjob retrieves all newly updated addresses for the day from Availability and seamlessly updates them in Build.