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

More documents

Recommendations

Info

IS-GPS-705 CRMCID Originator/Org. Page/Para Importance Comment PO Resolution & Concurrence NotesFrom: The block of operational SVs will be termed"Block III" SVs. The Block III operational SVs will Rationale:broadcast the L5 signalFinal To: See paragraph 6.2.3.2.6 of IS-GPS-200.The III operational SVs do broadcast the L5 signal.170 Rhonda SlatteryAerospacePage:Para: 6.3.2SRationale: Consistent definitions across ICDsComment: Need a IIIA version of this Add a IIIAversion of this or TBD placeholderFrom: N/AFinal To: A plot of a typical GPS Block III phasenoise spectral density will be added whenavailable.PO Resolution: AcceptRationale: GPSIII hardware hasn’t been built yet.Concurrence: ConcurRationale:Understand your response, but you haveadded TBDs elsewhere for information thatdoesn’t exist yet. Why not add themthroughout? Or delete them elsewhere?10-sept-09: ICC added a sentence to showthat a plot will be added later.171 Rhonda SlatteryAerospacePage:Para: 6.3.3SRationale: Consistent vision across all SVsComment: Where is the GPS III version of this.Should it go out to space service volume angles?Suggested Change: Add IIIA version or TBDplaceholderFrom: N/AFinal To: A table of a typical GPS Block III ellipticitywill be added when available.PO Resolution: AcceptRationale: GPSIII hardware hasn’t been built yet.Concurrence: ConcurRationale:05/05/09: Defer. Will need to waitUnderstand your response, but you haveadded TBDs elsewhere for information thatdoesn’t exist yet. Why not add themthroughout? Or delete them elsewhere?10-sept-0: a sentence has been added toshow that a table will be added later.172 Rhonda SlatteryAerospacePage:Para: 6.3.4and Section 3Rationale: Consistency between specification andICD and complete definition of the Block IIIrequirements.C Comment: To meet the IIIA and OCX Block 1 and 2specifications, you need at least 40 broadcastPRNs. These need to be defined for the user inthis updatePO Resolution: DeferRationale: Need to determine where the 40 broadcastPRNs requirement came from.If you want to define all 63, which areneeded by a later effectivity, that’s fine too.25-aug-09: refer to AI #16 for resolution.From:Concurrence: ConcurFinal To: Suggested Change: Add 8 more PRNs toRationale: It comes from the CS 800 spec.66
IS-GPS-705 CRMCID Originator/Org. Page/Para Importance Comment PO Resolution & Concurrence NotesSection 3173 Rhonda SlatteryAerospacePage:Para:20.3.3.1.1.4and 20.3.3.2.4CRationale: Current definition of UDRA does notcover all the IIIA and OCX errors.Comment: Where do errors that do not fall cleanlyinto clock or ephemeris get added to UDRA (e.g.,ISC errors, and all the other components of theURE)? Suggested Change: Clarify what errors areincluded in clock and ephemeris UDRA to showusers that all errors are covered as described inthe 800 specifications.From: N/AFinal To: Text in section 20.3.3.2.4: Clock-relatedURA (URAoc) accounts for signal-in-spacecontributions to user range error that include, butare not limited to, the following: the net effect ofclock parameter and code phase error in thetransmitted signal for single-frequency users whocorrect the code phase as described in Section20.3.3.3.1.1.1, as well as the net effect of clockparameter, code phase, and intersignal correctionerror for dual-frequency L1/L2 and L1/L5 userswho correct for group delay and ionosphericeffects as described in Section 20.3.3.3.1.2.2.PO Resolution: AcceptRationale: Will forward to the space IPT forresolution.Concurrence: ConcurRationale: This is in the requirement set for OCX block1, as well as GPS III SS. We need to know this datatoday, and it’s not just a SV problem25-Aug-09: 200 POC to provide verbiageconsistent with the 200. 10-sept-09: ICChas reviewed the 200 and did not see anychanges associated with this comment. ICCwill keep this as a defer and ensure this willbe discussed at the ICWG.10/01/09: Changed to accept. Includeddefinitions in the 20.3.3.2.4 section.10/14/09: Updated this Comment's "To"language to reflect the true nature of theICWG approved change.174 Rhonda SlatteryAerospacePage:Para:20.3.3.5.1.1CRationale: Complete update for IIIA and OCXComment: Coordinate transformations in the userequipment are using the technical note 21conventions. OCX and all SVs are switching to thetechnical note 32 conventions. SuggestedChange: At least insert a note to inform users thatthis is coming. Preferably, incorporate both setsof equations along with the note and a definedswitchover notice.From: N/APO Resolution: AcceptRationale: The commenter is encouraged to presentthe coordinate transformations at the Public ICWG.Concurrence: ConcurRationale:05/05/09: Accept with comment. Willincorporate suggested change uponfinalization of technical note 32conventions. Concurrence: Non-concur.This is in the requirement set for OCX block1. Even without the technical details, thedata contained in the ICD is incorrect andneeds to be fixed. 20-aug-09: 200 ICC toprovide a note that the tech note 21 willchange. 10-sept-09: ICC has placed the 200verbiage in this document.67
Page 4 and 5:
IS-GPS-705 CRMCID Originator/Org. P
Page 6 and 7:
Page 8 and 9:
Page 10 and 11:
Page 12 and 13:
Page 14 and 15:
Page 16 and 17: IS-GPS-705 CRMCID Originator/Org. P
Page 72: IS-GPS-705 CRMCID Originator/Org. P
show all

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

Create successful ePaper yourself

Delete template?

Save as template?