Prior Information Notice For Software package and information systems

Prior Information Notice For . Ii.4) Short Description Of Nature And Scope Of Works Or Nature And Quantity Or Value Of Supplies Or Services: The Federal Ministry Of Defense Plans To Procure A Battlefield Management System (Bms) And A Command Information System (Füis) With Project Support For The Digitization Of The Armed Forces, Taking Into Account The Following Framework Conditions: • The Software Must Consist Of At Least One Füis Module To Support The Staff Procedure And One Bms Module To Support The Commanders Procedure, Which Can Be Run And Licensed Separately. • The Software Must Have At Least A Trl 8 In The Version To Be Offered Later. • The Software Must Be Demonstrably Introduced In The Later Version To Be Offered By The Armed Forces Of Several (At Least 2) Nato Nations Or Nato Partner Nations. This Includes Neither Test Positions Nor Trial Operations. • The Software Must Be Terminal-Independent. • It Must Be Possible To Integrate The Software Into A Mission Net, Which Is Instantiated And Operated According To Fmn Principles (Fmn.... Federated Mission Networking). • The Software Must Be Interoperable And Therefore Offer The Current Fmn Service Instructions Relevant For Füis And Bms. • The Software Must Be Used In Classrooms, Relocatable Command Posts, On Vehicles, And On People During Training, Exercises, And Operations. • The Software Must Be Able To Run On Notebooks, Tablets And Handhelds And Therefore Be Optimized For Different Resolutions. • The Contractor Must Submit A Maintenance Plan For The Software, Which Must Include The Api. • The Implementation Of The Software Implementation Project Takes Place In German. • The Software Must Offer The Bmlv And Third Parties The Opportunity To Expand The System Via Open And Documented Programming Interfaces (Api) With A Development Environment (Sdk). The Apis Provided Must Allow The Software To Be Extended Or Modified At Any Level. Api Must Be Available For (At Least): ◦ The Integration Of Sensors (Sensor Integration Api), ◦ The Integration Of Communication Devices That Are Independent Of The Underlying Hardware Or Transport Protocols And Support Both Ip And Non-Ip Interfaces (Radio Driver Api), ◦ Integration With External Systems Via Web Services (Web Services Api), ◦ The Extension Of The User-Oriented Application With New Functions And Ui Components (Application Api), ◦ Changing And Expanding The Symbology Used By The Application (Custom Symbology Api), ◦ Interacting With The Gisclient, Which Allows Layers And Symbols To Be Displayed In Addition To The Native Information Displayed By The System Itself (Gis Api) ◦ All Apis Must Be Backwards Compatible To Reduce The Effort Involved In Migrating The Software And Addons To A New Version Of The Product.