BIS Mapping
Repository Service
A managed Git Service for integration projects in BIS
Challenges in mapping project management
BIS customers currently need to operate their own Mapping Repository or rely on external services such as GitHub, GitLab, or Bitbucket to version their mapping projects. This setup often results in:
Introducing the BIS Mapping Repository Service in BIS
The BIS Mapping Repository Service provides a fully managed Git environment embedded directly in the BIS Hub design time, purpose-built for BIS mapping projects. It makes repository-based mapping management easier and more visible for all customers while supporting established BIS 6.7 development workflows through direct integration with BIS Developer Studio.
Core features
Who benefits from the BIS Mapping Repository Service
- Perform Git versioning directly from BIS Developer Studio, minimizing setup and context switching.
- Store projects securely in standardized cloud repositories, improving consistency across the team.
- Gain central visibility into all mapping projects in BIS Hub, facilitating collaboration and monitoring.
- Apply consistent repository structures for easier project management and reporting.
- Eliminate internal infrastructure needs, reducing operational complexity and costs.
- Use secure Personal Access Tokens for controlled and auditable access.
- Maintain centralized oversight of repositories and permissions.
Why this service stands out
Managed Git service usable from BIS Hub and BIS Server:
No external systems or IT maintenance required.
Standard Git compliance:
Ensures compatibility with widely used Git tools and workflows.
Fully integrated into BIS Hub design time:
Reduces context switching and accelerates development.
Foundation for future web-based mapping
and deployment capabilities:
Establishes a central repository foundation that can support broader design-time and deployment capabilities over time.
Typical use cases
Creating a Git repository through the BIS Hub UI:
Set up a new repository quickly for mapping projects without external servers.
Generating a Personal Access Token for secure Git operations:
Authenticate commits, pushes, and pulls without passwords.
Performing commits, pushes, and pulls
from BIS (6.7) Server Developer Studio:
Manage versioning directly in the developer environment for efficiency.
Viewing mapping projects
in the web or local in the Developer Studio:
Integration teams and governance stakeholders can monitor projects centrally.
Managing multiple repositories per customer:
Organize multiple mapping projects efficiently within a single managed environment.
Conclusion and strategic benefits
The BIS Mapping Repository Service replaces customer-specific Git setups with a secure, fully managed solution in BIS Hub. At the same time, it establishes a central repository foundation that supports current BIS 6.7 development workflows and can serve as a practical starting point for broader design-time evolution over time.
Interested in learning how the BIS Mapping Repository Service can simplify and secure your mapping workflows?