DRAFT IS-GPS-705A Comment Resolution Matrix - GPS.gov

IS-GPS-705 CRMCID Originator/Org. Page/Para Importance Comment PO Resolution & Concurrence NotesChange: Insert the following paragraph after Rationale: Karl Kovach has developed some continuityparagraph 3.3.1.5 Phase Continuity While a language to replace 3.3.1.5. Need to discuss thesatellite is broadcasting standard I5 code and implementation at the next ICWG.standard Q5 code signals, there shall be nodiscontinuities that exceed 10 degrees (TBR) as Concurrence: Concurmeasured over any interval up to and including 10seconds, in the respective I5 or Q5 carrier phase Rationale:other than those attributable to the binary stateof the modulating signals.From: Request GPS Wing formally commenceTechnical Interface Meetings (TIMs) withparticipation by government only stakeholdersand their direct support government contractorsto support the evolution of language for this topic,and where it and any associations are or would benoted throughout this and other GPS Wingprescribed interface specifications (IS), systemspecifications (SS), and performance standarddocuments. TIMs should commence prior to thenext GPS Wing ERB meeting on this IS, while anyfinal proposed language intended forimplementation into this IS continue to bedeferred until the next or succeeding ICWG whereconcurrence by both federal and non-federalstakeholders in attendance or otherwiserepresented can be secured.Final To: Suggested Change: Insert the followingparagraph after paragraph 3.3.1.5 PhaseContinuity While a satellite is broadcastingstandard I5 code and standard Q5 code signals,there shall be no discontinuities that exceed 10degrees (TBR) as measured over any interval up toand including 10 seconds, in the respective I5 orQ5 carrier phase other than those attributable tothe binary state of the modulating signals.Rationale: Most precision GPS positioning, velocity28comment submitted for this review cycle inMarch 2009. First, request for the Civil’s tobe involved in TIMs with Karl Kovach tocoordinate, facilitate and lastly expedite aninterface specification/language that couldbe satisfactory for presentation andapproval by next ICWG attendees.Secondly, suggestion change(s) andrationale remain in effect as the Civil’srepeated response on this issue. 8/6/09:see comment 74, 124, 125 from 200 CRMfor resolution. need to touch base with KarlKovach for proposed language. 10-sept-09:If there is Phase "discontinuity," that is afailure that would fall under section3.2.5.2.3.2 Severe Signal Deformation of theSS-SS-800. There is nothing in thedocument that would allow a SV contractorto have a phase discontinuity that isn'tconsidered a failure. placing a requirementin there for "continuity" may give the SVcontractor the impression that phasediscontinuities are allowed. In the otherpublic SIS documents, phase continuity is inthere becuase we are concerned with theinteraction between two different signalson the same carrier.