SAP PURCHASE REQUISITION: 4200254357 THE CONTRACTOR SHALL IDENTIFY OPPORTUNITIES TO LINK EXISTING, STAND-AL…

Public award description

SAP PURCHASE REQUISITION: 4200254357 THE CONTRACTOR SHALL IDENTIFY OPPORTUNITIES TO LINK EXISTING, STAND-ALONE ATM SIMULATION SOFTWARE CODES AS A MEANS OF CREATING A COMBINED, EXTENDED CAPABILITY. ASSESS THE FEASIBILITY OF INTEGRATING MULTIPLE, STAND-ALONE MODELING AND SIMULATION CODES WITH OTHERS IN THE NASA ATM TOOL SUITE. PERFORM AN INITIAL INTEGRATION OF THE SELECTED CODES USING APPROPRIATE MIDDLEWARE TECHNIQUES. 4.1.1 TASK 1. THE CONTRACTOR SHALL INVESTIGATE THE FEASIBILITY AND UTILITY OF LINKING, THE FOLLOWING STAND-ALONE SOFTWARE CODES AS A MEANS OF CREATING AN INTEGRATED, AND EXTENDED AIRSPACE ANALYSIS CAPABILITY. 1) INTEGRATION OF TRAFFIC FLOW MANAGEMENT (TFM) SOFTWARE WITH ACES. CANDIDATE TFM CODES INCLUDE: COMMAND AND CONTROL (C2) TFM SOFTWARE DEVELOPED BY METRON AVIATION UNDER CONTRACT NNL06AA01C. 2) INTEGRATION OF THE KB3D CONFLICT DETECTION AND RESOLUTION ALGORITHM WITH ACES. CANDIDATE CODES INCLUDE: THE KB3D ALGORITHM WAS DEVELOPED IN THE SAFETY CRITICAL AVIONICS SYSTEMS BRANCH AT NASA LANGLEY RESEARCH CENTER. FOR EACH SOFTWARE CODE OPTION LISTED ABOVE, THE CONTRACTOR SHALL CREATE A LIST OF ASSOCIATED SOFTWARE DEVELOPMENT TASKS, AN ESTIMATE OF THE CORRESPONDING DEVELOPMENT COST AND EXPECTED LEVEL OF ANALYSIS CAPABILITY ENHANCEMENT. THE CONTRACTOR SHALL ALSO IDENTIFY POTENTIAL CHALLENGES AND OBSTACLES ASSOCIATED WITH EACH INTEGRATION OPTION. THIS INFORMATION WILL BE PRESENTED TO NASA PERSONNEL. NASA WILL THEN SELECT THE INTEGRATION APPROACH TO BE USED IN TASK 2. THE CONTRACTOR SHALL IDENTIFY SOFTWARE INTERFACING TASKS AND CANDIDATE CODES FOR FURTHER INVESTIGATION. 4.1.2 TASK 2. FOR THE SOFTWARE DEVELOPMENT EFFORT SELECTED IN TASK 1, THE CONTRACTOR SHALL EXPLORE AT LEAST TWO APPROACHES FOR LINKING THE SOFTWARE CODES. THE CONTRACTOR SHALL THEN PROVIDE TO NASA, IN THE FORM OF THE DETAILED PLAN D4, THE RECOMMENDATION FOR THE PREFERRED LINKING ARCHITECTURE, ALONG WITH THE BASIS FOR THAT RECOMMENDATION. THE CONTRACTOR SHALL GENERATE A SOFTWARE DEVELOPMENT PLAN AS PART OF THE DETAILED PLAN. THE LINKING ARCHITECTURE CAN USE COMMON MIDDLEWARE TECHNIQUES OR DIRECT INTEGRATION OF CODE, E.G. VIA A PLUG-IN INTERFACE AS USED BY THE ACES SIMULATION CODE. THE CONTRACTOR SHALL EXAMINE THE DETAILS OF THE COMMON MIDDLEWARE AND DIRECT INTEGRATION OPTIONS ALONG WITH DETAILS ASSOCIATED WITH TIME MANAGEMENT, NAS COMMON OBJECT MODELING AND SERVICE ORIENTED AND LIBRARY ORIENTED INTERFACES SPECIFICATION AND IMPLEMENTATION. NASA WILL THEN SELECT THE LINKING APPROACH TO BE USED IN TASK 3. 4.1.3 TASK 3 LINK AND INTEGRATE THE SELECTED SOFTWARE CODES FROM TASK 1 ABOVE, USING THE APPROVED LINKING APPROACH SELECTED FROM TASK 2 ABOVE. AT THE CONCLUSION OF TASK 3, THE CONTRACTOR SHALL DEMONSTRATE SUCCESSFUL INITIAL, INTEGRATED SOFTWARE FUNCTIONALITY. THE CONTRACTOR SHALL COLLECT AND MANAGE CHANGES TO SOFTWARE REQUIREMENTS. THE CONTRACTOR SHALL ENSURE THAT THE SOFTWARE CODE IS UNIT TESTED PER THE PLANS FOR SOFTWARE TESTING. THE CONTRACTOR SHALL COMPLETE AND DELIVER DOCUMENTATION TO SUPPORT THE OPERATION AND MAINTENANCE OF THE SOFTWARE PRODUCT. THE CONTRACTOR SHALL ESTABLISH AND IMPLEMENT PROCEDURES FOR STORAGE, HANDLING, DELIVERY, RELEASE, AND MAINTENANCE OF DELIVERABLE SOFTWARE PRODUCTS. THE CONTRACTOR SHALL THEN IMPLEMENT AND EXECUTE THE DETAILED PLAN.