THE PNP ARCHITECTURE CONSISTS OF CORE SERVER-SIDE FUNCTIONALITY AND INTERFACES THAT ALLOW SOFTWARE CLIENTS TO INTERACT WITH THE CORE SIMULATION VIA AN APPLICATIONS PROGRAMMERS INTERFACE (API). THE SOFTWARE CLIENTS IMPLEMENT THE CODE THAT REPRESENTS NEXTGEN CONCEPTS. CLIENTS CAN REQUEST DATA, AND CAN SEND BACK TO PNP MODIFICATIONS OF THE DATA, INCLUDING FOR EXAMPLE, FLIGHT PLAN MODIFICATIONS VIA THE API. THE CONTRACTOR SHALL CREATE SEPARATION ASSURANCE (SA) CLIENT SOFTWARE AND ENHANCE THE PNP CORE FUNCTIONALITY TO SUPPORT THE REQUIREMENTS OF CURRENT AND ANTICIPATED FUTURE NASA DEVELOPED TACTICAL AND STRATEGIC SEPARATION ASSURANCE (SA) ALGORITHMS. THE CONTRACTOR SHALL DEVELOP THE SA CLIENT WITH THE CAPABILITY TO RECEIVE MESSAGES FROM THE PNP SERVER; PROCESS DATA; AND SEND REROUTE REQUESTS TO THE PNP SERVER. THE CONTRACTOR SHALL COLLABORATE WITH NASA RESEARCHERS TO DESIGN A GENERAL SA CLIENT AND TO DEVELOP AN AGREED UPON LIST OF REQUIRED SA CLIENT FUNCTIONS AND CAPABILITIES. NASA WILL APPROVE THE DOCUMENTED REQUIREMENTS PRIOR TO IMPLEMENTATION. THE CONTRACTOR SHALL, AT A MINIMUM, MAKE THE FOLLOWING ENHANCEMENTS TO PNP: CLIENT SOFTWARE THAT IMPLEMENTS THE CONTROL FUNCTIONS REQUIRED TO ALLOW OPERATION OF SA ALGORITHMS WITHIN THE PNP CORE FUNCTIONS. INTERFACES TO PNP THAT ALLOW THE SA CLIENT TO ACCESS TRAJECTORY STATE AND INTENT INFORMATION FOR OWN-SHIP AND ALL OTHER FLIGHTS IN THE SIMULATION WITHIN A RANGE SPECIFIED BY DISTANCE OR TIME (TO SIMULATE ADS-B OR OTHER DATA LINK COMMUNICATION CAPABILITY). STATE INFORMATION INCLUDES CURRENT LATITUDE, LONGITUDE, ALTITUDE, AND VELOCITY (RELATIVE TO GROUND AND AIR). INTENT INFORMATION INCLUDES LATITUDE, LONGITUDE, ALTITUDE AND PROJECTED INTERCEPT TIME FOR EACH WAYPOINT IN THE TRAJECTORY.