Amendment 9531BM24Q0020P00002 - UAS Fleet Mgmt Software.pdf

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing items 8 and 15, and returning or (c) By separate letter or electronic communication which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE

RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by letter or electronic communication, provided each letter or electronic communication makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

E. IMPORTANT: Contractor is not is required to sign this document and return copies to the issuing office.

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

1. CONTRACT ID CODE

2. AMENDMENT/MODIFICATION NUMBER 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQUISITION NUMBER 5. PROJECT NUMBER (If applicable)

7. ADMINISTERED BY (If other than Item 6) CODE

STANDARD FORM 30 (REV. 11/2016)

Prescribed by GSA FAR (48 CFR) 53.243

FACILITY CODE

9A. AMENDMENT OF SOLICITATION NUMBER

9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NUMBER

10B. DATED (SEE ITEM 13)

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers is extended. is not extended.

12. ACCOUNTING AND APPROPRIATION DATA (If required) copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NUMBER AS DESCRIBED IN ITEM 14.

CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER

NUMBER IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation data, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15C. DATE SIGNED

15A. NAME AND TITLE OF SIGNER (Type or print)

16C. DATE SIGNED

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

PAGE OF PAGES

6. ISSUED BY CODE

8. NAME AND ADDRESS OF CONTRACTOR (Number, street, county, State and ZIP Code) (X)

CODE

15B. CONTRACTOR/OFFEROR

(Signature of person authorized to sign)

16B. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

Previous edition unusable

P00002

See page 2 for details.

NTSB Acquisition Division 490 L'Enfant Plaza East SW Washington, DC 20594-0003

9531BM24Q0020

1 3

09/19/2024

09/11/2024

9531BM24Q0020 – UAS Fleet Management Software

Amendment P0002 – Questions & Answers

The following responses are provided to questions received prior to the deadline for receipt of questions:

1. Could you elaborate on the expected scope of real-time tracking for flights, aircraft, and flight crews across different locations? Does the NTSB anticipate the need for integration with external geospatial or flight tracking systems to complement the core solution?

NTSB Response: Initially, we are looking at the ability for missions to “auto upload” to the applicable Fleet Management program, tracking of battery cycles, etc. Not exactly “real time tracking as it’s happening” All this with pilots that operate across the country and not from a centralized “home base.” Potential for future integration with external geospatial or flight tracking systems – but not “hard fast requirement” for contract.

2. Could you provide more detail on the importance of mobile app availability for fleet management? Specifically, are there any scenarios where offline functionality would be required?

NTSB Response: The ability to access pre-flight briefing and pre/post-flight checklists, weather briefings, etc., from iOS mobile devices (i.e., iPad/iPhone) – as well as the ability to conduct overall mission planning, risk assessment documentation, and access to team documentation (i.e. SOP, FOM, FTM).

3. We understand that training is a key part of the implementation. Could you provide more information on the types of users (administrators vs. end-users) training is required.

NTSB Response: Likely 2 Administrators that would have full access to settings, features, editing, etc. Approx 15 pilots to log normal flights, mission requirements, etc – not editing checklists, entering new aircraft, etc.

4. Who will need access to the system? Will it be limited to administrators, or will crew members and pilots also require direct access to perform specific tasks such as entering flight logs or managing assets?

NTSB Response: All would require some level of access – as mentioned above, likely 2-3 with full admin rights, but all pilots with access to enter flight logs, utilize checklists, and risk management tools.

5. Regarding the requirement for 24/7 on-call technical support, could you clarify the specific support expectations for mission-critical issues? Are there defined response time requirements or escalation procedures that the NTSB would expect as part of this service?

NTSB Response: We would expect a basic level of 24/7 critical support for major connectivity issues, and/or entering system “help tickets” etc. However, we will have our own redundancy built in to operate in the event of a temporary system outage.

6. Could you provide more details on the level of customization needed for the checklists and workflows? For example, are there specific templates or forms already in use that need to be replicated in the new system, or will these need to be designed from scratch within the platform?

NTSB Response: We would like the ability to enter our own checklist items for each of a number of internally used checklists (i.e., pre-flight mission briefing, mission risk analysis, pre/post flight checklists, post flight mission briefing, weather briefing, etc.) These would be varied between type aircraft, and potentially type mission as well. We do not want to be required to use “canned” checklists provided by the program provider.

7. Are there existing workflows that need to be integrated with the new system, or are you expecting to develop new workflows entirely within this platform?

NTSB Response: We have formalized mission briefing, on-scene checklists, weather briefing, and safety risk assessment procedures – so we do want the ability to have our own customized workflow.

8. Will all user roles (e.g., administrators, crew members, pilots) need access to edit or interact with checklists and workflows, or will certain functions be restricted to specific roles?

NTSB Response: The administrators need access to edit, crewmembers need access for use/entry

– NOT editing or development. We would like the ability to set permissions for all team members.

9. What level of automation do you expect in the workflow system? For example, should certain tasks or notifications be triggered automatically based on flight or mission events, or are most workflows expected to be manually driven?

NTSB Response: Most workflows may still be manually driven – but the more we can automate with regard to logging flights, etc. – the better. Notifications when a mission has begun/closed are valuable.